hi,
one of our members in and-roid.ir is facing a strange problem... his phone is s-off and recovery v.3 was flashed.
he was installing a rom and suddenly there was an error in the installation... he tried to enter recovery and restore a back up but when trying to enter recovery from bootloader instead of entering recovery mode it will enter fastboot mode...
he flashed recovery again but no luck...
suddenly when usb was plugged he entered recovery mode... he tried again with usb unplugged and couldn't enter recovery mode...
so after entering recovery mode with usb plugged memory card won't mount... he tried to manually mount it and still no luck...
any ideas what's the problem?and how to trouble shoot it?
any clues at all?
Reflash the misc partition. (you can see how to do this in the root HBOOT 1.00 thread) Or you can boot into recovery...
Go to fastboot
put the custom-recovery.img in your android-sdk/tools folder
fastboot boot (drag and drop recovery.img into cmd or terminal) press enter
so i have to do following commands? correct?
Code:
adb shell
su
...you should have root privileges now (showing #). Next thing is backing up misc partition and replacing it with one from hack4legend-v5.zip. Extract this zip somewhere and fire another command promt there. Now you should upload flash_image binary and misc1-2.img:
Code:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
...switch back to 1st command prompt and change permission of flash_image_binary:
Code:
chmod 755 /data/local/flash_image
...and backup your current misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Now flash misc1-2.img:
Code:
/data/local/flash_image misc /data/local/misc1-2.img
exit
Click to expand...
Click to collapse
I believe so yes
Related
Sup guys, can someone show me how to change a recovery img via 1click root method? Right now I'm using Cyanogens 1.4 which is great but would like to upgrade to the new Amon RA's img. Any help would be appreciated.
TTT back up
Using ADB...
from the command prompt...
where you see recovery.img just type in the file name that you have in plasce of it....
adb remount
adb push recovery.img /sdcard/recovery.img
adb shell flash_image recovery /sdcard/recovery.img
adb shell reboot recovery
Well I need help. Last week when verizon was having probelms with service my friend thought that it was his phone. He got to messing with **** and now he cant load any roms. Im hoping someone can help. When he boots into recovery mood he no longer has the option to flash zip from sd. Also Nand backup is now missing so he can not backup to a restore point. the only options he has is flash update reboot wipe cache and factory reset. I have heard of people losing root but with that would you even be able to boot by pressing power and the volume up key... he wont leave me alone about fixing his problem so any info someone could shed on the situation I would really appreciate... Thanks
leech2082 said:
Well I need help. Last week when verizon was having probelms with service my friend thought that it was his phone. He got to messing with **** and now he cant load any roms. Im hoping someone can help. When he boots into recovery mood he no longer has the option to flash zip from sd. Also Nand backup is now missing so he can not backup to a restore point. the only options he has is flash update reboot wipe cache and factory reset. I have heard of people losing root but with that would you even be able to boot by pressing power and the volume up key... he wont leave me alone about fixing his problem so any info someone could shed on the situation I would really appreciate... Thanks
Click to expand...
Click to collapse
Just redo Amons recovery. That should fix it.
Follow these steps: (Also found in Sticky section)
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
* adb shell mount -o rw,remount /dev/block/mtdblock3 /system
* adb push recovery.img /sdcard
* adb push flash_image /system/bin
* adb shell chmod 755 /system/bin/flash_image
* adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
Once you do this...power down... then volume up + end = recovery..
The behavior of the recovery boot that you are describing is an HTC recovery; it is not Amon_RA. Amon_RA didn't change, it got replaced.
That strongly suggests that "your friend" re-flashed an HTC ROM onto the phone, probably using a HBOOT method (using a "PB00IMG.ZIP" file).
droidkevlar said:
Just redo Amons recovery. That should fix it.
Click to expand...
Click to collapse
droidkevlar assumes here that what got flashed was the HTC Root PB00IMG.ZIP file.
For the sake of "your friend who won't leave you alone", I hope droidkevlar is correct; otherwise your friend has joined the leak club.
Good luck,
bftb0
vash8806 said:
* adb shell mount -o rw,remount /dev/block/mtdblock3 /system
* adb push recovery.img /sdcard
* adb push flash_image /system/bin
* adb shell chmod 755 /system/bin/flash_image
* adb shell flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
or you could do it from the PC with a single command. Put the phone into FASTBOOT mode (power on phone holding down both Send+End/Power), and then
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
The md5sum of Amon_RA v1.6.2 for the Eris is e3932991f097993602af3c7a4b61a4f8
You can check to see if fastboot is communicating with the phone by using the command "fastboot devices". (Note that if running fastboot from Linux, fastboot needs to be run as root to access the USB device).
bftb0
YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html
Description of the Error:
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)
Solution:
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 and fastboot setup (e.g., 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
Plugging into another USB slot solved mine
I had the same problem. 1200003 error.
Plugging the tablet without an extension cable directly in on of the back slots solved the prob.
I'm stuck with only the ability to go into recovery while the rom doesn't boot and backups are stored on the uSD.
It's the Clockworkmod Recovery 5.8.3.4, and it looks like it doens't read from my uSD. I am able to connect via adb and push an other recovery.zip, that does work with the uSD, but it looks like the flashing goes ok, but when i reboot, i just end up in clockworkmod recovery 5.8.3.4 again.
adb push works to push multiple recovery.zip, but when i try with some rom.zip, i get, maybe because of the filesize, a 'protocol failure'.
I tried easyflasher 0.8.3, but it also doesn't have any effect.
Is there anyone who can help me guiding what else i can try or what the problem could be?
Try these steps
1: use adb to push a new recovery file (which you already did)
2: flash the zip
3: use the adb shell to execute the following command
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0