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?

ClockworkMod Recovery Images Available for Verizon LG G2

I have created Loki-enabled images for ClockworkMod Recovery and Touch Recovery.
Links to the images:
http://www.androidfilehost.com/?a=show&w=files&flid=8961
recovery-clockwork-6.0.4.4-vs980.lok
http://www.androidfilehost.com/?fid=23196940996968932
recovery-clockwork-6.0.4.4-vs980.lok.img
http://www.androidfilehost.com/?fid=23196940996968933
recovery-clockwork-touch-6.0.4.4-vs980.lok
http://www.androidfilehost.com/?fid=23196940996968931
recovery-clockwork-touch-6.0.4.4-vs980.lok.img
http://www.androidfilehost.com/?fid=23196940996968934
There is one set of images for CWM recovery and one for CWM Touch recovery. The loki images were created from the CWM images on clockworkmod.com using loki_flash.
Files ending in *.lok.img are identical (binary-same) to the corresponding *.lok files. Use these if using Flashify, since it doesn't allow flashing of files ending in *.lok. Or, just rename the *.lok files to *.img. Your choice.
These images should be flashed using the loki_flash method detailed here (use option 1):
http://forum.xda-developers.com/showthread.php?t=2449670
Just replace the name of the file specified in those instructions with the *.lok file you downloaded from the link above.
Or, as stated above, you can use Flashify.
Don't try to set up a custom CWM (or TWRP) recovery image from within CWM ROM Manager - you will end up with a non-working recovery mode. This is how I stumbled upon this issue and why I created the above loki images. If you are in a broken recovery state, just use the above images to get back to a working recovery state.
*** THESE IMAGES ARE ONLY VALID FOR THE VERIZON LG G2 VARIANT [vs980]! DON'T FLASH THEM ON ANY OTHER DEVICES ***

How is the cache wipe on this? Does it takee a long time (5-10 min) like TWRP? Thanks for the development

BriVG said:
How is the cache wipe on this? Does it takee a long time (5-10 min) like TWRP? Thanks for the development
Click to expand...
Click to collapse
There are instructions on how to make twrp do wipes faster in the 3rd post of the Cleanrom thread. It wipes everything in only a few seconds. Been using this method for a couple of weeks with no problems.

Cache wipe took 13 minutes... Just cache
Sent from my VS980 4G using Tapatalk

Originally Posted by BriVG
How is the cache wipe on this? Does it takee a long time (5-10 min) like TWRP? Thanks for the development
Click to expand...
Click to collapse
There are instructions on how to make twrp do wipes faster in the 3rd post of the Cleanrom thread. It wipes everything in only a few seconds. Been using this method for a couple of weeks with no problems.
Click to expand...
Click to collapse
Not sure this answered his question.
Thanks Devs. From my VZW G2.

trickster2369 said:
Not sure this answered his question.
Thanks Devs. From my VZW G2.
Click to expand...
Click to collapse
Just curoius is CWM has any benefits or downsides compared to TWRP?
Thank you

Evilmonstertruck said:
Just curoius is CWM has any benefits or downsides compared to TWRP?
Thank you
Click to expand...
Click to collapse
I havent run CWM yet on my g2 but thats all I ran in the past and it's really just personal preference. TWRP does have a bit more options and features and can be themed whereas CWM is pretty simple and plain. I think I like CWM a bit more though just because the layout is a bit nicer imo.

Evilmonstertruck said:
Just curoius is CWM has any benefits or downsides compared to TWRP?
Thank you
Click to expand...
Click to collapse
I've never used CWM touch, so I can't speak to that. I used CWM on my Incredible and Rezound, and they do the same things. The first time I used TWRP was on my Nexus 10, because CWM wasn't available as an option. Probably the biggest difference is the UI. TWRP can be themed also. Kind of like getting a new pair of shoes. The old ones are worn in and comfortable, and your used to them. The new ones look nice and clean, and work pretty much the same, but eventually grow on you. That's where I am with TWRP.
Thanks Devs. From my VZW G2.

I was curious about the wipe because I've heard that the - rm option was not wiping sufficiently for some people...

Just installed it and ran a backup. Seems to backup quicker than TWRP.
:good:

Because i'm not lazy
Here's the TWRP tip for faster wipes.
The Fix

locoface said:
Because i'm not lazy
Here's the TWRP tip for faster wipes.
The Fix
Click to expand...
Click to collapse
Yeah it's very fast but I've read in other posts of different forums that some people reported that this method left artifacts that possibly messed with subsequent flashes

