Database Develop

Ginger-Root Resource Thread: How-To + Issues + Fixes

Ok so I have successfully rooted my phone after updating to Gingerbread. However, I had a few issues and had to read through a bunch of different posts to get there. So I'm bored and decided to consolidate everything into one.
If anyone has any other issues or fixes post them here and I will update the OP.
Credit goes to mtmichaelson and all those who helped get this working
http://androidinvasion.us/forum/index.php/topic,77.0.html
Here it is:
1. ROOT PROCESS
A. Get back to Stock:
-download the stock Zv4 ROM zip from here and put it on your external SD card- http://forum.xda-developers.com/showthread.php?t=1326893
-Back up all your apps in titanium (important: USER apps only, no data or system apps)
NOTE: It has been reported that restoring apps and data in titanium may cause some issues coming from Froyo to Gingerbread. I backed up my user apps only for easy re-install and NO data or system apps. It worked without a problem.
-MAKE SURE YOU HAVE 4G ENABLED
-boot into recovery (CWM)
-backup?
-factory reset
-select "install ZIP from SD card" in CWM, and install the stock ZIP from the link
-re-bootyour phone (you will have to re-activate it as well)
-install revo toolkit from here if it was wiped with the system reset - http://forum.xda-developers.com/showthread.php?t=1144951
-press "install recovery" and then !!!Revo Stock!!! to go back to stock recovery and wait for it to complete
B. Update to Zv6 then Zv7 (Gingerbread)
-manually search for the update and install it (this will install the v6 update)
-once that installs, manually search again to install the gingerbread update
NOTE: Some people still can't get gingerbread. Verizon has not finished rolling the update out to everyone yet.
Now here is where it gets a little dicey...
C. Rooting Your Gingerbread Phone
-pick up the rooting package from mtmichaelson here - http://forum.xda-developers.com/showthread.php?t=1326509
-follow the instructions he has on that page to obtain root
-Two issues arose for me from this point on.
2. ISSUES
A. Drivers Issue
-The first issue was that some people, including myself, couldn't download the esteem drivers.
-Some people were able to get the drivers from this page to work - http://androidnerds.net/2011/10/08/lg-esteem-oneclickroot-now-ready/.
-I was not able to get my computer to recognize my phone using the above drivers either. I would run the root command from the downloaded package and it would get stuck at "running daemon something something".
-What I did was manually uninstall the LG drivers from my computer and deleted everything "LG related"
-Then I got the drivers from the LG website at this link - http://www.lgforum.com/resources
-Scroll down to the Verizon section and download the "LG_VZW_UNITED..." drivers.
-Your phone should be recognized using the drivers from one of these links.
B. Superuser/Root access Issue - NOTE: this should be fixed now with mtmichaelson's newest root method found here - http://forum.xda-developers.com/showthread.php?t=1326509
-The second issue that came up was that the previous superuser app I had installed stayed on my phone after the updates, even though I lost root.
-The root command from the LG Esteem page would think I had root, but I actually didn't get root access.
-Apparently this issue came up on the Esteem previously and someone wrote a fix for it here - http://androidforums.com/esteem-all...-w-superuser-3-0-6-binary-3-0-3-download.html. It will uninstall the old superuser and install the new version.
3. INSTALL CWM RECOVERY
-mtmichaelson's new rooting package should automatically install CWM recovery on your phone now.
Old method:
-To get CWM back on your phone it's the same process as before the update. Get the Revo Toolkit from thecubed here and follow the instructions - http://forum.xda-developers.com/showthread.php?t=1144951
-There is sometimes an issue where the recovery does not install correctly and gives a fatal error. If this happened, make sure you have version 1.17.1 of busybox installed at system/bin. This worked for me and I got it installed correctly.
...And you should have root after trying a combination of the above. Hope this helped.
-If you have READ through this and still have any issues you can get more personalized help on the IRC channel here.
-Again I did not help with any of this, I'm just consolidating info. If you want to thank someone, thank mtmichaelson and everyone else who helped figure all this out.
-I will keep updating this as new issues arise.

