Ok so its been two years with this phone, I've droped it a hundred times. So this is what happened. I tried to load a new Rom and it didn't load,so I tried to restore the backup I had and got errors.tried that with three different backups with same result. So I did old faithful and restored back to no root original state .7 phone is s-off. Went through steps to root via cyanogenmod. But it will not let me install a recovery. Tried cwm and ra manual but no luck keep getting errors. Then I tried to download Rom manager but I keep getting parse error. This has been with at least 50 different apks. Still no recovery.
Could it be that I have just reacheda limit to the phone? I've rooted this thing countless times. Don't know what else to try.
Thanks
What were the errors you received?
#Root-Hack_Mod*Always\
the error i got was when i got to "flash_image recovery recovery-clockwork-2.5.0.7-heroc.img" :
adb push recovery-clockwork-2.5.0.7-heroc.img /sdcard/recovery-clockwork-2.5.0.7-heroc.img
adb shell
su
cd /sdcard/
flash_image recovery recovery-clockwork-2.5.0.7-heroc.img
reboot recovery
and it said file not found,this happens on either cwm or ra.
flash_image: not found
Install flash_image. See here.
thank you worked like a charm. now on to my next problem which is to figure out why i cannot flash a rom or a backup.
just to let you know before i start looking around the forum is that when i resore a backup i stay in checking md5 for two minutes and then it says it cannot flash boot image, and when i try to install a rom i get two different results,1st. is that it installs fine and then when i go to reboot it bootloops htc screen and then goes back to recovery. 2nd. is that it tells me again that boot image error.
but again thanks for getting me to have a recovery.
I would try downloading either the recovery or ROM again just in case your download is corrupt. Or try a different recovery image...this one is working well for me.
Related
Hi guys. I don't really know what happened here. I've flashed a few different versions of Cyanogen's builds onto my MT3G without any problems. Today I flashed the official 1.6 dev build of Donut before doing Cyanogen's 4.2.3.1 flash. Well, the 1.6 seemed to go smoothly, but after the reboot, the recovery would no longer load. It's now giving me a picture of the phone with an exclamation point when I try to load the recovery.
How can I fix this? Anyone? Please?
taken from cyanogens website site instructions.
If you boot the 1.6 image it will install the HTC stock recovery. Booting back to recovery will show the /!\[] symbol. THIS IS NOT LOSING ROOT. You can still flash update.zip files from this recovery. Also, you can still flash a nicer (CM-1.4) recovery with fastboot, or flash_image inside the CM install once you get it installed.
thats what sounds like happen to me
How do I do anything though? I don't have the ability to do anything, it just sits there on that screen.
<edit> Also, I can't re-flash the recovery. I've tried, but it gives me the error:
Flash FAILED: The command could not be run
After figuring out how to install ADB and trying to fix it via that, it appears that I have somehow lost root. It's giving me Permission Denied or remote device not allow when I try to flash or use fastboot.
Got it fixed. Took me forever, but I made a goldcard and flashed with the stock ROM. Now I'm good to go again after installing CM recovery 1.4.
running latest cyanogen 5. I installed rom manager and flashed the clockwork recovery, which wouldn't work. I then tried to roll back to RA in the terminal, and no matter what i do, i get an out of memory error. I've cleared every cache, and deleted every file i'm comfortable with deleting in the system folder. I cannot get into any recovery console at all, so i can't even restore or flash another rom. What the hell do i do? I can't even hard reset. In addition to that, the drivers error out no matter what on my computer, so i can't fastboot usb.
I had a similar problem with Clockwork not working. However I was able to easily reflash RA recovery in fastboot. Perhaps try reinstalling your drivers and try fastboot again.
If you still have problems, you could always try another computer?
Same thing happened to me. Fastboot fixed it. Perhaps a second reason to not trust clockwork.
Bradart said:
running latest cyanogen 5. I installed rom manager and flashed the clockwork recovery, which wouldn't work. I then tried to roll back to RA in the terminal, and no matter what i do, i get an out of memory error. I've cleared every cache, and deleted every file i'm comfortable with deleting in the system folder. I cannot get into any recovery console at all, so i can't even restore or flash another rom. What the hell do i do? I can't even hard reset. In addition to that, the drivers error out no matter what on my computer, so i can't fastboot usb.
Click to expand...
Click to collapse
There is no need to open a new thread for something you can post in the CM5 thread.
firstly, wrong section - this belongs in QnA
secondly, in rom manager, at the bottom there is an option to install an "alternate" recovery image - Amon_RA 1.6.2
this takes a bit of time, so be patient
i had the same issue when i tried clockwork a week ago and couldnt get fastboot to work (no matter how hard i tried) when it had been working fine before that
moved to Q&A, best
If you want to remove rom manager and clockwork, try using the fastboot and use the command.
Fastboot erase recovery
and try to reflash the RA recovery.
Fastbot recovery nameofrecovery.
and see if it help's.
Alright, I give up.
I've wasted one full day and all I do is keep going in circles. I have an unlocked bootloader but I am not able to flash custom recovery to it. When I do:
fastboot flash recovery recovery-RA-passion-v2.2.1.img
it is successful but am having the problem mentioned here:
"Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android)."
http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638
So, no custom rom because I cant turn off verification in order to flash custom rom zip file. Now the problem is that I can't even fix this problem because I don't have root so I can't delete the following files:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
When I try adb shell it keeps saying "permission denied"
It gets better - I've managed to mess things up royally even further. I tried flashing FRG83 system image using "flashboot update update.zip". It was successful but now my phone is going in boot loop!!
Can someone please help me before I lose hope in humanity?
Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to...
You can either flash a pre-rooted GB, flash the su.zip and then you'll have su access to delete the files when in system or adb, or flash this zip which will remove the two files...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA App
danger-rat said:
Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to...
Click to expand...
Click to collapse
I totally did not know this. Thanks a lot buddy
So starting with a functioning CM7 and CWMR v2ish...
I started this whole adventure trying to flash a new recovery via adb and got a "mtd: not writing bad block at 0x001c0000 (ret 1 errno 2)" error and have ever since been unable to boot into recovery.
I'd like to wipe everything and start from scratch but I'm having some problems: cannot flash really anything without errors and cannot get into recovery. Installing recovery through rom manager pulls errors. Cannot flash HERCIMG.zip without error. and I'm stuck with s-on. but no recovery leaves me at a loss for getting s-off... the phone boots fine normally and into bootloader and is visible to adb.
any help would be great!
Hi
Have u tried the old school ruu from HTC via USB plug in?
Its the slowest but most reliable.
Have u tried a different recovery?
Not a new cmr but an older one....
Or
Try RA recovery which is available thru ROM manager.
Sent from my HERO200 using Tapatalk
Download any recovery image on here and extract the recovery.img file and place it on the root of your SD card then issue these commands in terminal emulator:
su
flash_image recovery /sdcard/recovery.img
私のEVO 3Dから送信される
dastin1015 said:
Download any recovery image on here and extract the recovery.img file and place it on the root of your SD card then issue these commands in terminal emulator:
su
flash_image recovery /sdcard/recovery.img
私のEVO 3Dから送信される
Click to expand...
Click to collapse
+1. Make sure that you're recovery image is named recovery image, or make sure you use the right name of that image. Some might have numbers as well. It won't work it's not right. That could be what happened the 1st time. I know from experience. Go s-off next so you can use a HERCIMG.
You think Meth is bad? Try being a flash whore with a Gingerbread habit and a legacy device! It ain't pretty.
noriyori said:
So starting with a functioning CM7 and CWMR v2ish...
I started this whole adventure trying to flash a new recovery via adb and got a "mtd: not writing bad block at 0x001c0000 (ret 1 errno 2)" error and have ever since been unable to boot into recovery.
I'd like to wipe everything and start from scratch but I'm having some problems: cannot flash really anything without errors and cannot get into recovery. Installing recovery through rom manager pulls errors. Cannot flash HERCIMG.zip without error. and I'm stuck with s-on. but no recovery leaves me at a loss for getting s-off... the phone boots fine normally and into bootloader and is visible to adb.
any help would be great!
Click to expand...
Click to collapse
I have a Zip file that can be Flashed from RomManager to give you S-Off!
PM me your Email, and I'll Send it to you!
I found a signed (I THINK....not 100% sure how to tell as I'm S-OFF at this point) HERCIMG.zip that's from a stock RUU. PM me if you want it. I'm 99.8% positive I used it to flash back to stock as a normal RUU won't work for some strange reason when I was still S-ON.
After flashing the latest TWRP 3.3.1 image file from TWRP 3.2.3 and upon reboot I got an error "Could not do normal boot" and it took me to ODIN mode. Thinking maybe it was a corrupt file I flashed the .tar file from Odin and it successfully completed and rebooted into the system. Okay great. So I tried to boot into recovery from the system and it took me back to the same error. Tried several times to flash recovery from Odin and each time it completes successfully, boots into the system. Everything looks great and works - until I try to boot into recovery. Tried powering down completely and giving it a few minutes but the same thing happens when I power up. the only way I can get back into the system is to flash the TWRP tar file again from Odin and let it boot the system upon finishing.
I have searched the forums and the web without finding any solution that doesn't include going back completely to stock. In those cases the system was corrupted as well. Not really wanting to do that since everything works except booting to recovery. Any suggestions?
Update - I was finally able to download XAR-T813XXS2BSJ3_T813XAR2BSA2-20191016 and install it so I currently have the latest stock I can find for my T813. I have not tried to install TWRP yet on this version. I am a little leery to do so at this point since I've had no luck on any previous attempt.
Well, SSDD! No matter what version TWRP I flash, when I try to boot into recovery I get "Recovery Booting....Could not do normal boot" and it takes me to download mode (Odin Mode). I give up. I guess I am doomed to using a stock tablet and all of my previous apps and set up is no longer accessible. If by some miracle somebody has a fix I'm all ears.
Update - Finally was able to root with CF-Auto-Root through Odin. While it is not my root method of choice it is the only way I can root since TWRP will not load for me. At least I can get to my TB backups and restore most of my apps. Also, I can get rid of the bloat that pure stock sticks on the tablet. If I hadn't just bought a new laptop, I would seriously consider replacing this tablet.