I've been searching for a solution to this, but most posts assume you can get into recovery and I can't. In short, I let an acquaintance borrow my rooted Nook running 4.2.2 and TWRP from internal memory, and he called me 2 days later and asked why it is just rebooting to the Nook logo over and over. I got it back and best I can guess he must've tried flashing something though he says he didn't. Anyway, it never gives me a chance to get to recovery, and with it rebooting I can't access it via adb. I've tried several bootable sd images but only once did it even try and within a minute it was rebooting again without trying to run from sd. I've tried a SanDisk 8GBP and a Kingston and an off brand and I can't tell if I'm wasting my time or if someone can confirm that it isn't unrecoverable and help me identify a recommended bootable image and card.
Thanks for any help.
Sent from my SCH-I535 using Tapatalk 2
My NT (which was running CM10.1.3) recently while running the usual apps got into a spontaneous CM boot-loop, then as its battery started to get really low the boot-loop got no further than the "N" logo.
I'd suggest you first try charging your NT, then test to see if it would run a pre-made CM10.1 or 10.2 image on SD (available at http://iamafanof.wordpress.com/). If the test is successful, you can the proceed to re-install CM internally following the process outlined at http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123.
FWIW, I've come across reports of similar spontaneous boot-loop incidents on NT and HD+ running 4.2.2, so I don't think your boot-loop problem was caused by your acquaintance doing something he was not supposed to do.
That's good to hear. It doesn't seem to want to charge though because when I plug it in it powers on and then starts rebooting and I can't figure out how to get it to power down. Do you have any ideas?
Sent from my SCH-I535 using Tapatalk 2
I'd suggest trying one of the following approaches:
Power it off, put in a bootable SD card (i.e., with a CM SD image, or with boot files and CWM/TWRP recovery), then plug in power cable.
Power it off (by holding down the power button for 20-30 sec) after plugging in the power cable.
[As a last recourse] Let the boot-loop continue to drain the power totally, then plug in power cable to start the charging (you'll need to use the BN power adapter and leave it charge for at least 4-6 hours).
Thanks for the response. I couldn't get those to work straightaway so I burned a bootable CM image to multiple SDs and got it to boot and charge, and then I was able to reinstall recovery in emmc and it's working again. Thanks so much!
Sent from my SCH-I535 using Tapatalk 2
Related
Firstly, it should be noted that I'm a noob.
I just bought this Nook Tablet 8GB today. I tried following Adam's post on downgrading a 16GB NT to 2.1.0. Attempting this on my 8GB seemed to be working as it was seemably installing the "update" with a yellow loading bar. It never booted, and its been a black screen since.
I have an SD card, with Adam's UbuntuTotalReflash image burned on it, to boot from, but I cannot tell if the device is on or off. Is there a way to boot it using a software through USB? Someone please help. Thanks.
I am having the same problem, installed the acclaim 1.4.0 downgrade on a 8 GB 250A nook tablet and now it doesnt power on. The computer recognizes it as an OMAP when its plugged in but it does not boot. please help
do not use Adams total wipe wait a bit that meghd00t is cooking something for the bricked 8gb nook tablets, and i be helping with support.
For now try to boot something else from sdcard like cm7 or the new recovery made by meghd00t that is proven to work fine for the 8gb NT.
If you press power button for 20 minutes or so it may power off. You can tell because of the color screen under the light if is black black with no signs of light in a corner then is off but if you see some blue with some light to the top right corner then is not completely off and if that happens it will for sure overheat your tablet.
Hmmm maybe you can use the method to put it in a fridge for 2-3 hours, check it up.
The goal here is to make it boot up even if it's from sdcard only for now.
~ Veronica
Try USB BOOT?
No matter what I've done to mine in the past, it would always boot by inserting the USB cable (preferably plugged into charger not PC) with a Bootable SD card installed.
My 2 cents
Yesterday I had some serious problems accessing the sd cards of my GS2 (international i9100 no letter; NeatROM with SiyahKernel S2-v6.0beta5).
After detecting there where some scrambled files at the internal and external sd cards root directorry.
I tried connecting it to my computer, but just the external sd card was accessible.
I also noticed, that mounting the device on my computer takes longer than I’m used to.
I re-flashed a 3parted Stock Rom (I9100XWLP7) to re-partion, did a factory reset after booting and all was working again.
So, I did start restoring my files and applying my settings.
After ~ 2 hours, the display and LEDs flickered multiple times, then my GS2 powered off.
I tried to power it up again, but nothing happened.
I pulled of the battery, waited for about 15 minutes, reinserted the battery and it powered up.
But then it hangs at the GS2 logo and not booting any further.
I’m not certain, but I think, there was a gentle “buzzing” from inside the device, after reinserting the battery for the first time, while the boot logo was showing.
I can boot into recovery and download mode and the batteries are charging.
My GS2 is still in warranty and I hadn’t re-flashed NetROM at this moment.
Should I try re-flashing it again, trying something different or should I just send it in for warranty?
The story began when I decided to install CM10 on my nook tablet using old recovery that goes for CM7 and eventually broke my partition table and lost my ID(./adb devices shows 0000000000000000). Since my nook refused to boot futher than CWM loading screen (box) i decided to recreate my partitions through ADB using this method and then reflash nook with AdamOutler's Ubuntu recovery (he provided his own mmcblk0p5).
So, I succesfully recreate partition table (everything was in order, I checked a few times) and reflash it with Ubuntu recovery. Interesting part starts here. Now i get "bla-bla-bla please restart your device" and picture with exclamation mark. A couple of reboots gave nothing and brought me to the same screen. Reflash with BN factory recovery as well as factory reset did not work. At that point I decided to inspect partitions again. Everything was ok, formating, size, etc. But my ID still was 0000000000000000. This brought me to the conclusion that something is wrong with mmcblk0p5 and i need to flash partitions with dd again using this files (method). So, all went well without errors, at the end i killed adb server, dismount SD and pressed "reboot device" in CWM menu. And... From that time my nook is completely dead.
It didn't respond to any key. I charge it all night. I tried to hold home+power simultaneously. No response. Connecting to a computer or power outlet is also nothing.
Be kind, I'd like to hear your advice. Sorry for my runglish.
WidePants said:
The story began when I decided to install CM10 on my nook tablet using old recovery that goes for CM7 and eventually broke my partition table and lost my ID(./adb devices shows 0000000000000000). Since my nook refused to boot futher than CWM loading screen (box) i decided to recreate my partitions through ADB using this method and then reflash nook with AdamOutler's Ubuntu recovery (he provided his own mmcblk0p5).
So, I succesfully recreate partition table (everything was in order, I checked a few times) and reflash it with Ubuntu recovery. Interesting part starts here. Now i get "bla-bla-bla please restart your device" and picture with exclamation mark. A couple of reboots gave nothing and brought me to the same screen. Reflash with BN factory recovery as well as factory reset did not work. At that point I decided to inspect partitions again. Everything was ok, formating, size, etc. But my ID still was 0000000000000000. This brought me to the conclusion that something is wrong with mmcblk0p5 and i need to flash partitions with dd again using this files (method). So, all went well without errors, at the end i killed adb server, dismount SD and pressed "reboot device" in CWM menu. And... From that time my nook is completely dead.
It didn't respond to any key. I charge it all night. I tried to hold home+power simultaneously. No response. Connecting to a computer or power outlet is also nothing.
Be kind, I'd like to hear your advice. Sorry for my runglish.
Click to expand...
Click to collapse
I'm having the same problem. I downgraded from 1.4.3 to 1.4.0. I was able to boot it once and then shut it back down so I could root it. Now it won't start up at all and I have tried everything that I can find to boot it to no avail.
The NT can sometimes get stuck in limbo while booting up, especially with SD-based boot. To get out of it, hold down the power button for 20-30 sec to turn it off then power it on again. Also remove any "bootable" SD card from the card slot; if it boots then the card was not bootable and its non-bootability was the problem.
It's also possible that the NT battery is completely drained (battery readings on some CM builds can be quite off, sometimes as much as 20 points) in which case you'd need to use the BN wall-charger and charge it for 8-12 hours.
Hi all,
Ok, so I have a weird problem with my Asus TF101 that for the life of me I can't seem to solve myself. Which is why I finally decided to ask for help.
To make a long story short: About two years ago I bought a used TF101 that I have been very happy with so far. And I definitely don't want to give it up, as it's been working fine until a few weeks ago. Then those boot loops (that everybody seems to be talking about) started and I was able to revive the device once by leaving it plugged off for a few days until the battery was empty (thus, I think, forcing a clearing of some kind of cache) and then re-booting it. Unfortunately, this does not seem to work anymore.
My TF101 has been rooted by the guy that owned it before. It features TWRP in version 2.2.1.4 and an older KatKiss ROM. Now, my situation is as follows:
Boot loops are preventing me from getting past the boot screen. I can thus not install or use any apps.
I can enter TWRP recovery mode and I could wipe the device, but I cannot find any ROM on the internal memory.
When connecting the TF101 to the computer (I'm using Linux Mint 17.3) it doesn't show up as disk. Only when unplugging it again, an error shows up on the Linux screen saying that the TF101 could not be connected. This is preventing me from loading a new ROM onto the device via a cable.
The device doesn't seem to recognize an SD card (32GB), no matter if formatted as FAT32 or as EXT3, with or without SWAP. So, in the TWRP file manager I cannot access an external SD card to load and flash a ROM.
When I enter "Mount" in the TWRP menu, I can't seem to switch to "Using external SD": When doing that I get an error "E:failed to mount /sdc (No such file or directory)" in the terminal window.
I have been reading forums up and down, but can't seem to find any helpful advice that applies in my case. I'm guessing the boot loop would disappear, if I could flash a new ROM, but I don't know how to put that on the device. Also, in case some of the problems are caused by version of TWRP that is installed, I would like to update that... but, again, I don't know how to get the new version on the device. I thought about entering APX mode, but holding Power and Vol+ simply turns my display black after a few seconds... no sounds, no beeps, nothing showing up on my desktop.
Any ideas? Pretty please?
Any help would be much appreciated.
Thanks in advance.
Hey all,
I installed Omega ROM v6.1 on my i9300 and for a while it was good.
Unfortunately one day it decided to crash and crash hard.
It was stuck in a boot loop and so I decided to wipe all the system, cache and factory reset in TWRP.
I then tried to reflash the ROM but it did not reinstall the full thing.
I believe this was down to the fact that I did not perform format data, as I have some mp3's on the internal storage that I wanted to save.
I tried to copy the files from the internal storage to the external micro sd card. This worked at first but then it quit part way through.
I thought this was due to the low battery so I charged and tried to resume. However whenever I tried to copy or move the files over to the external storage the next time it just failed.
I tried to do this a few times as I noticed it would work for a few seconds or a minute before quitting and so thought I could get them all eventually.
The total size of the folder is 2.4GB.
After doing this a few times my phone then decided to boot loop TWRP. It will sit on the startup screen of TWRP but when you try to do something it then resets.
I am running TWRP version v2.3.1.0.
As mentioned before I cannot connect my phone to a computer as the connection port is broken too.
Any help on this matter would be appreciated. I have searched the web for hours but found no such luck.
Kind Regards,
Shaun
You can try reflashing twrp but don't hold your breath.
Without the usb port the device cannot be flashed unless you have mobile odin, for which your device needs to be working.
The only other way is try holding all of the buttons on the device until it boots. Sometimes devices do a reboot when you hold all of the buttons. You must be exact and get all of them at precisely the same time. If no joy then the phone is goosed.
Thanks bro
Thanks for your help, a week or 2 later it decided not to turn on at all....
Think it's toast mate.
Just grabbed and s7 instead