Database Develop

phone reboots to bootloader image with 3 skateboards

i have a class 6 adata 8gb 2gb ext4 64mb swap rest fat32
im running cyanogen 4.0.2 or 4.0.4 whichever one i load up from sd at the time, but both are stable. i have newest radio and spl also. the issue is simple. i can get into recovery mode and bootloader menu. everytime i reboot it goes to bootloader menu(3 skateboards). camera button is not held down either or stuck. the only way to get past this screen is to evertime i reboot to factory wipe and install new rom which is a pain. i was wondering if by having the original image DREAIMG file in a folder on my sd is whats causing this. but now that i cant get past this screen i cant remove it from sd. i also already tried mounting sd to comp from console using: "ums_enable" it does nothing(tried it on 3 computers). im tired of reseting and reflashing. pls some assistance.

Have you tried to reflash the SPL? You could just redo the entire root process and replace everything.

New Isuue, Same Problem
Sorry it took so long to get back here. No I haven't tried that. How could it be the SPL? Im asking it in a meaningful way, like why and/or how could it be?
I will reflash the SPL tonight and edit post if it works.
I also erased my sd card and re partioned in in "parted" it booted fine. The battery died today and i rebooted it and BAM! bootloader screen again. So i factory reset and flashed a new ROM image. then it worked fine. now only problem is the private apps i have installed wont work and they get stuck on uninstalling....Whats the fix for that?
Thanks XDA!!

You need to start over and replace everything. It sounds like you have multiple problems. Use THIS guide starting with the downgrade bacause it will reflash EVERYTHING on your phone. If the problem persist then it's hardware issues. Redownload everything, don't use anything you already downloaded because these files might be bad too.

Help with root, cant get into recovery image!

okay I followed regs guide and when I reached the part to where I have to run the command to flash the custom recovery image
regaw says it may take many seconds for it to complete
when I do it it takes less than 1 second and when I run the final command to reboot the phone into the recovery menu it simply boots up normal
I have tried booting while holding the home button and still a no go
I think the recovery image isnt flashing into my phone for some reason...
but cmd says it was successful , any help apreciated

can anyone help?
please, I've followed everything as it should be.
I've tried 3 computers(2 running XP , 1 running windows 7)
I've Hard reset the phone everytime I have tried to perform the root
Everytime I flash the recovery img it says its successful but when I place the comand to reboot into recovery my phone freezes and I have to do a battery pull.
I don't get what I'm doing wrong
I have all the files in the correct directory
I have usb debug on
I have set the phone to charge only
I have htc sync installed
any help apreciated :/

just mount your sdcard copy the recovery to it again then try to flash it once more. it could have corrupted the image on the first copy. if that doesnt work. try to download the 1.6.2. recovery image and flash that.

nfinitefx45 said:
just mount your sdcard copy the recovery to it again then try to flash it once more. it could have corrupted the image on the first copy. if that doesnt work. try to download the 1.6.2. recovery image and flash that.
Click to expand...
Click to collapse
can you point me to where I can find that download?
Thanks I will try to mount the card now

No luck putting the files directly into the card ; ;
what else should I try?

I'm having the same issues. I'm running a brand new hero not even activated yet that has 1.5 (sprint send me new one bc couldnt revert.. didnt know root was coming) ANYWAY I need help.
I have root and I've copied damage controls zip to my sd card. I tried rebooting into recovery mode and i get an error picture so I had to reboot.
this is frustrating.. can someone give me step by step including commands that I should type? I can load the sprint 2.1 and unlock (have old version) but right now im as frustrated as all the other noob's.
it sounds so easy but im clearly doing something wrong..

gab2012 said:
No luck putting the files directly into the card ; ;
what else should I try?
Click to expand...
Click to collapse
1.5.2 http://www.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-heroc-v1.5.2.img
1.6.2 http://rapidshare.com/files/360288584/recovery-RA-heroc-v1.6.2.img

it worked with 1.6.2 thank you!

no problem

sporty9xterra said:
I'm having the same issues. I'm running a brand new hero not even activated yet that has 1.5 (sprint send me new one bc couldnt revert.. didnt know root was coming) ANYWAY I need help.
I have root and I've copied damage controls zip to my sd card. I tried rebooting into recovery mode and i get an error picture so I had to reboot.
this is frustrating.. can someone give me step by step including commands that I should type? I can load the sprint 2.1 and unlock (have old version) but right now im as frustrated as all the other noob's.
it sounds so easy but im clearly doing something wrong..
Click to expand...
Click to collapse
this is the walk thru you should do with 1.5 just used the 1.6.2 Recovery I posted, it has less issues with flashing
http://forum.xda-developers.com/showpost.php?p=4930043&postcount=1

