I have a rooted HTC Hero (Sprint) and during preparations for upgrading to CM7 I ran into issues with ROM Manager.
First, I backed up everything (apps and data) via two different methods. I cleared davlik cache, and then performed a CWM Flash Recovery backup. Once that completed successfully, I sought out to apply the CM7 ROM. I selected it from the GUI menu, rather than rebooting into the Flash Recovery. I selected to backup everything and then wipe the data/cache. During the process, the phone hung (white HTC screen for over 10 minutes). I could reboot successfully after this, and selecting "Recovery" didn't work either. I figured my phone was bricked. But miraculously, it managed to finally recover.
The recovered ROM was a fresh clean slate. So, I installed ROM Manager and Titanium backup again. However, when I tried to reboot to the CWM Flash Recovery, or even try entering the CWM CUI menu from power up (by holding the HOME key), the phone hangs. Something is seriously screwed up with ROM Manager. I'd like to wipe it completely clean and start over, but everything I've tried results in a phone that hangs. I'm now thinking I should use a different program for managing the ROMs... but, being familiar with ROM Manager and seeing other people use it successfully, I feel determined to make it work. Any suggestions?
I would just flash an RUU and start from scratch.
https://docs.google.com/file/d/0B9lyYjZr_O3gZnJrRVFqRmh4eVU/edit
I was able to recover.
What I didn't realize is that the first boot can take upwards of 20-30 minutes. I pulled the battery after around 15 minutes, thinking my phone had hung.
Anyway, when I selected "Recovery" again I left the phone alone and eventually I got a stock ROM again. Whew!
While ClockworkMod is fine for 2.1, when you're on 2.3 there's no question that TWRP is the way to go. I've flashed it to my phone (did "flash_image recovery [recoveryfilename.img]") from the terminal window and it's working great, far more extensive than ClockworkMod.
Related
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
bradels said:
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
Click to expand...
Click to collapse
myrobelle said:
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
Click to expand...
Click to collapse
Thats too bad guys,and i m sorry to hear that news.I would like to havean answer but i dont...
The fact is that since most people in this forum use some custom roms,and all of us think the same,that we can always go back,so it would be great if you give some more details about what happened to you,and mybe why it went wrong,and it would be even better if one of the BIG guys would give some explanation about this...
I already thinking of not updating my rom anymore,dot want to end up in looping too,so lets see if someone will find something.Good luck guys..
By the way,i didnt get it right,CWM recovery cannot load your backup????
I just got an idea,but not sure if or how it would work or not.
Since you can push file with ADB,if soeone made a clean backup with his CWM (o e mail,contacts,setting saved) and send it to you,so that you log in with CWM recovery and flash that ???
Just an idea..maybe stupid dont know...
Its not very clear if youve tried this already but cant you just boot into recovery through adb? or does that not work either?
Is it possible? if so how is everyone getting into recovery mode on the ZIO
Code:
adb reboot recovery
Warning: This is the same as hitting "factory reset" in android, so you WILL wipe your data/cache upon reboot to recovery, so back ur stuffs up.
Recovery is essentially useless to us until koush gets clockworkmod recovery working for the zio (he has a couple images on his site already, but they do not work).
Kyocera has brilliantly tied in the factory reset feature of android to the recovery partition. This is why koush's recovery isnt working. I have flashed the recovery to the boot partition and ran it fine, so I know the image works, theres just no work around (as of yet) to the factory reset problem.
That is what I was afraid of. I had attempted several times with different key press combinations to no avail. Then I used ROM Manager to put it in recovery and it just wiped the phone, I of course had my Titanium back up ready to go so...... no worries. oh well guess I will keep messing around then.
I am currently trying to reinstall a new ROM on my phone because all other ROMs have ended up deleted due to my stupid mistakes. However, everytime I choose install zip from sd card, mount, or factory data reset, in CW recovery 6.0.3.0 the phone shuts off and inevitably ends up in the bootloader. I have tried to sideload a ROM and then aroma installer loads up but as soon as i get past the settings and options and the installation begins it shuts off again and goes straight to bootloader. Can anybody help me with this. If I try flashing TWRP with the all in one tool it simply refuses to load period, so at least CW loads...
Hi,
So I had my ROM rooted, and I was messing around with the Xposed settings. I flipped a switch, the phone rebooted and it wouldn't boot anymore...
So I decided to go ahead and just flash a new ROM (ARHD 10.2). To my surprise, when I try to touch the sdcard partition or the data partition, the phone automatically reboots. I wiped everything (except sdcard and data, because I can't touch them).
I tried to sideload the ROM with no luck.
My phone is a VODAP304, HTC One 32 Gb. I can use fastboot USB and the recovery (latest clockworkmod touch). However, like I said, I'm unable to flash a ROM because I can't do that from the sdcard, and if I try to sideload it, when installing, it instantly reboots.
What can I do? Am I bricked? I'm really worried as I need this phone in a week or so because I'm going to be away from home for a few days
Hi everyone! I have been suffering with this problem for 2 full days on my S10 (SM-G973F/DS) and now i just have absolutely no idea how to fix it, so I thought it was worth writing about it here.
On stock, I used one old and outdated application that made user certificates system certificates, but which worked. Having tried it on EvolutionX 5.9.1 (Android 11), it brought the phone into a bootloop. I didn’t have a backup and because in order not to go through the installation process on a new one again, I decided that I would try to delete the folders from the data partition ONLY, but after half a day of attempts, nothing happened and I started to install the rom from scratch, but then weird things began to happen: after reinstallation/factory reset, boot animation randomly started (check attached video), which either went into an endless boot, or loaded the system back, but then if boot animation started on loading then this loading become endless, and the buttons (in the system) "Reboot to recovery", "Reboot to bootloader" and etc simply turning off the phone without booting into the recovery or bootloader, and if this happened, then somewhere in 2 minutes after turning it off.
I think i tried almost everything: re-installation according to the instructions, re-installation according to the way I did it before, I even tried to install the stock, and after the recovery again and then rom, but absolutely nothing changes, I cannot use custom rom if it is up to this worked fine and everything started on the same version as I was trying to install like before, I even tried to download the rom installation file again, not installing magisk-patch in boot, installing multidisabler, even find my old backup for TWRP that has every partition, but absolutely nothing changes, maybe someone knows how to fix it?
Thanks in advance!
P.S Stock rom works perfectly (android 11), but i want to use custom anyway (also android 11)