Okay so here's the story.
I was running pacman 4.3 nightly roms on my tablet.
At some points id have this weird issue where out of nowhere I would start bootlooping (and bc of some weird issue i couldnt boot into recovery from the bootloader unless i was plugged in to a pc. idk it was weird. the bootloader was like 3.13 or whatever)
anyway, yesterday my battery drained completetly and I would do what I would normally do, plug in to my pc, boot into the bootloader, boot into recovery and let it charge a little bit, then i would reboot into the system. but this time it would die during the splashscreen, so that was weird. Anyway, I eventually got it past the splashcreen onto my homescreen and my battery was apparently at 0 percent and then it would just die even tho I was plugged in.
i could leave my tablet in recovery for a while without being plugged in which was weird.
Anyway I tried flashing a newbootloader. 4.23 or something and it successfully flashed, now it wont boot up. fancy paperweight in my hands lol
lsusb command on my linuxbox gives me nothing. RIP nexus7, its been real.
oh and i did everything through adb
and before it died, whenever i plugged it in to usb or my power adapter, some strange sounds came from inside the tablet, like static lol
update, i had it plugged in and not even the charging screen was coming up so i was just there holding the power and volume buttons then the charging screen came up and went away. hmmmmm
The usb cable works fine for file transfers/being detected on my linuxbox on my s3 and evo so its not the port or cable
another update.
charging screen now comes up and stays on for a while. guess its an issue with a port on the tablet, but whenever i power it on or try to get to the bootloader the screen goes black for a second then back to the charging screen. so Im guessing this tablet is done for and shouldnt bother trying to fix the port?
deleted.
Is it still under warranty (less than a year old from when you purchased it)? If so, RMA the sucker. That's what I did and they replaced the motherboard for me.
Related
Hi everyone,
I have had some trouble with my Vogue. At first it simply would not turn on. I would get a red light when I plugged the phone in to charge it. I have been using my old phone for several months now. Today I went out to the nearest Bell store and it seems like anything new is going to cost in the $500 area because I still have 1 year left on my contract. So I have renewed my interest in getting my Vogue working again
The original thread describing my original problem (with the red light) is here:
http://forum.xda-developers.com/showthread.php?t=546674
I purchased a new battery and now when I plug it in on the USB I can turn it on (no lights, red, green, or otherwise) but it does turn on. It boots up just passed the blue “Bell” splash screen and then reboots. It does this over and over again.
I am able to get into the boot loader screen by holding down the power and camera buttons and pressing the reset button.
Any ideas on what I can do? Any suggestions are welcome.
Regards,
The Fish
Reflash your rom when you get to the bootloader screen.
If you are unlocked flash nfsfan or whatever, just rename the nbh file to 'VOGUIMG.nbh' and it will flash.
If you were on stock you'll need the nbh from the stock package.
OK, here is an update
I have tried a hard-reset (press Send and End buttons at the same time and press reset button). This worked but the phone still kept rebooting. Tried the original battery, phone booted a little further up before rebooting.
I got the phone into boot loader mode and left it plugged in on the USB cable for a few minutes. This time when I rebooted I became ecstatic. I got all the way to the “align your screen” stage before hearing the “phone is dying” sound and the phone turned off. So here is what I think may have happened:
I have long lost the home charger kit. So I have, for as long as I can remember, been charging it by plugging it into a PC via the USB. This is fine except that Windows will only power the USB for the device if there is a driver installed. The device/phone looks different to Windows when it is in boot loader mode then when it is fully booted up. If the device is so dead as to not even have a flicker of life I don't think Windows sees it.
I have been doing this tonight under Linux. Linux seems to either have the driver, a more generic driver or powers the USB all the time for any device. I noticed this same behavior when charging my Moto Razr the same way. Under Linux it just worked by plugging it in. Under Widows I had to install the driver. So maybe here is what happened.
The battery got SO dead that it was not able to boot the phone up far enough for Windows on the PC to see it, recognize it and begin powering the USB port. Perhaps leaving the phone in bootloader mode and plugged into a Linux box got the battery a little more charged till I got to the point of being able to align the screen.
Anyway, I am more then ever convinced that this is some kind of battery/power issue. The phone is now lying here powered up and charging (already at 20%). The carrier customizations ran, rebooted while I crossed my fingers, and came back up. I even called *BELL and got a message about activating my phone. Tomorrow if the phone is charged up and behaving normally I will get an ESN change done and be back in the world of decent smartphones. Man have I ever missed my Google Maps
The next step is to flash a more up-to-date ROM... if I dare mess with a good thing.
The Fish
Ok my buddy has an atrix 4g for ATT. he 'said' he was in cwm and loading a rom and now its softbricked. though i am familiar with droid, after reading recovery threads and everything, im still unsure of my resolution. most threads tell me i need an unlocked bootloader, others say not to flash if you were on this version. Honestly i have no idea if the BL is locked, what version or update he was on. at the moment it says failed to boot, starting RSD mode, battery is too low to flash.
A. will it charge while it says that or how should i charge it in this state?
B. after it does charge, what should i flash to it?
I apologize that i dont have much information. you have no idea how long it took me to find the power button lol. I appreciate any and all suggestions. Thanks
You definitely need to get more information from him before you can do anything. If his bootloader wasn't unlocked, then he was likely trying to flash one of the P-Roms like Greyblur or Gingerblur, in which case your solution will be a lot messier since the only way I remember accessing recovery back then was by using Tenfar's CWM app that reset it to recovery w/ a wall charger.
As for charging the phone, I don't recommend keeping it on and plugged in, in the chance that it doesn't charge and you are left with a dead battery. When the phone is completely off and you plug the charger in, do you see the charging battery?
When the phone is plugged into the wall charger it boots up automatically and says failed to boot 1, starting rsd, battery too low to flash. If I plug it into my pc the green power light turns on but nothing else happens. I never get any pictures on screen. No battery and no motorola logo. He was on 2.3.4 but he took his sd so I couldn't see what he was trying to flash. I will try to get more info
Sent from my DROID3 using XDA App
Same thing happened to me, and I can assure you it doesn't charge in that state. I have to find a way to charge the battery now... It is 0% dead. I hope I can use RSD Lite to fix it when it is charged.
alright, what happened was his battery was too low to finish the flash. it died halfway through, and now the phone is in some sort of limbo state that is just completely unusable.
but, if you have a spare USB cable you can fix this.
http://www.youtube.com/watch?v=EQ6JNCvIe8k
just watch that video, and let your phone charge for about half an hour to 45 minutes. after that, reflash the pudding .sbf with rsdlite (unless you can boot into recovery, then you can just reflash any ROM)
If you can boot the phone into recovery by holding the volume down key when powering on, then simply find the alien rom, save onto your SD card from the PC, then install in recovery...then you should be able to reboot into a working phone and charge. If you can't boot into recovery, and the phone is stuck on the "starting rsd protocol" screen, than...I think its a paper weight, but I could be wrong.
Although this problem could probably be fixed by an earlier post, I'm curious....
what would happen if you plugged it into the wall charger, let it boot up into the boot loop, then pulled the battery, left it out for 30 seconds, then put it back in. (this is without unplugging it from the wall charger). Does it allow the phone to stay off and charge, or does it still automatically boot up? Just curious.
im gonna look at the youtube video. ive got a D3 and i saw where a kid had cut a usb cable and made something work for 30 minutes and was able to flash again, but i was def trying to avoid that lol. also, there is no loop really. it doesnt restart, it just sits there. when the battery is pulled, it still stays on the same screen and never powers off until the charger is removed. i may see if i can get a new battery. i really apprecaite the feedback
Phalanx7621 said:
Although this problem could probably be fixed by an earlier post, I'm curious....
what would happen if you plugged it into the wall charger, let it boot up into the boot loop, then pulled the battery, left it out for 30 seconds, then put it back in. (this is without unplugging it from the wall charger). Does it allow the phone to stay off and charge, or does it still automatically boot up? Just curious.
Click to expand...
Click to collapse
It will not charge in this state
well my only option at this moment is to try the usb trick. im trying to strip the wire and hook it to the connector on the phone and then just smash teh battery on top of it, but i have no idicator light, so i dont know if its charging. would it charge if i tape/rig/solder it to the battery itself and not have it in the phone? i really dont wanna try a wall outlet charger
I am going to splice a cable and report back with results. My only other option is to charge the battery in my friend's Droid X
If that fails, to AT&T I go.
i havent been able to get it to charge through the usb using the red and black wires. i was very careful and have a decent set of tools to work with. he can buy the external battery charger for $30 if he'd like. im not really sure what else to do at this point.
Bought a 16 GB Wifi Samsyng Galaxy 10.1 Tablet from a friend. Not rooted. Was working fine until I upgraded to the stock 3.2 from Samsung. Now, it won't boot unless it's pugged into the wall charger. The battery says its at 100%, but it goes immediately off when I unplug it. It won't boot at all....not even into recovery unless it's plugged in. The computer wont recognize it when using the USB cord and it won't do anything.
Can the software do weird things to the battery? What do I do? I can use the wall charger, boot into recovery, wipe data and factory reset....then setup my google account and it works fine....until I unplug it. Then it goes black immediately.
I'm not a noob, (several Android phones, all rooted and custom Roms flashed...thx XDA).......but I'm stumped on this one.
Pease help.
Try going back to 3.1 and see if it goes away, or try a Custom Rom. Task14 is very stable and reliable to test with
as long as you can turn it on, you are safe. Like above said, install Task14 rom!!
badboy47 said:
as long as you can turn it on, you are safe. Like above said, install Task14 rom!!
Click to expand...
Click to collapse
Thanks for the suggestions....but since I can't get the tablet to do anything while it's connected to the computer, how do I get the tablet rooted or even get the 3.1 or a custom Rom onto the tablet?
I plugged it in again last night (with wall charger)....it showed the battery as 100%....then it vibrated and the screen faded (as it's supposed to do). It won't turn on when you press the power button only.....not even if I hold it down to force a reboot. So I have to boot it up by using the power button and the down volume key combo. From there, I wiped the cache, and did a factory reset. (all this time it's plugged into the wall charger) Then when it rebooted and I was able to set it up with the Wifi, Google account, market access, etc. I even played a game and went to You Tube and watched a couple videos just to make sure it was working. Everything was working perfect (as long as it's plugged in to the wall charger). I left it alone for several hours to see if the battery was just reporting 100% but in fact was NOT at 100%. The screen went black, but would come back on when pushing the power button quickly (as it's supposed to do) So I left it like that overnight. This entire time the battery was reporting 100%.
This morning, I quickly tapped the power button and it came back up (still plugged in). Working great. As soon as I unplug it from the wall, it went black and now it won't do anything.
It won't boot or do anything using the USB cord and the computer. How do I get the new ROM or old stock 3.1 onto the dang thing if I can't get it connected?
This thing is frustrating me.
Had my N7 for well over a year, rooted, unlocked bootloader, all of a sudden it wont turn on... If I plug it in I get a blue screen, unplugged nothing..
Any Idea's out there?
mojimmy said:
Had my N7 for well over a year, rooted, unlocked bootloader, all of a sudden it wont turn on... If I plug it in I get a blue screen, unplugged nothing..
Any Idea's out there?
Click to expand...
Click to collapse
Try opening the back panel of your nexus and unplug and replug the battery.
Leonhan said:
Try opening the back panel of your nexus and unplug and replug the battery.
Click to expand...
Click to collapse
That did it...I usually just thump it on the side and it works...N7 flaw, thanks for your help..
I was reimaging my device from 4.4 back to 4.3 (since Kit Kit broke flash videos). Stupid me, I told it NOT to wipe my user data (even though I backed everything up, including the internal storage device). When it rebooted, the X logo was there, but it never would boot up. I'm assuming because it was because I should have wiped data. Oh, and it was fully charged before I did the reimage to 4.3.
Well, I tried to reboot it (did the reset) to try and get into the bootloader which I did. I wipe the cache only and then rebooted and that was it. Blank screen and nothing else. I can't tell if it's turned on or off. Plugging the charger into the wall outlet doesn't elicit any type of response on the screen. Usually, the screen turns on if it's already on or else, if it's off, you get the battery icon. Neither one happens.
The screen is blank (even when I press and hold power+vol up+vol down. I've hooked it up to the PC to see if I could hear at least the sound when it powers down on the reset and it does indeed do that. Then, it connects and then I get a different sound and the PC says it cannot identify the USB device connected when before all of this happened, it was working just fine (had to since I JUST used the N7 tools to flash back to 4.3).
I've also left it hooked up to the original wall charger for over an hour and nothing. Screen is still blank and never comes on no matter what I do.
I've also opened the back up (hopefully they can't tell if I've done this or not) and unplugged the batter, waited and plugged it back in. Still nothing.
I've uninstalled all the drivers, rebooted and tried it again. After it installed the drivers, still the same issue. It worked for almost a year. Luckily, I purchased the N7 on January of 2013, so I'm still under warranty.
Here's the problem: I unlocked the bootloader. Will this void the warranty? Am I hosed if I try to RMA it? I cannot get connected back to to an fastboot oem lock on it. N7 toolkit is useless (well, NOW it is since I have a non-functioning device), so I cannot do anything there.
I'm just trying to see if there is anything else I can do or is the N7 fubar'd? If so, does this mean they won't be able to keep my data (which is fine by me)? I would hate for them to boot it up and see the unlocked icon on the screen and then come back at me for money.
OPT took a blow to its back, now wont turn on w/o USB & Boot Loops when USB plugged
FML ... ok so my OnePlus Two (A2001) slipped out of my hand while I was using it and the area right under the camera took a hit (not too hard) to the side of a nearby table (Battery was at around 50% last time I checked). Now the bloody thing wont respond, UNLESS i have it plugged in.
While it is plugged in, It either boot loops, with the boot screen being off center (the Word Android is on the bottom left of the screen and the OnePlus logo is on the Center-Left of the Screen, OR it boot loops with the screen perfectly justified when +V and Power is pressed. I had the newest official oxygen 2.2.1 installed on it. At this point I can only get it into fastboot mode using +V and Power. When plugged in and left on it's own, it boot loops with occasional "Low Battery" (with charging light on) but then it reboots again (disabling charging light an charging)
I've had the original OnePlus usb drivers installed on my PC before but plugging it in does nothing. Ive tried the Qualicomm Driver + MSM8994 method (http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449) with no avail. Installing the Drivers manually the OnePlus Two still shows up as "Unknown USB Device (Device Descriptor Request Failed)"
I've also taken it apart to see if there's anything loose/broken. I dont see anything wrong with it. Ive also pryed the battery from the back and detached the battery connector from the motherboard. Then plugged it back in, but it still does everything described above.
Fastboot commands to not work as it just looks for device. Fastboot Continue does not work.
Im running out of ideas..... =( Anyone have any new ones?
Seems like the OnePlus Two doesn't respond well to impact. Mine slid off my desk a few times onto a wood floor and now won't respond at all.