SD Card Issues - EVO 4G General

So, the other day I was excited to see the TWRP update to 2.0. I've enjoyed the TWRP 1.x line for quite a while so I figured, why not? Then the troubles started. As that post of mine says, I cleared up the initial SD issues (not able to mount in recovery) with the "fastboot oem enableqxdm 0" command. I reverted it to TWRP 1.1.1. It still boot loops (both the recovery or system) quite often, requiring another enableqxdm and reflash the recovery. Each time I reboot, I have to cross as many fingers I can find the house and hope it gets through to the system. I had to go through 12 hours at work without my trusty phone to occupy my down time. Talk about grueling! Then I get home, turn it on so I could do some more fastboot magic, but missed the volume-down in time. It boots right into the ROM that time (not the 14 times I tried at work!.
Now, when it does successfully boot into the ROM (jaredthegreat's ICS Alpha 2.3) the notification bar is forever saying "Preparing SD Card." It ran all night and still wasn't done "checking" for errors. I have another 1GB SD card I tried, just to make sure it wasn't my normal one, and it does the same thing. I have formatted it (with Panasonic's SDFormatter) a few times, and still no luck.
I don't quite understand how flashing a ROM (even if it goes bad) would overwrite the phone's own settings (like enableqxdm) or cause this sporadic boot looping. I have been reluctant to flash another ROM, but I think it's the only thing I haven't tried.
Does anyone have any other insight into the how/why, or something else to try to get the SD card to work in the system, past this "preparing" stage?

So as to confuse myself even more, I have found that I can get past my boot-loop problem by just plugging in a USB cord. Whether it's my AC charger or my computer, for whatever reason, it needs a cord plugged in to get past the white initial EVO boot logo.
Now to work on the SD issue. I have read that deleting the fsck_msdos bin from the phone "fixes" it, but I haven't gotten my Windows adb to recognize my phone when it has any ICS ROM yet. Is it an HTC Sync/Driver issue or Android issue?

Sounds like you need to go with the ics-deck-pa8 ROM

Related

G1 won't boot

