A while back I rooted my Moto G 4 (XT1622), in the process I installed TWRP recovery. I am selling the device to a friend now and would prefer to put it all back to stock.
I was looking at guides to flash a stock ROM, but I guess I only really need to flash stock recovery and lock the bootloader again?
Can anyone confirm and confirm the commands used perhaps? (Or of course, link to a guide)
Many thanks.
I am searching for an answer for this too. I got as far as the "no command" screen with the android character and the red warning sign. I tried all the methods, I googled.
Related
Hey peeps
Ok so here's what I had:
A500 with ICS unlocked bootloader, CWM 10.1 and Thor recovery.
I've upgraded to a Samsung note and now want to flick off my A500. But before I do that I need to return to complete stock. I followed another websites guide (stupid me XDA all the way!) and now ended up in a pickle!
What the other website recommended was to download the OTA ICS (which I already had) and flash it like a normal ROM. I did that and the bootloader is still unlocked and I am not able to gain root on the custom ROM to repair the recovery (which gives me the little android on his back with red "!").
So here's where things get tricky. I can't regain root because ADB isn't detecting my device. I've tried every tool in blackthunders bag of tricks and they all come back saying "Done" but they don't actually work. I do have ATX mode and fastboot.
Can someone please help me figure out how to:
Get ADB working
Load stock bootloader
Get stock recovery back?
Thanks in advance!
PS: I've tried searching the forums and followed a number of threads and how to's but none seem to work for me
Ok update on this. I'm such a moron! I removed ADB drivers and re-installed. Once I got ADB working I simply used afterota (forgot I had it!) to flash stock and then do the update.zip trick
So my friend and I both have razr M's.
His was bought through a 3rd party and already had the bootloader unlocked, but was updated to the latest VZW update for the M.
I cannot for the life of me get a custom recovery to install.
First I tried the traditional "fastboot flash recovery" method. It sends the recovery without error messages, but attempting to reboot into the recovery only yields the green android with the exclamation point coming out of his chest.
I next tried to even just boot the recovery image from the bootloader, which gave me the operation not permitted error.
Any ideas as to why this may be happening? I feel like I'm pretty android-savvy, but this is stumping me. My initial guess would be that it was because he took the latest update on the stock recovery, but even then his bootloader is still unlocked.
fo0you said:
So my friend and I both have razr M's.
His was bought through a 3rd party and already had the bootloader unlocked, but was updated to the latest VZW update for the M.
I cannot for the life of me get a custom recovery to install.
First I tried the traditional "fastboot flash recovery" method. It sends the recovery without error messages, but attempting to reboot into the recovery only yields the green android with the exclamation point coming out of his chest.
I next tried to even just boot the recovery image from the bootloader, which gave me the operation not permitted error.
Any ideas as to why this may be happening? I feel like I'm pretty android-savvy, but this is stumping me. My initial guess would be that it was because he took the latest update on the stock recovery, but even then his bootloader is still unlocked.
Click to expand...
Click to collapse
Are you rooted?
Use rom manager it is easy. See my goodies.
Or use my restore - a link in goodies too.
aviwdoowks said:
Are you rooted?
Use rom manager it is easy. See my goodies.
Or use my restore - a link in goodies too.
Click to expand...
Click to collapse
That particular phone is not rooted, although the bootloader is unlocked.
Thanks for the links, so I should be able to use the RSD lite to restore your version that has CWM as well? If so, that should get it up and running so I can at least obtain root from the recovery.
I got my spare G2 today and have run into a bit of a problem with rooting it. The root process seems to have gone fine. It says I am rooted and I can use Root Explorer to remove bloat and such, but something seems to have gone wrong with the recovery. If I try to boot into recovery, I get an error message that says something about Secure booting error. It has some other info, but the screen goes black so quickly that I can't make out what it is saying. If I hold the power button down, I can reboot the phone as normal so it's not bricked, but without a recovery I can't do any custom Roms. I've tried various methods to flash a new recovery and they all said they were successful, but I still can't get into recovery mode.
Does anyone know what I did wrong or how to get around this? The phone came with firmware 4.4.2 26a if that means anything to your advice.
Thanks a million for any help.
Looks like your recovery gone. Flash stock Lollipop Kdz then root and install TWRP with Autorec from Google Play.
Thank you. Just did the TOT method to flash back to stock 26a so thankfully all is back to normal. Now i'm afraid to try it again because I don't know what went wrong. The ioroot version I have is an older version for 24a or backwards. That's the one I used for my original G2. So I tried using a different method (one click) for this phone and it was a mistake. Could I use the flash tool to kdz back to 24a and then root using the method I know or do I have to stick to 26a for hardware reasons?
Howdy folks -- I'm having issues with my G2 that I hope people here can help me with. I've already had some advice in the Noobs thread, so thanks for that.
My phone is a LG G2 D800 (AT&T) and is unlocked, being used on the Rogers network. The previous owner of the phone had installed CloudyFlex, which is what I was using until recently.
Here's the story in a nutshell:
On my first attempt to upgrade my ROM from CloudyFlex, I booted into recovery (TWRP installed by the previous owner) and then flashed the newest TWRP for my phone. I then realized I didn't have all the files needed to do the upgrade, so after the TWRP image was successfully flashed, I went to "Reboot System". Doing so gave me a non-responsive phone (LG logo then nothing but a slowly flashing LED).
I managed to get the phone into Download Mode and followed the instructions for LG Flash Tool in the first post here exactly: http://forum.xda-developers.com/showthread.php?t=2432476 which gave me a "stock" functional phone again, but one now running Jellybean (4.2.2, software version D80010o). I'd like to be on Kitkat or (preferably) Lollipop.
I am able to root the phone easily using the LG One Click Root tool. No problem there.
So that's the story. I now have a AT&T D800, unlocked and running on Rogers with Jellybean 4.2.2 (D80010o). I would like to bring my phone into 2016 by updating it to at least KitKat, preferably Lollipop (if I can). The problem is that I can't get a working recovery. Here's what I've tried:
Flashify: following its instructions exactly seems at first like it's working (I get some kind of "success" message) but when it then goes to reboot the phone, it reboots to a black screen (phone is non-responsive -- have to hold down the power button to shut it off, then turn it back on, at which point it boots normally into Android)
TWRP Manager: I've tried it as well, and get the same outcome as Flashify (apparent success followed by a black screen etc.). Once the phone is on and back into Android, TWRP Manager seems to think that TWRP is not installed.
AutoRec: I installed the version from the thread here: http://forum.xda-developers.com/showthread.php?t=2715496 ran it, and again it appeared to be successful. When it rebooted, it did go into recovery, TWRP 2.7.0.0 or something like that. Then I went to "reboot system" but got the same problem as before -- phone non-responsive, slow flashing LED, had to go back into Download Mode and flash the Jellybean TOT file, etc.
Can anyone help me figure out what is going on? I just want to get my phone to a nice stable Lollipop state with decent performance and battery life. Failing that, KitKat. Not sure what to do next.
Crisis averted: I managed to get CloudyG2 2.2 running on my phone and all seems well. Here's what I did:
I installed stock KitKat on my phone using the procedure outlined at http://forum.xda-developers.com/showthread.php?t=2663369
I then rooted the phone with ioroot (following its instructions)
I then used AutoRec to install recovery. For some reason I'm only ever able to boot to recovery directly from AutoRec -- when I try to get into recovery using the usual techniques, the phone locks up. I literally have to reinstall recovery every time and then say "yes" when AutoRec asks me if I want to reboot into recovery. Not sure why this is. The TWRP version I see is 2.7.0.0
I then flashed the KK bootloader and then CloudyG2. So far so good.
I'm a bit too shellshocked to try to install a Lollipop ROM on this phone right now. Maybe some day. In the meantime, many thanks to those who helped me out on other threads.
Why didn't you just tot to the latest rom?
stan54 said:
Why didn't you just tot to the latest rom?
Click to expand...
Click to collapse
Based on comments at http://forum.xda-developers.com/showthread.php?t=2432476 I was under the impression that the farthest I could get would be Jellybean. Then found the other thread with the KitKat TOT. That enabled me to use Autorec (though recovery still works wonky on my phone) so I now have CloudyG2.
Hi I am using the windroid toolkit trying to root my new x pure. I got thru the first two steps ok, with a message thats its ok to move on to step 3, root access by flashing superuser.... everytime I try to flash super user I get a message that the phone is in the wrong state? I am still in the fastboot mode, start option. Is that correct? I tried rebooting the phone into the recovery mode by selecting the power and up volume keys, but that did not work? Im confused.......If I got by the 2nd step, should team win be in the recovery? thanks for any ideas here......
Why do you need a toolkit to root?
update,,,, the toolkit was on youtube and looked like an easy way to go thru the unlock, install recovery, root process. It worked fine and fast for the first two sections. I have an unlocked bootloader and teamwin recovery. I went to a different video that showed how to flash superuser into the recovery. I did that and now the phone is stuck on the Android M bootup screen. I am able to boot into the fastboot flash mode and teamwin recovery, so Im not completely bricked. Just stuck on the boot screen. Turns out the flashing superuser method does not work on Marshmellow... Anyone know how to fix this?
Did a bunch of searching and after a very long night I was able to return to stock, 5.1.1. Phone is back to normal and rooted. Lots of info here....just need to find it.....
Garyalp said:
Did a bunch of searching and after a very long night I was able to return to stock, 5.1.1. Phone is back to normal and rooted. Lots of info here....just need to find it.....
Click to expand...
Click to collapse
You can update to Android M 6.0 and then you should flash SuperSU 2.62-3 through TWRP to gain root, after rooting with this version or SuperSU, you should be able to update to a new version of SuperSU, I have update to SuperSu 2.65 with no issue. This was the easiest way that I have found to root our phone running Android M 6.0.
Thank you for that information. Wish I had it from the beginning, would have saved a bunch of trouble. Turns out I spoke to soon. I am having the wi fi issue that some have had. I have gone from a stock 5.1.1 to 6.0, unlocked bootloader, teamwin recovery, soft brick, back to 5.1.1, now rooted. Not sure exactly where the phone is. The bootloader remained unlocked thru the reflash to stock 5.1.1. I noticed that the mac address and Ip address are both, "unavailable", when I go to: settings/wifi/ advanced. Most likely the reason wifi is inop. Is there a way to find the mac and Ip address? Which modem should I be on, now that Im 5.1.1? Will a factory reset bring them back or does that just clear user data? As you can tell I know just enough to be dangerous....lol.
mcx6 said:
You can update to Android M 6.0 and then you should flash SuperSU 2.62-3 through TWRP to gain root, after rooting with this version or SuperSU, you should be able to update to a new version of SuperSU, I have update to SuperSu 2.65 with no issue. This was the easiest way that I have found to root our phone running Android M 6.0.
Click to expand...
Click to collapse
exactly what I did, works great.