Database Develop

[OFFICIAL UPDATE][ROM]EL01 HC 3.2 TW UX update file for the VZW LTE Galaxy Tab 10.1

Ok guys, for all of you who are STILL waiting for the official update to roll out to our tabs, wait no longer. Thanks to PCPIMP over on android forums who pulled the update file from /cache in his tab before installing, we now have it and can flash it ourselves. However, there are a few quirks to getting this thing to flash properly. First: It must be flashed from stock recovery, NOT cwm recovery. Also, once you download the file from the multiupload link, you must rename it to update.zip Be careful here. When I renamed it to update.zip, somehow it would automatically add "bin" on to the end of the file. So without being able to see it, the file ended up with the name update.zip.bin and it was not showing up in stock recovery to flash. Use a file manager like 7zip to change the name or open up the properties on your PC to do it properly. Once it's renamed properly, put it on the the SD card. Here is something I am not completely sure of......but I *think* it doesn't matter what build you're on when you flash this file. It appears to me to be very insecure. You can even open up the update.zip with 7zip and debloat the stuff you don't want. I did. I only see one "patch" file in the update.zip and that was the LTE modem. What that means I'm prettty sure is that it will only require one file to be present on your tab to flash properly. This *may* even be able to be flashed directly from the Leak I posted of this build, for those of you who are on it. As long as you are on the correct radio because that's what it looks for. When you flash this file, it even wipes your data for you, But it does NOT wipe the SD card. I actually flashed it twice to see how secure it was. I flashed it from EH04 and EH04 radios and then I reflashed it directly over itself (EL01 and the EL01 radios) and it worked fine. So, I hope everyone understands all of that long winded babble I just spewed.
Step 1. Download update http://goo.gl/6XtFD (<--Huge thanks to PCPimp for hosting this) and rename it PROPERLY with 7zip or something to update.zip and place it on the root of your SD card. Make sure you don't have any other files named update.zip already on your SD, as that could get confusing, lol.
Step 2. Odin flash this recovery: http://dl.dropbox.com/u/20070269/lterec.tar.md5
Step 3. Boot into the stock recovery you just flashed and select apply update from SD card. Then scroll until you find update.zip. If it is not there, that means you didn't properly rename it. It most likely added the letters bin to the end of the name and can't be recognized by the recovery. So reboot and fix that and then start step 3 back over.
Step 4. When it is named properly and you flash it, most likely you are immediately going to see the dreaded Yellow exclamation point on the android signifying that there is an error or that you did something wrong.......Just wait. Keep watching it. It will eventually flash and your tab will reboot and you will be on EL01 and updated. Now, if you want root, see step 5
Step 5. Download both of these files: Kernel - http://droidbasement.com/galaxy/ker...36.4_lte_hc32-oc-xtra-vfpv3-d16_fp-010912.zip SU.zip - http://dl.dropbox.com/u/20070269/Superuser-3.0.7-efgh-signed.zip and put them both on your SD card.
Step 6. Open up odin program on your PC and click PDA and you will need to quene up this file in PDA: http://dl.dropbox.com/u/20070269/recovery.tar.md5 also, uncheck Auto Reboot in odin. YOU DO NOT WANT AUTO REBOOT TO HAVE A CHECK IN IT IN ODIN. REMOVE IT. Then power off tab and then boot into download mode by holding the power button until you see the samsung galaxy tab screen, then quickly let go of the power button but then immediately after and at the same time, hold power button and volume up until you are given two choices: A white box or the android. Careful, volume down at this point will choose for you. You will already be on the one you want to choose, which is the full sized android. BUT, make sure that odin is completely ready to go first. Make sure the recovery.tar that you just downloaded is quened up in PDA. On your tab push the volume down button and then follow the screen instructions. When the "Downloading" screen comes on, you need to move kinda quickly but you can relax. Just plug it in and hit start in odin. When you see the green pass in odin, unplug the tab and use the volume and power buttons again to boot into the other option, the white box and the little android. THIS IS VERY IMPORTANT! Once you have flashed the recovery.tar file, you must NOT let the tablet boot up fully and normally. You must directly into recovery. If it fully boots first, then the stock kernel will overwrite the cwm recovery with the stock recovery.
Step 7. So once you boot into to the turquoise cwm recovery, flash the 2 files you downloaded in step 5 in this order: The awesome kernel first, credit to Pershoot. Then flash the SU.zip file credit to ChainsDD: <------sometimes this SU.zip file will give you an error in CWM recovery when flashing it, just try it again and it will work.
Step 8. Reboot your tablet and enjoy a rooted EL01 updated tab with an AWESOME OC kernel from Pershoot.
Credit
Pershoot for the sweet kernel and recovery used in my guide
PCPIMP for pulling the update file from his tab and uploading it for us all
ChainsDD for root in general and the Superuser.zip used in my guide

