Related
I accidentally formatted bootloader, and now my device unable to detect,boot or anything. Is there anything I can do of ?
(might try everything to work it out )
Can you boot into the preloader with volume up and power pressed?
flash ROM via FlashTool
BlueFlame4 said:
Can you boot into the preloader with volume up and power pressed?
Click to expand...
Click to collapse
no, i could not
Kittehdispenser said:
no, i could not
Click to expand...
Click to collapse
Sounds like a hard brick, which means your phone is destroyed. What exactly did you do?
BlueFlame4 said:
Sounds like a hard brick, which means your phone is destroyed. What exactly did you do?
Click to expand...
Click to collapse
welp, i tried to install custom rom ( which need to download the rar and paste it into INTERNAL) but i accidentally paste it to my SD card. Then i start to install it.
Then i said it's uninstallable, I just restart my phone and everthing went normal buy my wallpaper screen turns black and unable to read it tho USB ( Just the standby screen shows wallpaper)
Then my brothers came out and said that all you need to do is format it again and reinstall. We tired countless times . But then it have another option which above Format everything but not bootloader and another is Format everything and bootloader.
Then my bro press it and ... It became bricked.
it's still warrantyable so .. I plan to play dumb to the warranty company if I can't fix it.
( even if i play dumb idk what reason I need to come off, if i say yesterday the battery from 70% drop to 0% then it unable to open again )
PS: before this happen my battery happens from 70% drop to 0%, after charged. it's fine
PPS: give me a good excuses to play dumb C::
Wait, wait. How did you format the bootloader? No recovery should have this option! The only possible option to hard brick the P8000 is to pull out the USB cable in the exact moment when the SPFlash Tool writes it. So, can you elaborate a bit more about what you've done? I'm pretty sure you're missing something.
Soft Bricked HTC Desire 616
BlueFlame4 said:
Wait, wait. How did you format the bootloader? No recovery should have this option! The only possible option to hard brick the P8000 is to pull out the USB cable in the exact moment when the SPFlash Tool writes it. So, can you elaborate a bit more about what done? I'm pretty sure you're missing something.
Click to expand...
Click to collapse
Hi,
I did something similar with my HTC Desire 616. I choose "Format All + Download" option with SP Flash Tool. The phone soft bricked. Later I tried "format whole flash (including bootloader)". It's still soft bricked...
Is there a way to revive my phone back??? :crying:
I had the same problem - but it is possible to set the phone to a special bootloader mode called META mode - see this video: https://www.youtube.com/watch?v=A3TmXtOA0IA
To do so you have to open the phone and disconnect the battery. You can find a howto easily on youtube.
Then set up everything to flash the phone (SP-Flashtool, scatter file, etc.) and push the volume down button while connecting the phone to the computer. This switches the phone to META mode, the computer can recognize the phone, installs the preloader driver and finally flashes the phone
Maybe you have to do the procedure twice because on the first connection only the preloader driver will be installed.
This worked for my P8000(B) which I treated with SP-Flash Tool and "Format All + download"
Be aware that you formatted the NVRAM and lost your IMEI's
FrauHofrat said:
P8000(B)
Click to expand...
Click to collapse
What the meaning of (B)? Just asking because i have (W)
Tecno spark 3 pro clone flash file mt6570 android 9.0 firmware
Hi
I need your assistance, please help me find the firmware for the above phone. I recently tried to flash it with a Spark 3 clone firmware i got online but it gives an error STATUS_PARTITION_NOT_FOUND and also i accidentally formatted the bootloader on SP Flash Tool so the phone is a brick, it can't charge, and it can't turn on. I have screenshots of the About section when the phone was working, which contains the phone's features model and build but on opening the back cover of the device, i realized its a clone phone and i cannot determine its real model to get the exact right flash file.
Thanks
Hello all,
I've done a lot of googling and searching on these forums and I'm having no luck. Hopefully by asking I can get some headway.
I was attempting to restore to stock rom. At 17% of the process using LGFlashTool 1.8.6 the tool gave me an error 'Unable to Communicate with phone' after about 10 minutes of no progress. I exited the LGFlashTool program and ran it again and now it fails saying 'Cant' change to download mode". If I turn the phone off and then press Vol+ and plug in my cable it just goes to the Firmware Update screen. My phone *IS* detected properly in the device manager as LGE Andriod MTP Device and under ports as LGE Mobile USB Serial Port (COM41). If I go into recovery (Vol- and power) it asks if I want to do the restore - but it doesn't actually do anything once I say yes twice. Just sits at the firmware update screen at 0%.
I looked at this post (http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091) but it appears to be either for a different phone or different problem (showing in device manager as a bulk device - mine is not doing that). Frankly I don't want to make things worse (if that's possible)
Does anyone have a way that I can restore the download mode for this D852 phone? I'm hoping if I can get download mode to work again I can reflash the stock rom. I don't care about the data on the phone at this point.
I'm willing to send some $$$ via paypal to whomever can get me back up and running! Thanks
Valgore said:
Hello all,
I've done a lot of googling and searching on these forums and I'm having no luck. Hopefully by asking I can get some headway.
I was attempting to restore to stock rom. At 17% of the process using LGFlashTool 1.8.6 the tool gave me an error 'Unable to Communicate with phone' after about 10 minutes of no progress. I exited the LGFlashTool program and ran it again and now it fails saying 'Cant' change to download mode". If I turn the phone off and then press Vol+ and plug in my cable it just goes to the Firmware Update screen. My phone *IS* detected properly in the device manager as LGE Andriod MTP Device and under ports as LGE Mobile USB Serial Port (COM41). If I go into recovery (Vol- and power) it asks if I want to do the restore - but it doesn't actually do anything once I say yes twice. Just sits at the firmware update screen at 0%.
I looked at this post (http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091) but it appears to be either for a different phone or different problem (showing in device manager as a bulk device - mine is not doing that). Frankly I don't want to make things worse (if that's possible)
Does anyone have a way that I can restore the download mode for this D852 phone? I'm hoping if I can get download mode to work again I can reflash the stock rom. I don't care about the data on the phone at this point.
I'm willing to send some $$$ via paypal to whomever can get me back up and running! Thanks
Click to expand...
Click to collapse
What happens when u just power up the phone ?
Thanks for the reply.
If I shut the phone down (by pulling battery) then plug it back in and just power it on, I get the LG logo then it goes to the firmware update screen with 'USER B84" in the box below the progress bar. Progress bar never moves. I get to this screen whether I start it in recovery (which is just the factory recov - looks like during the initial 17% it wiped out my TWRP), attempt to start it in download mode (I do not get the download mode screen with the blue dots anymore), or regularly by just holding the power button.
ok
Dont plug it into the computer and try to power it up what does ot do?
Same thing.
read this
http://forum.xda-developers.com/lg-g3/help/lg-g3-bricked-tried-everything-experts-t2852962 this might help
pacods61 said:
http://forum.xda-developers.com/lg-g3/help/lg-g3-bricked-tried-everything-experts-t2852962 this might help
Click to expand...
Click to collapse
Ok that didn't work for me but I did try the LGFlashTool using Board DL instead of Upgrade DL and it was moving a bit. Finally got to 10% and failed at 574 sec with the error "We can't communicate with Phone". I am using the cable that came with the phone. It isn't damaged or anything.
Here's what is shows in the LG Flashtool window (this is port 1 (com41)
Code:
PID: BS09S150309001007
IMEI: <myimei>
Model: D852
DLL: D852
BIN: <correct bin file from stock roms>
SWV: LGD852AT-01-V20C-302-720-FEB-04-(cuts off here can't read rest)
SWOV: LGD852AT-00-V20C-RGS-CA-FEB-04(cuts off here can't read rest)
Initializing
USB Connection Established
Start Download
LAF: Bin_User_Mode
PRIMARYGPT
MODEM
LAF:Bin_User_Mode
PRIMARYGPT
LAF:Bin_User_Mode
PRIMARYGPT
MODEM
[14: 7:28) We can't communicate with phone
00000064
On the phone it shows COM41 under the usb icon on under firmware update and 0% progress. In the box below it says:
Code:
F USER 50.0 A50.0 B70 UHS
S U LG-D852 04.4.2 Hrev_10
D85210b
D85210b
That's it. Should I leave the phone connected at this point or unplug it? Device still shown in device manager (have had it up beside the LG Flashtool window the whole time. I do see it refresh from time to time but the contents dont' seem to change at all.
Ok so I left this over night and when I checked the phone this morning it's different but I don't think it's good.
Looks like it proceeded but ended with:
FBOOT Check
FBOOT Complete Time [0s ] 1th try
Factory Reset Flag = 2
Factory Reset Flag Check Fail!!!
And my phone has a blue screen with Factory Reset Status and a big red '2'
Now what do I do?
Some further information.
If I run the LGFlashTool in Board DL action mode, it seems like the process works but I end up with the red 2 on the screen. But I don't get 'can't change to download mode' or 'cannot communicate with phone' errors.
However if I choose Upgrade DL action mode, then I get 'can't change to download mode' or cannot communicate with phone'. ARGH. What gives?
I have tried things like fresh restarts (restarting PC), restarting the LG FlashTool between attempts, not restarting flashtool, etc. I can't seem to find the sweet spot.
here
http://forum.xda-developers.com/sprint-lg-g3/help/fix-bricked-lg-g3-ls990-stuck-fastboot-t3084562 another tutorial to try
Thanks, but no dice.
I don't get fastboot options, and if i download and attempt to use fastboot, it shows no devices.
Also, when following the steps for the BOARD DL option in the lg flashtool, it goes through the process but I get no ATT screen. Nor do I get the option to tap OK or Normal - as soon as my device reboots after the flash, it gives me a MINI OS (iirc) screen with a bunch of vertical bars below it moving up and down then it changes to the Factory Reset screen with the number 2.
last one lol
http://androidforums.com/threads/ho...-2-lg-g3-d855-twn-32-gb-problem-fixed.911271/ i found one more that could help it said to use a jdz not a tot hope it helps if not sry
Thanks - I'm going to give this a try, however I can't finda .kdz file for my phone (canada/rogers D852 LG G3) - the links in that post that link to firmware is for a tot file. Does anyone have a link to the KDZ?
Hi, I'm having the exact same problem now, where the phone only boots to the Firmware Update screen. Did you manage to fix it?
Indeed.
I used the KDZ method pacods61 posted last, but I had trouble actually finding kdz firmware. With some help I finally managed to do so from here: http://devtester.ro/projects/lg-firmwares/country.php?country=Canada
Direct link for D852 Rogers Lolipop 5.0.1: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FWF448V332CPAKX8CEA4UCE/D85220g_00_1205.kdz
So yesterday i was browsing facebook on my phone when it suddenly freezes and i couldnt do anything so i took the bactery out. Now my phone wont boot it stuck on logo screen but this time not LED appears i dont see the LG logo moving i use to see a bright color thingy near it and this time no flashing LED i can enter twrp recovery but the internal storage becomes 0 and i cant flash a new rom because it gave me an error. I tried to enter download mode i thought it work it said download mode then for a few secs the screen just turn black and nothing. So this is basically hard bricked im guessing?
uoweme6 said:
So yesterday i was browsing facebook ...So this is basically hard bricked im guessing?
Click to expand...
Click to collapse
It's just the universe's way of telling you to stay off of facebook
You can tell if it is a hardbrick if your G3 shows up as something strange in the device manager of your PC like qualcomm 9006 or 9008 or something else under "ports" and will not be recognized as a phone. So check what your device manager on your computer says under "portable devices" and "ports", when you plug the phone in and you can tell if you're bricked or not.
For reference: when i'm in download mode(firmware update screen)on a healthy G3 my pc sees the phone as LGE Android MTP device under "potable devices", LGE Mobile for VZW USB serial port(com41) under "ports", and "LGE Mobile for VZW USB Composite Device" under USB controllers. (*Don't mind the VZW tags as that denotes it is for a Verizon phone.)
It's good you can get into recovery, but internal storage reading 0 in recovery is strange. What error do yo get when trying to flash something in recovery? Have you tried reflashing the TWRP recovery zip or .img file in your recovery? Have you tried a different/new battery(check the date code on the battery to see how old it is - if it's 2014 it's probably bad)? A bad battery can cause random shutdowns and bootloops, it could cause your phone to reboot while in download mode(which could be why you don't make it to the "firmware update" screen after it says "download mode"), but I doubt it would cause the recovery errors
Also, please include your G3 variant (D855, Vs985, etc.) and the ROM you were running when all of this happened. Someone may have experienced your issue before and it could be ROM/variant specific with an easy fix...if it's fixable and not a catastrophic hardware issue.
Best of luck to you getting it fixed :good:
yup it says qualcom 9008 thingy i might try to reflash an image and see what happens lol im planning to buy a new phone anyway so if it cant be fixed oh well idc XD. battery is from 2014 and its lg d855
Happened to me several times, phone get overheat then just refuse to turn on
In my case, I let it charge to 100% and if still not booting, reflash the ROM
I was clearing the sde partitions and my phone suddenly went blank and it is not starting any more.
if I plug it to the laptop it shows charging symbol and "press any key to shutdown" message on left top corner.
It is not getting detected as qualcom or anything it is not booting to bootloader. sometimes it is showing tmobile boot image.
Phone model XT1789-04
Please help , how can blankfash and get the bootloader back? how to go to EDL mode from here ?
latadswapnil said:
I was clearing the sde partitions and my phone suddenly went blank and it is not starting any more.
if I plug it to the laptop it shows charging symbol and "press any key to shutdown" message on left top corner.
It is not getting detected as qualcom or anything it is not booting to bootloader. sometimes it is showing tmobile boot image.
Phone model XT1789-04
Please help , how can blankfash and get the bootloader back? how to go to EDL mode from here ?
Click to expand...
Click to collapse
The phone is unbrickable unless the hardware issue.
Sent from my LG-LS997 using Tapatalk
cgigate said:
The phone is unbrickable unless the hardware issue.
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
Can you please suggest a way to get into bootloader ? because currently whenever I switch on phone it shows tmobile logo(boot screen) and nothing happens and there is a message in left top corner "press any key to shutdown" . I tried to switch it on with volume down and power key but nothing happens blank screen.
Also it is not getting detected on my laptop not even as unknown device.
latadswapnil said:
Can you please suggest a way to get into bootloader ? because currently whenever I switch on phone it shows tmobile logo(boot screen) and nothing happens and there is a message in left top corner "press any key to shutdown" . I tried to switch it on with volume down and power key but nothing happens blank screen.
Also it is not getting detected on my laptop not even as unknown device.
Click to expand...
Click to collapse
Have you tried holding vol up and pwr to boot into bootloader?
41rw4lk said:
Have you tried holding vol up and pwr to boot into bootloader?
Click to expand...
Click to collapse
Yes I did try that and it only shows the Tmobile boot screen and "press any key to shutdown" on left top of screen as attached in the picture. :crying:
latadswapnil said:
Yes I did try that and it only shows the Tmobile boot screen and "press any key to shutdown" on left top of screen as attached in the picture. :crying:
Click to expand...
Click to collapse
Make sure you're using a 2.0 port from your mobo, not a hub and not a 3.0+ port.
Unplug your phone and try entering these commands one at a time, you might need to unplug before each command.
This all depends on whether you had your bootloader unlocked, adb enabled, etc. You put yourself in a weird state.
Unplug, open cmd prompt and enter
fastboot reboot bootloader it should say waiting for device
plug in your phone and hopefully it'll get you there. If not, repeat above and try
adb reboot bootloader
following the same procedure
fastboot reboot recovery
like above
adb reboot recovery
Hopefully one of those will get you somewhere where you can try to reflash the phone, factory reset, whatever it takes.
Since your pc doesn't recognize your device... who knows.
Last resort
Fastboot oem blankflash
If that works you should be ready to blankflash
41rw4lk said:
Make sure you're using a 2.0 port from your mobo, not a hub and not a 3.0+ port.
Unplug your phone and try entering these commands one at a time, you might need to unplug before each command.
This all depends on whether you had your bootloader unlocked, adb enabled, etc. You put yourself in a weird state.
Unplug, open cmd prompt and enter
fastboot reboot bootloader it should say waiting for device
plug in your phone and hopefully it'll get you there. If not, repeat above and try
adb reboot bootloader
following the same procedure
fastboot reboot recovery
like above
adb reboot recovery
Hopefully one of those will get you somewhere where you can try to reflash the phone, factory reset, whatever it takes.
Since your pc doesn't recognize your device... who knows.
Last resort
Fastboot oem blankflash
If that works you should be ready to blankflash
Click to expand...
Click to collapse
Yes bootloader was unlocked and adb was enabled also phone was rooted.
I am trying what you have suggested but its not working till now. I tried on USB 2.0 ports and 3.0 as well but nothing happens. neither blankflash executes nor any of fastboot or adb commands executes.
will linux OS help ?
latadswapnil said:
Yes bootloader was unlocked and adb was enabled also phone was rooted.
I am trying what you have suggested but its not working till now. I tried on USB 2.0 ports and 3.0 as well but nothing happens. neither blankflash executes nor any of fastboot or adb commands executes.
will linux OS help ?
Click to expand...
Click to collapse
Never hurts to try, the thing is your phone is in some limbo state and your pc doesn't doesn't see it. I can't imagine that linux will help much. Have you tried holding the power button for a minute or so? I don't know what the sde partition is honestly, but obviously you shouldn't have messed with it. What lead you to that partition and what exactly did you do?
You might uninstall your moto drivers, adb drivers, and fastboot drivers and see if plugging your phone in will detect on your pc as new hardware. Might try installing qualcomm diag drivers to see it it will recognize your phone. I afraid that until your pc sees it, any command is pointless since it can't communicate with your phone.
41rw4lk said:
Never hurts to try, the thing is your phone is in some limbo state and your pc doesn't doesn't see it. I can't imagine that linux will help much. Have you tried holding the power button for a minute or so? I don't know what the sde partition is honestly, but obviously you shouldn't have messed with it. What lead you to that partition and what exactly did you do?
You might uninstall your moto drivers, adb drivers, and fastboot drivers and see if plugging your phone in will detect on your pc as new hardware. Might try installing qualcomm diag drivers to see it it will recognize your phone. I afraid that until your pc sees it, any command is pointless since it can't communicate with your phone.
Click to expand...
Click to collapse
SDE are mobile partitions and I was trying to delete modem partitions as I had installed pie modem on my device and I might have accidentally deleted the bootloader partition or something like that.
after holding power button for a minute nothing happens same screen appears and disappears as I have attached in my previous reply.
is there a button combination which can direct this device in edl mode?
laptop is not reading my device yet, I tried different laptops different ports and different cables. linux is also not reading the device.
please let me know if you know any way I can boot this in edl mode to blankflash. I tried that cable way green and black cable short thats not working either on this device.
latadswapnil said:
SDE are mobile partitions and I was trying to delete modem partitions as I had installed pie modem on my device and I might have accidentally deleted the bootloader partition or something like that.
after holding power button for a minute nothing happens same screen appears and disappears as I have attached in my previous reply.
is there a button combination which can direct this device in edl mode?
laptop is not reading my device yet, I tried different laptops different ports and different cables. linux is also not reading the device.
please let me know if you know any way I can boot this in edl mode to blankflash. I tried that cable way green and black cable short thats not working either on this device.
Click to expand...
Click to collapse
There is no key combo as far as I know to enter edl mode on this phone, and most likely it wouldn't solve your problem. You flashed pie modems on a TMO device, that has been done before and no one has been able to recover from that. Even if you were to somehow get your phone booting, you wouldn't have a baseband or any cell service.
41rw4lk said:
There is no key combo as far as I know to enter edl mode on this phone, and most likely it wouldn't solve your problem. You flashed pie modems on a TMO device, that has been done before and no one has been able to recover from that. Even if you were to somehow get your phone booting, you wouldn't have a baseband or any cell service.
Click to expand...
Click to collapse
While if the OP is correct, and the problem is that they replaced their bootloader, then that's exactly what edl mode is for. However, you're definitely right that there's no key combination. I've been trying to get my moto into edl for days. I even got the battery to die. It just makes other diagnostics more annoying when I need to charge. So far, from what I can tell, the MSM8998 in a Z2 force first of all plays by different rules, uses a different programmer, and is generally not going to respond to the stock "qualcomm unbrick" tutorials. If it gets into edl, then you might be able to blankflash. But I guess keep trying different things, from what I've read the drivers and usb ports are finicky even with phones where this is known to work. It is not known to work with TX1789, at least not with the ease it works in other snapdragon phones. It's actually a massive security vulnerability (if it works it allows arbitrary read/write from the lowest level of the chain of trust, bypassing most security by default. It's a total backdoor), it's just unfortunate we're on that side of the fence. It doesn't have to be that way, but it was designed to see all unsigned software as equally malicious.
latadswapnil said:
I was clearing the sde partitions and my phone suddenly went blank and it is not starting any more.
if I plug it to the laptop it shows charging symbol and "press any key to shutdown" message on left top corner.
It is not getting detected as qualcom or anything it is not booting to bootloader. sometimes it is showing tmobile boot image.
Phone model XT1789-04
Please help , how can blankfash and get the bootloader back? how to go to EDL mode from here ?
Click to expand...
Click to collapse
Does anybody have any new suggestion how I can get into EDL mode?
my phone is still stuck on to the screen where it says press any key to shutdown. It doesn't get detected at all on any USB port or with different cables.
Does anybody know if there are any EDL short points on motherboard or deep flashing cable?
although I tried cutting regular USB C cable for trying to short the two cables and force put it in edl mode but nothing worked yet.
If anybody has any suggestion please throw some light.
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