Related
Let me start off by saying that I just got this phone and decided to install a custom recovery and rom on it. As I do with all my phones that allow me to do so. I got the phone with android 4.4.4 on it, rooted it with Kingroot, and proceeded to use the XZDualrecovery tool to install TWRP. After that was all done, I downloaded the Z5 Expierience Rom, and I'm going to take a long shot here and say that I must have majorly missed something. Because after flashing that Rom in TWRP, my phone will do next to nothing. All went fine with the install of the ROM itself. Wiped Dalvik/Cache before restart.
If i hold down the power button I get a single vibration and then the phone does nothing (Does not even turn on backlight). If I plug the phone into my computer the phone will start a sequence of Red (LED), Green (LED), Vibrate. It does this aobut once every second. I can access Fastboot if I hold the volume + button, the LED then goes solid blue and the phone stops the LED - Vibration sequence. The only problem I have, as far as just not being able to Flashtool it back to life is, not being able to get the phone to go into Flashmode. No matter what I do, the phone will not let me get it into Flashmode. Im sure there is a good reason for this, I am just not sure what it is.
I've been flashing Roms and Recoveries since G1 days. I'm usually pretty decent at figuring this kind of thing out, but this thing has got me puzzled. I clearly went terribly wrong somewhere here, hopefully someone who knows this phone much better than I can point me in the right direction and hopefully get my less than 10 hour phone working again.
P.S. - If the phone is plugged into the wallcharger is does something similar to when it is plugged into my computer, but instead of a Sequence of Red - Green - Vibrate, I just get a steady red blink folled by a vibration. The phone will continue to do so until unplugged from the charger.
All help is very appreaciated!
I'm having the same issue. Anyone with the fix would be appreciated
Not sure what to try at this point!
I've been looking non-stop in my free time for a fix for this thing, and no matter what I do I keep getting the same results. Not really sure where to go from here, I have tried Flashtool, Emma, and PC Compainion out of desperaity. I tried all three options on teo seperate computers (One Windows 10 and the other Windows 7.) I have also tried multiple cables. No matter what I do all this thing will do is blink at me and vibrate. Is this thing hard bricked? I read its close to impossible to hard brick one of these phones. I'm wiling to accept that I have if that is the case. Just would like an opinion from someone who has some knowledge with these.
Same here, someone plz help.
If is only a change of batery or the phone is dead completly, an the stop trying to revive it.
Thanks .
Nick1801 said:
Let me start off by saying that I just got this phone and decided to install a custom recovery and rom on it. As I do with all my phones that allow me to do so. I got the phone with android 4.4.4 on it, rooted it with Kingroot, and proceeded to use the XZDualrecovery tool to install TWRP. After that was all done, I downloaded the Z5 Expierience Rom, and I'm going to take a long shot here and say that I must have majorly missed something. Because after flashing that Rom in TWRP, my phone will do next to nothing. All went fine with the install of the ROM itself. Wiped Dalvik/Cache before restart.
If i hold down the power button I get a single vibration and then the phone does nothing (Does not even turn on backlight). If I plug the phone into my computer the phone will start a sequence of Red (LED), Green (LED), Vibrate. It does this aobut once every second. I can access Fastboot if I hold the volume + button, the LED then goes solid blue and the phone stops the LED - Vibration sequence. The only problem I have, as far as just not being able to Flashtool it back to life is, not being able to get the phone to go into Flashmode. No matter what I do, the phone will not let me get it into Flashmode. Im sure there is a good reason for this, I am just not sure what it is.
I've been flashing Roms and Recoveries since G1 days. I'm usually pretty decent at figuring this kind of thing out, but this thing has got me puzzled. I clearly went terribly wrong somewhere here, hopefully someone who knows this phone much better than I can point me in the right direction and hopefully get my less than 10 hour phone working again.
P.S. - If the phone is plugged into the wallcharger is does something similar to when it is plugged into my computer, but instead of a Sequence of Red - Green - Vibrate, I just get a steady red blink folled by a vibration. The phone will continue to do so until unplugged from the charger.
All help is very appreaciated![/QUOTE
!st question is did you flash the correct rom for your device?
If you can go to recovery, then try to flash another rom,
Or use adb/fastboot to try and flash recovery img and use fastboot to reboot recovery.
Alternatively you may have to flash a kernel relevant to your rom.
Click to expand...
Click to collapse
Try this and see if it helps.........
If your phone is unbranded, i.e. not locked to a carrier, download a any generic(customized) firmware for your device through Xperifirm and flash it through Flashtool. It will wipe all your data (excluding your microSD, of course) but you don't have any other choice. This is most probably unbrick it...... So, try it and all the best.:good:
EDIT: If you've tried it, then go for this. Luckily you've fastboot still working, right? So, go to fastboot mode and flash a recovery image through it. It may take a lot of time but if recovery works, you can install a stock based rom for your device and then go back to stock firmware through Xperifirm and Flashtool.....
The phone is a Verizon model. I've tried to unlock the bootloader using command prompt following the sony instructions, after recieving my unlock key. I am able to connect to the phone and all of the fastboot commands work until I try and run the one to actually unlock the bootlaoder. That says the it is "not allowed." I think that is because I never enabled OEM Unlocking in the developers menu though. Not sure if there is a stock kernel I should try an flash through fastboot. Or if there is a stock recovery file that is flashbable through fastboot with a locked bootloader. The phone is definetley working in fastboot and somehow still knows how to charge. Im pretty sure at this point the problem is that the phone has a custom rom on it but the bootloader is still locked. I cannot unlock the bootloader because I can't get in Android to enable the proper options. Have also tried Flashtool for unlock the bootloader, along with extracting kernel sins from a stock 4.4.4 and a stock 5.0.1 FTF and trying to flash them. Since the begining I have still seen no change in the phone behavior.
Nick1801 said:
The phone is a Verizon model. I've tried to unlock the bootloader using command prompt following the sony instructions, after recieving my unlock key. I am able to connect to the phone and all of the fastboot commands work until I try and run the one to actually unlock the bootlaoder. That says the it is "not allowed." I think that is because I never enabled OEM Unlocking in the developers menu though. Not sure if there is a stock kernel I should try an flash through fastboot. Or if there is a stock recovery file that is flashbable through fastboot with a locked bootloader. The phone is definetley working in fastboot and somehow still knows how to charge. Im pretty sure at this point the problem is that the phone has a custom rom on it but the bootloader is still locked. I cannot unlock the bootloader because I can't get in Android to enable the proper options. Have also tried Flashtool for unlock the bootloader, along with extracting kernel sins from a stock 4.4.4 and a stock 5.0.1 FTF and trying to flash them. Since the begining I have still seen no change in the phone behavior.
Click to expand...
Click to collapse
dude I'm from the Verizon side yea like you have an bootloader status unlock no so your not going to change that and you can only flash Verizon z3v stuff you are really lucky if you can still get to fastboot after doing this. Use flashtool and flash a Verizon ROM from the z3v section only and pray it works.
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.
Hi, well it looks like i have probably hard bricked my phone. After updating to nougat i decided to do afresh clean install. I wanted my phone to as if i had just bought it and came with nougat/emui 5 installed. So i did a factory reset from within the settings menu. But then i thought i would completely erase everything and start from the latest build before nougat, so emui 4.1.2/ marshmallow. So after wiping all the partitions in twrp and then doing a volume up + power to do complete factory wipe followed by using the three button method to install the B130 UPDATE.APP in dload folder on my sdcard, all worked as expected. The update completed at 100% and then rebooted. So there i am waiting for my phone to boot to start the setup process as i have done dozens of times before...BUT...my phone will not boot to the initial setup wizard. It just stays stuck on the Honor logo pulsing animation for ever and ever and ever!!!!!!
So i do the volume up + power button to get to stock recovery and do factory wipe and cache wipe as well. It works as expected so i reboot and once again use the 3 button method to install the update.app on my sdcard. That works as expected and at 100% says its succeeded and reboots. Once again i wait for it to boot to the initial setup wizard but....ALAS...it stays on that DAMN pulsing Honor logo. Ive tried rebooting it several times, redoing the factory wipe and install several times, but nothing. Ive gone into fastboot mode (volume down + power) to try and flash the boot.img and system.img ive extracted from update.app but get the error message -- remote: command failed -- and the same if i try to unlock bootloader. Obviously its not going to work because my bootloader isnt unlocked and nor can i got in to developer settings to enable oem unlock and turn USB debugging on because my phone wont boot past that bloody honor logo.
The only thing i havent done yet is to use eRecovery but i dont have broadband and i doesnt seem to work over public wifi! So i will go to my friends tomorrow and use their broadband and hopefullly eRecovery will download/restore the latest firmware. The only other thing i can think of is to download the original nem-l51c432B102 that came with my phone when bought, extract the update.app file and replace the B130 i have on my sdcard dload folder at present.
Sorry for such a long post but i wanted to expalin evrything in detail to hopefully resolve my problem without going backwards and forwards with questions and answers and taking for ever.
So ANYONE and EVERYONE who managed to read the whole post, if you have even the slightest idea of how to get my phone working, please oh please share it with me. Also my phone is still under warranty so if i needed to send it to a huawei centre to get it fixed would they do it and do it for free??? because eseentialy all i did was a factory wipe/reset and install a frmware and it goes KAPUT!! thats not my fault right????!!???
Thank you to one and all for any wisdom you can share.
please....please.......help???
So sorry for my original long post people, i simply wanted to give as much detail and info as possible because being vague doesnt help anyone. It seems that might have worked against me.
Please,please any suggestions would be appreciated to the N'th degree! I have tried everything i can think of and i am truly desperate now. I dont understand why i cant get it to work...
I can go into stock recovery and wipe the cach and do factory reset and that works fine, no errors.
I can hold the 3 buttons down to install the firmware package(ive got update.app from B130 build) and that works fine, gets to 100% and says 'success' and then reboots, with no errors.
But either way the phone refuses to boot past the honor logo boot animation and ive left it for hours hoping,praying, it will work after the 32nd time...
I can access fastboot but that is useless because my bootloader is not unlocked and i cant get to developer options to enable 'usb debugging' and 'oem unlock'. So i just get error message 'remote: Command Failed' with any command i type.
But thats madness, i cant comprehend why it wont boot because everything seems to work!?!
There has to be a way to get my device functioning again.
I am pulling my hair out, i am at a complete loss, it doesn't make sense. PLEASE ANYONE ..... please help....
Thanks HONOR-able enthusiasts for any help, no matter how small!
I wanted to flash a ROM, so I unlocked the bootloader and installed TWRP successfully. Then I downloaded the ROM, factory reset, format data, and installed the ROM. When the phone booted, it showed a black screen, and only the hardware buttons worked. I could lock the phone, and if I pressed the power button, it would "light up" the screen, but still black. Holding the power button gave me the power menu from the ROM I flashed (advanced boot options).
I did another factory reset and flashed the ROM again, and from thereon out, it never made it to the lock screen again.
I have attempted the eRecovery function, but it doesn't fix the issue either. The firmware downloads and is installed, but then it just boot loops for a couple times, then goes back to the screen suggesting a recovery operation.
Is this permanent now, or can it can still be salvaged?
Huawei Mate 9
Version: MHA-L29C567B190
*Edit:
The ROM I attempted to install was ROM-Aur-v1.5.
I had no ROM installed previously; phone was stock.
I did not manipulate the OEM info; all I did was unlock the bootloader with the unlock code I was given by the Huawei online site.
Solution:
Apparently, unlocking the bootloader several times seems to have solved the issue.
Once again, thanks to everyone who helped me out with this.
Which rom did you install.
What was the rom, which was installed before?
Did you change branding via manipulating oem info?
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
use another Android phone download huaweifirmware finder on the google play ，select mha-l29c567，than select dns update，change your router dns，you can do erecovery after setup dns！
sweetjuice said:
use another Android phone download huaweifirmware finder on the google play ，select mha-l29c567，than select dns update，change your router dns，you can do erecovery after setup dns！
Click to expand...
Click to collapse
Thank you for your response. However, I tried it and it didn't work for me. I downloaded the app, checked the firmware was available, registered the update, changed my router DNS, and then attempted the eRecovery. It downloaded the package then installed it, but the same problem continues.
audioralf said:
Which rom did you install.
What was the rom, which was installed before?
Did you change branding via manipulating oem info?
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Click to expand...
Click to collapse
The ROM I attempted to install was ROM-Aur-v1.5.
I had no ROM installed previously; phone was stock.
I did not manipulate the OEM info; all I did was unlock the bootloader with the unlock code I was given by the Huawei online site.
Which stock? Model and firmware Version?
My device: Mate 9 supersu B190 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
you can install a full firmware with hwota method.
audioralf said:
Which stock? Model and firmware Version?
My device: Mate 9 supersu B190 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Click to expand...
Click to collapse
Is this the information you're asking for?
Huawei Mate 9
Version: MHA-L29C567B910
I don't know how to get any other information (other than the IMEI and SN which are on the box), since I can't make it past the boot logo screen.
mavera said:
you can install a full firmware with hwota method.
Click to expand...
Click to collapse
How would I go about doing that? I can't take the phone past the boot logo screen; it just boot loops then goes to the eRecovery screen. And when I try that recovery method, it only gives me the option to download latest version over WiFi and install it. Which does not fix the problem.
cr33p3r1n1134 said:
How would I go about doing that? I can't take the phone past the boot logo screen; it just boot loops then goes to the eRecovery screen. And when I try that recovery method, it only gives me the option to download latest version over WiFi and install it. Which does not fix the problem.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 use this guide. You can change your reg code as c432, c636 etc. Only you must know your unlock code.
mavera said:
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 use this guide. You can change your reg code as c432, c636 etc. Only you must know your unlock code.
Click to expand...
Click to collapse
Rebranding is not really necessary.
@OP
For MHA-L29C567B190 (you wrote B910 which I assume is incorrect), use:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1356/g77/v84935/f2/full/update.zip
http://update.hicloud.com:8180/TDS/...35/f2/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/.../v84935/f2/full/hw/usa/update_full_hw_usa.zip
I don't want to count my chickens before they hatch, but somehow it appears my phone is now working again. I did not rebrand nor update it. I simply unlocked the bootloader, AGAIN (which is what confuses me since I tried it before and it didn't work, at all). Regardless, I am not complaining!
I am not marking this thread as solved yet, just in case, but I will do so later on in the day if the phone continues working as before.
I want to thank all of you for your time and input, I really appreciate it.
Also, I'm never trying to flash anything on this phone again; I have learned my lesson. :/
cr33p3r1n1134 said:
I don't want to count my chickens before they hatch, but somehow it appears my phone is now working again. I did not rebrand nor update it. I simply unlocked the bootloader, AGAIN (which is what confuses me since I tried it before and it didn't work, at all). Regardless, I am not complaining!
I am not marking this thread as solved yet, just in case, but I will do so later on in the day if the phone continues working as before.
I want to thank all of you for your time and input, I really appreciate it.
Also, I'm never trying to flash anything on this phone again; I have learned my lesson. :/
Click to expand...
Click to collapse
Unlocking bootloader does a factory reset so that might be why it's working again
cr33p3r1n1134 said:
I wanted to flash a ROM, so I unlocked the bootloader and installed TWRP successfully. Then I downloaded the ROM, factory reset, format data, and installed the ROM. When the phone booted, it showed a black screen, and only the hardware buttons worked. I could lock the phone, and if I pressed the power button, it would "light up" the screen, but still black. Holding the power button gave me the power menu from the ROM I flashed (advanced boot options).
I did another factory reset and flashed the ROM again, and from thereon out, it never made it to the lock screen again.
I have attempted the eRecovery function, but it doesn't fix the issue either. The firmware downloads and is installed, but then it just boot loops for a couple times, then goes back to the screen suggesting a recovery operation.
Is this permanent now, or can it can still be salvaged?
Huawei Mate 9
Version: MHA-L29C567B190
*Edit:
The ROM I attempted to install was ROM-Aur-v1.5.
I had no ROM installed previously; phone was stock.
I did not manipulate the OEM info; all I did was unlock the bootloader with the unlock code I was given by the Huawei online site.
Solution:
Apparently, unlocking the bootloader several times seems to have solved the issue.
Once again, thanks to everyone who helped me out with this.
Click to expand...
Click to collapse
I know this is a really old thread, but this is happening to me too. How did you unlock the bootloader again? adb isn't recognizing my device? Any suggestions?
ji_mestone said:
I know this is a really old thread, but this is happening to me too. How did you unlock the bootloader again? adb isn't recognizing my device? Any suggestions?
Click to expand...
Click to collapse
Unfortunately, I do not remember the exact process I performed in order to unlock the bootloader the final time.
I remember I had to play a lot back and forth with adb and fastboot. Have you checked if fastboot recognizes your phone?
I believe that what I did was start from the very beginning; installing a recovery (I used TWRP). If fastboot recognizes your phone, and you are able to install a recovery, from there I'm pretty sure adb will recognize your phone and then you can unlock the bootloader.
I would recommend not trying anything fancy. Only recovery and bootloader.
I hope this answers your question and helps you out. Best of luck.
cr33p3r1n1134 said:
Unfortunately, I do not remember the exact process I performed in order to unlock the bootloader the final time.
I remember I had to play a lot back and forth with adb and fastboot. Have you checked if fastboot recognizes your phone?
I believe that what I did was start from the very beginning; installing a recovery (I used TWRP). If fastboot recognizes your phone, and you are able to install a recovery, from there I'm pretty sure adb will recognize your phone and then you can unlock the bootloader.
I would recommend not trying anything fancy. Only recovery and bootloader.
I hope this answers your question and helps you out. Best of luck.
Click to expand...
Click to collapse
Thanks for responding! I'm still at a loss two hours later.
Unfortunately USB debugging got turned off somewhere along the way, so ADB and fastboot aren't recognizing my phone. I can still access TWRP, but when I try adb sideload in TWRP is just says it's starting but keeps loading and nothing comes up and I get a message on my computer that says "the last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
ji_mestone said:
Thanks for responding! I'm still at a loss two hours later.
Unfortunately USB debugging got turned off somewhere along the way, so ADB and fastboot aren't recognizing my phone. I can still access TWRP, but when I try adb sideload in TWRP is just says it's starting but keeps loading and nothing comes up and I get a message on my computer that says "the last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
Click to expand...
Click to collapse
Yeah, the ADB sideload problem also happened to me. Eventually gave up on that.
I hope I'm allow to post links.
But here is a link to something I remember using.
http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/
Using those tools mentioned in that post helped me out. I had to do a lot of experimenting with that as well. Every time I connected and disconnected my phone from my computer, I checked which were the references that needed deleting, then deleted them. It was tedious, but I'm not expert, so maybe I took the long way.
Maybe try using those tools?
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