Develop Bugs

12 hours with a nexus 5x and it's already bricked

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.

Nexus 5x stuck in boot loop after OTA downgrade from N Preview to 6.01

The wife got a refurbished 5x from the Best Buy Sales this week, it was already on N. We went and opted out of the preview and it downloaded and installed 6.01. Since then it has gone into boot loop where it shows the Google Logo, then beginning on the animation, then starts over.
I am able to get into recovery mode, I tried a reset and that didn't work. I can get into adb, and the device is seen, but when I try to sideload, I get a E:footer error.
I also tried Nexus Root Kit, but its wants me to turn on developer mode for USB debugging, and the phone cant get me there.
Frustrated enough to call Best Buy, they sent me to the store Geek Squad. He said they could only exchange, and since they are out of phones, I am SOL for getting a working unit. Money back only.
Edit: When I try to run "fastboot flashing unlock" I get "FAILED (remote: oem unlock is not allowed)"

Pattond said:
The wife got a refurbished 5x from the Best Buy Sales this week, it was already on N. We went and opted out of the preview and it downloaded and installed 6.01. Since then it has gone into boot loop where it shows the Google Logo, then beginning on the animation, then starts over.
I am able to get into recovery mode, I tried a reset and that didn't work. I can get into adb, and the device is seen, but when I try to sideload, I get a E:footer error.
I also tried Nexus Root Kit, but its wants me to turn on developer mode for USB debugging, and the phone cant get me there.
Frustrated enough to call Best Buy, they sent me to the store Geek Squad. He said they could only exchange, and since they are out of phones, I am SOL for getting a working unit. Money back only.
Click to expand...
Click to collapse
I would be irritated too. Lets figure out where you are.
Lets boot into fastboot mode and see your bootloader is locked... Power off the phone then hold the power button and volume down button simultaneously. A few seconds later you will boot into fastboot mode. The bottom half of the screen should be information about your device. The last line should say DEVICE STATE = unlocked/locked. If it says locked you are in good shape. Just flash the latest factory images. If it is still locked, you need to figure out what path you want to get it running again.
Path 1. See if the bastard that had the phone before you flipped the "allow oem unlocking" in developer options. Reboot to fastboot mode as described above. Connect the phone to your computer. Then open a terminal (or command prompt) in the directory where your fastboot file is located and issue the following command:
Code:
fastboot oem unlock
If by some miracle it allows you to unlock, do it. You are in very good shape if you can. If you get to that point someone will help you fastboot the factory images. If not continue to path 2 below.
Path 2. Try and sideload the latest OTA. You are having trouble doing that, I see. You have a bad download. Also, I suggest using the developer preview OTA for reasons I cant explain. Let us know how it goes with another download and another try.
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.

PiousInquisitor said:
I would be irritated too. Lets figure out where you are.
Path 1. See if the bastard that had the phone before you flipped the "allow oem unlocking" in developer options.
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Returned with
FAILED (remote: oem unlock is not allowed)
PiousInquisitor said:
Path 2. Try and sideload the latest OTA. You are having trouble doing that, I see. You have a bad download. Also, I suggest using the developer preview OTA for reasons I cant explain. Let us know how it goes with another download and another try.
Click to expand...
Click to collapse
SHA256 Checksums on bullhead-ota-mtc19t-4ea6522b.zip match. When sideloading, at about 50% the phone says
"Warning: no file contextsThis package is for "bullhead" devices: this is a " ".
"E:Error in /sideload/package.zip
(Status 7)
Installation Aborted"
PiousInquisitor said:
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
Click to expand...
Click to collapse
I'm going to try that now.

You can use the Nexus root toolkit, manually put the phone in bootloader and click OK to get past the "enable debugging window". It's asking you to do that so it can reboot the phone itself into bootloader.

PiousInquisitor said:
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
Click to expand...
Click to collapse
The LG reset software got me going, but after it loaded, I did get an internal error message. I hit OK, it seem to be running fine. Will reload apps and see what happens.

