ok so basically i rooted my phone some time ago and it went kinda fine, after some time i realized i didn't really need it and i unrooted it just now with superSU, when doing so, superSU asked me if i wanted to return to the stock ROM, and i said yes, since i had an update to do, and you can't do those via OTA with a custom rom i think, anyways i said yes and unrooted my phone, the i proceded to delete lucky patcher, twrp, and everything root related, even after all this, after downloading the update my phone gets stuck in a bootloop and i have to press power+volumeup+volumedown to go into recovery mode (i think that's recovery mode?) and here it starts the update, after 5%, it says it failed and i have to reboot, how do i even check if i have my stock rom back?
Rurouni_ said:
ok so basically i rooted my phone some time ago and it went kinda fine, after some time i realized i didn't really need it and i unrooted it just now with superSU, when doing so, superSU asked me if i wanted to return to the stock ROM, and i said yes, since i had an update to do, and you can't do those via OTA with a custom rom i think, anyways i said yes and unrooted my phone, the i proceded to delete lucky patcher, twrp, and everything root related, even after all this, after downloading the update my phone gets stuck in a bootloop and i have to press power+volumeup+volumedown to go into recovery mode (i think that's recovery mode?) and here it starts the update, after 5%, it says it failed and i have to reboot, how do i even check if i have my stock rom back?
Click to expand...
Click to collapse
Because you have not flashed the stock boot. Use dload method to boot to stock rom now. You may flash the same build number or the one with ota.
Related
I was rooted and running CM6. I tried getting back to a stock 2.2 by flashing the stock image from Rom Manager. I downloaded the 2.2 update from google and it wouldn't update. In the system menu or bootloader I got a little format happy with boot/system and so on. Anyway, doing a nandroid now. Is there anyway to get this phone back to the kernel it shipped with?
You have to flash it with the stock recovery.
I've been using that Universal androot.http://www.androidappjudge.com/2010/08/one-click-root-application-universal_10.html I tried flashing stock 2.2 and I didn't read the two options, I just clicked them and kept going not realizing that I flashed the rooted, superuser version. Does this mean that I'm now rooted forever? When I try flashing stock 2.2 with rom manager It stops @ the android and /!\ symbol. Now it's even doing this with CM.
I'm now wondering how to get rid of whatever crap might be floating around on my phone and why it may not be flashing anymore?
there is nothing wrong, rooting allows you the ability to have super administrative rights. Since all you have done is grant yourself admin rights, the recovery should be the same.
Something is wrong. I can't Fix Permissions or flash anything.
Man, I should have just left it alone.
glwinkler said:
Something is wrong. I can't Fix Permissions or flash anything.
Man, I should have just left it alone.
Click to expand...
Click to collapse
Did you wipe? I used 1-click root and I hadn't flashed anything in over a year so I forgot to wipe and I boot looped until I pulled the battery, booted into recovery and wiped. Simple solution but it could be worth mentioning...
So you are saying that, you have the stock recovery now? Triangle with little android? If so, Just download a PASSIMG.zip and flash through bootloader. This will take you to stock.
I have an N1 with locked bootloader and when I wanted to go back to stock(Forgot to get a nandroid of unroot rom). I had to flash a stock recovery. then downloaded the PASSIMG.zip from here http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91+downgrade
This takes me back to ERE76. Then I download an OTA of FRF85B.
I think fix permissions fixed everything. Thanks for the tips!
THIS HELPED TOO:
http://forum.xda-developers.com/showthread.php?t=619153
TWRP Recovery
Rooted
Xposed framework installed
Been getting bugged for the 4.4.4 update, and I wanted to open and look at the ZIP out of curiosity, so I hit install now, thinking it still needed to download... but turns out it didn't, and rebooted right away.
So now I'm stuck in a boot loop of sorts.... it boots, and loads up Android, and I can use the phone, but after about 20-30 seconds it reboots into recovery.
Is there an easy way out of this without wiping everything? Preferably a modded OTA that I can install for the 4.4.4 update.
Check out the thread under general tab to use RSD Flasher or House of Moto to install the 4.4.4 FXZ
DB's Moto X
coreno said:
TWRP Recovery
Rooted
Xposed framework installed
Been getting bugged for the 4.4.4 update, and I wanted to open and look at the ZIP out of curiosity, so I hit install now, thinking it still needed to download... but turns out it didn't, and rebooted right away.
So now I'm stuck in a boot loop of sorts.... it boots, and loads up Android, and I can use the phone, but after about 20-30 seconds it reboots into recovery.
Is there an easy way out of this without wiping everything? Preferably a modded OTA that I can install for the 4.4.4 update.
Click to expand...
Click to collapse
The above post is good advice. If you use House of Moto with the full 4.4.4 FXZ, you can choose to "KEEP DATA".
You will need to flash TWRP back on and re-root afterwards AND re-install Xposed, but all of your apps and settings will remain intact.
The reason this happened is because you have TWRP installed - taking OTAs *always* requires you to have STOCK recovery - not custom.
Good Luck :good:
samwathegreat said:
The above post is good advice. If you use House of Moto with the full 4.4.4 FXZ, you can choose to "KEEP DATA".
You will need to flash TWRP back on and re-root afterwards AND re-install Xposed, but all of your apps and settings will remain intact.
The reason this happened is because you have TWRP installed - taking OTAs *always* requires you to have STOCK recovery - not custom.
Good Luck :good:
Click to expand...
Click to collapse
Thanks for the replies. Thanks for the reply... the phone eventually decided the update failed and gave up. Apparently clearing the cache would've also probably worked.
But, now I've reflashed stock recovery, removed xposed, and unrooted. I should be safe to just take the OTA now, right?
I would've done the FXZ earlier, but didn't realize there was a keep data option.
coreno said:
Thanks for the replies. Thanks for the reply... the phone eventually decided the update failed and gave up. Apparently clearing the cache would've also probably worked.
But, now I've reflashed stock recovery, removed xposed, and unrooted. I should be safe to just take the OTA now, right?
I would've done the FXZ earlier, but didn't realize there was a keep data option.
Click to expand...
Click to collapse
You can try, and it will probably work....but if it were me, I'd still use the FXZ and keep data option. It's cleaner and no chance of something going wrong. Afterwards, just do like I said -- re-flash TWRP, re-root, then reinstall Xposed.
samwathegreat said:
You can try, and it will probably work....but if it were me, I'd still use the FXZ and keep data option. It's cleaner and no chance of something going wrong. Afterwards, just do like I said -- re-flash TWRP, re-root, then reinstall Xposed.
Click to expand...
Click to collapse
Thanks for you help! I am all upgraded and got everything back going to the way it was!
coreno said:
Thanks for you help! I am all upgraded and got everything back going to the way it was!
Click to expand...
Click to collapse
Great!! Glad to hear everything worked out. I sent you a Private message - check your PMs
Just to add my experience: I too tried to apply the update (rooted, 4.4.2, xposed, stock recovery, locked boot loader).
Got the boot loop you mentioned.
Only remedy was for me to quickly go into root explorer and rename the 3c.ota.apk and 3c.ota.odex files. Now I no longer get the notifications (unless I reboot my phone).
jco23 said:
Just to add my experience: I too tried to apply the update (rooted, 4.4.2, xposed, stock recovery, locked boot loader).
Got the boot loop you mentioned.
Only remedy was for me to quickly go into root explorer and rename the 3c.ota.apk and 3c.ota.odex files. Now I no longer get the notifications (unless I reboot my phone).
Click to expand...
Click to collapse
And in your case, it was Xposed.
There are several threads (and posts) discussing conditions for taking an OTA. You need stock recovery, have to disable Xposed, and you need to be close enough to stock so the pre-flash verification will pass. Otherwise, the OTA will fail, and/or you'll get stuck in a boot loop.
There is a little more to it as well, but I'll ask you to see the other threads.
Thought I disabled xposed. But perhaps not. I've read other threads. From my understanding, I won't be able to root (or even the quasi-root) on 4.4.4 with a locked boot loader.
Thx for the reply.
On stock 4.2.2 rooted and perfectly happy for now, last time i tried to flash recovery i bricked the phone and don't want to deal with that again if i can help it. Do i need to flash a custom recovery or can i get by with just stock for now?
What to do about OTA? Is root keeper an option and just accept the updates as they come?
bell boy said:
On stock 4.2.2 rooted and perfectly happy for now, last time i tried to flash recovery i bricked the phone and don't want to deal with that again if i can help it. Do i need to flash a custom recovery or can i get by with just stock for now?
What to do about OTA? Is root keeper an option and just accept the updates as they come?
Click to expand...
Click to collapse
You don't need a recovery unless you want to back up your rom or install other ones.
As for the OTA, people were reporting root stuck when installing 24A, as long as you have stock recovery it should install ok. Worst case is you need to root it again.
it all depends what you want to do bc i had my phone rooted without a custom recovery and it worked just fine using like xposed but if you want to flash a rom or do nandroids then you need a custom recovery. I also took an OTA like a dumbass and it gave me a boot loop with a certification error and it took me a month to fix it so a) plz don't take an OTA and b) get a custom recovery if you want to just be safe, i would if i were you.
Thnx, will try auto rec again last time. What to do after install? Last time it installed, it opened and that was it, couldn't get it to reboot, do l need to do a back up first? What are the steps immediately after install?
This has probably been said 1000 times before, but, I'm an idiot.
Now that we got that out of the way, perhaps you fine folks will help a dummy out?
About a year ago, I followed this guide and was successful in all that it deals with (unlocking bootloader, root, installing custom recovery and flashing custom rom).
My phone started acting a little buggy lately, (probably because I had less than 5 gb of space left? ) so I decided I wanted to just wipe everything and start "fresh".
I went into TWRP, wiped EVERYTHING, (wipe/advanced wipe/checked everything (dalvick,system,data,internal,cache) rebooted into recovery, sideloaded the newest Pure Nexus ROM and GApps zips, flashed both. After flashing new ROM, tried to reboot system, a message appeared saying it appears I do not have supersu installed, would I like to install it now? or something to that effect.
I wiped for"yes", phone turned off, then was stuck on the animation screen (swirling/color dot things) when tying to boot up.
Hold power button down till shut off, then restarted in recovery, wiped EVERYTHING (again), re-flashed the ROM, only this time said "no" to the supersu install screen.
Phone loaded up and is running perfectly.
However, I am no longer rooted???
I wasn't aware wiping everything in TWRP would remove root.
I'm confused because as I already said, I'm a dummy!, but when following the guide, I should root, then install a custom recovery.
My question is, do I only need to concern myself with the one step for rooting with CF-Root
since I already have a recovery installed, or am I going to need to re-install TWRP after rooting and then re-flashing the ROM and GApps?
I'm sure you folks are probably sick and tired of fools like me who just blindly follow along with XDA's [HOW TO] threads without knowing what or why we are doing what we are doing, but I appreciate you all just the same!
Any advice is appreciated!
Thanks in advance.
totallybeachin said:
This has probably been said 1000 times before, but, I'm an idiot.
Now that we got that out of the way, perhaps you fine folks will help a dummy out?
About a year ago, I followed this guide and was successful in all that it deals with (unlocking bootloader, root, installing custom recovery and flashing custom rom).
My phone started acting a little buggy lately, (probably because I had less than 5 gb of space left? ) so I decided I wanted to just wipe everything and start "fresh".
I went into TWRP, wiped EVERYTHING, (wipe/advanced wipe/checked everything (dalvick,system,data,internal,cache) rebooted into recovery, sideloaded the newest Pure Nexus ROM and GApps zips, flashed both. After flashing new ROM, tried to reboot system, a message appeared saying it appears I do not have supersu installed, would I like to install it now? or something to that effect.
I wiped for"yes", phone turned off, then was stuck on the animation screen (swirling/color dot things) when tying to boot up.
Hold power button down till shut off, then restarted in recovery, wiped EVERYTHING (again), re-flashed the ROM, only this time said "no" to the supersu install screen.
Phone loaded up and is running perfectly.
However, I am no longer rooted???
I wasn't aware wiping everything in TWRP would remove root.
I'm confused because as I already said, I'm a dummy!, but when following the guide, I should root, then install a custom recovery.
My question is, do I only need to concern myself with the one step for rooting with CF-Root
since I already have a recovery installed, or am I going to need to re-install TWRP after rooting and then re-flashing the ROM and GApps?
I'm sure you folks are probably sick and tired of fools like me who just blindly follow along with XDA's [HOW TO] threads without knowing what or why we are doing what we are doing, but I appreciate you all just the same!
Any advice is appreciated!
Thanks in advance.
Click to expand...
Click to collapse
Boot back into TWRP and reflash SU
totallybeachin said:
... re-flashed the ROM, only this time said "no" to the supersu install screen......
Click to expand...
Click to collapse
That's correct. No in twrp - is needed when there is already a SU in the flashed rom.
Probably you have not the most recent version of twrp.
In play store there are apps to check if you have root acces.
You can also go to the launcher and start the superSU app
kwdan said:
Boot back into TWRP and reflash SU
Click to expand...
Click to collapse
It always seems to be the most simple thing!
I'm not generally a stupid person, but this stuff can sure make a girl blush!
Thank you.
Worked like a charm.
Falling in love all over again with my Nexus 6.
.....makes note for NEXT TIME I have been eating dummie bears!
As NLBeev said, you are probably using an outdated version of TWRP. It doesn't ask about su any longer.
For the longest time, I was on CM12 with TWRP on my Note 4. I had progressively updated the thing to every nightly update over the year and a half, and decided I wanted to go back to a stock non-rooted state so I can use Android Pay.
Everything flashed ok, the phone is working stock, but recovery is not. If I go into Recovery mode, it says "Installing Update..........................No command!". But then proceeds to "appear" to work. I'm worried this weird error into recovery may prevent recovery mode from installing future samsung updates. Is it normal for recovery to say no command on a stock reflash? I flashed EPG2 via ODIN.