Hello,
I went to flash a new ROM today and it didn't go well. Coming from Cloudy G3.
Running CWM v6.04.4
Downloaded Resurrection Remix and GApps. Wiped then flashed ROM then GApps. Went to restart got a prompt about fixing root, accepted. Not sure if that was my problem.
Upon attempting to boot for the first time it just kept looping to the LG start screen after 20 seconds or so.
Used the hard keys to try and get back to recovery, instead of recovery I got a Factory Hard Reset screen and it noted Rooted in the upper corner. Not having any other options I proceeded with Factory reset. It then drops me back into CWM.
Went to reinstall the ROM and my SD card is Empty/Blank.
Not sure where to go from here.
Thanks
Related
I've tried repeatedly to install CM7.2 and keep getting stuck on a blank screen. I'll see a "CyanogenMod" then "loading..." right below that. Then it goes blank and nothing ever happens after that.
Some background info. I've had CM7 installed on this in the past without problems. Months ago I went back to a rooted stock. Then yesterday I decided to try CM9 alpha. That installed perfectly. But it was too slow, so I decided to try CM7.2.
I used the same CWM 1GB boot SD, copied "encore_CM72-MiRaGe-02012012.zip" along with the Gingerbread Gapps and CWM. Installed in the same order and wipe data/factory reset.
So I got stuck on that blank screen after the CyanogenMod loading... message. I then decided restore to stock. Installed the 1.01 stock image. It also wouldn't boot up, but I powered it on and off 8 times and it did a factory reinstall and then it booted up normally.
Once back at a factory fresh system. I powered it off and tried installing CM7.2 again. Unfortunately I'm having the same problem again. Ugh, why won't it load now.
Hang on... I might be in the process of making a newb mistake. MD5 didn't match on my SD card, probably the ROM.ZIP is corrupted. Trying again with a good copy.
That was it. It's working now. Please disregard my idiot on the Internet moment. Thank you.
You always figure it out five minutes after you finally give up and post for help/venting.
Been there.
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.
I was running CM 9 nightly builds for the last year, and decided to upgrade to CM10. In my system settings there was a handly little "upgrade" button which I mistakenly used- and my phone got stuck in a reboot loop. I booted into recovery mode, and tried to restore the phone, but it did not work. It kept sticking at the blue circle boot image for over 20 minutes.
I tried recovery mode again, and every time I went to CW recovery I would get several lines saying can't mount SD card. OK, I broke it.
I then downloaded the factory firmware from samsung-updates.com - and flashed with Odin- just to get my phone to work. It's been 2 hours where I cna't get anything up. After rebooting (from factory firmware) I have the regular samsung s repeatedly coming up, and I'm still in a reboot circle.
Any suggestions or ideas? I need my phone for work, so I really just want to get it up at this point, with whatever will work.
I found the EZBase recovery kit thread, fixed myself Of course, it's the 101th thread I read in my search!
http://forum.xda-developers.com/showthread.php?t=2095519
Sorry, next time will keep searching. Worked to get my phone up and running,w ill now attempt CM10 again...
Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter
So i wanted a new rom for the awesome features so after i had rooted and installed twrp custom recovery i downloaded cm12 then created a nandroid. I put my phone into recovery wiped everything except internal storage and installed cm12 and gapps. This is where my problems started, as much as i liked the new rom it wasnt connecting to my cellular network so i thought ok ill just recover my nandroid so i wiped everything except the internal storage and then started the recovery when it finished i rebooted and it goes to the warning bootloader unlocked screen and sits for about 15 seconds the goes black and repeats. My phone is a motorola moto x 2014 victara, any help is much appreciated.
Please give us more details:
1) can you access recovery? Try holding the "power" button for like 20 seconds and trying to reboot into recovery when the phone boots.
2) can you access fastboot mode on the phone? maybe you lost your custom recovery but can access the bootloader and that makes things easier.
3) what is your device number? (xt1097, xt1095, xt1092, etc)
You are going to want to factory reset. Most times coming from a customer rom to another or even back to stock you will need to do a factory reset in order to wipe out anything that may have been left over that could cause issues.