Related
I received notice this morning that a firmware update was ready to install. I chose to install it and the tablet rebooted and start to apply the update. However, it gets to 32% on the update install, stalls, and then reboots and does the exact same thing.
Any thoughts on a solution?
rrhutch said:
I received notice this morning that a firmware update was ready to install. I chose to install it and the tablet rebooted and start to apply the update. However, it gets to 32% on the update install, stalls, and then reboots and does the exact same thing.
Any thoughts on a solution?
Click to expand...
Click to collapse
i have the same problm :crying:
Need more info than that.
For example... Are you rooted or stock?
If rooted, there are a couple of reasons off hand I can think of you could be having a problem.
If you're stock, well... All I can think of is wave your hands in the air, and wave them like you just don't care. Pretty sure that won't fix the problem though, but if it does, report back! xD
I'm rooted.
Sent from my DROID RAZR using xda app-developers app
exactly the same problem
I have the exact same problem.
GT-N8013, rooted, stock rom with root injected.
I called Samsung tech service and they said I should send my device to them.
The only way I can get out of this "update->reboot->update->reboot->..." infinite loop is to get into ODIN mode. (I can't turn off the device)
I decided to re-flash my rom (stock rom with root injected) in ODIN mode, but it does not have any effect and the device is still on this infinite loop. I'm worried if I messed up the device even more by doing that.
ytdong said:
I have the exact same problem.
GT-N8013, rooted, stock rom with root injected.
I called Samsung tech service and they said I should send my device to them.
The only way I can get out of this "update->reboot->update->reboot->..." infinite loop is to get into ODIN mode. (I can't turn off the device)
I decided to re-flash my rom (stock rom with root injected) in ODIN mode, but it does not have any effect and the device is still on this infinite loop. I'm worried if I messed up the device even more by doing that.
Click to expand...
Click to collapse
I'm in the same situation.
I'm going to try http://forum.xda-developers.com/showthread.php?t=1849994
when I get home tonight to see if this fixes it.
Is there any way I can at least access the internal storage somehow and copy my data?
There are some important job application info in S Note..
ytdong said:
I have the exact same problem.
GT-N8013, rooted, stock rom with root injected.
I called Samsung tech service and they said I should send my device to them.
The only way I can get out of this "update->reboot->update->reboot->..." infinite loop is to get into ODIN mode. (I can't turn off the device)
I decided to re-flash my rom (stock rom with root injected) in ODIN mode, but it does not have any effect and the device is still on this infinite loop. I'm worried if I messed up the device even more by doing that.
Click to expand...
Click to collapse
ytdong said:
Is there any way I can at least access the internal storage somehow and copy my data?
There are some important job application info in S Note..
Click to expand...
Click to collapse
you should've sync your snote data with drive or dropbox!!! any firmware update 101 is to back up all your data
ytdong said:
I have the exact same problem.
GT-N8013, rooted, stock rom with root injected.
I called Samsung tech service and they said I should send my device to them.
The only way I can get out of this "update->reboot->update->reboot->..." infinite loop is to get into ODIN mode. (I can't turn off the device)
I decided to re-flash my rom (stock rom with root injected) in ODIN mode, but it does not have any effect and the device is still on this infinite loop. I'm worried if I messed up the device even more by doing that.
Click to expand...
Click to collapse
Try using Odin to flash the high on android cwm recovery. Once I did that I could restore a backup and boot to android.
Thank you! but I've been on stock recovery so I never flashed cwm or made a cwm backup. How can I restore to a backup after I flash the cwm recovery?
Nefariouss said:
Try using Odin to flash the high on android cwm recovery. Once I did that I could restore a backup and boot to android.
Click to expand...
Click to collapse
if you've never flash CWM, that means you never backed up via CWM, which means you can't restore to a back up. You have to use ODIN and flash a stock firmware on your note to recover it
Yes I'm trying to find a stock firmware for N8013 (UEALGB) but no luck. There is only "root injected" stock firmware, which is causing the problem right now...
Has anyone resolved this problem?
khanh1289 said:
if you've never flash CWM, that means you never backed up via CWM, which means you can't restore to a back up. You have to use ODIN and flash a stock firmware on your note to recover it
Click to expand...
Click to collapse
ytdong said:
Yes I'm trying to find a stock firmware for N8013 (UEALGB) but no luck. There is only "root injected" stock firmware, which is causing the problem right now...
Has anyone resolved this problem?
Click to expand...
Click to collapse
I have a N8013 and was running the stock, root injected firmware (UEALGB). Today I got the update notification. I tried to install and it kept looping. This is what I did:
1. Flashed the stock firmware with ODIN. You'll find the stock firmware here:
http://forum.xda-developers.com/showthread.php?t=1847706
2. When my tab rebooted, I got another update notification. I installed it and it worked. I'm now running UEALI3.
I didn't lose any data. I just lost root.
This worked for me as well. Thanks a lot, Vincent9756!:good:
Vincent9756 said:
I have a N8013 and was running the stock, root injected firmware (UEALGB). Today I got the update notification. I tried to install and it kept looping. This is what I did:
1. Flashed the stock firmware with ODIN. You'll find the stock firmware here:
http://forum.xda-developers.com/showthread.php?t=1847706
2. When my tab rebooted, I got another update notification. I installed it and it worked. I'm now running UEALI3.
I didn't lose any data. I just lost root.
Click to expand...
Click to collapse
Vincent9756 said:
I have a N8013 and was running the stock, root injected firmware (UEALGB). Today I got the update notification. I tried to install and it kept looping. This is what I did:
1. Flashed the stock firmware with ODIN. You'll find the stock firmware here:
http://forum.xda-developers.com/showthread.php?t=1847706
2. When my tab rebooted, I got another update notification. I installed it and it worked. I'm now running UEALI3.
I didn't lose any data. I just lost root.
Click to expand...
Click to collapse
Worked for me. Thanks!
rrhutch said:
Worked for me. Thanks!
Click to expand...
Click to collapse
What if i didn't do Root Injected, but the Second Method of Flashing the Root.zip with CWM? which recovery do i download and flash in odin?
would that work?
Kikoshi said:
What if i didn't do Root Injected, but the Second Method of Flashing the Root.zip with CWM? which recovery do i download and flash in odin?
would that work?
Click to expand...
Click to collapse
Flash the recovery version for your firmware. If you have stock, flash the GB recovery. If you have LH2, flash that.
If you want to save root, use OTA RootKeeper before doing anything.
Z a p i x said:
Flash the recovery version for your firmware. If you have stock, flash the GB recovery. If you have LH2, flash that.
If you want to save root, use OTA RootKeeper before doing anything.
Click to expand...
Click to collapse
Im sorry but what do you mean GB Aaah that was the primary stock recovery before i updated to LH2 lol, now i get it.?The one that i have is the CWM HighonAndroid which was used for the Method 2 to obtain root, so then i jus tdownoad the stock LH2 Recovery, and use OTA rootkeeper before Odin LH2 Stock Recovery right? Will there also be a stock kernel and recovery for UEALI3 ? was thinking of possibly using the Triangle Away after this, possibly might be needed. Though maybe not.
Just want to make sure that everything is normal after this lol
ok... giving it a shot now, and using the OTA RootKeeper, lets see if this works
Everything Got updated !!! OTA seems to have worked which was awesome.
Testing everything to make sure that Root is fully funtional .
Used RootChecker, and things seems fully working!
Thank you loads for the help!
Kikoshi said:
Im sorry but what do you mean GB Aaah that was the primary stock recovery before i updated to LH2 lol, now i get it.?The one that i have is the CWM HighonAndroid which was used for the Method 2 to obtain root, so then i jus tdownoad the stock LH2 Recovery, and use OTA rootkeeper before Odin LH2 Stock Recovery right? Will there also be a stock kernel and recovery for UEALI3 ? was thinking of possibly using the Triangle Away after this, possibly might be needed. Though maybe not.
Just want to make sure that everything is normal after this lol
ok... giving it a shot now, and using the OTA RootKeeper, lets see if this works
Everything Got updated !!! OTA seems to have worked which was awesome.
Testing everything to make sure that Root is fully funtional .
Used RootChecker, and things seems fully working!
Thank you loads for the help!
Click to expand...
Click to collapse
Yeah, there will most certainly be kernel and recovery uploads.
the only issue you might run into is CWM not sticking. If it doesn't reflash CWM in ODIN with reboot unchecked. Then after you flash it, boot into CWM. When you select reboot, it should offer to prevent stock recovery from replacing it.
and you're welcome, glad to help
Guys u might think this is a dumb question but how do i flash stock recovery with odin like were do insert the file i know how tp put in dl mode and get my comp to see my tab in odin and i did flash the prerooted injected stock uealgb recovery to get root i just dont know were to put the files in odin some help would be greatly appreciated, cause i need to flash this first before i do the ota update correct ? If not i will bootloop ? So rootkeeper alows me to keep root acess after ota? Thanks guys
Sent from my GT-N8013 using xda app-developers app / jelly powered samsung infuse 4g
Hi,
I'm thinking about rooting my Note 10.1 (mostly because I want to use DicertoryBind/Link2SD) via ClockworkMod Recovery.
My questions:
I won't receive any OTA updates, cause the status will be custom, right?
I want to stay on stock FW, what can I do to update my tablet if there is a new OTA:
Can I directly flash the FW from sammobile with odin or are they not campatible with cwm? Would that mean that every time there is a new OTA, I have to unroot, flash back to stock recovery, get the OTA, flash back cwm and root again?
Isn't there a way to flash the update while keeping all my data (just like normal OTA does) and root ?
Thanks!
Kamairo said:
Hi,
I'm thinking about rooting my Note 10.1 (mostly because I want to use DicertoryBind/Link2SD) via ClockworkMod Recovery.
My questions:
I won't receive any OTA updates, cause the status will be custom, right?
Yes
I want to stay on stock FW, what can I do to update my tablet if there is a new OTA:
Can I directly flash the FW from sammobile with odin or are they not campatible with cwm? Would that mean that every time there is a new OTA, I have to unroot, flash back to stock recovery, get the OTA, flash back cwm and root again?
You can flash using ODIN, but you will need to re root the device, also chances are you will not lose data but in rare cases you will need to do a factory reset which will mean you lose all your data.
Isn't there a way to flash the update while keeping all my data (just like normal OTA does) and root ?
Above answer should answer this also but you will need to re-root the device
Thanks!
Click to expand...
Click to collapse
Hope this answers all queries
You can flash using ODIN, but you will need to re root the device, also chances are you will not lose data but in rare cases you will need to do a factory reset which will mean you lose all your data.
Click to expand...
Click to collapse
Okay, that means I download the firmware from for instance sammobile, flash it using ODIN (will that be PDA only, like flashing cwm?), and then re root means install superSU again from cwm or installing cwm completely new?
*edit* Thanks for the sticky!
Yes you can use this post to know how to install using odin http://forum.xda-developers.com/showthread.php?t=2080366
You do not require CWM to root you can use the exynos patch apk to root you can download the apk from here
http://forum.xda-developers.com/showthread.php?t=2050297
samir_a said:
Yes you can use this post to know how to install using odin http://forum.xda-developers.com/showthread.php?t=2080366
You do not require CWM to root you can use the exynos patch apk to root you can download the apk from here
http://forum.xda-developers.com/showthread.php?t=2050297
Click to expand...
Click to collapse
Hey, thanks so far, I just installed CWM, everything went fine, but if I look at the system status it still says "offical", does that mean I can receive OTA's? Or won't that work cause of CWM?
Also I believe before it didn't say "official" but "normal".
*edit* okay, nevermind, after a reboot it sys now "custom"
Since you have rooted your device you can also use Mobile ODIN to flash the roms from sammfirmware directly on your note 10.1. You just make sure everroot is ticked but if you think you might loose root then have both the CWM.tar file saved on your device, its a tiny file so no real space lost or if you don't care about CWM but want root access then keep the exynosexploit.apk on your device. I have everything I need on the sd card in case I cant get to a PC. Much better when I'm not tied to the PC...
ultramag69 said:
Since you have rooted your device you can also use Mobile ODIN to flash the roms from sammfirmware directly on your note 10.1. You just make sure everroot is ticked but if you think you might loose root then have both the CWM.tar file saved on your device, its a tiny file so no real space lost or if you don't care about CWM but want root access then keep the exynosexploit.apk on your device. I have everything I need on the sd card in case I cant get to a PC. Much better when I'm not tied to the PC...
Click to expand...
Click to collapse
Thanks so far, but theres one question left: From what you've said I think it's possible to flash with odin or mobile odin while CWM is still installed, what will happen to CWM after the flash? Is it completely gone (stock recovery comes with the firmware?!) or does "re root" only mean that I have to reinstall superSU with CWM?
You will go back to stock recovery but you might retain root if you ticked everoot function....
As I said earlier, you can reflash CWM onto your Note using mobile ODIN if you have the CWM.tar file stored on your device...
+1 for Mobile Odin if you're wanting to stay stock.
Use Exynos Abuse to root the first time.
Install Mobile Odin pro.
Backup your EFS partition off the device.
Install CWM using Mobile Odin and make a nandroid backup.
Back up apps with Titanium if required.
Download the new stock from you want and use Mobile Odin to install with Everoot selected.
Use Mobile Odin to install CWM.
Simplest method I've found by far.
Sent from my GT-N7100 using xda premium
After rooting with exynos abuse root, can you just do a factory reset to make you stock again to get OTA's?
I don't believe so (prepared to be corrected) but if you reinstall the stock rom without Everoot ticked and factory reset you'll be back to stock unmodified.
Sent from my GT-N7100 using xda premium
Never tried but I don't think so, The OTA checks for an unmodified system and even though stock recovery says its official the status in settings is "Custom".
What if I'm on the stock rom (never went custom) and stock recovery. All I did was root? Would a recovery restore allow me to get OTA's?
if you are on stock recovery then why would you restore recovery.
Yes if you are rooted only you will receive OTA if you are on the orignal rom (rom from country which note was purchased irrespective of the version you are on)
samir_a said:
if you are on stock recovery then why would you restore recovery.
Yes if you are rooted only you will receive OTA if you are on the orignal rom (rom from country which note was purchased irrespective of the version you are on)
Click to expand...
Click to collapse
That is my situation, exactly. So, I can take OTAs in my present situation? I used #2 root option from zedomax. I haven't changed anything or used a custom rom. All I want to do is get current on my updates, and retain root and CWM.
Should I also use TriangleAway, and at what point? Thank you.
Apologies to the OP, but I've been waiting for a chance to resolve this.
If you used method 2 you have replaced the stock recovery... That's what CWM recovery means...
You're flash counter will now be one and need to be reset using triangle away. No OTA for you...
ultramag69 said:
If you used method 2 you have replaced the stock recovery... That's what CWM recovery means...
You're flash counter will now be one and need to be reset using triangle away. No OTA for you...
Click to expand...
Click to collapse
Thank you.
Hello there.
I am running a stock, rooted, most recent TW 4.1.2. I had TWRP recovery and from what I remember, unlocked the bootloader.
After trying difference ROMS both TW and AOSP based, I decided that I would stick with the stock ROM, but rooted to add functionality, especially WIFI tethering.
I would like to get to Stock Rooted 4.3 TW so that I can (hopefully) use tethering. I attempted to take the OTA after flashing a stock recovery image, but the install failed.
I have several questions I hope the members here can assist me with:
1. Do you have to lock the bootloader prior to taking the OTA? I do realize that there is no way to unlock the bootloader on 4.3 as of the moment.
2. Is there a consensus that it is possible to root after taking the OTA via Safe Strap? I have been doing some reading on the forums, and some members indicate that it has worked for them.
3. Has anybody been able to get tethering to work after taking the OTA and rooting?
Thanks in advance! Happy holidays...
banditsw said:
Hello there.
I am running a stock, rooted, most recent TW 4.1.2. I had TWRP recovery and from what I remember, unlocked the bootloader.
After trying difference ROMS both TW and AOSP based, I decided that I would stick with the stock ROM, but rooted to add functionality, especially WIFI tethering.
I would like to get to Stock Rooted 4.3 TW so that I can (hopefully) use tethering. I attempted to take the OTA after flashing a stock recovery image, but the install failed.
I have several questions I hope the members here can assist me with:
1. Do you have to lock the bootloader prior to taking the OTA? I do realize that there is no way to unlock the bootloader on 4.3 as of the moment.
2. Is there a consensus that it is possible to root after taking the OTA via Safe Strap? I have been doing some reading on the forums, and some members indicate that it has worked for them.
3. Has anybody been able to get tethering to work after taking the OTA and rooting?
Thanks in advance! Happy holidays...
Click to expand...
Click to collapse
Lock the bootloader using ez lock 1.2
Best bet is a clean Odin flash and use this NO WIPE file MB1 image #1 http://forum.xda-developers.com/showthread.php?t=1974114 then do system update to MF1 and then again for 4.3
Saferoot works (I'm currently using it without any issues) http://forum.xda-developers.com/showthread.php?t=2565758
I'm on share everything plan so tethering is included
But just remember, if you do OTA the 4.3 your phone will be locked down with NO chance of ever installing a custom recovery or unlocking the bootloader and no more custom ROMs
Hope this helps
yepyep14u2know said:
Lock the bootloader using ez lock 1.2
Best bet is a clean Odin flash and use this NO WIPE file MB1 image #1 http://forum.xda-developers.com/showthread.php?t=1974114 then do system update to MF1 and then again for 4.3
Saferoot works (I'm currently using it without any issues) http://forum.xda-developers.com/showthread.php?t=2565758
I'm on share everything plan so tethering is included
But just remember, if you do OTA the 4.3 your phone will be locked down with NO chance of ever installing a custom recovery or unlocking the bootloader and no more custom ROMs
Hope this helps
Click to expand...
Click to collapse
Thanks for the reply. I tried to take the OTA update after flashing the stock recovery via EZ-Recovery app, and locking the bootloader via EZ-lock 1.2 per your advice, but the install failed. Did you ODIN back to stock?
I guess I will ODIN flash the image you reference, and do the OTA update that way. I used to flash all sorts of ROMS, but at this point, I just want a fully functioning rom. The developers do amazing work, that being said.
Thanks again.
banditsw said:
Thanks for the reply. I tried to take the OTA update after flashing the stock recovery via EZ-Recovery app, and locking the bootloader via EZ-lock 1.2 per your advice, but the install failed. Did you ODIN back to stock?
I guess I will ODIN flash the image you reference, and do the OTA update that way. I used to flash all sorts of ROMS, but at this point, I just want a fully functioning rom. The developers do amazing work, that being said.
Thanks again.
Click to expand...
Click to collapse
Yeah I had the same problems you're encountering. Those are the steps I took, so just follow those steps and ODIN MB1 no wipe, then system update to MF1 and then system update again to ML1, and you'll keep all your settings, contacts, apps, etc.
banditsw said:
Thanks for the reply. I tried to take the OTA update after flashing the stock recovery via EZ-Recovery app, and locking the bootloader via EZ-lock 1.2 per your advice, but the install failed. Did you ODIN back to stock?
I guess I will ODIN flash the image you reference, and do the OTA update that way. I used to flash all sorts of ROMS, but at this point, I just want a fully functioning rom. The developers do amazing work, that being said.
Thanks again.
Click to expand...
Click to collapse
Just be warned, that once you take the 4.3 OTA, you cannot ever, never go back or flash custom ROMs. you are stuck there.
DigitalMD said:
Just be warned, that once you take the 4.3 OTA, you cannot ever, never go back or flash custom ROMs. you are stuck there.
Click to expand...
Click to collapse
You can't say that for sure. All you can say that there is a 99.999999999% chance that you will never be able to unlock your bootloader again.
Running a custom ROM/recovery would be attainable with a locked bootloader with something like safestrap.
DigitalMD said:
Just be warned, that once you take the 4.3 OTA, you cannot ever, never go back or flash custom ROMs. you are stuck there.
Click to expand...
Click to collapse
I appreciate that fact. Maybe it will be a good thing, because I was a flashaholic. Maybe it will force me to do other things other than flash ROMS LOL.
banditsw said:
I appreciate that fact. Maybe it will be a good thing, because I was a flashaholic. Maybe it will force me to do other things other than flash ROMS LOL.
Click to expand...
Click to collapse
Well don't even try after the update or else you will be like me with a hopefully temporary bricked phone.
yepyep14u2know said:
Lock the bootloader using ez lock 1.2
Best bet is a clean Odin flash and use this NO WIPE file MB1 image #1 http://forum.xda-developers.com/showthread.php?t=1974114 then do system update to MF1 and then again for 4.3
Saferoot works (I'm currently using it without any issues) http://forum.xda-developers.com/showthread.php?t=2565758
I'm on share everything plan so tethering is included
But just remember, if you do OTA the 4.3 your phone will be locked down with NO chance of ever installing a custom recovery or unlocking the bootloader and no more custom ROMs
Hope this helps
Click to expand...
Click to collapse
I have tried downloading the MB1 image since this morning....having problems with downloading it...anyone have the file to download? Thanks.
EDIT: I guess the server had issues yesterday. Was able to download last night.
How do you unroot the GS3 and get back to stock unrooted? I am currently just stock rooted. I'm just done with flashing and don't want to worry about something happening to my phone while I'm rooted, and am sick of it not being able to take the VZW update on a daily basis. I understand there is an unroot in the superuser app, is it as simple as clicking that and it will unroot by itself? Is there more I need to do? Thanks for your help!
Bump
Many ways to unroot, you could use SuperSU and select remove root, then uninstall the app then reboot or use universal unroot app from play store.
buhohitr said:
Many ways to unroot, you could use SuperSU and select remove root, then uninstall the app then reboot or use universal unroot app from play store.
Click to expand...
Click to collapse
Thank you. Once you perform either or these methods, can you still root again in the future if you decide to?
I unrooted through SuperSU. Went to install the VZW update and it went into Teamwin Recovery. When it was trying to update the software and running all the checks, etc. I saw "checking for MD5 file...no MD5 file found." What is this and is this what is causing me to not be able to take the update? Am I supposed to still have Teamwin Recovery? How do I get rid of it? Root Checker said I'm unrooted now.
Where do I go from here? Thanks again!
Bump
irl5fan said:
Bump
Click to expand...
Click to collapse
Flash this file:
http://forum.xda-developers.com/showthread.php?t=2795659
With this guide:
http://forum.xda-developers.com/showthread.php?t=2586319
Then you're unrooted and up to date, but you'll erase all of your data. So backup all the pictures and music you want to keep.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Flash this file:
http://forum.xda-developers.com/showthread.php?t=2795659
With this guide:
http://forum.xda-developers.com/showthread.php?t=2586319
Then you're unrooted and up to date, but you'll erase all of your data. So backup all the pictures and music you want to keep.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
None of the links to the files have anything in them. Is there another way? Any other location to find these files?
irl5fan said:
None of the links to the files have anything in them. Is there another way? Any other location to find these files?
Click to expand...
Click to collapse
You're right, try to search for it in Google. I didn't bookmark anything.
Sent from my HTC6525LVW using Tapatalk
irl5fan said:
I unrooted through SuperSU. Went to install the VZW update and it went into Teamwin Recovery. When it was trying to update the software and running all the checks, etc. I saw "checking for MD5 file...no MD5 file found." What is this and is this what is causing me to not be able to take the update? Am I supposed to still have Teamwin Recovery? How do I get rid of it? Root Checker said I'm unrooted now.
Where do I go from here? Thanks again!
Click to expand...
Click to collapse
Dude.... You shouldn't be rooting if you don't know what TWRP is.... LMAO!
You need to flash stock recovery to take the OTA, you should of backed it up when you first flashed TeamWin to the device and it would of been a simple reflash through Flashify and it would of been good.
Now you need to download Odin (A PC flash tool) and reflash through that programme....
Sent From V500
Using XDA App
unroot gs3
LiamAtkins90 said:
Dude.... You shouldn't be rooting if you don't know what TWRP is.... LMAO!
You need to flash stock recovery to take the OTA, you should of backed it up when you first flashed TeamWin to the device and it would of been a simple reflash through Flashify and it would of been good.
Now you need to download Odin (A PC flash tool) and reflash through that programme....
When did I say I didn't know what TWRP is? So if I flash stock recovery will that get me where I want to be...stock unrooted and able to take OTA updates. I never did flash any custom roms or anything while I was rooted.
Click to expand...
Click to collapse
irl5fan said:
When did I say I didn't know what TWRP is? So if I flash stock recovery will that get me where I want to be...stock unrooted and able to take OTA updates. I never did flash any custom roms or anything while I was rooted.
Click to expand...
Click to collapse
Sorry, I realise my reply come of a little arsey, I will explain.
If you take the OTA in stock recovery it will go through, but as soon as you flash a custom recovery you give up the right to an OTA whilst on said recovery,
Instead you either:
1. Flash a custom ROM, and do updates with there ROM team.
2. Wait for stock ROM to come in a flashable zip for Custom Recoverys.
If you have root and stock recovery and take it, sometime it will go through, sometimes it won't.... Like Samsung Knox for example....
Sometimes it will take but as soon as you boot back up you will have no root.
If you OTA in Custom Recovery it will boot to TWRP and most likely abort straight away and bad things will ocure.
Mixed Partitions no ROM etc...
Now back to your question....
Yeah Stock non rooted you can take OTA (but in Samsung's case, they have a flash counter, that keeps track of system mods)
Best bet would be flash through Odin, to out-the-box firmware and take the OTA from there...to avoid any conflicts with the system.
I do apologise for my earlier post mate, write back if you got it upgraded.
LiamAtkins90 said:
Sorry, I realise my reply come of a little arsey, I will explain.
If you take the OTA in stock recovery it will go through, but as soon as you flash a custom recovery you give up the right to an OTA whilst on said recovery,
Instead you either:
1. Flash a custom ROM, and do updates with there ROM team.
2. Wait for stock ROM to come in a flashable zip for Custom Recoverys.
If you have root and stock recovery and take it, sometime it will go through, sometimes it won't.... Like Samsung Knox for example....
Sometimes it will take but as soon as you boot back up you will have no root.
If you OTA in Custom Recovery it will boot to TWRP and most likely abort straight away and bad things will ocure.
Mixed Partitions no ROM etc...
Now back to your question....
Yeah Stock non rooted you can take OTA (but in Samsung's case, they have a flash counter, that keeps track of system mods)
Best bet would be flash through Odin, to out-the-box firmware and take the OTA from there...to avoid any conflicts with the system.
I do apologise for my earlier post mate, write back if you got it upgraded.
Click to expand...
Click to collapse
No problem. This has been a long drawn out process over the past few months, so forgive me for all the questions and details of events. This is where I'm at. When I started the unrooting process, as stated above, used triangle away to reset the counter and then I unrooted through SuperSU. According to root checker apps I am unrooted, but I believe my bootloader is still unlocked. And obviously still have TWRP. Phone Info: SCH-I535, Version 4.1.2, Baseband I535VRBMF1.
Given that info, do I still flash the stock firmware (from here?--->) (http://downloadandroidfiles.org/download-sch-i535-vzw-i535vrbmb1-1360821900-zip/) and then flash stock recovery? Does flashing stock firmware re-lock my bootloader? Thanks for your help.
irl5fan said:
No problem. This has been a long drawn out process over the past few months, so forgive me for all the questions and details of events. This is where I'm at. When I started the unrooting process, as stated above, used triangle away to reset the counter and then I unrooted through SuperSU. According to root checker apps I am unrooted, but I believe my bootloader is still unlocked. And obviously still have TWRP. Phone Info: SCH-I535, Version 4.1.2, Baseband I535VRBMF1.
Given that info, do I still flash the stock firmware (from here?--->) (http://downloadandroidfiles.org/download-sch-i535-vzw-i535vrbmb1-1360821900-zip/) and then flash stock recovery? Does flashing stock firmware re-lock my bootloader? Thanks for your help.
Click to expand...
Click to collapse
So you used Triangle Away to clear the flash counter?
Great, so the only thing you need now is the stock recovery image for your device,
I would say just flash the stock recovery image through Odin, but their is that many models
with different numbers, it would be easier flashing 4.1.2 firmware again through Odin.
In future bud if your gonna be messing with ROMs and Recovery files I recommend this:
Flash recovery with this:
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB
(Backup Stock Recovery 1st)
Backup Stock EVERYTHING, Boot, System, EFS, Data etc in Recovery of choice.
Move backup to computer or cloud storage.
Then all you need to do to go back is triangle away, restore stock backup, restore stock recovery, unroot through SuperSU.
And the OTA should work.
Sent From V500
Using XDA App
LiamAtkins90 said:
So you used Triangle Away to clear the flash counter?
Great, so the only thing you need now is the stock recovery image for your device,
I would say just flash the stock recovery image through Odin, but their is that many models
with different numbers, it would be easier flashing 4.1.2 firmware again through Odin.
In future bud if your gonna be messing with ROMs and Recovery files I recommend this:
Flash recovery with this:
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB
(Backup Stock Recovery 1st)
Backup Stock EVERYTHING, Boot, System, EFS, Data etc in Recovery of choice.
Move backup to computer or cloud storage.
Then all you need to do to go back is triangle away, restore stock backup, restore stock recovery, unroot through SuperSU.
And the OTA should work.
Sent From V500
Using XDA App
Click to expand...
Click to collapse
I just want to clarify before I go ahead and do anything and get myself into a pickle. Are you saying to flash 4.1.2 firmware instead of stock recovery? Or am I still flashing both of them? If so, which order? Does that link I posted look like it is the correct firmware to you? Also, I have an older version of Odin on my computer, does that matter or should I get the newer one first?
irl5fan said:
I just want to clarify before I go ahead and do anything and get myself into a pickle. Are you saying to flash 4.1.2 firmware instead of stock recovery? Or am I still flashing both of them? If so, which order? Does that link I posted look like it is the correct firmware to you? Also, I have an older version of Odin on my computer, does that matter or should I get the newer one first?
Click to expand...
Click to collapse
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
My model number is SCH-I535. I have used Odin before, but I'll take a look at the guide just to make sure. Thanks for your help!
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
I just wanted to say thanks for helping out someone in our forums with the VZW variant, I was going to chime in but I see you had things under control. It's just odd to see so many people in our forums who don't have the version we have
From my Wicked S3 on SOKP
ShapesBlue said:
I just wanted to say thanks for helping out someone in our forums with the VZW variant, I was going to chime in but I see you had things under control. It's just odd to see so many people in our forums who don't have the version we have
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
No problem, glad I can help.
Verizon edition Models tend to get overlooked as oppose to International variants which is a shame, I think both should get equal recognition. Not just Sammy Verizon, most Verizon models and also Google Play Edition Model Phones/Tablets get pushed aside.... Crying shame.
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
Everything worked out great, flashed the stock firmware and was able to take the OTA. Thank you so much for your help, it's greatly appreciated!
FAQ section in the 2nd post.
BEWARE OF EVERYTHING! I AM NOT RESPONSIBLE if your phone implodes, aliens take over Mars, don trump starts WW3 and WW4, or your dish washer starts working again from using this guide. Remember: just because it worked for me, does not mean it will work for you, but it might! I recommend having an ODIN copy (.tar file) of the MDL bootloader so in case anything goes south, you can get back to stock and start over from scratch.
IMPORTANT! This guide will show you how to (easily) maneuver around the At&t sgh-i337 on the MDL bootloader as far as root and other things are concerned. This guide is NOT for any other bootloader! Once you have updated past jelly bean 4.2.2 then you will not be able to use this guide!
Now for the good stuff...
So you've just taken your new At&t GS4 out of the box and discovered that you're on the MDL bootloader (like I did)! First you're going to want to root it. You can do this by grabbing a good 'ol copy of towel root (just search the forums here or Google for it). Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you.
Next you may want to install a custom recovery. To do this, you will need to use an exploit file called Loki Doki. Follow this video to take the needed steps to get loki'ed and a recovery installed: https://www.youtube.com/watch?v=VmkL9atpVHw
Yes, I know it installs CWM which is way out of date, if you want to use TWRP go ahead. However, this guide deals with CWM so if you use TWRP you're using it at your own risk and going against the guide! GO WITH THE GUIDE!
However, if you want to update to TWRP recovery then this video by the same guy as in the last video should do it: https://galaxys4root.com/galaxy-s4-...or-verizon-galaxy-s4-with-twrp-v-2-8-4-0/amp/
Once you've got loki lurking around your phone's memory, you're good to install a custom ROM! TA-DA! Awesome how all that worked out isn't it?
How to install a custom (TW) ROM
If and only if you followed the ZedoMax video, you should now have OUDhs CWM Touch Req0very v1.0.3.4 installed. Now would be a great time to boot into it so power off your phone then hold power, home, and volume up at the same time. Hold it! Hold it! Hold it! Release when you see the CWM menu. Now let's Nandroid this hush puppy!
Goto backup and restore and hit backup. It will most likely save it to your internal memory, but you can copy it to SD card later, or just reboot now and move it. We now have a working backup in case your dog eats your homework. After that's done, make sure the ROM .zip file you are going to boot is on your SD card. Now go to wipe cache partition and select yes. Go to Advanced and wipe dalvik cache. Go to wipe data/factory reset and select yes. Goto mounts and storage and select format cache, then select format /system.
NOTE: If you want to keep all your personal data (pics, videos, etc.) then stop here! If you want to completely nuke your phone and start from scratch then select format /data from the mounts and storage menu.
Once you've formatted /system (or did a complete wipe by formatting /data too so now you have nothing), you're ready to install a ROM. Select install zip from SD card from the main menu. Find your ROM .zip file and select it. I used the latest GoldenEye ROM because it has an Aroma installer built in so it pretty much does everything for you once you tell it what you want. Easy!
ROM should now be installed and everything should work ok once your phone reboots out of CWM recovery.
How to boot a custom (AOSP/CM) ROM
WARNING! THIS IS EXPERIMENTAL! Following this may get your ROM booted or not. Do so at your phone's own risk! You could erase stuff on accident!
Place the ROM file on your SD card. Boot into recovery and select wipe cache partition. Then select wipe dalvik cache. Now select wipe data/factory reset. Once all that's done, you will need to format /system and /data. Now goto install .zip from SD card. Select your ROM file and pray to whatever higher power yourbelieve in that it worked. Next you're going to (maybe) need a kernel.
Kernels and Modems
Download a compatible kernel for the ROM you want to use. Boot into recovery and flash the .zip file for the kernel from your internal memory or external SD card. Be sure if you are booting a TW ROM that you use a TW kernel. Same goes for CM and AOSP.
Modems are pretty much universal on the MDL firmware and possibly on others as well. To flash a modem just select the .zip file and flash in recovery from your SD card or internal memory. You can use any baseband modem...MDB, MK3, NB1, OC3, etc.
FAQ Section
What is the MDL bootloader? It's the jelly bean 4.2.2 firmware for the at&t galaxy s4. It's a locked bootloader, however it has a flaw in it that can be exploited by Loki Doki to allow a custom recovery to be installed.
What is Loki Doki? It's something that exploits the flaw in the MDL bootloader allowing you to do things an unlocked bootloader can do. To my best of knowledge, it acts similar to a PlayStation modchip by tricking the bootloader into thinking that whatever you feed it, is authorized to boot.
Can I downgrade my bootloader to MDL if I took the OTA? Only if you're a Samsung or at&t smartphone hardware tech.
Why can't I use Loki on other bootloaders? Because the flaw that loki exploited was patched in the MF3 firmware. With the exception of the MDB bootloader which was the bootloader before MDL.
Do I need motochopper to root my at&t s4? Nope, towel root works just fine to get root on the MDL bootloader.
Why does OUDhs CWM recovery tell me root or recovery may be lost on reboot and want to fix it? I have no idea, I think it's a bug. Just select "go back" until your phone reboots and all should be fine.
Why does your guide say "experimental" for AOSP or CM based ROMs? Mainly because I haven't messed around with any and am basing on how to boot them off my time using the galaxy s2.
Why can't I use TWRP recovery instead of CWM? You can, as I pasted a link to get TWRP installed in my guide. It's just I based my guide around CWM because that's what I have always used. Do note that TWRP is different, so you'll have to figure out how to wipe and install the ROM property.
What's the difference between CWM recovery and TWRP recovery? Nothing really, except the UI and how they handle files and things. Due note that CWM recovery has been discontinued, while TWRP still thrives today with updates.
So I am on MDL and have OctOS 7.1.1 flashed but no root. I have tried towelroot with no success. I do however have TWRP 3.0 on my phone but SuperSU won't flash. Do you have any ideas?
Tubifex said:
So I am on MDL and have OctOS 7.1.1 flashed but no root. I have tried towelroot with no success. I do however have TWRP 3.0 on my phone but SuperSU won't flash. Do you have any ideas?
Click to expand...
Click to collapse
OctOS has root disabled by default. You have to flash a root .zip file to activate root. Make sure you are loki'ed and that you have the right TWRP version as well as the right root .zip for your phone. Towel root only works on stock Android jelly bean 4.2.2, 4.3, and kit kat 4.4.2
StoneyJSG said:
OctOS has root disabled by default. You have to flash a root .zip file to activate root. Make sure you are loki'ed and that you have the right TWRP version as well as the right root .zip for your phone. Towel root only works on stock Android jelly bean 4.2.2, 4.3, and kit kat 4.4.2
Click to expand...
Click to collapse
Where do you suggest I find root.zip file?
Tubifex said:
Where do you suggest I find root.zip file?
Click to expand...
Click to collapse
I am not too sure, I haven't messed with OctOs at all. Try here:
https://forum.xda-developers.com/galaxy-s4-att/orig-development/rom-team-octos-oct-n-t3532663
Someone there in that thread will probably know.
Finished! This guide is done!
Bump....happy flashing!
Does this APK work anymore? It will not download to my phone. I had to download it to my pc then transfer it via usb to my phone. When I go to install it I get an error saying There is a problem parsing the package.
Can anyone please provide the ATT-I337UCUAMDL-20130430103714.zip file? All the mirrors are dead
NVMD,found something similar here:
https://androidfilehost.com/?fid=23203820527944165
and here:
https://server.samsung-firmware.org...de28764422/ATT-I337UCUAMDL-20130430103714.zip
jabulon said:
Can anyone please provide the ATT-I337UCUAMDL-20130430103714.zip file? All the mirrors are dead
NVMD,found something similar here:
https://androidfilehost.com/?fid=23203820527944165
and here:
https://server.samsung-firmware.org...de28764422/ATT-I337UCUAMDL-20130430103714.zip
Click to expand...
Click to collapse
You are needing the MDL ODIN .tar / zip file correct?
7ravler said:
Does this APK work anymore? It will not download to my phone. I had to download it to my pc then transfer it via usb to my phone. When I go to install it I get an error saying There is a problem parsing the package.
Click to expand...
Click to collapse
Which APK file are you referring to? Towel root or something else?
StoneyJSG said:
You are needing the MDL ODIN .tar / zip file correct?
Click to expand...
Click to collapse
yep, but I've already found it
Thank you!
jabulon said:
yep, but I've already found it
Thank you!
Click to expand...
Click to collapse
Hi,
I'm trying to find a way to install MDL to be able to get past my att bootloader lock. I have everything except the MDL Odin file. Can you please tell me the link to get it. I'm new on the site sorry if Im in the wrong section. I want to be able to install custom rom on my SAMSUNG-SGH-I337 Att. I have already downgraded all the way to NB1 and rooted and updated all the way back to OK2 without losing Root access. I went ahead and reflashed stock for fun however to see if I could do it. It worked. So now I'm unrooted back on OK3 official via OTA. I just tricked the time on the phone, changed the date, to bypass ATT's stupid ota 24 hour update wait period inbetween updates. . So I have no issue experimenting because I have the way to downgrade all the way back to NB1 no problem with Odin and then Ota update back to OC3 then OK2, Ok3 ext. Ext. So I just need to get to MDL so I can use loki from what I have read. I'mean only able to get to NB1 basically due to lack of .tar/Odin file for the exploitable mdl bootloader.
So if I can get the Odin file or zip to MDL I will know what to do.. Thank you ahead of time for all your hard work! This post is amazing.
-Scott
(Hopefully I did this right lol)
Scottie32583 said:
Hi,
I'm trying to find a way to install MDL to be able to get past my att bootloader lock. I have everything except the MDL Odin file. Can you please tell me the link to get it. I'm new on the site sorry if Im in the wrong section. I want to be able to install custom rom on my SAMSUNG-SGH-I337 Att. I have already downgraded all the way to NB1 and rooted and updated all the way back to OK2 without losing Root access. I went ahead and reflashed stock for fun however to see if I could do it. It worked. So now I'm unrooted back on OK3 official via OTA. I just tricked the time on the phone, changed the date, to bypass ATT's stupid ota 24 hour update wait period inbetween updates. . So I have no issue experimenting because I have the way to downgrade all the way back to NB1 no problem with Odin and then Ota update back to OC3 then OK2, Ok3 ext. Ext. So I just need to get to MDL so I can use loki from what I have read. I'mean only able to get to NB1 basically due to lack of .tar/Odin file for the exploitable mdl bootloader.
So if I can get the Odin file or zip to MDL I will know what to do.. Thank you ahead of time for all your hard work! This post is amazing.
-Scott
(Hopefully I did this right lol)
Click to expand...
Click to collapse
Once your phone has been updated past MDL, you cannot go back. NB1 is the farthest back you can go without bricking. You are stuck with safe strap recovery for kit kat and flash fire for lollipop. You can only boot custom touchwiz ROMs.
Thank you so much!! You saved me a lot of time with this information. I can quit trying to find a way to go back. I will stick with flash fire and safestrap.
Scott
No problem. Be careful as safe strap works only with kit kat to my knowledge. If you're on NB1 I think that's kit kat. Flash fire works with lollipop as safe strap doesn't. Flash fire may also work under kit kat, but I am not sure.
StoneyJSG said:
Which APK file are you referring to? Towel root or something else?
Click to expand...
Click to collapse
Sorry to leave you hanging here. I was referring to towel root and I did find a good file. Thanks. I see you posted that I cannot go back to mdl after updating to OC3? Bummer! I should have researched a little more before I did that
Nope, once you update past MDL which is MK3 I believe it patches the loki doki exploit so it can't be used and also makes it so if you try to downgrade back to MDL you can brick the phone.
good guide.
err on the side of kindness