Develop Bugs

Help phone stuck at boot screen

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 :/

HTC One m8 doesn't boot

So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it. Today I wanted to recover it back to stock (When I got it out of the box) I did a command using fastboot which was along the lines of fastboot boot boot.img but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
PLEASE HELP ME
Issue Solved - 22/01/16

ChiefMustardo said:
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it.
Click to expand...
Click to collapse
Hard to help, if we don't know exactly what you did. Try to explain in detail (or as best you can) the exact steps (including file names, version numbers, etc.) of what you performed.
ChiefMustardo said:
I did a command using fastboot which was along the lines of fastboot boot boot.img
Click to expand...
Click to collapse
Again, hard to tell what the issue is, if we don't know exactly what you did.
Are you sure you didn't do fastboot flash? I don't think you would do anything permanent with the command fastboot boot.
What exactly were you trying to boot/flash with this command? What was the file name, where did you get it from, and what was the exact intent?
Did you get this idea from a thread or guide?
ChiefMustardo said:
but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
Click to expand...
Click to collapse
If you hold power + vol up for a long time (30 seconds or more) does the phone reboot? Then what, black screen again?
Do Power + vol up again. The moment the screen goes dark (but before the HTC logo screen with the red text warning) let go of those buttons, and only hold power down; and don't let go until you see the bootloader screen. If this fails, try again, you probably just got the timing wrong (started pressing vol down too late, or let go of it too early).
Once in bootloader, select fastboot (if not in that mode already) using vol keys, then confirm with power button. Connect to computer and do: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before you post).

Again, i am really sorry but i do not understand what i did. It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Here is the info:

ChiefMustardo said:
Again, i am really sorry but i do not understand what i did.
Click to expand...
Click to collapse
I seriously doubt that you can't remember any of the steps you did to try to root it.
Just sounds like you are too lazy to type. So why should I put forth more effort than you; when you are the one that wants help?
Describe as best you can, that is all I ask.
ChiefMustardo said:
It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Click to expand...
Click to collapse
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
And you really can't remember if you got this idea from a thread? You had to come up with it somehow.
What were you even trying to do here? What did you think the command would do?
Again, either you are just being lazy, evasive, or got hit on the head to cause amnesia; if you can't answer the questions.

So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect. I already new how to unlock the boot-loader because I owned a HTC desire 510. I went back onto my phone it has twrp installed but I use root checker and it says that proper root access is not granted and I have tried to use SuperSU but I got the binary issue so I gave up. It was working fine but today I decided I wanted to revert it back to stock again but did something which completely messed it up.
Also, i decided i wanted to restore it because if it broke and i needed it to be repaired it would void my warranty. I was thinking when i reset the RUU it would make it stock again but it did not.

Now, that's more like it!
ChiefMustardo said:
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect.
Click to expand...
Click to collapse
An Android app, or PC program?
Either way, one-click type root apps don't work on HTC devices. PC based toolkits worked at one time, but were never updated to support the recent software builds (outdated TWRP versions fail on Lollipop, and outdated SuperSU versions fail).
ChiefMustardo said:
S I decided I wanted to revert it back to stock again but did something which completely messed it up.
Click to expand...
Click to collapse
What did you think you were doing with the fastboot command (fastboot boot boot.img)?
One thing I can say for sure: Don't try mods, fastboot commands, etc. unless you know exactly what you are doing (such as following reputable instructions to the letter). The command you did just isn't right. You either got it from a bad source, or you decided to improvise or experiment (really bad idea). You made the issue much worse than it was to begin with (probably just needed to flash the updated SuperSU zip, maybe also update TWRP).
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
You also didn't answer the question:
redpoint73 said:
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
Click to expand...
Click to collapse

It was a computer application and i thought the command would reboot it with a different kernal/firmware thing. But yeah i followed the instructions like an idiot and messed up my phone and no i don't anymore because i deleted it

ChiefMustardo said:
i thought the command would reboot it with a different kernal/firmware thing.
Click to expand...
Click to collapse
Fastboot boot means you are trying to remote boot something without flashing it. A boot.img isn't bootable. I've only seen this done with recovery.img
I think you meant to do: fastboot flash boot boot.img
The one different word makes a huge difference. The action is to flash, not boot. The "boot" is the location of where to flash to.
Also, even if you properly flashed boot.img, this is just the kernel, and wouldn't change much. To return to stock, you want to flash a full ROM. And kernel, ROM and firmware are not interchangeable terms, so don't for a second think they are.

Ok. Is it possible though to revert it back to stock and if yes, do you think you can help me?