Help stuck on grey n screen and can't get out

I'm stuck at the grey N screen and I can't get out. I just got my NC today, updated to 1.0.1, used the latest Autonooter, followed the instructions to a T, everything worked great.
I left the SD Card in (didn't know you were supposed to take it out and reformat it, none of the instructions were specific about that). I was playing with the unit, everything was working great and decided to reboot it because I saw there was a custom animation and I wanted to see it (didn't remember seeing it the first time around). Now the thing won't reboot. It just gets stuck at the grey N screen. I've tried the power + home method and done the factory resets 3 times but when it resets it still hangs on the N-screen and won't boot.
I'm at a loss here. Some one please help.

jbright44 said:
I'm stuck at the grey N screen and I can't get out. I just got my NC today, updated to 1.0.1, used the latest Autonooter, followed the instructions to a T, everything worked great.
I left the SD Card in (didn't know you were supposed to take it out and reformat it, none of the instructions were specific about that). I was playing with the unit, everything was working great and decided to reboot it because I saw there was a custom animation and I wanted to see it (didn't remember seeing it the first time around). Now the thing won't reboot. It just gets stuck at the grey N screen. I've tried the power + home method and done the factory resets 3 times but when it resets it still hangs on the N-screen and won't boot.
I'm at a loss here. Some one please help.
Click to expand...
Click to collapse
Did you try taking the SD out and then booting? It'll keep trying to boot from it as long as nooter is on there.

wvcachi said:
Did you try taking the SD out and then booting? It'll keep trying to boot from it as long as nooter is on there.
Click to expand...
Click to collapse
Yes I did. It's doing all of this with the SD card out.

jbright44 said:
Yes I did. It's doing all of this with the SD card out.
Click to expand...
Click to collapse
I'd say interrupt the boot 8x (powering down will do) to initiate system restore, then re-root.

wvcachi said:
I'd say interrupt the boot 8x (powering down will do) to initiate system restore, then re-root.
Click to expand...
Click to collapse
Edit. That fixed it. Thanks. Man do I feel stupid. I thought the 8x reset and the 3 button method were the same. Apparently not. I'll try this again a little smarter hopefully this time.

Thank you for this thread. I thought I just bricked my 2 hour old nook. I stupidly restarted it after root with the nooter card still plugged in. Then I couldn't figure out why it was taking so long for the screen to turn on, so I kept pressing the button and then holding it. Then I realized the card was still in. Took the card out and tried to boot it, but it hung at the 'n' screen. The 8 interrupted boot method saved me from my stupidity though. Thanks.

Same here - left the card in...
8x reset and then a home and power reset cleared me up. Then update back to 1.1 and autonooter 3 again.
Loving it ever since.

hey
im having the same problem i did the factory reset to and nothing
wats the 3 count and wat else can i do

So what to do when factory restores and stock installs fail?!
OK... reviving this thread since it's my exact problem but I've been unable to find resolution. I've been searching everywhere for what to do next but nothing seems to be working.
I'm helping my buddy get his nook working. He said he was updating to 1.4 and when he rebooted it, it froze on the n screen. He plugged it back into his Win 7 machine to try the update again and it wouldn't mount as a USB device.
After a bunch of reading and fiddling, he built an SD card with ClockworkMod and installed in on an SD card. Or so he thought... he hadn't made it bootable. Over the phone, I walked him through restoring the image to his card and then it booted.
CWM comes back with a pile of errors. Specifically,
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When trying to format /data and /system, we also get errors.
We've downloaded various factory restore zips and tried installing them but they install (successfully according to CWM) and we reboot only to get stuck at the dreaded n screen again. We've done the 8 boot interrupt restore and get and error to call support (nobody answers this week) and done the regular power/+/n restore and it completes but leaves us again on the n screen.
Can anyone tell me the significance of these errors in CWM? It's the only thing different from all the tutorials and video walkthroughs we've followed and although we've seen these errors in other posts, there's never been a good explanation of them and how to resolve them if necessary.
Also, what is the latest version of CWM for the Nook Color and where do I find it? Is there an official site for CWM? Seems like people are just linking to older versions and sources all over the place with no common "go to the CWM site and get latest build of CWM." The latest I've found is 3.2.0.1 in a post back in August 2011.
Thanks in advance! Hoping this gets us over this hump and helps anyone else in the in the same situation.
moose

