So I got my Dream to work again after a theme caused it to boot loop, by reinstalling Haykuro's Rogers root and CM 3.6.8.1.
After installing Open Home and getting the phone all nice and pretty again, I decided to do a Nandroid backup. After rebooting the phone, Open Home would not load, so I rebooted again. Now it's stuck in boot loop. Restored backup, still boot loop.
Is it possible I have a crap SD card? Using ext3 and linux-swap on an 8GB class 4... I'm still within my 30-day return policy on the SD card.
Boot.img is a funny thing. Sometimes themes will cause a boot loop with edited boot images. Usually if the theme is designed for a different rom than you are running. The best bet is to run the update.zip again for the rom your are currently using. To do this you will have to take the SD card out and put it in your computer. You could also copy it over with some ADB commands. Your card is fine, I don't think it is bad at all. I am not sure if you tried to restore all the img's back to your phone or not. Usually this includes boot.img, system.img and data.img. The others are optional but not mandatory.
I reinstalled Haykuro's root using fastboot erase and reflashed 3.9.7 with Dark Hero theme, and it booted up fine. It's friggin' weird.
Related
I just got an A-Data Class 6 4 gig card. I can format 3 partitions, upgrade to ext3, copy update zips and files to it, but it boot loops when i try to load up a new rom (any rom). My old class 2 4 gig card loads everything fine. It even runs the latest king hero really well.
Any ideas?
robkoehler said:
I just got an A-Data Class 6 4 gig card. I can format 3 partitions, upgrade to ext3, copy update zips and files to it, but it boot loops when i try to load up a new rom (any rom). My old class 2 4 gig card loads everything fine. It even runs the latest king hero really well.
Any ideas?
Click to expand...
Click to collapse
How did you partition your card?
using parted in console. I've re-done it several times as well.
So no matter what rom you flash your getting a bootloop. Do you have a nandroid?
I do. Using Amon_Ra's 1.2.3
On 2nd thought, do you mean a nandroid of a bootloop instance?
robkoehler said:
On 2nd thought, do you mean a nandroid of a bootloop instance?
Click to expand...
Click to collapse
Naw a nandroid of a rom that was working before you started flashing.
unfortunately no. i got partition crazy and removed the fat32 it was on right before i thought "did i back that up?"
With my old class 2, i've been able to get up and running on 4.1.999 and this king hero rom with no troubles.
Can a taco be bad but not bad? like, it tastes good, but it was made with bad ingredeints or a horrible chef.....
It sounds to me like your wiping after flashing.
You wipe data, Wipe ext, fix ext, flash rom.
If you wipe after flashing, or flash without wiping you will always get a boot loop.
The image doesnt run from your sd card, so the only thing that would cause the loop is the data on your phone.
Find a tested and working rom (i suggest either Mligns newest or Kings newest)
Go into recovery and turn on USB.
Move rom to sd card.
Wipe data
Wip EXT and fix
REBOOT INTO RECOVERY
then go to flash any ZIP (if you dont reboot, the rom file will not be seen correctly)
flash the rom
Fix ext again just in case
Reboot and leave the phone alone for a few mnutes.
EVERY phone is different. Some take 2 min some take 10-20 min
But if you have flashed properly, the best way to know is the shimmer on the HTC will continue to flow and not stop.
Sometimes it will fade, sometimes the noti bar will appear for 5 min then boot...
Just have patience and try.
EDIT- You typed while I was typing, It sounds like then maybe that card is bad then. If all works with older card, then the flash may be bad on the newer card. may want to return it unless you have other uses for it.
Just to add a strange twist to this. Just reformatted card so it was all Fat32, wiped, and flashed 4.0.4. Everything went fine. What on an SD card could crash Apps2SD?
robkoehler said:
Just to add a strange twist to this. Just reformatted card so it was all Fat32, wiped, and flashed 4.0.4. Everything went fine. What on an SD card could crash Apps2SD?
Click to expand...
Click to collapse
Possibly the upgrade from ext2 to ext3. Thats why I like to do mine in Ubuntu. Format the card using linux for a linux phone.
Decided to go a step further and go back to parted and resize fat32 and add a 500mb ext2. Rebooted and it fired up and shows the ext2 in the settings screen.
All that and it's not even Halloween yet. I'm going to try to flash 4.1.11.1 just to see if i can break it again
I'm sending it back. wiped flashed 4.1.11.1. Got to setup screen but everything force closes. com.android.phone, com.google.process.gapps, com.android.setupwizard.
Skipped wizard.
signed in with google account.
no service connection ever made so no account sync.
time to email newegg and try this again
robkoehler said:
I'm sending it back. wiped flashed 4.1.11.1. Got to setup screen but everything force closes. com.android.phone, com.google.process.gapps, com.android.setupwizard.
Skipped wizard.
signed in with google account.
no service connection ever made so no account sync.
time to email newegg and try this again
Click to expand...
Click to collapse
lol.....you give up quite easily.. those problems arent related to the sd card (they are on your /system partition)
try to reflash your rom and repair ext partitions then fix_permissions in recovery
hmmmm.....got card #2 and it appears to be the same case....boot loops. i can't believe that 2 sd cards would be bad only when it comes to apps2sd.
got adb running on my work pc and uploaded a log of the fail
again, everything boots just fine (just booted king's new 1.0) with my lexar class 2
updated logcat - 1st one was when i couldn't get off of the g1 screen.
this logcat is of the bootloop. any help would be great
Hi team,
Having some trouble rooting my g1 and upgrading to CM 4.2.4
I have been following a tutorial from here: http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
... to achieve my goal. Followed all of the steps fine and to a tee. Installed all of the suggested files from the suggested places.
Succesfully upgraded the radio image, then moved onto upgrading the SPL. Ran through and rebooted phone, until the never ending "Formatting Cache" notice came up on the automatic boot into the Recovery Mode.
(FYI: radio and SPL images were from http://code.google.com/p/sapphire-port-dream/)
Moved on to installing CM 4.2.4 after realising that the format was complete... Alt-W then Install from zip. Installed CM. Waited for prompt for completion... pressed reboot... then the boot hangs on the G1 startup screen.
Only way I could get out was to remove the battery. Went through the process again (Alt-W, SPL install, reboot, Alt-W, CM install, reboot, hang) numerous times, all with the same outcome.
Only thing that I can think of that I am doing wrong is pulled straight from CyanogenMod Wiki explanation: "I've noticed on some devices that when you fresh install the first time and you update with the rooted adp package from htc, reboot and then update to latest CM, some people get stuck at the tmobile logo. What I did was install the rooted adp package from htc, reboot and sign in all the way to home screen, then rebooted and installed the latest CM. That should get you past the first screen freeze if it happens to you."
As I am a noob, I have been unable to try this for the following reasons: 1. Where can I find the HTC rooted adp? and 2. How do I get this image onto the SD card when I can't boot in? I have tried without booting and my computer won't let me access via USB...
I was going through the process from factory settings. Is this my problem... Very confusing.
Realise that there are currently two active threads running in this section that are similar... but these guys seem to have done the wrong thing and are trying to right the ship... I can't seem to figure where I've gone wrong.
Thank you in advance for your assistance.
As well: could booting with camera + power get me into the Dreaming.nbh OS to get HTC root OS onto the SD card?
http://developer.htc.com/adp.html
Download the 1.6 recovery image. It is actually the 1.6 Android Dev Phone ROM, flash that via recovery console... then flash the cm update. Make sure you wipe before you start flashing.
As well, do you have your SD card partitioned? It would be a good idea to do that as well. Two ways to do it, manually, or download and update to RA's recovery image 1.2.3:
http://forum.xda-developers.com/showthread.php?t=566669
I would update to that recovery first, use the option to part my SD card, upgrade to ext3, wipe, flash 1.6 recovery, flash cm update, good to go!
Thanks for the quick reply! Very handy info... How do I get the images onto my SD card without being able to boot though?
Do you have another device like a camera, or mp3 player that can take a microsd? If so just hook it up and transfer.. otherwise you may need some additional devices.. I bought an adapter so my sd can plug directly into a usb.. other than those couple options, I haven't any more suggestions to offer ya. If you cant get past the boot screen to mount, I don't see how you can do it through your G1.. there might be some terminal commands you can try to mount to a computer.. but that's beyond me.
Nathanial said:
Thanks for the quick reply! Very handy info... How do I get the images onto my SD card without being able to boot though?
Click to expand...
Click to collapse
You take it out of the phone, while the battery is pulled, put it in an micro SD card reader, plug that into your computer, tada! If you computer doesn't have a slot for the standard SD card adapter, you can get microSD to USB adaptors most everywhere that sells electronics.
Or if you have cyan's recovery installed... you can hold Home+power
go to console, press enter and type
ums_enable
Click to expand...
Click to collapse
and it will mount the sd on your pc.....
put ums_disable to unmount
Sorry to be a noob, but what benefit does partitioning do?
If you have an EXT3 partition, you will have app2sd. If you also have a linux-swap partition, you will be able to have a swap file (in simple terms its like adding more ram)
The ext partition is for apps2sd, and the Linux-swap partition is to give a little extra memory for the ROM.
Thanks for all of your help lads! Up and running. Muchly appreciated!
I went to update to use autonooter 3.0.0 with nook 1.1.0 software. I went through the process of installing the autonooter 3 and it booted up with the Android splash screen but it kept replaying the android sequence (spelling android) and it would keep restarting sometimes not getting through the entire spelling of android.
I went to reset to factory defaults and now it constantly reboots after "installing a new software update is being installed..." completes. Autonooter no longer boots it justs sits blank forever.
Please help!
hmmm...
Autonooter seemed to work for me. I just had to make sure that I was on stock 1.1 and it worked.
Try to obtain another microSD card. A 1GB will work just fine for the Autonook img.
Also, I would download another copy of the image. What you are going through seems to be a bad image either burned to the microSD or from the source.
Just my 2 cents.
I am sure that it works but for some reason I seem to be in some exception case and I need input how to get out of this mode. My nook is essentially bricked right now.
Have you tried to restore to stock using these instructions?
http://nookdevs.com/Flash_back_to_clean_stock_ROM
I could not get the 8 times failed boot to happen, no matter what the nook boot always happens, I could not get ADB to recognize the device to for the failed boot, I tried the new SD card and image. I give up. I bought it from BN last week so I will just exchange it. thanks for the help.
I have the same issue. The Nook loops the boot screen. The first time it gets through the boot animation afterwards it stops at AND then it pukes. I'm going to try taking it back to stock.
To all of you stuck in this boot loop use my guide posted here to return to stock.
It even includes the link to decadences pre-rooted 1.1 so you can use that instead of flashing back to stock 1.0 or 1.0.1. Good luck and have fun!
Note: Make sure to format /data /system and probably /boot if you are going to flash one of these. Its always best to start from a clean build.
Try the CWR bootable SD...?
quickwitt said:
I have the same issue. The Nook loops the boot screen. The first time it gets through the boot animation afterwards it stops at AND then it pukes. I'm going to try taking it back to stock.
Click to expand...
Click to collapse
Try this... if you have 2 SD cards...
1) Download iMonster's bootable CWR image... (1GB card should be plenty)
2) Download the stock kernel/image from XDA forums and copy onto card #2
3) Using the bootable imaged SD, hold the "n" + power to boot up... you should see two crossbone/skulls image and in-between them, the words "loading"
4) Once it boots into CWR, go to "install from sd"
5) Select the stock image from the SD card...
It should boot back up into stock. Then try the nooter again... try to re-download the file, re-image, and start process over.
Out of curiosity... did you get your nook before or after the who "temporary pulling off of the shelves" incident? I'm wondering if these devices have been reworked at their factory? I know there have been articles that mention that this is just a rumor... BUT you never know.
I used winimage to write the 1.1 image here to an sd card
http://forum.xda-developers.com/showthread.php?t=945838
Put the sd card in the Nook and rebooted. It booted into CWR, I followed the onscreen instructions and now I'm back to stock 1.1.
Reflashed Nooter 3.0.
Back in business.
hvuong2 said:
Try this... if you have 2 SD cards...
1) Download iMonster's bootable CWR image... (1GB card should be plenty)
2) Download the stock kernel/image from XDA forums and copy onto card #2
3) Using the bootable imaged SD, hold the "n" + power to boot up... you should see two crossbone/skulls image and in-between them, the words "loading"
4) Once it boots into CWR, go to "install from sd"
5) Select the stock image from the SD card...
It should boot back up into stock. Then try the nooter again... try to re-download the file, re-image, and start process over.
Out of curiosity... did you get your nook before or after the who "temporary pulling off of the shelves" incident? I'm wondering if these devices have been reworked at their factory? I know there have been articles that mention that this is just a rumor... BUT you never know.
Click to expand...
Click to collapse
I think the "pulling off the shelves" is a myth but I purchased my nook the 1st week of January. I've loaded every version of Autonooter as well as Froyo and Honeycomb without incident until now. I'm sure I screwed something up in the process or just had a bad write to the sd. I'm pleased that you can't really brick this great little tablet.
I have a Nook Color that was running the Cyanogenmod nightlies. After shutting it down, it would not boot again.
Since it still boots into recovery, I tried reflashing cyanogenmod, a recovery zipp that was supposed to restore the boot partition, dding boot.img and system.img to the internal memory, a total wipe of every partition, flashing with the latest version of clockwork, along with .7, the stuff mentioned here http://forum.xda-developers.com/showthread.php?t=949699, and flashing "nook color return to stock".
Although all flashes completed successfully, the device still won't boot without the sd card. Is there a method I'm missing?
Been in the same boat myself as well as many others. I found that to get it to boot correctly again do this. Use this link (http://forum.xda-developers.com/showthread.php?t=914690) and downlaod the "Remove CWR" file, you'll also want to download the repartition-boot-with-stock.zip which is the last link in the OP right under the Remove CWR link. Once you download each file copy them to a bootable sdcard. Then pop the bootable card into the nook and power it up to into CWR off the sdcard. After that install the Remove CWR zip first, then follow up by installing the repartition-boot-with-stock.zip. Once all is said and done power the Nook off by holding the power button in. take the sdcard out and then power it on. Odds are it will get stuck again but you should be stuck on the N screen. If so power it off and then put your bootable sdcard back in the device so you can start fresh reinstalling CM7 & gapps.
If you repartition boot, cwr will be removed in the process. No need for the second file..
Sent from my HTC Desire using XDA App
samuelhalff said:
If you repartition boot, cwr will be removed in the process. No need for the second file..
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
In theory it should and you are totally right on but I've personally seen it where even after repartitioning the boot it still will not boot correctly for whatever reason. That said personally I've found it just as easy to take the extra step to make sure it gets cleared up as it takes a matter of a couple extra seconds to do it.
Thanks, I'll try that.
Followed instructions exactly, but the thing still won't boot. I must have F'd up my /boot partition pretty badly.
Edit: Wiped every single partition and cache, then flashed, now it works. Thanks guys
I am having this same problem and have a question about the options to fix it. I have CM7 stable on my NC and it worked untill I formatted the SD card and rebooted.. now it just gets stuck at "touch the future of reading" screen.
Is it possible to remove CWM without harming the CM7 install? and still be able to boot to CM7?
So yesterday I grabbed a copy of OpenRecovery from the cyanogenmod4android Google Code page and unzipped it, threw it onto my Milestone's SD card, rebooted into recovery.
It restarted when the bootloader (or whatever) finished loading the update.zip. I thought it was a bad .zip, and so I re-downloaded, and unzipped it to the SD card. Nothing changed.
I decided "Meh, use now, fiddle later." and let it reboot, sat it down and went back to looking up things to do with my HTC G2.
A minute or so goes by and I notice it hasn't done its normal boot-up vibration. (It's always done that. Pretty sure it's the "Checking SD card for errors" notification.) I pick it up and see that it's rebooting after about 3 seconds at the Motorola logo. What happened? D:
Use this recovery, it's the most advanced one: http://forum.xda-developers.com/showthread.php?t=1091787
Download the "Minimod V0.23.zip" and extract it to your SD card.
You should then have a folder called "OpenRecovery" and the "update.zip" file in the root directory of your SD card.
Do not unzip the "update.zip"
Furthermore you need to flash a vulnerable recovery first.
It's all in here: http://forum.xda-developers.com/showthread.php?t=698059
If your phone is stuck in a bootloop then I honestly don't know how that could have happened.
If there's no important data on the phone you could try factory resetting it.
If this doesn't help you'll have to reflash the ROM.
Guess I should've come back sooner...
Eiertschik said:
If your phone is stuck in a bootloop then I honestly don't know how that could have happened.
If there's no important data on the phone you could try factory resetting it.
If this doesn't help you'll have to reflash the ROM.
Click to expand...
Click to collapse
Well, I powered it on a few more times, and it booted. Works normally apart from the OR issue. I already flashed the vulnerability from the guy who maintains(ed?) the Google Code page, and I've used the same OpenRecovery before, only that was with a different SD card. (Which I formatted and stuck in my HTC Vision without backing up, being an idiot)
I'll try out this one you linked me, and see what happens.
You can also try formatting that new SD card with the SD Formatter tool (link's in my signature)