I rooted this tablet and installed CWM recovery. I was getting horrible battery life after (it seemed as if the battery was being drained when it was connected to the keyboard folio, but I'm not sure) so I decided to do a factory reset. Now I'm getting 0% battery level and it doesn't increase when I leave it off and plugged in, but as soon as I unplug the device it complains that it is out of power and needs to shut down, and shuts down. Now I *think* it actually is charging because:
* I was using it fine for a few hours while I was trying to debug it
* However, as soon as you unplugged the cable it would complain it didn't have any power and would shutdown
* Now after debugging the entire time it seems to be really out of power, and I can only turn it on for about 2 min before it shuts off (no warning, just shuts off)
What I have tried:
* I have tried different cables, different usb ports, I've tried to plug in a different cell phone charger which goes straight into the outlet
* I booted into clockwork recovery and tried a wipe, clear cache, dalvik, battery stats and factory restore
* I tried logging in through adb shell but adb devices doesnt see the tablet at all. This is the same whether it's booted up, or if I'm in clockwork. This is whether I have debugging mode inabled or not. I had everything working fine when I rooted it so I think it's setup correctly, though windows did complain about 'MTP' device driver not installed
* when I view the log from clockwork I get:
"failed to open /sys/class/android_usb/android0/state: No such file or directory"
This seems to keep being displayed in the log file, because when I tried to do something else, like clear dalvik, and i look at the log file again the 'no such file or directory' messages are the most recent thing in the log and it keeps logging the same message over and over.
I'm not sure what else I can do. I think my next step is to try and reinstall the modified OTA2 files for this device, but the tablet has no power atm. I'll check again in the morning. The fact that I can't even see the device with adb concerns me though
If anyone has any ideas or has seen this before, please let me know.
Related
Ok this might seem strange, and just bare with me if I'm being thick...
I have had a nose around the forums and done a search but I couldn't find a solution to my problem.
I installed CM6 (by bumblebee) on my vega via CWM and instantly got BSOD - I didn't really think this was a problem because I knew the risk that it might happen and I had already done a backup etc.
However, all the parts for my new computer arrived the next day so I forget about my BSOD vega for a week as I started building my new computer and setting it up etc etc
I just got round to sorting my vega out when I realised I had completely wiped my old laptop with all the adb drivers on it etc (because I was going to sell it). Therefore, I cant get into recovery or flash anything to it because I cant use any adb commands :s (I cant reinstall the drivers - windows wont recognise the device as adb, only as a mobile device...).
Any suggestions? Am I being thick? Thank you for taking time to read through my rambling post anyway
You should be able to get into recovery and re-flash a stock rom. Make sure the device is plugged into the power and usb. Open device manager in win 7. Then hold down the back button for 2 secs then while still holding back hold power for 2 secs then release power but keep back button down for 2 more secs under universal serial bus controllers a new device should pop up. Point that at the usb drivers from the advent website. When the drivers have installed the screen on the vega will still be black but you should be able to flash the stock rom and start again.
Hope that helps
I will give that a try thanks for your help
Ok this is strange :S
EDIT: Drivers updated! But:
It only stays in APX mode for a couple of seconds before turning itself off - I know there is enough battery because I have booted it and left it for at least 10 minutes hanging in BSOD...
EDIT2: Ok, things have got worse:
- manged to flash stock image, booted in to 1.08
- flashed clockworkmod
- got into CWM and preceded to restore
- restore froze whilst restoring dalvik cache...
- left for an hour, no change
- decided best thing to do was to turn off device and boot again
- device boots, hangs
- used adb to reboot
- now wont even get to the 'booting...' screen, adb and pc wont detec device anymore
- tried to get to apx mode, works but my pc wont detect it so cant flash stock image again...
Sounds bricked anyone got any ideas? I know it was probably a stupid idea to switch it off whilst it was restoring but it was definitely frozen.
willk22 said:
Ok this is strange :S
EDIT: Drivers updated! But:
It only stays in APX mode for a couple of seconds before turning itself off - I know there is enough battery because I have booted it and left it for at least 10 minutes hanging in BSOD...
EDIT2: Ok, things have got worse:
- manged to flash stock image, booted in to 1.08
- flashed clockworkmod
- got into CWM and preceded to restore
- restore froze whilst restoring dalvik cache...
- left for an hour, no change
- decided best thing to do was to turn off device and boot again
- device boots, hangs
- used adb to reboot
- now wont even get to the 'booting...' screen, adb and pc wont detec device anymore
- tried to get to apx mode, works but my pc wont detect it so cant flash stock image again...
Sounds bricked anyone got any ideas? I know it was probably a stupid idea to switch it off whilst it was restoring but it was definitely frozen.
Click to expand...
Click to collapse
Keep trying to put it into recovery mode. At times it gets picky and you have to time it just right. Took me several attempts before it worked correctly again, so keep at it
Also, be sure to keep the USB plugged in while you are attempting to get it into recovery-mode and your sound turned up so you hear the infamous hardware-connected sound. Once you hear it, immediately plug in the power and start the recovery-flash. Do not wait too long or you'll have to start from scratch again
Keep at it, you're almost there.
Got there in the end thanks for your help!
[FYI: I don't a thing about tech stuff, but I can follow directions well enough if they're spelled out for me.]
I rooted my KF the day I got it using KF Utility. I don't remember what I did, and I certainly didn't understand much of it; I just followed the steps. That was several months ago (in December), and I haven't messed around with anything since. Everything worked fine, no problems. Haven't made any significant changes in months.
Then today, I tried to turn it on; the power light went on and the words "kindle fire" flashed for a second -- and then both disappeared. I connected it to a charger, and the same thing happened -- both, even the power light, disappeared after a second.
Same thing happens when I tried to connect it to my computer -- and my computer won't even recognize that it's there.
[It's now been connected to a wall charge for several hours, but the power light's not even glowing.]
What do I do? Is it "bricked"? And if so, how do I "unbrick" it, especially if my computer can't even recognize it?
Thank you in advance!
KF won't start, charge, or connect to PC
Absurd1 said:
[FYI: I don't a thing about tech stuff, but I can follow directions well enough if they're spelled out for me.]
I rooted my KF the day I got it using KF Utility. I don't remember what I did, and I certainly didn't understand much of it; I just followed the steps. That was several months ago (in December), and I haven't messed around with anything since. Everything worked fine, no problems. Haven't made any significant changes in months.
Then today, I tried to turn it on; the power light went on and the words "kindle fire" flashed for a second -- and then both disappeared. I connected it to a charger, and the same thing happened -- both, even the power light, disappeared after a second.
Same thing happens when I tried to connect it to my computer -- and my computer won't even recognize that it's there.
[It's now been connected to a wall charge for several hours, but the power light's not even glowing.]
What do I do? Is it "bricked"? And if so, how do I "unbrick" it, especially if my computer can't even recognize it?
Thank you in advance!
Click to expand...
Click to collapse
If you have the FIREFIREFIRE logo I hope this will help.
1. Make sure you still have the driver installed for you KF from KindleFireUtitly.
2. Open command prompt
3. change directory
cd C:\KindleADB
4. Check and see if adb services are running
adb devices
It will not come back with any device running and that is ok.
5. Look in the KINDLEFIREUTITLY folder for a bat file named Run.bat
double click and hit run and it will open a red command prompt.
After it has ran just a few short seconds it will give you a few number prompts. Chose number 5. and reboot Kindle and it will reinstall TWRP for you. These steps will also help if you ever get stuck in FIREFIREFIRE logo again.
I really hope this helps.
Thanks,
JohninLex
JohninLex said:
If you have the FIREFIREFIRE logo I hope this will help.
1. Make sure you still have the driver installed for you KF from KindleFireUtitly.
2. Open command prompt
3. change directory
cd C:\KindleADB
4. Check and see if adb services are running
adb devices
It will not come back with any device running and that is ok.
5. Look in the KINDLEFIREUTITLY folder for a bat file named Run.bat
double click and hit run and it will open a red command prompt.
After it has ran just a few short seconds it will give you a few number prompts. Chose number 5. and reboot Kindle and it will reinstall TWRP for you. These steps will also help if you ever get stuck in FIREFIREFIRE logo again.
I really hope this helps.
Thanks,
JohninLex
Click to expand...
Click to collapse
Well, like I said, I don't know much about any of this stuff, but here's what I can tell you:
I don't have FIREFIREFIRE. Not really sure what that is, but it's certainly never been on my Kindle.
What I did try doing was following those steps in Kindle Fire Utility anyway. I can get it to the point where it says:
ADB Status: Online
ADB Rooted: No
Boot Status Unknown
If from there I hit 5 (to "install latets TWRP recovery"), I get a whole bunch of
"The system cannot find the path specified." for each step it goes through, until finally it gets here:
"If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Normal Bootmode.
Please wait..."
To reiterate again -- I don't know what any of this ADB stuff is, where to find it, etc.
We are in the same boat. Was messing around w/ someone's Bare Bones CM7, and as per instructions, clicked wipe SYSTEM, and since then my device has been with screen "on" but black; non response to power button weather plugged on AC adapter or USB. Will have to research the forums tomorrow (cant find search function now) and let you know if I find a fix and please do the same if you find something first.
Sincerely,
-RM
---------- Post added at 08:49 AM ---------- Previous post was at 08:37 AM ----------
Actually --- I've just resolved the issue.
I had it plugged into the computer (still unresponsive), held down the power button for about 25 seconds, heard the computer do the "tuh-rup" sound, prayed, could finally stop seeing the "black screen" while on, it was pure black due to it powering off. After it was off, I powered back up and was able to get back into TWRP. Restored, did not wipe system and presto... hopefully you can get yours fixed.
theartofbone said:
Actually --- I've just resolved the issue.
I had it plugged into the computer (still unresponsive), held down the power button for about 25 seconds, heard the computer do the "tuh-rup" sound, prayed, could finally stop seeing the "black screen" while on, it was pure black due to it powering off. After it was off, I powered back up and was able to get back into TWRP. Restored, did not wipe system and presto... hopefully you can get yours fixed.
Click to expand...
Click to collapse
Nope, that's not doing anything for me. My kindle won't power on. All it does is display "Kindle Fire" for one second, then go dead.
Does anyone have ANY advice?
oundsde good
Try a different charger and plug into the wall for a little while.
_Justin said:
Try a different charger and plug into the wall for a little while.
Click to expand...
Click to collapse
Tried that. No luck.
Do you have a chat program, or google talk? I'll help you out.
_Justin said:
Do you have a chat program, or google talk? I'll help you out.
Click to expand...
Click to collapse
..........
My device has the same issue, it powers down as soon as I connect it to a PC or charger. The interesting thing, that it is charging, but the led is dark. When I take it off the charger the next day, it boots up and fully charged. (when I connect a cable again it shuts down immediately)
If you find out something I would be also interester. (I've also rooted before 6.2, than I've lost root, than after I while I've faced these issues)
Alright, unless any folks have any other advice, I'm gonna go ahead and contact Amazon for a return.
try to charge it with the wall charger for some hours - check the charger - should have ~1.8A - maybe the orange light is showing up after half an hour
try to power it off by holding pwr ~20sec to allow better charging - if you can't let it on the charger - try to power it off later (eg after an hour)
look here about charger spec and contact problems:
http://forum.xda-developers.com/showthread.php?p=23035482#post23035482
some had success with a factory cable:
http://forum.xda-developers.com/showthread.php?p=23034046#post23034046
Soo.. Droid Turbo 2 from Verizon.
Not rooted. No custom recovery. Not even a single attempt at anything like that. It's my girlfriend's phone.
Was working great over the weekend until Saturday night. We were playing some charades game on the phone and it froze. Powered it off with Vol Down + Power. Ever since then, it will not boot. I was able to put it into fastboot a few times to try restarting. Got it into recovery mode and tried a normal restart. Then went to recovery and attempted to wipe cache partition. Since doing wipe cache partition, it will not do anything. Will not even boot into Fastboot mode. Screen is blank. No charging indicator when plugged into a charger. Nothing. Attempts at using Verizon Software Repair Assistant has failed. Droid Explorer cannot find the device. However, I do get a random Unknown device when plugging it into my computer, however, nothing has been able to communicate with it and it doesn't register in SRA or Droid Explorer when plugged in. Attempts to manually force drivers onto the device via Device Manager have not been successful as there are no standalone drivers I was able to find to install to the device.
I'm out of ideas here. Normally I would just warranty the device through Verizon, since I know how to get them to do that. However, there is a slight issue with the volume up key. it doesn't click like normal even though it still responds to input normally. I don't want a damaged device fee. Any other suggestions?
Looks like broken motherboard.
My phone was working fine, and I decided to change ROMs, as I wanted to be able to use Split Screen, and the current custom ROM had a few issues. Anyway, I try flashing this new ROM, ExtendedUI: wiped the data, cache, and system and flash everything correctly, or at least I followed the instructions word for word. However, as I flashed magisk, there was an error, and I assumed that I would have to boot the phone first, as I have done in the past and it has always fixed the issue, come to find that when i reboot, it reboots into fastboot, and nothing else is on the system. Great. So i go back to MiFlash and flash davinci 11.0.2 and then go to reboot the phone and then nothing. Black. Phone doesn't vibrate when pressing both Vol up and power and/or Vol down and power. Left the phone to charge to see if it was just over drained battery wise and still nothing. Opened up the back and reconnected the battery to see if there had been some kind of hardware disconnect and, you guessed it, nothing. Any ideas on what I should do?
Well since you already bothered to open the phone I guess your can try the EDL/testpoint flash method.
I'd also double check or change the USB cable. For MiFlash to hard brick your device there must have been some transfer issues (or the source files were corrupted).
ShiningScias said:
Well since you already bothered to open the phone I guess your can try the EDL/testpoint flash method.
I'd also double check or change the USB cable. For MiFlash to hard brick your device there must have been some transfer issues (or the source files were corrupted).
Click to expand...
Click to collapse
After posting this message, I went to sleep, and woke up to the phone LED flashing. But nothing else had changed, even after trying all the key combos and connecting to the pc and whatnot. So I decided to try the EDL flash method, with multiple cables that have worked previously for data transfers, as well as different usb ports, and still nothing. I made sure to disconnect the battery. I'm not sure what else I can do.
All,
I have had my Nexus bootloader unlocked and even rooted it before.
However, I friend needed a phone so I let her use my phone...about a month later she said the battery was bad because the phone keeps cutting off.
Long story short I got the phone back and I think she picked up some type of virus or something got corrupted because I forgot to lock the bootloader when I gave her the phone.
Here's what I have found and done:
Found out:
1. The phone will turn on while plugged in after a couple of tries.
2.If the phone is not plugged in, it gets to the 4 dots and either re-boots or shuts off
3.If I turn it on while plugged in and then unplug it and set the display to turn off after 30 minutes...the phone will stay on, until the display shuts off then the phone shuts off.
Here's what I tried:
1. sideloaded Android 8.1 using TWRP (about 5 times)
2. Wipe cache and the other cached (several times)
3. Tried rooted it again...using SuperSu BUT during the re-boot it will stay on the "Google" screen for 30 minutes and not do anything...will not re-boot or nothing...phone get's really hot. (tried this several times)
4. Using TWRP recovery and if I leave the phone unplugged (while in recovery mode) the phone never cuts off.
So I am thinking one of these partitions is bad, corrupted or missing which is causing the phone to think the battery is low and cuts the phone off. Just guessing here. Maybe some malware is installed on a partitions and flashing is not during the trick.
Any suggestions???
I really wanted to keep this phone as a rooted phone I can play with and try different things.
Thanks,
Real
realkewl said:
All,
I have had my Nexus bootloader unlocked and even rooted it before.
However, I friend needed a phone so I let her use my phone...about a month later she said the battery was bad because the phone keeps cutting off.
Long story short I got the phone back and I think she picked up some type of virus or something got corrupted because I forgot to lock the bootloader when I gave her the phone.
Here's what I have found and done:
Found out:
1. The phone will turn on while plugged in after a couple of tries.
2.If the phone is not plugged in, it gets to the 4 dots and either re-boots or shuts off
3.If I turn it on while plugged in and then unplug it and set the display to turn off after 30 minutes...the phone will stay on, until the display shuts off then the phone shuts off.
Here's what I tried:
1. sideloaded Android 8.1 using TWRP (about 5 times)
2. Wipe cache and the other cached (several times)
3. Tried rooted it again...using SuperSu BUT during the re-boot it will stay on the "Google" screen for 30 minutes and not do anything...will not re-boot or nothing...phone get's really hot. (tried this several times)
4. Using TWRP recovery and if I leave the phone unplugged (while in recovery mode) the phone never cuts off.
So I am thinking one of these partitions is bad, corrupted or missing which is causing the phone to think the battery is low and cuts the phone off. Just guessing here. Maybe some malware is installed on a partitions and flashing is not during the trick.
Any suggestions???
I really wanted to keep this phone as a rooted phone I can play with and try different things.
Thanks,
Real
Click to expand...
Click to collapse
Not an expert but i suggest you do the following:
Backup the boot image, download the modified boot image for 4 cores. Try to boot, if it boots normally, your problem is BLOD and it will be solved. If that is not the case, use the 1 click flash bat from the modified fastboot folder that you can find doing some search, that bat will recreate partitions and reflash everything and also flash the rom you provide it then try to boot again. Shutdown the phone, give a charge until 90ish, let it cool and then boot it up.
xxJMarian said:
Not an expert but i suggest you do the following:
Backup the boot image, download the modified boot image for 4 cores. Try to boot, if it boots normally, your problem is BLOD and it will be solved. If that is not the case, use the 1 click flash bat from the modified fastboot folder that you can find doing some search, that bat will recreate partitions and reflash everything and also flash the rom you provide it then try to boot again. Shutdown the phone, give a charge until 90ish, let it cool and then boot it up.
Click to expand...
Click to collapse
Thank you for taking the time to reply...and thanks for your suggestions. I tried both and was very hopefuly...but did not work. The phone still will not boot unless the usb is connected and powered. However, not sure if I did the 4core correctly because I could not tell if it worked or not. I found a twrp 4core for bullhead and that is what I used. However, when you first flash it and it does an auto reboot it boots into TWRP not Android. So within TWRP I just click on reboot system...but same outcome.
I think maybe this phone's hardware is dead or something got burned out...but it is not the battery.
Thanks,
real
realkewl said:
Thank you for taking the time to reply...and thanks for your suggestions. I tried both and was very hopefuly...but did not work. The phone still will not boot unless the usb is connected and powered. However, not sure if I did the 4core correctly because I could not tell if it worked or not. I found a twrp 4core for bullhead and that is what I used. However, when you first flash it and it does an auto reboot it boots into TWRP not Android. So within TWRP I just click on reboot system...but same outcome.
I think maybe this phone's hardware is dead or something got burned out...but it is not the battery.
Thanks,
real
Click to expand...
Click to collapse
You did it wrong. You have to flash the boot.img that disables 2 of your cores. Search it here on the forum you'll find it