I bought it yesterday from some guy on craigslist with a dead battery, but after chrarging it with my carger it would not boot, just the G1 screen. i can not enter the recovery menu, but the boot loader menu does work. Is there anything I can do? I tried reloading the rc29 Dreaimg.nbh, but won't boot. It has the pvt 32b and seeing as how that one is easier to root, I am hoping it's a random issue and not a rooting brick.
As a side note, I have searched. through millions of forums, google, and even my attic for answers. there is always people who get no recovery and no Boot loader screen, then there are those who can access both, but I have not heard of one who can access one witout the other.
did the guy tell u if it had been rooted? if so you can flash a custom recovery image
do you know how to use fastboot? if not have a look around and then try this:
try flashing cyanogens recovery image found here:
http://forum.xda-developers.com/showthread.php?t=523558&highlight=recovery
hopefully this will allow you to do a wipe and flash a new image
if you cant do this give me a shout and il think of something else
The guy did not tell me it wouldn't work, he said it worked fine and then this happened. i traded him an old PSP I had laying around for it, so no big loss on my side. I have emailed him, but no response. Well, How would I type in those commands? Through the phone, or the PC? Thos directions are pretty unclear.
what happened when loading the Dreaimg.nbh
Did it successfully do it? It could take a while to boot afterwords so be patient.
find a guide to setting up fastboot.if ur running windows i cant help but if u run ubuntu or some other linux i can....
after setting up fastboot
boot into the spl by holding camera+power with the usb plugged in
and type the commands in on the computer (again just follow instructions on using fastboot)
its the 2nd set you should use, the ones with "fastboot clear...." etc
Oh thanks. I have jaunty installed on my other pc will see how that goes. The dreaimg.nbh file worked. No errors. Do I just restart with green+menu+red, or was I supposed to wait?
restarting should have been fine...
http://forum.xda-developers.com/showthread.php?t=537508
you may find this useful when trying to set up fastboot in jaunty....
remember when you first plug the phone in to type "sudo adb enable-server"
then "adb devices" to make sure it is detected
the first command needs to be sudo whereas the other doesnt otherwise your device wont be detected
adding the line to bashrc didnt work for me so i tend to do it from within
~/androidsdk/tools/
and it works perfect
good luck
if u dont get a reply here i may not be looking at my computer, so u can email me or gtalk me on [email protected] and il always get it (tnx to my g1 )
I was successful in running all the fastboot/adb files in Windows, but while doing some more research, I don't think this phone was rooted. I am not getting the fastboot menu when I hit back button and my PC won't read the phone.
Last night I found out that after leaving it on for like 15-20 minutes it restarts, but after the second restart the phone died. It had been charging all day as I was using it. Seeing as how it was plugged into the PC. I am heading to a t-mobile store and am going to see if I can get a hold of an extra battery, not buy one mind you just ask "politely" to see one. Seems crazy, but I have a hunch it might be that my battery has gone dead. None of the nbh files I tried did anything except the rc30, that one caused my phone to start restarting, before it would stay on the g1 one for more than thirty minutes without a restart.
Sounds like its unrooted and stock but somehow has a corrupted rom.. It should be recoverable. Try the goldcard method to get RC30 on there:
http://forum.xda-developers.com/showthread.php?t=485364
I have been reading through that thread, but I have no idea how to actually use the goldcard that was generated. Anyone can help me through it seeing as I can not enter commands from my phone.
Ok I went to my Mac because dd command does not work under cygwin that well for me( I'm more familiar with terminals from ubuntu and OS X) Well I can't get the goldcard.img onto my micro sd card. I have been reading and no one seems to have any troubles other than actually generatiiong the gold card. I will report back after I finish the whole thread. Also they suggest an allocation size of 4096, but my sd card only gooes to 100* something.
ok, bad news, I just finished the gold card instaallation and put my sd card into my phone. Now it won't go to the bootloader. Too bad.
Good news. Yesterday I tried to boot it while placing the phone in a drawer and it booted to the recovery menu! I did not have an as card at all so there was nothing I could do so I tried to wipe everything and it finished, but it went back to where it was. I had left it in blue light mode all night. So last night I left it to try and redo what I had done, but it did not work. Atleast it goes back to the bootloader. Gold card did not work but I blame it on the CID number. I can't seem to get the right one. I'm looking though.
I realized what I did. I did not mess with it. I took the battery out last night an did not touch it till just now and it booted to the android screen then froze and restarted and went back to the G3 screen I'm going to leave it like this and see if it gets fixed by tomorrow. Than while booting try to get to the recovery menu. Hopefully it will fix the problems. I seriously think it might be the battery. Tmobile store did not have a spare one though.
Just a suggestion, may or may not work.. I got a new G1 the other day, and have rooted it, etc.. Mine did the same thing, on the G1 screen for hours, never left it.. Take the SD card out of it, and try to start it.. Mine would not load due to the partitioning, I had a 47mb ext2, a fat32, and another ext2 partition, which caused it to hang on the G1 screen.. If no luck there, this site is what helped me root mine, gives the files, and the steps.. http://www.getyourdroidon.com/wiki/index.php5?title=How_to_Root_your_G1
Just take the sd card and put it on your computer via an adapter or something to copy the files (Make sure it's formatted fat32)
If by some reason, my explanation above did work, use partition manager 9 to fix the card.
I booted it withoutth sd card, but same deal. Left it without the battery last night and got it to the recovery menu but would not find the update file. Ended up freezing on me so I went ahead and rebooted. Same deal. I guess I will try again tomorrow.
Phone booted up, was entering my log in info and it froze.... I'm still trying to fix this.
At this point, I would try to go completely back to a fresh OEM install, which I'm not sure you've done since you started to get access to Recovery.
Download the original T-mobile bootloader. Rename it to update.zip and copy it along with dreaimg.nbh to the SD card. Enter Recovery and alt-s to install the bootloader... reboot using Home+Back. It will probably lock up at some point as it's been doing. Turn off the phone and get into bootloader to flash dreaimg.nbh.
Report back after you do this.

IDK What happened! Stuck at boot!

I've flashed roms before. I've went from Fresh to Dark to aloysius, etc so I'm not a noob to flashing/rooting/etc.
I've been using Aloysius for the last few days and today, I noticed Goog Maps Nav wasn't in the rom so I decided to restore my nandroid (as anyone would usually do).
Now I'm stuck at a boot screen. I've tried hardware button resets and still stuck. Tried reflashing or restoring again and again but no go.
Any help?
Plug it in to your computer, turn it off, and run adb logcat. It should say -waiting for device-. Turn it on, and copy-paste the last 20 or so commands.
A2SD
I have noticed that if I use A2SD and switch roms, my phone gets stuck at boot, so try wiping your phone, then take out the SD card then boot. If it boots succuessfully, then wipe the EXT partition on your SD card and you should be good.

[Q] Bricked!?!?!

I've heard about how it's pretty much impossible to brick the nook... Mine seems about as useful as a brick though. I was trying to set up a dual boot following these instructions. Basically, I had HC installed to the internal memory. backed it up, formatted system and data, then flashed update-nc-stock-1.2. CWM said that was successful. Then I rebooted with my CWM SD card out. Screen said "read forever" or whatever, then went blank. I waited for about 5 minutes, and pressed the power button. The screen went from an 'on' blank to an 'off' blank. Since then, I haven't been able to get it to turn on at all. Just an 'off' blank screen with no signs of life, even with charger cable connected. Tried it with CWM SD in and out. None of the buttons seem to do anything...
Thanks in advance!!
I'm pretty new to the Nook having just got it today, but I did some reading prior to attempting anything to see how easily I could back out if I had to.
Have you tried basically starting over (ie. Let go of the multi-boot dream for a bit and get back to basics)
You know, take a SD card, use diskimager to put the clockwork 3.0.2.8 image on it with the CM7 full ROM and boot to that, then format system, data and cache with clockwork and finally install the CM7 zip image (and gapps I guess) just to get going again.
If it all works, maybe take another run at whatever you are trying to do with the multi-boot stuff.
Thanks for the reply.
Sounds awesome; problem is I can't get the thing to do ANYTHING. boot period, into recovery or otherwise. I plug it in and it displays nothing - no 'wait 15 minutes and try again'. Just a black screen no matter what I do. I have an SD card with recovery on it, and i've tried making it do something with or without the SD card. No luck.
Good luck with your nook; I had really been enjoying mine.
So holding the power button for 10-15 seconds doesn't do anything?
Or when you plug in the power does it try to boot?
I mean in a complete worst case scenario you could grab yourself a T5 and open it up, disconnect the battery, and then reconnect it.
Then something is wrong with your Recovery SD card, as no matter what, hardware dictates that it reads the sd card first. The problem with what you did through dual boot methods is you resized partitions. So even if you do back out of all of this, you're going to be losing space unless you setup dual boot.
Recreate the CWM recovery card, either redownload the image and reburn it. Find a different one or something else, because it should load on startup.
Thanks for the help!
Reformatted SD again, then tried powering up with the power cord unplugged. Apparently it won't boot into recovery as long as the power cable is in, and whatever the boot was on EMMC was messed up. Happily running stock 1.2 now, next step, dual boot with HC!
Anyone know how I can delete this thread as it's pretty unnecessary?

[Q] The Unbreakable Bootloop - Am I bricked?

The Device:
Nookcolor Refurb - came with stock 1.2 installed. Rooted with CM7 - initially had boot partition problems and went back and did the fix for it. (was using an old CWR, so had to redo that, too). Worked mostly fine for a few weeks. Had a little trouble installing the recent cm7 stable update. But after clearing and redo, no problems. Then I updated Adobe flash to 10.3 through the market. bad, bad, bad. (I've discovered). It has gone into a bootloop, but it doesn't even get in far enough to bring up CWR either internally or on a bootable SD card. It brings up "loading" - whether in CM7 or CWR - then shuts itself off. I have tried the 3 button salute and 8 interrupted boots, but neither works in any way. Is there something else I can do?
Also, a side note, the device will not charge to green light - even if charging overnight. At first I thought it was a battery issue, but after a day of combing the boards, I'm thinking bootloop from hell.
Help!!!!
Are you running CM 7 internally or from a card? If internally, try making a bootable CM 7 card and booting from that.
I am running it internally. The device will not boot from a card or internally. It doesn't get far enough into the boot before it loops for CWR to start up - either internally or off the sd card. I can get to the boot menu (hold down n when it starts up), but it doesn't boot off any of the options there, just goes to black screen.
What happens when you do the 8 failed boots?
Nothing really happens with 8 failed boots. I think it terminates the boot process before it gets far enough along for it to "count". Loading comes up, I count one thousand one....all the way to one thousand seven. Then it shuts off, often reboots itself. Same deal with CWR. Loading comes up, count to 7, shuts off. I can get to the boot menu in CM7, but I it doesn't respond when I request any type of boot from anywhere. Either hangs or restarts.
I'm trying ADB, but it won't stay connected. Flicks on right at the end of the loading process and then shuts down. It really sucks.
Shelly, shoot me a pm... i'll give ya my phone number and we'll work on getting it going.
Sorry if this is redundant, but in very basic troubleshooting have you tried charging your Nook? It probably is more complicated/serious than a low battery, but it wouldn't hurt to rule it out.
I finally did get it to charge to green light. Didn't make a difference. I can get it to hang sometimes when it's trying to get into CWR. And it will stay on the Boot Menu.
Just a side note, I have another NC that I've had since Jan. Autonootered, Manual Nootered, CM7ed, brought back from the dead many a times.
Dizzy Den - am shooting you a message shortly. Thanks.
Has this been solved? If yes how?
Could you find a solution to your problem?
I'm having the same issue now. Bought a Nook Color in November, Autonooted, flashed recovery from ROM Manager, flashed CM 7.1.0 internally from downloaded ZIP files via ROM Manager, was working just fine for a week, stable, fast, perfect. Overclocked to 1200 MHz after a few days which made the experience even nicer.
Then installed and started Google Maps which didn't work - the Nook turned off on launch of Google Maps app.
I had set Wifi to "stay on all the time" beforehand (which might have been bad because it creates Sleep of Death syndrome as i now know).
Now when i turn it on it shows "Loading" for 7 seconds and then the screen turns off. This is when booting CM, when booting the internal recovery (shows "loading recovery" for 7 seconds) and when booting from any SD card image (i've tried at least 10 different bootable SD card images, different cards and different card readers).
It recognizes and tries to boot off SD cards - i get different "Loading" screens depending on the image, honey-colored for a honeycomb image, with two skulls for a recovery, ... So that works.
The nook seems to be in some kind of "on" state because i need to hold the power button to turn it off before i can get it to boot again.
I can get to the boot menu as you could, but booting from there doesn't do anything at all. So the hardware seems to be OK because the boot menu itself works well and for more than 7 seconds.
I can charge it and it goes to a green light so it's no battery issue.
The nook does not show up on USB - well once it did for a second but that was it.
I even tried to let the battery run completely empty so internal registers can get reset - didn't change anything.
Help! Is it bricked now?
Going to a B&N store isn't an option btw - the next one is 6500 km from here.
(This is the first time i ever ask for help on a forum. I am running a ZTE Blade with CM7 just fine, and I've been stuck often enough but always found a solution myself...)
Gunnar
Have you guys tried this:
http://forum.xda-developers.com/showthread.php?t=1308304
Or completely restoring it to stock:
http://mrm3.net/nook-color-recover-any-bricked-device/
Tried, can't get far enough
Kingdruid, thanks, yes i've tried both of those links - sadly they don't help at all because i can't even boot SD card recovery images...
I tried various recovery images including the newest clockworkmod, but i am still stuck They all work for 7 seconds only.
So yes, a nook can actually be bricked it seems.
G.
tralulu said:
Kingdruid, thanks, yes i've tried both of those links - sadly they don't help at all because i can't even boot SD card recovery images...
I tried various recovery images including the newest clockworkmod, but i am still stuck They all work for 7 seconds only.
So yes, a nook can actually be bricked it seems.
G.
Click to expand...
Click to collapse
When you overclocked it, did you notice it getting hotter than usual? I wonder if it was due to the overclocking. All the users I see with unrecoverable nooks is after they overclocked.
No, i did not notice much heat. And it was working well in its overclocked state for a few days.
Do you think it's CPU is fried now?
tralulu said:
No, i did not notice much heat. And it was working well in its overclocked state for a few days.
Do you think it's CPU is fried now?
Click to expand...
Click to collapse
I own 4 of them so I would prefer the term "Unbrickable", but at this point I'm not really sure.
Try 8 failed boots and see if you can get into recovery to reset to factory.
cant get it working
so first noob post
i used this thread to root my nook color
http://forum.xda-developers.com/showthread.php?t=1000957
problem is i have followed the steps and re done it about 5 times and every time i turn on the nook it goes right to read forever and runs the stock OS
nook 1.2 brand new, and 8gig SD card
when i boot i hold the power button for the 5 seconds, am i missing something?
tntviper1 said:
so first noob post
i used this thread to root my nook color
http://forum.xda-developers.com/showthread.php?t=1000957
problem is i have followed the steps and re done it about 5 times and every time i turn on the nook it goes right to read forever and runs the stock OS
nook 1.2 brand new, and 8gig SD card
when i boot i hold the power button for the 5 seconds, am i missing something?
Click to expand...
Click to collapse
how did you write the image to the SD card? you can't just do the write button in winimage, you have to use the "convert virtual hard disk image to drive" or something... really should be mentioned in the n00b guides.
Sequence in winimage:
Disk->Use disk (whatever your sd card is)
Disk->Restore virtual hard disk image on physical drive (select the image you're trying to write)
Click ok on the warning and you should have a boot disk
"Write disk" is prominent but just copies the files to the disk, not resize or make it bootable.
Nope - no change
DizzyDen, nope, 8 failed boots does nothing. Just fails 8 times, no restore.

[Q] Custom ROM, stuck at boot animation...

I wanted to run a custom ROM on my A500 (first attempt at installing custom ROM), but i'm now stuck at the boot animation.
I downgraded my A500 to 3.0.1, rooted, installed clockwork mod, upgraded cwm to 1.5. So far so good.
Then i downloaded thor rom v12, copied it to the external sd card (by putting it on USB thumb drive, transfer to tablet, copy to external SD using file explorer - something tells me I'm going to need to pick up an sd card reader for my computer)
Rebooted into recovery, wiped everything (had nothing of value installed yet), and then chose to install zip file, chose thor_rom_v12.zip on external SD card, it started installing - looked like it succeeded.
Reboot tablet, and i've been staring at the boot animation (electric blue pulsating android with spinning gears on it) for about 45 minutes.
How should I proceed from here? Any idea what I did wrong?
Thanks
Hold the power button down and see if you can force it to shut down. I dont think itll turn off but its worth a try. You could also try the hard reset button (pin hole on the side of the tab) if the reset works than you should be able to boot back into recovery. If not than youll just have to wait till the battery dies.
Once you eventually get it turned off than try booting into recovery and do a full wipe and reflash the rom. I have a feeling the file you downloaded is corrupted though. if this is so than your tab probally wont boot up again.
At this point id redownload the thor or another rom and than try flashing that. You'd have to get an sd reader since you won't be able to transfer the files through your iconia again. If you can manage to get a clean download on your micro sd somehow than i'd skip straight to this step and start redownloading the rom right now.
BTW these are just the things i would try from knowing what I do about android. I haven't had any issues with my tab yet so I havent looked for solutions for this it, but ive dealt with other boot looped and soft bricked devices.
I'm sure if you do a search you'll find something.

Categories

Resources