Database Develop

New update bricks NC

Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?

gtechnical said:
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
Click to expand...
Click to collapse
Do a factory reset, install the update, then use the new autonooter.

how to do a factory reset? thanks, I am a newbie to this area!

Not sure how much I can help-
Just how "bricked" is it?
A truly bricked device will do nothing. It will not start or do anything whatsoever.
A machine that is thoroughly HOSED may get stuck in a boot loop, or try to start and fail every time you press the power button.
When I forced the update manually it took a few minutes to take and reboot; how long ago did it do the update?
Have you tried connecting with adb yet?
Have you tried booting it with a nooter or auto-nooter sd card yet?

http://nookdevs.com/Installing_the_1.0.1_update_on_a_rooted_NC
Instructions for manually updating.

Here is my situation:
Around 9:30, my NC started updated itself, it reboot in about 15 minutes, and takes a very long time get to the "nook color" screen, then took another 10 minutes letting me select "home or zeam", after that, it has no response.
I tried to reboot, it got up to the "Nook Color" welcome screen, no further response!
I tried to factory reset, not working through adb, it did appear on the adb devices command!

Do a factory reset and start over.

I ran into a similar problem, but here is what happened to me:
1. I reset the device to factory settings.
2. I rebooted the nook 8 times, stopping the boot process. This took my NC back to factory version and no rooting at all.
3. Installed NC update 1.01 per B&N instructions.
4. Used AutoNooter (latest version for 1.01). AutoNooter rebooted the device as it is supposed to.
5. After AutoNooter reboot, I installed Astro File Manager and then after that the NC stopped responding to screen touch.
6. I held the power button to shut the device down. Strangely, the screen shut off and it appeared to be shut down, but I think it did not truly shut down.
7. I could not turn the NC back on. I tried to reset to factory settings 2-3 times and no response.
8. I plugged in my NC as if to charge, and it went through the boot process.
and it has worked just fine since then. To be honest it kind of scared me, because I love this thing to death, but I remained calm and kept at it and it was not bricked. I guess what I'm trying to say is that before you post here that the new update bricks the NC, you should be absolutely sure it is bricked and not just frozen like mine was.

gtechnical said:
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
Click to expand...
Click to collapse
Brick, like you can't do anything at all anymore, might as well lay it on papers, use it as a door stop and pour cement to build a house?
That's what bricked means... If you still can access it via ADB, run recovery, etc.. it is far from "BRICKED"...
-CC

Boot Loop - Help Please

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

At wits end with Kindle Fire HD 7" (7.5.1) - trying to install TWRP

Hi -
I have searched these forums multiple times, had numerous brower tabs open trying to follow instructions, and am at wits end. I am hoping that someone here can help me. I have a Kindle Fire HD 7" which had version 7.5.1 on it. I've rooted, tried using Fireflash to flash TWRP, bricked it twice, recovered it (with the fastboot cable that arrived in the mail 2 days ago), and now I am unable to switch on wifi (I did see the recent thread about this). I'm not sure what I'm doing wrong. The first two times before flashing the TWRP, I did not downgrade to 7.2.3. Could that have been why it bricked both times?
I just did another reset to factory defaults to try to get wifi back, to no avail. I am doing all of this so that I can install a ROM to escape all of the Amazon interface limitations.
Edit: I should add that I have so many files downloaded now (different versions, per each set of instructions) that I am confused.
Update: I just used SRT_v1.3.0 to restore factory recovery and now my wireless is enabled!
I am afraid to use Fireflash to flash TWRP again after two failures.
Thank you for any and all input!
PnGa

NM: Got it working.

Pickngrin said:
NM: Got it working.
Click to expand...
Click to collapse
HOW?? FOR GODS SAKE HOW???
I'm in the same boat, just bricked it now I think, red screen when turning on, thats it

Don't panic... get a factory (Fastboot) cable and use the Unbrick app to revive it. I took so many attempts to get it successfully flashed with CM12. I believe that I was using the incorrect boot image file and had not downgraded to 7.2.3 first. But I don't really understand the whole process. Good luck!

Pickngrin said:
Don't panic... get a factory (Fastboot) cable and use the Unbrick app to revive it. I took so many attempts to get it successfully flashed with CM12. I believe that I was using the incorrect boot image file and had not downgraded to 7.2.3 first. But I don't really understand the whole process. Good luck!
Click to expand...
Click to collapse
Cheers mate... I will try and find out to make one...

Help with recovery