Pattond said:
The LG reset software got me going, but after it loaded, I did get an internal error message. I hit OK, it seem to be running fine. Will reload apps and see what happens.
Click to expand...
Click to collapse
If I were you I'd unlock the bootloader, flash the latest factory images then relock the bootloader. Check the build number and date. I'm sure it's pretty old.
Sent from my SM-G930V using Tapatalk

PiousInquisitor said:
If I were you I'd unlock the bootloader, flash the latest factory images then relock the bootloader. Check the build number and date. I'm sure it's pretty old.
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
it is an old copy, 6.0. I started the update process, and got an update failed notice. I used the LG software again and it is getting it running, but I am still getting the internal error message (see attached)
.

Pattond said:
it is an old copy, 6.0. I started the update process, and got an update failed notice. I used the LG software again and it is getting it running, but I am still getting the internal error message (see attached)
.
Click to expand...
Click to collapse
The vendor image is out of date. When you boot up. Enable developer options. In developer options there is a toggle to allow OEM unlocking. Tick it. Then use fastboot to unlock the bootloader. Download and flash the latest images. You won't have any more problems.
Sent from my SM-G930V using Tapatalk

PiousInquisitor said:
The vendor image is out of date. When you boot up. Enable developer options. In developer options there is a toggle to allow OEM unlocking. Tick it. Then use fastboot to unlock the bootloader. Download and flash the latest images. You won't have any more problems.
Click to expand...
Click to collapse
All good, got it to 6.01, no internal error message on boot. I did the OEM unlock as you suggested, then let WugFresh's Nexus Root Toolkit take it from there. Thanks!

Damn I'm in the same situation but it will actually boot all the way to the lock screen and as soon as I put in my password it reboots. It actually will reboot regardless after sitting on the lock screen for about 10 seconds.
I really really don't want to lose everything on the phone. I have the factory image and can unzip it and manually install parts. I just don't want to wipe the data. Bootloader is still unlocked and I had oem unlock option enabled prior.

PiousInquisitor said:
I would be irritated too. Lets figure out where you are.
Lets boot into fastboot mode and see your bootloader is locked... Power off the phone then hold the power button and volume down button simultaneously. A few seconds later you will boot into fastboot mode. The bottom half of the screen should be information about your device. The last line should say DEVICE STATE = unlocked/locked. If it says locked you are in good shape. Just flash the latest factory images. If it is still locked, you need to figure out what path you want to get it running again.
Path 1. See if the bastard that had the phone before you flipped the "allow oem unlocking" in developer options. Reboot to fastboot mode as described above. Connect the phone to your computer. Then open a terminal (or command prompt) in the directory where your fastboot file is located and issue the following command:
Code:
fastboot oem unlock
If by some miracle it allows you to unlock, do it. You are in very good shape if you can. If you get to that point someone will help you fastboot the factory images. If not continue to path 2 below.
Path 2. Try and sideload the latest OTA. You are having trouble doing that, I see. You have a bad download. Also, I suggest using the developer preview OTA for reasons I cant explain. Let us know how it goes with another download and another try.
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
Click to expand...
Click to collapse
Ok, i feel really stupid asking this.....WHAT ARE YOU TALKING ABOUT WHEN YOU SAY "FLASH" THE LATEST FACTORY IMAGE????
Ive been stuck in a boot loop for 3 days now. it only gets as far as the "google" logo before rebooting agin and again and again and again....:crying::crying::crying::crying:

How to install Android in Download Mode

Hi everyone,
I'm really sorry, I really tried everything and I tried to look for an answer but it's very hard for me to understand.
My phone "died". I am not sure it's because of a firmware update or not, but now it's on an infinite bootloop.
I can access to recovery mode and download mode, I downloaded the factory image for Android 7 on the official website but then, I don't know how to continue. I open the file flash-all.bat, but in the command prompt it doesn't recognize it. I suppose I missed a step. Should I open the file from another software?
Please help...
Thanks a lot

http://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
Follow this guide to the letter. You probably haven't installed your fastboot drivers correctly.
Note: if your phone was working correctly and started bootlooping on its own, you might be one of the unlucky users who has a defective motherboard. If it continues bootlooping after flashing stock image RMA the phone.

