EDIT: My new problem is that the device no longer powers on after performing blankflash; see post 3+
Hello, I have a Moto G Fast (XT2045-3) that I tried to downgrade to Android 10 after it already had 11 (and didn't realize the bootloader had rollback prevention even after being unlocked) and got the dreaded "black-screen-of-death."
After cracking open the back cover and shorting the two pins to force EDL mode I am now at least successfully seeing the "Qualcomm HS-USB QDLoader 9008" in device manager which tells me I should be in EDL mode. (NOTE: I have done some some work on a different Qualcomm device months ago that was successful so I'm pretty confident that my EDL drivers are correct/working)
EDIT: I now know that Moto devices don't use QFIL and instead use blankflash with qboot -- leaving the rest below for reference
My problem now is that QFIL wants a "rawprogram*.xml" and "patch*.xml" that I can't seem to find. After some digging I was able to find a firehose MBN for the SM6125 on some other XDA thread for the Redmi Note 8 because I wasn't able to tell if the bkerler github actually had the firehose as it wasn't obvious to me based on filenames. Because of that I'm not fully 100% confident that I know I have the correct firehose, either.
I have yet to find the appropriate xml files that QFIL is asking for. Either that or I don't fully understand how to flash without those and just using, for example, the contents of the stock firmwares on the lolinet mirror. In QFIL if I try to do anything, all I get is "Sahara Fail" -- even when trying something as simple as "Tools" -> "Get Flash Information"
Can anyone let me know where I can get the QFIL special files (or a compatible firmware zip that contains them)? Alternatively, if there is some way to flash the lolinet stock ROMs in EDL mode that doesn't need those QFIL xml files please let me know. My digging hasn't given me any specifics if that's possible and I'm quite inexperienced with QFIL in general anyway.
Follow-up:
I've also tried blank-flash.bat as I've seen suggested elsewhere but it also fails at the beginning to even see the device:
.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ 0.001] Opening device: \\.\COM6
[ 0.042] Detecting device
[ 34.713] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.713] Check qboot_log.txt for more details
[ 34.713] Total time: 34.714s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
Click to expand...
Click to collapse
Contents of qboot_log.txt:
**** Log buffer [000001] 2023-02-11_10:25:12 ****
[ 0.001] Opening device: \\.\COM6
[ 0.042] Detecting device
[ 34.713] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.713] Check qboot_log.txt for more details
[ 34.713] Total time: 34.714s
[ 34.714]
[ 34.714] qboot version 3.86
[ 34.714]
[ 34.714] DEVICE {
[ 34.714] name = "\\.\COM6",
[ 34.714] flags = "0x64",
[ 34.714] addr = "0x62FD54",
[ 34.714] api.bnr = "0xF336B0",
[ 34.714] }
[ 34.714]
[ 34.714]
[ 34.714] Backup & Restore {
[ 34.714] num_entries = 0,
[ 34.714] restoring = "false",
[ 34.714] backup_error = "not started",
[ 34.714] restore_error = "not started",
[ 34.714] }
[ 34.714]
Click to expand...
Click to collapse
So, yet another follow-up. I've since learned that the Moto 'blankflash' is supposed to be the entire process that QFIL would be doing for other phones and that I shouldn't need QFIL or it's xml files.
I was able to get the blankflash to work once by starting it seconds after the phone showed up in device manager as the EDL qualcomm driver. Maybe there was a timeout delay issue from me not trying it right away or maybe I got lucky after several attempts. The blankflash completed in what seemed to be a successful manner.
After the blankflash script ran, however, I can no longer get the device to respond in any way. If I didn't know better I'd say it's not powering-on at all. The vol up or down plus power don't produce any vibration or anything on the screen and `fastboot devices` and `adb devices` show no results. What's worse now, though is that the same two test points on the board behind the back cover that I was using to enter EDL mode now also don't seem to be working. before the blankflash I was able to enter EDL consistently every time but now I can't get it up at all. I try unplugging the battery to make sure it's off first; I've left it plugged in to a charger overnight; I've tried with the screen connected and disconnected... no combination of anything I've tried gets the device to do anything anymore. Not EDL, not Fastboot, nothing on the screen, etc.
Using this space to document what I've tried for my own records and also in case anyone is able to give advice (or if the device is DOA).
All operations were tried multiple times, with multiple different USB cables and different USB ports on the PC. All of those ports and cables were all tested working for other devices. Anything where I say I held it was tried with varying lengths of time, usually 20-30 seconds. For each of these tests I had device manager open and sections expanded to see if/when any new device is recognized and so far nothing has even shown up once in device manager nor on the device's screen. That is, not since after I flashed the blankflash -- it used to work and enter fastboot/EDL etc but ever since flashing blankflash it seems to not even be powering on.
"Off state" means I disconnected the battery ribbon cable for 10+ seconds before starting the next step.
"Jump EDL testpoints" means shorting the two pads on the mainboard that successfully worked for me on this device in the past to get it into EDL mode
Off state -- Hold VolUp+Power -- Plug in USB while still holding down
Off state -- Reconnect Battery -- Hold VolUp+Power -- Plug in USB while still holding down
Off state -- Hold VolUp+Power -- Plug in battery ribbon while still holding -- Plug in USB while still holding down
These were also repeated with VolDown+Power, Just VolUp, Just VolDown and Just Power
Off state -- Jump test-points -- Plug in USB while still holding test points
Off state -- Reconnect Battery -- Jump test-points -- Plug in USB while still holding test points
Off state -- Jump test-points -- Reconnect battery while still holding test-points -- Plug in USB while still holding test-points
These were also repeated with including the button combinations alongside the test-points each time as well
I tried letting the device sit with the battery unplugged overnight (12+ hours) and repeating the tests after that, and I've also tried letting the device stay attached to a charger for 24+ hours before repeating the tests as well. I've attempted all of these tests at least once with the screen's ribbon cable disconnected and at least once with it connected.
All-in-all I've probably made almost 100 attempts after the blankflash to get the phone to do anything at all without success.
I'm now wondering if there is a simple way to measure voltage on some points on the board to see if it's even powering up at a basic level or not.
Related
Hi, i went out for a few drinks and got some party on.... it ended in my phone battery going dead..... now when i try to charge it, its just flashing read.. and it randomly boots into a white screen then shuts down after 10 seconds. something to do with my flashing recovery partition to get cwm and stuff which ofc didnt work look further down my post for more info about that, thats pretty much the only thing i have messed about with(rooted successfully tho... i dont understand why it wont charge just because of the bad flash, i tryed normal power outlet 230volt adapter to usb... the orginal that was bundled with my order... and tryed regular usb from my pc.
its just plain flat, and wont charge.. redlight flashing. some times it viberates boots into a white screen but wont charge..there should be a yellow light that should turn green at full capacity.
Now the question is if just could get myself into this fastboot or adb interface so i can flash my orginal recovery rom, i think the problem would solve, or if i maybe got to charge the battery manualy by physicaly removing it and charge it manualy without usb cable etc...
I have the firmware U9200-1V199R991C185B104.(norway)
In addition, I have rooted it.
used onkeys stuff, also realized i couldnt root it with my current windows 7 username (administrator) the script made it admini1 so errors appeared. I also used the Onekey_ROM_Ascendp1.exe it did some stuff copied some stuff, installed a recovery console that also didn’t work :S but nothing major changed, I think it has something to do with SD card mount names, but not sure about that
the thing is I can’t get the cwm_touch_recovery_viva_beta.img to work.
adb start-server
adb reboot-bootloader
2nd cmd prompt
fastboot erase recovery
fastboot flash recovery cwm_touch_recovery_viva_beta.img
fastboot reboot (unplugged usb as well)
Booted operating system
powered off, tried all the combinations of vol+up, vol+down and both vol-up/down + power, its basically stuck on the logo.
anyways so I went ahead to flash the stock recovery.img from page 7 8mb file.
now I have the standard recovery UI. with vol+up and power, that made me sure that the flash procedure is correct.
Right now I’m not sure if the cwm_touch_recovery_viva_beta.img is compatible with this b104... is anyone able to confirm this?
I have clockwork mod app installed on my phone though, it says my phone is not compatible yet.
+1 for our own ascend p1 forum tab!
Have a great day everyone n when its fully charged.
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot devices
? fastboot
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.878s]
finished. total time: 1.881s
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot flash recovery cwm_touch_recovery_viva_beta.img
sending 'recovery' (3335 KB)...
OKAY [ 0.110s]
writing 'recovery'...
OKAY [ 0.452s]
finished. total time: 0.567s
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 27.082s]
finished. total time: 27.084s
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.004s
When it was finished booting up i went for rom manager and reboot into recovery, then the app just froze and i could close or wait for it.
shut down device with usb cable in just froze up on huawei logo.
restarted did abd reboot recovery, after that no response in either fastboot or adb interface
Solved?
So did you solve the problem? and how?
its kinda same with my problem, cannot turn on, when plug the charge cable only vibrate, huawei logo and bootloop
but when I go to fastboot mode its only last around 40 seconds, its that normal
tried to flash the boot and recovery to stock still not working
anyone has solved the problem?
I have the same problem with a Huawei Ascend P1 U9200.
I have not flashed any new roms or recovery and it is not rooted.
The phone ran out of power, so was plugged into a wall charger, then when I checked on it later the "Huawei Ascend" screen displays for a few minutes then it powers off, vibrates, red led flashes and the Huawei Ascend screen displays again. It is stuck in a boot loop and unresponsive to the power and volume buttons.
adb devices displays nothing and
fastboot reboot displays < waiting for device >
I had a similar problem when flashing my Motorola Defy, and had to do the Macgyver Hack to directly charge the battery http://forum.xda-developers.com/showthread.php?t=1086953. But the U9200 has a sealed battery and it still has 11 months on the warranty so its not worth breaking the phone for.
As the battery is flat I cannot boot into recovery by pressing Vol Up + Vol down + Power as it has no power. So how can you boot into recovery with a flat battery?
Any advice would be greatly appreciated!
iv root my phone with locked boot loader & install timwin recovery for locked boot loader , its very good working then i decide try this CARBON-KK-UNOFFICIAL-20150221-2137-tianchi , copy 2 sd card & flash it whit tim win recovery all down but when i reboot it no responds
try to unlock bootloader with last version flash tools Version 0.9.18.5 but not entering flash mode by hold down vol botton just blink one time red & imiditly green light & agine red then turn led off
warning flash tool : Device connected with USB debugging off
04/037/2015 18:37:43 - INFO - For 2011 devices line, be sure you are not in MTP mode
fastboot mode is work when hold down vol up & plug usb cable solid blue led turn on . device attached & respons when unlock bootloader with given number
FAILED (remote: Command did not succeed)
finished. total time: 0.093s
second time try
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
try s1 tool with testpoint
resul:
DETACH USB CABLE FROM PHONE
REMOVE BATTERY FROM PHONE
ATTACH TESTPOINT
PRESS "READY", THEN ATTACH USB CABLE TO PHONE
will use Sahara protocol ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"
PROCESSING ...
SERIAL NUMBER : D7E50A04
HARDWARE ID 04000100E1509100 NOT SUPPORTED
HARDWARE ID : 04000100E1509100
NOT SUPPORTED HASH :B77943D5B24F7012CB12EB2FF857C69EAA6518C0E58957AA70C0B0590E1F3BCA
Elapsed:21 secs.
pleas help un bricked my d5322
tanx
Do you have working a fastboot mode?
modesazhi said:
iv root my phone with locked boot loader & install timwin recovery for locked boot loader , its very good working then i decide try this CARBON-KK-UNOFFICIAL-20150221-2137-tianchi , copy 2 sd card & flash it whit tim win recovery all down but when i reboot it no responds
try to unlock bootloader with last version flash tools Version 0.9.18.5 but not entering flash mode by hold down vol botton just blink one time red & imiditly green light & agine red then turn led off
warning flash tool : Device connected with USB debugging off
04/037/2015 18:37:43 - INFO - For 2011 devices line, be sure you are not in MTP mode
fastboot mode is work when hold down vol up & plug usb cable solid blue led turn on . device attached & respons when unlock bootloader with given number
FAILED (remote: Command did not succeed)
finished. total time: 0.093s
second time try
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
try s1 tool with testpoint
resul:
DETACH USB CABLE FROM PHONE
REMOVE BATTERY FROM PHONE
ATTACH TESTPOINT
PRESS "READY", THEN ATTACH USB CABLE TO PHONE
will use Sahara protocol ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"
PROCESSING ...
SERIAL NUMBER : D7E50A04
HARDWARE ID 04000100E1509100 NOT SUPPORTED
HARDWARE ID : 04000100E1509100
NOT SUPPORTED HASH :B77943D5B24F7012CB12EB2FF857C69EAA6518C0E58957AA70C0B0590E1F3BCA
Elapsed:21 secs.
pleas help un bricked my d5322
tanx
Click to expand...
Click to collapse
Dude! If light is blink.. It's not a hard brick, just a soft brick don't worry everything thing is okay. You flashed a wrong kernel/locked bootloader.
Follow these setups
1.Download latest flash tool.
2.Install and go eg C:/flashtool/drivers (install t2 drivers) /windows 8 has some problems_google it
3. Open SIM panel, you will find a purple button press once with pan tip/needle
4. Put your phone in charging keep 1_2 hours
5. Connect in fastboot, now try to unlock phone with Sony Official bootloader unlocking method.(Google it)
Best of luck
No charging just blink slowly red led continusly
hard brick of xperia t2 ultra d5322 device
I have rooted my sony xperia t2 ultra and installed twrp recovery on it and it worked fine..but when i try to flash a custom rom,it shows a successful message and got bricked afterwards..was on low battery that time..showing red blink on led but now thre is no vibration as well as there is no led blink..please help me to fix it..please..asap..
prabhata moharana said:
I have rooted my sony xperia t2 ultra and installed twrp recovery on it and it worked fine..but when i try to flash a custom rom,it shows a successful message and got bricked afterwards..was on low battery that time..showing red blink on led but now thre is no vibration as well as there is no led blink..please help me to fix it..please..asap..
Click to expand...
Click to collapse
It happened to me few hours ago. I flashed a wrong kernel, then got no response/screen/led. take your time and hold power and vol + buttons 'til you feel the phone vibrate 4 times (1+3). As it happens you're sure it's turned off. So, let it charge for one or two hours, then flash a previously working kernel through flashtools fastboot mode.
This worked for me and hope it helps you too.
Best regards.
Hey everyone.
I know how to flash and have knowledge with adb and fastboot and so on... but now iam helpless with this situation and googled allready alot.
1: I flashed to RR 7.02 Android 9.0 without Problems. But i had some Problems with Magisk and my Banking app.
2: I tryd to restore with TWRP my OLD oreo 8.1 backup but there it shows Problems with mounting system all the time. After Restore complete it allways says cant mount system - invalid argument and after boot it only goes to Fastboot.
3: I flashed original CEDRIC_OPP28.85-16_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip with fastboot commands. After finishing flash i did fastboot reboot but Phone gone off.
Now the the Problem: Screen wont turn on again. I had low Battery and thought it maybe its the Problem of no Battery. But now the Phone hangs like 2 Hours on the original Charger/tryd 2 other chargers allready and the Screen wont turn on. It just blinks the white LED when charger is plugged in. No normal power on no fastbooot or recovery power on. The screen wont just turn on. Strange?! Battery or Hardware defekt? But i had no problems before... The Phone is now 18 month old.
Any advise or Help. Thanks
c:\adb2>fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.690s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.598s]
Finished. Total time: 1.358s
c:\adb2>fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.695s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.635s]
Finished. Total time: 1.403s
and something like this i had never before... (bootloader) is-logical:recovery: not found or (bootloader) Image signed with key bad key ( but this shouldnt be the problem)
NOW it shows this under device manager when i plug it in look screenshot.
If it's a battery issue hold the power button for 30 seconds whilst the charger is plugged in - if you can then see the charging animation don't attempt to turn the phone on until it reaches 5% charge
You can also try these steps
1) Plug it into the charger
2) Hold the VOL DOWN key
3) While still holding the VOL DOWN key, press and hold the POWER key
4) Hold both keys down for over 120 seconds. This is more than two minutes and will seem like a long time. You might want to time yourself to make sure you hold it longer than two minutes.
5) After holding the keys down for more than two minutes, release them.
6) The Fast Boot screen will display, and the Normal Reboot option will be highlighted
7) Press the VOL UP key and the device will start a normal reboot.
If it's a firmware issue you may have hard bricked the device from incorrect or incomplete firmware flash
See my hardbrick thread for a possible solution if it is hard bricked else you may require a motherboard replacement
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
i think its hard bricked. I will try now your unbrick tutorial. Thanks for this
TheFixItMan said:
If it's a battery issue hold the power button for 30 seconds whilst the charger is plugged in - if you can then see the charging animation don't attempt to turn the phone on until it reaches 5% charge
You can also try these steps
1) Plug it into the charger
2) Hold the VOL DOWN key
3) While still holding the VOL DOWN key, press and hold the POWER key
4) Hold both keys down for over 120 seconds. This is more than two minutes and will seem like a long time. You might want to time yourself to make sure you hold it longer than two minutes.
5) After holding the keys down for more than two minutes, release them.
6) The Fast Boot screen will display, and the Normal Reboot option will be highlighted
7) Press the VOL UP key and the device will start a normal reboot.
If it's a firmware issue you may have hard bricked the device from incorrect or incomplete firmware flash
See my hardbrick thread for a possible solution if it is hard bricked else you may require a motherboard replacement
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
Click to expand...
Click to collapse
Your Tutorial with Linux min worked. The Phone is back to life. Good i didnt gaved up early. Thank you very much. I would like to buy you a beer if you dont mind...got paypal? cuz you made my head free now
fenerbuuh said:
Your Tutorial with Linux min worked. The Phone is back to life. Good i didnt gaved up early. Thank you very much. I would like to buy you a beer if you dont mind...got paypal? cuz you made my head free now
Click to expand...
Click to collapse
Glad it's working - I give advice for fun not for money but thanks for the offer
Greetings !
I have a very hardbricked Honor 7x device, maybe experts have any idea.
If I turn it on, the device stuck at blue honor screen.
If I press up volume+power, nothing happen only rebooting into blue honor screen.
If I connect to pc + low volume+ power , Fastboot and rescue mode arrives, but phone locked and frp lock
If I copy the service rom from the russian forum to sd then up+low volume + power, long black screen then green background with rgb lines then restart and do the same.
What can I do to make it boot into system ?
Or how can I reinstall the recovery or something without any access ?
Maybe I need to dissasembly then do something with the service pins ?
Thank you for your help guyz !!
Turn 2:
I dissasembled the device and found there an EDL mode to flash the BND-L24 .
https://forum.xda-developers.com/honor-7x/how-to/download-guide-bnd-l24-board-firmware-t3959990
I think they are common devices.
The IDT started then Fail at 49 second. Error(41).
The manual told me: "强制加载后进入 fastboot 加载超时" aka "Enter fastboot loading timeout after forced loading"
The IDT log:
20201110-19:44:25 usb1: Start downloading with VCom!
20201110-19:44:25 usb1: Load DownLoadBoot Version 2.0.0.9
20201110-19:44:25 usb1: eek: pening COM6 Success
20201110-19:44:27 usb1: download mode enter:31
20201110-19:44:27 usb1: Downloading xloader begin.
20201110-19:44:27 usb1: Writing xloader...
20201110-19:44:27 usb1: Write delay = 3000 ms.
20201110-19:44:30 usb1: Download xloader end.
20201110-19:44:30 usb1: download mode enter:255
20201110-19:44:30 usb1: Downloading fastboot begin.
20201110-19:44:41 usb1: Writing fastboot...
20201110-19:44:41 usb1: Write delay = 3000 ms.
20201110-19:44:44 usb1: Download fastboot end.
20201110-19:44:44 usb1: VCom download successfully.
20201110-19:45:15 FAIL (49 s). Error (41)
I hope some experts will be there because Im hopeless.
Can't access recovery menu.
When I turn the phone on with volume up and power button held down the phone boots up normally and I get this error message:
[PDP] Back-up : fail setup-wizard [ FINISH ]
I have the stock ROM, no root or anything like that
I used "universal android de-bloater" (uad gui) to remove some crap, mostly Samsung and Knox stuff, but I didn't remove anything that wasn't in the recommended list, or didn't have a clear description.
Did I do something wrong or Is this a known issue? What should I do?
(I didn't try adb reboot to recovery command, I don't know much about adb and I couldn't get it connected to my phone yet and I didn't even know if a command like this even exists.)
(OEM unlock and USB debugging is turned on)
FelixVyra said:
Can't access recovery menu.
When I turn the phone on with volume up and power button held down the phone boots up normally and I get this error message:
[PDP] Back-up : fail setup-wizard [ FINISH ]
I have the stock ROM, no root or anything like that
I used "universal android de-bloater" (uad gui) to remove some crap, mostly Samsung and Knox stuff, but I didn't remove anything that wasn't in the recommended list, or didn't have a clear description.
Did I do something wrong or Is this a known issue? What should I do?
(I didn't try adb reboot to recovery command, I don't know much about adb and I couldn't get it connected to my phone yet and I didn't even know if a command like this even exists.)
(OEM unlock and USB debugging is turned on)
Click to expand...
Click to collapse
If you want to boot to recovery, you also need to have your phone connected to the PC. While the phone is connected to the computer, then hold vol up + power buttons.