Diagnosis: bricked? - Shield Tablet Q&A, Help & Troubleshooting

Used Windroid Universal Android Toolkit to unlock bootloader and flash twrp. All went fine.
Then I tried to gain root by flashing supersu, also with the same toolkit.
Then I got a android figure with a warning sign.
Can't remember exactly what happened then, but after that I can't power on, screen stays black whatever I do.
Charging I going fine though, charging led is green.
My desktop recognizes when the tablet is connected with usb, but I can't login with the toolkit.
Any idea what I could do or is the diagnosis: bircked?

Can you get into the bootloder? If so you are not bricked you can reflash the firmware

No, I'm not able to get into the bootloader, screen stays black, whatever I try.

Some change now.
While charging the battery, don't know how it became empty, the display shows a charging battery...
Wait till the battery is full, and then try some things again.

So happy! My problem is solved.
Here is what I did what resulted in my problem solving.
First I opened the back panel to see if the battery was all right.
After that my battery was empty, and I started loading my battery with the Nvidia adapter.
The screen showed a loading battery figure. After that I was able to boot into android as well as in the bootloader.

Related

Unusual Boot loop - even after RUU. Please help.

Hello,
I’ve got a One S (S4 version) that’s driving me crazy. Can you help me please?
I bought this phone second hand – hoping that I could fix it up and give it to my mum for her birthday. It looks immaculate, but it was sold because the previous owner couldn’t get it out of a boot loop.
When I received the phone, the first thing I did was to hook it up to the charger. As soon as the charger was connected, the charging LED came on, but then after about 5 seconds (without pressing the power button), the device turned its self on and begin rebooting at the “Quietly Brilliant” screen. It wasn’t the usual “Quietly Brilliant” screen though… There was a progress bar in the top right hand corner, indicating that it was trying to flash something. The progress bar went from 0-100% twice, then after a pause of about 20 seconds – it rebooted again. This process would repeat endlessly
After a lot of messing around, I managed to get into the bootloader. The status was “Tampered – Relocked”. At this point, I downloaded and flash the latest RUU (2.31). However, even though the RUU flashed successfully, it still boot loops. The only difference is that the “Quietly Brilliant” screen no longer has the progress bar in the top right corner (it’s just the normal boot screen now).
After this, I unlocked the bootloader via HTCDev and flashed CWM recovery. The flash was successful , but trying to access recovery also fails. It just sits on a screen with the “for development purposes only” warning for a few seconds, then reboots and follows the same boot loop sequence as before.
Does anyone know whether I’m wasting my time on the phone? At this point I’m very worried about flashing things, because I never know how much juice is left in the battery. If I hook up the charger, the charging LED does come on, but only for a matter of seconds. After 5-10 seconds, the charge LED goes out and the device automatically fires up into a boot loop. It’s impossible to power down the device when it’s connected to the charger. It will turn its self back on again! The best I can do is to leave the phone sat in the bootloader, but there is no indication that it’s charging (no LED).
:crying:
I've just read over my last message and I think the clue is in the way this thing turns on by its self when connected to power. I bet some water has got into the phone and caused a mess inside. I think it might be time to get the screwdrivers out.

Dead photon?

Hello, my Photon started acting up really weird. First of all, it was really slow. I thought it's because I had like 150MB left and it was nearly full data-wise. However, I erased most of the data, and left it with 3GB left. Didn't work and it got worse.
I have these stripes around the display (just at sides, not at middle), while phone is turned on. Doesn't matter if in system, or at boot logo. Doesn't matter, because whenever I get to system, I can be in system for like 1 minute, then every application starts crashing (Apex launcher, Google play, whatever you pick) and I basically can't get anywhere. Also if I go to sleep mode, phone is basically dead and it's pure luck when I will turn on phone again. I am trying every few minutes and it's worthless, because any time I get to system anyway, I crash after few seconds.
What to do? I was planing to install custom ROM yesterday, but never got to that, because this all started to act up. So what should I do? Reset system? Any other ideas? Is phone dead?
Sorry for bad english, no bully please.
Thanks in advance
Update - now when I am trying to start up my phone, I have just black screen with white lines in the middle. Then phone shuts down. I will give more info when I will be at home and can get phone on charger
Well definitely try to charge the device up. You might try re-flashing the stock ROM using RSD Lite... Although from your description I fear your issue may be hardware related.
Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened
kanek06 said:
Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened
Click to expand...
Click to collapse
Charge the device as much as you possibly can before doing anything with RSD. Ideally you should have at least 50% battery in the device when flashing anything.
This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.
kanek06 said:
This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.
Click to expand...
Click to collapse
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?
arrrghhh said:
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?
Click to expand...
Click to collapse
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.
kanek06 said:
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.
Click to expand...
Click to collapse
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.
arrrghhh said:
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.
Click to expand...
Click to collapse
Phone is not new. I bought it used about one year ago.
I am not entirely new to android, but I didn't have android phone for 2 years and then I got this one. So I am really pretty **** with android atm
I will try reboot to bootloader from some console application.
I am rooted, opened bootloader, stock rom
Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.
kanek06 said:
Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.
Click to expand...
Click to collapse
Well reading back thru this thread, I was suggesting RSD Lite back to stock. I'm not really sure what you want to achieve tho, what your "final" goal is here.
I'm not even sure what kind of recovery you are booted into - stock recovery? CWM?
Either way, if you want to RSD the phone back to stock, you need to boot into fastboot/bootloader mode - not recovery. Just make sure the phone is charged up as much as possible before flashing in RSD.
Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot
kanek06 said:
Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot
Click to expand...
Click to collapse
Not sure if stock recovery has adb enabled, but if you have adb you can 'adb reboot bootloader'.
Otherwise do the power+cam trick I mentioned earlier.
http://i.imgur.com/3XYLngJ.png
kanek06 said:
http://i.imgur.com/3XYLngJ.png
Click to expand...
Click to collapse
Did you remove the getvar lines from the xml file...?
Yes
Weird. I only recall seeing that when people were trying to downgrade... but you are flashing 4.1.2.
The phone is in fastboot mode? What happens when you click "show device"? The "Device Properties" section is eerily empty.
I know it sounds shady, when I am coming back here again in few weeks, just been a bit busy lately, sorry about that.
However, somehow I got phone to flash it. The white graphical lines on sides dissapeared, however I got some new bug - I can't use phone in portrait mode, just in landscape - aka I need to swipe keyboard to have phone working. Also, that thing when phone completely stops working now occurs only when I am in that portrait mode, but I can restart phone this time.
When I finished this, it was midnight so I went to bad, so I tried to set up alarm, if it's gonna randomly shutdown like before and unfortunately, yes it did. I was waken up with this classical white line graphical bug black screen and had to reboot the phone. Oh well, managed to boot to system and it takes 5 minutes to fetch sim card (I have sim card mod from cornholio) and as I said, those white lines on side aka mysterious graphical bug is back.
Unfortunately for me, starts looking like real hardware issue now

