I rooted my Moto Droid easily, and decided to try the Charity ROM (from Droid forums) first. I saved and moved the zip to the root folder on my SD card. I used ROMManager and did the Clockwork Mod successfully. Then I used the ROMManager program to flash the new ROM. Everything went fine, got into recovery mode, loaded, etc etc. It said everything was successful. It went to reboot, and I read it would take 25-30 minutes to boot for the first time.
Here's the problem...it's been in the boot sequence for well over an hour, back and forth to the "DROID" written that morphs from the red image. It just keeps doing that as if it is trying to boot.
Do I wait longer? Or do I need to do something else to get this thing booted?
Thanks in advance!
Well, I went ahead and pulled the battery and went to recovery mode....wiped and cleeared...and it booted great! And the Charity ROM is loaded!!!
Related
ok my phone is stuck in a boot loop after trying to install FRF85B. my N! is a UK vodafone set on EPF30.
I found this guide http://forum.xda-developers.com/showthread.php?t=714016 but needed to unlock my bootloader so i used this guide http://forum.xda-developers.com/showthread.php?t=636795 but missed out the rooting step.
so the unlock went fine. I took the EPE54B recovery from the first link renamed it, copied the recovery.img to the right folder (should i have renamed the zip on the first link to recovery instead of taking the .img?) then wrote it the phone. now im not sure if i was meant to do more at at this stage? should i have flashed the recovery file in the phone?? when i went into fastboot/recovery it gave me a droid with the ! .
through reading the guide i thought it was enough for the US recovery to be on my phone so i went ahead and flashed the phone to FRF85B it seemed to be work it gave me a progress bar then a droid jumping out of a box then and progress bar, it rebooted but the android x kept repeating.
the guide said if you get the repeating logo to wipe from stock recovery and reapply the update.zip. well i dont have the stock recovery on my phone. should i connect to the PC and copy on the original recovery back? how do I use recovery to return my phone to EPF30?
Please help a foolish noob out here. Im starting to freak
By stock recovery, it just means a 'normal' N1 recovery, not a custom one.
This may sound odd, but try taking your SD card out and trying to boot up, this helped with someone on another forum going from stock Voda to FRF85B.
Ok I put the original one on anyway just incase. took the SD card out and restored to factory settings thinking I would go back to EPF30 but when it booted there was froyo FRF85B as if nothing had gone wrong! dumb luck says today I dont have a brick for a phone I entered my google account and before you no it all my apps redownloaded - didnt release the N1 could do that
Thanks for your advice rusty
I'm off to enjoy some Froyo, (screw you Vodafone)
Ok so here's what happened.
I rooted my nook with autonooter 3.0.0, then I installed rom manager to install cwm. I installed the latest version of cwm and I tried to make a backup, it ended up in my nook only booting in cwm. So I found a cwm removal script and removed cwm. I booted my nook and opened rom manager and I decided to try an older version of cwm. I pressed make a backup in rom manager and it just went into a boot loop. I can't really turn off my nook, and I can't really turn it on. It just keeps going to "touch the future of reading", then turns off, then a couple of minutes later, goes back to "touch the future of reading". To make it clear, I do not have a backup.
So can anyone please assist me in fixing my nook? I'm in a dead end here.
Sounds like a boot loop try
Method one: Eight interrupted Boots
1. Power off the nook.
2. Tap the power button.
3. As soon as Welcome to the future of reading appears, hold the power button down to interrupt the boot process.
* If the boot animation does not appear, add 1 to your interrupted boot count.
* If the boot animation DOES appear, your interrupted boot count is reset to zero. Start over.
4. Repeat from step 2 until your failed boot count reaches 8. At this point, the nook will re-flash its /system partition. You will see the process on the right.
From Nook Devs
i went through this yesterday... i was told you can't brick a nook color so I restored it back to the original firmware...go to this website www.theunlockr.com then click the how to's then go to Android and look for Nook Color then look for how to restore to stock firmware and follow the instructions. they worked for me and I'm sure they will work for you also...Good Luck
Stupner said:
Method one: Eight interrupted Boots
1. Power off the nook.
2. Tap the power button.
3. As soon as Welcome to the future of reading appears, hold the power button down to interrupt the boot process.
* If the boot animation does not appear, add 1 to your interrupted boot count.
* If the boot animation DOES appear, your interrupted boot count is reset to zero. Start over.
4. Repeat from step 2 until your failed boot count reaches 8. At this point, the nook will re-flash its /system partition. You will see the process on the right.
From Nook Devs
Click to expand...
Click to collapse
Thing is, I can't power off or power on the nook.
I'm going to try and restore it to stock.
bennook said:
Ok so here's what happened.
I rooted my nook with autonooter 3.0.0, then I installed rom manager to install cwm. I installed the latest version of cwm and I tried to make a backup, it ended up in my nook only booting in cwm. So I found a cwm removal script and removed cwm. I booted my nook and opened rom manager and I decided to try an older version of cwm. I pressed make a backup in rom manager and it just went into a boot loop. I can't really turn off my nook, and I can't really turn it on. It just keeps going to "touch the future of reading", then turns off, then a couple of minutes later, goes back to "touch the future of reading". To make it clear, I do not have a backup.
So can anyone please assist me in fixing my nook? I'm in a dead end here.
Click to expand...
Click to collapse
You need to boot a stock image. Try this link http://www.androidtablets.net/forum...ll-clockwork-recovery-revert-stock-image.html
I'm So hoping someone will help me, I tried to root my device but it didn't work I couldnt get off the software so I installed 2gb clockwork 0.7 and nook complete restore 1.0.1 I followed all tutorials carefully, but when it comes to restore data it says no files found. Lost, I went ahead with the restore. It appeared to work except now I get a message flashing up that I cant read the screen just flashes and I think the partitions are lost too. I'm on the verge of tears. (im a girl dont judge) lol. And I'm lost with my expensive doorstop. PLEASE can anyone help me fix this as i'm at a loss (
No need to worry. The nice thing about the NC is that it will always boot from the SD card first. Sounds like you tried this...I suggest deleting everything you have (clockwork mod files, stock restore files etc) re-download everything and start fresh.
on your computer, format your uSD card, use Win32DiskImager to flash the clockwork mod boot image onto the uSD card and copy over the stock restore files. Place the uSD card into the NC and reboot. you should boot into clockwork mod and from there you can install the stock zip file from the uSD card.
GL!
Thanks,
I managed to get it working by resetting 8 times and booting a factory reset, but now it wont install any updayes and i'm stuck on the poo 1.01 software. I tried putting the official update on clockwork and booting from there but it says file bad with any version I use (screams in frustration)
This will fix your partitions
It was awhile ago, so I don't remember the exact steps, but the following file will fix everything...
nookie-froyo-0.6.8.custom.3.zip
When you unzip it you will get the following:
nookie-froyo-0.6.8.custom.3.img
You will need a program like 'WinImage' to write this image file to your SD Chip. Once done, boot your Nook with this chip and install Froyo. You probably don't want Froyo, but thats OK. This is just the first step... but it is key.... This install will 100% recreate and fix all your partitions.
Now you have two choices,
1. Find a stock nook image, and install it to your nook. I think it is 1.01
or
2. Find 'boot.img' and 'system.img' for the nook color. Write those to a bootable SD chip and install.
I am not sure if it was #1 or #2 that worked for me. Try #1 first. If it works, you will be able to start up your nook and register it with B and N. Then you can download their 1.2 update and install it as they instruct.
Good luck.
Follow this thread and you can get it back to original stock 1.0 or 1.01 and then do the updates as normal by waiting for OTA or sideloading them.
http://forum.xda-developers.com/showthread.php?t=931720
Thank you guys I've followed your steps and also looked around this site and im back on the latest stock software. I appreciate your help
So I'm trying to get my VZN Galaxy Tab back on its feet. After trying to get Gingerbread in it so I can use Netflix - and failing - I'm going through a lot of motions.
Okay. First I rooted it with Super One Click. I should have been happy with that, but noooo. Then I tried flashing GB on it (I wish I can remember which ROM I started with...it's a mess. I think the pit file was gt-p1000_mr? Does that sound right?).
When that didn't work, I went to the much-cross-posted procedure for returning it to stock using Heimdall and SCH-i800_VZW_stock. Tried it five times. Each time, it booted into the Galaxy Tab/Samsung logos, then a fast glimpse of scrambled letters for a second followed by twinkly music, then black nothingness. It would then bootloop. I attempted to boot into recovery to wipe data/cache, but I couldn't get there. Vol-Up/Pwr just brought up the logo and scrambled video again.
Since I was still able to get into download mode, I tried flashing another ROM...this one the "P1000XXJQ1_P1000XXJQ1_P1000XXJPZ" method. With this, I was able to also flash CWM so I have SOME recovery mode. Sadly, booting brings up the GT/SAMSUNG logos and I get the spacey animation, but after that, again - blackness. This time, however, the Menu/Home/Back/Search buttons light up, so something's happening in there.
Also, booting into CWM, I cannot get my sdcard to be recognized. I tried different cards, so there's something goofy with the slot itself, I'm guessing.
So nothing is really working, but since I can get into CWM and also download modes, I'm holding out hope that this is not completely bricked.
I just need to find the right method of getting it back to a functioning tablet. If anyone has any suggestions, I'm all eyes. Thanks so much.
UPDATE: I tried reflashing stock using the tried and true method. But this time, I went in and flashed CWM replacing the stock recovery which never worked for me. I got the Galaxy Tab/Samsung logo, and at long last, the animated VZW logo. Then it would bootloop there. I booted into CWM recovery and wiped the data/system and the cache from the first page. It still booted and bootlooped the same. This time, I booted into recovery, went to the mounts and storage section and formatted the system, data and cache. Opening logo only. CWM again, and got a whole bunch of "cache missing" messages. But I think I'm getting closer. Back to work.
UPDATE II: So the farthest I can get is the animated VZW logo using the combo of the stock flash through Heimdall, then flashing CWM with Odin. Still no sdcard access. Anything I should try here? Thanks.
same question here
Did anyone figure out how to restore Verizon tab?
Hey, my buddy let me borrow his rooted NC running the Honeycomb Preview on it. He wanted to see what MIUI looked like on it, and let me put it on there for him. I guess I was dumb to assume this was running Android, so it must flash files like any android phone.
He has some program to boot the NC into clockwork mod recovery. While in CW recovery, I wiped data, but after this, it froze while in CW recovery! I've never encountered this, so I just decided to reboot the thing and go from there. It rebooted and directed me to the set-up screen with the green android dude with the persons hand telling me to press him
"Welcome to LogicPD Zoom 2"
No matter what I press, nothing responds. I read up on http://nookdevs.com/Flash_back_to_clean_stock_ROM#ixzz1AAsuy5td and tried to accomplish the 8 restart thing. I don't think I can complete that because whenever I boot up, it immediately puts on a splash screen that says "Loading.."
No part of the boot cycle does it say "Welcome to the future of reading"
Is it possible flashing this thing back to stock? I tried to tap into adb, so I could put it into bootloader from there, but my adb doesn't recognize it. Even with the "adbfix.bat" file.
Any help will help.
Thanks
First, load an image of CWR v3.2.0.1 on an SD card. Then, get a CM7 ROM and the market app .zip file and put them on the card and you should be good to go. Older versions of CWR tend to freeze up when wiping the cache....
In my opinion, no one should be running Honeycomb on the Nook unless off an SD card as a secondary "toy".
Well thanks for the suggestion. I couldn't boot into any kind of recovery mode, which made things kinda confusing.
I fixed my adb issue, so luckily, I could log into adb. I cleared data and cache through adb, and than downloaded the boot.img file and system.img file. Pushed those to the nook that way. Now I'm back to out of box status ready to put some MIUI goodness on here.
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