Minor bloat removed...pretty darn fast without deodexing or kernel changes. I may just keep it stock with SU access.

Thanks for the files and the guide, everything is working great. I didn't wipe and am really surprised how well it's working, but still wish I could get rid of the TouchWiz stuff.
If I might make a suggestion, it'd be good to know to copy SU and the kernel to the device before flashing the CWM Recovery via ODIN. After flashing CWM, I had to let the tablet start up, copy the files, re-flash with ODIN, then load CWM and flash the kernel and SU. Not a big deal, just could have saved a step for me (although, I also could have read ahead...).

So i odin'd back to factory stock to use this, and it did push this update to me at the end of it, so it wound up not being necessary, thanks though!

Installation of the ROM failed. I did initially get the yellow exclamation mark you spoke of in step 4, but it went away and the moving gears appears showing progress. The yellow exclamation mark reappeared, however, and after 15 minutes I powered off. A bootloop ensued... downloading a TAR file of the stock shipped Verizon ROM to use in ODIN.

Is the ota update radios the same as in the leak?
sent from my 4g galaxy tab

inline6power said:
Is the ota update radios the same as in the leak?
sent from my 4g galaxy tab
Click to expand...
Click to collapse
No they are not.
Sent from my SCH-I905 using Tapatalk

ifiweresolucky said:
Installation of the ROM failed. I did initially get the yellow exclamation mark you spoke of in step 4, but it went away and the moving gears appears showing progress. The yellow exclamation mark reappeared, however, and after 15 minutes I powered off. A bootloop ensued... downloading a TAR file of the stock shipped Verizon ROM to use in ODIN.
Click to expand...
Click to collapse
Hmmm......interesting. What build and radio were you on when you flashed the update zip?
Sent from my SCH-I905 using Tapatalk

ifiweresolucky said:
Installation of the ROM failed. I did initially get the yellow exclamation mark you spoke of in step 4, but it went away and the moving gears appears showing progress. The yellow exclamation mark reappeared, however, and after 15 minutes I powered off. A bootloop ensued... downloading a TAR file of the stock shipped Verizon ROM to use in ODIN.
Click to expand...
Click to collapse
Had the exact same results using leaked 3.2 Baseband i905.02V.EIO2 Build HT85B.EIO3.SCH-I905.EI03 pershoot Kernal

Psean said:
Had the exact same results using leaked 3.2 Baseband i905.02V.EIO2 Build HT85B.EIO3.SCH-I905.EI03 pershoot Kernal
Click to expand...
Click to collapse
Yea, it seems that we do in fact have to be on at least the EH04 radios to flash the update. I noted in the OP that the update.zip contains an LTE modem patch, meaning it first has to detect the prior official radio so that it can patch the update to the modem. If it doesn't detect the correct modem, it errors out.
Sent from my SCH-I905 using Tapatalk

Is it any better or different than the leaked version though? I'd rather not go through the hassle if I'm not getting any changes over what I already have. Currently supercharged and zipaligned so I don't have any performance complaints right now, looking ahead to ics if there's nothing new in this ROM.

muzzy996 said:
Is it any better or different than the leaked version though? I'd rather not go through the hassle if I'm not getting any changes over what I already have. Currently supercharged and zipaligned so I don't have any performance complaints right now, looking ahead to ics if there's nothing new in this ROM.
Click to expand...
Click to collapse
Way better. Radios are ten times better and the nice thing is now ypi can view the market in portorit and not just landscape
sent from my 4g galaxy tab

muzzy996 said:
Is it any better or different than the leaked version though? I'd rather not go through the hassle if I'm not getting any changes over what I already have. Currently supercharged and zipaligned so I don't have any performance complaints right now, looking ahead to ics if there's nothing new in this ROM.
Click to expand...
Click to collapse
I have to agree that the radios are better. And, to me, it actually seems a little more snappy. And I don't think it's placebo either because at first, the update seemed a little buggier. But now that a few days has passed, I guess it's settled and it appears the bugs are gone. I would suggest updating.
Sent from my SCH-I905 using Tapatalk