Do the fastboot command: fastboot oem lock. Then download the 4.16.401.10 RUU from the following thread, and run it from PC: http://forum.xda-developers.com/showthread.php?t=2701376
Your alternative is to restore the proper stock TWRP backup. While the relevant files are on that same link, you'll find clearer instruction on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

It now says Relocked then underneath security warning. Is that good?

ChiefMustardo said:
It now says Relocked then underneath security warning. Is that good?
Click to expand...
Click to collapse
The security warning just means you altered something in the stock software (root, kernel, etc.). It doesn't matter, as the RUU will write all partitions to factory condition.

Will i have to re unlock the boot-loader for the RUU.exe to work?

ChiefMustardo said:
Will i have to re unlock the boot-loader for the RUU.exe to work?
Click to expand...
Click to collapse
NO. Its required to be LOCKED or RELOCKED to run RUU.
Its the only reason I told you to relock it.

Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one

ChiefMustardo said:
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
Click to expand...
Click to collapse
What does your PC screen say? Is the RUU stuck sending?
You probably just need to disconnect the phone and start again. RUU just gets stuck sometimes. It shouldn't take any more than 5 or 10 minutes.

Yeah it says updating 0 out of 7 sending ........................

ChiefMustardo said:
Yeah it says sending 0 out of 7
Click to expand...
Click to collapse
It should be safe to just disconnect the phone and start over with the RUU again.

This is what comes up

It send that 1 had been sent then it said error

L24 completely bricked. Only goes to erecovery. What are the options?

Geez i wish haahwhahai would have a working erecovery. This is maddening.

I've been there before. I was able to use the method involving connecting / disconnecting the usb to get into fastboot, adb the recoveries, and reboot, being immediately prompted to factory restore. I don't know if that's helpful at all.

johncro13 said:
I've been there before. I was able to use the method involving connecting / disconnecting the usb to get into fastboot, adb the recoveries, and reboot, being immediately prompted to factory restore. I don't know if that's helpful at all.
Click to expand...
Click to collapse
Do you have a link to this method of restoring kind sir?
Thanks!

If possible, turn the phone completely off.
Plug the USB cable into the phone
Hold vol down
Hold power and IMMEDIATELY plug the other end of the USB cable into the PC.
This should get you into fastboot. From here, you should be able to use ADB.
Here's the thread that helped me most.

johncro13 said:
If possible, turn the phone completely off.
Plug the USB cable into the phone
Hold vol down
Hold power and IMMEDIATELY plug the other end of the USB cable into the PC.
This should get you into fastboot. From here, you should be able to use ADB.
Here's the thread that helped me most.
Click to expand...
Click to collapse
What should i use after i'm in fastboot? I've downloaded the latest full firmware that's out there, but it seems to be corrupt.

lowspeed said:
What should i use after i'm in fastboot? I've downloaded the latest full firmware that's out there, but it seems to be corrupt.
Click to expand...
Click to collapse
Is your bootloader unlocked?

smokinjoe2122 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Relocked

lowspeed said:
Relocked
Click to expand...
Click to collapse
I'm not sure how much you can do if the device is locked...A guess a few questions (In my tech support voice):
1.) How did it get to that point?
2.) Can you re-open the bootloader, and if you can, are you opposed to it?
3.) What was the last firmware you installed on it?

smokinjoe2122 said:
I'm not sure how much you can do if the device is locked...A guess a few questions (In my tech support voice):
1.) How did it get to that point?
2.) Can you re-open the bootloader, and if you can, are you opposed to it?
3.) What was the last firmware you installed on it?
Click to expand...
Click to collapse
1) I don't recall.
2) I could probably unlock it again. i'll give it a try.
3) it had some weird restore that i used, but that rom didn't have any update option.
I must sound retarded....

lowspeed said:
1) I don't recall.
2) I could probably unlock it again. i'll give it a try.
3) it had some weird restore that i used, but that rom didn't have any update option.
I must sound retarded....
Click to expand...
Click to collapse
Well most of the time, if it's a software issue, it's fixable. I don't know as much about this phone as I'd like, but I do know there's update packages out there you can use to your benefit if you can get the bootloader unlocked. I believe the Update.APP can even be unzipped or decompiled to get the main imgs from it, such as boot, recovery, and system.