Solved it...
I've managed to solve the problem I outlined above. I'm not at home right now, so I'll post the specifics once I can get back and post the links and images I used to get this working.
Note that I had no concern for the data/books/apps that were on the device originally. I just wanted it working again with stock 1.4.1.
Basically, I noticed that after restoring to 1.1, the initial screen said "welcome to the future of reading" and then when I updated to 1.2, it said "read forever" so I knew the updates were at least doing something. I now needed to get rid of the errors in CWM 3.2.0.1 so started looking for something to blow away corrupt (?) partitions.
I found a post that had two zip files and it said they repartitioned the nook entirely. I hoped they would blow away my corrupted partitions by rewriting the partition table. I ran one, and it forced me to reboot. Then I ran the second and rebooted. It loaded up, got to the n screen and paused just long enough for me to lose some hope and then flipped over to the nook color boot animation. Yah! Progress!
Tried to register the device using my own bn.com account but wasn't successful. Turns out that you need to either use the original registered account on bn.com or unregistered the nook from his account, but since the error shared the same wording as previous failed factory restores (but this time in the nook registration interface), I assumed it was something locally. I came across a post in the searching that mentioned the need to unregister the nook from the original account to register it on another.
While trying to figure out what to do, I found a 1.4.1 signed stock image that also reconfigured the restore on the device and worked through CWM "install zip from SD" rather than using bn.com update zip via usb (i was still having trouble accessing the nook via usb at this point).
I downloaded the stock cwm 1.4.1 zip and installed it through cwm 3.2.0.1. It booted and then I saw the intro video on the nook registration page had a different woman. I got my buddy to send me the email and password he registered the nook with and the registration process was successful. I now have a working stock 1.4.1 nook color to return to my buddy.
I'll post the actual links to the posts/images that I used once I get home.
Hope this helps others!

I'm also getting the E: Can't mount / errors.
Will try this when I get home.
Also i'm just realizing now that i am using an older CWR v3.0.0.5, so that might be my issue also.

links
Mooseroo Could you please post links used to fix this issue

Try using this version of CWR. Just remember you can always choose a recovery image smaller than or the same as your SD card but not larger.
http://mrm3.net/blog/2011/03/11/nook-color-updated-clockwork-recovery-bootable-sd/

this is not working. same issue with nook 1.4.1 and CM7...hangs at "N" or goes black with CM7

Have you check the MD5 of all your files to make sure you have good downloads? It is frequently a skipped step but one of the easiest and first things you need to check.

Mooseroo - where are you?
mooseroo said:
I've managed to solve the problem I outlined above. I'm not at home right now, so I'll post the specifics once I can get back and post the links and images I used to get this working.
Note that I had no concern for the data/books/apps that were on the device originally. I just wanted it working again with stock 1.4.1.
Basically, I noticed that after restoring to 1.1, the initial screen said "welcome to the future of reading" and then when I updated to 1.2, it said "read forever" so I knew the updates were at least doing something. I now needed to get rid of the errors in CWM 3.2.0.1 so started looking for something to blow away corrupt (?) partitions.
I found a post that had two zip files and it said they repartitioned the nook entirely. I hoped they would blow away my corrupted partitions by rewriting the partition table. I ran one, and it forced me to reboot. Then I ran the second and rebooted. It loaded up, got to the n screen and paused just long enough for me to lose some hope and then flipped over to the nook color boot animation. Yah! Progress!
Tried to register the device using my own bn.com account but wasn't successful. Turns out that you need to either use the original registered account on bn.com or unregistered the nook from his account, but since the error shared the same wording as previous failed factory restores (but this time in the nook registration interface), I assumed it was something locally. I came across a post in the searching that mentioned the need to unregister the nook from the original account to register it on another.
While trying to figure out what to do, I found a 1.4.1 signed stock image that also reconfigured the restore on the device and worked through CWM "install zip from SD" rather than using bn.com update zip via usb (i was still having trouble accessing the nook via usb at this point).
I downloaded the stock cwm 1.4.1 zip and installed it through cwm 3.2.0.1. It booted and then I saw the intro video on the nook registration page had a different woman. I got my buddy to send me the email and password he registered the nook with and the registration process was successful. I now have a working stock 1.4.1 nook color to return to my buddy.
I'll post the actual links to the posts/images that I used once I get home.
Hope this helps others!
Click to expand...
Click to collapse
Just found this thread and I have the same issue - can you post the links you reference? Please?

tmccully said:
Just found this thread and I have the same issue - can you post the links you reference? Please?
Click to expand...
Click to collapse
I think he's talking about my files in this post.

[Q] Help|Endless loop and system failure