Thank you for compiling this information, it is a useful reference for people to have. I know that the drivers issue took me quite a while to work out even though it is pretty simple. Hopefully this helps others to get rooted with much less trouble.

Quick question using that stock ROM will it completely unroot me?
Also a bit confused with me running revolt does that mess up me just flashing that and it has the stock boot image.
I've Revolted have you?? Sent via tapatalk plugin.

i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...

xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
Hey guys, I have a new package for root for those having problems. I need testers though. If you can come on irc in about 20 minutes. It has the drivers in it also.
Sent from my VS910 4G using xda premium

xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file

Haro912 said:
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file
Click to expand...
Click to collapse
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.

xjli said:
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.
Click to expand...
Click to collapse
Got it. I guess the first release of revo toolkit didn't have the flash stock recovery option. Can't wait to finally have gb on this thing..

Still reboots to cwm... it won't flash stock recovery. Any ideas?

xjli said:
Still reboots to cwm... it won't flash stock recovery. Any ideas?
Click to expand...
Click to collapse
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium

mtmichaelson said:
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
It doesn't..still says 4.0.0.2... how long should it take to 'install?'

OP updated for the new packages from mtmichaelson

xjli said:
It doesn't..still says 4.0.0.2... how long should it take to 'install?'
Click to expand...
Click to collapse
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.

jrf28 said:
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.
Click to expand...
Click to collapse
Righto. Only slow 3g in my silo of an office :-/ ill let it go for a while.

Just reinstalled busybox... got it!

The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...

borborpa said:
The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...
Click to expand...
Click to collapse
It looks like it's a common problem. I haven't installed the ROM yet but mt's new gingervolt rom is supposed to make CWM stick - http://forum.xda-developers.com/showthread.php?t=1326542

Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?

i_t_n said:
Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?
Click to expand...
Click to collapse
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine

Haro912 said:
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine
Click to expand...
Click to collapse
Awesome, thank you for the quick reply. Another stupid question that i'm sure is answered somewhere on here, but what exactly will I lose when flashing a ROM, and what will I be able to restore back with a backup?

Stuck on bootloader unlocked screen.

Hello,
I yesterday got new at&t Atrix hd with android 4.0.4. I updated to newest 4.1.2 (I think). I rooted it with Motochopper. I tried to install CWM with Myth Tool. Didn't work.
Finally I installed CWM with this method.
Install CWM Recovery by Epinter
Read Epinter's RAZR HD CWM Thread
Download the recovery image
On stock rom, navigate to /system/etc and rename install-recovery.sh to install-recovery.sh.bak
Reboot into fastboot -- use "adb reboot bootloader" from Terminal\Command Prompt
Wipe the existing recovery -- "fastboot erase recovery" !
Flash the recovery with "fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img"
That's it, CWM is installed.
Click to expand...
Click to collapse
Then I installed [ROM] CM 10.2 (Android 4.3) for AtrixHD from zip in CWM. Everything was working great till turned Atrix off.
Then it stuck on "bootloader unlocked" screen. Most of the time I was not able to enter CWM but one time somehow I managed to enter CWM, if I use restart option in CWM after restart android loaded successfully. Tried restart again but I was not able to enter recovery and got stuck again. After messing around with volume/power key somehow android loaded again successfully (without enter recovery).
Now it's working but I'm scared to restart or do anything.
What do you think? What should I do? Is it ROM problem, system or what?
Currently there are no install-recovery.sh (or install-recovery.sh.bak) file. Maybe this could be problem?
I would appreciate any help.
Thanks!

mm166 said:
Hello,
I yesterday got new at&t Atrix hd with android 4.0.4. I updated to newest 4.1.2 (I think). I rooted it with Motochopper. I tried to install CWM with Myth Tool. Didn't work.
Finally I installed CWM with this method.
Then I installed [ROM] CM 10.2 (Android 4.3) for AtrixHD from zip in CWM. Everything was working great till turned Atrix off.
Then it stuck on "bootloader unlocked" screen. Most of the time I was not able to enter CWM but one time somehow I managed to enter CWM, if I use restart option in CWM after restart android loaded successfully. Tried restart again but I was not able to enter recovery and got stuck again. After messing around with volume/power key somehow android loaded again successfully (without enter recovery).
Now it's working but I'm scared to restart or do anything.
What do you think? What should I do? Is it ROM problem, system or what?
Currently there are no install-recovery.sh (or install-recovery.sh.bak) file. Maybe this could be problem?
I would appreciate any help.
Thanks!
Click to expand...
Click to collapse
Are you sure the install-recovery.sh file is not installed? Just to make sure, I would install Root Explore to use that to check to make sure.

