Database Users

[Q] Possibly bricked MT4G after attempting root with visionary 14, please advise

So like the total noob I am I tried to root my MT4G using visionary v14 (I think, can't start my phone to check) without having all the appropriate files in place. This caused Visionary to crash when I rebooted my phone. I gave it some time and then being unable to restart using the power button I pulled the battery. After that the phone has been totally dead, I can't get it to turn on at all or even recognize that it is plugged in. I have tried starting plugged into my computer, unplugged, plugged into charger and all possible combinations of SIM card and SD card in/out. Nothing. I am very afraid I bricked the damn thing, but I'd appreciate any input... especially since the the replacement would come with Gingerbread and I really don't want to have to go through the whole downgrading crap.
Thanks.
Cheers,
RobotPenguin

Hello RobotPenguin,
I'm not a specialist (actually, I'm quite a newbie here) but most of bricked device can boot to the bootloader or at least display the splashscreen.
Are you sure the battery is alright and correctly installed ?
Regards

I assume so. It was fully charged when it crashed and the "tech" at the T-mobile Store swapped out the battery in my phone with the charged battery from her functional MT4G to no benefit.
Thanks.

I believe this may be my answer... damn.
http://forum.xda-developers.com/showthread.php?t=1231765
I swear I searched for hours... I guess wrong keywords. That's what I get for frantic sleep deprived searching...
Cheers,
RobotPenguin

Well, lets check to see if it is bricked
1: pull the battery out
2: put the battery back / put on the battery door.
3: hold the power button and the volume down rocker.
* the device should boot to a white Screen with three Android Skateboarders.
**If you get to that screen it's a good thing.
**if you don't then you are SOL.
4: try doing a factory reset from that white screen
5: reboot the phone.
If it still doesn't boot you need to load the PD15IMG.zip onto the root of the SD card and start over.
If the PD15IMG.zip doesn't load (given the MD5SUMs match), or give you any errors at all you are SOL.

neidlinger said:
Well, lets check to see if it is bricked
1: pull the battery out
2: put the battery back / put on the battery door.
3: hold the power button and the volume down rocker.
* the device should boot to a white Screen with three Android Skateboarders.
**If you get to that screen it's a good thing.
**if you don't then you are SOL.
Click to expand...
Click to collapse
I got that far and no recovery screen... so I guess I'm SOL. I guess I'll just wait for the new one to come from T-mobile and do the whole downgrade bit so I can root the phone. Pain in the @$$, oh well.
Thanks for helping me out.
Cheers,
RobotPenguin

Most probably you've attempted to flash Engineering HBOOT ("root.sh" way of rooting) and failed, which left your phone without bootloader.
You can't recover from it.

if holding power and volume down does not get u into hboot then u r screwed. Hopefully u didn't cheap out and got the insurance for your fone. If u do have insurance on the phone then call asurion (the insurance company t mobile uses) and tell asurion that u lost your fone (say u left it on the bus).then pay your deductible and get another fone.

I have rooted 2 myt 4gs and they both crapped out for 3-10 days then magically started working. The whole time they were down all they would do is flash an orange light and vibrate 3 times when i powered on or vibrate 5 times and flash green when i tried bootloader. I pulled the battery out and left it out the first one was 3 days and the second time was close to 10 days then bam they came back up

+1
Thanks for the info guys

wont turn on and screen flashes when plugged into a charger..weird?

so i got my nexus 7 back around january and right when i got it i unlocked and rooted it with the tool kit. I was flashing many ROM's and kernals too but im a college student and got busy around march and so i wasnt using it and it was just sitting in my drawer. At the time it was in my drawer i remember it was working and powering on. So last month it came to my mind that i wanted to use the nexus 7 since i have time now. I go and look for it and when i found it and tried to turn it on it just wouldnt turn on.
First i plugged it into the charger with the ORIGINAL cable and plug for the whole day but when i plugged it in the screen started flashing every 3 seconds with a plain white light. So i tried booting into recovery using the power and volume buttons and that didint work. So i searched around the web and found that pulling out the battery and re connecting it works for most people. So i tried that and nothing changed. Right now its sitting plugged into the charger...flashing a white light every 3 seconds. So what else can i try? Idk if i have warranty too so im worried right now. The original owner received it as a gift and he was like 45 years old and didin't have the receipt to return it. My brother knows this guy because hes a regular customer and he bought it off of him and gave it to me knowing i like android devices. So i don't have a receipt for a RMA so idk what to do. Another thing is that the bootloader was unlocked last time i used it.
Please dont ignore this post and give me an opinion on what to do. Recommend me trying to give it to a electronics place to have them look at it and quote me how much would it cost me to get i fixed?

