Related
Hello XDAers,
So a couple of days ago I tried to root my Republic Wireless 1st gen Moto X (x1049) using the Suicide Flash method made by NiceneNerd for lollipop. What ended up happening is that the phone entered Qualcomm Emergency Mode, and stayed there since the script glitched when I tried running it. I tried many ways to get out of it - CrashXXL's method, s5610's method, and a few other methods to try and get out of this state. I can't even access bootloader at this point either - all there is is a black screen. And yes, i have tried every button combo possible to get out of this black screen. I dont have any phone for now - so if anybody has the solution or can contribute please help.
Thank you.
Heronicola said:
Hello XDAers,
So a couple of days ago I tried to root my Republic Wireless 1st gen Moto X (x1049) using the Suicide Flash method made by NiceneNerd for lollipop. What ended up happening is that the phone entered Qualcomm Emergency Mode, and stayed there since the script glitched when I tried running it. I tried many ways to get out of it - CrashXXL's method, s5610's method, and a few other methods to try and get out of this state. I can't even access bootloader at this point either - all there is is a black screen. And yes, i have tried every button combo possible to get out of this black screen. I dont have any phone for now - so if anybody has the solution or can contribute please help.
Thank you.
Click to expand...
Click to collapse
Did u make any progress sir?
hbenz2008 said:
Did u make any progress sir?
Click to expand...
Click to collapse
Unfortunately i did not. It still is in Qualcomm Emergency Mode, and Device Manager shows it as Qualcomm HS-USB QDLoader 9008
Heronicola said:
Unfortunately i did not. It still is in Qualcomm Emergency Mode, and Device Manager shows it as Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
There is a thread that will get you back up hopefully, look for "how to unbrick..." I will link you if needed
hbenz2008 said:
There is a thread that will get you back up hopefully, look for "how to unbrick..." I will link you if needed
Click to expand...
Click to collapse
Well, I have tried any links that are related to bricking and unbricking. For example - blankflash returns this -
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
EOF_REC
Sleeping for 3s
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
Still no data, giving up!
sdl_hello() - Failed to receive ACK
sdl_hello() - Invalid response: 7e030003331b7e
sdl_hello() - This is a NAK response from ROM code, which means the device has been reset back to blank flash mode. Usually this is caused by power supply issues. Please try again with battery eliminator if it persists
Welp, i also just tried to pop off the back and i broke of the connector that connected the volume rocker. Im guessing then the volume button doesnt work anymore and i cant access fastboot anyways/
Heronicola said:
Welp, i also just tried to pop off the back and i broke of the connector that connected the volume rocker. Im guessing then the volume button doesnt work anymore and i cant access fastboot anyways/
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2629057
hbenz2008 said:
http://forum.xda-developers.com/showthread.php?t=2629057
Click to expand...
Click to collapse
i tried that too
Hello everyone
My brother's Mi A2 is bricked for no reason. I tried to solve this problem and searched a lot but didn't manage to solve it. I hope you can help.
* before telling my story here is some stuff to know:
- The phone was running official firmware and bootloader is locked, I've never played with it's software before.
- Oem unlocking option isn't turned on.
- The phone doesn't go to recovery mode, only fastboot or regular boot.
- I used EDL mode in every flashing attempt.
- I don't remember that there is a mi account assigned to the device.
* Here is what happened:
- The phone suddenly shut down during a call and never passed the AndroidOne logo after that.
- Tried EDL mode and miflash to flash the latest firmware. Flashing completed successfully but the phone still stuck on the androidone logo.
- Did it again and again but the result was constant.
- Tried flashing older firmware "Oreo 8.1" but during flashing system.img the process stopped with an error. (I don't remeber what the error was).
- I tried to turn on the phone but after showing AndroidOne logo This message appeared:
"Your device is corrupt. It can't be trusted and will not boot.
Visit this link on another device: g.co/ABH"
and the device shuts down in a minute.
Hint: Sometimes when I try to turn one the phone the above message appears after androidone logo and sometimes the device just keep showing the logo.
- Trying to flash any firmware version by using Miflash Beta gives an error message "Can not found programmer file" immediately. when I try again it gives: "can't read from port COM4", Changing the port gives the same error with different port number.
-When I use any other version of "Portable miflash", The flashing process starts normally but fails when trying to flash "dsp.img", giving an error of "writing time out".
- I tried reinstalling all drivers needed with no change at all.
I hope that you guys can help me solving this problem.
Thank you so much!
Try EDL mode opening your phone...
Badotti said:
Try EDL mode opening your phone...
Click to expand...
Click to collapse
I did.
Bootloader is locked, so EDL mode was the only way. But now I get error writing timed out while flashing any firmware version.
Ahmed A. Mohsen said:
I did.
Bootloader is locked, so EDL mode was the only way. But now I get error writing timed out while flashing any firmware version.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=wav1xNdJzII
Youtube you find several tutorials, work and open the phone ...
Badotti said:
https://www.youtube.com/watch?v=wav1xNdJzII
Youtube you find several tutorials, work and open the phone ...
Click to expand...
Click to collapse
I opened the phone and used edl mode already but the problem is still present.
up
Have you tried to use qfil? See in the 3d dedicated to conversion A2 <> 6x
HTCDevil said:
Have you tried to use qfil? See in the 3d dedicated to conversion A2 <> 6x
Click to expand...
Click to collapse
This needs bootloader to be unlocked and my device's bootloader is locked.
Any solutions?
Go to service center this is last option you save RIP mi a2 ?
As I can see from picture you have posted, your bootloader is unlocked.
SkullSatan88 said:
Go to service center this is last option you save RIP mi a2
Click to expand...
Click to collapse
They refused to receive my device because I bought it from another country.
bomil said:
As I can see from picture you have posted, your bootloader is unlocked.
Click to expand...
Click to collapse
when I checked bootloader status in the beginning it was locked.
Are you sure that it's now unlocked?
Text me on telegram. @dejavutr
Guys I was trying to do unlock my ROG Phone II with EDL mode:
https://forum.xda-developers.com/rog-phone-2/how-to/how-to-unlock-rog2-phone-via-edl-mode-t4008267
My phone is still in edl mode it shows as a COM port in my pc. I really need help I cannot do anything. I tried to flash it in MiFlash and it gives an error every time. Please help me!!!!!!!! PLEASE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I NEED HELP IMMIDIETELY PLEASE
The app works just fine... Also why are you trying to use a Xiaomi flash tool on an Asus device?
Get out of EDL mode with vol- vol+ power all three together.
EfeKamil said:
Guys I was trying to do unlock my ROG Phone II with EDL mode:
https://forum.xda-developers.com/rog-phone-2/how-to/how-to-unlock-rog2-phone-via-edl-mode-t4008267
My phone is still in edl mode it shows as a COM port in my pc. I really need help I cannot do anything. I tried to flash it in MiFlash and it gives an error every time. Please help me!!!!!!!! PLEASE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I NEED HELP IMMIDIETELY PLEASE
Click to expand...
Click to collapse
Have you tried doing the process with the correct drivers installed? (I have not done this method, but it could be driver related) See here for drivers
EDIT: at the bottom of your EDL thread it does state you need the Qualcom drivers installed, not sure if they're the same as the ones i linked to, but the ones in that thread are here
Also, this post may be of some use to you, might wanna read the rest of the thread too for tips...
'I read somewhere that you must start the EDL unlocking process as soon as you run the fastboot command to boot it into EDL mode. It wouldn't run correctly for me at first, but then I rebooted into fastboot, ran the enter dload command, then immediately ran the unlocker (or if it fails because your device hasn't entered EDL mode just yet, keep spamming it).
I have no idea why that's the case but it worked for me.'
My Moto G6 play failed to boot. Have now idea how to fix or if can be? It just happened while the phone was on sitting idle. Tried to connect to Software Upgrade Assistant but it didn't pick my phone up. Went through the menu and tried factory reset even and it still brought this error up.
Any thoughts? Error is summarized below
Thanks
failed to validate boot image
ERROR: failed to pass validation, backup to fast boot
Now got it connected up to Software Repair Assistant and it's been running for 15minutes stuck on below. Any ideas?
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 Factbook Flash Mode (Secure)
USB connected
cmd: getvarroduct
cmd: getvar:secure
cmd: getvar:version-bootloader
cmd: getvar:cid
cmd: getvar:ro.build.fingerprint
cmd: getvar:ro.build.version.full
cmd: getvar:ro.build.version.full
cmd: getvar:serialno
cmd: getvar:imei
cmd: getvar:sku
cmd: getvar:ro.carrier
Tried to re-install the Software with the help of Smart Assistant Tool but it kept failing halfway through with no meaningful error message. Any thoughts? Is it now a brick?
Gazza76 said:
Tried to re-install the Software with the help of Smart Assistant Tool but it kept failing halfway through with no meaningful error message. Any thoughts? Is it now a brick?
Click to expand...
Click to collapse
Hey dude! It is a little old, but do you get a solution for your problem? I have the same issue, and now that I´m willing to lost everything on my phone it does not allow to do a factory reset. Damn phone...
Paulista666 said:
Hey dude! It is a little old, but do you get a solution for your problem? I have the same issue, and now that I´m willing to lost everything on my phone it does not allow to do a factory reset. Damn phone...
Click to expand...
Click to collapse
Gazza76, I don´t know exactly why, but I just charge my phone all the way, and try again expecting that was some battery protection. Maybe if the battery is below some threshold it stop the boot to avoid issues. But no, keeping having the same problem.
But, I pluged in the computer with LSMA installed and it let me reinstall all firmware. It recommends the right firmware, you download it through the app, and install it really fast in my opinion. Could be a solution for you if you are with the problem yet...
I was trying to flash a new rom and accidentally hit "boot to fastboot" in the pixel experience recovery
now when i try to boot it goes black and i cant get back into recovery at all
when i put it into fastboot it isn't detected by my computer.... am i screwed?
Worst case just blank flash
Arealhooman said:
Worst case just blank flash
Click to expand...
Click to collapse
How do i do that?
Download Mi Flash Tool and flash Stock.
JingleDraws said:
I was trying to flash a new rom and accidentally hit "boot to fastboot"....
Click to expand...
Click to collapse
Have you tried a very, very long press on power to start up?
Had you flashed already that new rom and pressed then boot to fastboot instead of boot to recovery?
Elinx said:
Have you tried a very, very long press on power to start up?
Click to expand...
Click to collapse
Hey @Elinx you try to help everyone. I like that
Laptapper said:
....you try to help everyone....
Click to expand...
Click to collapse
I try , like you do too, but sometimes I forgot my crystal ball to understand the question.
Elinx said:
I try , like you do too, but sometimes I forgot my crystal ball to understand the question.
Click to expand...
Click to collapse
Yep....me too....but new members have a child protection
This just happened to me on the same recovery. I cleared my storage/cache ect then clicked boot to fastboot to flash a new recovery this then led to me just having a black screen.
Also mi flash seems to require fastboot in which my device is not showing.
Also thanks for any help anyone gives
WeeScottishMan said:
.... just having a black screen.
...
Click to expand...
Click to collapse
A black screen does mostly mean that the phone is started in EDL mode.
That is why I advice first to try a very long press on power.
You could check this inside device manager on PC, with or without the right USB drivers.
(Qualcomm HS-USB QDLoader 9008)
Flashing from EDL isn't possible without Mi authorisation as long there isn't a hacked firehose file.
Holding power seems to just be turning it off and on again. Also I cannot seem to find the phone on device manager although it plays the connection sound and refreshes when plugged in and turned on. Do you know where I would find it in device manager.
Thanks again for the help
oh wait yes it is in edl mode does that mean I am massively screwed :<
Thanks again.
WeeScottishMan said:
... yes it is in edl mode does that mean I am massively screwed....
Click to expand...
Click to collapse
If the phone does start black again after very long press.
Yes, you are screwed up with EDL and you need to go to a Mi service center, or try an "online unbrick service" with Teamviewer from a third party.
I'll seek out an online unbrick service if I can since I do not live near any mi service centers.
I did suspect it might be EDL but I am glad I now know it is.
Thank you so much for helping and also for the amazingly quick responses I hope this helps out the guy who posted this thread.
I'll post an update if I get it fixed, I won't give up that easily
WeeScottishMan said:
I'll seek out an online unbrick service if I can since I do not live near any mi service centers.
I did suspect it might be EDL but I am glad I now know it is.
Thank you so much for helping and also for the amazingly quick responses I hope this helps out the guy who posted this thread.
I'll post an update if I get it fixed, I won't give up that easily
Click to expand...
Click to collapse
I don't find the reason, in any of your posts, why it would be bricked. If your device is not really bricked, then to get it out, you have to press the three buttons at the same time for about 9 seconds, while you see the changes in device manager PC, so you can see in which mode it is. Eventually in the booting process, change the hardware buttons as if you will send it to fastboot or recovery mode, it doesn't matter the display is showing nothing, just check the device manager to have an idea.
Thanks for your suggestion.
I tried that yet it still shows the Qualcomm HS-USB QDLoader 9008 (COM3). I am also a bit confused why it has bricked since I really didn't think I had done anything wrong :/
mine appears in device manager, is that a good sign? what do i do from here
WeeScottishMan said:
I'll post an update if I get it fixed, I won't give up that easily
Click to expand...
Click to collapse
if you do get it fixed please let me know what they did so i can do it as well! thank you and good luck!! ...at least this isn't my main phone..
Be sure to try all the methods to get it in other modes, it's just a timing thing, while device goes from a state to another, then you should try one time to enter to fastboot, and in a new cycle reboot, try to enter to recovery mode, BUT If the device, can't definitely enter to recovery nor fastboot mode, and it always redirects to Qualcomm HS-USB QDloader 9008 (apart than shutting down), then it's bricked.
EDL mode, using MiFlash tool requires a Mi authorized account, just older devices can use it for free, this is not the case, unfortunately.
Instead, you can try with other Qualcomm flasher tool, like QPST, not sure if it still works for this device (for older it does), you should give it a try.
@SubwayChamp is right about that.
There is a difference if EDL came out of the box or after an attempt to update or other flashing attempt.
That is why to try all possibilities to get into fastboot or recovery.
So try Vol up+ Vol down+power, Vol up+power, Vol down+power and only power always first to see if you can get out of EDL.
You can try QPST too, but search for some HowTo with pictures, because it isn't the same as Miflash and is a bit complicated if you never used it.
There still isn't a modded firehose file (prog_ufs_firehose_sm7150_ddr.elf) for RN10P to pass Mi authorization, but there is a very small chance that QPST does work.