kidserious said:
Step 5. Download both of these files: Kernel - http://droidbasement.com/galaxy/ker...36.4_lte_hc32-oc-xtra-vfpv3-d16_fp-010912.zip SU.zip - http://dl.dropbox.com/u/20070269/Superuser-3.0.7-efgh-signed.zip and put them both on your SD card.
Step 6. Open up odin program on your PC and click PDA and you will need to quene up this file in PDA: http://dl.dropbox.com/u/20070269/recovery.tar.md5
Click to expand...
Click to collapse
Question for you. I was already updated before this was posted, but if I odin in the recovery file in step 6, then flash in the 2 files from step 5, the end result will still be the same right? Rooted, with CWM and Pershoot's kernel installed, on the official update?
EDIT: NVM. I followed step 6 to the letter, then flashed in files from step 5. Of course next stop was SetCPU... Everything working fine.

eXiled Killah said:
Question for you. I was already updated before this was posted, but if I odin in the recovery file in step 6, then flash in the 2 files from step 5, the end result will still be the same right? Rooted, with CWM and Pershoot's kernel installed, on the official update?
EDIT: NVM. I followed step 6 to the letter, then flashed in files from step 5. Of course next stop was SetCPU... Everything working fine.
Click to expand...
Click to collapse
Yep, that works, lol. Cool deal
Sent from my SCH-I905 using Tapatalk

Bah . . stuck at bone stock 3.2 with stock recovery.
Tried flashing CWM 5.0.2.7 both from the dropbox link and from pershoot's site but when I try to boot into it I just get a blank screen. Rebooting into 3.2 gets me back the stock recovery but I'm unable to get CWM to work.
Open to ideas.
Odin flash of the CWM recovery file goes perfectly smoothly. I reboot and pick it and immediately get a blank screen (can see the bleed through of the backlight) and it sits there for as long as I let it (left it for 5 minutes waiting).
Long story short, I didnt realize the issue with the modems before trying the procedure coming from the leaked 3.2 which forced me to do a full wipe and reset using stock 3.1 and doing OTA updates normally to get to 3.2. That all went okay after spending an hour figuring out what was wrong . .

muzzy996 said:
Bah . . stuck at bone stock 3.2 with stock recovery.
Tried flashing CWM 5.0.2.7 both from the dropbox link and from pershoot's site but when I try to boot into it I just get a blank screen. Rebooting into 3.2 gets me back the stock recovery but I'm unable to get CWM to work.
Open to ideas.
Odin flash of the CWM recovery file goes perfectly smoothly. I reboot and pick it and immediately get a blank screen (can see the bleed through of the backlight) and it sits there for as long as I let it (left it for 5 minutes waiting).
Long story short, I didnt realize the issue with the modems before trying the procedure coming from the leaked 3.2 which forced me to do a full wipe and reset using stock 3.1 and doing OTA updates normally to get to 3.2. That all went okay after spending an hour figuring out what was wrong . .
Click to expand...
Click to collapse
Apply rooted kernel, because stock kernel keeps on flashing stock recovery. then flash custom recovery. sounds like recovery is being stupid/corrupted. Or odin back to stock then reroot etc.

magneticzero said:
Apply rooted kernel, because stock kernel keeps on flashing stock recovery. then flash custom recovery. sounds like recovery is being stupid/corrupted. Or odin back to stock then reroot etc.
Click to expand...
Click to collapse
Not sure why I had to but I rebooted my PC and tried again. What I noted is after updating to 3.2 via OTA my pc stopped recognizing the tablet on the USB port I normally used to flash. Other ports worked so I switched but as you suggested the recovery being flashed by Odin was going in corrupted.

muzzy996 said:
Not sure why I had to but I rebooted my PC and tried again. What I noted is after updating to 3.2 via OTA my pc stopped recognizing the tablet on the USB port I normally used to flash. Other ports worked so I switched but as you suggested the recovery being flashed by Odin was going in corrupted.
Click to expand...
Click to collapse
So you got cwm flashed eventually?
Sent from my SCH-I905 using Tapatalk

kidserious said:
So you got cwm flashed eventually?
Sent from my SCH-I905 using Tapatalk
Click to expand...
Click to collapse
Yep, all back to normal. We'll see how it goes. Out of the box it was noticably better than the leak, like perhaps it was zipaligned or something. Leaked rom with zipalign and v6 supercharger was pretty sweet already though.
Running fine right now.
Most irritating thing for me is the wifi toggle is gone from notification menu, replaced instead with mobile data toggle. Why someone would do this is beyond me. Leaked version had both a wifi toggle and an airport mode one. Now, I have to add a toggle onto a home screen, run extended controls or dive into settings manually to toggle it.
Also I'm not 100% sure if I hit it by mistake but I could have sworn I turned off auto brightness this morning and yet it was back on during lunch today.
All in all I'll agree its worthwhile to move from leaked to this but only marginally so, for stability sake and getting the latest modem drivers. If it puts you closer to the next OTA then its worth it.

