Okay so I'm really thinking I bricked my phone but I hope I did not! I am phone-less right now.
First, I changed my stock ROM to MIUI Android 2.4.6 but it started to slow down a couple of hours later so I wanted to switch back to my stock ROM. I backed it up on my SD card and when I wiped data and cleared all cache in recovery mode, I went to backup and restore and tried to restore my stock ROM.
It said MD5 sum not found and it was an error. Right now I am stuck on the recovery mode without any other ROM to flash other than the stock ROM I thought was gonna work that was in my SD card. Now that I'm at the recovery mode menu, when I try to select on something, a Android opened box with an arrow coming out of it pointing towards an Android icon is showing up.
EDIT: Problem was resolved by taking out the battery and putting it back in which allowed me to boot back into CWM and flash another rom.
Related
Ok I have a massive problem here. Last night I decided to use the 1 click universal root app to root my phone and flash it to get CM.
I downloaded the app did the root, downloaded clockworkmod then did a clockworkmod recovery. After that finished i was given a pre-root option to backup my phone and wipe data/storage.
I only chose back up my phone. My nexus one then rebooted and proceeded to backup my phone then it went to install CM 6 RC2.. After this had finished it then rebooted and went to the multicoloured animation where the colours ceom from the left and right..
Here it would continuously loop and never do anythign else. With this I pulled the battery and loaded into recovery where I was in ClockworkMod. I then proceeded to use the recovery and as it was doing the recovery it just froze and the progress bar nor any words would come up.
From here I pulled the battery again did a soft/hard reset but it would hang on the loading animation again. I then did a wipe data/clean option and now it just hangs on the X logo.
On my sdcard I still have the clockworkmod folder with the backup, nandroid, system and all the other files as well. Vodafone Australia have no stock of the Nexus One at all and won't be getting anymore in since it's a finished product
I barely have any cash for a new phone and need to know asap what to do to fix this problem! If anyone can help!
When you installed Cyanogen CM6 did you install the proper baseband also or you just didn't write it down for us? If you had 2.2 on the phone before you rooted the baseband is ok for CM6.
Did you try hooking your phone with USB and try if ADB interface works? If your computer sees the phone via fastboot?
IF fastboot works, you could always restore your stock recovery and install a stock FRF91. (And then try again with CM6, this time installing the proper baseband AND WIPING like you should when installing CM6!!)
When installing custom ROMs always read the install instructions whole first then install.
http://forum.cyanogenmod.com/topic/...y-crap-its-full-of-awesome-v600-rc2-07252010/
Hello, I'm new to the forums and I feel bad I'm already screwing things up :/
Anyway on to the problem... I've had CM9 running on my phone for about two weeks now but I wanted to get rid of the rainbows in CWM and at boot. Today I downloaded Rom Manager from the market place, and when I ran it, it prompted me to install CWM recovery to my SD card, although I already had it installed I thought I'd give it a try. Bad idea, now I can't leave recovery mode, my phone will continually reboot into recovery, I've tried wiping all data and clean installing CM9 again and still nothing. I've even tried the exitrecovery.zip script to no avail
Any suggestions or ideas on how to fix it and boot into my ROM again?
Thanks!!
I would venture to say you might have to reflash...or start over from stock...
i would reload stock....then reload ics or the rom of your choice...
Thanks a lot! Worked like a charm, I used Odin and flashed factory stock 2.2.1, now I'm off to getting ICS back.
Thanks again!
Does anyone know why this happens? I've noticed that anytime I open CWM and choose the boot to recovery option is when I get stuck with CWM Recovery looping. I then have to go back to stock and start over again.
I'm not entirely sure why it happens, my guess was that it puts up a bad flag not compatible with ICS that keeps it from booting that, that was why I tired the exitrecovery script, I looked through it and it appeared to me to change a flag for booting. I'm not sure why it happens but I'd say just use the reboot to recovery option that the ROM provides in the shutdown menu, I know that always works.
Well today I took some time to try and figure out why people are having so many issues loading up these nice custom ROMS that the Developers have spent such great time on to make or tablets so great. We'll let start off with first I am no way a Developer and I do understand to processes that are needed to take my Tablet to the next level and recover whatever problems I happen to fall in along the way. After saying that let's begin.
This processes that I did is only for those willing to go the distance on there devices. If this is your first time with installing a custom rom and you where or are running TapUI firmware 5699 or if you happen to reverted back to stock TapUI to get the latest 5699 firmware update and are having trouble with installing new ROMS then this is for you. Others well I guess stick to the Q&A forums for further help, but this might help you out as well.
I went ahead and reverted back to stock using the 1.2 NVflash file found here http://viewsonic-gtablet-for-dummie...sig_permission_level=0&fb_sig_network=fw#2132
This got me back to stock 1.2 with stock Android recovery, not CWM. After the installation was complete I went ahead and checked for update and sure enough there was 5699 update available. So after update I tried loading up G_Harmony_Gingebreadv2.8.2 for 1.2 BL using stock recovery. I changed file name to update.zip like usual and installed it. Sure enough on reboot system it just stayed at the android splash screen, not the bootanimation. So, I thought maybe it's the recovery so I loaded up CWM 3.0.2.8 on its update zip to my internal SD card. Got it going and since I was using it I just left the ROM file name alone and installed it from internal SD card. Same thing happened as before. Was able to get back into recovery and mounts and format cache, data and system and install. Guess what same thing. For some reason I think is that the new firmware changes something that would cause these 1.2 ROMS not to load up. I tried 3 different ROMS without success and all 3 worked before the update. Solution I did was go into current CWM recovery and wipe data factory reset go into mounts and format cache, mount data then format and mount system then format. Go back and reboot system and when the first splash screen shows up hold down the power button to shut the tablet down. Reboot into APX mode and NVflash to fully stock 1.2 with Android recovery and let it boot up the TapUI fully. Then you can NVflash recovery 3.0.2.8 or NVflash 5.5.0.4 beta 15 for DRH. Choose you poison and flash away again without issues. Hopefully this will help other out and if you need the NVflash files I will be more then happy to uplink them or point you in the right direction.
I tried following some guide online to get my S3 rooted and running stock Jelly Bean and all was going so well...Casual Root worked like a charm, cyanogen all set. But when I went to install the ROM and Gapps in recovery it kept getting hung up. I assumed this was due to encryption on the device from my work email, so I went back to factory andremoved the account and decrypted the device.
Then it was back to recovery to flash the ROM and Gapps. All seemed to go well,the ROM installed fine, Gapps installed fine, but reboot got stuck at the cyanagenmod loop. I had mad a backup of the original ROM, but I must have saved it to the internal SD card by accident before i factory wiped. I thought my best bet would be to load the Gapps and ROM onto my external SD and flash from there, but I cant get it to mount.
The one good thing that I can do is get to the Odin boot screen. Anyone think there's a chance I can get Odin to flash something that will boot? And does anyone have suggestions of what to flash?
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
bejahu said:
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
Click to expand...
Click to collapse
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Badouken said:
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Click to expand...
Click to collapse
I tried that to no avail. I unfortunately had to revert to stock unrooted via ODIN mode and it got me to boot back up. I can just reroot now. Luckily I made a backup with Titanium and uploaded it to my Google Drive.