Months ago I flashed a Modaco custom ROM to my friend's San Francisco. There haven't been any problems of late, however today I attempted to flash a Froyo build so he can try out C2DM apps like Beejive and Facebook and I was unable to load up a recovery screen. When holding Vol DOWN and booting I just got a white rectangle with FTM inside it - indicating that there was no recovery image installed.
I tried flashing Clockwork Recovery with the ZTE Blade Recovery Manager 2.9 but it kept saying 'Unrecognised' after selecting the .img file, no matter which one I used or whether I changed the name or screamed 'hail Mary'. I attempted multiple reinstalls to no avail.
The device is rooted so I tried using Terminal from the Android Market and flashing the recovery image but although it didn't come up with any errors I was still unable to boot into the recovery image. All it does now is show a green android the same as it would if pressing VOL UP when booting.
I've even tried installing with fastboot for mac, but despite being able to input the necessary commands, fastboot doesn't flash the device and just sticks at 'waiting for device' when the recovery flash command is executed. I've tried connecting the device a number of times, rebooting etc. I have no other USB ports available and no access to a Windows pc at present.
Can anyone assist here? The phone still works fine with the Modaco ROM but it's a bit annoying if that's all he will ever be able to use now!
Thanks in advance.
Japanese_Jellyfish_RLS9_image.zip should be easy, and it installs recovery as well. Please read how to install it.
I just got the new CWM recovery update through Rom Manager today, and it said it was successfully flashed, but the phone only hangs on the HTC logo when goingto recovery. I can still do fastboot and boot to Android tho, so I'm now gonna try to figure out how to get my recovery back before something bad happes xD
anyone have advice or know where I can download a standalone copy of CWM 5.0.0.1 for G2?
Wish me luck I'll keep updating as things progress
okipokey, solved my own issue. Just had to reflash back to an older recovery and try again a couple times before it stuck.
Time to test out the new recovery!
I decided to flash the upgrade as well. The flash went perfectly. However, I couldn't boot into recovery while within Android. I had to power off and boot into the bootloader and then select recovery... Whenever I tried to reboot to recovery via the Android UI, it restarted and hung at the boot splash screen.. It didn't even work if you selected the option from the ROM Manager itself... I rolled back to previous version as well and its working again. It may be a bug... Early adopters nightmare....
Same here just reinstalled the new version and it worked second time round
must be a bug they havn't quite worked out. Next time I'll do a fastboot flash instead for a low build number.
First time I flashed I tried it from a battery pull through HBOOT and it still hung. Reflash to 3.5 and then back to 5.0 fixed it like you guys
epolaris said:
I decided to flash the upgrade as well. The flash went perfectly. However, I couldn't boot into recovery while within Android. I had to power off and boot into the bootloader and then select recovery... Whenever I tried to reboot to recovery via the Android UI, it restarted and hung at the boot splash screen.. It didn't even work if you selected the option from the ROM Manager itself... I rolled back to previous version as well and its working again. It may be a bug... Early adopters nightmare....
Click to expand...
Click to collapse
try just reflashing version 5 I had the same problem,but rebooted the phone reflashed version 5 from the rom manager and now is all good
I just sent the dev a comment about it on his Google+
maybe he'll have a fix out soon
Nice one, seems a "double flash" fixes it have just tested 3 or 4 times,seems to be working
yessir, seems to me that if it's a bug its really minor. I can see this being a problem if someone accidentally screws up something on their phone right after flashing the recovery, but not very likely and they'd still be able to reflash through fastboot
Seemed to flash the new version ok. But then, when trying to boot into recovery for the first time, the phone hung on the HTC logo boot splash. Pulled battery, and booted into recovery ok after that.
that's interesting that some of you didn't hang after the battery pull while mine did. Maybe it depends which version we're upgrading from?
stuck at htc
hey i also had this problem and i can't get my g2 to boot up at all. It hangs at the htc screen. I don't know how to fix this issue as i was trying to restore a backup from recovery right after the update. i can't get into recovery or anything else...all i get is the htc screen. Any ideas how I can fix this?
Luis
Any sign of a changelog?
I have no idea how to get to a changelog...can you tell me how?
biglou421 said:
I have no idea how to get to a changelog...can you tell me how?
Click to expand...
Click to collapse
found this
-From Mr.Dutta via G+
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
So far no issues here while playing around.
my issue is i can't get back to android at all now. i went into rom manager to restore a backup and was told there was an update, then it reflashed the recovery. When i tried to restore my backup it froze and i have not been able to get past the htc screen at all.
biglou421 said:
my issue is i can't get back to android at all now. i went into rom manager to restore a backup and was told there was an update, then it reflashed the recovery. When i tried to restore my backup it froze and i have not been able to get past the htc screen at all.
Click to expand...
Click to collapse
can you get into the HBOOT?
pull the battery, put it back in, hold the volume down button and then hit the power button. you should come to a white screen with some options
In the case you want to update your recovery using fastboot method, heres what you'll need:
CWM 5.0.0.1 for G2 (Vision)
HTC Sync drivers
ADB fastboot from Android SDK
Make sure your phone is all the way off by pulling the battery. Get into the HBOOT by holding down the volume down button and then hitting the power. use the volume keys to navigate and the power button to select. Choose "FASTBOOT"
Rename the recovery that you downloaded from CWM to "recovery.img" and put it in your ADB and Fastboot folder
plug your phone into your computer and pull up a command line for your adb/tools/ or adb/platform-tools/ folder where you should have ADB and Fastboot.
under the command line type in:
fastboot devices
<list of devices>
If you do not see your device make sure the cable is plugged in and your drivers are installed. if still nothing try a different cable til you get it to be recognized by the computer.
Once it's recognized do:
fastboot flash recovery recovery.img
when its done:
reboot
I flashed through ROM manager. On suggestion, I checked the box for "erase recovery - recovery will be erased prior to flashing". On first reboot to recovery it sticks at HTC screen. Pulling battery and vol. up+power then entering recovery the 2nd time works just fine.
Hope this helps.
right so i have twrp 2.2.1.4 and made a backup, flashed cm10 (no gapps), tried to boot, nothing but a black screen. so i held the power button and vol down to get into bootloader but idk what to do from there because clicking "recovery mode" sounds like something other than a boot into twrp and fastboot commands aren't working. can someone tell me how to get this working again?
also when i tried restoring a backup via twrp before i wasn't able to boot cm it would just reboot twrp and not restore...
Edit: nvm i fixed it. i thought recovery mode would put it in something similar to dfu mode on ipods but clicked it anyway and got to twrp still can't restore my backup tho...
Edit2: ok now found out that 2.2.1.4 was a bad release. went back to 2.2.1 and all is good
Hi there,
I wanted to install latest CM10.1 coming from 0526 yesterday on my Defy+.
Did a backup with TWRP first.
Then the flashing failed, so I wanted to recover from backup.
Phone now is stuck at Motorola M not booting anymore.
When I enter bootloader (vol down) and want to enter "custom recover" he just jumps back to the same menu. TWRP is not starting.
Choosing "stock recovery" is possible, but if I choose a CM10.1 zip file it's not accepted.
RSD Lite does not recognize the phone when it's in the bootloader menu or in the stock recover menu.
Help is very much appreciated, what can I do?
Thanks and best regards.
are edianKa
[Idiot mode=on]
Okay, I found out why I couldn't enter flash mode by using Vol+ when starting.
The phone powered already up when I put in the battery, so I always pushed Vol+ too late.
Pressing Vol+ WHILE inserting the battery did the trick, phone went into flash mode and I could re-flash 2.3.6 sbf using RSD lite.
[Idiot mode=off]
Still not sure why TWRP was messed up just by recovering from a TWRP-made backup...
Best regards
Same situation to me.
I opened Terminal Emulator, gained root access
then type below command to get recovery mode
# reboot recovery
Custom recovery not running
I have a similar issue.
I rooted my stock S4 and installed the proper TWRP.
Heres where my situation is a bit different from anything I have seen on the forum threads. All attempts—both hard and soft—to reboot into recovery, all direct the reboot to Odin Mode. Just to clarify I have not flashed any rom custom or stock, the only thing I have flashed has been TWRP and CWM recovery. And I only flashed CWM AFTER the Failings of TWRP.
When I attempt to boot into recovery, it flashes the blue characters then sends me into a Odin Mode loop until I hard-key the "download mode" and select restart to boot the os normally.
my phone works fine other than not being able to flash custom roms, which is a pain in the arse especially with all the s4 Bloatware.
Here's what I have done so far to help myself:
• install CWM recovery
• tried hard-key reboot recovery (power off/ press home/volume up/power)
• soft reboot recovery through both Goo, CWM and ROM Toolbox pro
• removed my sd card and tried reboot recovery
• removed battery and reboot recovery
• emulator reboot recovery
• reboot recovery both with and without usb cable
I looked into flashing stock with Odin but all tutorials i could find were of an older version and I didnt want to guess what I needed to get that to work,
Please let me know if theres anything I can do.
(Verizon) Samsung Galaxy S4 jfltevzw
Hi,
I was on stock bootloader and stock OTA 4.03 ICS rom. I wanted to upgrade to jellybean rom from tegraowners. I am now stuck in recovery mode.
Here are the steps i did.
1) rooted my A500 succesfully
2) With the Blackthunder APX flash tool i flashed in auto mode the Skrilax_CZ V8 bootloader (with multiboot) also succesfully.
3) Then i flashed with ADB.exe the 1.8.1 Touch recovery image that also went well and succesfully flashed it.
4) Booted in recovery mode and wiped data.
5) Went to install from external zip the latest jellybean rom from tegraowners wich is ofcourse on my sd card.
6) It started to formatting my system partition ( i think it was on 7%) and then it suddenly restarts my tab.
Now the only thing i have is power + -VOL is my recover mode and power + +VOL is my other menu i have wich contain the fastboot menu.
From there i am stuck and don't know what else i can do.
I do have my UID number and SBK.
Here is a screenshot of what i have in recovery mode:
Thanks and hopefully someone can help!
You will have to do a "real" data format. And for more help with ROMs from "other" forums you should ask on those "other" forums.
You will find the moderators here do not condone those "other" ROMs.
Perform a real format, then flash a ROM again (you'd better go to Tegraowners.com for more support), but if the problem persists then it may be a bad download, which means you have to download and flash your recovery again. However at TegraOwners you can also find the latest TWRP recovery.