I updated to the new version of the software a few weeks ago and have had trouble with my SD card ever since. Today I was transferring an app to my SD card, when the phone reset on it's own. I tried to turn it off to do a proper boot, and it went to the BLU screen but never changed from there, it's stuck on that screen. I don't know how to remove the battery on this thing, it's screwed in or something. I tried holding the power button, tried holding the volume up button, but it's not responding at all.
Please help.
EDIT: Okay, got it to reboot, but I REALLY need to downgrade my operating system. Does anyone know how I can roll back the update from last month?
Terrabull said:
I updated to the new version of the software a few weeks ago and have had trouble with my SD card ever since. Today I was transferring an app to my SD card, when the phone reset on it's own. I tried to turn it off to do a proper boot, and it went to the BLU screen but never changed from there, it's stuck on that screen. I don't know how to remove the battery on this thing, it's screwed in or something. I tried holding the power button, tried holding the volume up button, but it's not responding at all.
Please help.
EDIT: Okay, got it to reboot, but I REALLY need to downgrade my operating system. Does anyone know how I can roll back the update from last month?
Click to expand...
Click to collapse
If it was an official update and not a modified one,then no we don't currently have any roll-back.
Related
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
I did a manual shutdown because I couldn't kill some goofy NES rom app. Now it won't reboot. Do I have to replace the SD card with the imaged one every time I want to restart this thing?
No... Sounds like you medded something up when you manually rebooted, though. Oh well, just restore to factory and reroot and you should be fine Id bet...
Sent from my NookColor using XDA app
Crapcrapcrap. I think I broke it.
I tried to do the factory reset as you suggested but it wouldn't do ANYTHING. I did some more searching and finally got it to work by holding power button plus volume up plus home button and then holding power button. But it went to the future of reading screen and then the Nook screen and wouldn't do anything. More searching told me to reset it 8 times and on the 9th it would completely restore factory, so I tried that.
It seemed to have worked but then went into ANDROID boot/initialize sequence and was repeating that over and over and over. Seems weird that it would boot Android after a complete reset, but I digress....
I thought maybe it was because the imaged card was not in, so I inserted that into the slot. Same thing....repeat over and over Android boot up sequence.
I powered it down manually and it seemed dead again - not booting back up by traditional means. I tried holding different buttons, whatever...FINALLY got it to the future of reading screen again. Proceeded to boot up - Android sequence....you guessed it, on repeat. No card in now. Crap!
Please help! Newbie here not sure what to do!
your case is similar to what I experienced yesterday. I took out my memory card, and did factory reset and 8-time reset trick. On the 9th it installed a fresh rom (1.0.0), and booted successfully afterwards.
jerry_smith_80 said:
your case is similar to what I experienced yesterday. I took out my memory card, and did factory reset and 8-time reset trick. On the 9th it installed a fresh rom (1.0.0), and booted successfully afterwards.
Click to expand...
Click to collapse
Thanks for the response jerry. Something is definitely jacked here.
I did the 8-time reset again....Got the message it was installing a software update, the future of reading screen, etc.....and then it went into the freaking Android boot sequence on repeat again. Why is it booting up Android instead of 1.0.0?
No memory card here, either. I am totally flustered.
I would really appreciate any help that anyone out there can provide. Did I brick this thing?
Update. I powered it down from the Android reboot cycle and then followed the instructions here to perform another factor reset. Somehow this time it worked. It rebooted with 1.0.0 and made me go through the setup steps again.
I think I'm going to upgrade to 1.0.1 this time before rooting....I was having some bugs and somehow it culminated in the above debacle. Hopefully it is smooth sailing from here.
Something is still messed up here and I'm not sure what's going on.
As mentioned above, I finally got the thing to reset, clear, and boot back up with 1.0.0....or at least so I thought.
I had only ordered one book and it was present on the reboot - not sure if that is significant or not. At any rate, my initial plan was to update to 1.0.1 like I mentioned since I seemed to have issues/bugginess before w/ 1.0.0. I downloaded the .zip file to my desktop, copied it over exactly as instructed and the thing never rebooted with the update. I waited and waited. I put it to sleep and waited. I woke it up. I tried to navigate to it. Nothing.
Ok, perhaps another fluke. From what I've read the update is unimportant anyway. So I tried to root again with auto-nooter on 1.0.0. Followed steps again to a T. Even re-downloaded all of the files to my computer just to eliminate issues. Put my card in, plugged it into my laptop....never found any drivers. CN stayed off. Tried to boot it up manually - nothing. Tried to reset it manually w/ Power + home + volume up. Nothing.
Finally I removed the SD card and booted it up and it worked. During initialization I quickly put my card into the slot and it booted Android successfully....much like the first time I rooted it.
It is working...but not like it is supposed to. I'm wary to go down this path again considering the trouble I eventually encountered last time. Should I start over? What the hell did I do wrong?
I have 1.0.1 and used the correct autonooter and successfully rooted it. Although, after turning on and off the phone, I run into big problems. One time it got stuck in the boot screen and I had to do the 8x reflash thing. Now I'm getting the error "Battery too low to power ON. Please wait 15 minuets and try again" after charging for many hours! *EDIT* Now the reset method ("n" button, power, and +) isn't working. What am I doing wrong? I'm confused about what I'm supposed to do with the sd card. After rooting, do I leave it in for ever or do I take it out? I didn't even get adb working correctly.
Any help? Thanks
I'm sorry if this has been answered before, I searched but wasn't able to find anything.
It started when my phone suddenly didn't recognize the sd card. I took the card out and put it back in a couple of times, and reebooted the phone a couple of times. After that didn't work, I figured I would factory reset the phone, and as I did, it started to reboot, but was never able to boot back up.
When I now try to boot the phone, I get to the initial Samsung-S4 Active GT-I9295 -logo, and it says BOOTING RECOVERY in the top left corner, but after ~2 seconds it shuts off.
Interesting: It only boots a couple of seconds after I let go of the power button.
The phone was rooted using this guide: (not able to post links. The guide is on android geeks, and can be found by searching for Root Galaxy S4 Active (International I9295 and AT&T I337 models))
And Xposed was installed, but no modules were activated.
Firmware was 4.2.2 MF/MU 3 - something, I think. Sorry I cannot remember. I got it OTA some two weeks ago.
Any suggestions?
Thank you!
EDIT: When playing around with it, I managed to solve it. When booting, as soon as the logo appeared, I pressed and held the volume up + home button, which caused it to not shut down (?). It then preceeded to boot for a long time while, I guess, the phone was factory reesetting itself. Now it boots just fine, factory reset =D . (SD card still not detected )
My wife's phone is completely stock, I have never rooted it or anything.
A couple of days ago, she started getting a strange notification with the android icon and something called Smith with the message that it is disabled. Her phone would reboot itself a couple of times a day and now it is stuck in a boot loop. The phone has been stuck in the loop for a couple of hours now, stopping on the white android screen for a second and shutting down, rinse and repeat.
I can get into recovery by ONLY holding down the volume key, which is kind of strange. I also cant select anything in recovery.
Any help would be appreciated, she is about to kill me and switch to an iPhone.
allstarfung said:
My wife's phone is completely stock, I have never rooted it or anything.
A couple of days ago, she started getting a strange notification with the android icon and something called Smith with the message that it is disabled. Her phone would reboot itself a couple of times a day and now it is stuck in a boot loop. The phone has been stuck in the loop for a couple of hours now, stopping on the white android screen for a second and shutting down, rinse and repeat.
I can get into recovery by ONLY holding down the volume key, which is kind of strange. I also cant select anything in recovery.
Any help would be appreciated, she is about to kill me and switch to an iPhone.
Click to expand...
Click to collapse
Follow this guide - it should fix you up.
StormyNight said:
Follow this guide - it should fix you up.
Click to expand...
Click to collapse
unfortunately this doesn't apply to my situation because the phone has never been rooted
allstarfung said:
unfortunately this doesn't apply to my situation because the phone has never been rooted
Click to expand...
Click to collapse
Follow the instructions here then. Be warned though, this will wipe everything, including internal storage.
The Smith file is some file that HTC put into the ROM that expired in mid-August. Ever since then, the app shows as expired when you reboot. Nothing you can really do about it if you are not rooted, but HTC is supposedly working on a fix that they will push via OTA.
However, it shouldn't be causing the bootloops as far as I know. If a factory reset doesn't work, then running the RUU is most likely the way to go.