any direct instructions for us noobs to adb on how to do this from just root with stock recovery?

HOWTO:install custom recovery with root and stock recovery
1) Download and install LG G2 Windows USB Driver, if you haven't already.
2) Download and install Flashify from the Google Play Store.
3) Download CWM Recovery or CWM Touch Recovery image file (*.img, not *.lok files). Either one - your choice.
4) Connect your phone to your PC via USB using Media sync (MTP) option.
5) Copy the appropriate *.img file, downloaded in step 3, to a location on your phone's SD card
6) Using Flashify, select Flash -> Recovery Image, and browse to the location on your phone's SD card where you copied the *.img file in step 5.
7) Select the file, and choose "Yup!"
Enjoy CWM Recovery goodness.
Viper76269 said:
any direct instructions for us noobs to adb on how to do this from just root with stock recovery?
Click to expand...
Click to collapse

kaczmar2 said:
1) Download and install LG G2 Windows USB Driver, if you haven't already.
2) Download and install Flashify from the Google Play Store.
3) Download CWM Recovery or CWM Touch Recovery image file (*.img, not *.lok files). Either one - your choice.
4) Connect your phone to your PC via USB using Media sync (MTP) option.
5) Copy the appropriate *.img file, downloaded in step 3, to a location on your phone's SD card
6) Using Flashify, select Flash -> Recovery Image, and browse to the location on your phone's SD card where you copied the *.img file in step 5.
7) Select the file, and choose "Yup!"
Enjoy CWM Recovery goodness.
Click to expand...
Click to collapse
Can't we just install CWM from Rom manager?

Unless the image available from within ROM manager has been updated, NO. You will end up with a broken recovery image. That is why I made the images above. I did this exact thing myself and that is how I found the issue and made these images.
The images on clockworkmod.com and in ROM manager didn't work for me until I created Loki versions.
However, you are welcome to try to see what results you get. If you boot into recovery and get an error, you can just flashify the images above to get back a working recovery.
Sent from my VS980 4G using Tapatalk

kaczmar2 said:
Unless the image available from within ROM manager has been updated, NO. You will end up with a broken recovery image. That is why I made the images above. I did this exact thing myself and that is how I found the issue and made these images.
The images on clockworkmod.com and in ROM manager didn't work for me until I created Loki versions.
However, you are welcome to try to see what results you get. If you boot into recovery and get an error, you can just flashify the images above to get back a working recovery.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Oh ok, i went ahead and did yours instead of Rom Manger before your reply anyway lol, works great. One big question though. what the heck is Loki in the phone world? I spent 2 years with galaxy nexus, rooting, zipping etc etc and never stumbled upon Loki stuff.

litobirdy said:
Oh ok, i went ahead and did yours instead of Rom Manger before your reply anyway lol, works great. One big question though. what the heck is Loki in the phone world? I spent 2 years with galaxy nexus, rooting, zipping etc etc and never stumbled upon Loki stuff.
Click to expand...
Click to collapse
same here, but to my understanding, Loki is a way to bypass the bootloader, or tricking the phone to thinking the bootloader is unlocked.
---------- Post added at 11:10 PM ---------- Previous post was at 10:42 PM ----------
i was looking for my buddy's phone on AT&T, and it says you have to be on TWRP in order to install there. is that the same for this? or can i use flashify and flash CWM while i have a stock recovery?

The LG G2 (and other devices, like the Samsung Galaxy S4) on Verizon and AT&T used locked bootloaders. These same devices on other carriers (T-Mobile, etc.) include an unlocked bootloader, which allows users to flash custom kernels and make other modifications to the software on their own devices, AT&T and Verizon branded devices ship with a locked bootloader that prevents these types of modifications.
Loki is effectively an exploit that fools the locked bootloader into loading an unsigned, modified (loki-fied) image. You can read more about how it works here and here, if you wish.
You can use Flashify and and flash CWM while you have a stock recovery if you use the images I posted and follow the instructions in a post above. My understanding is that the AT&T variant of the G2 has a locked bootloader, so these same instructions would apply to that device, I would assume. If you want to use TWRP instead of CWM, there is a Loki-enabled image of that floating around the XDA forums; you can use Flashify and flash TWRP if you wish.
Viper76269 said:
same here, but to my understanding, Loki is a way to bypass the bootloader, or tricking the phone to thinking the bootloader is unlocked.
---------- Post added at 11:10 PM ---------- Previous post was at 10:42 PM ----------
i was looking for my buddy's phone on AT&T, and it says you have to be on TWRP in order to install there. is that the same for this? or can i use flashify and flash CWM while i have a stock recovery?
Click to expand...
Click to collapse

