So i was using my phone and decided to restart it after updating my adaway files but my phone never turned back on. The two press the power button screens did not show up either. I tried to uses the MSMdownload tool since i thought my phone was somehow bricked but that didnt work either, it just kept restarting the download process after everything was completed. my computer makes a sound when its connected and it connects correctly as a quallcomm 9008 device but even after all this nothing is working. has anyone experienced something like this or does anyone have any advice?
did you try to long press both power button and vol up ...you should feel a vibration...
maybe it's not turned of maybe it's error causing the screen to be off... also is there any heat?
Which method of the unbrick tool did you use? First or second? If the first, then maybe you should give the second also a try.
Sent from my ONEPLUS A3003 using Tapatalk
I've tried everything and I used th me second method yet nothing happened. I can see my phone get recognized by the computer and get listed on the MSN device list yet nothing happens after it finishes the process. After the green line shows up telling me that it's completed everything the process restarts writhing a few minutes unless I unplug it. No vibration no nothing the phone just died on me after I restarted it .
Try doing MSM on a different PC with all drivers installed , hope it helps
Try to repeat flashing again, there is no other way. Use method 2only. Extract tool again and try flash.
When I was used Xperia Z1, I bricked my phone with a soft brick. So I installed driver in my PC and flash Kernel though FASTBOOT(ADB) either it's not show Device in my PC (I show just "Unknown Device").
After that my phone can connect to my PC again (Now It shown C9303 or something that meant it know it's a phone).
So I can flash by Flashtools again. Soft brick is not scary as Hard brick, you'll find some way to bring it back easily.
Hope this help!
PS. Bricked Phone is WEAK in Battery, always connect it with charger.
Hello, I would like to first tell you the story my LG G4 has gone through and then I tell you the error.
So, at first my phone was working absolutely properly. I accidentally deleted some pictures and to do a recovery, I had to root it. And rooting would be useful for later so why not do it?
So I first unlocked the bootloader through the code from the LG site. After unlocking, the phone reset (because it would be just too good to make some memory changes and nothing more.) But allright. Then I was ready to root. I just booted the phone, everything was fine. I unlocked the developer mode and opened ADB. I rebooted to recovery through
Code:
adb reboot recovery
I was expecting to see some menu with buttons (but that would be just too good). However, I saw just android with a red triangle in the middle. Nothing more. No response to buttons, nothing.
So I thought. Allright, let's boot into recovery using hardware buttons (vol down + power) at startup. Unfortunatelly, it seemed like there is no such mode System just normally booted (and that was just after bootloader unlocking. Recovery mode goodbye.).
I tried to send commands to the phone using diagnostic port. Unfortunately, it responded by FAIL to every command.
I reboot to bootloader and booted an image: "boot-em.img" (from here: google: how-to-root-lg-g4-on-android-6-0-marshmallow-20a20b-firmware. I'm a newbie here. thx for understanding.)
After that the console uploaded the image and booted successfully. Then, however, system started to boot up and was endlessly booting (LG boot animation) till the battery was critical.
I was able to access the EMI number through volume-down button and volume-up button pressed simultaneously.
I was also able to access some factory-reset dialog by holding volume-down and pressing power-button several times. I choosed to reset everything and then accepted it with one more 'are you sure dialog'. System rebooted and was stucked in the LG boot animation.
Then I got to download mode, since recovery mode was lost in hell. Through LG-UP I flashed the original KDZ firmware and everything got back to normal, but recovery mode was still inaccessible through the hardware buttons. I got through the process of setting everything up, getting developer, rebooting to bootloader and I booted TWRP.
TWRP loaded and it responded to double-tap on screen to wake it up. I just checked the menus and let the phone sleep.
After several hours I went back to the phone and double-tapped on display. Nothing. Phone was not responding. I pressed the power button and the phone restarted (I think. It either restarted into the system or was not responding to power button.)
So I got to the system and again rebooted to the TWRP (through fast-boot). I tried to back-up one partition to the disk. During the process phone had turned the display off. So I double tapped. Nothing. I removed the SD card and the phone woke, saying that back-up process was not able to complete. Suddenly it stopped responding to double-tap. It woke up through an interrupt. I re-inserted the card, successfully backed-up the partition to the SD-card and I left the phone laying on the bed plugged in the charger. It stayed that way for 4 hours or so, doing nothing. All of a sudden, a yellow screen was there, (and that's a screen of absolute death that was never supposed to come. Little I knew.) saying that an unexpected critical error happened and to do a memory dump, insert a cable, set up some communication (I don't remember what it was, didn't take a picture of it.) and it could send the memory dump to PC or somewhere. I thought to myself. So, the application is not so stable after all. It said that to reboot just press the power button or something.
And now the problem comes:
The first start: Bootloader booted, LG animation went on and finished. The starting up apps dialog came rolling. Then, system restarted.
The restart: Bootloader booted, LG animation went on and freezed. Then, the phone restarted.
Second restart: The same thing as the first one.
Fourth restart up till now: Bootloader tries to boot and restarts before the LG animation.
I got to download mode and it restarted even there. After re-inserting the batterry I can sometimes get to the Firmware Update window and communicate. There I flashed the official firmware again.
No success, as if I didn't even do it. It restarts before the animation.
Can I do anything with the phone? Hopefully I can. No hardware problem occured (except for a situation where the error could fry the wires inside the mighty System On Chip.)
For the software state I cannot even tell but I might say it's cooked just wrong. That's why I came here.
I know I did some pretty stupid steps. But the error was not done by me. It worked fine and after the yellow screen which came by itself, it just (some bad words).
Thanks for replies.
Phone: LG-G4 H815, European market
Solution
So, I was looking around and believe it or not, this problem disconnected the pins on the motherboard's snapdragon 808.
I think this happened: The device, although it was heated many times during its life, it withstood that so far.
However, a longer run of the TWRP had finished it off. Memory got disconnected while running and it threw a yellow-screen.
Pins got disconnected and from then on it was just a standard common LG bootloop issue.
The continuous process of dying (First it partially loaded, then only animation, then nothing) is explained by this fact that the pins were so-so there and a couple of reboots just got it totaled.
Temporary fix:
Pre-heated the memory chip to 250°C using Hot-Air gun. After 18 seconds at this temperature I pressed the memory on top of the snapdragon down to the board while cooling.
Then I added a little metal square on the metal part that is covering the system on chip. This part is over the SOC where before there was just some tape.
This can work for several days in sleep mode or a couple of 'heat-demanding' operations on the phone.
Permanent solution should be to reball the memory chip on the snapdragon. That's my next step.
T-Mobile S8+ [G955U] -- Factory reset resulted in complete wipe & no longer boots up.
I have a Samsung galaxy S8 plus (T-Mobile) [SM-G955U]
Current Firmware:
G955USQU4CRE9
I'm using windows 7 to attempt to repair my phone.
My problem is as follows...
A few weeks ago my phone started giving me the dreaded:
"Unauthorized actions have been detected..."
error code and sending my phone to restart.
This has happened to me in the past on other phones so i thought, ok. restart and it should be fine. However, this kept happening... the next day and on the 3rd day it happened about 3 times in a row. At this point I was cautious and backed up all my files, turned on USB debugging and shut off my wifi & data.
I then proceeded to do a factory reset from the settings. Once it restarted I got a weird error stating something like no such recovery file could be found. When I saw this I knew I messed up because I didn't first take a backup of my system & recovery...
I got a hold of T-Mobile who walked me through their reset steps, none of which worked. They had me contact Samsung and I did but to no avail. Simply stated they mentioned they could fix it if I had warranty, if not I would have to pay for repair.
Either way I sent all information to Samsung and they have not gotten back to me even though they mentioned we'd hear back in 48 hours. (it's been about a week) I've tried to reach out since then but I haven't had a lot of time to sit on the phone with their elevator music...
Ever since then I've tried everything from Samsung Smart Switch to re-flashing through Odin with no luck.
I've tried all of the reset options...
Hard reset
Soft reset
Wipe cache (recovery mode)
Wipe and factory reset (recovery mode)
Simulated battery pull
etc., etc., etc.
Nothing works. Odin flashes correctly (i get "PASS") and the phone turns off but does not turn back on.
I've tried several tricks to get it to turn back on but it won't go past the boot screen (Samsung Galaxy S8+ screen)
I've flashed, re-flashed, wiped, reset, etc.
Now smartswitch doesn't even work on it because it does not recognize the device...
When i connect my phone now it just shows up as the qualcomm chip. I get "Qualcomm HS-USB QDLoader 9008" under devices...
ADB only works when it's in download mode or recovery mode but it doesn't recognize the device either...
Another problem is the increased time it takes to get into the boot menus (download or recovery).
Sometimes when I haven't touched my phone for a whole day I can get into download mode within 10 seconds or less but the more I try it and especially if I successfully flash stock software, the next time booting into recovery or download mode can take up to 5 minutes (holding the button combination). Recovery mode is worse.. even after 24 hours without touching the phone it will come up maybe in 3 minutes but has taken as long as 7 minutes... my fingers are in pain.
Essentially, even after successfully flashing my phone will not boot. and when i hold vol_down + power i can sometimes get the boot screen but it won't go past that.
Also, None of the above boot options work if my phone isn't connected to power--these options only work when it's plugged in. If my phone is not plugged in it will not vibrate, light up, boot up, or do anything other than behave as a paperweight.
I believed it may have been a charging issue so i left it plugged in overnight and even went to download mode and plugged it in for a few hours but that doesn't affect it at all. Even if i'm in download or recovery mode it'll turn off right when i unplug the device.
I'm trying to get it to the best buy that's approved for samsung repair but when I called they said they wouldn't repair it anyways because i didn't buy it there... -_-
Please let me know if I need to provide any other information. I'm trying to get an image of the recovery screen so you can see the error it gives me... Something about no file found. This is increasingly difficult though because some times it takes too long to get into these modes and I leave it alone and come back to it later.
Has this happened to anyone else? Can someone provide some sort of advice or a method to fix this?
thanks in advance.
Can you download the Qualcomm HS-USB QDLoader 9008 driver, and then see if you can fastboot oem-unlock and see if it unlocks your bootloader
Hello.
I could really use some help/directions in recovering the bricked phone. Right now it doesn’t react to any buttons pushed (including power + Up/Down etc.) I think the issue is with the incorrectly processed boot/recovery layers/partitions.
What did I do?
The phone was fully functional, so it is unlikely a hardware failure. After flashing the TWRP to the recovery I was getting BOOT error (typical for lollipop), and attempted to fix it with autoRec.
After the phone turned off, it is not turning on again. Connecting it to two computers (Win 10 and Win 8) does not result in any new devices appearing in the Device manager. Shortening the second pin on the phone does not result in anything either.
When the phone is without battery and is connected to the PC it displays a battery problem on the screen – the charging symbol together with yellow triangle with a question mark (the only time when the screen turns on). If I connect it once again, when the second pin is shortened with the ground, the phone remains dead.
Currently I’m out of ideas, and curious whether the phone is already bricked for good, or there are still some other options left.
The Phone is D855 16GB version (most likely German).
Apparently the problem was with Win 8.1/Win 10.
For some unknown reason the phone wasn't identified even in Quallcom mode. I've made a clean Win 7 install, and then it did (after shortening of the second pin). Now it works.
edelgul said:
Hello.
I could really use some help/directions in recovering the bricked phone. Right now it doesn’t react to any buttons pushed (including power + Up/Down etc.) I think the issue is with the incorrectly processed boot/recovery layers/partitions.
What did I do?
The phone was fully functional, so it is unlikely a hardware failure. After flashing the TWRP to the recovery I was getting BOOT error (typical for lollipop), and attempted to fix it with autoRec.
After the phone turned off, it is not turning on again. Connecting it to two computers (Win 10 and Win 8) does not result in any new devices appearing in the Device manager. Shortening the second pin on the phone does not result in anything either.
When the phone is without battery and is connected to the PC it displays a battery problem on the screen – the charging symbol together with yellow triangle with a question mark (the only time when the screen turns on). If I connect it once again, when the second pin is shortened with the ground, the phone remains dead.
Currently I’m out of ideas, and curious whether the phone is already bricked for good, or there are still some other options left.
The Phone is D855 16GB version (most likely German).
Click to expand...
Click to collapse
Hallo mein Freund
Use my guide here:
https://forum.xda-developers.com/lg...w-d855-30b-t3286268/post72875603#post72875603
Lol the thread is from April...but who knows,perhaps we save a phone today
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Call whoever you bought the phone from and do warranty claim.
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
Bootloader unlocked?
cultofluna said:
Bootloader unlocked?
Click to expand...
Click to collapse
If I remeber correctly flashing factory images forces you to unlock the device. So yes, the bootloader of rao_hamza's device should be unlocked.
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Pixel 6 uses Google's own new Tensor chip - so no Qualcomm tools
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
roirraW edor ehT said:
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
Click to expand...
Click to collapse
This and a bad/wrong cable seem to be the most common culprits
ridobe said:
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
Click to expand...
Click to collapse
Any idea how long you had to hold that button combinaiton? I tried longer, maybe 60 sec, but still no response from the phone.
tids2k said:
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Click to expand...
Click to collapse
What is EDL? and had the Google usb drivers installed, to get the fastboot working.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
Yes, I don't know who to get into a bootloader in this situation, if that were working I would have some hope.
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
pysklona said:
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
Click to expand...
Click to collapse
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
rao_hamza said:
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
Click to expand...
Click to collapse
Sorry, misread the post.
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
ootri said:
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
Click to expand...
Click to collapse
Thanks for sharing your experience. I just returned the device and got myself a new one.
anyways, i am not sure what is causing this hard brick. thats is something we all should be careful about it.
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Hmm, maybe plug it in to a PC via USB to supply it with power (maybe the battery is down) and just do a very long press of the power button - at least 30 seconds - until the phone starts up. If it does and isn't in fastboot you could try "Power-VolDown" to get into fastboot...
If it just doesn't react to all of this and waiting a bit (in case the battery was at 0% and needs some minimal charge) I think a replacement is the only way to go....
Enddo said:
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Click to expand...
Click to collapse
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
roirraW edor ehT said:
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
Click to expand...
Click to collapse
appreciate the links. right now, I can't even get into fastboot/bootloader mode. so neither of those tools detect the phone.
@s3axel the battery definitely isn't low. I charged it up before all this specifically so that I know it had plenty of juice (was at 93% or something).
I'm thinking maybe after letting the battery die, charging it back up will let me boot into a special boot mode
but any other ideas, please, I'm all ears