My phone's screen was broken, I could only use my phone with some tools like screenshot. Today before I was about to repair the phone, I wiped all the things (including system, I don't know what I was thinking about, I thought I was doing a factory reset) in TWRP recovery. So now the thing is tricky. I cannot boot my phone, and I don't know what is going on there because the screen is broken. I connected my phone to PC, and after typing "adb devices", I saw that device was offline(but at least there was a device listed, though it was offline instead of attched).
So I cannot use adb, I tried 4.4.3 stock RUU, but it said that "ERROR 170 USB CONNECTION ERROR". I've installed HTC Sync Manager, it couldn't detect my phone, either.
I cannot enter the recovery, either. I don't know what to do now. Wonder if anybody here could help me. Any help appreciated.:crying:
mycityofsky said:
My phone's screen was broken, I could only use my phone with some tools like screenshot. Today before I was about to repair the phone, I wiped all the things (including system, I don't know what I was thinking about, I thought I was doing a factory reset) in TWRP recovery. So now the thing is tricky. I cannot boot my phone, and I don't know what is going on there because the screen is broken. I connected my phone to PC, and after typing "adb devices", I saw that device was offline(but at least there was a device listed, though it was offline instead of attched).
So I cannot use adb, I tried 4.4.3 stock RUU, but it said that "ERROR 170 USB CONNECTION ERROR". I've installed HTC Sync Manager, it couldn't detect my phone, either.
I cannot enter the recovery, either. I don't know what to do now. Wonder if anybody here could help me. Any help appreciated.:crying:
Click to expand...
Click to collapse
Finally it worked, I kept pressing volume up and power button to reboot to fastboot, then pressed volume down and power in order to recovery, now RUU worked just fine. Cheers!
I have just flash the custom 5.0.2 ROM using philz touch 6.48.4.
After I flashed the ROM, I reboot to the philz recovery and flashed back to cwm 6.0.4.8.
However, the device stuck on the LG logo screen.
I have try to enter Download mode/Emergence mode/Hard reset mode/Recovery, but all of them I cannot go into.
Please help! Thank you for your helping!!
pchuen said:
I have just flash the custom 5.0.2 ROM using philz touch 6.48.4.
After I flashed the ROM, I reboot to the philz recovery and flashed back to cwm 6.0.4.8.
However, the device stuck on the LG logo screen.
I have try to enter Download mode/Emergence mode/Hard reset mode/Recovery, but all of them I cannot go into.
Please help! Thank you for your helping!!
Click to expand...
Click to collapse
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
hawkwind212 said:
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
Click to expand...
Click to collapse
Thank you for replying.
I cannot do anythings since I cannot enter into download mode.
I pressed volume key + and - and insert the usb cable to computer. There is nothing happened, computer dose not show the devices attached and the phone stay in the LG logo screen.
Also, I cannot use adb commands to force the phone enters into download mode as it shows nothings under "List of devices".
Is there any methods I can go into the download mode???
Thank you!
pchuen said:
Thank you for replying.
I cannot do anythings since I cannot enter into download mode.
I pressed volume key + and - and insert the usb cable to computer. There is nothing happened, computer dose not show the devices attached and the phone stay in the LG logo screen.
Also, I cannot use adb commands to force the phone enters into download mode as it shows nothings under "List of devices".
Is there any methods I can go into the download mode???
Thank you!
Click to expand...
Click to collapse
If your phone shows LG start screen, it should go into Download mode. I had similar problem few days ago while I was testing some kernel patches, it just froze on the LG screen. Solution was to unplug it, remove it's battery, SIM & SD (you don't have to remove SIM & SD, I just work that way) , make sure it's off, return battery back, press Vol + & Vol - at the same time and plug-in the USB cable.
Before that, make sure you have installed LG Unified driver (can be obtained via LG's software from support site), because without that Windows won't recognise your device.
After that, once you make your phone usable with Freegee/whatever you use to install initial recovery, flash official TWRP, because others are too old - that Philz CWM is old but still working with Lollipop but not work good and is tends to lock itself into a bootloop if you use hardware keys to enter; that other one, from GPRO_recovery APK is not supported and not working well (for me since day one), so it should be replaced as soon as possible.
Also, I can suggest you to flash your phone from stock 4.1 (not KitKat), root, flash recovery via freegee and after reboot update to latest official TWRP via Flashify.
hawkwind212 said:
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
Click to expand...
Click to collapse
ShadySquirrel said:
If your phone shows LG start screen, it should go into Download mode. I had similar problem few days ago while I was testing some kernel patches, it just froze on the LG screen. Solution was to unplug it, remove it's battery, SIM & SD (you don't have to remove SIM & SD, I just work that way) , make sure it's off, return battery back, press Vol + & Vol - at the same time and plug-in the USB cable.
Before that, make sure you have installed LG Unified driver (can be obtained via LG's software from support site), because without that Windows won't recognise your device.
After that, once you make your phone usable with Freegee/whatever you use to install initial recovery, flash official TWRP, because others are too old - that Philz CWM is old but still working with Lollipop but not work good and is tends to lock itself into a bootloop if you use hardware keys to enter; that other one, from GPRO_recovery APK is not supported and not working well (for me since day one), so it should be replaced as soon as possible.
Also, I can suggest you to flash your phone from stock 4.1 (not KitKat), root, flash recovery via freegee and after reboot update to latest official TWRP via Flashify.
Click to expand...
Click to collapse
Thank you for your detail reply.
I have tried to reinstall the LG driver and try to enter download mode again.
The screen is still stuck on LG logo and I cannot find the device in hardware manager (cannot recognize it).
I cannot do anythings until it can recognize it.
(Is it the bootloader is broken? and can I fix it?)
Thank you very much and waiting for your reply soon.:good:
pchuen said:
Thank you for your detail reply.
I have tried to reinstall the LG driver and try to enter download mode again.
The screen is still stuck on LG logo and I cannot find the device in hardware manager (cannot recognize it).
I cannot do anythings until it can recognize it.
(Is it the bootloader is broken? and can I fix it?)
Thank you very much and waiting for your reply soon.:good:
Click to expand...
Click to collapse
Which version of Windows are you using? It should be displayed under Serial ports in Device manager (named something like LGE Serial device) and LGFlashTool should recognise it immediately. I can't make you a screenshot/check for real name because I'm running Linux right now and can't reboot.
Also, try with another cable/port, remove all other android drivers you may have (Samsung's, Google's...) and disable antivirus.
ShadySquirrel said:
Which version of Windows are you using? It should be displayed under Serial ports in Device manager (named something like LGE Serial device) and LGFlashTool should recognise it immediately. I can't make you a screenshot/check for real name because I'm running Linux right now and can't reboot.
Also, try with another cable/port, remove all other android drivers you may have (Samsung's, Google's...) and disable antivirus.
Click to expand...
Click to collapse
It does not work on Windows 7 and XP.
I did not find any LGE XXX under Serial ports part.
Thank you!
pchuen said:
It does not work on Windows 7 and XP.
I did not find any LGE XXX under Serial ports part.
Thank you!
Click to expand...
Click to collapse
Hm.... Phone shows that it have entered download mode? Black screen, centered gray message and "DOWNLOAD MODE" red text?
ShadySquirrel said:
Hm.... Phone shows that it have entered download mode? Black screen, centered gray message and "DOWNLOAD MODE" red text?
Click to expand...
Click to collapse
No... nothing happens, just showing LG logo...
pchuen said:
No... nothing happens, just showing LG logo...
Click to expand...
Click to collapse
OK, it doesn't enter download mode. So, step by step:
- remove battery and leave it for 15-30 seconds, return battery
- press Vol+ and Vol- at the same time and keep them pressed,
- plug USB cable in while keys are pressed
It should immediately put you into download mode, with no LG screen, just black screen with gray box and red text I've described to you.
ShadySquirrel said:
OK, it doesn't enter download mode. So, step by step:
- remove battery and leave it for 15-30 seconds,
- press Vol+ and Vol- at the same time and keep them pressed,
- plug USB cable in while keys are pressed
It should immediately put you into download mode, with no LG screen, just black screen with gray box and red text I've described to you.
Click to expand...
Click to collapse
I understand what download mode screen is.
I followed your methods, bur I still cannot enter it and the computer cannot recognize that.
Sorry for disturbing :crying:
pchuen said:
I understand what download mode screen is.
I followed your methods, bur I still cannot enter it and the computer cannot recognize that.
Sorry for disturbing :crying:
Click to expand...
Click to collapse
So, whatever you try to do, phone just shows LG logo, not even a message in an upper left corner?
I'm running out of ideas. I have exact same variant (E988) but only time it didn't want to enter download mode this way was when cable I was using was broken...
ShadySquirrel said:
So, whatever you try to do, phone just shows LG logo, not even a message in an upper left corner?
I'm running out of ideas. I have exact same variant (E988) but only time it didn't want to enter download mode this way was when cable I was using was broken...
Click to expand...
Click to collapse
I have changed the cable, but it is the same.
So I soft bricked my LG G Pad II 8.0 Tablet... Not the worst thing in the world, except that 1.) There seems to be not much at all on the internet as far as stock ROMs or how to guides on fixing my particular tablet. 2.) My computer does not seem to be recognizing my tablet when trying to use ADB, despite having installed all the drivers etc.
My device is stuck in a BootLoop, it will allow me to try a Hard Reset, which is unsuccessful. But it will not go into recovery mode OR Download mode no matter what sequence of the buttons I push and i've scoured the internet trying different button sequences.
My Tablet will charge when plugged into USB, my comp will also go *ding* when i press the power button with the tablet plugged in as if it is reconginzing it and everything. Also Device Manager seems to have it listed with no Exclamation Point or any sign of trouble... Just when I go to use ADB and i search for the device it says *error no device found*
The Tablet just sits there with the LG Logo screen pissing me off more and more as my attempts fail.
I will say USB debugging was not enabled beforehand *cough cough* my mistake
Will reflashing it work by using the MicroSD card method? If that is the only way i will have to just buy one i guess. It did not come with it and it is a Wifi only tablet, no carrier attached.
And if I try the MicroSD method, will it still work without being able to put the tablet into recovery mode?
I believe I have the correct .IMG file for my stock ROM... I just can't seem to get anywhere with flashing it to the device at this point.......
Please Help!
bbrumley said:
So I soft bricked my LG G Pad II 8.0 Tablet... Not the worst thing in the world, except that 1.) There seems to be not much at all on the internet as far as stock ROMs or how to guides on fixing my particular tablet. 2.) My computer does not seem to be recognizing my tablet when trying to use ADB, despite having installed all the drivers etc.
My device is stuck in a BootLoop, it will allow me to try a Hard Reset, which is unsuccessful. But it will not go into recovery mode OR Download mode no matter what sequence of the buttons I push and i've scoured the internet trying different button sequences.
My Tablet will charge when plugged into USB, my comp will also go *ding* when i press the power button with the tablet plugged in as if it is reconginzing it and everything. Also Device Manager seems to have it listed with no Exclamation Point or any sign of trouble... Just when I go to use ADB and i search for the device it says *error no device found*
The Tablet just sits there with the LG Logo screen pissing me off more and more as my attempts fail.
I will say USB debugging was not enabled beforehand *cough cough* my mistake
Will reflashing it work by using the MicroSD card method? If that is the only way i will have to just buy one i guess. It did not come with it and it is a Wifi only tablet, no carrier attached.
And if I try the MicroSD method, will it still work without being able to put the tablet into recovery mode?
I believe I have the correct .IMG file for my stock ROM... I just can't seem to get anywhere with flashing it to the device at this point.......
Please Help!
Click to expand...
Click to collapse
*UPDATE* So I happened to stumble upon a random piece of information that proved REALLY useful in this situation. Someone put in a forum that Lollipop ONLY is detected when plugged into USB 2.0 ports NOT USB 3.0 ports like I was using. So I did this and was able to make my tablet enter into Download Mode FINALLY.... Anyone have any good methods on how to Flash Stock ROM using ADB and a connected soft bricked tablet?
I have already tried a couple methods that I have found and they were unsuccessful. One was using ODIN software and the other was using LG Flash Tool, unfortunately neither worked....
Dear xda-developers-community,
I'm trying to get a phone of a friend of mine working which just reboots whenever the phone is started. The resulting boot loop can only be interrupted by taking the battery out or wait until it is depleeted.
In order to fix this soft-brick I first tried to use recovery by pressing VOL - & POWER. In the menu, I could select and confirm to recover to factory settings, but after some seconds the boot loop appeared again with (seemingly?) no change having been made. The error kept appeaing over and over again.
After trying recovery mode, I attempted to start the phone in download mode by pressing VOL + on the (switched off) phone and connecting a USB cable. The respective menu also opened, here, showing "Firmware Update" and "Do not unplug the USB connection until the process is complete". According to many tutorials I found on the internet, when having installed the required drivers (I used LG United Mobile drivers from here), this procedure should allow you to flash a recovery image through LG's flashing tool (which one can also find on that page).
However, when I connect the LG G3 (D855) to a computer the driver is installed on, there is no new device shown in the Device manager. I tried this out with Windows 10 x64 and Windows 7 x64 and disabled driver validation on both systems and enabled test signing on Windows 10, respectively. Additionally, I followed these instructions, but in this case the screen stays dark and the device is not detected either. It seems like there are not so many people experiencing this error, but I hope we can find a solution.
nVentis said:
Dear xda-developers-community,
I'm trying to get a phone of a friend of mine working which just reboots whenever the phone is started. The resulting boot loop can only be interrupted by taking the battery out or wait until it is depleeted.
Click to expand...
Click to collapse
This may sound like a dumb question, but have you tried a new battery yet? If it is one of the original batteries it could have gone bad & started bootlooping...like mine did a few months ago.
As far as the PC not recognizing the phone you can try downloading USBDeview and uninstall anything that has the vendor ID's of 1004 & 18d1(pretty much anything that says android or LGE in the description) & reboot the PC. Hopefully it'll recognize your device and install the drivers the next time you plug it in. If it doesn't find the drivers automatically for you then install LG drivers manually.
Link for usbdeview: http://www.nirsoft.net/utils/usb_devices_view.html
Link for LGE drivers: http://www.lg.com/us/support/software-firmware-drivers
Good luck :fingers-crossed:
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