I don't have root access but I think I should be able to see that file, right?

Do you have root access? You need to install a file manager like Root Explorer so you can easily change the file permissions and rename the file by adding .bak to the end of the file name.
Weird, I don't see it either. I see it in mine though.

No, I don't have root access. I hope it's ROMs issue. CM10.2 doesn't come with root access. There are weird things going on with my phone. I really hope that other ROM will fix that. Thanks for reply.

mm166 said:
No, I don't have root access. I hope it's ROMs issue. CM10.2 doesn't come with root access. There are weird things going on with my phone. I really hope that other ROM will fix that. Thanks for reply.
Click to expand...
Click to collapse
Maybe you could install Root Explorer. Maybe that will allow you to see the file.

I also have problems getting straight into recovery sometimes but if I hold vol up+vol down+power I can select recovery from there. as far root on cm 10.2 flash superuser.zip

Can you tell me what key combinations you use for what purpose? I doubt you make a mistake there...
Sent from my MB886 using xda app-developers app

Just bumping this one
I am pretty desperete now
RSD'ed to Mexican retail
Rebooted fine but I get N/A in every device property value in RSD
When I flash CM 10.2 (wiping cache/dalvik/factory reset/format system and wiping caches/factory reset after) It boots fine the first time and gets stuck in Moto log/Unlocked bootloader when I reboot
I know I missing something but WTF am I missing?

narta said:
Just bumping this one
I am pretty desperete now
RSD'ed to Mexican retail
Rebooted fine but I get N/A in every device property value in RSD
When I flash CM 10.2 (wiping cache/dalvik/factory reset/format system and wiping caches/factory reset after) It boots fine the first time and gets stuck in Moto log/Unlocked bootloader when I reboot
I know I missing something but WTF am I missing?
Click to expand...
Click to collapse
have you tried PAC 4.3 to see if it gives same issue.

frog1982 said:
have you tried PAC 4.3 to see if it gives same issue.
Click to expand...
Click to collapse
it does

I'm having the same problem. Running CM10.2.

[Q] Can't just replace TWRP with Stock 12b Recovery?

Can someone point me to a thread that explains why someone on rooted stock 12b with TWRP can't simply flash a stock recovery to get the OTA? No one seems to be doing it, or even talking about doing it. Not knowing why is driving me crazy!! Thanks guys

wolf5150 said:
Can someone point me to a thread that explains why someone on rooted stock 12b with TWRP can't simply flash a stock recovery to get the OTA? No one seems to be doing it, or even talking about doing it. Not knowing why is driving me crazy!! Thanks guys
Click to expand...
Click to collapse
Yup can do it as long as nothing else is modified but most people who root modify system,files. I did exactly what you're saying except a little different. I used flashify to back up stock recovery, then I flashed twrp and when kitkat came I restored to suck recovery uninstalled xposed framework and manually installed kitkat. Then I used Autorec to install twrp again and backed up recovery worth flashify first. This time though I forgot to backup the kernel too because Autorec modifies it. So now I'll probably have to kdz to stock uhh f a later update comes unless there's a flashible zip for it.
Sent from my VS980 4G using xda app-developers app

abdel12345 said:
Yup can do it as long as nothing else is modified but most people who root modify system,files. I did exactly what you're saying except a little different. I used flashify to back up stock recovery, then I flashed twrp and when kitkat came I restored to suck recovery uninstalled xposed framework and manually installed kitkat. Then I used Autorec to install twrp again and backed up recovery worth flashify first. This time though I forgot to backup the kernel too because Autorec modifies it. So now I'll probably have to kdz to stock uhh f a later update comes unless there's a flashible zip for it.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Can you post the 12B recovery, I cannot find a copy and want to do this to update with OTA
Thanks
Matt

