I am looking for a 2.3.4 stock recovery image for a Nexus S (USA T-Mobile model). I am needing this for a friend who rooted his and has decided to un-root it and wants to go back to stock 2.3.4 with GTalk.
I would like a recovery image I could just restore or flash from clockwork and it takes everything back to stock including including the recovery image and I can re-lock the bootloader when I done. Any help would be appreciated.
Doesn't the T-Mo Nexus S have a install-recovery.sh script? In other words it should overwrite the custom recovery with the stock recovery evertime you reboot the phone.
If that's the case, there are only two things you need to do to revert back to stock
1) Remove the superuser/busybox package using adb (got this from another thread)
adb devices
adb shell
su
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/bin/busybox
rm /system/bin/rootshell
reboot
Click to expand...
Click to collapse
2) lock the bootloader (fastboot oem lock)
Related
I have tried to flash using terminal.
su
flash_image recovery /sdcard/recovery.img
but i just get a message saying no permitions
Ive copied the Flash_image file into system/bin
any ideas im trying to flash a recovery so i can flash 2.3.3 without fast boot or a pc
Im on the LG GT540 using the Baltic 2.1 rom but no fastboot
Sent from my GT540 using Tapatalk
Had Tiamat xoom 1.1 + Tiamat Kernel. Trying to get back to stock
I have tried to flash the .img files several times. Boot, recovery and userdata all flash just fine. However, when ever I flash system I get the following error:
Failed to process command error (0x120000)
anyone have any ideas how to recover from this? I've tried changing usb ports as one thread for a very slightly similar issue stated. Didn't work.
UPDATED: managed to get on stock 3.1.. eventually. huge PITA but it's done.
holtenc said:
Had Tiamat xoom 1.1 + Tiamat Kernel. Trying to get back to stock
I have tried to flash the .img files several times. Boot, recovery and userdata all flash just fine. However, when ever I flash system I get the following error:
Failed to process command error (0x120000)
anyone have any ideas how to recover from this? I've tried changing usb ports as one thread for a very slightly similar issue stated. Didn't work.
UPDATED: managed to get on stock 3.1.. eventually. huge PITA but it's done.
Click to expand...
Click to collapse
I am running into a similar issue. Coming from Tiamet 2.2 + Tiamet kernel I am unable to flash back to system. I can flash boot, recovery, and userdata images, but the system image gives the same error (Failed to process command error (0x120000)).
Could you please share how you made it back to stock (if you can remember, I know it's been a few months
Recover from Failed to process command error (0x120000)
I have tried to flash the .img files several times. Boot, recovery and userdata all flash just fine. However, when ever I flash system I get the following error:
Failed to process command error (0x120000)
Alrighty, it took me 2 days but I finally figured out how to get past this dreaded error.
My Fastboot was unable to flash system.img (but successfully flashed boot, recovery, and userdata) to my rooted, unlocked US Xoom Wi-Fi Only running 3.1, 3.2, and/or 3.21 (yes I tried from all 3 versions using various update.zip methods).
I was attempting to revert to stock using the methods described in multiple threads on XDA, but couldn't get past the 0x120000 error when trying to flash the system.img.
Disclaimer:
This was done on an unlocked, rooted US Wi-Fi Only Xoom running HC 3.1. While this fixed my issue, I take no responsibility if the method does not work on 3G/4G versions, non-US versions, or just plain works differently between different devices. Using dd to flash images is not the safest route, but for me it was the only route.
Prerequisites:
Have adb access (preferably through installing the Android SDK)
Have CWM Recovery installed on Xoom
Steps:
Download the stock HWI69 images from bwcorvus' sticky http://forum.xda-developers.com/showthread.php?t=1049485
Extract the image files into your platform-tools directory in the android-sdk
Reboot into recovery
Code:
adb push boot.img /sdcard/
adb push system.img /sdcard/
adb push recovery.img /sdcard/
adb push userdata.img /sdcard/
adb shell
su (if it doesn't bring you into root # prompt)
busybox dd if=/sdcard/boot.img of=/dev/block/mmcblk1p7
busybox dd if=/sdcard/system.img of=/dev/block/mmcblk1p8
exit
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Follow lock instructions on device
Hey all.
I'm trying to root my Moto G and the Superboot option doesn't work, so I'm trying to flash by recovery. However, I want to restore my original stock recovery afterwards. Does anyone have a link to the stock recovery so I can flash it through ADB after rooting?
Thanks!
http://forum.xda-developers.com/showthread.php?t=2578243
Or you can try second time with superboot by Modaco.
1. Download Minimal ADB and Fastboot here https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing
2. Install it.
3. Extract boot.superboot.img from superboot.zip available from Paul's thread at Modaco - http://www.modaco.com/topic/366771-root-your-moto-g-option-1-superboot/ where you installed Minimal ADB and Fastboot.
4. Start Minimal ADB and Fastboot
5.
Code:
adb reboot-bootloader
fastboot boot boot.superboot.img
So I've managed to make it to Lollipop without losing my locked bootloader and warranty.
I'd like to install the 515 update however its a nerve-wracking process because first boot wipes recovery to stock and if it doesn't boot up with root properly its impossible to go back without unlocking and voiding the warranty.
Is there a way to remove or replace the recovery.img included in an update zip?
I've seen "disable recovery flash" before is that a possibility? I'd feel more comfortable if the stock recovery img wasnt even on the device.
What about using a terminal/adb command while still in recovery to delete the img after installing then DDing recovery over ADB before first boot?
dd if=/data/media/0/recoveryTWRP.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
so i have a mtk device in which i mistakenly flashed a wrong custom recovery using mobile uncle tools. now i have no working recovery in this device & device wont even factory reset as it tries to reboot into recovery mode then fails to boot into corrupted recovery & again reboots into operating system without doing any reset.
so im here to know if there is any way to recover my built-in recovery system or atleast factory reset my device without using any recovery. i have tried using adb but faced the following error:
PS C:\adb> adb devices
List of devices attached
0123456789ABCDEF device
PS C:\adb> adb root
adbd cannot run as root in production builds
PS C:\adb> adb shell
[email protected]:/ $ wipe data
Wiping /data
Error opendir'ing /data 'Permission denied'
Done wiping /data
[email protected]:/ $
Khaled786 said:
so i have a mtk device in which i mistakenly flashed a wrong custom recovery using mobile uncle tools. now i have no working recovery in this device & device wont even factory reset as it tries to reboot into recovery mode then fails to boot into corrupted recovery & again reboots into operating system without doing any reset.
so im here to know if there is any way to recover my built-in recovery system or atleast factory reset my device without using any recovery. i have tried using adb but faced the following error:
PS C:\adb> adb devices
List of devices attached
0123456789ABCDEF device
PS C:\adb> adb root
adbd cannot run as root in production builds
PS C:\adb> adb shell
[email protected]:/ $ wipe data
Wiping /data
Error opendir'ing /data 'Permission denied'
Done wiping /data
[email protected]:/ $
Click to expand...
Click to collapse
You need to obtain a copy of your stock recovery and then flash that copy of stock recovery onto your device. If you can find a copy of your stock firmware, you can try extracting a copy of stock recovery from the firmware and use that copy to flash the device.
Sent from my SM-S767VL using Tapatalk
I have searched a lot and found one copy of my stock firmware (still not 100% sure about the rom) and it contained recovery.bin file (but I need recovery.img) image file to flash with mobile uncle or flashify.
So I used SP flashtool to flash only the recovery file into my device. But it showed some error (PMT has changed of this rom) and failed the flash. After searching for solution, people were telling me to erase my full device including boot & bios with SP flash tool then flash the new copy of my downloaded stock firmware. But I can't take the risk of erasing my device and bricking it (as I already told I have doubts about the downloaded rom)
Droidriven said:
You need to obtain a copy of your stock recovery and then flash that copy of stock recovery onto your device. If you can find a copy of your stock firmware, you can try extracting a copy of stock recovery from the firmware and use that copy to flash the device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
what if the downloaded rom is also corrupted like the custom recovery i tried to flash........ im trying to avoid this kind of risky steps. i have heard mobile uncle tools flashes custom recovery temporarily & the stock recovery is still there somewhere which can be found using root explorer. so i was asking is there any way i can extract that stock recovery from system files and use it OR just any other way to factory reset my device using adb/fastboot
Khaled786 said:
what if the downloaded rom is also corrupted like the custom recovery i tried to flash........ im trying to avoid this kind of risky steps. i have heard mobile uncle tools flashes custom recovery temporarily & the stock recovery is still there somewhere which can be found using root explorer. so i was asking is there any way i can extract that stock recovery from system files and use it OR just any other way to factory reset my device using adb/fastboot
Click to expand...
Click to collapse
I told you what you needed to do, now, you just need to accept it and do it.
Sent from my SM-S767VL using Tapatalk