Okay, so short story shorter:
I bought a Nook Tablet off a friend. Rooted and installed CWM7. It was running perfect. I was using a music downloading app that I've used on three other devices without issue and got a virus. The virus drained the battery, now it's stuck in a boot loop. It gets to the initial silver "n" boot up screen then shuts off and just keeps repeating.
Is there anyway to fix this or did I just waste $90?
Related
Hi there!
I have a friend who has this phone, Nexus 4, which has some problems..
Out of nowhere it startet to not start. It boot up fine, gets into Android, and the first thing it does is shutting it self down. I get the message "shutting down" and there is this "loading screen" as if I had done the shutdown sequence myself.. Which I am most definitely not doing!
I thought that deleting everything and doing a foctory reset would do the trick. This turned out to delete everything, including the OS. After that happened the red light of doom started showing up. It turns out the phone was completely drawn for battery, which I fixed by putting the battery in a "professional" charger. The same charger I power up my RC batteries with. When this was done it once again booted, and I got to flash a new 4.4.2 OS onto it.
And then it starts to shut itself down again..! Every single file is deleted and reseted. I have even switched out the battery with a new one. Just too be sure..! Does anyone have a trick I could try?
Thanks in advance!
Hello,
My Pioneer R1 tablet the other night decided to do an automatic upgrade when booting up and hung for hours on 14 of 18 files updated. I rebooted the tablet for it to get to the home screen but come up with the error android phone services not initinalized and then froze. so rebooted and it got to the animated pioneer logo and just sits there never loading fully. Pioneer customer support sucks with helping and the tablet has a reset button on the back in a pin hole. I pressed that the tablet turns off. The tablet still stuck on animated logo.The tablet was running stock jellybean 4.2. The Pioneer people didnt want to do any troubleshooting. told me to send it to them to fix and that if they found anything wrong other than hardware issue i am liable for the charges on to of the shipping cost. I dont have money to just hand out to people who dont have a system setup for troubleshooting. Sorry for a long story but my question is is there anyone who can help me fix this issue.
Been running the GPE ROM flawlessly since I flashed on the 12th... Until today. Don't know if this is ROM related but maybe you guys can help.
Out of nowhere, my phone kept shutting off. Couldn't use it for more than a minute after booting before it would turn off completely. Battery was charged so I was kind of like 'wtf'. Then all of a sudden it wouldn't even get to the swirling colors boot screen. It would shut off halfway though the Samsung Custom logo. ****.
Tried plugging it in and pulling the battery multiple times. I can't even boot to recovery! The blue text shows in the upper left but then it will go off again. It's plugged in now but not showing the battery charging screen.
I can only get it to turn on for about a second. Am I ****ed? Is this thing bricked? Super random because I changed NOTHING this morning and it was fine yesterday.
crovax33 said:
Been running the GPE ROM flawlessly since I flashed on the 12th... Until today. Don't know if this is ROM related but maybe you guys can help.
Out of nowhere, my phone kept shutting off. Couldn't use it for more than a minute after booting before it would turn off completely. Battery was charged so I was kind of like 'wtf'. Then all of a sudden it wouldn't even get to the swirling colors boot screen. It would shut off halfway though the Samsung Custom logo. ****.
Tried plugging it in and pulling the battery multiple times. I can't even boot to recovery! The blue text shows in the upper left but then it will go off again. It's plugged in now but not showing the battery charging screen.
I can only get it to turn on for about a second. Am I ****ed? Is this thing bricked? Super random because I changed NOTHING this morning and it was fine yesterday.
Click to expand...
Click to collapse
It could be a power button failure, it's actually quite common on the S4.
Google "Galaxy s4 power button problems"
Check out this link:
http://forum.xda-developers.com/showthread.php?t=1931310
Hi,
I have Nextbook Premium 8SE and I have been using it for some years. Last month I installed some games and the tablet was fine. The next day the tablet was turned off, I thought that the battery was out so I put it on charger and turned it on. Since then the tablet is stuck at the first boot image, the tablet just stays on the first image and after 1 second the screen brightens and nothing happens. What could be the problem? I cannot go into recovery, I've tried everything software related.
I guess it is goodbye tablet...
So my kid has a 3rd Gen Fire. I got it for him like 3 yrs. ago. At the time I loaded TWRP and CM11. Been fine ever since. Yesterday evening he claims while playing some Minecraft like game (Block craft 3D) the tablet screen went black and the boot loop started.
Now it's stuck there, it restarts itself every 35-37 secs (timed), and only reads "Kindle Fire" in white, then screen flashes and repeats. I can hold power to turn off, volume up/down combinations do nothing.
I used the factory cable, but device manager doesn't pop up anything. I told him high chances it's dead. Yet it'd be awesome to be able to go back and tell him I fixed it.
Does anyone have any further suggestions? or confirmation this is a end of service life type error? TIA
tavuslokus said:
So my kid has a 3rd Gen Fire. I got it for him like 3 yrs. ago. At the time I loaded TWRP and CM11. Been fine ever since. Yesterday evening he claims while playing some Minecraft like game (Block craft 3D) the tablet screen went black and the boot loop started.
Now it's stuck there, it restarts itself every 35-37 secs (timed), and only reads "Kindle Fire" in white, then screen flashes and repeats. I can hold power to turn off, volume up/down combinations do nothing.
I used the factory cable, but device manager doesn't pop up anything. I told him high chances it's dead. Yet it'd be awesome to be able to go back and tell him I fixed it.
Does anyone have any further suggestions? or confirmation this is a end of service life type error? TIA
Click to expand...
Click to collapse
What does it do when connected to wall charger?
Sent from my Chromebooks using XDA Labs
sd_shadow said:
What does it do when connected to wall charger?
Sent from my Chromebooks using XDA Labs
Click to expand...
Click to collapse
Being plugged to either PC or wall charged does not change the loop behavior.
tavuslokus said:
So my kid has a 3rd Gen Fire. I got it for him like 3 yrs. ago. At the time I loaded TWRP and CM11. Been fine ever since. Yesterday evening he claims while playing some Minecraft like game (Block craft 3D) the tablet screen went black and the boot loop started.
Now it's stuck there, it restarts itself every 35-37 secs (timed), and only reads "Kindle Fire" in white, then screen flashes and repeats. I can hold power to turn off, volume up/down combinations do nothing.
I used the factory cable, but device manager doesn't pop up anything. I told him high chances it's dead. Yet it'd be awesome to be able to go back and tell him I fixed it.
Does anyone have any further suggestions? or confirmation this is a end of service life type error? TIA
Click to expand...
Click to collapse
Device is likely gone; older 3rd gens are known for blown EMMC likely due to internal heating. Check auction sites for offerings; many good deals as folks fail to recognize the full potential of this device which remains competitive today. All 3rd (not 4th) gen HDX varients can be easily rooted and refreshed with the latest Android (Nougat based) ROMs - without using Safestrap.
That said, there is a somewhat involved procedure for dumping a HDX into 'bulk mode' to attempt a last ditch recovery. It is not for the faint of heart and won't help if the device has a hardware fault. I'd have to hunt down links and hand you off to another resource (@draxie) if you want to explore further.