im gonna go ahead and throw this out there. i just returned from the hardest brick i have ever done. i managed to make it so the phone wouldnt boot it would bootloop twice and go to erecovery and fail to restore. then i tried flashing the stock img's extracted from the update.app inside twrp and that made it worse. the screen went completely black and wouldnt do ****, the computer recognized it in bootloader mode but i couldnt flash a single thing as it would say i didnt have permission to or something like that(acting as if the bootloader was locked even though it was unlocked, or locked frp) i was about to give up and put my sim card back in my nexus as no matter what i did i couldnt get the screen to even turn on.
Well i found a post on the mate 9 sub-forum about someone who did the same thing and fixed it with dc-phoenix but costed him 18$, i decided 18 was worth it if it meant i had a working phone. and sure enough 5 minutes after paying and clicking flash update.app in the software it was up and running. now i have no idea how dc-phoenix can flash images when adb couldnt...but it works. if your out of options i would 100% say try it as 18$ is much better than a new phone.
---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------
something i did notice as the software did the commands to flash each image i noticed it started its commands with some kind of backdoor command. so maybe they know a backdoor to bypass a locked bootloader/frp

darkmage1991 said:
im gonna go ahead and throw this out there. i just returned from the hardest brick i have ever done. i managed to make it so the phone wouldnt boot it would bootloop twice and go to erecovery and fail to restore. then i tried flashing the stock img's extracted from the update.app inside twrp and that made it worse. the screen went completely black and wouldnt do ****, the computer recognized it in bootloader mode but i couldnt flash a single thing as it would say i didnt have permission to or something like that(acting as if the bootloader was locked even though it was unlocked, or locked frp) i was about to give up and put my sim card back in my nexus as no matter what i did i couldnt get the screen to even turn on.
Well i found a post on the mate 9 sub-forum about someone who did the same thing and fixed it with dc-phoenix but costed him 18$, i decided 18 was worth it if it meant i had a working phone. and sure enough 5 minutes after paying and clicking flash update.app in the software it was up and running. now i have no idea how dc-phoenix can flash images when adb couldnt...but it works. if your out of options i would 100% say try it as 18$ is much better than a new phone.
---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------
something i did notice as the software did the commands to flash each image i noticed it started its commands with some kind of backdoor command. so maybe they know a backdoor to bypass a locked bootloader/frp
Click to expand...
Click to collapse
Which files did you flash in DC Phoenix?
Thanks for posting this!

JDBarlow said:
Which files did you flash in DC Phoenix?
Thanks for posting this!
Click to expand...
Click to collapse
downloaded the latest update on firmware finder for my device(l24) and used winrar to pull the update.app from the zip. then you select that in dc phoenix to do the restore/flash

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 Help, Bootloader locked phone bricked

So I just received the phone today and as I always like to do with my new phones I downloaded the latest full ota, installed it through local upgrade and when I pressed reboot the phone rebooted normally.
I went an pressed reboot to recovery and boom the phone just died, no recovery it goes to QUALCOMM crash dump and I am able to boot into bootloader but OEM unlock is still off in the developers options, cant unlock boot loader, cant flash anything in fastboot and there are no MSM tools.
Anyone have any ideas??
Be careful I was on stock rom flashed with stock latest rom with locked bootloader and no funny business and the phone just dead.

I would contact oneplus. I had this once happen to me on my oneplus 3t and they were able to fix it using remote access and walking me through a few steps.

Will check that now

Once in fastboot. Try and run the commands for unlocking the bootloader. That's what worked for me.

speakeasy2 said:
Once in fastboot. Try and run the commands for unlocking the bootloader. That's what worked for me.
Click to expand...
Click to collapse
Won't work, I think its due to the OEM unlock toggle in the Developers options. (Was your toggled on?)

awsan said:
Won't work, I think its due to the OEM unlock toggle in the Developers options. (Was your toggled on?)
Click to expand...
Click to collapse
Yes, did you try and adb the stock.img if you can get into fast boot you should have a chance.

speakeasy2 said:
Yes, did you try and adb the stock.img if you can get into fast boot you should have a chance.
Click to expand...
Click to collapse
Tried that, tried flashing and booting from a boot.img and both returned with failed locked

What model do you have? I don't see why your OEM unlock option would be greyed out...

i just did the same thing, cant get past "device is corrupt and will not boot" i can get into fastboot but no commands work and it will not boot into recovery at all. unlocking the bootloader comes back "flashing unlock not allowed"
any fixes?

i just did the same thing, cant get past "device is corrupt and will not boot" i can get into fastboot but no commands work and it will not boot into recovery at all. unlocking the bootloader comes back "flashing unlock not allowed"
any fixes?