I came across another thread that seemed to help me a bit. Can't find it again. So, hoping someone can point me in the right direction or better yet, give me a magic solution
History - I have a kindle fire - 5th gen. Got it with 5.1.2 which upgraded automatically to 5.1.4. I sideloaded 5.1.2 and it worked just fine. However, I missed the fact that the bootloader is locked on 5.1.2 and tried to flash TWRP. I also blocked OTA updates. (Rootjunky's tool)
Current situation - I am rooted and on 5.1.2. I want to get to Cm 12.1, but I can't get into recovery at all. It is stuck on the "Amazon" logo when I try to get to recovery. It is not the blue logo - I have never seen it, but my logo's not blue. I'm able to boot normally and use the tablet without any issues.
Question - The thread I came across earlier said that a fastboot cable is the only way out. But this person seemed to be at the "blue amazon" logo. Help? Thoughts?

smvsmv said:
I came across another thread that seemed to help me a bit. Can't find it again. So, hoping someone can point me in the right direction or better yet, give me a magic solution
History - I have a kindle fire - 5th gen. Got it with 5.1.2 which upgraded automatically to 5.1.4. I sideloaded 5.1.2 and it worked just fine. However, I missed the fact that the bootloader is locked on 5.1.2 and tried to flash TWRP. I also blocked OTA updates. (Rootjunky's tool)
Current situation - I am rooted and on 5.1.2. I want to get to Cm 12.1, but I can't get into recovery at all. It is stuck on the "Amazon" logo when I try to get to recovery. It is not the blue logo - I have never seen it, but my logo's not blue. I'm able to boot normally and use the tablet without any issues.
Question - The thread I came across earlier said that a fastboot cable is the only way out. But this person seemed to be at the "blue amazon" logo. Help? Thoughts?
Click to expand...
Click to collapse
bootloader was always locked, but 5.0.X allows booting a custom Recovery
if it will not boot to recovery nor rom/system, nothing can be done
fastboot cable doesn't work with 5th gen fires
Sent from my DROID Turbo using XDA Labs

Thanks... When you say "if it will not boot to recovery nor rom/system, nothing can be done", I see a glimmer of hope. The only thing I'm unable to do is boot to recovery. I am still rooted and able to use the tablet fully. There are no issues with that.
Does that help?

smvsmv said:
Thanks... When you say "if it will not boot to recovery nor rom/system, nothing can be done", I see a glimmer of hope. The only thing I'm unable to do is boot to recovery. I am still rooted and able to use the tablet fully. There are no issues with that.
Does that help?
Click to expand...
Click to collapse
Thoughts:
- you can still flash a custom ROM but if something goes wrong during the upgrade you're screwed without a recovery environment.
- recent versions of FlashFire have the ability to preserve and rewrite the recovery environment; not certain if the process works on this device and potential side effects (if any).
- several months ago another contributor claimed to have resurrected the stock recovery environment via adb which created quite a stir at the time. Have not seen much since so I suspect the solution was not generically applicable.
- I'm of the belief that most recovery access issues are actually a booting problem vs a damaged recovery partition. Your situation may be a little different as you attempted to rewrite the recovery partition by flashing TWRP.

oh well.. I'll just wait for you brainy guys to figure a way out. Not messing with the device anymore for now. Thank you!

fix brick

one of the tablets roms was haveing sound issuses with dead trigger 2 so i decided to install another rom (cm12) and it seems to be in a boot lap and cant get into fire os recovery by holding switches is there fix for that?

Nightmare-Rex420 said:
one of the tablets roms was haveing sound issuses with dead trigger 2 so i decided to install another rom (cm12) and it seems to be in a boot lap and cant get into fire os recovery by holding switches is there fix for that?
Click to expand...
Click to collapse
Likely not. If CM 12.1 was installed incorrectly it can bork access to stock recovery. If so there is no known recovery at this time.
Quick test:
- untether device
- long press power (20+ sec) to insure device is powered off
- press and hold key closest to headphone jack (vol-up)
- while continuing to hold <vol-up> press and hold <power>
- release both buttons when screen comes on
What happens next?

ah dang that sucks and i think it was the xposed framwork that bricked it becuase i did it to the other tablet and it bricked but was able to recover and start fresh, howcome dose cm12 screw recovery while other firmwares don't and how do you get xposed installed without it causeing a brick?

now i was able to get into recovery and flash 5.1.2 back but now i cant seem to be able to get root back with kingroot giveng error 592 once and then other error (chinese text) i tried re-installing the 5.1.2 again an additional like suggested if kingroot fails.

Nightmare-Rex420 said:
now i was able to get into recovery and flash 5.1.2 back but now i cant seem to be able to get root back with kingroot giveng error 592 once and then other error (chinese text) i tried re-installing the 5.1.2 again an additional like suggested if kingroot fails.
Click to expand...
Click to collapse
- assuming you didn't register with Amazon when device initialized
- try different builds of KingRoot, in particular 4.8.5, 4.9.2 and 4.9.6
- avoid version 5.x; difficult to uninstall and/or replace KingUser with SuperSU
- patience is a virtue: http://forum.xda-developers.com/amazon-fire/general/fireos-5-3-2-arrived-t3500922/post70077755
- some individuals report trying "dozens of times" before finding joy