Nexus 5 boot loop, Google logo, works only on cable

Hello
I'm having problem with my Nexus 5 .
It started when I wanted to replace the battery. I have been replacing it in another nexus 5, done it gently, with plastic tools. And that's what happened - constant boot loop. Only thing that appear are battery charging image and white Google text, restart and over and over... nothing more (android colorful text/logo) doesn't appear.
Firstly I've read that it might be a problem with a power button, that it's stuck inside and making these constant loops. I tried to gently make a taps and flicks on the phone but it wasn't helpful. I accessed motherboard, took it off and checked the button, it seemed fine. But I took it to a mobile service place, and they replaced the button. But that didn't help.
I can't power it on when it's not connected to the charger or PC. It doesn't even start looping when not connected via cable to anything. On the bootloader screen I can go up and down using volume keys, but when i try to access "Recovery menu" it turns off and start looping. Even trying to use "power off" option makes it loop.
So I flashed it using factory image from google: 6.0.1 (M4B30Z, Dec 2016) (hammerhead-m4b30z-factory-625c027b).
I did it manually, on bootloader screen, entering all these fastboot commands. one by one. Everything seemed fine, all flashed with success. Already was happy! But after rebooting, it's still bootlooping
I installed TWRP recovery img to it, (successfully), and tried to access recovery menu, but also started looping.
I don't know what to do anymore. I've read so many threads and I think everywhere problem disappeared after successful flashing. I tried also this method:
https://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632 But after flashing to 4.4.4 firmware, it was bootlooping..
Since it doesn't even react to power button on both batteries, is there some bigger hardware problem with a motherboard? A battery connector socket on motherboard is broken or something?
krystian-92 said:
Hello
I'm having problem with my Nexus 5 .
It started when I wanted to replace the battery. I have been replacing it in another nexus 5, done it gently, with plastic tools. And that's what happened - constant boot loop. Only thing that appear are battery charging image and white Google text, restart and over and over... nothing more (android colorful text/logo) doesn't appear.
Firstly I've read that it might be a problem with a power button, that it's stuck inside and making these constant loops. I tried to gently make a taps and flicks on the phone but it wasn't helpful. I accessed motherboard, took it off and checked the button, it seemed fine. But I took it to a mobile service place, and they replaced the button. But that didn't help.
I can't power it on when it's not connected to the charger or PC. It doesn't even start looping when not connected via cable to anything. On the bootloader screen I can go up and down using volume keys, but when i try to access "Recovery menu" it turns off and start looping. Even trying to use "power off" option makes it loop.
So I flashed it using factory image from google: 6.0.1 (M4B30Z, Dec 2016) (hammerhead-m4b30z-factory-625c027b).
I did it manually, on bootloader screen, entering all these fastboot commands. one by one. Everything seemed fine, all flashed with success. Already was happy! But after rebooting, it's still bootlooping
I installed TWRP recovery img to it, (successfully), and tried to access recovery menu, but also started looping.
I don't know what to do anymore. I've read so many threads and I think everywhere problem disappeared after successful flashing. I tried also this method:
https://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632 But after flashing to 4.4.4 firmware, it was bootlooping..
Since it doesn't even react to power button on both batteries, is there some bigger hardware problem with a motherboard? A battery connector socket on motherboard is broken or something?
Click to expand...
Click to collapse
Have you tried putting the original battery back in it? Does it not correctly only when plugged in to a charger cable? Idk how but it seems either something bad happened to your emmc or there's something not plugged in correctly to the motherboard and something may have happened to whatever piece(s) that is. I'd just take everything out and put it back together, I had to do that when I replaced my screen, it's a pain in the ass but it worked again. Hopefully I could help you, or even give u a clue as to what it is
Try flashing 4.4.2 or an older stock ROM.
Aurey24 said:
Have you tried putting the original battery back in it? Does it not correctly only when plugged in to a charger cable? Idk how but it seems either something bad happened to your emmc or there's something not plugged in correctly to the motherboard and something may have happened to whatever piece(s) that is. I'd just take everything out and put it back together, I had to do that when I replaced my screen, it's a pain in the ass but it worked again. Hopefully I could help you, or even give u a clue as to what it is
Click to expand...
Click to collapse
I did it now. On both batteries it doesn't even power on. Only on a cable plugged it it starts bootlooping, when disconnecting, it powers off.
I checked all the connectors and sockets on mainboard, especially the one connecting battery and they doesn't seem anyhow broken (but I'm not any tech specialist so..)
audit13 said:
Try flashing 4.4.2 or an older stock ROM.
Click to expand...
Click to collapse
I used now 4.4 (KRT16M). No result, still boot looping