Wrssmithjr04 said:
I would contact oneplus. I had this once happen to me on my oneplus 3t and they were able to fix it using remote access and walking me through a few steps.
Click to expand...
Click to collapse
Thanks it worked, they contacted me and started a remote session and fixed the phone
craznazn said:
What model do you have? I don't see why your OEM unlock option would be greyed out...
Click to expand...
Click to collapse
It was not greyed out I just didnt press it before the phone was corrupted
jammin6996 said:
i just did the same thing, cant get past "device is corrupt and will not boot" i can get into fastboot but no commands work and it will not boot into recovery at all. unlocking the bootloader comes back "flashing unlock not allowed"
any fixes?
Click to expand...
Click to collapse
Chat with oneplus and request a remote session repair they will send you the files and one person will get remote access to fix your phone, Worked for me

awsan said:
Thanks it worked, they contacted me and started a remote session and fixed the phone
It was not greyed out I just didnt press it before the phone was corrupted
Chat with oneplus and request a remote session repair they will send you the files and one person will get remote access to fix your phone, Worked for me
Click to expand...
Click to collapse
thank you for the reply, i have been waiting on that remote session for 16 hours, hopefully they will contact me soon, i keep getting a run around from there live chat.

jammin6996 said:
thank you for the reply, i have been waiting on that remote session for 16 hours, hopefully they will contact me soon, i keep getting a run around from there live chat.
Click to expand...
Click to collapse
All you need is to change the active boot slot to that of before it was messed up.
In fastboot type:
fastboot getvar current-slot
This will tell you what (corrupted) slot you're currently booting from (either a or b). Then just change to the other one with the command:
fastboot --set-active=a
or
fastboot --set-active=b
Then reboot with the command:
fastboot reboot

i did something similar (hello, im an idiot) and oneplus just had me send my phone to a licensed repair place and have them send me a brand new one.
3 days later, sure enough, it was just a new phone. coming form op6, i didnt realize the state of rooting since OP8. Since google handles OPs OTA updates, its a lot harder and op8t was only able to root thanks to a generous insider who leaked the code needed to make MSMdownloadTool work.

purpleman2k said:
All you need is to change the active boot slot to that of before it was messed up.
In fastboot type:
fastboot getvar current-slot
This will tell you what (corrupted) slot you're currently booting from (either a or b). Then just change to the other one with the command:
fastboot --set-active=a
or
fastboot --set-active=b
Then reboot with the command:
fastboot reboot
Click to expand...
Click to collapse
I attempted that however OEM Unlock is not turned on in developer settings and fastboot --set-active just returns an error, something like Commands not allowed.
After 16 hours I finally got my remote session, it took almost 2 hours and they attempted to flash the wrong files on to my device, thank god MSM verifies that first. Then after the tech says "I apologize, my bad, I should have checked that first, we will try again in about 24 hours."
That was a bit ridiculous and if a supervisor isn't able to get it fixed soon, I'm just gonna return it and take my business somewhere else.

jammin6996 said:
I attempted that however OEM Unlock is not turned on in developer settings and fastboot --set-active just returns an error, something like Commands not allowed.
After 16 hours I finally got my remote session, it took almost 2 hours and they attempted to flash the wrong files on to my device, thank god MSM verifies that first. Then after the tech says "I apologize, my bad, I should have checked that first, we will try again in about 24 hours."
That was a bit ridiculous and if a supervisor isn't able to get it fixed soon, I'm just gonna return it and take my business somewhere else.
Click to expand...
Click to collapse
Please return the device, there are way too people messing up their device and can't fix it. You are seriously going to blame the manufacturer for something you messed up?

schmeggy929 said:
Please return the device, there are way too people messing up their device and can't fix it. You are seriously going to blame the manufacturer for something you messed up?
Click to expand...
Click to collapse
No I'm not blaming then for that. I'm blaming then for there lack of communication and the fact that they have me a run around for 16 hours and being transferred between 2 remote technicians, because "we apologize but Agnes is new here and wasn't sure what she was doing" just for the 2nd technician, Olivia, to attempt to flash the wrong files, and then says "we will try again this time tomorrow" that shows me how incompetent they are. They ask for a list of information before hand so that they make sure they have the right device and files.
And to further my reason for return, when I placed my pre-order it was listed as Dual-SIM, just to receive a single sim version. And the phone gets much hotter then most, and the battery life is no where near what it should be. With all that they want nearly the same price as all other flagship devices..

Finally got OnePlus to fix my phone using the MSM tool, and was able to keep an unprotected copy of it. what is the best place to upload and host a 3.5gb file so i can share it here?

Install TWRP through Odin and format data,, then flash factory stock ROM with Odin. Done!!!

Faizanbutt907 said:
Install TWRP through Odin and format data,, then flash factory stock ROM with Odin. Done!!!
Click to expand...
Click to collapse
odin is for samsung. you are on OP9 Pro section.