**
I think i just bricked it.
it is now stuck on the N screen
been stuck there for 10 minutes. not going anywhere
i am looking but cant find anything on what to do now.
any suggestions?
thanks guys
Hello,
I want the new upgrade so i was trying yo go back to stock but i must be doing something wrong.
first i tried method one
...Flash_back_to_clean_stock_ROM[/url]
and at 7 clockworkmod opens up and it never goes into the " re-flash its /system partition"
so then i tried connecting to my computer and using adb but it always just says there is no device found.
anyone have any idea on what I am missing?
my nook is 1.0.1
Have you tried the manual 8 interrupted boots?
yes and on the 7th interrupt clockworkmod started.
seems irreverent now that i am stuck on the n spalsh screen.
thank you for your reply
but i think i buggered things up
Related
I've had my NC rooted for 3 weeks. No probs. I decided to update to 1.0.1 to see if wifi was better and so I entered the adb command to force system update and all seemed to be well. After that it went into a boot loop.
I forced another "update" by powering down 8x during bootup. It reinstalled and then same problem. I then tried the directions at nookdevs to fix boot loops. I couldn't ssh into the NC, but to my surprise I could use adb, but I can't do the listed commands because I get "permission denied".
I did an adb logcat and I get nonstop info going by, mostly looking for stuff that shouldn't be there anymore, i.e. apps I loaded when it was rooted. Dalvik cache??
So, long story short, I've tried a system wipe 4x now and I'm stuck in an endless boot loop BUT I do have adb access. What now?
Power, +, N button doesn't work either?
norkoastal said:
Power, +, N button doesn't work either?
Click to expand...
Click to collapse
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?
GTOMEX09 said:
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?
Click to expand...
Click to collapse
Head over to Nook Devs for the breakdown of the two.. Both methods are requied for using the newest AutoNooter... Glad to hear the device is still in working order.
Stuck in Boot Loop
Noob here with a problem. I’ve had my NC rooted for 5 days and the rooting went well. I had all my favorite android apps up and running. However I was experiencing random reboots (2-3 times per day). So, I decided to unroot and let the 1.0.1 update install and then I was going to use Auto-Nooter 2.12.18 to get everything back.
I did the 8X reboot thing and after reloaded, the NC went into a boot loop. The first thing I tried to do was the n, volume+ and power button. It simply went back to the boot loop.
I immediately put the auto-nooter sdcard in the NC, plugged in the usb to the pc. As opposed to the other times I did this, I got no visual indication that the PC recognized or activated the NC. I waited the full 5 minutes and removed it. The boot animation had changed, but the NC stayed in the boot loop.
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
Before I ejected the NC I opened the command line window and I did adb devices and it came back with nothing. So now my NC is not recognized by the PC (and was before all this).
Can anyone point me in the right direction? Any help with the putty ssh screen issue? Any help will be appreciated.
Geezer Squid said:
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
.
Click to expand...
Click to collapse
Out of desperation I downloaded putty.exe again and it worked this time. Using the script on the nookdev.com website, the NC booted. I then did the data wipe and the 8X reset. I'm now back to stock (mostly) and I'll see if it updates tonight. If not, I'll force it tomorrow and don the new auto-nooter.
I'm learning!!
Glad you fixed yours too. This device is nearly impossible to brick unless you deliberately try to. Definitely easy to undo hard work, but hard to brick.
I have the same problem. Minutes after rooting with autonooter, my Nook restarted and I didn't even set up ADB access. I tried reseting several times with no luck Please help!!
Mine is currently stuck in a boot loop as well. I did not update to the newer firmware it auto-updated and jacked everything up. Pretty upset right now.
I know I can reset the device but I need to get the data from it first. I have the entire storage full of data that I need. It will not boot at all and if this gets erased i'll more than likely end up returning the device and purchasing something that I won't have this problem with every update.
Unfortunately, there aren't many devices that will automatically backup all your important data to external media without you having to take some action on your own to set that up.
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
Well, I'm not an expert, but I have been through this kind of thing. I would think you have two possibilities. One would be to put the nooter sdcard back in and hook it to the computer again. If it isn't very corrupted, it may automatically reload from the nooter sdcard.
If that won't work, then I think it's time to do the 3 finger data wipe and then the 8X reboot thing. You can then redo the nooter sdcard thing.
Good luck.
Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
EXACT Same thing happened to me and a friend when using autonooter and 1.0.1. I think there is a problem with autonooter or 1.0.1 messing up the booting process. I wonder whats wrong So I was able to do the 8X reboot thing and get back to stock 1.0.0 and from here I'll try to attempt to use autonooter for 1.0.1. But I'm staying with 1.0.0 until Froyo next month.
thanks! the 8x thing worked good, I did the whole auto noot process again and it works at all except by this market issue
Ok guys heres the deal, i have been trying to reflash NC stock and to no avail i get the same issue everytime no matter what version i use, i have even tried ADB, and that does not work.
Ok my problem is this everytime i try to boot it it just loops at the barnes and noble nook color screen forever. When i tried ADB my computer would not even find the device but it found 2 which when i tried to uninstall them they install right after so i cannot use ADB(and yes i turned off automatic driver install). So here is where i land and my question. Do i have a 300 dollar paper weight or is their hope, and if so please explain what i am doing wrong. Thank you for your time
First off...
are you trying to flash the stock B&N?
how are you trying to flash it?
do you have CWM or TWRP on eMMC or stock recovery?
if you're trying to use cwm or twrp to flash stock rom... see the customizing rom thread in my signature for modifications required.
ok i am trying to flash to the stock bn, i am using cwm, but when i do that it just loops through, and adb now does not even recognize the device so i can tie them together so to speak.
Ok, i did everything that forum on your sig told me to do got it installed but it still loops at the "barnes and noble Nook Color" flash screen. Any Ideas?
Now that you have stock on the nook color... do the 8 failed boots to cause it to erase data and deregister the device... it should bring it back to factory and resolve the boot loop issue
Finally! thank you so much for your help been working on this issue for 3 or 4 months now, it works just need to get it charged and hopefully it will take a charge.
Hey guys,
Long time reader and flasher, first time poster.
I just recently made a huge mistake (lack of sleep) and loaded Android Revolution HD for i9500 on my i9305.
I don't know what I was thinking, like I said lack of sleep. Anyway I went through with the process and got to a prompt asking to install SuperUser from the Recovery after Android Revolution successfully installed.
The device then rebooted and has been stuck at the Downloading... screen, I have tried rebooting into Recovery mode, it just goes to the same screen. I can boot into odin mode.
I have tried using heimdall to flash the recovery with something else. But I keep getting the following error: ERROR: Protocol initialisation failed!
I'm having a stab in the dark but I am guessing I have stuffed the partition tables or lost the IMEI.
I have done about 3 hours googling and searching theses forums and can't find an answer.
I have given up and was hoping someone could help me.
P.s. I'm running Ubuntu on my PC and do not have access to a windows or mac system.
Thanks for your help in advance!
Delete
Please Delete, I have fixed the problem.
I have no idea why it all of a sudden worked... but it did yay!
Thanks in advance
Does it boot into download mode?
Thats good, i was just going to say that if you can get into download mode then you should be able to flash the stock rom back
Hey guys!
Earlier today I rooted my another Android device so I wanted to try it with my Samsung Galaxy Ace S5830. I rooted it successfully, then I wanted to install a custom ROM...well, I wanted to upgrade it to Android 4.3 since I found a tutorial for it.
I downloaded two zip files, put them on the card, booted the phone into recovery mode and during installation of files, there was an error (Status 0), something like that. When I wanted to boot my phone, it could not boot up. It would just have that splash screen saying Samsung Ace S5830 and it would stay there forever.
I got back to the recovery mode and there is error saying "E:failed to mount /system (Invalid argument).
I figured out I messed it up, so I tried to flash it with Odin. However, after reading millions of guides, I failed to do it. I put my phone into download mode and it just says "Downloading..." on a black screen, there is no picture or anything like that, and I saw in the guides there should be one, so am I in the wrong mode?
Anyway, I "managed" to flash my phone. The process took ~10 seconds then rebooted my phone and I was waiting on a countdown (4 minutes or so), then it said my phone is done and I saw a blue button saying "PASS". However, my phone was showing only a backlight during that process, there wasn't anything like a download bar.
I restarted my phone, wiped cache and did a factory reset, but it's still unable to boot.
What should I do?
Thanks a lot!
AsPeHeat said:
Hey guys!
Earlier today I rooted my another Android device so I wanted to try it with my Samsung Galaxy Ace S5830. I rooted it successfully, then I wanted to install a custom ROM...well, I wanted to upgrade it to Android 4.3 since I found a tutorial for it.
I downloaded two zip files, put them on the card, booted the phone into recovery mode and during installation of files, there was an error (Status 0), something like that. When I wanted to boot my phone, it could not boot up. It would just have that splash screen saying Samsung Ace S5830 and it would stay there forever.
I got back to the recovery mode and there is error saying "E:failed to mount /system (Invalid argument).
I figured out I messed it up, so I tried to flash it with Odin. However, after reading millions of guides, I failed to do it. I put my phone into download mode and it just says "Downloading..." on a black screen, there is no picture or anything like that, and I saw in the guides there should be one, so am I in the wrong mode?
Anyway, I "managed" to flash my phone. The process took ~10 seconds then rebooted my phone and I was waiting on a countdown (4 minutes or so), then it said my phone is done and I saw a blue button saying "PASS". However, my phone was showing only a backlight during that process, there wasn't anything like a download bar.
I restarted my phone, wiped cache and did a factory reset, but it's still unable to boot.
What should I do?
Thanks a lot!
Click to expand...
Click to collapse
Did you read rules?
Did you search for help?
Do you know that it's not the correct section to post your questions?
PLEASE USE Q&A ThREAD!! We need to keep clean general section!
Which model have you got?
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
dorkydroid said:
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
Click to expand...
Click to collapse
try stock 5.1.2 firmware
otherwise there is no fix that I know of
Sent from my KFFOWI using XDA Labs
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
dorkydroid said:
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
Click to expand...
Click to collapse
I fear I'm in the same boat. Which version of flash fire were you using?
Any further progress?
Sent from my Nexus 7 using XDA-Developers mobile app