anyone get a white screen asking you for a code to put in after hitting reboot system from CWM recovery? i just shut the phone off and back on and it was ok, but i'm just wondering if it was a fluke

[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

Root, Backup & ROM Verizon LG G2 on 4.4.2???

I can't seem to find a process for backing up my current "stock" setup, then rooting it and installing TWRP and ROM's.
I had a G2 previous to it getting kitkat and had done all of this with that, fairly easily too...but can't seem to find the same process to do it after the kitkat update (4.4.2)...?
Any help would be greatly appreciated.

sdgmcdon said:
I can't seem to find a process for backing up my current "stock" setup, then rooting it and installing TWRP and ROM's.
I had a G2 previous to it getting kitkat and had done all of this with that, fairly easily too...but can't seem to find the same process to do it after the kitkat update (4.4.2)...?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You need to root it (using ioroot), install a recovery (using autorec) then you can back it up.

mjones73 said:
You need to root it (using ioroot), install a recovery (using autorec) then you can back it up.
Click to expand...
Click to collapse
This worked to get twrp on it thanks! ks (i was able to eventually get it rooted using ioroot and did a nandroid backup), i am however not able to flash a new rom (using cm's latest nightly for the vs980 now...going to try the snapshot next, but the nightly just fails almost immediately and i did have twrp fix permissions????
thanks again!
EDIT: And crap, stuck in a boot loop...said it flashed the snapshot ok, almost immediately, rebooted and boot loop.

mjones73 said:
You need to root it (using ioroot), install a recovery (using autorec) then you can back it up.
Click to expand...
Click to collapse
It's official, I'm bricked...lg logo boot loop, nothing else. Somehow in the process my nandroid and twrp backups no longer show up in twrp either (have to do the factory reset (hold down vol down and power twice, then power twice to confirm reset)...I've looked in the backup folders using twrp file manager and the folders have lots of stuff in them (not sure if it's correct stuff though?) and the folders are named as I named them when I did the backups...also, most other data seems to be on the phone and only 13gb's free according to twrp, so has to be a "system" there, but just get boot loop...
I've since read that the cm builds dont work on 24a kk 4.4.2 vs980; results in boot loops, but I can't get adb to work either so I can't even download a different rom to get it going...
I'm stuck...way stuck....

sdgmcdon said:
This worked to get twrp on it thanks! ks (i was able to eventually get it rooted using ioroot and did a nandroid backup), i am however not able to flash a new rom (using cm's latest nightly for the vs980 now...going to try the snapshot next, but the nightly just fails almost immediately and i did have twrp fix permissions????
thanks again!
EDIT: And crap, stuck in a boot loop...said it flashed the snapshot ok, almost immediately, rebooted and boot loop.
Click to expand...
Click to collapse
Did you use jackpotcalvin's cm11? If not then you're in a bootloop because the official cm11 for our phone users 4.2.2 kernel base, whereas jpc's uses kk kernel.
Can you get into download mode? If so, return to stock using kdz or tot method (I've used tot, fairly easy).
Sent from my VS980 4G using XDA Premium 4 mobile app

ADB Sideload may work for you.
http://teamw.in/ADBSideload
Boot into TWRP, Advanced, ADB Sideload.

[ODIN][TAR] 5.1 I9505GUEUDOH2 Full Restore

OH2 is released.
NOTE: This image is *NOT* rooted! If you need root, see here.
WARNING: Stop asking if you can flash this on other phones. You can NOT. It is meant for the I9505G ONLY. This is NOT a "rom". This is a system image for the I9505G. Flashing to any other phone will brick it.
Kernel Source:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-I9505G
OTA zip (must be sideloaded in stock recovery):
https://android.googleapis.com/pack...I9505G_XAR_UDNL3_to_UDOH2_Update_FWD_USER.zip Thanks @dmapr
ODIN FULL RECOVER IMAGE (root is NOT built in):
Shamelessly stealing @MJHawaii instructions from this thread (THANK YOU):
http://forum.xda-developers.com/showthread.php?t=2398217
(DISCLAIMER) Please read and follow the instructions carefully. I nor anyone else on this forum is responsible if you brick your phone, lose your job, or life as you know it ends. Make sure you fully Understand what you're doing before you do it. Modifying any phone comes with a risk.
INSTRUCTIONS:
WARNING: Please do not flash this if you're low on battery...go charge your phone!
o) Download the I9505GUEUDxxx_FULL.tar.md5.gz package from below
o) Make sure you have the USB Drivers installed and you have Odin 3.09 from below
o) Put your phone in download mode and connect it to USB:
-Disconnect the phone from USB
-Power OFF your phone
-Hold Volume Down, Home, and Power
-When the "WARNING!!!" screen comes up, release the buttons
-Volume up to enter download mode
-Connect the phone to USB
o) Open Odin
o) Click on AP, then select the I9505GUEUDxxx_FULL.tar.md5.gz package you downloaded
o) Odin will extract the tar md5 file from the gzip archive, and this will take a while...be patient
o) Once the tar md5 is loaded, make sure you have a COM PORT in Odin ( any )
o) Click Start and wait till it finishes flashing...your phone should reboot when it's done
NOTE: If your phone does not boot, then boot into stock recovery and Wipe Data Factory Reset.
DOWNLOADS:
ODIN 3.09
I9505GUEUDOH2_FULL
A GIANT thank you to @MJHawaii for helping me learn this process!!!