[Q] Stuck without a ROM and safestrap

while i was installing xnote build 11 i forgot to acutally install the zip before going to odin but i did remembered to delete system and data so now im stuck at the boot screen and i cant go into recovery since safestrap got deleted when i deleted the stock rom so i can get into download but i didnt have usb debugging on so i cant really use ADB im little stuck on what i should do next..

SS is still there. You need to get the togetsafestrap files provided in the OP and in the thread. They were posted shortly after you asked in there.
Also, please only post questions one time.
Sent from my SM-N9005A using XDA Premium 4 mobile app

A30laa said:
while i was installing xnote build 11 i forgot to acutally install the zip before going to odin but i did remembered to delete system and data so now im stuck at the boot screen and i cant go into recovery since safestrap got deleted when i deleted the stock rom so i can get into download but i didnt have usb debugging on so i cant really use ADB im little stuck on what i should do next..
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=2476353 to get back to stock and start over.
Also, usb will still work in download mode (follow instructions in thread). If you have trouble getting your device recognized in ODIN then try a different USB slot. That solves 90% of the problems with ODIN.

graydiggy said:
SS is still there. You need to get the togetsafestrap files provided in the OP and in the thread. They were posted shortly after you asked in there.
Also, please only post questions one time.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So I downloaded those files and went through that process of installing so what I should do is odin those files then I should be able to hit vol down and powrr to get into ss since it doesn't pop up like safestrap usually does? Because all I see is the note 3 boot screen not the ss before that

You need to restore back to stock using the link i posted earlier.
Then root using kingo.
Install custom safestrap apk.
Install recovery in safestrap app.
Manually reboot into download mode.
Use ODIN and flash 'togetsafestap'.
Reboot and select recovery at startup.
Wipe everything except 'ext sd card'.
Install custom rom ( I recommend Knoxdroid 4.0 + Bobcat theme)
Clear dalvik and cache.
Reboot into download mode.
Use ODIN to flash 'togetbooting'.
Reboot into system.
Enjoy.
This is the best and fastest way to avoid any problems that may have been introduced with what has already been done. If you need any help just ask and feel free to search the dev threads.

Its been a while since I messed around with linux is there a verison you recommend to use on VMware since I'm going to be using it on Windows?

A30laa said:
Its been a while since I messed around with linux is there a verison you recommend to use on VMware since I'm going to be using it on Windows?
Click to expand...
Click to collapse
If you prefer Windows, use this thread. It's probably a bit easier to tell you the truth. Let me know if you need anything else.

[How-To] Root GS5 Active - G870A_OA1 - 4.4.4 (2/7/2015)

**Make certain that your reactivation lock in security settings is off before beginning this process**
1. Take the OA1 OTA update.
2. Download and install Towelroot-v3.apk(this version does not require internet access).
3. Place your phone into "Download Mode" (press and hold the Home, Volume Down, and Power keys until the phone powers on and displays warning screen, then press Volume Up key) and flash the G870A_NE4_Stock_Kernel using Odin's PDA slot(AP in Odin v3.09+).
4. Open the Towelroot app from your app drawer and press "Make it Rain" to root your device.
5. Power off then boot into "Download Mode" again and flash the G870A_OA1_Stock_Kernel also using Odin's PDA slot(AP in Odin v3.09+).
6. Install SuperSU to manage root access. Done!
Troubleshooting:
1. Should the OA1 OTA update fail consider flashing the G870AUCU1ANE4_Full_Odin.tar to return to factory stock then take the OTA updates to OA1. Or, place the G870A_NE4_to_NG3_OTA.zip and G870A_NG3_tA1_OTA.zip onto your ext-sdcard and sideload each file from stock recovery beginning with the G870A_NE4_to_NG3_OTA.zip. Once updated to OA1 continue from Step 2 above.
2. When flashing the kernel the most common cause of an Odin flash failure is a bad usb port or cable. Please check before reporting a failure!
Notes:
1. The above process will not affect your User Data or Knox Warranty Flag.
2. After flashing the NE4 kernel your phone will run a little wonky and towelroot may not root on the first try. If that happens reboot and try towelroot once again. Once rooted and after flashing the OA1 kernel your phone will once again run like a champ!
Alternative Method for Safestrap Users:
1. Place the G870A_OA1_100%_Stock_Rooted_ROM onto your ext-sdcard.
2. From Safestrap recovery press "Backup" and backup your User Data.
3. From the main menu press "Wipe" then perform an "Advanced Wipe" and wipe everything but your ext-sdcard.
4. Next, press "Install," then select and install the G870A_OA1_100%_Stock_Rooted_ROM.
5. Once complete, press "Restore" and restore your User Data.
6. Last, from the main menu press "Reboot," then "System." Done!
After following the above process your phone will pause on the AT&T splash screen for about 2 minutes before rebooting.
Notes:
1. The above process will not affect your User Data or Knox Warranty Flag.
2. The ROM will update your Modem, Non-hlos, System, Kernel, Stock Recovery, and Bootloader to OA1.
3. The "Backup" and "Restore" steps in the instructions are not mandatory but will greatly reduce your device's set-up time. All currently installed non-system apps and settings will be automatically restored.
4. The ROM does not contain BusyBox which is required by the Safestrap.apk. Download the BusyBox Installer to re-install BusyBox.