abdel12345 said:
Yup can do it as long as nothing else is modified but most people who root modify system,files. I did exactly what you're saying except a little different. I used flashify to back up stock recovery, then I flashed twrp and when kitkat came I restored to suck recovery uninstalled xposed framework and manually installed kitkat. Then I used Autorec to install twrp again and backed up recovery worth flashify first. This time though I forgot to backup the kernel too because Autorec modifies it. So now I'll probably have to kdz to stock uhh f a later update comes unless there's a flashible zip for it.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
mzimand said:
Can you post the 12B recovery, I cannot find a copy and want to do this to update with OTA
Thanks
Matt
Click to expand...
Click to collapse
I found a repository here: http://forum.xda-developers.com/showpost.php?p=48794341&postcount=4
When I renamed the 12b version from .bin to .img and flashed with Flashify, it factory reset my phone and even wiped internal storage. So I restored my nandroid (that I'd backed up externally), then flashed the 11a version. That installed on my 12b phone successfully.
The OTA then errors out with 0x1111004.
Upgrade Assistant tries but fails to detect the phone in ethernet mode.
In download mode the phone is detected but PC displays "Authentication fail"
I can't recall doing any mods outside of g2xposed and I've uninstalled the framework but maybe I did?
Was recovery was updated when 12b rolled out?
I'll try to dig up an earlier nandroid of my system partition and see if I can rule out other mods. Ideas welcome, thanks

[Q] Where's my recovery?

So I just recently decided to flash the unbloated OTA offered in the download section. I was on the 12 radio before running a regular ROM with ROM Manager and everything working perfectly. I flashed everything and all went smoothly. I flashed the OTA and the other required .zip. I then tried to root with IOroot25. Well my phone is detected, but when it goes to reboot into recovery, it never really does. So I tried to adb reboot recovery and the same thing happened - not going into recovery, just kinda' sitting at a very dark, though barely lit, screen.
Everything functions fine but it appears I do not have any sort of recovery at all. How would I go about fixing this? Any help would be greatly appreciated.

What debloated ROM did you flash?

BoostinBen said:
So I just recently decided to flash the unbloated OTA offered in the download section. I was on the 12 radio before running a regular ROM with ROM Manager and everything working perfectly. I flashed everything and all went smoothly. I flashed the OTA and the other required .zip. I then tried to root with IOroot25. Well my phone is detected, but when it goes to reboot into recovery, it never really does. So I tried to adb reboot recovery and the same thing happened - not going into recovery, just kinda' sitting at a very dark, though barely lit, screen.
Everything functions fine but it appears I do not have any sort of recovery at all. How would I go about fixing this? Any help would be greatly appreciated.
Click to expand...
Click to collapse
It got removed, you need to downgrade the aboot to install a recovery once you upgrade the firmware to 24A. 24A plugs the exploit that was being used. Easiest route is to use the AutoRec app in the LG G2 Development section.

mjones73 said:
It got removed, you need to downgrade the aboot to install a recovery once you upgrade the firmware to 24A. 24A plugs the exploit that was being used. Easiest route is to use the AutoRec app in the LG G2 Development section.
Click to expand...
Click to collapse
How can I use this program if I can't attain root? It says it requires root, which IOroot25 cannot do due to not having a recovery to boot into to apply the .zip.

I'm going to try the KDZ method here to flash the factory version in its full glory. Hopefully that will restore recovery mode and allow me to root the thing. I'll report back with my findings, and whether or not I was able to do this using the above link, IOroot, and AutoRec.

I am having the same issue. I was running CM11 on a verizon lg g2 with CWM recovery. I flashed prerooted 4.4.2 from MicroMod777 along with the KK baseband. It worked, but I lost root AND recovery. Now when I tried to use ioroot 25, my phone won't boot into recovery at all. It appears that I lost recovery. Is there a simple way to install recovery back?

holsteinmoo said:
I am having the same issue. I was running CM11 on a verizon lg g2 with CWM recovery. I flashed prerooted 4.4.2 from MicroMod777 along with the KK baseband. It worked, but I lost root AND recovery. Now when I tried to use ioroot 25, my phone won't boot into recovery at all. It appears that I lost recovery. Is there a simple way to install recovery back?
Click to expand...
Click to collapse
Return your phone to stock, let it take the OTA then rroot and install recovery.
http://forum.xda-developers.com/showthread.php?t=2448960

mjones73 said:
Return your phone to stock, let it take the OTA then rroot and install recovery.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
Yep...that did it! Thanks!

mjones73 said:
Return your phone to stock, let it take the OTA then rroot and install recovery.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
Running TWRP and am happy with that but would prefer CWM touch recovery. Have tried several methods to install from various XDA treads with no luck. Any info you know of on that?

CWM installed fine for me using their purchased app and just flashing the touch version after selecting my device model.
I have also installed it using .img files provided in the forums and using Flashify to flash them.

BoostinBen said:
CWM installed fine for me using their purchased app and just flashing the touch version after selecting my device model.
I have also installed it using .img files provided in the forums and using Flashify to flash them.
Click to expand...
Click to collapse
I was able to use .img files in the forums with 11a...I never took 12b...just stayed on 11a and ignored the update.
I returned to stock to get to 24a and was able to root but can't for the life of me get CWM recovery installed. I have tried flashify, installing zips, pushing .img with adb...no dice. I get error messages every time or the black screen you described in this thread's original post.
Just tried to load the zip from TWRP...no dice.
I purchased touch through the paid version of CWM and chose my device...nada...it's killing me!
I can live with TWRP but love CWM touch. Really at a loss.
Are you running 24a? If so, can you point me toward the forum link you used to get CWM loaded?

holsteinmoo said:
I was able to use .img files in the forums with 11a...I never took 12b...just stayed on 11a and ignored the update.
I returned to stock to get to 24a and was able to root but can't for the life of me get CWM recovery installed. I have tried flashify, installing zips, pushing .img with adb...no dice. I get error messages every time or the black screen you described in this thread's original post.
Just tried to load the zip from TWRP...no dice.
I purchased touch through the paid version of CWM and chose my device...nada...it's killing me!
I can live with TWRP but love CWM touch. Really at a loss.
Are you running 24a? If so, can you point me toward the forum link you used to get CWM loaded?
Click to expand...
Click to collapse
With 24a I pushed it with adb instead of flashing it via Flashify and it worked decently for me. Personally, though, I do like TWRP more, albeit it doesn't have that convenient application like CWM does.

holsteinmoo said:
I was able to use .img files in the forums with 11a...I never took 12b...just stayed on 11a and ignored the update.
I returned to stock to get to 24a and was able to root but can't for the life of me get CWM recovery installed. I have tried flashify, installing zips, pushing .img with adb...no dice. I get error messages every time or the black screen you described in this thread's original post.
Just tried to load the zip from TWRP...no dice.
I purchased touch through the paid version of CWM and chose my device...nada...it's killing me!
I can live with TWRP but love CWM touch. Really at a loss.
Are you running 24a? If so, can you point me toward the forum link you used to get CWM loaded?
Click to expand...
Click to collapse
So you took the OTA and you're on 24A now? If thats the case you need to push the 12B aboot first before you can flash recovery. AutoRec will do all that. And flash recovery for you. After its finished you can flash CWM touch if you want.
---------- Post added at 01:13 AM ---------- Previous post was at 01:12 AM ----------
BoostinBen said:
With 24a I pushed it with adb instead of flashing it via Flashify and it worked decently for me. Personally, though, I do like TWRP more, albeit it doesn't have that convenient application like CWM does.
Click to expand...
Click to collapse
Have you ever seen this? https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager It flashes recovery for you, you can manage backups, with a donation you can even make live backups while still booted in Android. I haven't tried it yet because I keep forgetting. Sounds so cool though.

Stock Flashable LS995 Sprint Flex Rom

Here is a stock flashable sprint flex rom for those who might ever need it. It can be used for development purposes or if you simply messed up your phone and need it.
steps to install
1. First download Playfulgods app that installs clockwork mod recovery
2. Download the flashable rom located here: https://drive.google.com/file/d/0B6HYWZRx8JLsRHhPVVhvQko3akU/edit?usp=sharing
3. Boot to recovery by turning phone all the way off and holding down vol + and power until you see a black screen with a symbol and korean writing. You will then see cwm recovery start.
4. scroll to advance
5. click the loki toggle. This will stop the recovery from trying to loki the boot.img and causing an error. The boot.img is already lokied thanks to Playfulgod
6. Install the Rom and let it finish
7. reboot the device.

Very nice work,....
Sent from my LG-LS995 using XDA Free mobile app

So if loki is enabled in cwm then the rom dev doesn't need to patch the boot.img? or is because it's the stock boot.img?

I'm on T mo but hellz yea to development congrats n thanks! !!
sentfromybrain

PattyNYC said:
So if loki is enabled in cwm then the rom dev doesn't need to patch the boot.img? or is because it's the stock boot.img?
Click to expand...
Click to collapse
Clock work is having errors with loki at the moment. Therefor Playfulgod made me a lokied stock boot.img for now. So loki is not needed.

Awesome! U r the man. Thx!
Sent from my LG-LS995 using XDA Premium 4 mobile app

Is this 4.2.2 ZV3 or 4.4 ZV6
Sent from my iPad using Tapatalk

jesmann said:
Is this 4.2.2 ZV3 or 4.4 ZV6
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
4.2.2. I am going to try to make a 4.4.2 today
Sent from my LG-LS980 using XDA Premium 4 mobile app

I uploaded the update file the kit Kat discussion thread if that helps
Sent from my LG-LS995 using Tapatalk

Any headway on a 4.4 Rom? Decided I'll wait for a Rom rather than unroot for the update. It's good to see advances are being made! Good work dude.

scarsofapathy said:
Any headway on a 4.4 Rom? Decided I'll wait for a Rom rather than unroot for the update. It's good to see advances are being made! Good work dude.
Click to expand...
Click to collapse
If your on sprint variant you can update to kitkat and root it with IOroot25 that's what i did. I'm also waiting for roms but not 4.2.2 roms im waiting for kitkat roms i don't see the point to be hype for JB roms when kitkat is out and as long as you can root kitkat that should be fine to hold you off until roms start popping out.
Sent from my LG-LS995 using Tapatalk

yellowman82 said:
If your on sprint variant you can update to kitkat and root it with IOroot25 that's what i did. I'm also waiting for roms but not 4.2.2 roms im waiting for kitkat roms i don't see the point to be hype for JB roms when kitkat is out and as long as you can root kitkat that should be fine to hold you off until roms start popping out.
Sent from my LG-LS995 using Tapatalk
Click to expand...
Click to collapse
need recovery to work on kk first b4 you can have roms.

So if I flash this stock Rom will my phone accept the kk update or do I still need to unroot? I read something about needing to unroot but also read you can flash a stock Rom? Confused about the best way to take the kk update. I've just seen some people saying it's best to wait for a kk Rom and others say go ahead and update then root haha

No won't update with custom recovery
Sent from my LG-LS980 using XDA Premium 4 mobile app

justinswidebody said:
Here is a stock flashable sprint flex rom for those who might ever need it. It can be used for development purposes or if you simply messed up your phone and need it.
steps to install
1. First download Playfulgods app that installs clockwork mod recovery
2. Download the flashable rom located here: https://drive.google.com/file/d/0B6HYWZRx8JLsRHhPVVhvQko3akU/edit?usp=sharing
3. Boot to recovery by turning phone all the way off and holding down vol + and power until you see a black screen with a symbol and korean writing. You will then see cwm recovery start.
4. scroll to advance
5. click the loki toggle. This will stop the recovery from trying to loki the boot.img and causing an error. The boot.img is already lokied thanks to Playfulgod
6. Install the Rom and let it finish
7. reboot the device.
Click to expand...
Click to collapse
I desperately need this and the link doesn't work, ..I need to fastboot flash all these files because this phone won't respond to charging and the screen doesn't show anything, yet it willl take fastboot flashes...it's strange..even "fastboot devices" returns a "? fastboot" instead of showing the device #

adb
justinswidebody said:
Here is a stock flashable sprint flex rom for those who might ever need it. It can be used for development purposes or if you simply messed up your phone and need it.
steps to install
1. First download Playfulgods app that installs clockwork mod recovery
2. Download the flashable rom located here: https://drive.google.com/file/d/0B6HYWZRx8JLsRHhPVVhvQko3akU/edit?usp=sharing
3. Boot to recovery by turning phone all the way off and holding down vol + and power until you see a black screen with a symbol and korean writing. You will then see cwm recovery start.
4. scroll to advance
5. click the loki toggle. This will stop the recovery from trying to loki the boot.img and causing an error. The boot.img is already lokied thanks to Playfulgod
6. Install the Rom and let it finish
7. reboot the device.
Click to expand...
Click to collapse
Was finally able to download the zip file, is there anyway to get it on my device from Recovery? My Device is stuck in a boot loop but I can get the phone into recovery mode, but I believe the CWM on my device isn't working 100%, I can back up and restore if that helps, but when I restart the system, I get nothing but the LG Boot Logo.
Tried adb sideload, "device not found"
UPDATE: Somehow got sideload to cooperate but keep getting * failed to write data 'protocol fault <no status>' * get this at about 55-60%
Sideload gets to exactly 59% every time, then fails. Can I not sideload this Stock ROM?

justinswidebody said:
Here is a stock flashable sprint flex rom for those who might ever need it. It can be used for development purposes or if you simply messed up your phone and need it.
steps to install
1. First download Playfulgods app that installs clockwork mod recovery
2. Download the flashable rom located here: https://drive.google.com/file/d/0B6HYWZRx8JLsRHhPVVhvQko3akU/edit?usp=sharing
3. Boot to recovery by turning phone all the way off and holding down vol + and power until you see a black screen with a symbol and korean writing. You will then see cwm recovery start.
4. scroll to advance
5. click the loki toggle. This will stop the recovery from trying to loki the boot.img and causing an error. The boot.img is already lokied thanks to Playfulgod
6. Install the Rom and let it finish
7. reboot the device.
Click to expand...
Click to collapse
Were you ever able to make a kit Kat zip I have someone who will they also were looking for the about and stock kit Kat recovery for ls995
---------- Post added at 02:26 PM ---------- Previous post was at 02:21 PM ----------
rekamyenom said:
adb
Was finally able to download the zip file, is there anyway to get it on my device from Recovery? My Device is stuck in a boot loop but I can get the phone into recovery mode, but I believe the CWM on my device isn't working 100%, I can back up and restore if that helps, but when I restart the system, I get nothing but the LG Boot Logo.
Tried adb sideload, "device not found"
UPDATE: Somehow got sideload to cooperate but keep getting * failed to write data 'protocol fault <no status>' * get this at about 55-60%
Sideload gets to exactly 59% every time, then fails. Can I not sideload this Stock ROM?
Click to expand...
Click to collapse
This same thing is happening to me I'm on kit Kat but like an idiot installed twrp and now I only have twrp dlmode and I can ADB push ADB sideload reads but I get that same protocol thing annoying

Hi
The ROM link is no longer available.
Could anyone offer a another link!

justinswidebody said:
Here is a stock flashable sprint flex rom for those who might ever need it. It can be used for development purposes or if you simply messed up your phone and need it.
steps to install
1. First download Playfulgods app that installs clockwork mod recovery
2. Download the flashable rom located here: [B]https://drive.google.com/file/d/0B6HYWZRx8JLsRHhPVVhvQko3akU/edit?usp=sharing[/B]
3. Boot to recovery by turning phone all the way off and holding down vol + and power until you see a black screen with a symbol and korean writing. You will then see cwm recovery start.
4. scroll to advance
5. click the loki toggle. This will stop the recovery from trying to loki the boot.img and causing an error. The boot.img is already lokied thanks to Playfulgod
6. Install the Rom and let it finish
7. reboot the device.
Click to expand...
Click to collapse
link not working

Don't mean to perpetuate the broken record but. Link isn't orking. I need this very very badly.Stuck in boot loop without backup. Thanks