I recently got a Motorola Moto X 2nd gen(kind of an old phone). I've been experimenting with bootloader and rooting my device. Being the idiot that I am, I decided to reboot my device for no reason. I got a boot loop and have tried factory resetting which did not work. I'm kind of desperate at this point.
radigirl said:
I recently got a Motorola Moto X 2nd gen(kind of an old phone). I've been experimenting with bootloader and rooting my device. Being the idiot that I am, I decided to reboot my device for no reason. I got a boot loop and have tried factory resetting which did not work. I'm kind of desperate at this point.
Click to expand...
Click to collapse
Can you put the phone in bootloader mode and type:
fastboot getvar all
And paste all the info here.
Related
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
rootSU said:
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
Click to expand...
Click to collapse
Hmm, thanks anyway. I think this means I'm bricked. Moto E time I think.
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
TheAmazingDave said:
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
Click to expand...
Click to collapse
Can't be done.
Have the same problem and try to solve it with Motorola. No luck at the moment.
lee.jarratt said:
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Click to expand...
Click to collapse
try flashing the factory img via your bootloader/fastboot
simms22 said:
try flashing the factory img via your bootloader/fastboot
Click to expand...
Click to collapse
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
rootSU said:
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
Click to expand...
Click to collapse
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
TheAmazingDave said:
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
Click to expand...
Click to collapse
That's what all the threads about this today are saying... Including the op of this thread.
rootSU said:
That's what all the threads about this today are saying... Including the op of this thread.
Click to expand...
Click to collapse
Damn, that's really lame...
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
I'm an idiot.
I made the mistake of trying to update my Nexus 6 (Stock 5.0 encrypted, rooted, Xposed) while talking to AT&T customer service on my other phone. Distracted flashing is a bad idea. I am sure I made SEVERAL mistakes.
I too was trying to flash the new 5.1 image and got an error when running ./flash-all.sh (I'm on a Macbook). Friend suggested I try to do it by flashing the boot.img recovery.img and then system.img manually. Got the boot to flash. Recovery flashed. System failed. Unfortunately I have closed the terminal windows and don't have the errors anymore. When it failed it said something about insufficient space. So (I'm assuming this is where I f**ked up) I hit start from the boot loader screen to boot into the system and delete some things even though I had plenty of space (over 20gb). It booted fine. When I went to reboot into bootloader, I accidentally selected recovery. It booted back into TWRP which confused me. I thought best bet would be to wipe the device and start over fresh. I wiped everything and booted back into bootloader... blackness. Now I have no response from the device at all. Nothing. No response from the power button. Nothing when I plug to a charger. Just blackness. Just a pretty, 2 day old Nexus 6 (warranty replacement from T-Mobile on Tuesday).
You wiped the boot partition too? Ouch...
Last time I did that, it was with my Nook Color. Thankfully that was able to boot from SD cards...
I have a similar problem with another Nexus 7 right now. Flash went corrupt, won't boot at all. No bootloader, no Google logo, nothing.
My only hope is that the device still talks to the computer, it shows up as a Qualcomm device under Ports in Windows Dev Manager. QPST picks it up and says it's in download mode. If I can source the hex files to flash, I think I can bring it back. I'm only sharing that because it might be your only hope too. Godspeed, sir.
beachbum40 said:
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
Click to expand...
Click to collapse
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
simms22 said:
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
Click to expand...
Click to collapse
The problem is that bootloader got relocked, and the OP is unable to get to the setting to enable oem unlock. Fastboot is errors out saying to Check "Allow OEM unlock", and FAILED (remote failure).
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
efrant said:
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
Click to expand...
Click to collapse
Thank you for taking a look at my post. I have tried all the options in the bootloader menu with no dice. Things aren't looking promising for me...
You're all using the newest fastboot?
flash the factory img
edit.. nevermind, i see ive already said that
Did something stupid and bricked my 2013 Moto X. When plugging it in, the QHSUSB_DLOAD does not show up. If I unplug the battery and plug the phone in, it connects for a second and disconnects.
From researching, I found that I need to ground a pin to kick the phone into QHAUSB_DLOAD mode. Does anybody have experience in this and know what pin needs to be grounded?
core2kid said:
Did something stupid and bricked my 2013 Moto X. When plugging it in, the QHSUSB_DLOAD does not show up. If I unplug the battery and plug the phone in, it connects for a second and disconnects.
From researching, I found that I need to ground a pin to kick the phone into QHAUSB_DLOAD mode. Does anybody have experience in this and know what pin needs to be grounded?
Click to expand...
Click to collapse
If you were trying to root using the "brick" method, then it's advisable to check with OP and follow the instructions completely. I believe the next step in that thread was to use a script to bring it back to life.
Actually I had a Dev Edition Bootloader Unlocked XT1060 that a friend flashed to an XT1053 4.4.4 software. Obviously it failed at all system updates so I tried to restore it to the XT1060 5.1 software. That failed at flashing system.img so I reflashed from the start to 4.4.4 XT1060 software. Ran OTA once the phone was back up and it bricked.
I am getting it into the QHSUSB_DLOAD mode however I believe I have the newest 30.BE bootloader. Trying to unbrick using the following method doesn't do anything. Step 0 completes successfully however RSD can't get the phone into fastboot mode.
http://forum.xda-developers.com/mot...loader-v30-t3153725/post62367508#post62367508
I have the same problem. Did a system update and now the screen does not wakeup. Cannot go into bootloader. No charging indication nor responds to buttons. Just black screen. Followed the guide. Step 1 completes successfully but RSDLite says phone failed to switch to fastboot mode. I am using a Verizon Moto X 1st Gen Developer Edition. Bootloader is unlocked before the problem happened. Appreciate any help.
I recently tried rooting my Moto X 2nd gen again, but something failed and now twrp is reporting " No OS". i can still get into recovery and fastboot mode. I believe i can flash the factory images but motorola is taking forever to grant access to it. suggestions?
LilTurtle said:
I recently tried rooting my Moto X 2nd gen again, but something failed and now twrp is reporting " No OS". i can still get into recovery and fastboot mode. I believe i can flash the factory images but motorola is taking forever to grant access to it. suggestions?
Click to expand...
Click to collapse
XT1092?
Hello, recently i had some issues with my phone, and i thougt. well i should do a factory reset, just in case, but when i did the reset, the phone was in the same condition as before, so my next step was to reflash the stock rom, im not in custom ones btw, and my phone is still locked, long story short, with every program comand, and even oficial software, my phone refuses conection, with android cmd tools, its always stuck forever in a line called, sendig partition (45kb) and thats all it can be there for hours, the phone is just doing nothing, also the booloader oficial cmd, cant extract the key just sit there doing nothing, however, my phone is not bricked, bootloader devices detect my phone but i cant reflash the phone, i already tried the blank flash cmd, just say waiting for device. can someone help me with this issue? im not a noob, i already save one moto x with blank flash and rooted several past generations of moto phones.
priviet.toledo said:
Hello, recently i had some issues with my phone, and i thougt. well i should do a factory reset, just in case, but when i did the reset, the phone was in the same condition as before, so my next step was to reflash the stock rom, im not in custom ones btw, and my phone is still locked, long story short, with every program comand, and even oficial software, my phone refuses conection, with android cmd tools, its always stuck forever in a line called, sendig partition (45kb) and thats all it can be there for hours, the phone is just doing nothing, also the booloader oficial cmd, cant extract the key just sit there doing nothing, however, my phone is not bricked, bootloader devices detect my phone but i cant reflash the phone, i already tried the blank flash cmd, just say waiting for device. can someone help me with this issue? im not a noob, i already save one moto x with blank flash and rooted several past generations of moto phones.
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
I had a similar problem just now - could not do anything in fastboot mode, LMSA failed as well. To solve it, I switched to another PC, and stopped using USB3 to USB-C custom cable, and used the original one I got with the phone (USB-C to USB-C). So my guess is, you need to connect to the PC with the original cable, directly, or just with a better cable than the one you were trying with.
my motog7 Lenovo android is stuck in bootloader mode tried to reset or restart nothing keeps jus sitting there Help
Gingerale2020 said:
my motog7 Lenovo android is stuck in bootloader mode tried to reset or restart nothing keeps jus sitting there Help
Click to expand...
Click to collapse
What does getvar all say
Code:
fastboot getvar all [/Code
[url]https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039[/url]
so yeah dsu loader plop No valid system found. cant unlock bootloader, recovery not booting. nothing
I'm in the same, no recovery, no system and bootloader blocked, already tried flashing different stock roms which are supossed to be signed by Moto and nothing works, can't wipe userdata, can't unlock bootloader, can boot imgs. I think the only solution would be to to a blanflash but I can't find a way to boot the device into EDL mode neither, did you find any solution?
Ar-Dinthalion said:
I'm in the same, no recovery, no system and bootloader blocked, already tried flashing different stock roms which are supossed to be signed by Moto and nothing works, can't wipe userdata, can't unlock bootloader, can boot imgs. I think the only solution would be to to a blanflash but I can't find a way to boot the device into EDL mode neither, did you find any solution?
Click to expand...
Click to collapse
[SOLVED] Recover Moto G50 from hardbrick state (stuck in EDL)
Hallo Moto Users😃 Last few days, it was a nightmare to find some ready and working solution on hardbricked Motorola. After 5 or 6 days finally bootloader screen appeared😎 Just to mention - until one week ago I was just and only Samsung user for...
forum.xda-developers.com
Check this out. U may only need to start from booting into edl mode