You can extract it from the bin files sammyz found depending on which one you're after (zv5/zv6). That's where I get my original images from. Hope that helps.
How would i extract it from the bin files?
Upvote
0
You can extract it from the bin files sammyz found depending on which one you're after (zv5/zv6). That's where I get my original images from. Hope that helps.
If u cant get what you need with the bin extracter i will gladly do the unbrick method after work tomarow... so let me know.
Writing Files...
Writing File : 0-PrimaryGPT.img -- DONE --
Writing File : 1-modem.img -- DONE --
Writing File : 2-sbl1.img -- DONE --
Writing File : 3-sbl2.img -- DONE --
Writing File : 4-sbl3.img -- DONE --
Writing File : 5-aboot.img -- DONE --
Writing File : 6-rpm.img -- DONE --
Writing File : 7-boot.img -- DONE --
Writing File : 8-tz.img -- DONE --
Writing File : 9-system.img -- DONE --
Writing File : 10-system.img -- DONE --
Writing File : 11-system.img -- DONE --
Writing File : 12-system.img -- DONE --
Writing File : 13-system.img -- DONE --
Writing File : 14-system.img -- DONE --
Writing File : 15-system.img -- DONE --
Writing File : 16-system.img -- DONE --
Writing File : 17-system.img -- DONE --
Writing File : 18-system.img -- DONE --
Writing File : 19-system.img -- DONE --
Writing File : 20-cache.img -- DONE --
Writing File : 21-cache.img -- DONE --
Writing File : 22-cache.img -- DONE --
Writing File : 23-cache.img -- DONE --
Writing File : 24-cache.img -- DONE --
Writing File : 25-cache.img -- DONE --
Writing File : 26-cache.img -- DONE --
Writing File : 27-userdata.img -- DONE --
Writing File : 28-userdata.img -- DONE --
Writing File : 29-userdata.img -- DONE --
Writing File : 30-userdata.img -- DONE --
Writing File : 31-userdata.img -- DONE --
Writing File : 32-userdata.img -- DONE --
Writing File : 33-userdata.img -- DONE --
Writing File : 34-userdata.img -- DONE --
Writing File : 35-userdata.img -- DONE --
Writing File : 36-userdata.img -- DONE --
Writing File : 37-userdata.img -- DONE --
Writing File : 38-persist.img -- DONE --
Writing File : 39-recovery.img -- DONE --
Writing File : 40-BackupGPT.img -- DONE --
Finished
I like the rom and the fact that you got the most garbage removed, butttt the camera sucks, also the QSLIDE get it removed please . . I dont understand why all this time. . that should have been the first thing removed.
I like the rom and the fact that you got the most garbage removed, butttt the camera sucks, also the QSLIDE get it removed please . . I dont understand why all this time. . that should have been the first thing removed.
As for the camera and the gallery app, that's what was in the cm rom I compiled. If you don't like it, use another. If you want the stock camera and gallery apps, pull them from the deodexed stock rom.
Guys, i'm tired of defending the apps in this rom. This is just how it is. If you don't like it, swap them out or use a different rom. Stop asking for the stock apps back. If you want stock, use a stock rom.
For now on, if anyone asks for a stock app to be placed back into this rom I'm going to ignore it.
I like the rom and the fact that you got the most garbage removed, butttt the camera sucks, also the QSLIDE get it removed please . . I dont understand why all this time. . that should have been the first thing removed.
enjoying this rom other than constant errors with random programs. will watch this closely and post specifics as they come up thanks man!!!
Yea full wipe and cleared dalvik cache too. I ended up reinstalling yesterday after i posted that because i accidentally did a system update. Only issue i have now (other than errors youve listed on this thread) is xbmc remote crashes when opening a shared folder, this did not happen on the stock zv5 or zv6. Not sure if thats something you could help me with tho
Hey guys, I just followed all of the instructions, and had the ROM working fine. However, I did not like it, and wanted to reset it. I decided to use the LG hidden menu reset, to reset it since it was the easiest. Now when I try to boot, the LG menu pops up, and says "Secure Boot Failed" and then boots into CWM recovery. I tried reseting it and everything i could think of... any ideas on how to fix it?
lol, http://androidforums.com/virgin-mobile-optimus-f3-all-things-root/779320-unbrick-vm-sprint-f3.html
There's other things you can do like install a stock rom in cwm. You can use adb sideload to copy it over. It's up to you how to fix it
Run the Unbrick Guide
I just wanted to give you guys an update on my progress. I know it's been awhile.
I'm finally able to modify the boot.img. For awhile, every time I modified it, it wouldn't work. Even something as simple as decompiling it, and then recompiling it wouldn't allow it to boot.
Turns out it was the software I was using. The Psycho Billy Rom now has a modified boot img. The only thing modified is the splash screen when you first boot. I changed the splash screen as a prof of concept.
I have now merged our stock boot.img with cm boot.img and it boots. The psycho billy stock rom boots, not the full cm rom.
After booting, it rejects the LG SystemUI app as well as other apps now crash. To fix this, I will need to port over the cm framework files. This is great news. It's a partial port over to the cm framework.
Unfortunately every time I port one framework file it won't boot. It will get stuck on the boot animation. Grrr
I just wanted to catch you all up on where i'm at. I'm making progress slowly.
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.