I was trying to fix boot loop and completely hard bricked my phone. I can only get into AP Fastboot Flash Mode (Secure) in bootloader. I have been trying to flash it with windows batch file copied into firmware folder but not getting anywhere.
'No valid operating system could be found' on the screen when its not in bootloader.
Please help flash the stock ROM.
Thanks
How I fixed my Z4 XT1980-3
TLDR, try downloading and using the Lenovo Moto Smart Assistant (LMSA) tool
Yesterday I was trying to root my new Z4 and flashed a magisk patched boot img after I got the bootloader unlocked, and I'm pretty sure I ended up exactly where you are. I panicked, tried to do a recovery, a factory reset, nada and got suck in fastboot (apparently that's a Motorola thing). Then I stumbled on a thread elsewhere referring to the Lenovo Moto Smart Assistant (LMSA) tool.
I downloaded it thinking it couldn't hurt. After I started the program and waited through the stupid splash screen, I connected my device (which my PC could no longer detect) and it immediately began installing the Motorola drivers (by that point I had uninstalled just about everything).
I used the rescue function, chose my model, and it downloaded the stock rom. After about an hour, it finished and I started the rescue process. It went through fine until it got to 47%, and then it seemed to hang. After I waited (probably not long enough), I restarted fastboot and unplugged then plugged my phone back in, and it installed the rom and restarted. Back to stock! Not rooted, but working with the BL still unlocked. Yay!
I was shocked at how easy it was, I got cocky and immediately proceeded to soft brick it again. I thought I was better off this time because I wasn't stuck in fastboot, but using the LMSA program was not successful several times. Some times it told me my device wasn't compatible, other times it would just fail. After messing around with it all afternoon, I was where I was the night before--no phone. I was bummed and figured I deserved it, but kept messing with it. I rebooted and had the program redownload the rom, tried it again, and it worked!
No idea if this is the same problem or if it can work for you, but probably can't make it worse? --A
aurelya.hyjal said:
TLDR, try downloading and using the Lenovo Moto Smart Assistant (LMSA) tool
Yesterday I was trying to root my new Z4 and flashed a magisk patched boot img after I got the bootloader unlocked, and I'm pretty sure I ended up exactly where you are. I panicked, tried to do a recovery, a factory reset, nada and got suck in fastboot (apparently that's a Motorola thing). Then I stumbled on a thread elsewhere referring to the Lenovo Moto Smart Assistant (LMSA) tool.
I downloaded it thinking it couldn't hurt. After I started the program and waited through the stupid splash screen, I connected my device (which my PC could no longer detect) and it immediately began installing the Motorola drivers (by that point I had uninstalled just about everything).
I used the rescue function, chose my model, and it downloaded the stock rom. After about an hour, it finished and I started the rescue process. It went through fine until it got to 47%, and then it seemed to hang. After I waited (probably not long enough), I restarted fastboot and unplugged then plugged my phone back in, and it installed the rom and restarted. Back to stock! Not rooted, but working with the BL still unlocked. Yay!
I was shocked at how easy it was, I got cocky and immediately proceeded to soft brick it again. I thought I was better off this time because I wasn't stuck in fastboot, but using the LMSA program was not successful several times. Some times it told me my device wasn't compatible, other times it would just fail. After messing around with it all afternoon, I was where I was the night before--no phone. I was bummed and figured I deserved it, but kept messing with it. I rebooted and had the program redownload the rom, tried it again, and it worked!
No idea if this is the same problem or if it can work for you, but probably can't make it worse? --A
Click to expand...
Click to collapse
I really appreciate your reply.
I have tried LMSA tool but it's failing once I select the model number "Failed to match the connected device. Please plug it out and try again.". I have attached the screenshot.
Motorola ADB Interface driver is installed just like you described.
I think the bootloader is locked (Verizon ver.) and don't think there is any way to unlock it.
Thanks again for looking into this.
pate201 said:
I really appreciate your reply.
I have tried LMSA tool but it's failing once I select the model number "Failed to match the connected device. Please plug it out and try again.". I have attached the screenshot.
Motorola ADB Interface driver is installed just like you described.
I think the bootloader is locked (Verizon ver.) and don't think there is any way to unlock it.
Thanks again for looking into this.
Click to expand...
Click to collapse
UPDATE:
I managed to flashed stock ROM successfully without any error. But the phone is still in boot loop at logo instead of bootloader screen. Baseband is <not found> when booting into fastboot mode. LMSA tool still failing to to match the connected device. Verizon Software Upgrade Assistant is recognizing the phone in fastboot mode and trying to repair but software is not installing downloaded updates; it is stuck at 0% even won't do anything.
I think, I need to fix the Baseband but not sure what to do.
Thanks
I'm pretty confused where you are in the process.
Your device is Verizon? My understanding (and I could be wrong) is that Verizon devices can't have their bootloader unlocked, and without unlocking the bootloader, you can't flash a new ROM.
So, is your BL unlocked?
I specifically got the unlocked Amazon variant Z4 XT1980-3 hoping I could unlock the BL and root. I was able to do both, but I could only root after I got the BL unlocked.
I think I could upload my baseband file if you want to play around, but I have no idea if you're gonna brick your device. I'd check around in other forums/online and see what you can find out. I got the z4 because it was super cheap (comparatively) so if I killed it I wouldn't feel too bad buying a replacement. But $$'s still $$.
GL man!
aurelya.hyjal said:
I'm pretty confused where you are in the process.
Your device is Verizon? My understanding (and I could be wrong) is that Verizon devices can't have their bootloader unlocked, and without unlocking the bootloader, you can't flash a new ROM.
So, is your BL unlocked?
I specifically got the unlocked Amazon variant Z4 XT1980-3 hoping I could unlock the BL and root. I was able to do both, but I could only root after I got the BL unlocked.
I think I could upload my baseband file if you want to play around, but I have no idea if you're gonna brick your device. I'd check around in other forums/online and see what you can find out. I got the z4 because it was super cheap (comparatively) so if I killed it I wouldn't feel too bad buying a replacement. But $$'s still $$.
GL man!
Click to expand...
Click to collapse
You are right, it is a Verizon (XT1980-4) device and I cannot get the bootloader unlocked. I was only trying flash stock to unbrick it. I flashed the stock VZW firmware that I found somewhere without any error using fastboot.
Sure, I can give it a try with your baseband file. I already have stock Flash ready to re-flash it if necessary, and my device is not in working condition so nothing to loose.
Thanks for you reply.
I'll try to do that tonight when I get home from work. Sorry my responses have been so dumb. I'm still figuring it all out.
I would also need help to flash stock ROM. I have Z4 XT1980-3 with BL LOCKED. Already tried to reflash factory image via fastboot after an unsuccessful OTA upgrade. I can flash all parts except of boot, dspso and vbmeta. For these I get a "Preflash validation failed" error. So I have not been able to flash an entire factory image. I can only go to fastboot mode, nothing else. LMSA says my device is not compatible. RSD Lite says my device can not be switched to fastboot mode (but I already am in fastboot mode ???). So no joy with these. Can anybody give me any advice how to reanimate my device?
Maheshwara said:
I would also need help to flash stock ROM. I have Z4 XT1980-3 with BL LOCKED. Already tried to reflash factory image via fastboot after an unsuccessful OTA upgrade. I can flash all parts except of boot, dspso and vbmeta. For these I get a "Preflash validation failed" error. So I have not been able to flash an entire factory image. I can only go to fastboot mode, nothing else. LMSA says my device is not compatible. RSD Lite says my device can not be switched to fastboot mode (but I already am in fastboot mode ???). So no joy with these. Can anybody give me any advice how to reanimate my device?
Click to expand...
Click to collapse
I am also on same boat with Z4 XT1980-4 Verizon model. Bootloader is locked and Baseband missing on the fastboot screen. Please help if anyone have recover their phone from this.
Thanks
Related
okay so i just updated my droid razr hd and i had an unlocked bootloader, but no root, when i looked it was still unlocked and when i tried to restart my phone it would go to ap fastboot and i couldnt pass it and this happens everytime i turn it on, does anyone have any suggestions i can do? My android version is 4.1.2 and my system version is 9.20.1.XT926.Verizon.en.US. Anything would help.
D4V3Y said:
okay so i just updated my droid razr hd and i had an unlocked bootloader, but no root, when i looked it was still unlocked and when i tried to restart my phone it would go to ap fastboot and i couldnt pass it and this happens everytime i turn it on, does anyone have any suggestions i can do? My android version is 4.1.2 and my system version is 9.20.1.XT926.Verizon.en.US. Anything would help.
Click to expand...
Click to collapse
When you end up in Fastboot, what does it give for a reason? If you enter it because of the power/volume combo it will say so. If your update didn't work, it might say reason: flash failure (something like that...flash failed, flash something)
If you get the flash failure, I'd have to think something got mucked up during your update and now its just not able to boot, garbage or corrupted data where it expects good data.
If that is the case, there are tools/scripts in the developer portion of the forums (http://forum.xda-developers.com/showthread.php?t=2307439) that you can use to get your phone back to stock (pre OTA). You can reload the ROM fresh and reload your recovery fresh. It will erase everything on your phone...all your personal files. This should give you a functioning phone though.
You can try taking the update again after that.
Lenny
Thanks it worked
Hello, back in december I was trying to load up an app on my phone but in a video the guy said to download chainfire so I did and installed the driver and my phone got stuck in the warning unlocked bootloader screen and I really can't remember what I did but I did something with downloading the system restore image but it wouldn't work so I changed up the files and now my phone is stuck in fastboot and no longer is usable so I just threw it in my drawer and never used it again up until now here I am asking for help on how to resolve this issue. I'm no android techie so I really don't know much about anything other than rooting phones. My phone is a Moto G XT1031. Also I can't charge my phone because when I leave it, the phone just keeps rebooting and it really doesn't charge much.
UPDATE:
I managed to unlock the bootloader but now when I power it up, the device is stuck on the motorola screen.
If you can get into fastboot mode, try flashing a stock ROM for your phone.
audit13 said:
If you can get into fastboot mode, try flashing a stock ROM for your phone.
Click to expand...
Click to collapse
Thank bro it worked for me thanks a lot
Hello, I've bricked my device (( moto g xt1032, I bought the device from Tesco back in 2013 and I just wanted to get the lollipop update on my phone, I looked online and found this video: watch?v=-L44JqysUy8 it didnt do as intended it rebooted and my device was ok, so I looked again and came accross a thread here on XDA: http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
first mistake I made was doing step 2.1 instead of going straight to 2.2, my phone rebooted and got stuck in a boot loop (i think, it was a black powered by android screen) I looked on google yet again and found an article that told to clear the cache in recovery I did that and it didnt work, boot loop again, then I found a forum post saying that having bluestacks on your machine will cause a conflict I uninstalled that and started from scratch with the same problem, I re did the steps seen in the above youtube video thinking that would put my device back to normal and still stuck in bootloop with the blue motorola m logo, I cant enter recovery of the fast boot menu anymore and my battery doesnt seem to be charging, its essentially a paperweight.
paulh2k8 said:
Hello, I've bricked my device (( moto g xt1032, I bought the device from Tesco back in 2013 and I just wanted to get the lollipop update on my phone, I looked online and found this video: watch?v=-L44JqysUy8 it didnt do as intended it rebooted and my device was ok, so I looked again and came accross a thread here on XDA: http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
first mistake I made was doing step 2.1 instead of going straight to 2.2, my phone rebooted and got stuck in a boot loop (i think, it was a black powered by android screen) I looked on google yet again and found an article that told to clear the cache in recovery I did that and it didnt work, boot loop again, then I found a forum post saying that having bluestacks on your machine will cause a conflict I uninstalled that and started from scratch with the same problem, I re did the steps seen in the above youtube video thinking that would put my device back to normal and still stuck in bootloop with the blue motorola m logo, I cant enter recovery of the fast boot menu anymore and my battery doesnt seem to be charging, its essentially a paperweight.
Click to expand...
Click to collapse
im now back to the boot loop thing not much better lol, is it fixable or should i just not bother
If it is booting up, then probably it is soft bricked. Not hard bricked.
If it can detect in ADB, re-flash the recovery?
Thankyou both for your replies, I dont know why I bothered back in the day symbian was so much easier lol, im an absolute noob when it comes to this so how would i go about getting to the recovery you mention, i can get to the fastboot menu but after selecting recovery the phone just loops at the boot logo
SInce it is bootlooping, I'm not sure which ROM is currently on your phone.
Try and flash the recovery from the ROM you tried to install by finding the recovery.img file, boot the phone into fastboot, and type "fastboot flash recovery recovery.img" or, if using mfastboot commands, type "mfastboot flash recovery recovery.img".
If you can't get into recovery, flash the recovery from your original ROM.
If you still can't get into recovery, flash your stock ROM, one partition at a time.
In fastboot, which bootloader version is on your phone?
the last thing I flashed was the link provided in the youtube vdeo if that helps, ive done the recovery thing and it still loops, my bootloader hmm im not sure heres the details from the fast boot screen..
AP Fastboot Flash Mode (S)
41.13 (sha-7dc8e78, 2014-06-16 16:33:29)
Device is locked Status Code (0)
is it because my bootloader is locked, I fail
You need to unlock your bootloader via the motorola website.
Thanks for your reply it turns out its not eligible for unlock for some reason so I'm deciding its a decent paper weight and giving up, I really appreciate the replies and the time the posters have taken out to help, I'll know to take my time to read every detail if I decide to do this again, thankyou!!
Are you sure it's not eligible? I thought my Telus xt1032 was not eligible but it turns out I mistyped a couple of numbers.
I tried a few hours later and I got the code from Motorola.
audit13 said:
Are you sure it's not eligible? I thought my Telus xt1032 was not eligible but it turns out I mistyped a couple of numbers.
I tried a few hours later and I got the code from Motorola.
Click to expand...
Click to collapse
I copied and pasted direct from the cmd, I read on another forum that you needed to be logged into the phone with the Motorola account which I didn't
I don't recall logging into the phone, I just recall logging into the Moto site with a google ID.
Don't worry bro just try and you will be successful. I'm also bricked my Micromax Canvas A1 on first try.
audit13 said:
I don't recall logging into the phone, I just recall logging into the Moto site with a google ID.
Click to expand...
Click to collapse
Thanks ill try it again
lol i need to wake up, I had spaces when iIcopied from the cmd its working now... and I have the code!!!
and im unlocked ! so what do i do know, i dont want to ruin it all now
Excellent. Boot into fastboot and post your bootloader version. It should be 41.xx.
41.13 ? thats on the second line in the boot menu
You have a KK bootloader. I suggest downloading the stock 4.4.4 ROM for your carrier and flash everything except the gpt and motoboot file. Once you finish flashing all partitions via fastboot, use the phone's volume button to boot into recovery, wipe perform a full wipe, and reboot.
Ok, I've been reading around the forum for about a week, trying to solve a problem with an original moto g (falcon). Basically my cousin got the moto g a few years back, and I, in my ignorance, tried to root the device for him. What I can remember was oem unlocking the bootloader with Motorola's unlock code through their website and adb. then my cousin freaked about the warranty warning on the boot animation, and decided against it. So cut to now, I'm a little more experienced, the phone's years old now, and he'd like to refresh it with a new rom, which I suggested, trying to help him. So forgetting what I'd originally done those years ago, I started the process of rooting the phone, installing a custom recovery, to hopefully put a lighter rom on it for him.
OK so it's a UK Retail on tesco mobile, moto g xt1032 running Android 5.1.
in bootloader menu it says "Device Locked status 2", dunno what this is in relation to.
first I checked the bootloader was still unlocked, and adb said it was. so I tried to use CF-autoroot to finish the job, but there was issues. it restarted the phone into fastboot mode, but when the script started, pc end did nothing, on the phone it said, "flashing unlock" and just sat there for 10-15mins doing nothing (i left it the time, just incase it was doing it).
So i read a little more, and found because i'd already unlocked the bootloader, I could just flash a custom recovery and root from adb? so I downloaded the latest twrp and tried. I was unable to do so. it said the partition wasn't the right size? should have documented it, but really didn't expect to run into any problems.
So I restarted and tried to do my usual fallback, and flash the factory image and start again, But couldn't find a source for the specific img, and tried to keep fighting on.
So I noticed that the phone wouldn't respond to adb or fastboot once in fastboot mode, when in android with usb debugging, no problems, in fastboot, didn't show up as adb devices?
I tried booting into the recovery from the bootloader menu, and got a no command. So there isn't a recovery, and I can't flash a new one? if i could find the stock recovery, I would try that.
so apart from deleting all his apps and settings, I hadn't solved the problem at all, and had to leave the job there as I couldn't find a solution.
I know this isn't the most detailed, but I've done this with quiet a few phones now, and felt I was pretty competent. I see everyday as an excuse to learn more, and like to think I have humility. So, I'm assuming I did something those years ago to damage the recovery? I'm running out of ideas, and was hoping someone could point me in the right direction?
I've lurked on xda for years, and learned so much about this kind of thing through my past experiences, but I'm stumped this time, and feel obliged to resolve the problem, as it was me who caused it.
TL DR
Can't flash recovery, no command when I try to open recovery, trying to either factory image back, or root/custom recovery it.
any insight would be much appreciated.
Hi. I just rooted and installed CM13 on an old XT1034 about two days ago. I am also sort of a ROM noob, I have ROMed a few devices, but usually but following strict step by step guides I have found here on XDA. Over the years I have some minor understanding of the process now.
I also got the "No command screen" when trying to get into TWRP recovery. The issue seems to be that if you reboot via ADB and the ROM launches it will automatically rewrite the recovery to the stock one, and when you try to go to recovery from fastboot, it gives you the "no command" error. Apparently you can get to the stock recovery from there by a hardware key combo, something like holding up vol for 10 sec then a quick press of power (I can't remeber the exact key sequence or what forum I read it in). If it does this you have to reflash TWRP again. This issue is mentioned here (http://wiki.cyanogenmod.org/w/Install_CM_for_falcon) in step 8 about installing recovery. What I ended up doing was after the flash of TWRP via ADB, I manually powered down, then manually bood into fastboot by holding volume down and power, and selecting recovery. This was a bit fiddly and I had to attempt it a few times but eventually it worked and TWRP installed.
The issue with the phone not being recognized may be due to incorrect drivers. I had no issue with this because I installed the official driver package from Motorola. It is available in their website in the developer section. I don't have the URL right now.
Hopefully this helps, for me CM13 Official has been an a stable fresh start for this old device.
As per title, it just happened while I was using the phone while charging. Trying my luck as I'm not in the country(Australia) that I bought my Pixel from. Grateful for any suggestion that the sub can provide. Non rooted stock rom
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Yes only bootloader. What you have mentioned do not require recovery mode right ? Cos I can't boot into it. Thanks for your reply
k.s.deviate said:
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Click to expand...
Click to collapse
The bootloader would have needed to have been unlocked already.
indifferent1 said:
The bootloader would have needed to have been unlocked already.
Click to expand...
Click to collapse
no it doesnt, I suggested unlocking the bootloader first, that way it factory resets. this might fix the problem, if not its unlocked so he can flash the factory image.
Bump? I'm having this problem as well.
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
graymoment said:
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
Click to expand...
Click to collapse
I'm having the same issue. My wife's Pixel entered a continuous boot loop today. It only loads the white screen that says "Google." I can enter the bootloader, but when I select "recover," it goes back to the bootloop. As far as I know, she is on Android 8.1, debugging mode is off and the phone is 100% factory.
If anyone has solved this issue, it would be greatly appreciated!
Thanks
has anyone figured this out?? this happened to me today, i was using the phone, the poof it restarted itself and stayed in a boot loop. i can get into the recovery, i tried wipe/factory reset. any suggestions? google told me i need to send it to whatever company to get it fixed or get a new phone. verizon told me to go through insurance. insurance told me to go through verizon because i may be able to use the extended warranty. went back to verizon but they wont take it because the screen cracked a year ago. its not a deep crack and it didnt affect the phone at all, never had an issue. so now i go back to assurion and now they need an affidavit about my screen being cracked. im at a loss.... i havent rooted a phone since my droid x, then s3 days. so im essentially new again!
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
thedosbox said:
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
Click to expand...
Click to collapse
I had the same thing happen yesterday (not long after the Android 10 update). I was finally able to get it to boot after multiple tries and it stayed up long enough for me to enable "OEM unlocking" in Developer options. Now at least I have the option of unlocking the bootloader and re-flashing the OS with an image directly from Google.
Has anyone been able to get past this problem by reflashing the image? I suspect the underlying problem is some kind of hardware fault with eMMC, DDR, or the SOC itself.
One other interesting behavior I noticed is that the only way to shut it down and stop the bootloop is to select the "Power off" option in the bootloader menu. However, if I plug it in to charge when it is fully powered "off", it will start up the bootloop again.
Same sitution here. A couple of days after installaing it suddenly went inte a G-bootloop frenzy.
Erratic though, sometimes I could boot up (2-3/40 boots) but then it froze and started again.
Also Recovery and Safemode is very hard to get into.
Got in once or twice out of 100 boots, Bootloader Fastboot is generally reachable though.
It exhausted the battery and now I'm holding off trying to interfere, until I get more info off the net.