The Story:
I bought a new Nexus one.
Got the OTA updates and updated the phone (first 2.1 then 2.2 and 2.2.1)
Since then the phone is not rebooting properly. usוally it just reboot and reboot and reboot.
After I formated the SD card the phone booted succeussfully but crashed again after a minute back to the endless loops.
can someone please help?
I tried to unlock the bootloader, root the device and flash Amon's recovery but although the cmd windows said that it ewent alright besides of the open lock sign nothing seems to change.
Please Please Please Help, It's a brand new phone...
p.s.
if there is any way to just erase everything (already tried earse cache and userdata from the recovery...) and get a "new" phone - please tell me how.
I know how to use adb/fastboot, I'm not a noob...
Thanks a lot!!!

Where is my question...?
I can't find it...

It's right here.
Anyway, I suspect your problem after flashing recovery is you're rebooting, and the OS is reverting to stock. Go straight into it first, take a backup and wipe it.
Failing that you'll need to grab FRG83 image from http://developer.HTC.com and use fastboot to flash over system.img and boot.img

You'll be able to format every partition on your Nexus One by using Clockwork Recovery.
By Amon's recovery you can do similar thing but it doesn't offer ability to format System partition (it's not quite useful to format System partition anyway..)
You mentioned that your phone could boot successfully with a formatted SD card and then ran into problem, my guess is that your SD card has bad block(s), please verify this by take your SD card out and use your phone for few hours, is there any stability issue?

so... an update:
I downloaded the original files and flashed them all in fastboot (recovery.img, userdata, boot and system).
The phone is on the "nexus-one sign" screen for over then half an hour now and nothing seem to change.
a. Is there somthing else that I should do? how long it should take...?
b. what are the odds that it's a hardware problem...?
c. could it be a problem related to incompatible radio?
Thanks...

and other update...
even after reflashing the original files I can't enter recovery (original) so I guess the problem lies within it.
with this information and the other messages - does anyone has an idea...? please...?

did you try another SD card?
try this and let me know if it works
kuldrivedotcom/host/n1/Back2Stock.zip
just unzip the file and follow the instructions.
let me know if it worked
nexus @ kuldrive dot com

PCNemy said:
try this and let me know if it works
kuldrivedotcom/host/n1/Back2Stock.zip
just unzip the file and follow the instructions.
let me know if it worked
nexus @ kuldrive dot com
Click to expand...
Click to collapse
Thank you, but the problem solved.
It was a big HARDWARE problem.
HTC knew right away what the problem is.
Sent the phone to HTC, got it back in 3 days, everything work just fine since.
Thanks anyway...

[Q] N1 tried everything i could find

Hi everyone,
My N1 is stuck on the X, but my problem seems to be different to the other "my nexus is stuck on X" threads, as I've tried everything that was suggested and am still stuck...here is as much info as I can give.
My phone is rooted (has been since day 1 when it first came out) but I had not used it in a while.
The last rom I had on there was Cyangenmod 5.0.5 (or something like that.)
I booted into recovery (amon_ra from back in the days) and tried to flash Cyanogenmod 7.
The phone booted up, got passed the X but got stuck on the android on the CM circle with the rotating arrow...only the arrow was not rotating.
Anyway, I went back into recovery, and tried again...same thing...so I tried 5.0.5 and that worked.
Happy with my success I tried to install clockwork and try again...
this time, the phone got stuck on X...
tried going back to 5.0.5 but again, phone stuck on X.
So I tried to go back to stock.
fastboot flash boot boot.img and user data.img worked fine but system would fail.
I tried the PASSIMG.zip, but 7) system was fail-PU
read some more and some people said that with hboot 0.35 this was not possible, so I managed to downgrade to 0.33, but that didn't help either.
I've tried Clockwork and Amon
older roms and newer ones
PASSIMG.zip from different sources...nothing has worked.
In hboot now i have 0.35 and underneath I have a B (which I think is for amolded)
I've can't seem to get ADB to work either...I have done in the past, but for some reason this is not working for me this time...fastboot yes.
Could anyone PLEASE help me...
Thanks,
Lou

Fail-PU means Failed Partition Update, means your internal memory on /system partition couldn't be written, means a dead NAND, means your phone is really bad.
You could try to recover from it by using Blackrose hboot, and repartitioning the device.

Blackrose it is...I'll try that..thanks
L

So I got blackrose on, but that didn't help...still the same thing...
I've given up on the phone, but I'd still like to solve this, now that I've devoted som much time into it
L

You don't need to just load Blackrose, it won't solve a thing. You need to repartition your phone, making sure that the /system partition isn't sitting on the bad block. Try to move /system partition forward, making /data smaller.

I partitioned it as per the blackrose thread...are you saying i should use different values? could you recommend some to try?
L

I can't, because I don't know where the failure might be on the /system partition.
Try to change values between /system and /data, for example (move /system into /data). Just for testing. You'll need to find some position for it that won't cause write failures, and there's nothing I can suggest but to try and see at what address the failure seems to be, and repartition in such way as to exclude this address.