I used your Odin restore today on my GS4 GPE and it worked great. Thanks!

Great. Glad it worked for you!

Just a kind of off-topic question guys, is camera working fine on the real GPE S4 with this update?
It doesn't work at all on the international S4, some people are trying to figure it out but so far... nothing...
Is it working fine on your phones?

-Ric- said:
Just a kind of off-topic question guys, is camera working fine on the real GPE S4 with this update?
It doesn't work at all on the international S4, some people are trying to figure it out but so far... nothing...
Is it working fine on your phones?
Click to expand...
Click to collapse
Posted on the GPE Stock ROMs thread too.

I replied in the rom thread a few days ago stating that, yes, it's working on the GPE just fine.

SamuriHL said:
I replied in the rom thread a few days ago stating that, yes, it's working on the GPE just fine.
Click to expand...
Click to collapse
if its ok with you (and if i get camera working)
Edit: Camera Is Working on I9505
would you mind if i posted it in S4 (int) forum (because i use your share here restore OS tar file as base) though i only use system file
Regards

LastStandingDroid said:
if its ok with you (and if i get camera working)
Edit: Camera Is Working on I9505
would you mind if i posted it in S4 (int) forum (because i use your share here restore OS tar file as base) though i only use system file
Regards
Click to expand...
Click to collapse
Many people use the ODIN images I create for the basis of roms for other S4 variants. I've no issue with that.

SamuriHL said:
Many people use the ODIN images I create for the basis of roms for other S4 variants. I've no issue with that.
Click to expand...
Click to collapse
Well I always ask since I got a closed thread for "kang" someone's work [emoji14]
Sent from my MotoE2(4G-LTE) using Tapatalk

LastStandingDroid said:
Well I always ask since I got a closed thread for "kang" someone's work [emoji14]
Sent from my MotoE2(4G-LTE) using Tapatalk
Click to expand...
Click to collapse
It never hurts to ask and I fully appreciate it. So no issues there.

Hi, thanks for your continued effort with these files. I am stuck in a weird place and could use some advice.
When I updated from 4.4.4 to 5.0, I sideloaded the OTA in stock recovery, and it worked great. I just tried to do the same thing with 5.0 to 5.1, and am running into a weird issue. First, I tried to sideload the OTA from a CWM recovery that I booted into (but did not flash). I am not sure if this was a mistake, but the sideload failed because of a mismatch with device jgedlte. Which made no sense, because my device is indeed that device. I realized I probably should have done the sideload in stock recovery. So I tried to boot into stock recovery, and it's like it's not even there anymore. I got into a screen which I'd never seen before (which I now believe it the Odin screen) saying "downloading do not turn off target" and in the upper left "could not do normal boot." I have multiple ways of getting into recovery (keypress sequence at power on, adb reboot, bootloader selection, etc) and all of them take me into this weird Odin screen, and once I get there, any reboot cycle takes me back there, UNLESS I actually try to enter Odin (something I'd never done before), and then I can "cancel" out of "downloading a custom OS" and reboot device as normal.
Any ideas what's going on? Seems like my stock bootloader might be screwed up somehow? Which would be weird since I never did anything to it...