peltus said:
http://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
Follow this guide to the letter. You probably haven't installed your fastboot drivers correctly.
Note: if your phone was working correctly and started bootlooping on its own, you might be one of the unlucky users who has a defective motherboard. If it continues bootlooping after flashing stock image RMA the phone.
Click to expand...
Click to collapse
Hi, thanks a lot for your answer.
I'm stuck at oem unlock. The command prompt tells me
FAILED (remote: oem unlock is not allowed)
And on the internet, they say to unlock it in the dev options... but I can't access to my phone. Am I stuck?
Edit: I tried to skip this and I succeeded in these conclusions: abd works but then I get an error when I try to abd sideload: footer is wrong, aborted.
Then I tried fastboot but fastboot doesn't recognize my device. What to do?

Light_Ben said:
Hi, thanks a lot for your answer.
I'm stuck at oem unlock. The command prompt tells me
FAILED (remote: oem unlock is not allowed)
And on the internet, they say to unlock it in the dev options... but I can't access to my phone. Am I stuck?
Click to expand...
Click to collapse
Pretty much, yes probably. As i said if it started bootlooping running completely stock you probably can't do much about it by flashing anyway.
It's a common fault on the n5x that started popping up recently.

peltus said:
Pretty much, yes probably. As i said if it started bootlooping running completely stock you probably can't do much about it by flashing anyway.
It's a common fault on the n5x that started popping up recently.
Click to expand...
Click to collapse
I tried to skip this and I succeeded in these conclusions: abd works but then I get an error when I try to abd sideload: footer is wrong, aborted.
Then I tried fastboot but fastboot doesn't recognize my device. What to do?

OK I did a lot of research and I think I'm stuck.
fastboot recognized my device, I had to connect the phone on USB 2 instead of USB 3 port.
ADB shows an error on the phone, and fastboot says OEM is forbidden. And because OEM can be activated only from the phone... I'm doomed I suppose.
LG said my warranty expired. And anyway, I would have to pay for shipping and all.
:'(
Thanks for everything. If you find anything, answer here.

I think someone has already started a thread on unbricking bootloader locked phones. You might search for that.
But to me, it just sounds like the hardware has gone belly up just as many others. You might search for that problem also.

Thank you, I contacted the author of the topic!
Just in case for people, here is the topic: http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740 ([REQ] Need help. Unbrick phones with locked bootloader, oem unlock disabled)

Light_Ben said:
Hi everyone,
I'm really sorry, I really tried everything and I tried to look for an answer but it's very hard for me to understand.
My phone "died". I am not sure it's because of a firmware update or not, but now it's on an infinite bootloop.
I can access to recovery mode and download mode, I downloaded the factory image for Android 7 on the official website but then, I don't know how to continue. I open the file flash-all.bat, but in the command prompt it doesn't recognize it. I suppose I missed a step. Should I open the file from another software?
Please help...
Thanks a lot
Click to expand...
Click to collapse
just sent it to lg ...I iam paying 130 euros for new bootlader because mine stucked on bootloop but I can acces the recovery mode and I tried to flash stock but nothing if you never locked the bootloader try to sent it to lg and say to them you never unlock the bootloader ....sorry for my bad engilsh

I have a big problem and I did not find any solution at xda.
I flashed a custom rom and now after entering pin my phone bootloops. I am not able to enter recovery or download mode.
It feels like the phone is ignoring volume up and volume down buttons. I also tried to press the buttons directly on the motherboard. I cannot immagine that the buttons are broken. Has anybody an advice or me?

How to access EDL mode on g7 play?

How do you access EDL mode on this device? Fastboot oem blankflash does not work. It only returns a denied message. If your wondering why I need access to this mode it's so I can fix my baseband. I read somewhere here on xda that doing so may help me get the original baseband back.

