I want to replace twrp with stock recovery, so I can update to lollipop without worrying about being rooted. I'm not concerned with being rooted anymore with this phone. I need it to be more reliable for work and have had lots of issues lately. Does anyone know where I can find the stock recovery?
You can root it with kingroot. Put it someplace cold first or it may heat up and shut off.
Sent from my D6708 using XDA-Developers mobile app
Related
I'm running 4.3 and kind of getting tired of waiting for a root method other than vroot. So I might as well use it. I just have a few questions for people that have used it.
- Does it show a custom boot animation?
- Can you receive OTA updates?
- Can you completely unroot?
- If you unroot will the boot animation go back to stock? (From what I've seen and heard there is a custom boot animation but I wasn't sure)
- Does it wipe your phone/delete everything?
- Does it void the KNOX warranty? (0x0 to 0x1)
For the most part I've heard some answers here and there and they were not clear enough. I would like to know from someone who's done it and what their experience was like. Thanks.
Sent from my SCH-I545 using xda app-developers app
1. Yes it does
2. I'm on MJ7 so I couldn't say for sure
3. Haven't tried it yet but while I was attempting to root there was an area that appeared to be unroot, don't mark my words
4.
5. Does not wipe
6. Not that I know
Sent from my SCH-I545 using XDA Premium 4 mobile app
tredonkulous said:
I'm running 4.3 and kind of getting tired of waiting for a root method other than vroot. So I might as well use it. I just have a few questions for people that have used it.
- Does it show a custom boot animation?
- Can you receive OTA updates?
- Can you completely unroot?
- If you unroot will the boot animation go back to stock? (From what I've seen and heard there is a custom boot animation but I wasn't sure)
- Does it wipe your phone/delete everything?
- Does it void the KNOX warranty? (0x0 to 0x1)
For the most part I've heard some answers here and there and they were not clear enough. I would like to know from someone who's done it and what their experience was like. Thanks.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I'm only going to attempt one question on that list.
At this point presume that rooting will cause OTA to fail, minimally you will lose root.
I say this because the files they check are getting more encompassing.
When I went from ME7 to MI1, no problem, rooted and retained root.
MI1 -> MJ7, can't update rooted unless you jump through a couple of hoops.
Presume those hoops will get tighter and tighter as Verizon tries harder at every update to hold your phone hostage.
I'm not going to MJ7 because tethering is now difficult at best and all the hacks that allowed Google Wallet to work, don't work anymore.
tredonkulous said:
I'm running 4.3 and kind of getting tired of waiting for a root method other than vroot. So I might as well use it. I just have a few questions for people that have used it.
- Does it show a custom boot animation?
- Can you receive OTA updates?
- Can you completely unroot?
- If you unroot will the boot animation go back to stock? (From what I've seen and heard there is a custom boot animation but I wasn't sure)
- Does it wipe your phone/delete everything?
- Does it void the KNOX warranty? (0x0 to 0x1)
For the most part I've heard some answers here and there and they were not clear enough. I would like to know from someone who's done it and what their experience was like. Thanks.
Sent from my SCH-I545 using xda app-developers app[/QUOTE
It has the stock samsung boot animation with the pad lock unlocked, you can recive ota if you dont freeze or remove system apps or install xposed framework but ota usually kills root so freeze sdm 1.0 and knox through titanium backup to avoid future ota hassle, to completely unroot download odin and get the mj7 odin file boot your phone into odin download mode and flash back to stock. Dont worry about the boot animation if use odin it all gets wiped back to stock but it does wipe your data but knox wont be tripped if you use odin because you are reflashing the rom which resets everything. I used vroot with zero issue and love my 4.3 stock rooted phone!
Click to expand...
Click to collapse
I have a stock rooted 4.4.1. The OTA 4.4.2 came through. I used Root Keeper and did a temp unroot. Then I installed the update. At first there was the android with an exclamation point and underneath that "Error". I turned it off and back on. Now the Exclamation android is there and the words, "No Command." What do I do?
You will need to load a stock image via ADB if there is no OS. You can also use Skipsoft or Wugfresh toolkit to automate the process. Both talk you through the process. I use Skipsoft because incan never get drivers to load with Wugfresh, but in all likelihood it is my laptop that causes this. Others never have this issue.
Sent from my Nexus 10 using Tapatalk 4
jideay said:
I have a stock rooted 4.4.1. The OTA 4.4.2 came through. I used Root Keeper and did a temp unroot. Then I installed the update. At first there was the android with an exclamation point and underneath that "Error". I turned it off and back on. Now the Exclamation android is there and the words, "No Command." What do I do?
Click to expand...
Click to collapse
Same issue. Very scary. I solved it by downloading a stock odexed 4.4.2 ROM. Use the wug nexus tool to flash tarp recovery and ouch the zip to the tablet while in the recovery. Flash the ROM via the recovery. Once installed. Let it start up. Then use the tool again to flash the stock image. And root it. And your set. In wanted to be 100% stock. So after u flash the stick ROM via the recovery you can just keep it there.
Sent from my Nexus 10 using XDA Premium 4 mobile app
Hey
The ota worked with me just fine of course you will need to re root ur device for that u can very easily use nexus root toolkit it will do every thing for you
Sent from my Nexus 10 using xda app-developers app
happened to me to...
Going from 4.4 to 4.4.2... I was able to get back to 4.4 by flashing stock without formatting user data but it was lame. I wish someone had a clue why this is happening? I was stock rooted and did have appops but didn't making any permission changes.
I've read this is happening to stock unrooted n4, n5, n7, and us on n10's. I've even read Google is replacing devices for users that don't know how to fix the problem as its over their heads.
notfaded1 said:
Going from 4.4 to 4.4.2... I was able to get back to 4.4 by flashing stock without formatting user data but it was lame. I wish someone had a clue why this is happening? I was stock rooted and did have appops but didn't making any permission changes.
I've read this is happening to stock unrooted n4, n5, n7, and us on n10's. I've even read Google is replacing devices for users that don't know how to fix the problem as its over their heads.
Click to expand...
Click to collapse
I had exactly the same problem and fixed it in the same way. I guessed it was because I was rooted and I had messed with so many things (using xposed, tibu) but it seems that is not the case. Very weird...
Sent from my Nexus 10 using xda app-developers app
Ok, I know I'll be needing my flame retardant suit for this, but I'm in a tight spot and work has made it where won't really have the time I need to dig through the mass of threads for at least a couple weeks.
When I got my S4 in January, it was the first time I didn't even bother dropping a recovery or custom rom on a new Android. Usually I'm running something custom by the next day. In this case, all I did was root, but left it stock. When 4.4. dropped, I froze the OTA update notice so I didn't have to deal with it. So for the last several months, I've been running 4.3 on a rooted MK2 build with no custom recovery or anything else.
Fast forward to now and I've finally hit a point where I either need to try and wipe/reset my current, or more preferred go ahead up to 4.4 and be done with it. That's where the challenge comes in. When last I was looking (a few months back), going from a rooted stock 4.3 to 4.4 was a bit of a nightmare. Is that still the case or has the bootloader finally been dealt with by the mighty devs out there? I've been looking for a sticky or just a thread on if we're back to a good old one-click approach, but so far have come up blank.
Anyone in a position to dodge the fireballs and point me in the right direction?
Since you are already on a locked boot loader custom recovery is not an option. You may as well unfreeze the OTA and unroot. Then take the OTA to NC5 KitKat and root with towelroot. That is my recommendation...
Sent from my SCH-I545 using XDA Free mobile app
Or use Odin and the no wipe files and re-root with towel root
http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my SCH-I545 using XDA Free mobile app
sponix2ipfw said:
Since you are already on a locked boot loader custom recovery is not an option. You may as well unfreeze the OTA and unroot. Then take the OTA to NC5 KitKat and root with towelroot. That is my recommendation...
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Blows my mind that they finally managed an unbeatable bootloader. *50s gangter voice* Curses!!!
I had root access on 4.4.2, downloaded OTA1 update, failed to install OTA2. I used Samsung Kies to install OTA2 and now I am on 5.0.1 without root access.
My phone isn't fully functional at the moment, with some apps not working and some completely broken due to no root access.
Is there a way for me to gain root access while already on 5.0.1? I see these ways to have rooted 5.0.1 but that is when you phone is rooted 4.4.2.
Thanks.
Nope. No way to root 5.0.1 yet.
Sent from my SCH-I545 using XDA Free mobile app
Bleh, that's what I thought when I was searching but I was hoping I had been missing something. My phone is pretty messed up at the moment too. Numbers on my lockscreen randomly turn to blocks.
urawizardhary said:
Bleh, that's what I thought when I was searching but I was hoping I had been missing something. My phone is pretty messed up at the moment too. Numbers on my lockscreen randomly turn to blocks.
Click to expand...
Click to collapse
Out of curiosity, since I'm in the same position... Can you flash Kit Kat firmware onto it with ODIN? Are you able to go back to a rooted 4.4.2?
No, no downgrading. A qFuse was blown, no way to go back. You can flash the stock 5.0.1 firmware with Odin to fix that though(the problems with the OP's phone)
I've had this pending on my phone for quite awhile, I haven't done it because I'm rooted. I decided one day to try it, my phone rebooted to TWRP and nothing happened. Which is exactly what I thought would happen. So I pulled the stock recovery from the stock rom and successfully flashed it. Tried the update again and I am getting a bit error from the stock recovery. The phone goes into "wtf just happened" mode and I have to do a battery pull and reboot. Which works fine. I don't really want to backup everything and re-root and reinstall everything, so does anyone know what my bootloader isn't seeing, but needs to see in order to push the update through?
Also, my phone isn't reading my brand new 64gb SanDisk evo suddenly. Was reading it fine last week... And ideas?
I'm on stock rooted ZV8 with sprint naval kernel.
Sent from my Sprint LG G3 sexiness via tapatalk
partitions may be zv4/zv6 on your phone? that may be why you cant do the OTA. what about dirty flashing stock rooted ZVA(not recommended, but works great for me)? there is a navel kernel for it also. Make a backup and if you dont like it, flash back? what connectivity fix does the ZVA update claim? I thought the only (LISTED) update was they added factory reset protection?
He can't take the OTA cause he has TWRP installed. OTA will only install with stock recovery. Probably will need to use the flashtool to go to complete stock if you want to receive the OTA.
Sent from my SM-G920P
Arjohns said:
He can't take the OTA cause he has TWRP installed. OTA will only install with stock recovery. Probably will need to use the flashtool to go to complete stock if you want to receive the OTA.
Sent from my SM-G920P
Click to expand...
Click to collapse
He said he put stock recovery back on, but yes he would probably need to flash completely stock to do the ota
Sent from my LGLS990 using XDA Free mobile app
Guess I should have read that better, sorry. As stated, try the rooted ZVA. OTA can be stopped due to edited build prop, debloating, etc. So complete stock through flashtool or flashing a rooted ZVA would be the only way to get to the new version.
Sent from my SM-G920P