Let me be the first to comment...I rooted doing this but since I was already rooted I had to Odin back to ne4 then ng3 (sideload or ota, what ever works) and then update to oa1 (sideload or what ever works). After that, everything is exactly as the tutorial says.
Sent from my SAMSUNG-SM-G870A using Tapatalk

Did you have to revert just the kernel or the whole ROM before you could install the OTA update? I'm currently Towelrooted on NG3 and patiently awaiting the OTA download.

bigric_tx said:
Did you have to revert just the kernel or the whole ROM before you could install the OTA update? I'm currently Towelrooted on NG3 and patiently awaiting the OTA download.
Click to expand...
Click to collapse
I had to Odin the whole ne4 Rom and then from there use the ota update files to get to oa1 and then use the kernel trick to root with towelroot. Other wise it kept giving me signature errors even if I Odin'd just the system partition
Sent from my SAMSUNG-SM-G870A using Tapatalk

Can anyone tell me whether the G870AUCU1ANE4 full odin tar file will reinstall previously deleted system files or not. I was thinking of using titanium backup to remove a lot of bloatware but want to know first if this will get me back to stock with all factory equipped apps. When I flashed this full odin tar so that I could update and then reroot, my home screen and all my apps went unchanged so I'm skeptical to believe it's similar to flashing the phone back to stock.
thank you for any help

nhautotech said:
Can anyone tell me whether the G870AUCU1ANE4 full odin tar file will reinstall previously deleted system files or not. I was thinking of using titanium backup to remove a lot of bloatware but want to know first if this will get me back to stock with all factory equipped apps. When I flashed this full odin tar so that I could update and then reroot, my home screen and all my apps went unchanged so I'm skeptical to believe it's similar to flashing the phone back to stock.
thank you for any help
Click to expand...
Click to collapse
Yes it will
Sent from my SAMSUNG-SM-G870A using Tapatalk

bigwillyg said:
Yes it will
Sent from my SAMSUNG-SM-G870A using Tapatalk
Click to expand...
Click to collapse
So it will replace deleted system apps but leaves user installed apps alone?
Will performing a factory reset on this phone replace deleted system apps?
The phone i had prior was an s2 and when using odin to flash it with a stock rom, it would be similar to factory resetting it but when i flashed the full ne4 on this one, I still had all my apps and home pages, settings etc. I know the flash worked cause i was able to install the update that i couldn't before flashing due to towelroot.
I just realized the full ne4 file linked to in this thread (.rar zip file) isn't exactly the same as the stock firmware file available from sammobile (zip zip file). Is the ne4 .rar file linked to here modified to leave the users apps and settings alone?

Thanks. Worked great. :good:
I used safestrap. Very easy, after days of annoying update notifications.

nhautotech said:
So it will replace deleted system apps but leaves user installed apps alone?
Will performing a factory reset on this phone replace deleted system apps?
The phone i had prior was an s2 and when using odin to flash it with a stock rom, it would be similar to factory resetting it but when i flashed the full ne4 on this one, I still had all my apps and home pages, settings etc. I know the flash worked cause i was able to install the update that i couldn't before flashing due to towelroot.
I just realized the full ne4 file linked to in this thread (.rar zip file) isn't exactly the same as the stock firmware file available from sammobile (zip zip file). Is the ne4 .rar file linked to here modified to leave the users apps and settings alone?
Click to expand...
Click to collapse
I hadn't looked at the one on here but if it's a .tar.md5 then flashing through Odin should reset it back to ne4 stock out of the box with everything. I used the firmware to fully go back to stock
Sent from my SAMSUNG-SM-G870A using Tapatalk