Also require access to EDL mode, but can't find a way.
I have the same question...
Deep flash cables don't seem to work, although I just learned that I need to check the "ports" section of Windows device manager and not simply expect it to pop up like a new device normally would.
My G7 Play isn't bricked.
Not rooted, and no TWRP installed either.
I need to figure out a way to make a full disk image without destroying the data already present.
The options theoretically possible seem to be:
1. Root via exploit - I'm currently exploring the viability of privilege escalation from Ubuntu installed in Termux
2. Unlock the bootloader without formatting anything - Guides do exist for other phones, but I only get one chance to get this avenue right.
3. Enter EDL mode and backup the entire disk using Qualcomm's own software. - The easiest way (on paper), but the method to put this phone in EDL mode continues to elude me.
I'm aware of the typical three ways to get a Qualcomm device in EDL mode without bricking it...
Deep flash cable - doesn't seem to work, but I'll try again with freshly aquired knowledge.
ADB/fastboot command - I've tried all of them native to my device, and a few that were added from guides about other devices
JTAG "pins" - much more like pads than pins...
Can't find diddly about 'em.
Don't know if they exist on a G7 Play, or which two to short to each other if they are even there.
Anyone have a potential solution that i may have overlooked?

Not sure if this is what you need or not but here's s link for a PDF file that's chock fill of nerd stuff (schematics/pinouts/etc) regarding the g7 play (-4 variant, I think)
The term JTAG hits like 13 times so it might hey you in the right direction at least.
[Google drive]/file/d/15aZddF1RALQyjJ9hUI4nTYLewYSa9ERY/view?usp=drivesdk
(I've been a member forever but this is my first post. Not sure if I can post links or not so just replace the above with drive.goog...etc...)
If you have any problems with the link PM me and we'll sort it out.
Good luck.

travis.mcgaw said:
Not sure if this is what you need or not but here's s link for a PDF file that's chock fill of nerd stuff (schematics/pinouts/etc) regarding the g7 play (-4 variant, I think)
The term JTAG hits like 13 times so it might hey you in the right direction at least.
[Google drive]/file/d/15aZddF1RALQyjJ9hUI4nTYLewYSa9ERY/view?usp=drivesdk
(I've been a member forever but this is my first post. Not sure if I can post links or not so just replace the above with drive.goog...etc...)
If you have any problems with the link PM me and we'll sort it out.
Good luck.
Click to expand...
Click to collapse
You need 10 posts to share links
Clickable link
https://drive.google.com/file/d/15aZddF1RALQyjJ9hUI4nTYLewYSa9ERY/view
Sent from my ali using XDA Labs

How to over think the simple things?
Thanks for the input gentlemen,
I'll hang on to the literature for future reference.
Turns out that I was wayyyyyyyy over thinking it.
Motorola's adb and fastboot commands (particularly on Qualcomm socs) is highly contextual.
When the documentation said 'adb reboot edl' that's what it meant.
Not from the booted os though.....
From recovery (SMH).
Simple as that for anyone else who's trying to take a full disk image without unlocking their bootloader
I think I'll still pursue a root exploit via termux though.
It could help a lot of folks out who don't have a solid root solution (Samsung users).
I'm too close to just forget about it anyway.
Seems to be working out like the old adb temp root, but with the possibility of automating the process into something less cumbersome.

Select slot_b from TWRP, then reboot into fastboot. You'll brick and go into EDL. I just did it last night on accident.

ok so i have the xt1952-t variant i have no stock recovery ive flashed in fastboot stock android 10 rom (XT1952-T_CHANNEL_RV_9.0_PCYS29.148-154-8_cid21_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml) everything flashed fine but it wont boot it says no baseband and ro.full build is blank. everytime it says unable to read non-hlos and kicks me back to fastboot. also bootloader is locked still i have my unique key but without being able to boot to os i cant toggle oem unlock..... this has been so frustrating. I believe i need to blank flash the device but cant get to edl.... can somebody tell my noob @$$ how to fix this thing? its my friends device i think he issued an erase all command. ive tried oem config fsg-id tmo and oem config carrier tmo both say ok but nothing fixes it.....please sos. Thanks in advance.
EDIT* Got it to boot to stock recovery after all thanks
---------- Post added at 09:36 AM ---------- Previous post was at 09:12 AM ----------
when you say "adb reboot edl" from recovery do you mean adb sideload? didnt work for me help please?

chrisdsj said:
ok so i have the xt1952-t variant i have no stock recovery ive flashed in fastboot stock android 10 rom (XT1952-T_CHANNEL_RV_9.0_PCYS29.148-154-8_cid21_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml) everything flashed fine but it wont boot it says no baseband and ro.full build is blank. everytime it says unable to read non-hlos and kicks me back to fastboot. also bootloader is locked still i have my unique key but without being able to boot to os i cant toggle oem unlock..... this has been so frustrating. I believe i need to blank flash the device but cant get to edl.... can somebody tell my noob @$$ how to fix this thing? its my friends device i think he issued an erase all command. ive tried oem config fsg-id tmo and oem config carrier tmo both say ok but nothing fixes it.....please sos. Thanks in advance.
EDIT* Got it to boot to stock recovery after all thanks
---------- Post added at 09:36 AM ---------- Previous post was at 09:12 AM ----------
when you say "adb reboot edl" from recovery do you mean adb sideload? didnt work for me help please?
Click to expand...
Click to collapse
How did you get??

dmferrer89 said:
How did you get??
Click to expand...
Click to collapse
I honestly dont remember bro. ive moved a few times and i dont have that phone anymore, i did successfully fix it though. im working on xt2131-1 now.

LeeSylva said:
How to over think the simple things?
Thanks for the input gentlemen,
I'll hang on to the literature for future reference.
Turns out that I was wayyyyyyyy over thinking it.
Motorola's adb and fastboot commands (particularly on Qualcomm socs) is highly contextual.
When the documentation said 'adb reboot edl' that's what it meant.
Not from the booted os though.....
From recovery (SMH).
Simple as that for anyone else who's trying to take a full disk image without unlocking their bootloader
I think I'll still pursue a root exploit via termux though.
It could help a lot of folks out who don't have a solid root solution (Samsung users).
I'm too close to just forget about it anyway.
Seems to be working out like the old adb temp root, but with the possibility of automating the process into something less cumbersome.
Click to expand...
Click to collapse
You can't reboot to EDL from recovery using the phones interface nor ADB if in sideload mode etc. This just isn't possible.
There are a lot of custom made ADB versions out there other than the stock platform tools. These other ones contain special commands for various brands that support them. I do know these will work but unfortunately only testpoints, bricking, or like smoeone said possibly changing configuration of boot are the only ways to get into EDL I can think of.

I never could get motorolas into EDL switching between slots and such with TWRP.
Spaceminer said:
Select slot_b from TWRP, then reboot into fastboot. You'll brick and go into EDL. I just did it last night on accident.
Click to expand...
Click to collapse
Seriously? That's odd. What build? I could never achieve this (didn't try intentionaly either) . Every time I would do as you explain for testing purposes my phone would simply reboot to TWRP or back to slot a. This is with majority of motorolas i have with slots and with no configuration changed by me.

fastboot oem blankflash

Question Unlocked Pixel 6 Pro - "Your Device is corrupted and cannot be trusted" error after trying to manually flash Dec 2021 factory image

I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?

Deleted

You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
lil_michelle said:
Did you flash disable dm verity first after unlocking the bootloader before flashing a patched system image?
Click to expand...
Click to collapse

mac796 said:
You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
Click to expand...
Click to collapse
thank you! Using the Android Flash Tool resolved my issue.

I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?

summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
Hard to say, for those of us who haven't had any problems...yet. I've flashed the full factory image at least twice so far.
Normally, the USB cable and to a lesser extent, the USB port used on the computer, would be my first suspects as to the problem, but since you said it finished successfully, I have no clue.

Do I need to disable dm verity at least once, or is that just completely obsolete now.

summitfox said:
Do I need to disable dm verity at least once, or is that just completely obsolete now.
Click to expand...
Click to collapse
When using Magisk 23016 for rooting it is not necessary at all.

summitfox said:
Do I need to disable dm verity at least once, or is that just completely obsolete now.
Click to expand...
Click to collapse
The *only* time you *might* still need to disable verity and verification are for some custom kernels - until those kernels are updated the same way Magisk Canary 23016 was, and then they won't need it. If you're not planning on using custom kernels, and just rooting the stock kernel instead, then there's no reason to disable them anymore.

tuffCookie said:
I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?
Click to expand...
Click to collapse
summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
Did either of you verify the hash of the download before flashing?
Before flashing any image, the hash should always be verified as it ensures the file is secure and not corrupted.

JW09I4 said:
Before flashing any image, the hash should always be verified as it ensures the file is secure and not corrupted.
Click to expand...
Click to collapse
^ This. For years now, I've just gotten used to verifying the hash of every important thing that I download that has the hash value made available. Saves a lot of hassle later on since if the downloaded file is corrupted just slightly, everything will go wrong down the road in the process.
I also check for new Platform Tools and Google's USB driver each and every time I flash a new update. It's just habit and again, saves a lot of trouble.

To add on the previously said:
Windows has a built-in hash checker, you just need to open CMD and type
Get-FileHash <Drag'n'Drop'le'File'here>
Click to expand...
Click to collapse
Then just copy the hash (strg+c) into your browser search window where you downloaded the OTA/firmware (strg f to open search, strg v to paste) and if you get a match (1/1), the hash checks out.
It's easy, it's fast, it's reliable. It will only cost you a few seconds. No hassle involved.

Morgrain said:
Windows has a built-in hash checker, you just need to open CMD and type
Click to expand...
Click to collapse
For anyone who doesn't know, this is referencing Windows' built-in PowerShell. It may be the default these days as Microsoft pushes it and it's more capable than Command Prompt, but you can still open CMD and the "Get-FileHash" won't be available there.

Morgrain said:
To add on the previously said:
Windows has a built-in hash checker, you just need to open CMD... Then just copy the hash (strg+c) into your browser search window where you downloaded the OTA/firmware (strg f to open search, strg v to paste) and if you get a match (1/1), the hash checks out.
Click to expand...
Click to collapse
roirraW edor ehT said:
For anyone who doesn't know, this is referencing Windows' built-in PowerShell. It may be the default these days as Microsoft pushes it and it's more capable than Command Prompt, but you can still open CMD and the "Get-FileHash" won't be available there.
Click to expand...
Click to collapse
It's often better to use a program that will compare the hashes, else a SHA256 or SHA512 hash becomes tedious to manually compare - I'm partial to QuickHash [GitHub] due to its broad functionality (drag and drop file for it to auto-compute hash and you can paste what the hash should be either before or after)

For quick one or two-file comparisons, I prefer Implebits' HashTab, which adds a new configurable tab to the file properties dialog in Windows. I originally got turned onto the program when it was Beeblebrox.org, which being a Douglas Adams fan definitely got my attention back then but I stuck with it after they sold it.
Edit: I see Implebits is going out of business and HashTab will go to GitHub and be open source, so exciting times!
Implbits Software, LLC is going out of business
We will soon release Hashtab as an Open Source project on Github. Until we do... you can download the last build of Hashtab that we made using the link below:
Click to expand...
Click to collapse

Actually the same situation here. What's the version of your adb tool. Do I have to use the web tool to flash in the future? Could I use adb with flash.bat as always？

mac796 said:
You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
Click to expand...
Click to collapse
That's what I had to do and agree to relock bootloader

Joynaruto said:
Actually the same situation here. What's the version of your adb tool. Do I have to use the web tool to flash in the future? Could I use adb with flash.bat as always？
Click to expand...
Click to collapse
Tried that with no joy as future idk. My situation was different after flashing Los the recovery was overwritten and flashing stock said something about timestamp error

summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
I think you should of used the full image not the update with flashall.bat

tuffCookie said:
I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?
Click to expand...
Click to collapse
I had this before as well after manually flashing the November update. Got the device cannot be trusted. Rebooted, flashed again, and device completely fried. Wouldn't turn on, not recognized by computer, nothing. Complete brick. Suspect system board fried. I'll never try to manually flash an update with a Google device again. Hopefully it ends better for you.