Related
Hello. I just tried to unlock the bootloader on on Verizon Galaxy nexus. Now it's stuck at the bootscreen with the lock image. I did a search and couldn't find a exact answer for my issue. I hope I haven't bricked my phone. Anyway, any help would be appreciated.
I wasn't trying to root just unlock the bootloader. It appeared everything went ok but, now I'm stuck. I used the same method for unlocking the bootloader on my GSM G-nex and it worked.
I know I've done something wrong or this may be something simple. I just need help so I can use my phone.
are you able to boot into the bootloader? if so you should be able to recover and can't worry a little less.
same thing here... I posted a request for a LTE boot.img since can still get into the bootloader
Goat_For_Sale said:
are you able to boot into the bootloader? if so you should be able to recover and can't worry a little less.
Click to expand...
Click to collapse
No I don't believe I can. When I type fastboot it just says "waiting on device" I can hold the volume down & power buttons and get to the screen were it says "start" at the top and below that "downloding"
Yea, that was what I was eluding too, The device just came out and google released the GSM image. I am sure that it will appear online in the near future.
if you are able to get into the bootloader does it say that its unlocked ? is your google splash screen showing the unlocked padlock ? you could also try fastboot flash recovery to get cwm on there and provide additional potential solutions.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
qnet said:
No I don't believe I can. When I type fastboot it just says "waiting on device" I can hold the volume down & power buttons and get to the screen were it says "start" at the top and below that "downloding"
Click to expand...
Click to collapse
That is download mode used for odin.
hold BOTH volumn buttons and power to get into the bootloader/fastboot
Goat_For_Sale said:
Yea, that was what I was eluding too, The device just came out and google released the GSM image. I am sure that it will appear online in the near future.
if you are able to get into the bootloader does it say that its unlocked ? is your google splash screen showing the unlocked padlock ? you could also try fastboot flash recovery to get cwm on there and provide additional potential solutions.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
That is download mode used for odin.
hold BOTH volumn buttons and power to get into the bootloader/fastboot
Click to expand...
Click to collapse
Yeah, when I did the procedure it said that it was unlocked. Everything looked ok , it booted show the unlock symbol under Google. It then went to the colorful animation and was stuck there. At that time I pulled the battery and, it's been stuck at the screen showing google and the unlock image.
qnet said:
Yeah, when I did the procedure it said that it was unlocked. Everything looked ok , it booted show the unlock symbol under Google. It then went to the colorful animation and was stuck there. At that time I pulled the battery and, it's been stuck at the screen showing google and the unlock image.
Click to expand...
Click to collapse
you should have let the animation run for like 10 minutes the phone has to rebuild the first boot can take like 15 minutes sometimes.
try booting into the bootloader see if that works still
Sorry I wasn't paying attention and didn't read the part were you told me how to get to the fastboot screen. I'm there now. Can I just relock or fix the bootloader from problem there? It shows it unlocked at the fastboot screen.
qnet said:
Sorry I wasn't paying attention and didn't read the part were you told me how to get to the fastboot screen. I'm there now. Can I just relock or fix the bootloader from problem there? It shows it unlocked at the fastboot screen.
Click to expand...
Click to collapse
you could try fastboot oem lock and see if that works but if the phone wasn't booting i don't know if that will fix it but worth a shot.
try it out and see. it shouldn't do any harm to try
I had the issue with the failure to boot up after doing the fastboot oem unlock (I had to use the pda net drivers to get my device recognized to get even that far). I did a lot of things like pulling the battery, locking again and then unlocking and nothing worked until I went here http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-adb-method/, then downloaded the files following their directions and doing the fastboot boot boot.img command. It took a LONG time to boot up, but it did boot finally.
GirLuvsDroid said:
I had the issue with the failure to boot up after doing the fastboot oem unlock (I had to use the pda net drivers to get my device recognized to get even that far). I did a lot of things like pulling the battery, locking again and then unlocking and nothing worked until I went here http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-adb-method/, then downloaded the files following their directions and doing the fastboot boot boot.img command. It took a LONG time to boot up, but it did boot finally.
Click to expand...
Click to collapse
Thank you, I'll try that.
I have another question. One of the selections on the fastboot screen is recovery mode. Can I try that or is this something were you have to have a rom stored on a sd-card?
qnet said:
I have another question. One of the selections on the fastboot screen is recovery mode. Can I try that or is this something were you have to have a rom stored on a sd-card?
Click to expand...
Click to collapse
you could download the recovery image from
http://forum.xda-developers.com/showthread.php?t=1392336
then when connected in fast boot flash it with
fastboot flash recovery recovery.img
(rename the file from the linked thread to recovery.img)
this should write your custom recovery partition.
once you have that though you are still not going to be able to boot but it would allow you to flash a nandroid backup if someone made one for you or a LTE based rom
EDIT: you could also try a factory data reset and wipe dalvk cache from withing cwm. that may fix your boot problem
I had this problem, too.
I downloaded Clockwork Recovery and used 'fastboot boot LTErecovery_cwr.img' to boot into it, I wiped data and cache / factory reset and then rebooted. It rebooted twice, but after ten minutes or so I was back to the ICS Welcome screen. All of the files I'd put on my internal storage were wiped (during the oem unlock, I assume) but I'm in the stock rom but Superuser was installed and I have root access.
Hope it helps.
EDIT: looks like this is the same thing Goat_For_Sale posted above, but his command flashes CWM where mine temporarily boots into it. Since most of us will be installing CWM anyway I'd recommend using his command instead.
mixedlemon said:
I had this problem, too.
I downloaded Clockwork Recovery and used 'fastboot boot LTErecovery_cwr.img' to boot into it, I wiped data and cache / factory reset and then rebooted. It rebooted twice, but after ten minutes or so I was back to the ICS Welcome screen.
Hope it helps.
Click to expand...
Click to collapse
where did you get the lterecovery_cwr.img ? could you link to it please
I linked to the thread in my post, but here's a link to the mediafire upload from that thread: http://www.mediafire.com/?mdf0mtacskob5yg
mixedlemon said:
I linked to the thread in my post, but here's a link to the mediafire upload from that thread: http://www.mediafire.com/?mdf0mtacskob5yg
Click to expand...
Click to collapse
Thanks, my bad I didn't realize you were refering to the recovery image, thought it was the boot image for the LTE device.
Goat_For_Sale said:
Thanks, my bad I didn't realize you were refering to the recovery image, thought it was the boot image for the LTE device.
Click to expand...
Click to collapse
Ahh no problem.
I got pretty worried for a second that I'd already broke my shiny new Nexus, so I'm really hoping I can help out someone else that had the same problem.
Solved
I believe it's fixed now. I use the method that GirLuvsDroid posted from the Rootzwiki forum. Once it rebooted, I stopped there and didn't root the phone. I was just happy to get it booted.
It's downloading all my apps and settings now. Thanks to everyone who tried to help me, I really appreciate. This was a good learning experience for me.
qnet said:
I believe it's fixed now. I use the method that GirLuvsDroid posted from the Rootzwiki forum. Once it rebooted, I stopped there and didn't root the phone. I was just happy to get it booted.
It's downloading all my apps and settings now. Thanks to everyone who tried to help me, I really appreciate. This was a good learning experience for me.
Click to expand...
Click to collapse
So you were just able to go through the Rootzwiki method? Were you stuck at "Downloading...Do not turn off target !!" screen when you went to boot screen originally? My device still can't be detected :/
Hi Guys!
Today I was getting to rooting the device, until I ran into a problem
I accidentally flashed Android KK aboot and the rest on Android L versions.
The result was inability to boot ANYTHING (System/Download/Recovery)
It also showed an error message saying to following
ERROR : boot certification verify
[630]-----------------------------------------------
[630]
[630] Secure booting Error!
[630] Cause : boot certification verify
[630]
[630]-----------------------------------------------
Shortly following that is a black screen with red and blue flashing LED. (Vol. Down leads to restart and Vol.Up seems to stop the flashing, however still on black screen)
Is it possible for me to get out of this problem? Or have I hard bricked my phone?
Its bricked, there is a version mismatch between your android bootloader and your phone's bootloader meaning that it prevents you from going into download or recovery mode
KuHaKu said:
Hi Guys!
Today I was getting to rooting the device, until I ran into a problem
I accidentally flashed Android KK aboot and the rest on Android L versions.
The result was inability to boot ANYTHING (System/Download/Recovery)
It also showed an error message saying to following
ERROR : boot certification verify
[630]-----------------------------------------------
[630]
[630] Secure booting Error!
[630] Cause : boot certification verify
[630]
[630]-----------------------------------------------
Shortly following that is a black screen with red and blue flashing LED. (Vol. Down leads to restart and Vol.Up seems to stop the flashing, however still on black screen)
Is it possible for me to get out of this problem? Or have I hard bricked my phone?
Click to expand...
Click to collapse
I HAVE YOUR SOLUTION flash this patched boot img which is used for phones when you downgrade the aboot and laf to kk to get twrp working http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
Quote100 said:
I HAVE YOUR SOLUTION flash this patched boot img which is used for phones when you downgrade the aboot and laf to kk to get twrp working http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
Click to expand...
Click to collapse
If you bothered to read properly he cant boot anything
itsbighead said:
If you bothered to read properly he cant boot anything
Click to expand...
Click to collapse
if you bothered to android properly he doesn't need to boot into anything if the computer can recognize it
---------- Post added at 01:45 PM ---------- Previous post was at 01:41 PM ----------
Also ever since i flashed twrp on mine, whenever i click reboot my phone doesn't reboot and i just get a black screen with no led and i have to remove the battery for it to boot again. I'm not sure if this will work in your situation but it couldn't hurt to try
Quote100 said:
if you bothered to android properly he doesn't need to boot into anything if the computer can recognize it
---------- Post added at 01:45 PM ---------- Previous post was at 01:41 PM ----------
Also ever since i flashed twrp on mine, whenever i click reboot my phone doesn't reboot and i just get a black screen with no led and i have to remove the battery for it to boot again. I'm not sure if this will work in your situation but it couldn't hurt to try
Click to expand...
Click to collapse
itsbighead said:
If you bothered to read properly he cant boot anything
Click to expand...
Click to collapse
Yep, I cannot get my computer to recognize my phone in anyway (i tried going into TWRP and Download) and both did not work.
Any ideas?
KuHaKu said:
Yep, I cannot get my computer to recognize my phone in anyway (i tried going into TWRP and Download) and both did not work.
Any ideas?
Click to expand...
Click to collapse
did you try to boot into the factory reset mode? (hold volume down and power to turn it on and stop when you see the lg logo and then hold them again after stopping)
Quote100 said:
did you try to boot into the factory reset mode? (hold volume down and power to turn it on and stop when you see the lg logo and then hold them again after stopping)
Click to expand...
Click to collapse
That would be what i would of noted as TWRP or Recovery - No
KuHaKu said:
That would be what i would of noted as TWRP or Recovery - No
Click to expand...
Click to collapse
ah i have no idea then you might just have a permanent brick but i have one last idea that may or may not help, (probably not) you said you stop the flashing by pushing the volume up button im not at all sure what that mode is supposed to be but does the computer recognize it in that mode?
FIXED
I have a solution to your problem..
Heres a solution to your problem... http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
brick
it bricks bro
Quote100 said:
ah i have no idea then you might just have a permanent brick but i have one last idea that may or may not help, (probably not) you said you stop the flashing by pushing the volume up button im not at all sure what that mode is supposed to be but does the computer recognize it in that mode?
Click to expand...
Click to collapse
BINGO!
Currently working on finding a way of throwing over the system, but other than that, i got my computer to recognize it, if any progress is made, I'll post it here .
THX TO QUOTE100 ))))
Celly624 said:
I have a solution to your problem..
Heres a solution to your problem... http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Click to expand...
Click to collapse
Fastboot doesnt work for any variant with a locked bootloader
OP can try the old LG Flash Tool guide but i doubt that will work
KuHaKu said:
BINGO!
Currently working on finding a way of throwing over the system, but other than that, i got my computer to recognize it, if any progress is made, I'll post it here .
THX TO QUOTE100 ))))
Click to expand...
Click to collapse
Alright! that's great, glad i could help
Please help urgently! So I just S-OFF'd my phone (right after unlocking my bootloader via htcdev) and I was excited to finally manually flash a 5.1 update to my EE UK One m9. I sort of made it a European version by changing one of its update numbers to [BLANK].401.[BLANK]. I then spent the whole night booting my phone into download mode and using fastboot commands: "htc_fastboot flash zip...".
Each zip was the previous update to the other, I.e. I was already on 1.32.401.6, so I used fastboot to get to 1.32.401.8 as the cmd. prompt said that it was successfully installed on my phone (p.s. I didn't have an sd card big enough to exfat 32 and put the update zips on it). I then repeated the steps again, but then fastboot flashed "2.10.401.", this was the update that would hopefully bring my phone to 5.1 . The cmd. prompt said that it was a success so I booted my phone up as normal, but I went to the settings to check software information and it was still on 1.32.401.6! It then said an update was ready to install so I just installed it as normal. Once it went into the bootloader it flashed it without any problems and tried to boot back up again. It then lit up a blue screen for 10 seconds and then went into the black HTC RUU screen with the grey htc logo. My phone has now, for the last hour, been stuck in this infinite loop of blue screen, vibrate, ruu screen and REPEAT. I've tried pressing vol. down and power as well as up to get into other modes like download mode, but it doesn't work. I CAN'T EVEN TURN IT OFF! I HAVE TO WAIT FOR IT TO RUN OUT OF BATTERY! MORE IMPORTANTLY, ADB DOESNT RECOGNISE IT, NOR DOES FASTBOOT!!!! SO I CAN'T EVEN FLASH A STOCK RECOVERY, SYSTEM IMG, ETC! PLEASE IF ANYONE CAN, HELP ME. I REALLY DON'T WANT TO HAVE TO BUY A NEW ONE AND PAY S-OFF AGAIN!
Louis118 said:
Please help urgently! So I just S-OFF'd my phone and I was excited to finally manually flash a 5.1 update to my EE UK One m9. I sort of made it a European version by changing one of its update numbers to [BLANK].401.[BLANK]. I then spent the whole night booting my phone into download mode and using fastboot commands: "htc_fastboot flash zip...".
Each zip was the previous update to the other, I.e. I was already on 1.32.401.6, so I used fastboot to get to 1.32.401.8 as the cmd. prompt said that it was successfully installed on my phone (p.s. I didn't have an sd card big enough to exfat 32 and put the update zips on it). I then repeated the steps again, but then fastboot flashed "2.10.401.", this was the update that would hopefully bring my phone to 5.1 . The cmd. prompt said that it was a success so I booted my phone up as normal, but I went to the settings to check software information and it was still on 1.32.401.6! It then said an update was ready to install so I just installed it as normal. Once it went into the bootloader it flashed it without any problems and tried to boot back up again. It then lit up a blue screen for 10 seconds and then went into the black HTC RUU screen with the grey htc logo. My phone has now, for the last hour, been stuck in this infinite loop of blue screen, vibrate, ruu screen and REPEAT. I've tried pressing vol. down and power as well as up to get into other modes like download mode, but it doesn't work. I CAN'T EVEN TURN IT OFF! I HAVE TO WAIT FOR IT TO RUN OUT OF BATTERY! MORE IMPORTANTLY, ADB DOESNT RECOGNISE IT, NOR DOES FASTBOOT!!!! SO I CAN'T EVEN FLASH A STOCK RECOVERY, SYSTEM IMG, ETC! PLEASE IF ANYONE CAN, HELP ME. I REALLY DON'T WANT TO HAVE TO BUY A NEW ONE AND PAY S-OFF AGAIN!
Click to expand...
Click to collapse
hold power and vol up and vol down all at the same time will get you to bootloader, we hope
Aldo101t said:
hold power and vol up and vol down all at the same time will get you to bootloader, we hope
Click to expand...
Click to collapse
That helped thanks, but I still can't boot into anything else... I'm pretty sure I can't install anything through fastboot without download or run mode...
Louis118 said:
That helped thanks, but I still can't boot into anything else... I'm pretty sure I can't install anything through fastboot without download or run mode...
Click to expand...
Click to collapse
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Aldo101t said:
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Click to expand...
Click to collapse
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Aldo101t said:
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Click to expand...
Click to collapse
what you should do is if you can restore a backup, put a 5.1 rom on your sd card and after you flash the latest firmware 2.10.401.xx. then boot to recovery and install the 5.1 rom.
---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------
Louis118 said:
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Click to expand...
Click to collapse
you still have TWRP INSTALLED, do you have a backup.
Aldo101t said:
what you should do is if you can restore a backup, put a 5.1 rom on your sd card and after you flash the latest firmware 2.10.401.xx. then boot to recovery and install the 5.1 rom.
---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------
you still have TWRP INSTALLED, do you have a backup.
Click to expand...
Click to collapse
How do you expect me to boot into it? I told you, pressing any other mode besides power off, causes the blue screen loop
Louis118 said:
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Click to expand...
Click to collapse
try powering it off then go back to bootloader and try to get to recovery again
Aldo101t said:
try powering it off then go back to bootloader and try to get to recovery again
Click to expand...
Click to collapse
Nope, still does the blue loop.
Louis118 said:
Nope, still does the blue loop.
Click to expand...
Click to collapse
well, that's the sh^ts, I don't know at this point.maybe someone else can chime in here that can help.
I've seen this before, and there is no fix that I'm aware of. You've corrupted something important in your firmware, probably by flashing all those firmware packages.
You made several mistakes here, the first in thinking you needed to flash every firmware for your phone. All you needed was the last one. The other mistake was confusing your OS version with your firmware version. You were still on 1.32 base but your firmware was updated.
The last mistake, and the one that probably did the damage, was trying to take an OTA after all that. You were stock enough for it to run, but since your firmware was already updated, the OTA broke something.
As far as I know, the only thing you can do is return it to HTC for service.
Sent from my HTC One M9 using Tapatalk
iElvis said:
I've seen this before, and there is no fix that I'm aware of. You've corrupted something important in your firmware, probably by flashing all those firmware packages.
You made several mistakes here, the first in thinking you needed to flash every firmware for your phone. All you needed was the last one. The other mistake was confusing your OS version with your firmware version. You were still on 1.32 base but your firmware was updated.
The last mistake, and the one that probably did the damage, was trying to take an OTA after all that. You were stock enough for it to run, but since your firmware was already updated, the OTA broke something.
As far as I know, the only thing you can do is return it to HTC for service.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help anyway. Also, I got this under contract from EE, so do I have UH OH protection automatically from htc? Or will it cost me to get it serviced?
Louis118 said:
Thanks for trying to help anyway. Also, I got this under contract from EE, so do I have UH OH protection automatically from htc? Or will it cost me to get it serviced?
Click to expand...
Click to collapse
Uh Oh protection isn't available in the UK.
As you unlocked your bootloader and got S-OFF, they will almost certainly charge you for repairs as this isn't a hardware issue and was actually caused by you flashing your phone.
Sent from my HTC One M9 using Tapatalk
Questions............
Did u install any recovery like twrp?
Did you root?
Post pictures of bootloader/try to post any other screen you may be able to enter
LLegion said:
Questions............
Did u install any recovery like twrp?
Did you root?
Post pictures of bootloader/try to post any other screen you may be able to enter
Click to expand...
Click to collapse
I'm able to enter the boot loader menu (with the options to reboot, power down, download mode and bootloader). Unfortunately, clicking any of the options (apart from power down) causes the blue screen boot loop to continue.
This wasn't really Crazy you now All You have to do is go to the bootloader menu and from there Ashley you can actually flash the Recovery ebusiness Leave me and if you don't believe me godaddy redirect link to the Team Win recovery project Website Just follow the instructions to flash recovery as they say
---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------
You can flash recovery from bootloader menu i did that way when by mistake did erease all my internal card including system.img.....i was lost my phone didnt boot line yours also getting the bluescreen and voilaaa!!! I did flash on bootloader menu but download the 2.8.7.1 beta here the proof link....https://twrp.me/devices/htconem9.html
LLegion said:
This wasn't really Crazy you now All You have to do is go to the bootloader menu and from there Ashley you can actually flash the Recovery ebusiness Leave me and if you don't believe me godaddy redirect link to the Team Win recovery project Website Just follow the instructions to flash recovery as they say
---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------
You can flash recovery from bootloader menu i did that way when by mistake did erease all my internal card including system.img.....i was lost my phone didnt boot line yours also getting the bluescreen and voilaaa!!! I did flash on bootloader menu but download the 2.8.7.1 beta here the proof link....https://twrp.me/devices/htconem9.html
Click to expand...
Click to collapse
I flashed the recovery file successfully (according to the command window) but when I click the "reboot recovery mode" option it brings up the red development text and then goes back into the bluescreen loop.
Louis118 said:
I flashed the recovery file successfully (according to the command window) but when I click the "reboot recovery mode" option it brings up the red development text and then goes back into the bluescreen loop.
Click to expand...
Click to collapse
You said before that fastboot wasn't working. It's working now? Does it show up in fastboot devices?
If so, you might try running a RUU from bootloader.
The trixk is to flash and just after reboot press power and down vol to wnter immediatly into rexovery twrp just as it says in the link...just do it and will go into twrp once you have entered justflash any nandroid or flash a zip ruu from sd card in a sexond boot
I'm not able to enter RUU mode...
This is my first post and I am writing it after a Christmas night with the fam, so please expect errors.
This phone has given me problems even before it arrived to my door Christmas eve. My city received too much snow for the mailman to deliver my package to my door, making it more difficult for me to obtain my device on time. Once I received my device it was great, fingerprint sensor was extremely convenient, took great pictures for Christmas, call quality was good, among other little things. Getting to the point of this thread. I got a notification to update my phone to the latest software, because we eating, I tried to set it for later. The "later" button did not work. after 2 hours and the annoying notification, I decided to download the update and install it. These are my steps:
Pluggled in the charger
Downloaded update
let the phone do its thing overnight
I woked up
"Google logo" bootloop
I can't access the recovery partition, it shows the green android logo with the string "no command"
When I manually boot the device using the bootloader:
"Your device is corrupt. It cant be trusted and may not work property
visit this link on another device
g.co/ABH
press power to continue "
please need help, It has been only 12 hours with the device, and I do not have a C to USB adapter to flash anything to the device.
Does bootloader allow you to use adb commands still?
hopesrequiem said:
Does bootloader allow you to use adb commands still?
Click to expand...
Click to collapse
I do not have a USB type C adapter, so I can not use any adb commands with the device.
The "No Commands" happens when I use the volume button to access recovery, as if there was no recovery partition installed
Call Google.
bobby janow said:
Call Google.
Click to expand...
Click to collapse
I would have tried, but the nexus 5 is the only device on the house.
I managed to find a type C cable at my local store (probs the only thing open today) I am going to try to flash a factory image using google's official method.
Any tips would be welcome.
I just checked and my recovery says no commands, I think it always does. To actually get the recovery commands to come up, when you're in recovery, press and hold the power button and then press volume up straightaway. The recovery menu will then come up and I suggest wiping your cache and rebooting. If that fails then u can also factory reset from there.
Sent from my Nexus 5X using Tapatalk
I was not able to flash anything yet.
Hayth said:
I just checked and my recovery says no commands, I think it always does. To actually get the recovery commands to come up, when you're in recovery, press and hold the power button and then press volume up straightaway. The recovery menu will then come up and I suggest wiping your cache and rebooting. If that fails then u can also factory reset from there.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply, when I used your method, a new screen showed up, downloading mode.
Firmware Update
Do not unplug the USB connection until the process is complete.
0%
I tried to adb and fastboot to access the recovery and wipe the cache but no luck.
LeGrassy said:
I was not able to flash anything yet.
Thanks for your reply, when I used your method, a new screen showed up, downloading mode.
Firmware Update
Do not unplug the USB connection until the process is complete.
0%
I tried to adb and fastboot to access the recovery and wipe the cache but no luck.
Click to expand...
Click to collapse
Huh, that is strange.. Sorry to hear it didn't work. Sounds like somethings definitely not quite right, I'd definitely go down the flashing stock images route.. I'm not sure how you can go about unlocking the bootloader though if you haven't already. Now we have the choose the allow oem unlock option in developer options u need to be able to start the phone :/
Sent from my Nexus 5X using Tapatalk
Ok, I uninstall and re-installed all the drivers with SDK tools and I that fixed my fastboot problems.
Now I have to unlock my device, but I can't load the OS, I have the factory image, downloaded from the google developer website.
I have the bullhead LGH790 16GB variant, and downloaded the (MMB29K) 6.01 Marshmallow
The issues as mentioned before is that the OS does not load so I cannot unlock my bootloader.
Is there any way to unlock it to flash a stock rom throught ADB, Fastboot, bootloader, etc?
LeGrassy said:
Ok, I uninstall and re-installed all the drivers with SDK tools and I that fixed my fastboot problems.
Now I have to unlock my device, but I can't load the OS, I have the factory image, downloaded from the google developer website.
I have the bullhead LGH790 16GB variant, and downloaded the (MMB29K) 6.01 Marshmallow
The issues as mentioned before is that the OS does not load so I cannot unlock my bootloader.
Is there any way to unlock it to flash a stock rom throught ADB, Fastboot, bootloader, etc?
Click to expand...
Click to collapse
That my friend is a very good question. I'm curious to hear the solution myself.
Maybe you can try this, adb flash stock recovery, and then load up the recovery like how I mentioned earlier. Then adb sideload this rom, it's completely stock but in zip format. I don't think it flashes the bootloader radio etc but I don't think they've changed since 6.0. If for any reason they have or u wanna flash the stock images thru fastboot to make sure everything's up to date, then u can go about unlocking the bootloader and reflashing the stock image to make sure uv got the right bootloader, radio etc : http://forum.xda-developers.com/showthread.php?t=3267096
Sent from my Nexus 5X using Tapatalk
I think the question is how do I unlock the bootloader if I can't enable developer options since I can't boot into the stock rom? The bootloader command says you can't unlock, thus really you can't do anything like flashing even a stock .img file. How do you bypass that? How are you able to do anything if you can't boot even into stock rom?
I'm not 100% sure if adb sideload needs an unlocked bootloader or not. I know that flashing an OTA thru stock recovery (update via adb) doesn't need an unlocked bootloader, so could be worth trying that if this doesn't work? Obviously gotta make sure you use the right OTA file
Edit: Actually, now that I think about it I think you need a custom recovery to adb sideload. So the only other thing I can think of is trying to flash the same OTA via stock recovery, OTA files can be downloaded here: http://www.droid-life.com/2015/12/09/download-android-6-0-1-marshmallow-updates-for-nexus-devices/
If your stock recovery isn't working properly though and it still just goes into download mode then I'm outta ideas might have to be an RMA to google
Sent from my Nexus 5X using Tapatalk
I extracted all the files from the .tgz I got from the google's website, and tried to flash the recovery ... but I can't really do it.
HTML:
target reported max download size of 536870912 bytes
sending 'recovery' (12509 KB)...
OKAY [ 0.479s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.502s
I am in the phone with google, and their are transferring me to LG, they will probably want me to return the device.
What a Christmas gift I received. The epic hold music is not helping me feel better either
LeGrassy said:
I extracted all the files from the .tgz I got from the google's website, and tried to flash the recovery ... but I can't really do it.
HTML:
target reported max download size of 536870912 bytessending 'recovery' (12509 KB)...OKAY [ 0.479s]writing 'recovery'...FAILED (remote: device is locked. Cannot flash images)finished. total time: 0.502s
I am in the phone with google, and their are transferring me to LG, they will probably want me to return the device.
What a Christmas gift I received. The epic hold music is not helping me feel better either
Click to expand...
Click to collapse
Christmas music?
RMA in process
Edit: "Christmas music? ", it was the classical music you see in the movies when the evil guy is killing innocent people.
Thanks for everybody who replied, you guys were helpful in one way or another.
LG's manufactures warranty said that my problem needed to repaired, the process will take 7-9 business days, if they cannot fix it they would send me a new phone.
Mods; if needed feel free to close this threat. Thanks
There has to be a way to recover from this. All the guides say to do this or that after you boot into rom and allow unlock bootloader. What if you can't get into the rom. Come on guys someone knows what to do. IRC perhaps? All you need to do is unlock the effin' bootloader and you're golden.
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
LeGrassy said:
Edit: "Christmas music? ", it was the classical music you see in the movies when the evil guy is killing innocent people.
<snip lol>
the process will take 7-9 business days
Mods; if needed feel free to close this threat. Thanks
Click to expand...
Click to collapse
BS 7-9 business days is ridic. No!
bobby janow said:
There has to be a way to recover from this. All the guides say to do this or that after you boot into rom and allow unlock bootloader. What if you can't get into the rom. Come on guys someone knows what to do. IRC perhaps? All you need to do is unlock the effin' bootloader and you're golden.
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
BS 7-9 business days is ridic. No!
Click to expand...
Click to collapse
I'm not BSing she said that they would give me a printing label so I can send it, once they receive the device they will take 7-9 days to repair it and then they would ship. I even made a joke to the customer rep, that in 7-9 days I could find a solution and charge them for my service.
She did not laugh
bobby janow said:
There has to be a way to recover from this. All the guides say to do this or that after you boot into rom and allow unlock bootloader. What if you can't get into the rom. Come on guys someone knows what to do. IRC perhaps? All you need to do is unlock the effin' bootloader and you're golden.
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
BS 7-9 business days is ridic. No!
Click to expand...
Click to collapse
yep, all you have to do is unlock the BL, too bad there is no way to do it in this condition. its fairly common knowledge.
bweN diorD said:
yep, all you have to do is unlock the BL, too bad there is no way to do it in this condition. its fairly common knowledge.
Click to expand...
Click to collapse
I did not know that. Very useful information, thanks.
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Dielahn said:
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Click to expand...
Click to collapse
That simple thread actually gave me an idea. I grabbed the latest SDK tools. Presto!
Note to anyone else with this issue...
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
By the way, the dead Droid is recovery, from that screen, hold power and press up for recovery menu, in case you ever get stuck again
And just for future reference for others who may be in a similar issue and stumble across this thread...
As long as you've successfully unlocked your bootloader and "fastboot devices" successfully pulls up your device, you'll be just fine. You just gotta take a step back, breath and then make sure your SDK tools are updated before moving forward.
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
Make sure you try a different cable to connect your phone to your PC.. I had the same issue, and I try two different cable before my device accepted the flash-all
Okay, so somehow fortunately I was able to get back into my TWRP 1 last time and able to push my files I needed to boot it back up...
Raistline said:
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
Click to expand...
Click to collapse
The funny thing is I was able to and was in bootloader but I couldn't use any commands from my computer (as far as I know) which is why I was freaking out.
I should've but I didn't actually try using other cables. I did try other usb ports but that didn't do anything.
I still kind of believe that my phone (somehow) got messed up from loading TWRP. I don't know if it's because it is still beta or what but I am like 99% sure it was from that as I can't see anything else being the problem.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
Something similar for me but with different reason for starting all this. When I did sideload of 8.1 all went well but my camera wasn't working (I saw the same thing in 8.1 DP) so I needed to go back to 8.0 but you can't sideload downgrade. I went to Google to get replacement sent and figure I might try to sort things out with this one in the meantime. I had to unlock to be able to just flash the factory 8.0 image so did that with both the unlock commands, then after that and after update I just got hung on the white screen with google logo. I was able to get back to bootloader with the power button + volume from off and from there I would get to the screen with the android and the exclamation point - I think you hold volume up and then power to go to sideload. Once there I just sideloaded 8.0 and all was good. I do still get the warning about corrupt whatever and have to hit power on reboot or fresh power up but I could redo the locks and whatnot and all seems fine now with camera working.
At the least I got camera back while waiting for replacement.
b4db0ys said:
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
This cleaned things up for me - still no camera in 8.1 but I got the replacement coming.
So I'm in the same boat as the OP but my bootloader is locked. Am I totally screwed? Is there a way to do any of this when the device won't show up in ADB?
Deuces said:
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
can you just develop some scripts that working on locked bootloader ?
i have a bricked Pixel xl with locked bootloader and oem locked
If you can boot twrp but can't connect to a pc, a type c flash drive comes in handy. Load it with the needed ota, twrp installer zip and Just mount it and you're good to go.