I rooted for the 1st time since getting my new s5 active. Well, it came w/3NG build; Got the OTA BEFORE my 1st attempt at root.
I installed ND via Odon, made it rain, rebooted, & am still on 4.4.4 (0A1A or something of the like.
Didn't even have to follow (or get to) the step to Flash newer kernal to get back to 4.4.4. Thanks all involved

gitardan17 said:
I rooted for the 1st time since getting my new s5 active. Well, it came w/3NG build; Got the OTA BEFORE my 1st attempt at root.
I installed ND via Odon, made it rain, rebooted, & am still on 4.4.4 (0A1A or something of the like.
Didn't even have to follow (or get to) the step to Flash newer kernal to get back to 4.4.4. Thanks all involved
Click to expand...
Click to collapse
You need to flash the newer kernel because your phone could have issues
Sent from my SAMSUNG-SM-G870A using Tapatalk

@muniz_ri Your rooted stock rom worked like charm. Thanks bunch!

You were right bigwillg. Didn't really get a chance to test it 1st. After noticing choppy stuff & a bigger than usual battery drain, I "Odin'ed" the newer kernal. Now its like butter. Still on stock ROM with frozen bloat stuff. Considering uninstalling em all together at a future date. Gonna get to know my phone 1st I guess.
In case I didn't already hit thanks on OP, I soon will. And on a side note THANK you for this topic/forum.
Edit: Watch them push lollipop now. Literally right after I did this. Lol

Hi. Question? Does the Odin in the first post work on the phone, or would I need to use Odin on a PC? Sorry...been out of the scene for awhile lol
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

sailzfast said:
Hi. Question? Does the Odin in the first post work on the phone, or would I need to use Odin on a PC? Sorry...been out of the scene for awhile lol
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Click to expand...
Click to collapse
Odin is for your computer

Unable to install latest OTA
My G870A was rooted before the previous OTA was sent.
This latest OTA gets to about 27%, then fails.
I have looked around to see how to fix this, yet I can't seem to find anything.
The steps here start with the OTA, so they're currently useless to me.
I have tried going back to 4, but towelroot has no way to remove root once set.
SuperSU mentions a removal of root, but it appears to be just to uninstall itself.
Anyone have any ideas?
Andy

llandyw said:
My G870A was rooted before the previous OTA was sent.
This latest OTA gets to about 27%, then fails.
I have looked around to see how to fix this, yet I can't seem to find anything.
The steps here start with the OTA, so they're currently useless to me.
I have tried going back to 4, but towelroot has no way to remove root once set.
SuperSU mentions a removal of root, but it appears to be just to uninstall itself.
Anyone have any ideas?
Andy
Click to expand...
Click to collapse
You need to review the OP more thoroughly.

I repeated the steps, and this time it worked.
Don't know why it didn't work the first time. I don't think I missed any steps.
Andy

odin app?
Im currently stock not rooted was wondering if i absolutely need to use a pc to root my gs5active, or does the odin app work? No pc access, all i have is my phone and a asus memo pad, thanks ; )

Hello,
I am with tmobile with G870A with Ne4 modem rooted. Can I just flash the OA1 modem?

[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

Installing Magisk on Lollipop 5.0 - Paradox?

Ok, so here is an explanation of what I have going on here. My ultimate goal is to install Magisk on my phone (Running Kitkat 4.4) . I have learned that in order to do that, I need to install a custom recovery on my phone. I have learned that normal custom recoveries cannot be installed on AT&T phones because they have double locked bootloaders or something of that nature, but that Safestrap can work around it. So after finding all that out I successfully installed Safestrap then went on to install Magisk, but when I tried to install the zip, I was told that it is only compatible with Android 5.0 minimum. Fast-forward, I install Lollipop 5.0 on my phone successfully. I then go back and install safestrap, however it appears that it is now not compatible with my upgraded kernel and will not show me the custom recovery on startup... So it seems as if Safestrap will only work for me on Kitkat, but what I need it to do I can only do on Lollipop. Am I simply out of luck, or is there some cleaver way around this?
I appreciate any help I can get on the matter.

Did you root your phone while on KK? If not, you may be out of luck now. There are a few lollipop rooted rooms that will work and you can keep using SS but you must already be rooted. Mine is still rooted with SS, I am not upgrading for the foreseeable future.

johnkirchner said:
Did you root your phone while on KK? If not, you may be out of luck now. There are a few lollipop rooted rooms that will work and you can keep using SS but you must already be rooted. Mine is still rooted with SS, I am not upgrading for the foreseeable future.
Click to expand...
Click to collapse
Yes, I rooted my phone while still on KK, then I used Flashfire to upgrade to LP which allowed me to still keep root.

Unfortunately I am not sure why SS isn't working for you, not sure if the lollipop Rom you installed is having issues with it or what? As for the locked boot loader, these phones are like fort Knox. SS is merely a bypass that does not replace an unlocked boot loader.

Justhere4GO said:
Yes, I rooted my phone while still on KK, then I used Flashfire to upgrade to LP which allowed me to still keep root.
Click to expand...
Click to collapse
Ok so if you have three of these four things it should work for you depending if your running a g900a or 870a ,1. you will need the kernel flasher ,900a takes nce kernel flasher , 870a requires ng3 kernal flasher , these are model specific. 2. Busybox installed . 3. Safestrap. 4 safetrap flashable kernels.zips. install busybox, install whichever specific kernel flasher you have per your model, install safetrap. Make sure you have the flashable kernel zip for lollipop on external sd for safe keeping. Cuz if you wipe internal sd for any reason and the zip you will have to resort to the odin flashable versions and odin. Then flash kk kernel with flasher apk then you should enter ss ,flash install magisk then install again the recovery flashable kernel .zip for lollipop and then reboot back into lollipop. All good.
Sent from my SM-G900F using XDA-Developers mobile app

captivated1971 said:
Ok so if you have three of these four things it should work for you depending if your running a g900a or 870a ,1. you will need the kernel flasher ,900a takes nce kernel flasher , 870a requires ng3 kernal flasher , these are model specific. 2. Busybox installed . 3. Safestrap. 4 safetrap flashable kernels.zips. install busybox, install whichever specific kernel flasher you have per your model, install safetrap. Make sure you have the flashable kernel zip for lollipop on external sd for safe keeping. Cuz if you wipe internal sd for any reason and the zip you will have to resort to the odin flashable versions and odin. Then flash kk kernel with flasher apk then you should enter ss ,flash install magisk then install again the recovery flashable kernel .zip for lollipop and then reboot back into lollipop. All good.
Click to expand...
Click to collapse
Alright, now we're getting somewhere. So I downloaded NCE Kernel Flasher (I have 900a), along with the G900A_OC4_Stock_KERNEL_Recovery-Flashable.zip file. So is that file the stock kernel for Lollipop to bring me back after using the program? From what the instructions say, it looks like the NCE Kernel Flasher already comes with the Kitkat kernel in it, but I am still not certain I am reading this correctly.
My second question is about the Magisk program itself if you have any insight on that which you could offer. It is recommended that it be installed on a stock rom, and I believe I need to be unrooted when I put it on to make it work correctly. So while I'm in the safestrap recovery via NCE Flasher, should I do a factory reset first, then flash magisk, then flash the stock kernel zip?

Justhere4GO said:
Alright, now we're getting somewhere. So I downloaded NCE Kernel Flasher (I have 900a), along with the G900A_OC4_Stock_KERNEL_Recovery-Flashable.zip file. So is that file the stock kernel for Lollipop to bring me back after using the program? From what the instructions say, it looks like the NCE Kernel Flasher already comes with the Kitkat kernel in it, but I am still not certain I am reading this correctly.
My second question is about the Magisk program itself if you have any insight on that which you could offer. It is recommended that it be installed on a stock rom, and I believe I need to be unrooted when I put it on to make it work correctly. So while I'm in the safestrap recovery via NCE Flasher, should I do a factory reset first, then flash magisk, then flash the stock kernel zip?
Click to expand...
Click to collapse
Really i havent messed with magisk at all so i cant say anything about that . But yes after you flash it or install it just go back to the install button and install the kernel zip to get you back to lollipop. Then reboot. And yes they are only stock kernels because the bootloader wont let us use custom kernels
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
But on your second question i dont see how you can install it and not be rooted . Because you have to be rooted to have ss running.
Sent from my SM-G900F using XDA-Developers mobile app

captivated1971 said:
Really i havent messed with magisk at all so i cant say anything about that . But yes after you flash it or install it just go back to the install button and install the kernel zip to get you back to lollipop. Then reboot. And yes they are only stock kernels because the bootloader wont let us use custom kernels
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
But on your second question i dont see how you can install it and not be rooted . Because you have to be rooted to have ss running.
Sent from my SM-G900F using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, thanks. I successfully booted up into SS mode. I made a backup just in case I need it, then did a factory reset. I chose my Magisk file through the install option, and confirmed it for installation. But now is shows that it is flashing the file, but I have been stuck on the same screen for roughly 20 minutes so far, with no progress on the status bar. From all of the videos I've seen, it looks like this flashing procedure shouldn't take longer than a minute or so, and I fear that something has gone wrong. I know I need to flash my Lollipop kernal back prior to leaving SS, but if my phone is indeed frozen, if I take out the battery and power it up, will I still get a SS Recovery prompt prior to my Samsung logo popping up so I can restore the backup and my correct kernel, or am I on the path to bricksville?

captivated1971 said:
Really i havent messed with magisk at all so i cant say anything about that . But yes after you flash it or install it just go back to the install button and install the kernel zip to get you back to lollipop. Then reboot. And yes they are only stock kernels because the bootloader wont let us use custom kernels
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
But on your second question i dont see how you can install it and not be rooted . Because you have to be rooted to have ss running.
Click to expand...
Click to collapse
So I did just take out the battery, and was able to get back into custom recovery and restore my backup. I tried to install magisk a few more times to no avail. (Kept saying installing but never progressed) My only thought is that maybe because Magisk is not compatible with Kitkat, I would need to update the kernel back to lollipop first before installing magisk. My concern though is, if that is not what the issue is, then restoring my kernel will keep me from being able to re-enter custom recovery to restore my data if I need to. Does that sound like it could be a plausible reason that the file will not install?
Also, if I do attempt to update the kernel in SS, should I still be able to use Odin to restore a stock rom if I have to pull the battery on my device again due to it freezing during installaion? (I've only used Odin twice, so I'm not 100% sure of it's capabilities).

Justhere4GO said:
So I did just take out the battery, and was able to get back into custom recovery and restore my backup. I tried to install magisk a few more times to no avail. (Kept saying installing but never progressed) My only thought is that maybe because Magisk is not compatible with Kitkat, I would need to update the kernel back to lollipop first before installing magisk. My concern though is, if that is not what the issue is, then restoring my kernel will keep me from being able to re-enter custom recovery to restore my data if I need to. Does that sound like it could be a plausible reason that the file will not install?
Also, if I do attempt to update the kernel in SS, should I still be able to use Odin to restore a stock rom if I have to pull the battery on my device again due to it freezing during installaion? (I've only used Odin twice, so I'm not 100% sure of it's capabilities).
Click to expand...
Click to collapse
Hows it goin? Sorry i dont pop in all the time here . Yes odin will work fine everytime as long as its all stock .but it will wipe everything again except external sd card . So if you saved a backup to internal sd it will be wiped . If you saved to ext sd it will still be there if you have to odin . And everything else will be gone also like ss and kernal flasher and all itll be pure stock again also will erase root.
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
Everything is returnable from on these phones unless you update the bootloader past oc1. Then no root . Even if you hardbrick where it will hardly do nothing but make a sound when plug it to your computer is fixable . But it is a lengthy process and hope you two of them to be able to fix the other or do the right method and be able to flash an image to an sdcard to get you into download mode .lol unless you brick it and just sell it to me for 5 bucks lol.
Sent from my SM-G900F using XDA-Developers mobile app

captivated1971 said:
Hows it goin? Sorry i dont pop in all the time here . Yes odin will work fine everytime as long as its all stock .but it will wipe everything again except external sd card . So if you saved a backup to internal sd it will be wiped . If you saved to ext sd it will still be there if you have to odin . And everything else will be gone also like ss and kernal flasher and all itll be pure stock again also will erase root.
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
Everything is returnable from on these phones unless you update the bootloader past oc1. Then no root . Even if you hardbrick where it will hardly do nothing but make a sound when plug it to your computer is fixable . But it is a lengthy process and hope you two of them to be able to fix the other or do the right method and be able to flash an image to an sdcard to get you into download mode .lol unless you brick it and just sell it to me for 5 bucks lol.
Sent from my SM-G900F using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, good to know. I retried booting into SS, reinstalling lollipop kernel, then installing Magisk, but it still froze without any progress. I think the problem is that I the phone is rooted, and Magisk may only be able to be installed on an unrooted phone (It is meant to replace traditional root with a systemless version that can be toggled on and off). But like you said, I cannot get into my custom recovery unless I'm rooted, so that is the predicament I currently find myself in. I actually tried to uninstall root via SuperUser, but that also froze from me when it showed it was supposed to be uninstalling. I'm not sure if that is due to my phone being rooted on KitKat, and that carrying it over into Lollipop ingrained it to the point where I cannot easily take it out. Anyways, it's looking pretty grim for me being able to install this on my device, but I think I may have to go lurking around in a Magisk forum for my next lead.
Anyways, I really appreciate your help in the matter leading me to how to run SS on Lollipop; I'm sure it will come in hand in the future!