The111 said:
Hi, thanks for your continued effort with these files. I am stuck in a weird place and could use some advice.
When I updated from 4.4.4 to 5.0, I sideloaded the OTA in stock recovery, and it worked great. I just tried to do the same thing with 5.0 to 5.1, and am running into a weird issue. First, I tried to sideload the OTA from a CWM recovery that I booted into (but did not flash). I am not sure if this was a mistake, but the sideload failed because of a mismatch with device jgedlte. Which made no sense, because my device is indeed that device. I realized I probably should have done the sideload in stock recovery. So I tried to boot into stock recovery, and it's like it's not even there anymore. I got into a screen which I'd never seen before (which I now believe it the Odin screen) saying "downloading do not turn off target" and in the upper left "could not do normal boot." I have multiple ways of getting into recovery (keypress sequence at power on, adb reboot, bootloader selection, etc) and all of them take me into this weird Odin screen, and once I get there, any reboot cycle takes me back there, UNLESS I actually try to enter Odin (something I'd never done before), and then I can "cancel" out of "downloading a custom OS" and reboot device as normal.
Any ideas what's going on? Seems like my stock bootloader might be screwed up somehow? Which would be weird since I never did anything to it...
Click to expand...
Click to collapse
You need stock recovery to flash the OTA. Consider to flash it in order to use The update.
Boot into 5.0 let it download the ota.
Then flash the update and h must have stock recovery installer
Sent from my GT-I9505G using Tapatalk

LastStandingDroid said:
You need stock recovery to flash the OTA. Consider to flash it in order to use The update.
Click to expand...
Click to collapse
As far as I know, I should already have stock recovery. I've never installed another one. But even weirder is that trying to enter recovery takes me into Odin. Is that expected under any circumstances? Just trying to make sense of where I am now before I do anything else. If I need to re-flash stock recovery then I will do that, but first I'm curious why I go into Odin when trying to enter recovery, that's never happened in the past on any device.

Never flash an ota with custom recovery. It clearly corrupted your device which is not good. At this point I'd seriously use the odin image and upgrade.

SamuriHL said:
Never flash an ota with custom recovery. It clearly corrupted your device which is not good. At this point I'd seriously use the odin image and upgrade.
Click to expand...
Click to collapse
Yeah, my bad there for sure. Sorry for another newbie question, but will complete Odin restore flash wipe my data? I've rooted a dozen devices and done lots of flashing, but I've never touched Odin before so I don't know.
I want to keep my data so I'm tempted to just flash the stock recovery in Odin, and then sideload OTA again (in correct recovery this time), but I also don't want to risk borking my device further than it is...
Thanks for the info!

The111 said:
Yeah, my bad there for sure. Sorry for another newbie question, but will complete Odin restore flash wipe my data? I've rooted a dozen devices and done lots of flashing, but I've never touched Odin before so I don't know.
I want to keep my data so I'm tempted to just flash the stock recovery in Odin, and then sideload OTA again (in correct recovery this time), but I also don't want to risk borking my device further than it is...
Thanks for the info!
Click to expand...
Click to collapse
This ODIN image keeps data. Not all do, but, this one was designed to not erase data.

SamuriHL said:
This ODIN image keeps data. Not all do, but, this one was designed to not erase data.
Click to expand...
Click to collapse
Thanks for explaining that. I went ahead and just flashed the NL3 stock recovery in Odin (thanks again to you for posting that in the other thread) and after that was able to sideload the OTA properly. Need to remember: stock recovery for sideloading OTA's, and custom for sideloading root.

I don't even flash recovery for sideloading root. I have a program that boots cwm without flashing and then waits for you to put it in sideload mode so it can flash supersu zip.

SamuriHL said:
I don't even flash recovery for sideloading root. I have a program that boots cwm without flashing and then waits for you to put it in sideload mode so it can flash supersu zip.
Click to expand...
Click to collapse
Same here. I never flash a custom recovery on any of my devices. A simple fastboot boot custom-recovery.img will load a custom recovery without flashing it. Which is why it was so weird that I managed to get my recovery borked up somehow when trying to sideload OTA from a custom (but not flashed) recovery. I'm not surprised the OTA failed, but I am surprised my recovery got hosed.

The111 said:
Same here. I never flash a custom recovery on any of my devices. A simple fastboot boot custom-recovery.img will load a custom recovery without flashing it. Which is why it was so weird that I managed to get my recovery borked up somehow when trying to sideload OTA from a custom (but not flashed) recovery. I'm not surprised the OTA failed, but I am surprised my recovery got hosed.
Click to expand...
Click to collapse
I'm not surprised. While some people have had success flashing ota from custom recovery, it's almost always a very bad idea and usual something gets corrupt or goes wrong. But hey, that's why we have these odin images. Lol