Related
i flashed EP4P stock, deodexed, debloated and rooted and all was good for a couple of weeks. 2 days ago i was able to use barnacle but i went to use it today and it says i do not have root privliges so i wnet to superuser to check for an update and it says i do not have root. tried restarting phone and thats about it. anyone know why this happened and how i can fix it?
I think the easiest thing to do would be to reflash the rom. Is it an ODIN only flash or do they have a CWM flash posted as well?
nailem said:
i flashed EP4P stock, deodexed, debloated and rooted and all was good for a couple of weeks. 2 days ago i was able to use barnacle but i went to use it today and it says i do not have root privliges so i wnet to superuser to check for an update and it says i do not have root. tried restarting phone and thats about it. anyone know why this happened and how i can fix it?
Click to expand...
Click to collapse
http://androidsu.com/superuser/
Flash this in your recovery.
thank you for the quick replies.
i am new to roots and have only used odin twice.
i really hate to reflash with odin only because it is a pain to get everything back to how i want it. but if i have to i will.
i have never user CWM. so i will do some searches for how to unless you can point me in the right direction.
i assume i need to flash the superuser into the recovery with CWM????
i do have superuser that showed up after i flashed 2.3.6 and i tried reinstalling it and still the same thing
nailem said:
thank you for the quick replies.
i am new to roots and have only used odin twice.
i really hate to reflash with odin only because it is a pain to get everything back to how i want it. but if i have to i will.
i have never user CWM. so i will do some searches for how to unless you can point me in the right direction.
i assume i need to flash the superuser into the recovery with CWM????
i do have superuser that showed up after i flashed 2.3.6 and i tried reinstalling it and still the same thing
Click to expand...
Click to collapse
you have to use Odin to flash CWM, then immediately boot into CWM after and flash that superuser.zip file... if still nothing download/update it from the market
sent from my Acer Iconia A500 tablet via XDA app
thanks used CWM to flash .zip and it worked
i get an error when trying to flash the .zip file
something about the file is incorrect
i can flash it again and post the exact error if it helps
bibntziu said:
i get an error when trying to flash the .zip file
something about the file is incorrect
i can flash it again and post the exact error if it helps
Click to expand...
Click to collapse
it was probably a bad download, redownload and try flashing again
I am completely new to rooting. I tried to use super one click on my charge after it was updated to 2.3.6 and it failed, so from what I understand, one click methods are out for now. I want to root my phone still, so where would I start? And would that method involve me having to do a factory reset? Thank you
How to root your Droid Charge
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.
Hi everyone,
Now I know I'm not alone on this because I've seen quite a few other questions about this and I haven't really seen any straight forward answers about this same problem.
Anyways I own the N8013 and like many I couldn't wait for the US version of 4.1 so I flashed the german n8010 version. No problems there, Ive been using it fine. However I always intended to go back to stock,and for the most part I have. I got back on the n8013 ics, reset the flash counter and all that so I am no longer custom and it says I haven't flashed anything. Downloaded the 4.1 OTA update, checked to make sure I wasn't rooted, I'm not, so almost everything is perfect. The only problem I have left is that SuperSU is on the device and I cant uninstall it.
Now I heard something about rooting to uninstall it but Im confused because if I root then remove it how do I unroot? Also Im worried that this will somehow affect my flash counter and official status. Anyways I'd really appreciate some help on this, I know there are others like me who could benefit from maybe a simple step by step process of getting SuperSU off and getting to unmodified, stock, unroot status. I have a physical defect with my device and even though I've heard samsung is lenient id like to not take any chances.
Again I'd really appreciate any help people have to offer, thanks for reading.
Root, run triangle away to reset counter. Go to supersu and find in settings the unroot and remove supersu setting. It will remove super su and unroot. You may need to reflash the stock recovery or stock rom again via ODIN. Stock recovery is only a few seconds, stock rom about 4 - 5 mins.... Your choice....
Should be completely stock now...
ultramag69 said:
Root, run triangle away to reset counter. Go to supersu and find in settings the unroot and remove supersu setting. It will remove super su and unroot. You may need to reflash the stock recovery or stock rom again via ODIN. Stock recovery is only a few seconds, stock rom about 4 - 5 mins.... Your choice....
Should be completely stock now...
Click to expand...
Click to collapse
Well I already rooted and reset the counter, the problem is I can't find any setting in SuperSu to remove itself. I found the unroot which I ran but I dont know where to remove SuperSU, maybe I'm missing it? Or do I need to re root and follow these steps again? Or do I just flash stock again? Also if I flash stock through ODIN will that affect my counter? Sorry If I'm just missing it, I really appreciate your help.
Via recovery format system cache data and sd card and nothing is on the phone .
Boot to download mode and flash stock rom via Odin .
jje
No, flashing a stock rom through ODIN won't raise flash counter..
I'm really confused about something and before I get flamed for not searching before posting, let me preface by saying that I have and still can't find a definitive answer given that nobody seems to reference the problem I'm having - at least it doesn't show up in my attempts to search.
My Question: Once I'm rooted, what is the process for accepting an OTAs (over the air updates) from Verizon? Whenever I download and install them, I get the "Custom" Lock Icon during bootup.
Here are the steps I've followed:
1. Flashed back to stock 4.1.1
2. Flashed the VRALEC bootchain
3. Flashed CWMR
4. Booted into CWMR recovery and ran the SuperSU_Bootloader_FIXED.zip (Note: no message appeared asking me about locking
5. Flashed the 4.1.1 bootchain
6. Downloaded and it auto rebooted to install the OTA (I wanted to see what it's like the NEXT time verizon pushes out an OTA so I know what the process is once all my apps are installed)
7. When finished applying the update it asks me: A. Do I want to Disable recovery flash? and B. Do I want to preserve root?
At first I tried answering both questions with yes and yes since I saw the message about that here: http://forum.xda-developers.com/showthread.php?t=2046439
My Problem: As soon as I rebooted, I get the custom lock icon message during bootup. So then I repeated the entire process and answered No and No to those questions. And again, I get the custom lock icon message during bootup.
Yes, I realize, I can and probably should install the OTA and then root the device. But that's not my point. I want to understand what to do the NEXT time Verizon pushes out an OTA. Do I have to flash back to stock every time I install the OTA and root the device only after installing the OTA just to avoid getting the custom lock icon? If not, how do I accept the OTA without getting the custom lock icon? (Obviously I can't seem to figure out how to do it now, so I won't be able to do it the next time an OTA rolls around - thus the reason for my question).
Thanks,
Jonathan
you might have to flash a custom ROM to block Verizon from pushing OTA.
http://forum.xda-developers.com/showthread.php?t=1762709
Reference section 5 for me. It looks like you already know how to get to that point. It has great instructions for recovering to stock from the triangle.
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
Honestly, if you want the new feature just wait a day or two after the release. There is always a lovely developer waiting to debloat, deodex, and optimize the official OTA update for your use without breaking root access.
Have I helped with your question? Or have I misinterpreted your needs?
First, thanks for the replies!
ManiakalSealion said:
http://forum.xda-developers.com/showthread.php?t=1762709
Reference section 5 for me. It looks like you already know how to get to that point. It has great instructions for recovering to stock from the triangle.
Click to expand...
Click to collapse
I think you misunderstood me on this point. When installing an OTA after root, I never get the yellow triangle, so there is no need to recover. The problem I'm having is that on the very first screen that appears when you first power on the phone (after installing the OTA on top of a rooted version of Android) it adds a large lock icon with the word "CUSTOM" to black screen (think it says Samsung but I don't recall) to indicate that Verizon has detected something custom about the phone.
I was trying to determine if after having rooted my phone if there was a way to accept the OTA and still maintain root - rather than having to flash back to stock or flash an update using ODIN. It's a pain to have to always flash something at home - I'd like to be able to accept the OTA if possible while I'm away from home. I tried OTA Rootkeeper but that didn't seem to do anything for me - perhaps I'm not using it correctly???
ManiakalSealion said:
http://forum.xda-developers.com/showthread.php?t=1762709
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
Click to expand...
Click to collapse
So if I understand correctly, an app such as OTA Rootkeeper is useless for Verizon Galaxy S3 - the only way to get root and the Verizon OTA is to either 1. flash back to stock, install all OTAs and then re-root OR else 2. flash the custom OTA from a forum member, is that correct? In other words, once I've rooted, I always have to use ODIN to get an update - there is no other option?
jkrueger2020 said:
First, thanks for the replies!
I think you misunderstood me on this point. When installing an OTA after root, I never get the yellow triangle, so there is no need to recover. The problem I'm having is that on the very first screen that appears when you first power on the phone (after installing the OTA on top of a rooted version of Android) it adds a large lock icon with the word "CUSTOM" to black screen (think it says Samsung but I don't recall) to indicate that Verizon has detected something custom about the phone.
Click to expand...
Click to collapse
I'll suggest using EZ Unlock v1.2, just tap to lock then immediately tap to unlock your bootloader and you'll hear an audio confirmation upon pressing unlock. I think that should take care of the custom lock when booting up.
I was trying to determine if after having rooted my phone if there was a way to accept the OTA and still maintain root - rather than having to flash back to stock or flash an update using ODIN. It's a pain to have to always flash something at home - I'd like to be able to accept the OTA if possible while I'm away from home. I tried OTA Rootkeeper but that didn't seem to do anything for me - perhaps I'm not using it correctly???
Click to expand...
Click to collapse
I'll say this, most custom roms block Verizon OTA's from installing so you'll just have to accept that you need to flash back to stock to accept an OTA OR just stick to a rooted OTA based rom. There's at least seven of these, one per OTA or leak that we've seen to date.
So if I understand correctly, an app such as OTA Rootkeeper is useless for Verizon Galaxy S3 - the only way to get root and the Verizon OTA is to either 1. flash back to stock, install all OTAs and then re-root OR else 2. flash the custom OTA from a forum member, is that correct? In other words, once I've rooted, I always have to use ODIN to get an update - there is no other option?
Click to expand...
Click to collapse
Absolutely correct. Can I ask you something? Do you intend on using custom roms or do you just want to use rooted stock OTA's? Cuz you're inquiring an awful lot about OTA's for someone who would be using custom roms. That said, XDA devs have posted a rooted version of each OTA available. Each is in the dev section, they'll be titled something like "Stock Root JB 4.1.2 - I535VRBMB1 Official Update". You could easily just flash any one of these then pull down an OTA since these are left untouched with the only addition being SuperUser. Even still, you would need to re-root after accepting an OTA since OTA's wipe out root so you'll be doing this for as long as we see updates on this phone.
If you're rooted you can use OTA Rootkeeper to back up root, install OTA and then use it again to restore root. I just did this for the current OTA without any issues. Just make sure you also have stock recovery reinstalled if you installed TWRP or CWM, and relock the boot loader first.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
I'll suggest using EZ Unlock v1.2, just tap to lock then immediately tap to unlock your bootloader and you'll hear an audio confirmation upon pressing unlock. I think that should take care of the custom lock when booting up.
Click to expand...
Click to collapse
Yes! That removed the lock icon. So my next question is, when my phone booted back up and said the OTA failed (yet still shows the incremented version number making it appear like the update actually was successful) was there anything that got messed up as part of the upgrade? Or would I be better off going the route of another person's reply which said I should lock the bootloader and flash back to stock recovery first before accepting the OTA?
SlimSnoopOS said:
I'll suggest using EZ Unlock v1.2
Can I ask you something? Do you intend on using custom roms or do you just want to use rooted stock OTA's?
Click to expand...
Click to collapse
Currently I'm not really looking for custom ROMS - my experience with ROMS with my original Galaxy S was just a buggy experience (i.e. call volumes that kept reverting to max for every call, etc) and was not very enjoyable. As long as I stay rooted and current with Android I'm happy at this point (of course that could change down the road).
mav3rick478 said:
If you're rooted you can use OTA Rootkeeper to back up root, install OTA and then use it again to restore root. I just did this for the current OTA without any issues. Just make sure you also have stock recovery reinstalled if you installed TWRP or CWM, and relock the boot loader first.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
Note: The lock icon appeared still
5. Used EZ-Recovery 2.2. to flash CWM recovery in place of the stock recovery (I couldn't get it to flash the same tar.md5 file I used with ODIN though - don't know what kind of file EZ-Recovery needs - so I used the version of CMWR that it provided)
6. Restored root access using OTA Root Keeper (needs reboot I think for this step)
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
jkrueger2020 said:
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
Note: The lock icon appeared still
5. Used EZ-Recovery 2.2. to flash CWM recovery in place of the stock recovery (I couldn't get it to flash the same tar.md5 file I used with ODIN though - don't know what kind of file EZ-Recovery needs - so I used the version of CMWR that it provided)
6. Restored root access using OTA Root Keeper (needs reboot I think for this step)
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
Click to expand...
Click to collapse
Almost worked flawlessly... I had to reboot from SuperSU to get root again.
I found the sdm thing to freez
smalrus said:
Almost worked flawlessly... I had to reboot from SuperSU to get root again.
Click to expand...
Click to collapse
I found the sdm thing to freez but could not find the fwupgrade one. I was also not able to fine the ez unlocker is that in the play store?
I am not sure if the sdm will block the update but now when I go to about phone and select software update it errors out. Also I am only rooted do I realy need to worry about the update? Also looking for a good stable rom. If anyone wants recomend one. Just got my phone like a week ago. Thank you guys. Xda has been great help.
joker66599 said:
I found the sdm thing to freez but could not find the fwupgrade one. I was also not able to fine the ez unlocker is that in the play store?
I am not sure if the sdm will block the update but now when I go to about phone and select software update it errors out. Also I am only rooted do I realy need to worry about the update? Also looking for a good stable rom. If anyone wants recomend one. Just got my phone like a week ago. Thank you guys. Xda has been great help.
Click to expand...
Click to collapse
Re-read the thread to find EZ Unlock, I'm fairly certain someone posted a link. I will say it's been removed from the Play Store for awhile now.
Freezing sdm 1.0 is all you really need to do. That's normal that it errors out now. You froze that setting so it won't be polling for an OTA nor allow you to manually search for an OTA. Whether you want the OTA or not is on you, there isn't much present that we do not already have in custom roms plus the OTA has already been rooted.
Sent from my SCH-I535 using xda app-developers app
This is what worked for me except I reversed step 5 and 6 (I edited the quote below to match what I did). Thanks!
jkrueger2020 said:
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
5. Restored root access using OTA Root Keeper
6. Used EZ-Recovery 2.2. to flash TWRP recovery in place of the stock recovery
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
Click to expand...
Click to collapse
Stock rooted MB1 here w/ TWRP. Tried to update earlier and completely soft bricked my phone. Had to do some fancy work to get it back and restore.
Now I tried this process:
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
5. Restored root access using OTA Root Keeper
6. Used EZ-Recovery 2.2. to flash TWRP recovery in place of the stock recovery
7. Unlocked boot loader using EZ-Unlock 1.2
and when I get to the step of actually installing the OTA - it reboots into stock recovery - and about 15 seconds in it fails and shows the android guy on his back. lol
It actually boots back into the phone properly & says that the update failed. Status page shows the baseband got updated, but not the ROM. Any ideas?
thanks
Edit: Bah. It's the stupid 'E: Error in /tmp/sideload/package.zip error.' According to my searches there's no easy fix.
Edit #2: I just wound up dirty flashing the full stock root package from Scott & Beans. That worked.
I'm running the MD3 on the stock ROM and rooted. Now when I originally rooted my phone (using this guide: http://forum.xda-developers.com/showthread.php?t=2046439), I'm fairly confident that I did NOT unlock the bootloader and also installed the CWM Touch recovery. After the process was over I had an unlocked padlock image show up on my phone every time it booted.
Now, I tried to install the new update via OTA (I defrosted all apps I had frozen) and when the phone re-booted to start the update, I received the warning message "System software not authorized by Verizon...." and in the upper left hand corner it says in red, "Secure: Kernel". The phone will continue to boot to this message. When I try to boot into recovery, it goes to this message, not the CWM recovery. The only way to get out of that message is to boot into Odin mode and hit Vol DOWN to cancel.
SO.....what do I need to do in order to install this new update?
UPDATE: I unlocked via EZ Unlock and rebooted into recovery and this time I was able to get into my CWM recovery and updated the zip file posted on another thread in the general forum. All is well now.
Can I upgrade OTA after root but on STOCK ROM?
So if I'm rooted, but still running one of the VERIZON's STOCK ROM,
1. Can I upgrade OTA?
2. Will suck OTA upgrade unroot my phone?
Thanks
mandar_h said:
So if I'm rooted, but still running one of the VERIZON's STOCK ROM,
1. Can I upgrade OTA?
2. Will suck OTA upgrade unroot my phone?
Thanks
Click to expand...
Click to collapse
As of this moment, yes to both. The newest ota is VRBMF1 and you can still root/unlock that version just as easy as any other.