[Solved] S6 G920V reboot loop, cannot boot into maintenance, only ODIN mode

Hi!
Very weird situation. Before that everything was stock and OK (no custom ROM or anything).
- If the phone is unplugged, nothing works at all (key combinations,...)
- The battery is charged, at some point, when totally off, it showed the battery charging, 60% at least. But have not been able to go back into this mode.
- When connected, it starts booting, but keeps rebooting very fast (1-2 s after Samsung splash screen).
- Unable to boot into Recovery mode (UP+HOME+PWR, for wiping cache,...). Just does nothing, howerver long I wait
- Unable to boot "directly" into Maintenance Mode (all buttons), more on that later
- Can boot into Download (ODIN) mode (DOWN+HOME+PWR) very easily. I was able to flash stock ROM, but nothing changed.
- From ODIN mode I can boot into Maintenance mode (all buttons). I can navigate the menu, but any choice, even Factory Reset, gets me directly back to the reboot loop...
As I can not even turn it off, I cannot drain the battery (at least not quick). As soon as I disconnect the cable it goes dark (whatever mode I am in).
Anything I missed that I could try before throwing the phone?
Thanks!
SOLVED
Just to leave a trace on what happened:
- Left the phone alone, un plugged, for 8-10 hours.
- Just to see, tried to reboot it normally,
- It booted on a blue/cyan display, with "installing updates".
- At one point before I had that screen, but after 10 seconds it rebooted into the loop cycle. And after playing with the recovery reboots, I had never managed to get this special boot again.
- This time it stayed on "installing updates" for 1-2 mn, then rebooted, and Voilà!!!
So apart from my magic touch of doing nothing, don't really know what happened... So much for the recovery recipe!
A fairly similar thing happened to my girlfriend's g920v yesterday. We haven't been that lucky that it got fixed.
The situation is slightly different though, it boots for about 3 seconds, makes the low battery sound, battery indicator says 0%, then shuts back down.
Tried flashing stock in odin a few times, a few factory resets, nothing.
It seems like an OTA update failed and now the stupid locked bootloader won't let me or the or OS fix it.
Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.
guimou_qc said:
Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.
Click to expand...
Click to collapse
There's got to be some connection of some sort, yours is the 4th post I've seen here or on Reddit this month about bootloops probably related to updates

Samsung GT-P3110 Bricked(?)

Hello, recently I started reading comics and found my old tab lying around so ill give it a go
First thing first it wont boot becaue it had no charge obviously (been there for like some years), then I tried to plug the charger but to no avail
I cleaned the contacts of the charger with a dry brush and start charging which then my tab starts charging!
when I booted, I think it was CM 12 (or 13? the one with andy I believe) and everything is force stopping.
I then tried to go to recovery mode and wipe data, but when i rebooted it it just stuck with the splash screen (the one before bootanimation)
I turned the tab off and tried to boot to download/recovery mode but it would just boot me right to the splash screen again, which mean i cant go to TWRP or ODIN.
And it doesn't always want to turn on, sometimes it just stuck there with black screen (not turned on) even if i press power/combo button, sometimes it pop up to the splash screen. what i notice is that i should wait for the charging indicator to show up before i can try to boot again (i got enough juice now, 56% the last time it turned on)
also one thing i remember is something about F2FS but im not sure what that is, but that might be a clue to my situation so ill just write this down here
Hi
Same here with P5110 and Slim7. I can't start it anymore....
I didn't use it for some time and then i charged it to 100% and it started but everything seemed to lag. Then i turned it off and wanted to look for another rom or a newer build. But i can't start it anymore. when i plug in the charger i can see the charging screen but beside of that i can do nothing. It has no effect when i push the on/off button or anything else...and it has to be at nearly 100%...

Categories

Resources