Related
Mine motog5s updated to stock fw and root uninstalled after it it hangs on boot screen. I flashed stock fw again with fastboot but after restart mobile didn't display anything not even vibrate just blinking notification when connect usb wire . how to unbrick only shows qualcomm hs dloader 9008 what to do, pls. reply.
You cannot log into fastboot mode?
qualcomm hs dloader 9008 = EDL mode, you should be able to restore with QFIL: https://forums.lenovo.com/t5/MOTO-E-1st-Gen/Moto-E-Not-Boot-Up/td-p/3231144 but it looks like motorola doesn't provide the files ... most likely you'll need a service center
Do not use QFIL. To unbrick, we need the blankflash file for G5S. And it is not on the Internet yet. Do not use the blankflash of any other models. Your best bet is to take the phone to a service center.
---------- Post added at 11:46 AM ---------- Previous post was at 11:46 AM ----------
Did you try holding the power down button and turning on the phone to enter bootloader?
Thanks for the reply the service center guys sayin as bootloader is unlocked out of warranty. They said mobile is rooted without checking the mobile as its not turning on, how they can say that its rooted . They just talking on phone with other persons but cant provide any solution what can be done.
Please provide any other solution.
ASHDCBZ said:
Thanks for the reply the service center guys sayin as bootloader is unlocked out of warranty. They said mobile is rooted without checking the mobile as its not turning on, how they can say that its rooted . They just talking on phone with other persons but cant provide any solution what can be done.
Please provide any other solution.
Click to expand...
Click to collapse
You downloaded the unlock key from Moto website by giving them your device serial number. That's how they know you unlocked bootloader. Service center won't help you. But fortunately, there is a way to revive your phone. But I'm not getting the blankflash file anywhere.
Tell me what exactly did you do to your phone.
Thank you,
Ok I just flahsed & tried stock roms, root & custom roms. Then I flashed stock rom of mine region firmware npp26.102.19 then motorola gave the updates to npp26.102.55-1 Dec. patch. Then next day new update came Feb patch npp26.102.55-4 just after it mobile started hanging & when restart it stuck on boot, not booting just stuck on boot animation. I tried TWRP recovery it said encrypted then I entered the unlock pin then it shows all the folders. Then I again fastboot npp26.102.19 to solve the issue but after flashing & restart it did not boot nor screen on no vibration tried several times but no response, when connect with pc or charger a white notification light blinking only & it detected as QHUSB_BULK something like that then I searched for it & install driver then shows as qualcomm dloader 9008.
Ok you should never flash an older bootloader over never one. It's a classic mistake that you made. I suppose we need the blankflash file to repair your phone. Let's wait to see what senior devs say.
ShattrdChain said:
Ok you should never flash an older bootloader over never one. It's a classic mistake that you made. I suppose we need the blankflash file to repair your phone. Let's wait to see what senior devs say.
Click to expand...
Click to collapse
Hmmmmmmmm
Please provide blankflash soon file I'll try.
there is no notification light on my g5s. what is blinking on yours?
Andrew Joseph said:
there is no notification light on my g5s. what is blinking on yours?
Click to expand...
Click to collapse
Next to front flash right side a white light is blinking. Try pressing power button then it will show.
nope. can't find it. the g5s plus has a 'secret' notification light. can't find anything about the g5s having the same.
what phone do you have?
Andrew Joseph said:
nope. can't find it. the g5s plus has a 'secret' notification light. can't find anything about the g5s having the same.
what phone do you have?
Click to expand...
Click to collapse
Its Moto G5s XT1795.
when you connect your device with PC what driver it shows fastboot, ADB or mtp or else QHUSB_BULK qualcomm dloader 9008.
does this only happen when you root your phone?
Can someone Help Us?
Hey, i have unlock the bootloader of my phone and flash the updated rom in my device. After that my phone is just off, i press the power button but it don't turn on, connect do pc or chargers but it not turn on, that is the hard brick, can i have a solution to this?
I have this:
"The Hardbrick tutorial you always craved for
Let's get some things straight
Forget flashing stock firmware anymore this makes permanent changes to your phone's firmware but this is the only thing that will resurrect the fallen lad
Requirements
Albus blankflash
Qualcomm drivers
Adb and fastboot
Bootloader from Albus
Steps
Get the Qualcomm drivers installed… make sure you disable Driver Signature Enforcement for your windows version
Run the script in albus blankflash to get into a dummy bootloader
Now flash bootloader and partition files and recovery from addison2potter.zip
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash recovery recovery.img
Now try flashing a stock firmware it will flash but you will not be able to boot right now
Now flash or boot TWRP recovery
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
Now flash the debloated stock ROM or the TWRP Flashable stock build by Gtrcraft
(This is needed to get RIL back )
You should be able to boot into the stock ROM now
Now you can go back to TWRP and flash any ROM of your choice ".
But i don't know if it will work, because i don't know if this files can match my model: moto g5s xt1792
And sorry but i can't post links yet.
Please Help Us.
brunovsc said:
Hey, i have unlock the bootloader of my phone and flash the updated rom in my device. After that my phone is just off, i press the power button but it don't turn on, connect do pc or chargers but it not turn on, that is the hard brick, can i have a solution to this?
I have this:
"The Hardbrick tutorial you always craved for
Let's get some things straight
Forget flashing stock firmware anymore this makes permanent changes to your phone's firmware but this is the only thing that will resurrect the fallen lad
Requirements
Albus blankflash
Qualcomm drivers
Adb and fastboot
Bootloader from Albus
Steps
Get the Qualcomm drivers installed… make sure you disable Driver Signature Enforcement for your windows version
Run the script in albus blankflash to get into a dummy bootloader
Now flash bootloader and partition files and recovery from addison2potter.zip
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash recovery recovery.img
Now try flashing a stock firmware it will flash but you will not be able to boot right now
Now flash or boot TWRP recovery
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
Now flash the debloated stock ROM or the TWRP Flashable stock build by Gtrcraft
(This is needed to get RIL back )
You should be able to boot into the stock ROM now
Now you can go back to TWRP and flash any ROM of your choice ".
But i don't know if it will work, because i don't know if this files can match my model: moto g5s xt1792
And sorry but i can't post links yet.
Please Help Us.
Click to expand...
Click to collapse
Yes tried this & other blank flash it show only this-----
Failed identify board. Wrong package?
ERROR: error loading package
FAILED: qb_flash_singleimage()->error loading package
other tried this also----------
Found this can anyone try
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
qfil also not flashing sahara error.
I have tried this but there's an error
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
em QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
em QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
ASHDCBZ said:
Its Moto G5s XT1795.
when you connect your device with PC what driver it shows fastboot, ADB or mtp or else QHUSB_BULK qualcomm dloader 9008.
Click to expand...
Click to collapse
i haven't tried to root or connect via adb or anything else. my phone is just plain stock from factory.
brunovsc said:
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
em QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
em QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Same error shows in Qfil.
Andrew Joseph said:
i haven't tried to root or connect via adb or anything else. my phone is just plain stock from factory.
Click to expand...
Click to collapse
So is it not switch on or displaying anything.
I tried downgrading my G7 Play by flashing the stock rom for the phone. Now it will say "bad key" and keep bootlooping until eventually it says "Start Up Failed: Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant. AP Fastboot Flash Mode (Secure) No bootable A/B slot Failed to boot Linux, falling back to fastboot. Fastboot Reason: Fall-through from normal boot mode USB connected."
Any ideas how to fix this?
jpereira611 said:
I tried downgrading my G7 Play by flashing the stock rom for the phone. Now it will say "bad key" and keep bootlooping until eventually it says "Start Up Failed: Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant. AP Fastboot Flash Mode (Secure) No bootable A/B slot Failed to boot Linux, falling back to fastboot. Fastboot Reason: Fall-through from normal boot mode USB connected."
Any ideas how to fix this?
Click to expand...
Click to collapse
You can't downgrade. Try flashing the most recent stock firmware through the bootloader/fastboot or use rsdlite
jpereira611 said:
I tried downgrading my G7 Play by flashing the stock rom for the phone. Now it will say "bad key" and keep bootlooping until eventually it says "Start Up Failed: Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant. AP Fastboot Flash Mode (Secure) No bootable A/B slot Failed to boot Linux, falling back to fastboot. Fastboot Reason: Fall-through from normal boot mode USB connected."
Any ideas how to fix this?
Click to expand...
Click to collapse
Try
Moto Smart Assistant
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my perry_f using XDA Labs
Hello friends
a friend brought me a Moto G7 Play (XT1952-2), and said he had forgotten the password, the email and all, to try to recover, he tried to flash, but did not unlock the bootloader, did not enable USB debugging and did not enable OEM unlock and yet downgraded on mobile.
The result is that the phone no longer leaves the Start Up Failed screen, it shows the following messages:
Fastboot AP Flash Mode (Secure)
SSM: Android checking failed.
No bootable A / B slot
Failed to boot Linux, failing back to fastboot
Fastboot Reason: Falling Through Normal Boot Mode
I already tried to unlock the bootloader, but as the OEM unlock option is not enabled, I could not. I tried to flash with the same rom as before or with a more current one and it didn't change anything either. I've tried basically everything I found in the forums. Can someone give me an idea of what to do?
Tks!
riickseven said:
Hello friends
a friend brought me a Moto G7 Play (XT1952-2), and said he had forgotten the password, the email and all, to try to recover, he tried to flash, but did not unlock the bootloader, did not enable USB debugging and did not enable OEM unlock and yet downgraded on mobile.
The result is that the phone no longer leaves the Start Up Failed screen, it shows the following messages:
Fastboot AP Flash Mode (Secure)
SSM: Android checking failed.
No bootable A / B slot
Failed to boot Linux, failing back to fastboot
Fastboot Reason: Falling Through Normal Boot Mode
I already tried to unlock the bootloader, but as the OEM unlock option is not enabled, I could not. I tried to flash with the same rom as before or with a more current one and it didn't change anything either. I've tried basically everything I found in the forums. Can someone give me an idea of what to do?
Tks!
Click to expand...
Click to collapse
Download Your Latest ota zip from
https://mirrors.lolinet.com/firmware/moto/channel/official/
then flash via rsd lite that will fix your phone and reset it
Help download
motorola/aljeter/aljeter:9/PPPS29.55-35-12-3/a0b9b:user/release-keys
Hi, I reciently got an Moto Z2 play the Verizon version with 3gb ram. I search a tutorial on youtube to upgdate Android 9 but i dont unlock the bootloader ando now just stay in recover mode, i can´t pass frome there. Help pliz. I already try the Lenovo Moto assistant but nothing.
PD: in the bootloader says: ERROR: Failed to pass validation, back up to fastboot
Fasboot reason: Fall-through from normal boot mode.
Isaac33ag said:
Hi, I reciently got an Moto Z2 play the Verizon version with 3gb ram. I search a tutorial on youtube to upgdate Android 9 but i dont unlock the bootloader ando now just stay in recover mode, i can´t pass frome there. Help pliz. I already try the Lenovo Moto assistant but nothing.
PD: in the bootloader says: ERROR: Failed to pass validation, back up to fastboot
Fasboot reason: Fall-through from normal boot mode.
Click to expand...
Click to collapse
Hellow dear i have already this problem but i installed verizon software asistant on my pc and install online frimware but download when flashing start it says device not conected so i tried same frameware manually from adb fastboot
@Isaac33ag
Hello everybody, I have a problems with unbricking Note 8 Pro - begonia - M1906G7G.
It stuck in boot loop. Bootloader is locked.
I have tried that python bypass and flashing firmware using SP Flash Tool. I get success / done message after a while, but when I power the phone, there are no changes. Phone is sitll in boot loop.
Is there anything, what can I do?
Thank you in advance!
EDIT:
Have just tried to flash TWRP, now I'm getting "system has been destroyed" error. So flashing probably works. Problem must be somewhere else.
If you dont care about data (I think you dont because you flashed by Sp flash tool), just unlock bootloader and flash by Sp Flash Tool again. Maybe you flash fastboot rom not same region with stock phone with locked bootloader. This is the way to unlock bootloader unofficial way you can try.
Kirasu2080 said:
If you dont care about data (I think you dont because you flashed by Sp flash tool), just unlock bootloader and flash by Sp Flash Tool again. Maybe you flash fastboot rom not same region with stock phone with locked bootloader. This is the way to unlock bootloader unofficial way you can try.
Click to expand...
Click to collapse
At first, I could not use that tool. Everytime I tried, I get this error: "mtk: error: argument cmd: invalid choice: 'xflash'".
I had to edit the mtkclient-gui.py with this two commands (from github)
subprocess.call(f"{runtime} mtkclient/mtk e metadata,userdata,md_udc")
subprocess.call(f"{runtime} mtkclient/mtk da seccfg unlock")
Now after running the commands I get this in log: "Failed to format all partitions." and after that: "
100.0% Write (Sector 0x1 of 0x1, ) 0.05 MB/s
xflashext - Successfully wrote seccfg."
After this process, when I turn on the phone I get errors:
"dm-verify error
Android system on your device is corrupted."
When I check with fastboot mode, phone have bootloader unlocked now.
So I have tried to flash firmware using SP Flash Tool, got 100% done success message, but on phone I still can see only:
"dm-verify error
Android system on your device is corrupted."
I have also tried fastboot rom and flashing using fastboot "flash_all.bat". Result was "OKAY" for every single file. Phone rebooted and again this error:
"dm-verify error
Android system on your device is corrupted.".
UPDATE:
Finally found firmware, which does not give me "dm-verify error. Android system on your device is corrupted.". But phone is still in a bootloop.
Growicek said:
At first, I could not use that tool. Everytime I tried, I get this error: "mtk: error: argument cmd: invalid choice: 'xflash'".
I had to edit the mtkclient-gui.py with this two commands (from github)
subprocess.call(f"{runtime} mtkclient/mtk e metadata,userdata,md_udc")
subprocess.call(f"{runtime} mtkclient/mtk da seccfg unlock")
Now after running the commands I get this in log: "Failed to format all partitions." and after that: "
100.0% Write (Sector 0x1 of 0x1, ) 0.05 MB/s
xflashext - Successfully wrote seccfg."
After this process, when I turn on the phone I get errors:
"dm-verify error
Android system on your device is corrupted."
When I check with fastboot mode, phone have bootloader unlocked now.
So I have tried to flash firmware using SP Flash Tool, got 100% done success message, but on phone I still can see only:
"dm-verify error
Android system on your device is corrupted."
I have also tried fastboot rom and flashing using fastboot "flash_all.bat". Result was "OKAY" for every single file. Phone rebooted and again this error:
"dm-verify error
Android system on your device is corrupted.".
UPDATE:
Finally found firmware, which does not give me "dm-verify error. Android system on your device is corrupted.". But phone is still in a bootloop.
Click to expand...
Click to collapse
Flash this TWRP if you using Miui 12.5.x: MOD EDIT: Link Removed
Try
- Advanced > Patch vbmeta
- Reboot > System and check
If you dont have twrp:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And vbmeta.img take from fastboot or recovery rom you flashed
If not work, try flash custom rom same as Miui Firmware based to check if phone still can work or not.
And if Custom roms work, just throw Miui away.
Kirasu2080 said:
Flash this TWRP if you using Miui 12.5.x: MOD EDIT: Link Removed
Try
- Advanced > Patch vbmeta
- Reboot > System and check
If you dont have twrp:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And vbmeta.img take from fastboot or recovery rom you flashed
If not work, try flash custom rom same as Miui Firmware based to check if phone still can work or not.
And if Custom roms work, just throw Miui away.
Click to expand...
Click to collapse
Have tried flashing that TWRP. After doing it, I have tried: fastboot reboot recovery. Recovery never loaded. Just pure bootloop. Have also tried flashing vbmeta.img from firmware I have flashed. Then I powered on the phone. Again bootloop. When I tried to flashing few others TWRP. Same result - bootloop. Recovery never boot.
Could not find any custom rom, which is flashable through SP Flash Tool (With working scatter etc..), so I have tried to flash img files from custom rom one by one using fastboot (probably did something wrong or maybe not, idk), phone still in bootloop.
Growicek said:
At first, I could not use that tool. Everytime I tried, I get this error: "mtk: error: argument cmd: invalid choice: 'xflash'".
I had to edit the mtkclient-gui.py with this two commands (from github)
subprocess.call(f"{runtime} mtkclient/mtk e metadata,userdata,md_udc")
subprocess.call(f"{runtime} mtkclient/mtk da seccfg unlock")
Now after running the commands I get this in log: "Failed to format all partitions." and after that: "
100.0% Write (Sector 0x1 of 0x1, ) 0.05 MB/s
xflashext - Successfully wrote seccfg."
After this process, when I turn on the phone I get errors:
"dm-verify error
Android system on your device is corrupted."
When I check with fastboot mode, phone have bootloader unlocked now.
So I have tried to flash firmware using SP Flash Tool, got 100% done success message, but on phone I still can see only:
"dm-verify error
Android system on your device is corrupted."
I have also tried fastboot rom and flashing using fastboot "flash_all.bat". Result was "OKAY" for every single file. Phone rebooted and again this error:
"dm-verify error
Android system on your device is corrupted.".
UPDATE:
Finally found firmware, which does not give me "dm-verify error. Android system on your device is corrupted.". But phone is still in a bootloop.
Click to expand...
Click to collapse
That dm-verity error is normal if you use mtkclient. You need to lock the phone in mtkclient and reunlock the phone in the normal way to get rid of that error
Also the link seems to got removed but i use Salih-Sonar's TWRP for MIUI 12.5 (search begonia-oss and download the MIUI 12.5 one)
You can just flash the full fastboot rom and it should work unless you corrupted properitary partitions (nvdata,persist,nvcfg etc)
Canny1913 said:
That dm-verity error is normal if you use mtkclient. You need to lock the phone in mtkclient and reunlock the phone in the normal way to get rid of that error
Also the link seems to got removed but i use Salih-Sonar's TWRP for MIUI 12.5 (search begonia-oss and download the MIUI 12.5 one)
You can just flash the full fastboot rom and it should work unless you corrupted properitary partitions (nvdata,persist,nvcfg etc)
Click to expand...
Click to collapse
I have finally after hours and hours of trying flashed firmware, which is not stuck in bootloop. Now the phone reboots after few seconds of running. I found out, that CPU is overheating, so probably hardware issue. Will try reball of the CPU chip and we will see, if it helps.
Growicek said:
I have finally after hours and hours of trying flashed firmware, which is not stuck in bootloop. Now the phone reboots after few seconds of running. I found out, that CPU is overheating, so probably hardware issue. Will try reball of the CPU chip and we will see, if it helps.
Click to expand...
Click to collapse
Well good luck then.
There is a super small chance that the overheat is be related to the firmware though. But the odds of that are really low if the phone is running normal.
Canny1913 said:
Well good luck then.
There is a super small chance that the overheat is be related to the firmware though. But the odds of that are really low if the phone is running normal.
Click to expand...
Click to collapse
Phone was in a bootloop, so I have unlocked bootloader, flashed latest firmware, phone was still in bootloop. So I have flashed very very old firmware and then phone booted successfuly. I was able to set language, region, connect to wifi and then freeze. After few seconds it rebooted. I have checked the temperature of CPU (with my finger) and it was quite hot.
Let's hope that reballing will help.