Related
Hello everyone. It's me again now this time I bring you root access to the new OTA KITKAT for our S4
Disclaimer : I'm not responsible if your phone suddenly dies, explodes or your cat catches fire. Be warned.
SOME PEOPLE REPORT MOBILE DATA NOT WORKING AFTER THIS PROCESS SO ALL YOU GOTTA DO IS GO INTO YOUR APN SETTINGS MENU AND DO RESET TO DEFAULT SETTINGS AND WRITE YOUR CARRIERS APN SETTINGS AND IT WILL WORK.
This process has a lot of steps but if you follow them correctly you will end up with stock rooted 4.4.2 kitkat with super user and safestrap
Requirements:
If you already took the update and your system version is 4.4.2 keep reading.
1. Patience
2. Pwned Kitkat OTA Update link
3. Pwnedkernel for 4.3 Download
4. System image from stock 4.3 Tar file Download
5. Safestrap for the Galaxy S4 Active Download
6. Stock 4.4 Kitkat Kernel Download
7. Chainfire's SuperSu.zip Download
First after you finish downloading the stock 4.3 image extract it somewhere you remember and you'll see the following files:
BL_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar
AP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar
CSC_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar
CP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar
Put your phone in download mode and fire up odin. Under PDA select and flash
AP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar
This will downgrade your system back to 4.3 because yes the new kitkat bootloader allows you to flash 4.3 signed firmware. Note: YOU CANNOT DOWNGRADE BOOTLOADER SO DONT ATTEMPT IT
Wait until odin finishes flashing the firmware and when the phone reboots itself put it again in download mode. Now you must flash pwnedkernel.tar.md5 selecting PDA again in ODIN and wait for phone to boot up. If your phone gets stuck in the ATT logo then perform a factory reset .
Once your phone boots up enable USB debugging mode and root it using saferoot or vroot. GOOGLE it and you'll find it...Then you must install safestrap.apk
adb install safestrapactive.apk
Click to expand...
Click to collapse
Now copy pwnedkitkat.zip and update-Supersu.zip to your SD Card and once that's finished open up safestrap in your device and tap install when that's done tap reboot to recovery.
Now you'll be at the safestrap recovery screen so go ahead and select install zip file.
IMPORTANT : DO NOT DELETE DATA/CACHE OR DO A FACTORY RESET BEFORE FLASHING THE KITKAT.ZIP OTHERWISE YOU'LL HAVE TO START ALL OVER AGAIN.
Install pwnedkitkat.zip and once it finishes go ahead and install update-supersu.zip to enable root access.
AND FINALLY VERY IMPORTANT YOU MUST FLASH THE 4.4.2 STOCK KERNEL IMAGE USING ODIN AND SELECTING PDA OTHERWISE YOUR PHONE WONT BOOT
Wait for your phone to reboot, open up superuser and disable knox security.
Enjoy your rooted 4.4.2 S4 Active.
Credits : hashcode for making safestrap possible and the other amazing developers at XDA that discovered these exploits in the past and special thanks to Samsung for "letting" open these loopholes
If you are in official 4.3 ML2 see my next post.
Sunderwear said:
Hello everyone. It's me again now this time I bring you root access to the new OTA KITKAT for our S4
Uploading files at the moment....keep in mind that this is not a one click solution and we gonna have to exploit the loooholes courtesy of samsung to get this working..
For now some screenshots..
Click to expand...
Click to collapse
Thank you!
Can't wait. When is the ETA? estimate, 10 minutes?
I just can't wait transforming my S4 to S5!
Edit: 40 minutes passed
Now it is probably close to me. I can feel it!
THANK YOOOOOOU!!!!!!!!!!!!!!!!!!!!!!
If you're currently running 4.3 ML2 official update and you want to upgrade to 4.4.2 but dont want to lose root then keep reading.
In the following steps I'm assuming that you're currently running stock 4.3 Rooted ...see my other guide...and that you didn't modify any system apps otherwise the update will fail and you'll have to restore using the Odin package for 4.3.
1. Download pwnedkitkat.zip from 1st post.
2. If you dont have safetrap installed then you must download it and install it.
3. Copy pwnedkitat.zip and update-superuser.zip to your sdcard
4. Restart your phone in safestrap recovery and install pwnedkitkat.zip and when it's done flashing install superuser.zip.
WARNING : DO NOT PERFORM A FACTORY RESET BEFORE FLASHING THE ZIP. THIS IS A MODIFIED OFFICIAL UPDATE SO ONLY SYSTEM FILES WILL BE UPDATED. YOUR DATA WILL BE UNTOUCHED.
5.Put your phone in download mode and flash the 4.4.2 stock boot.tar.md5 kernel and your phone will boot after a few minutes with root access enabled.
Enjoy.
Deleted. As I managed to do it.
TransformixS4 said:
Thank you!
Can't wait. When is the ETA? estimate, 10 minutes?
I just can't wait transforming my S4 to S5!
Edit: 40 minutes passed
Now it is probably close to me. I can feel it!
THANK YOOOOOOU!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Done writing a quick messy guide. If you have any questions let me know. Enjoy:laugh:
need to delete all again , But you save us again !
Thank you !!
I took the ATT 4.4 ota. Can I still perform this method? You discussed the 4.3 to 4.4 method but not from 4.4 to 4.4 rooted. Thank you!
Sent from my SAMSUNG-SGH-I537 using Tapatalk
EDIT: I reread your post and it looks like the instructions are assuming you took 4.4 already. Correct me if I'm wrong. Thank you.
Followed procedure from root ML2, and now the screen is just at the boot animation with blue led for about 5 minutes now, i messed up, need the 4.4.2 odin files
help
--------------------------------------------------------------------------------
hey I tried doing your root method after updating to 4.4.2 and after I flash the pwned file with odin everything goes fine but my usb debugging will not com up at all so I cant even root and im stuck with android version 4.3 but my baseband version is i537ucucn9 and that's 4.4.2 and nothing works no wifi no data no calls no nothing could you help or point me to anything cause I cant even use my phone. Thanks
Xanthos58 said:
Followed procedure from root ML2, and now the screen is just at the boot animation with blue led for about 5 minutes now, i messed up, need the 4.4.2 odin files
Click to expand...
Click to collapse
Same, need 4.4.2 odin files
primeboss said:
Same, need 4.4.2 odin files
Click to expand...
Click to collapse
Ok i got out of this state, you need the ML2 cp and csc files and the original kernel for ML2 flash them and youll be good
You guys should try flashing the 4.3 Odin package and starting from there. I know I have a lot of modified system apps, so I'm likely going to re flash 4.3 just to make sure I'm stock. Thanks again sunderwear!! Good luck rooting everyone. I'll post back with an update in a bit!!
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Xanthos58 said:
Followed procedure from root ML2, and now the screen is just at the boot animation with blue led for about 5 minutes now, i messed up, need the 4.4.2 odin files
Click to expand...
Click to collapse
primeboss said:
Same, need 4.4.2 odin files
Click to expand...
Click to collapse
You guys dont need to , just go to recovery and Factory Rest thats all , its happens to me too
what about us 4.2.2 stock rooted users?
I'm sure most S4 Active owners are still on 4.2.2 rooted. What is the best procedure for us?
Should i unroot my phone via SuperSU then accept the stock 4.4.2 OTA update, then follow the method in the OP?
Or can i leave it rooted and flash stock 4.4.2 via Odin and then follow the OP?
akjimbo said:
I'm sure most S4 Active owners are still on 4.2.2 rooted. What is the best procedure for us?
Should i unroot my phone via SuperSU then accept the stock 4.4.2 OTA update, then follow the method in the OP?
Or can i leave it rooted and flash stock 4.4.2 via Odin and then follow the OP?
Click to expand...
Click to collapse
I was in a similar position with being rooted on 4.3 ML2 (Sunderwear's method). I unrooted thru SuperSU, unfroze everything under TiBU, unchecked every module under xposed framework, reboot phone then proceeded to uninstall all my root apps. I then did a factory reset, then I flashed back to the stock 4.3 under ODIN and following that I took the 4.4.2 OTA successfully.
In the end it's up to you, but IMHO I consider it wise to begin anew with a fresh clean phone.
Yes if you get stuck after downgrading system you must do a factory reset otherwise you'll get stuck in the ATT LOGO.
sunderwear thank you I downloaded it kitkat zip file. I flashed it with safestrap and then I flashed suprSu then I reboot the phone won't boot ... I flushed with Odin the kernel 4.4.2 every things works greats
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
tet1 said:
sunderwear thank you I downloaded it kikat zip file I flashed it with safestrap and the I flashed supruser I reboot my phone won't boot then I flushed with Odin the kernel 4.4.2 very things works greats
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Click to expand...
Click to collapse
Glad to hear it worked for you. REMEMBER EVERYONE YOU MUST FLASH THE KITKAT KERNEL AFTER FLASHING the kitkat.zip update.
I was on ML2 with root .. and I did the stapes above
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
So I can't lock the screen no matter what it is set to. Any way to fix?
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Hey guys. I'm hoping someone with more knowledge will be able to help. I was previously rooted using CF Autoroot and tried to install TWRP when it was released. Tried to flash it with Odin but it failed so I Odined to the latest firmware and tried to reroot but that failed and I'm currently unrooed.
Any ideas?
Same.
i also using that cf-root. i have no problem rooting it. just make sure usb debug check and follow guide. i did it on 2 of my note 4 both with no problem.
solographics said:
Hey guys. I'm hoping someone with more knowledge will be able to help. I was previously rooted using CF Autoroot and tried to install TWRP when it was released. Tried to flash it with Odin but it failed so I Odined to the latest firmware and tried to reroot but that failed and I'm currently unrooed.
Any ideas?
Click to expand...
Click to collapse
Reflash back to stock using ODIN, root using CF-Root, download Flashify from the Play Store and use that to flash TWRP. Of course, follow all directions to each step to the "T".
I'll give that a try tonight after work and report back.
solographics said:
I'll give that a try tonight after work and report back.
Click to expand...
Click to collapse
Mine said "failed" too. Nothing I could do would make any difference. So I unplugged the phone, pulled the battery waited a few seconds and powered back on. To my amazement, the rooting process continued and when it rebooted, I was rooted. Same thing happened when I odined twrp.
Charlie
Same thing happened to me! Been struggling with this 24 hrs now.
Solved!!!
I solved my problem by doing a factory reset on the phone in the settings>backup/reset>factory reset or something like that then going through the rooting process outlined by TEKHD.
Hope this helps everyone else having the same problem.
OK I GOT IT GUYS! If you have the reactivation lock checked in the security setting then its preventing odin from doing its thing. Just uncheck that and it should work.
hello
i upgraded my phone to 4.4.4 weeks ago, but when i needed to root it -> i had to downgrade to 4.4.2 and make the root then upgrade again to 4.4.4 using flashtool.
now after those steps i can't enter the recovery mode at all !
i tried every way to enter it but failed.
any ideas please?
thanks
drmet said:
hello
i upgraded my phone to 4.4.4 weeks ago, but when i needed to root it -> i had to downgrade to 4.4.2 and make the root then upgrade again to 4.4.4 using flashtool.
now after those steps i can't enter the recovery mode at all !
i tried every way to enter it but failed.
any ideas please?
thanks
Click to expand...
Click to collapse
Ahh!! have you installed any recovery??
drmet said:
hello
i upgraded my phone to 4.4.4 weeks ago, but when i needed to root it -> i had to downgrade to 4.4.2 and make the root then upgrade again to 4.4.4 using flashtool.
now after those steps i can't enter the recovery mode at all !
i tried every way to enter it but failed.
any ideas please?
thanks
Click to expand...
Click to collapse
does your root still work, did you flash the complete 4.4.4 ftf, that would mean you flashed even the root and your phone is back to stock.
follow this again http://forum.xda-developers.com/showpost.php?p=55357181&postcount=1
coolrevi said:
Ahh!! have you installed any recovery??
Click to expand...
Click to collapse
thanks for reply, actually i'm not so experienced in these issues.
i did the steps of rooting by downgrading and upgrading again, but didn't install any recovery !
may you help me how to install a recovery whenever i'm using the stock firmware?
thanks again
RohitBopnna said:
does your root still work, did you flash the complete 4.4.4 ftf, that would mean you flashed even the root and your phone is back to stock.
follow this again http://forum.xda-developers.com/showpost.php?p=55357181&postcount=1
Click to expand...
Click to collapse
thanks for reply,
when i made the downgrade and upgrade again, the steps included flashing the kernel only, and at the end the root was working nicely.
but when failed to enter recovery mode, i made a complete flash cuz i thought the problem is with the root !
but still got nothing and can't enter the recovery.
still want me to follow those steps in the link?
thx
drmet said:
thanks for reply,
when i made the downgrade and upgrade again, the steps included flashing the kernel only, and at the end the root was working nicely.
but when failed to enter recovery mode, i made a complete flash cuz i thought the problem is with the root !
but still got nothing and can't enter the recovery.
still want me to follow those steps in the link?
thx
Click to expand...
Click to collapse
looks like you need to install a Recovery.
Download "Installer" XZ-lockeddualrecovery2.8.2-RELEASE.installer.zip from http://nut.xperia-files.com/XZDualRecovery and follow steps here to install
http://forum.xda-developers.com/showpost.php?p=46341961&postcount=2
to hard reset the phone i used to enter the recovery mode and reset the phone.....not i cannot after lollipop update.
Hey guys, I was just wondering if I can flash the 4.4.4 or 4.4.2 in Odin to downgrade then root? I'm on stock 5.0 now
Thanks In advance
michael872410 said:
Hey guys, I was just wondering if I can flash the 4.4.4 or 4.4.2 in Odin to downgrade then root? I'm on stock 5.0 now
Thanks In advance
Click to expand...
Click to collapse
With the OC4 boot loader on the device I was able to flash the 'downgrade to nce' full rom in ODIN, documented steps from there to reassert root will work.
http://forum.xda-developers.com/att...to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120
C0derbear said:
With the OC4 boot loader on the device I was able to flash the 'downgrade to nce' full rom in ODIN, documented steps from there to reassert root will work.
Pls someone help , I updated to lolipop. In order to get root , i dowgraded to 4.4.2 and got my phone soft brick . Pls someone help.
Click to expand...
Click to collapse
took 5.0 update from att yesterday and am unable to downgrade!! tried downgrade to nce but soft brick and had to use the 5.0 partitions tar to get back up and running. and solutions to downgrade with success and root??
C0derbear said:
With the OC4 boot loader on the device I was able to flash the 'downgrade to nce' full rom in ODIN, documented steps from there to reassert root will work.
http://forum.xda-developers.com/att...to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120
Click to expand...
Click to collapse
C0derbear said:
With the OC4 boot loader on the device I was able to flash the 'downgrade to nce' full rom in ODIN, documented steps from there to reassert root will work.
http://forum.xda-developers.com/att...to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120
Click to expand...
Click to collapse
That is good news but I believe that you have been the only one able to successfully downgrade. Hope others that have had success chime in.
Just to confirm, that you took the 5.0 ota yesterday correct?
Do you have a link to that file?? i have a downgrade to nce file but not sure if its the one you used or not . the one i have softbricked me so i had to use the 5.0 partition tar to fix
C0derbear said:
With the OC4 boot loader on the device I was able to flash the 'downgrade to nce' full rom in ODIN, documented steps from there to reassert root will work.
http://forum.xda-developers.com/att...to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120
Click to expand...
Click to collapse
muniz_ri said:
That is good news but I believe that you have been the only one able to successfully downgrade. Hope others that have had success chime in.
Just to confirm, that you took the 5.0 ota yesterday correct?
Click to expand...
Click to collapse
The sequence is silly, but whatever.
I started with 4.4.4, rooted, safestrap. Very light root usage - props file changed to enable SD card usage for more apps, logon sound replaced with silence, TiBu (with bloatware/et. al. frozen but not removed), ServiceDisabler, Busybox, Safestrap. Otherwise stock.
Made safestrap and Kies backups.
Used your zip under safestrap to wipe and restore, rebooted w/o odin flashing the boot/kernel from you the first time (didn't catch the reboot fast enough).
After allowing the device to sit black-screened for a few minutes to make sure I wasn't being impatient, I powered down, brought it up into download mode, and ODIN flashed your second step (bootloader/partitions/whatever else is in that flash).
Power cycled phone, it again locked up black-screen without getting even the Samsung animation.
Waited a few minutes to to be sure, and power cycled again to be sure.
Brought phone up, used ODIN to flash the 'downgrade to NCE' package.
Power cycled, phone booted normally, let it go into setup sequence but skipped everything until I could tell it to shut down.
Brought phone up, used ODIN to flash the next two OTA files to bring it to 4.4.4.
Again, power cycled, phone booted normally, let it go into setup sequence but skipped everything until I could tell it to shut down.
Brought phone up, used ODIN to flash the 5.0 OTA.
Brought phone up, runs as expected (of course, no root).
Addendum. I have extra fun with ODIN because my PC runs Ubuntu Linux, so I use Odin within Win 8 running inside VMware Player. Seems to work fine but I would never guarantee it doesn't introduce quirks.
I may at some point in the next couple weeks backstep and again try your safestrap based root-keep setup, but want to take some time with it 100% stock and see how things run.
Cheers.
C0derbear said:
The sequence is silly, but whatever.
I started with 4.4.4, rooted, safestrap. Very light root usage - props file changed to enable SD card usage for more apps, logon sound replaced with silence, TiBu (with bloatware/et. al. frozen but not removed), ServiceDisabler, Busybox, Safestrap. Otherwise stock.
Made safestrap and Kies backups.
Used your zip under safestrap to wipe and restore, rebooted w/o odin flashing the boot/kernel from you the first time (didn't catch the reboot fast enough).
After allowing the device to sit black-screened for a few minutes to make sure I wasn't being impatient, I powered down, brought it up into download mode, and ODIN flashed your second step (bootloader/partitions/whatever else is in that flash).
Power cycled phone, it again locked up black-screen without getting even the Samsung animation.
Waited a few minutes to to be sure, and power cycled again to be sure.
Brought phone up, used ODIN to flash the 'downgrade to NCE' package.
Power cycled, phone booted normally, let it go into setup sequence but skipped everything until I could tell it to shut down.
Brought phone up, used ODIN to flash the next two OTA files to bring it to 4.4.4.
Again, power cycled, phone booted normally, let it go into setup sequence but skipped everything until I could tell it to shut down.
Brought phone up, used ODIN to flash the 5.0 OTA.
Brought phone up, runs as expected (of course, no root).
Addendum. I have extra fun with ODIN because my PC runs Ubuntu Linux, so I use Odin within Win 8 running inside VMware Player. Seems to work fine but I would never guarantee it doesn't introduce quirks.
I may at some point in the next couple weeks backstep and again try your safestrap based root-keep setup, but want to take some time with it 100% stock and see how things run.
Cheers.
Click to expand...
Click to collapse
Thank you, but based on what you have stated you never flashed the OC4 bootloader which explains why you were able to downgrade.
At this time there is no downgrade method for those that have taken the OC4 ota update.
muniz_ri said:
Thank you, but based on what you have stated you never flashed the OC4 bootloader which explains why you were able to downgrade.
At this time there is no downgrade method for those that have taken the OC4 ota update.
Click to expand...
Click to collapse
Wasn't that part of G900A_OC4_Stock_Partitions_wOA1_BL.tar.md5 (flashed via ODIN after restoring your backup in SS)?
C0derbear said:
Wasn't that part of G900A_OC4_Stock_Partitions_wOA1_BL.tar.md5 (flashed via ODIN after restoring your backup in SS)?
Click to expand...
Click to collapse
No, that file includes the OA1 bootloader.
Got it. Thanks.
Sent from my Nexus 7 using Tapatalk
So let me get this straight, if ur not rooted and running 5.0 theres no way to root after taking 5.0 ota??
Joehen873 said:
So let me get this straight, if ur not rooted and running 5.0 theres no way to root after taking 5.0 ota??
Click to expand...
Click to collapse
YES! If your phone is on official ATT 5.0 OTA, then there is NOT a way to root or even downgrade to NCE. You will have to wait until root exploit is found or bootloader unlocked.
Sent from my SAMSUNG-SM-G900A
removed
Deleted
gallupcomputers said:
STEPS I TOOK TO ROOT.
You will have to start from scratch and factory.
Download on your pc and flash in download mode the G900A_Downgrade_to_NCE.tar using Odin's PDA slot(AP in Odin v3.09+) This will bring device to stock factory.
Setup you phone first use.
Download and place the G900A_NCE_to_NG3_OTA.zip onto your ext-sdcard and sideload from stock recovery.
Flash the G900A_ND3_Stock_Kernel using Odin's PDA slot(AP in Odin v3.09+).
Install Towelrootv3.apk and run app and update SuperSu
Install safestrap.
Make a nandroid backup with safestrap To ext-sdcard.
Extract the G900A_OC4_Stock_Rooted_Backup folder from the .rar archive and place it into the following folder: ext-sdcard/TWRP/BACKUPS/xxxxxx, fyi...the name of this folder will vary.
From Safestrap recovery press "Wipe" then "Advanced Wipe" and wipe everything but your ext-sdcard.
From the main menu press "Restore," then select and restore the G900A_OC4_Stock_Rooted_Backup.
Once complete from the main menu press "Reboot," then reboot into "Download" mode.
Last, flash the G900A_OC4_Stock_Partitions_wOA1_BL using Odin's PDA slot (AP in Odin v3.09+) and reboot.
All credit goes to Muniz_ri.
This is were I downloaded everything from Muniz_ri
I got most everything from his 4.4.4 upgrade steps.
http://forum.xda-developers.com/att...to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120
And his how to keep root Lollipop
http://forum.xda-developers.com/att...w-to-update-to-g900aoca-5-0-keeproot-t3076803
Click to expand...
Click to collapse
Stop giving wrong information! Did you read the OP? This is about downgrading stock OTA 5.0 and not rooting. You cannot downgrade if your phone is on official stock OTA 5.0……! You will brick your phone. The information you have provided only works if your phone is Still on NG3 or OA1. Again if your bootloader is already on OC4, then you cannot downgrade. The reason @muniz_ri method can be downgraded is that he using a 5.0 ROM while keeping the bootloader at OA1.
Sent from my SAMSUNG-SM-G900A
Billy06010 said:
took 5.0 update from att yesterday and am unable to downgrade!! tried downgrade to nce but soft brick and had to use the 5.0 partitions tar to get back up and running. and solutions to downgrade with success and root??
Click to expand...
Click to collapse
I mistakenly tried to downgrade my AT&T S5 after the lollipop OTA update... am now soft bricked. can you please elaborate on what you did regarding "5.0 partitions tar" to get back up and running? process steps and where to get said file(s) would be GREATLY appreciated!!!
DamnYank! said:
I mistakenly tried to downgrade my AT&T S5 after the lollipop OTA update... am now soft bricked. can you please elaborate on what you did regarding "5.0 partitions tar" to get back up and running? process steps and where to get said file(s) would be GREATLY appreciated!!!
Click to expand...
Click to collapse
I am in the same boat. Please explain how you got your phone back to working after ota 5.0 upgrade then attempting to downgrade because i did the same thing and now in a soft brick.
DamnYank! said:
I mistakenly tried to downgrade my AT&T S5 after the lollipop OTA update... am now soft bricked. can you please elaborate on what you did regarding "5.0 partitions tar" to get back up and running? process steps and where to get said file(s) would be GREATLY appreciated!!!
Click to expand...
Click to collapse
If you need help I solved my soft brick. Put your phone into download mode then flash the stock kernal using odin. Reboot then flash using odin the stock partition. While this wont downgrade to 4.4.X because you are on ota 5.0 you will be able to get your phone back to 5.0 lollipop. Thanks to Fitz110 who uploaded these files and for the solution. Here is where I go these from. http://forum.xda-developers.com/att...phone-trying-to-downgrade-to-4-t3076706/page4
https://drive.google.com/file/d/0B7W6koj4lSniQ3ZQUXVCMGg4MWM/view?usp=sharing stock kernal
https://drive.google.com/file/d/0B7W6koj4lSniX1JRaHVMSDdSLW8/view?usp=sharing stock partition.
Thank you sooooo much was freaking out at first but I knew eventually someone would figure out something. Thanks to you all!!!
This fixed my soft brick phone after I tried to root it on 5.0
Would kingroot or kingoroot work to root the oc4 lollipop?
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