Your battery has discharged too low and your tablet has entered a form of hibernation to prevent it from becoming permanently damaged. Plug it in and hold all three hardware buttons to boot to the bootloader. From there, select power off. You should then be able to charge and use your device normally. These instructions are among the potential steps to take posted in the sticky thread at the top of this forum. http://forum.xda-developers.com/showthread.php?t=2090826

Thanks for the ride

So my otherwise trusty I9100 decided that it wanted to sleep the eternal black sleep. Yesterday it locked up and I had to remove the battery. When powered on, it asked for the password for the encrypted storage (I do not have encrypted storage that I know of). I could only power off or reboot at that point. I chose shutdown and let the phone rest for a couple of minutes. Then I started it again and then it went into eternal boot loop. I powered off by holding the power button and when that seemed to fail, I removed the battery. I tried to enter the normal boot menu (running standard firmware 4.1.2). This failed. I tried to use the volume down+home+power button and that to my relief showed the warning about installing a custom os. I proceeded and Odin started on the phone. Great I thought. I can at least flash the phone and have a phone again. I downloaded the firmware and Odin 3.0.7 and proceeded to flash. Odin 3.0.7 could detect the phone and started sending the cache image preparing instructions to the phone. This took a long time and then it timed out. The phone still showed the Odin downloading screen. I tried to restart the software on the pc, but that failed right away. I tried to restart Odin on the phone, but the phone was now completely dead. Black screen forever.
For reference, I have flashed with Odin before (long time ago) and it worked as intended. Besides, I was following the troubleshooting guide presented here on this site for the S2 and right now, I can get zero signs of life from this phone.
Seeing as my friends S2 died after 2-3 years with black screen of death and my sisters S2 died with black screen of death, also after approx 2 years and now my phone after close to 3 years, I can only suspect that Samsung has made the phone to die this fast. I only know of 2 more persons that have such a phone and their phones are not so old yet. But I guess theirs will die after 2-3 years as well. :-/
So, it was interesting having a smartphone and I liked it, but now I am back on my trusty old Nokia i6110 (has run 11 years without issues and with original battery, still lasting 3-4 days per charge).
But I'd like a new smartphone, just not a Samsung. They have burned me enough.

I just learned that the phone might be salvageable using the JTAG interface. So, any JTAG'ers around the Århus, Denmark area?

galmok said:
I just learned that the phone might be salvageable using the JTAG interface. So, any JTAG'ers around the Århus, Denmark area?
Click to expand...
Click to collapse
There's a thread called jTAG centre near you or something like that, look it up, maybe you can stike luck.
My device is like 3 years now, but it's gonna live forever, I'ma see it thru

If you have any linux (get a live cd for free everywhere) at hand post 'lsusb' into an terminal when the phone is connected. if it shows up any sign of an active usb device it might still be alive, else it truly is a jtag case

Nexus 6p - bricked?????

Hi all,
Hopefully this wasnt covered before- I used the search function and it didnt return any results, at least not for my specific scenario.
I've had this 6p for about 18-20 months roughly. Been my best phone by far, and I've been very happy with it(normally i replace my phones every 8-12 mos because I need the latest and greatest lol).
About six months ago I threw PureNexus on there with I believe Flash kernel. Worked flawlessly, and I've been really happy with it.
About a week ago, it powered off on its own but i had it in my back pocket so I just assumed it was an accidental reboot. However, this morning, I woke up, threw it on the charger for about 30 minutes, got to about 60%, and unplugged it. While I was using the browser, it froze up for a minute then shut down. No bueno. Cannot get it to power back on. No power light while charging. I did what others have had luck with, holding power, and/or power/down for several minutes, still nothing.
I reached out to Project Fi, and they want a 500 dollar hold to send me out a refurb replacement. I know they release the funds in approximately 12 days but we had a recent death in the family and I just cannot afford to have 500 bucks locked up, especially right now. Spoke w a supervisor, apologized, but said nothing they can do.
On a whim, I plugged it into the pc, and it DOES detect it but its the dreaded QHSUSB_BULK under 'other devices'. So that tells me its at least got power, but, I'm unsure if just trying to use adb(i havent in a while, not since i did the initial rom install but im sure i can find instructions) to attempt to throw the base image back on there, will work, or which direction to go.
I found this but I dont think its for my specific phone but thought maybe there was a set of instructions for this particular phone similar to these:
https://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I have seen several reports of this error happening when flashing the wrong rom, or using the wrong image, but never just all of a sudden when its been running like a champ.
any thoughts? thanks in advance.

Nexus 6p is plagued with issues like shutting down at certain percentages and the dreaded bootloop of death. You could get in contact with Google heard even people out of warranty having success. Could also have a shop replace the battery in some cases that fixed the shutdowns.

