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.
Related
Bought a new color nook two days ago and began rooting it after i bought it using the walkthrough here. I made the bootable SD and that went fine. Put the Zip for nooter on there and that went on fine. I got on and created an account with the android marketplace and all. Then I got the Cyanogen mod from their site, the latest stable version and tried to install it. Got stuck at the color splash loading screen. Turned the unit off and have been constantly messing with it and got it to boot to CM7 but i have no google apps and when i press the home button i am still getting 3 options (Zeam, Softkeys, and something else).
I have tried numerous times reloading MN but it will get stuck at the n screen and not do anything. Sadly my idiot self didnt make a backup before i started rooting and the erase to factory in CWM doesnt do much.
Any ideas? It seems like i might be able to just get by with getting the gapps and putting them on but i dont think it will be that easy...
Thanks in advance for the help
UPDATE: Got the gapps to install but everytime i try and go to something in the market it force closes. Sounds like i need a wipe and start over but i am not sure..
make sure you have a class 2/4 sandisk(brand is what counts here).
Otherwise, I'd just reinstall everything over again through your cwm recovery disk.
As easy as it is to flash back to stock I just don't see the merit of running CM7 off a micro SD. Yes, it can be done, but if you're new to rooting your Nook my suggestion is to start over, wipe everything and install to internal memory.
I finally upgraded my wife's Verizon Tab to the 7/25/12 CM9 nightly four days ago. In that time, she's experienced two random sleep-of-death instances, from which I succesfully recovered. Today, however, she put her Tab down after using it for a bit, went back to it later, and it was off again, and very warm. She plugged it in and tried to re-start it, but it would hang on the CM9 splash screen forever.
I tried to re-start it and got the same results.
Then I tried booting into CWM Recovery to reboot from there, but got the same results.
I tried to fix permissions in CWM, but CWM became unresponsive.
I rebooted into CWM again and tried to restore a nandroid, but it failed since /data couldn't be mounted.
I then tried to flash the 7/28 nightly, but it couldn't mount /data either.
I used Heimdall to reflash Recovery and kernel (5.0.2.7 if I remember correctly) I had used to upgrade to CM9, and then tried to flash the 7/28 CM9 again. This time, after a very quick flash sequence, and a very long time (20 minutes) on the CM9 splash screen, it finally moved on to the boot animation, and eventually booted...right into a screen that said "Encryption Unsuccesful."
Per that screen's instructions, I elected to do a factory reset and reboot. After a very long time, the Tab rebooted to the same error screen.
Bottom line is, I've since learned the "Encryption Unsuccesful" bug is an ICS one (especially with unofficial ROMs), and it does a number on your internal and external data partitions/SD card. I was lucky in that the SD card didn't get wiped, but my Tab is unrecoverable. My latest attempt is to load a rooted stock Verizon ROM/recovery/kernel using Heimdall, but after almost an hour, I've just made it to the "Verizon Wireless" boot animation. Most threads I've read on this issue end up in dead-ends, and I couldn't find a single one that pertained to the Original Galaxy Tab, much less Verizon's.
Does anyone have any ideas as to what else I can do?
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
uvii said:
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
Click to expand...
Click to collapse
I suggest flash 3-file GB rom via odin with ticked re-partirion and phone bootloaderupdate.
First of all init.d has nothing to do with the boot of kernel and ROM itself. It's just like autostart in Windows, so if it's missing it shouldn't cause problems.
My solution is to flash a complete stock Gingerbread ROM using Odin. You can get them at sammobile.com. Then afterwards flash a custom kernel and then whatever you like.
If you need help,feel free to ask me
Sent from my Gameboy Color
Yes! Thank you! That worked!!
It happened again! just 10 days later.
Is the Infinidtum rom ****ed up in any way?
it's stuck on the loading part of the rom
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,
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