Hey all, this is my first post, so bear with me.
I have my tf700 for allmost a year now. I have unlocked it, rooted it, flashed different roms ( cleanrom, paranoidandroid). last month I decided to unroot it, so i could sell it to a friend
I succesfully unrooted it and it worked perfectly for a week. Then I experienced a low battery shutdown while playing a game, I let the tablet charge fully overnight. and the next day when i tried to turn it on, it just vibrated twice after ten seconds, nothing else.(NOTE: it's the first time it turned off after I unrooted it)
I tried everything, boot into recovery, reset hole.. nothing worked.
At last i tried to connect it to my TV through HDMI... and voila the tablet booted normally on my TV, but the tablet screen was pitchblack.
NOW my question to you, is my screen permanently dead (burned or something???) ? or is there still something i could try (like there is some software fault, because it is the first time the tf700 was rebooted after my Unroot-procedure).
Please help me save my little infinity :'(
I had a friend who had exactly the same problem. He left it for 3 days, came back charged it and it started working again.....
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
ricarpe said:
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
Click to expand...
Click to collapse
Same thing happened to me on Wednesday. Stock ROM, S-Off, perm root and a few minor modifications. Screen timed out as normal after a little bit of usage and about 40% battery life left, went to pick it up and turn it on and it was completely dead, for what ended up being about six hours or so. Called Verizon to have my old phone reactivated until I figure out what I'm going to do. Tried everything from pressing combo of buttons, charging, adb commands, no luck. HTC one came back on after I plugged it into the wall and held power. So I called Verizon to reactivate it. Verizon offered me a brand new device since I am still within my 2 week period for a return. I have until this Saturday to return the device, but everything has been fine these past couple days. Still not sure what I'm going to do. It's almost as if the device was completely stuck or frozen until the battery died, then when I plugged it in again it powered on and showed 1% charge. It might also have something to do with Verizons new XLTE. Either way, scared the crap out of me and I was pretty frustrated for awhile. Never experienced this before and I've been rooting and ROMing devices for about 4 or 5 years.
Thought I would add, that I was sitting next to my fiance and within the 5 minutes that this happened to my device, her old samsung stellar, which is rooted and rom'd, started vibrating and was stuck vibrating for about 15 seconds before she picked it up and turned the screen on. Very strange.
Happened to me as well. It was just one time a couple weeks ago. It did this in the middle of the night, while it was on the charger for sleep. I woke up and wanted to check the time and could not wake the phone with any gestures or button press combinations. I ended up having to hold down or up (don't remember which) plus the power button and the phone eventually turned on. Sucked because I doubt my alarm would have went off.
I haven't had this with my M8, but I've had it happen in the past with my Dell Streak 7 tablet. It was a software problem. Basically like an app not responding but on a system level. Only way to fix most times was to reset.
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Kuuroki said:
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Click to expand...
Click to collapse
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
I did grant permission at first without thinking about it, until I immediately thought why the hell is Verizon asking for root, so i went into the superuser app and permanently denied permission. It was days before this happened to me.
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
hgoldner said:
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
Click to expand...
Click to collapse
Interesting..I run paranoid android on my One, and as such, have gotten rid of the Verizon bloatware.
That's slightly worrying. Verizon scares me sometimes.
In my mind, this validates my decision to go over to the CM11 nightlies and never look back.
Happened to me a couple times I just hold both volume keys then power till it restarts to simulate a battery pull cuz I always assumed it just got stuck in sleep
Sent from my HTC6525LVW using XDA Premium 4 mobile app
I've had this happen a couple times with my M8. The first time it made me late for work because my alarm clock didn't go off. Just last week I woke up and unplugged it from the charger. When I looked at the phone I noticed that the green charging light was still on solid even though the phone wasn't plugged in anymore. I held the volume keys and the power button and eventually got it to start back up. It's concerning, but I don't want to return my phone because I have an expensive Spigen glass screen protector on it. I guess I'll just hope it's a software issue and HTC will eventually get it sorted out. I'm currently running CleanROM and the CodeCraft_Final kernel.
I was quickly able to avoid the Verizon root perms. First of all I always recommend disabling play store auto update. I very rarely update apps unless the update fixes a direct issue I am having. Once I heard about the root perms, I disabled the app in settings and carried on the s off process (eventually). I then searched carefully for a ROM w/o my Verizon included and flashed cleanrom and that's where I'm at now. All these threads are making me scared to reboot my device lol. Only hope I have in finding some info about this is a rogue Verizon employee
Sent from my HTC6525LVW using Tapatalk
It isn't necessary to hold both volume keys, just volume up and power.
Some kind of an issue with Verizon bloat acting up?
I disabled most of Verizon preinstalled bloat and I've never seen this issue.
andybones said:
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
Click to expand...
Click to collapse
I am a little disappointed.. you didn't take your phone with you into the bathroom? Lol. this happened to me after I tried an aosp Rom for the first time then went back to my stock rooted with soff and thinking about it now I accidentally allowed root permission to Verizon application which I quickly disabled in su. I didn't think much of it considering I thought it was something I had done or maybe battery died but it only lasted about 5 minutes rebooted and I was good. I remember on a previous HTC phone if you had a bad Rom and radio/kernel combo the phone would act vertually dead even if the battery was fully charged.
This just happened to my M8. I rebooted it and it didn't reboot. When plugged in, the LED didn't come on. Rooted, S-OFF, running pretty close to stock ROM with an unvervolted, overclocked kernel. I've let the phone sit for about 24 hours now. Have ordered a warranty replacement, but may try once or twice more to see if it springs back to life. Very strange. Can't get into hboot or any other key combination. For all intents and purposes it is a brick. (If it can't register a charge, it won't take adb).
Even if it does come back from the dead, I'm not taking a chance and swapping it out.
UPDATE: Truly bizarre. Returned to life and rebooted in response to power-volume up about 26 hours later. Battery had dropped from 80% to 40%. Rebooted like nothing had ever happened. Editing this on it now.
This happened to my first m8, what I believe is happening is they are going into the bootloader, but the backlight is off. I didn't notice until I held it under a bright light and saw there was something in the screen. Afterwards I was able to navigate to reboot the device. Or you can try simulating a battery pull. Just something to try before you write your baby off as dead.
Sent from my HTC6525LVW using XDA Free mobile app
Sounds like SOD.
My tablet is unrooted, untouched, unmolested, etc. Running 5.0.1 from the ota update.
My tablet's battery died while I was using it a few hours ago. I put it on the charger and wait a bit before turning it on. It boots up normally but I'm immediately greeted with the "power off" message box as soon as android loads. I've done fastboot and did the recovery boot (whatever that means in this case) and nothing I have tried has helped.
I'm afraid of tampering with it to install custom roms, because if that doesn't work the warranty would be void.
Anyone experience this problem before?
Sounds unusual but my only recommendation is to leave it on the charger overnight to get it fully powered up.
If not, you might have to boot into the stock recovery and perform a factory reset. At that point if it still doesn't work, if your tablet is completely unrooted with a locked bootloader, just send it to Nvidia.
Yeah it sounds like it's gonna get rma'd. It was charging the whole time, in the 4 or so seconds it was on the lockscreen before turning off it would show the battery percentage at something like 60%+, so it was definitely charging.
After enough tries it just wouldn't even give me the nvidia start up splash screen. I managed to do a factory reset (which seemed to take a really long time). The factory reset let it get back to the lockscreen but it immediately turned off again.
Other things for people who might have this problem as well:
It started after I put in a 32gb micro SD card I bought for it. I think the SD card is fine because it works in my phone.
Also this tablet was only about 4 days old when it broke.
The tablet is completely stock. I'm lucky it broke so soon as I was about to root it.
http://forum.xda-developers.com/shield-tablet/help/tablet-shutdown-boot-t3035492
Posted this on reddit but figured might be helpful on here.
Did some testing with the phone with very little apps for the last day. Decided to go to the play store and go to my apps and started DL'ing my apps I mostly use basically everything that's on my G4. Phone froze rebooted OK whatever, rebooted again, again, ok stuck in reboot loop. Called Alcatel was able to do a master reset took maybe 10 mins for it to load back up in Android everything is froze and just reboot loops again.
I can't even power if off well I can but it power's back own and does the loop. Waiting for the battery to die. Now here's a reason why removable battery is great.
Seriously WTF happened.
After talking with Alcatel and Amazon they are sending a replacement with 1 day shipping be here tomorrow. Wonder if I should even bother with it. Was going to mostly use it for my 2nd line for a Hotspot for the Data and just a backup to my G4 and or rotate them.
https://vid.me/grFZ
Now I do recall after it first froze and rebooted it said Android is updating or whatever that screen is. I recall the phone having 2 updates it updated though the day before. Should have the replacement on here later this evening.
I had CPU temp app running so I could see what app were heating up the phone when I used and when I had Google Maps on it the car it did heat up to the low 70's C once in awhile and was sticking mostly around 67-69C did the phone get too hot. Not even sure what the overheating temps are for this.
Probably just a defective phone but was fine running basically not added apps just installed NoChromo, Battery Monitor Widget, CPU Temp, Netflix, Rhapsody, Signal Check Lite, Speed Test, Spotify, I believe that's what I had installed before the issue. Then I just went and download everything else I usually use at once.
BDestroyer8418 said:
Posted this on reddit but figured might be helpful on here.
Did some testing with the phone with very little apps for the last day. Decided to go to the play store and go to my apps and started DL'ing my apps I mostly use basically everything that's on my G4. Phone froze rebooted OK whatever, rebooted again, again, ok stuck in reboot loop. Called Alcatel was able to do a master reset took maybe 10 mins for it to load back up in Android everything is froze and just reboot loops again.
I can't even power if off well I can but it power's back own and does the loop. Waiting for the battery to die. Now here's a reason why removable battery is great.
Seriously WTF happened.
After talking with Alcatel and Amazon they are sending a replacement with 1 day shipping be here tomorrow. Wonder if I should even bother with it. Was going to mostly use it for my 2nd line for a Hotspot for the Data and just a backup to my G4 and or rotate them.
https://vid.me/grFZ
Now I do recall after it first froze and rebooted it said Android is updating or whatever that screen is. I recall the phone having 2 updates it updated though the day before. Should have the replacement on here later this evening.
I had CPU temp app running so I could see what app were heating up the phone when I used and when I had Google Maps on it the car it did heat up to the low 70's C once in awhile and was sticking mostly around 67-69C did the phone get too hot. Not even sure what the overheating temps are for this.
Probably just a defective phone but was fine running basically not added apps just installed NoChromo, Battery Monitor Widget, CPU Temp, Netflix, Rhapsody, Signal Check Lite, Speed Test, Spotify, I believe that's what I had installed before the issue. Then I just went and download everything else I usually use at once.
Click to expand...
Click to collapse
Gotta love boot loops! Sorry to hear your troubles.
kevin6876 said:
Gotta love boot loops! Sorry to hear your troubles.
Click to expand...
Click to collapse
LOL could use a bowl of those.
BDestroyer8418 said:
Posted this on reddit but figured might be helpful on here.
Did some testing with the phone with very little apps for the last day. Decided to go to the play store and go to my apps and started DL'ing my apps I mostly use basically everything that's on my G4. Phone froze rebooted OK whatever, rebooted again, again, ok stuck in reboot loop. Called Alcatel was able to do a master reset took maybe 10 mins for it to load back up in Android everything is froze and just reboot loops again.
I can't even power if off well I can but it power's back own and does the loop. Waiting for the battery to die. Now here's a reason why removable battery is great.
Seriously WTF happened.
After talking with Alcatel and Amazon they are sending a replacement with 1 day shipping be here tomorrow. Wonder if I should even bother with it. Was going to mostly use it for my 2nd line for a Hotspot for the Data and just a backup to my G4 and or rotate them.
https://vid.me/grFZ
Now I do recall after it first froze and rebooted it said Android is updating or whatever that screen is. I recall the phone having 2 updates it updated though the day before. Should have the replacement on here later this evening.
I had CPU temp app running so I could see what app were heating up the phone when I used and when I had Google Maps on it the car it did heat up to the low 70's C once in awhile and was sticking mostly around 67-69C did the phone get too hot. Not even sure what the overheating temps are for this.
Probably just a defective phone but was fine running basically not added apps just installed NoChromo, Battery Monitor Widget, CPU Temp, Netflix, Rhapsody, Signal Check Lite, Speed Test, Spotify, I believe that's what I had installed before the issue. Then I just went and download everything else I usually use at once.
Click to expand...
Click to collapse
More than likely either the 1st or the 2nd update applied to your phone put it in a bootloop but you would have had to click on them to allow them to install. Going into recovery via rebooting till you first see the alcatel screen and then holding down vol up would have allowed you to do a factory reset which in all previous cases of boot loop being mentioned corrected the issue.
If it wasn't the updates then one of the apps downloaded did not work well with the phone but a factory reset should still have fixed that, unless you were installing apps that use superuser in which case you should first have at least booted twrp and backed up system if not all the partitions so you could do a restore. Remember these suggestions for your 2nd phone.
Ideally we need someone to back up system both before the 1st update and the 2nd so we could "downgrade" if necessary. Some have complained the 2nd update caused a bug that makes making google voice calls unavailable.
warranty repair..the easiest anf fastest way at this situation.
famewolf said:
More than likely either the 1st or the 2nd update applied to your phone put it in a bootloop but you would have had to click on them to allow them to install. Going into recovery via rebooting till you first see the alcatel screen and then holding down vol up would have allowed you to do a factory reset which in all previous cases of boot loop being mentioned corrected the issue.
If it wasn't the updates then one of the apps downloaded did not work well with the phone but a factory reset should still have fixed that, unless you were installing apps that use superuser in which case you should first have at least booted twrp and backed up system if not all the partitions so you could do a restore. Remember these suggestions for your 2nd phone.
Ideally we need someone to back up system both before the 1st update and the 2nd so we could "downgrade" if necessary. Some have complained the 2nd update caused a bug that makes making google voice calls unavailable.
Click to expand...
Click to collapse
I installed both updates before doing anything with the phone. The phone was fine for 24 hours or so. I did the power button and volume reset with Alcatel and it was able to reset it just fine but still was stuck in the reboot loop. Not sure why one of those apps would have cause it to do that but maybe it was defective and one of those apps just finally pushed it ? I was not trying to Root the phone at all, atleast not right now I'm not. Don't you need to flash TWRP for root if so I don't have access to that and not doing that at this time.
I did get the replacement one yesterday as promised. Turned it on downloaded and installed the update. AFAIK it only downloaded and installed 1 update for me this time. Not sure if this is the current build 7SQR-UER0 but that's what I have after the update and it showing it's up to date. The build before it I checked was 7SQ3-UE30 that's what came on the 2nd phone I don't recall what was on the 1st phone.
I just set it up and went to play store and downloaded everything didn't have any issue's so well test some more the next few days. Could of just been bad phone.
BDestroyer8418 said:
I installed both updates before doing anything with the phone. The phone was fine for 24 hours or so. I did the power button and volume reset with Alcatel and it was able to reset it just fine but still was stuck in the reboot loop. Not sure why one of those apps would have cause it to do that but maybe it was defective and one of those apps just finally pushed it ? I was not trying to Root the phone at all, atleast not right now I'm not. Don't you need to flash TWRP for root if so I don't have access to that and not doing that at this time.
I did get the replacement one yesterday as promised. Turned it on downloaded and installed the update. AFAIK it only downloaded and installed 1 update for me this time. Not sure if this is the current build 7SQR-UER0 but that's what I have after the update and it showing it's up to date. The build before it I checked was 7SQ3-UE30 that's what came on the 2nd phone I don't recall what was on the 1st phone.
I just set it up and went to play store and downloaded everything didn't have any issue's so well test some more the next few days. Could of just been bad phone.
Click to expand...
Click to collapse
If you have not yet rooted and have any model other than 6045i (settings, about phone) you could really help the idol3 users out....details here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
famewolf said:
If you have not yet rooted and have any model other than 6045i (settings, about phone) you could really help the idol3 users out....details here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Click to expand...
Click to collapse
I believe that is the model I have what ever the USA bought on Amazon.com are.
I have rooted successfully with king root. Tried to change it to Supersu but failed su binary i think because Im on 5.1. Also is it actually boot looping or does it just not load. Because mine will boot up say Alcatel One Touch then be stuck on boost mobile boot screen for a while. I unplug battery and try again and just leave it. It takes a long while but it comes back
i7vSa7vi7y said:
I have rooted successfully with king root. Tried to change it to Supersu but failed su binary i think because Im on 5.1. Also is it actually boot looping or does it just not load. Because mine will boot up say Alcatel One Touch then be stuck on boost mobile boot screen for a while. I unplug battery and try again and just leave it. It takes a long while but it comes back
Click to expand...
Click to collapse
why you root it with king root, when there is a procedure to root the device with custom recovery?the device couldnt be running android 5.1 becaouse we all have only 5.0.2. How you manage to unplug the non removable battery?
My Nexus 5x was bought by May 15 2018, i was excited for this phone, but i never knew about all the issues it is inclined to have.
EP 1:
It started with this simple notification that started to appear randomly without any solid cause.
"USB supplying power to attached device"
I tried a couple of fixes, like cleaning the usb port, Factory and Cache wipe, and nothing worked, it was just becoming a real annoyance.
EP 2:
The next day, after i did the factory reset and realized there was nothing different about the issue, i put it to charge, moments later i tried to turn it on but i realized it wouldn't go past the google screen, google screen was just rebooting constantly, it was at this moment i got acquainted with our fellow bootloop.
I started investigating, talked to a couple of people and they recommended flashing.
At that moment i could access bootloader, and recovery...
Ok, i turn it off.
After a while, when im ready to flash, cant access recovery.
Bootloader is accesible, but oem is locked and wont allow.
Later i finally found what could be the way of solving the issue.
And i could sleep peacefully that night.
EP 3:
Now, on top of all the complications, the fatality:
Next morning.
It wont even turn on into bootloader.
But i do see that it is charging, however; it wont turn on.
Is there some way of booting it connected through the pc ?
I think i wont be letting this problem like this anytime soon, im still up and willing to find a way to solve this.
If it's still early, just return it for a refund the Snapdragon 808 and 810 are infamous for problems 9 times out of 10 for not being soldered to the motherboard properly so I would advise to return for refund or replacement