[Q] Nexus 10 bricked after restoring apps with Nexus Root Toolkit..? - Nexus 10 Q&A, Help & Troubleshooting

I was unlocking the bootloader and rooting my N10 with the Nexus Root Toolkit, everything went fine. Then a was gonna restore my apps using the toolkit. Something went wrong and the tablet just turned black, now I cant turn i on or even get into recovery mode. Is it hardbricked? When I plug the power and hold the power button it only shows a battery icon. Is there something I can do?

I solved the problem, the tablet wasnt bricked. When I was trying to power on the tablet it just showed a battery icon and the screen became brighter after 1 second and then just black. I did this a couple of times right after each other and they tablet turned on. So if someone have this problem try that.

Thank you.
From my S-Off BadSeed DNA

Leave it plugged in on the charger for a while until it has enough battery to boot again.

Related

[Q] Phone won't boot - Sapo a5 ZTE Blade

Hello, new user here, I have a technical problem and I could use some advice. If I posted on the wrong thread or if this is already solved, please forgive me.
Anyways, It was like 02:00, my phone was at around 38% battery at the time, I figured this would be enhough for me to make a backup of my CM9 ROM and then restore CM7. I set Clockworkmod to backup CM9, and that was successful. Then I restored CM7 from a backup of it I made earlier. I think it was successful but I fell asleep before I could notice. (Staring at clockworkmod restoring data puts you to sleep) It most likely ran out of batteries after completing the restore in Clockworkmod.
When I woke up today, I found my phone shut down and with no battery. I proceeded to plug it in to my PC. No charging... I saw that was wierd, and then when I tried again I figured out my phone was essentially dead.
Here's the problem, when I press the power button, it vibrates successively, and shows no signs of booting. I began reading forums, including Modaco (I had to use google cache because it just happened to be offline at the worst possible time), and they say that it's because the battery is dead. So I put it in my wall charger. After an hour or so, same problem. No boot, always vibrating in succession, and also even though I press volume up and down I get no signs of clockworkmod.
When I plug it into my USB, strangely my mouse disconnects from my PC. I use a laptop, and this never happened before today, and it is possibly related to my problem. In short, Blade plugs into USB, Mouse dead.
I don't know if my phone is refusing to charge or if it's bricked, I can't tell, and I really fear it may be bricked, because I can't afford a replacement. (No job, still living with my mom, I'm 19) I also have no clue if my computer can even recognize it, nothing shows up except for this wierd mouse problem.
So, can anyone help me?
Connect charger with blade,then boot into recovery....
Is it booting into recovery?
Nope
Nope, I wish. : ( When I connect it to the charger and try to turn it on, it only vibrates, nothing else, no recovery, no Android logo.
Vryonorg said:
Nope, I wish. : ( When I connect it to the charger and try to turn it on, it only vibrates, nothing else, no recovery, no Android logo.
Click to expand...
Click to collapse
Do a tpt or use the adb method.. I experienced this issue before.. after tpt,it worked fine..
Sent from my ZTE Blade using XDA app
Okay
Very well, I'll go look it up. If I have any doubts I'll post here again.
Uhhh
Well I tried the TPT method, I did the manual steps as described in a website I can't link to because I have too few posts ( : ( ), and the phone does nothing, it just keeps vibrating in succession as I hold the power, volume buttons and other buttons, even with the TPT in my SDCard, is there anything I'm doing wrong, and how do I do the ADB method, is there a basic tutorial on that that's easily explained? Thanks in advance.
EDIT: I've got dim signs of life from my phone as the red led light appeared for a brief moment. I'll see what happens next.
FINAL EDIT: After a while of waiting, the red light greeted me again. And I pressed the power on button and my phone turned on like normal! : O I didn't even need to TPT! 1% Battery... My phone scared the heck out of me by being half-dead... Note to self: Never let your phone discharge too much.
Somebody close this thread ; D
my mobile having same problem

[Q] Nexus 4 now Hard Bricked, stock, It destroyed itself

Hello,
I have been having a few odd issues with my Nexus 4, random reboots, no sound from speakers unless a reboot. Anyway Last night I had it on charge and it started rebooting itself in a loop so I managed to break the cycle and I ended up on a screen with a android on its side with a big arrow pointing at the power button, so I pressed the power button and it rebooted and was sat on the Nexus 4 logo.
I left the phone doing that and when I came back a while later the phone was still on the Nexus logo (which was still animating) but the phone was roasting hot, I turned the phone off by holding the power button.
Anyway, now the Nexus will not turn on, when it is plugged into a power source I get a red LED for a couple of seconds and then it goes out. In device manager I have qhsusb_dload in device manager.
I have done many hours of searching, I tried a few things suggested on other posts using Ubuntu but nothing.
This was a stock device that had only ever been updated with official updates. I can send it back no problem but I thought I would try save everyone's time and effort and see if there was anything I could try.
Thanks
qhsusb_dload stands for Qualcomm high speed download mode. Theres nothing you can do, other than a jtag. Sorry

[Q] N7 Failure

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.

[Q] Nexus 7 (2012) dead. Just flickers

My Nexus 7(2012) 16 gb appears dead. Was on CM11 with TWRP recovery.
Here's what happened :
I was using my N7, the screen froze for a second while scrolling on the browser.
After that a dead black line appeared permanently in the middle of the screen(horizontal).
I figured it might just be the case of dead pixels.
I continued using it like that only.
After a few weeks of usage, now the device won't power up at all.
When i connect to the wall charger, i just get a back light. No display. Nothing.
I tried booting into recovery, but nothing appears on the screen.
I kept it charging for few hours, but no luck.
It only flickers when connected to charger. Disconnecting the charger causes no activity what so ever on the device.
Nothing happens if i connect it to computer via usb.
Any solutions i can try?
Press & Hold the power button for at least 10 seconds while plugged into a power source. If no signs of life after completing the above step my first thought would be a faulty board..
Its just a black blank screen.
Sent from my GT-N7100 using XDA Free mobile app
Well, I would hate to be the bearer of bad news but it appears your device had a critical failure and is now dead... Obvious answer right? HaHa
RIP Nexus :crying:
You can always try and leave it to charger for a day and see if you get some life to your nexus. I had similiar thing with my nexus, I was actually booting new ROM and then it did some flickering and got blacked out. After connecting to charger nothing happened, just random flickering. I was able to recover and get it back in bussiness when I woke up next morning (it had been charging over night). This was almost a year ago and atm I'm writing this with the same particular device. So give it a shot again, you might still get it back to work. Also you could try to boot the device to fastboot mode by pressing power+volume buttons at the same time for a while. Good luck, let me know if you were able to get it boot&work again!
You could also try popping the back off and make sure the ribbon cables for the display are seated properly. While your there check the battery cable.

Spontaneous brick after years of disuse?

I discontinued using my X Compact in mid-2020 when I got a new Pixel 4a. It's been sitting in a drawer since. It was rooted but working fine.
Recently I pulled it out to try charging it up to use as a spare. What I found was, upon plugging it in to charge, I'd get the "Your devices has been unlocked and can't be trusted" splash screen, then after the 5 seconds it would vibrate and bootloop back into the same screen, etc. I tried booting into recovery with power button / volume down and got only a blank screen. I booted it into fastboot with power button / volume up and left it to charge in that state.
Today I got all the drivers set up on my laptop and was able to access fastboot. I tried installing two different versions of TWRP for kugo (twrp-3.3.1-0-kugo and twrp-3.6.2_9-0-kugo). In both cases, subsequently attempting to boot into recovery, I got the SONY screen followed by the TWRP splash screen and then... hang.
Certainly seems like something got corrupted in there. Should I just call it a brick and leave it alone, or are there any further bright ideas on what to try?
Is the battery good? It may not be able to sink enough current otherwise.
blackhawk said:
Is the battery good? It may not be able to sink enough current otherwise.
Click to expand...
Click to collapse
Hard to judge in this state, but if I immediately plug it into charge after launching recovery mode, it still hangs.

Categories

Resources