If it doesnt boot up at all I can't help you. If you can get to bootloader, flash stock image, un-root, re-lock your phone. see if it boots. I had to do all this, this morning. Phone would just shut off at 80%, reset and hang at the google sign. I could only get to into the main system with a hard reset every time. then it would reset and lock up. So i reverted it to stock and we will see how it goes. So far its been 6 hrs and no random resets and its in full use.

Yea, the problem is, I cant. Its not even a boot loop. Just looks like its dead. Held the power button down for roughly 10 minutes out of desperation.
The odd thing is, if i plug it into my pc it shows how i mentioned in my initial post. So it must have juice even though the power light/etc isnt on and it doesnt show charging.
Last hope I think i have is to run it out of battery leaving it on the table, then hope somehow when i plug it into charge, that resets it somehow since it was dead, and maybe clears whatever the issue is. Very odd considering it was working fine until this.

Your phone is stuck in the EDL mode when its detected as QHSUSB__BULK. There are solution for this but i dont know if this solution is combined with data loss or not and i try to find that out recently. I also still dont know how to fix that with linux.
Here two howtos:
https://forum.xda-developers.com/nexus-6p/general/guide-how-to-bring-to-life-dead-nexus-t3581948
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838

Bricked Le Pro 3 727 (Blue Screen of Death)

Hello friends,
My LeEco Le Pro3 (727) bricked two days ago and I haven't had any luck turning it back on. It was running LineageOS 8.1 latest official build with an unlocked bootloader, Magisk 16.0, TWRP 3.2.1, and OpenGapps ARM64 8.1 nano. Immediately prior to bricking I was setting it up for bluetooth with my car and was trying to run Google Maps through voice command. As I directed Google Maps to take me to a location, the phone froze, the screen got all "fuzzy" and I got the dreaded blue screen of death.
From that point on I have not been able to turn the phone back on. When I press the power button it will vibrate every 5-10 seconds as though it will turn on but it never does. Ive tried everything I can think of to get to work again including:
- Pressing power button for 2 min, 5 mins, 10 mins
- Pressing power button + vol up (recovery) for 2 min, 5 mins, 10 mins
- Pressing power button + vol down (fastboot) for 2 min, 5 mins, 10 mins
- Pressing power button + vol up + vol down (QFIL MODE) -> Installing Qualcomm driver, downloading "FlashOne2.0", flashing all versions of "qfil files" that I could find but still unable to boot up
- Pressing all different button combinations while plugged in to computer/charger
- Using different cords/chargers/usb ports
- Leaving it to charge overnight/full day then trying to boot up
- Leaving it sitting not charging for a full day then trying to boot up
At this point I'm starting to think it might be a hardware issue but who knows..
Any advice/suggestions would be greatly appreciated.
Thank you.

Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium

My one did the same, the issue was motherboard. You should send it back to repair.

mchlbenner said:
Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thank you for the reply.
It was purchased from a local retailer here in the United States through Google Express. Fortunately I should still be able to return it for a full refund but I would rather have a working phone than my money back.
No flashboot either. It's like the phone just decided to quit working one day. Tried holding power while plugging in USB as well and no change.
marik1 said:
My one did the same, the issue was motherboard. You should send it back to repair.
Click to expand...
Click to collapse
The conclusion I'm reaching at this point too. I'll see what the return policy.

Well if it will not turn on it is hardware issue you should be able to return it.
Sent from my LEX727 using xda premium

That is so strange. The screen going fuzzy like that is indicative of a hardware issue, IMO. I saw that on my laptop once, but that was because I hit the screen too hard. Never seen a BSOD on an Android device before. TIL.
I assume you've already tried an adb logcat. Were you using the original LeEco cable? I heard it has issues since it's not up to spec. 99% hardware failure, but I can't help but think it has something to do with driver communication confusing the device and causing hardware failure (?) if that's even possible.

Just a final update for those curious.
After leaving the phone alone for two days I plugged it into the charger and low and behold it started vibrating and booted up by itself. It was running a Chinese developers editions 720 rom due to the QFIL File I had flashed in my earlier in my attempt to fix it. Battery was drained so I let it charge for a while and everything was fine until I attempted to restart the phone. As the boot animation was loading, I got the blue screen of death for a second time.
I took a quick picture, the phone shut off itself off, and same as before it wouldn't boot again. As other users have suggested it appears to be a hardware issue, likely with the motherboard. Fortunately I was still able to return the phone (purchased through Google Express via a local retailer) and received a full refund. I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.

shyboi122 said:
Just a final update for those curious.
I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.
Click to expand...
Click to collapse
You bought the same phone again? :good: You're courageous, lol.

i been experiencing the exact problem like your on my x720, as i boot up the system or enterting the recovery mode the screen go fuzzy on loading screen and shut itself off completly, i can still able access fastboot. As i left it for a while the phone will be able to almost finish the boot then ending it all with a blue screen.
Have anyone found a way to fix this DIY since my phone has past the guarantee plan ?