Related
For anyone who wants it, here's the STOCK PRE & Post-OTA recovery images. (I just added PRE-OTA if for some reason it's needed down the road.)
If you plan on flashing it back over the ClockWork recovery image, make sure S=OFF otherwise the flash won't complete successfully.
You can turn S=ON back after the flash.
THIS IS NOT A FLASHABLE ZIP - I only zipped it to get it to upload as an attachment! You will need to do a Fastboot Flash to install (there may be other methods but Fastboot is what I used).
Below are instructions I am borrowing from the Amen-Ra recovery installation from the N1 - they will apply the same here!
via fastboot
Code:
Copy recovery.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding volume down, then select fastboot)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery.img
via terminal app
Code:
Copy recovery.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter)
I hope this proves to be useful to at least 1 person!
Thanks a lot!
MYT4G (Glacier)
sounds like a good way to restore...now all we need are some roms
The reason I dug this up was that I am very curious as to whether after having rooted, if you have stock recovery and S=ON whether or not further OTAs will come to you.
Back in my N1 days if the stock recovery was not present an OTA couldn't install.
Sweet! Was looking for the stock recovery before exchanging my mytouch. Where/how did you get this?
Great contribution
c_licious said:
Sweet! Was looking for the stock recovery before exchanging my mytouch. Where/how did you get this?
Click to expand...
Click to collapse
Actually I merely extracted them from the stock Rom here on xda and from the ota update file someone posted but nobody has figured out how to apply. Both have been tested on my phone.
I figured I would make it easier on everyone who simply wants to download the recovery as opposed to the entire rom or update.
Does this then solve the problem people have of not being able to root because they downgraded? If so, we may not need that OTA update link anymore.
kitsunisan said:
Does this then solve the problem people have of not being able to root because they downgraded? If so, we may not need that OTA update link anymore.
Click to expand...
Click to collapse
Check this thread out - I was just reading it, should help out!
http://forum.xda-developers.com/showthread.php?t=843428
Nevermind, wasn't paying attention when I posted, thought it was something else. Still, will come in very handy for me, I just got my replacement today, and replacing clockwork recovery was the last thing I needed to do.
JWhipple said:
The reason I dug this up was that I am very curious as to whether after having rooted, if you have stock recovery and S=ON whether or not further OTAs will come to you.
Back in my N1 days if the stock recovery was not present an OTA couldn't install.
Click to expand...
Click to collapse
Thanks for making these available. I also wanted to get the recovery to hopefully let me get OTA's again (got the first one).
I was hoping I could do so with everything stock (unroot with visionary) but also being able to leave s=off - does that absolutely have to be set back =on?
You got the first one after reverting back from being rooted?
gaww said:
Thanks for making these available. I also wanted to get the recovery to hopefully let me get OTA's again (got the first one).
I was hoping I could do so with everything stock (unroot with visionary) but also being able to leave s=off - does that absolutely have to be set back =on?
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
gaww said:
Thanks for making these available. I also wanted to get the recovery to hopefully let me get OTA's again (got the first one).
I was hoping I could do so with everything stock (unroot with visionary) but also being able to leave s=off - does that absolutely have to be set back =on?
Click to expand...
Click to collapse
Not sure - but if you want to "appear" to be 100% stock w/ OTA update, probably best to set it to S=ON.
The thing is though, my understanding is that if even if you use the unroot, you still will have persistent root unless HTC or Google somehow patches the exploit that was used to get root in the first place. So, you'll have root but won't be able to change anything on the ROM unless you turn S=OFF again. I ran the unroot and S=ON and still have the ability to do everything (other than mess with the ROM) that your standard Rooted phone would be able to.
jjlean said:
You got the first one after reverting back from being rooted?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
You can force install the first OTA, but without forcing it I don't believe it's going to happen.
http://forum.xda-developers.com/showthread.php?t=843428 shows how to do it.
JWhipple said:
You can force install the first OTA, but without forcing it I don't believe it's going to happen.
http://forum.xda-developers.com/showthread.php?t=843428 shows how to do it.
Click to expand...
Click to collapse
I got the first OTA before doing s=off (needed the OTA to make it work at the time - did it first day).
I am trying to find out about the second OTA, about which there is practically no information available. I would I assume I have to have the first one installed to get the second (but what is it?).
Again - thanks for posting the original stock recoveries - have a feeling I may need one down the road (like when 2.3 finally comes out and I have a reason to go back to stock).
I've yet to see anyone say that they have actually received a 2nd OTA... Go figure?
Would I be able to use this recovery image to get my phone back up an running again?
I was messing around trying to apply the custom animations and somehow ended up getting my phone stuck in a constant reboot mode.
I have done some research and think that I am on the right track, but can someone verify this for me?
I have permroot with S-OFF, factory reset from the bootloader menu does not get me anywhere, but the phone is recognized through the "fastboot" prompt.
Would I just place the recovery image in the root of the sd card and run these commands?:
fastboot erase recovery
fastboot flash recovery.img
Thanks in advance for any help
From terminal im getting image not found? Do I have to mount or something?
Also... From pc ....Put .img in a place where fast boot can see it, where is thay
Sent from my HTC Glacier using XDA App
Ok guys, the absolute easiest way to do this... This is dependent upon you having S=OFF.
1) Install the android SDK....
2) In my case, fastboot is in C:\sdk\tools as I installed the SDK to C:\SDK. For fastboot to see the image file, I placed the image file (after extracted from the .ZIP) into the C:\sdk\tools folder.
3) Shut down the phone. Turn it back on while holding down the VOL-DOWN button.
4) On the bottom of the screen you'll see:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
5) FASTBOOT should already be highlighted. Press the POWER button.
6) If your USB isn't already plugged in, do it now.
7) Give the PC max of 30 seconds to recognize the bootloader mode.
8) From a DOS prompt, navagate into the C:\SDK\TOOLS folder.
9) Type "FASTBOOT DEVICES" (less the quotes) and press ENTER. If your phone is recognized it should show the serial info of your phone.
10) Type "FASTBOOT FLASH RECOVERY RECOVERY.IMG" (again, less the quotes) and press ENTER .
11) You should see the send and receive. If you do, SUCCESS.
I was able to do all of the steps listed, but I keep getting stuck at a boot loop.
Fastboot recognized my phone, flash recovery from fastboot says that it is successful, but still no luck.
Sent from my HTC HD2 using XDA App
I got the notification last night for the update to 4.4 and proceeded with the install, it rebooted in TWRP recovery started installing and then after 5 minutes or so it dropped back to the TWRP menu.
I tried a reboot but whatever I try and do it always boots into recovery which I take to mean the upgrade failed and something is wrong with the boot loader.
I've tried to sideload the full firmware but it just sits there saying waiting for ADB mode and does nothing.
How can I go about rescuing my N7?
Thanks for any help.
Jon
jonchill said:
I got the notification last night for the update to 4.4 and proceeded with the install, it rebooted in TWRP recovery started installing and then after 5 minutes or so it dropped back to the TWRP menu.
I tried a reboot but whatever I try and do it always boots into recovery which I take to mean the upgrade failed and something is wrong with the boot loader.
I've tried to sideload the full firmware but it just sits there saying waiting for ADB mode and does nothing.
How can I go about rescuing my N7?
Thanks for any help.
Jon
Click to expand...
Click to collapse
I dont know the fix actually. but its not safe to do an OTA update when you're not in stock(recovery)!
I had the same problem. Apparently TWRP isn't working with 4.4.
It seems to be a rule never to OTA if you're not on full stock.
Anyway, here's a solution to get you back to a working 4.3 without loosing data. I just followed the steps and they work fine:
Flashing stock factory image
Afterwards use one of the guides to manually upgrade to 4.4
bur2000 said:
I had the same problem. Apparently TWRP isn't working with 4.4.
It seems to be a rule never to OTA if you're not on full stock.
Anyway, here's a solution to get you back to a working 4.3 without loosing data. I just followed the steps and they work fine:
Flashing stock factory image
Afterwards use one of the guides to manually upgrade to 4.4
Click to expand...
Click to collapse
Thanks for this worked a treat, never to be repeated.
Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.
Just restart device to bootloader, unpack official Lollipop image and run flash-all.bat within directory with fastboot.
It's very difficult to hard brick..
kuba9519 said:
Fastboot works, but adb doesn't see my device now.
Click to expand...
Click to collapse
FWIW adb only works when booted into Android. Fastboot only works in the bootloader.
kuba9519 said:
Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.
Click to expand...
Click to collapse
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now
Nexus still in mortal peril
GalaxySN00B:0 said:
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now
Click to expand...
Click to collapse
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?
This shows how to get to recovery mode from the dead Android screen http://www.robschmuecker.com/how-to-boot-into-recovery-mode-nexus-7/
Sent from my XT1080 using XDA Free mobile app
atrielienz said:
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?
Click to expand...
Click to collapse
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!
DMF1977 said:
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!
Click to expand...
Click to collapse
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.
Use wugs but make sure you tick tablet is in bootloop, worked for me.
atrielienz said:
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.
Click to expand...
Click to collapse
U can't boot in to android, but u did state earlier that u can boot to the bootloader, and that it was unlocked, so its definitely not hard bricked!
So I was tring to go back to stock completely, after I locked my bootloader and installed stock recovery, I proceed to sideload oss, like I've done before I put the phone in sideload mode, the device is recognized by adb although I got a cannot read file error, I downloaded the stock rom again (even though the zips were not corrupted as I could browse them easily) and the same thing happend.
Now I'm at a loss as what to do as it has stock recovery and no os installed, I can get into the bootloader and the stock recovery but I've never had this happen and I can't find anything that will help.
I tried with cmd prompt and adb in administration mode no change, I also made sure the file was in the adb folder.
I'm not sure of what else to say except to ask for help, I'm way bummed out, I've gone back to stock on this device before the only difference was I was running marshmallow other than that idk any other changes since the last time.
I would be very grateful for any help at all. Right now I just need a working phone,
Thank you for reading my post and thank you in advance for possible help with my issue.
Simple reboot of PC should do the trick, at least that did it for me
Didn't work for me, after the first fail I went to a l coffee shop and downloaded the rom again after shutting the pc off in the mean time.
It had no problem flashing the stock recovery it was only after I locked the bootloader and then tried to flash the stock rom
Check the specification of pc should be 4GB ram, drivers, and disable anti virus.
lebeatnik said:
Didn't work for me, after the first fail I went to a l coffee shop and downloaded the rom again after shutting the pc off in the mean time.
It had no problem flashing the stock recovery it was only after I locked the bootloader and then tried to flash the stock rom
Click to expand...
Click to collapse
Keep your bootloader unlocked, I assume you try to ADB sideload? Try adb push file /sdcard/ then manually flash it through TWRP
madsponge26 said:
Check the specification of pc should be 4GB ram, drivers, and disable anti virus.
Click to expand...
Click to collapse
This doesn't make sense... Even a 1GB RAM laptop can do this.
The specs. Of the pc is not the issue
So your advice would be to unlock the bootloader and use twrp?
Currently as I s
lebeatnik said:
The specs. Of the pc is not the issue
So your advice would be to unlock the bootloader and use twrp?
Currently as I s
Click to expand...
Click to collapse
No the specs are not an issue lol.. Basically it cannot read the file you are trying to sideload, this is because of either wrong adb drivers, or wrong Fastboot drivers... A easy work around is to manually push the file with "adb push filename directory" then you manually flash it but since stock recovery can't do this it won't work.
So what steps do I need to do to fix this,
Do I first lock the bootloader, then flash twrp? Also to push the file with adb what mode should I put the phone in?
Sorry For these terrible replies, I'm on a very old backup device.
It's odd to me as adb detects the device just fine, I was even able to flash the stock recovery, as I was trying to go back to complete stock.
In all I need to get the device work again.
I have the latest stock rom and twrp, I just don't want to make it totally bricked as right now I can at least get the phone into the bootloader and in side load mode (although it doesn't work)
So basically I'm asking how in what order should i go about, locking the bootloader, flashing twrp, and push the rom, I've never done this before.
I can't thank you enough for trying to help me out.
I'm thinking I would unlock the bootloader then flash twrp recovery, then idk what mode I should be in to try and push the rom via adb (I've never done this) as once I get twrp on the device and have the rom on the device I hope to have no problem flashing the rom through twrp.
Thank you for replying I hope to resolve this ASAP.
Sorry for not editing my previous post im struggling with the device I'm currently using, I don't understand why my drivers or adb version isn't working as i had no problems locking the bootloader and flashing stock recovery, the only problem I ran into was the last step, flashing the rom.
So yeah I don't know but after I locked the bootloader.... problems
lebeatnik said:
Sorry for not editing my previous post im struggling with the device I'm currently using, I don't understand why my drivers or adb version isn't working as i had no problems locking the bootloader and flashing stock recovery, the only problem I ran into was the last step, flashing the rom.
So yeah I don't know but after I locked the bootloader.... problems
Click to expand...
Click to collapse
Unlock your bootloader, install twrp. Then wipe all partitions. Adb push your rom to a directory you can remember I usually do /sdcard/ (just stay in twrp.) then you click on install and your rom should be there.
Keep the bootloader unlocked... Just in case, no need to relock it again since you will lose data if you run into an issue.
THANK YOU! All I did was unlock the bootloader and the phone started up I am assuming it did not wipe the system partition and it ended up restarting as if I did a factory reset
Hey guys, I've been searching all day for a way to revert to stock recovery on my t mobile moto z2 force (XT-1789-04) and I can't find anything anywhere. I've scoured the forum and google all day but just can't seem to find either a. a rom that has stock recovery or b. a stock recovery image. Would anyone be willing to point me in the right direction? Thanks!!!
Edit: this is so I can install OTA updates again because when the download verifies, it fails without asking me to reboot meaning I can't use flashfire in this case. I'm very particular about things being a certain way with my phone, so please help me out!
thedemonschild said:
Hey guys, I've been searching all day for a way to revert to stock recovery on my t mobile moto z2 force (XT-1789-04) and I can't find anything anywhere. I've scoured the forum and google all day but just can't seem to find either a. a rom that has stock recovery or b. a stock recovery image. Would anyone be willing to point me in the right direction? Thanks!!!
Edit: this is so I can install OTA updates again because when the download verifies, it fails without asking me to reboot meaning I can't use flashfire in this case. I'm very particular about things being a certain way with my phone, so please help me out!
Click to expand...
Click to collapse
You'd have to flash a stock boot image and lose root. You can't take OTA without going full stock then rerooting afterwards. The OTA does a hash check on the device to make sure system has never been mounted rw and also checks to see if boot is unmodified (where root and recovery sits in this phone).
Ok then, thank you for the advice. The stock boot.img files I've used haven't brought back stock recovery though. It says no command with an android on its back. Could you please point me in the direction of a proper stock boot.img I could flash? I don't care about losing root. Also, I tried using blank flash for my device (I'm not entirely sure what that does though as I haven't yet gotten it to work) but it always hangs on <waiting for device>. Any advice?
thedemonschild said:
Ok then, thank you for the advice. The stock boot.img files I've used haven't brought back stock recovery though. It says no command with an android on its back. Could you please point me in the direction of a proper stock boot.img I could flash? I don't care about losing root. Also, I tried using blank flash for my device (I'm not entirely sure what that does though as I haven't yet gotten it to work) but it always hangs on <waiting for device>. Any advice?
Click to expand...
Click to collapse
That us stock recovery. Press power and vol up at the same time. It is very wonky and barely works correctly. Takes me a few goes at it before the recovery menu pops up.