Recover moto G5 with broken power button - Moto G5 Questions & Answers

Hello, everyone.
I have this moto G5 which power button doesn’t seem to work and it doesn’t let me enter fast boot mode (I think). Using adb in Linux, is there a way I can do it? I attached pictures of it when powering it on through USB and after pressing volume down.
Thank you in advance!

Clearly the software is corrupt. Try using the "Software restore tool" which it suggests to restore your device, then give it a go

PhotonIce said:
Clearly the software is corrupt. Try using the "Software restore tool" which it suggests to restore your device, then give it a go
Click to expand...
Click to collapse
I tried, but it didn’t work. The software, on windows (the Lenovo/motorola recovery tool) said it didn’t recognized it and asked to enter in fast boot, which takes me to what I said in my first post.

Haven't you entered fastboot in the second image?

My first answer would be yes, but whe recovery tool doesn’t recognize the phone on windows and it’s also not listed on Linux with the adb command, so my last answer is I’m really not sure.

try installing the correct drivers and checking that your cable does indeed support data transfer

PhotonIce said:
Clearly the software is corrupt. Try using the "Software restore tool" which it suggests to restore your device, then give it a go
Click to expand...
Click to collapse
Hello again.
I tried checking the cable, like you suggested, and then I was able to go a step further: the cell phone communicates with the computer. But I’ve got an error message from the restore tool (it’s in Portuguese) when I try to recover that, briefly, says my models name is all “0”, what doesn’t seem normal.
Any ideas about where I can go from here? Thank you!

did you say that your device is a motorola? why are you using a lenovo tool?

PhotonIce said:
did you say that your device is a motorola? why are you using a lenovo tool?
Click to expand...
Click to collapse
Leneovo own Motorola

Related

LG G4 after flashing it went dead.

Hello, Friends, I wanted to unlock an LG G4 T-mobile for a customer with "Device unlock app"
after the flashing using LG Tools from z3x the phone now is a dead black screen. When I plugged into the computer I can hear the sounds it's connected but nothing is showing. Need help to turn it back on thanks. I can't even load in Download mode.
Thanks for any help.
umarmansare said:
Hello, Friends, I wanted to unlock an LG G4 T-mobile for a customer with "Device unlock app"
after the flashing using LG Tools from z3x the phone now is a dead black screen. When I plugged into the computer I can hear the sounds it's connected but nothing is showing. Need help to turn it back on thanks. I can't even load in Download mode.
Thanks for any help.
Click to expand...
Click to collapse
Can you boot to recovery? Should be the power + volume down combo until the logo comes up.
Alternatively,
Have you installed ADB and fastboot drivers?
Can ADB see your device when you're plugged into the computer? Perhaps you can get into bootloader mode through ADB if so.
Connect LG G4 to your computer.
On the PC, access the Android SDK folder (download it if you don't have it).
There, open a command prompt window by pressing shift + right click on any blank area.
In the CMD window, execute the command " adb reboot bootloader " without quotes. If you haven't enabled USB debugging, you may be out of luck.
Tried but not working
Hello, Friend Thank you very much for your time and efforts while typing this to help me out. I did but still doesn't recognize took the owner. Technically the phone is dead.
umarmansare said:
Hello, Friend Thank you very much for your time and efforts while typing this to help me out. I did but still doesn't recognize took the owner. Technically the phone is dead.
Click to expand...
Click to collapse
why you use flash tools.? you should ut use LGUP and KDZ file.
what is this app customer with "Device unlock app"
unlock what.??
umarmansare said:
Hello, Friends, I wanted to unlock an LG G4 T-mobile for a customer with "Device unlock app"
after the flashing using LG Tools from z3x the phone now is a dead black screen. When I plugged into the computer I can hear the sounds it's connected but nothing is showing. Need help to turn it back on thanks. I can't even load in Download mode.
Thanks for any help.
Click to expand...
Click to collapse
1. Point us to that dubious unlock app please!
2. Very very often an issue occurs because a user do not use the correct commands or important error messages are thrown and the user do not show. So please write EXACTLY what you do. For example the exact command to proof the connection (e.g. "adb devices") and the exact result. easiest and best way is to just make a screenshot of anything.
3. Another example is how to you try to get into download mode? There are some guides which do not work so explain what you do always helps others to help you.
I use the following method:
Pull out battery
Plugin USB cable connected to the pc
Press vol Up and keep pressed while putting battery back in place
4. To avoid driver issues you should consider to use FWUL ( https://tinyurl.com/FWULatXDA ) for anything else then kdz flashing (this requires windows)
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
1. Point us to that dubious unlock app please!
2. Very very often an issue occurs because a user do not use the correct commands or important error messages are thrown and the user do not show. So please write EXACTLY what you do. For example the exact command to proof the connection (e.g. "adb devices") and the exact result. easiest and best way is to just make a screenshot of anything.
3. Another example is how to you try to get into download mode? There are some guides which do not work so explain what you do always helps others to help you.
I use the following method:
Pull out battery
Plugin USB cable connected to the pc
Press vol Up and keep pressed while putting battery back in place
4. To avoid driver issues you should consider to use FWUL ( https://tinyurl.com/FWULatXDA ) for anything else then kdz flashing (this requires windows)
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Hi, Thank you very much for taking your time and energy to answer me. I used Z3x to Factory the LG G4 (T-Mobile) I wanted to flash it by downgrading before to see if it could work. this is how I break the phone with the downgrading. So now the phone is not recognizing by the computer as Modem when I plugged in, I see it only as External Drive.
umarmansare said:
Hi, Thank you very much for taking your time and energy to answer me. I used Z3x to Factory the LG G4 (T-Mobile) I wanted to flash it by downgrading before to see if it could work. this is how I break the phone with the downgrading. So now the phone is not recognizing by the computer as Modem when I plugged in, I see it only as External Drive.
Click to expand...
Click to collapse
you cannot downgrade h811 it has antirollback. and in autoprime 20i thread says it bricks phone.. if it was on MM and flashed lower antirollback.
what is Z3x.???

Locked bootloader by mistake, can't use the phone now

Hey all,
I just got a OnePlus 5T and because I needed a specific system language I decided to flash a custom ROM. I unlocked the bootloader, flashed Derpfest on it and it was all good until I made a mistake. From the Developers options I unchecked "OEM Unlocking" and then when I restarted into the bootloader I did a fastboot oem lock
Now the phone says it's corrupted and it won't boot. Since it's bootloader is locked I can't unlock it, I can't go into recovery and I can't start the phone. Is there anything else I can do to get it back? I don't care about wiping everything at this point, I'm just trying to get it back to a working state.
I want to add I did try the Unbrick tool https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012 but I am getting stuck at the drivers. Windows won't see QHUSB_BULK in device manager and I don't see anywhere else where the driver for the phone might be. I do see the device when doing fastboot devices but again, can't see what drivers is using.
Thanks!
Emo113 said:
Hey all,
Since it's bootloader is locked I can't unlock it, I can't go into recovery and I can't start the phone. Is there anything else I can do to get it back? I don't care about wiping everything at this point, I'm just trying to get it back to a working state.
I want to add I did try the Unbrick tool https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012 but I am getting stuck at the drivers. Windows won't see QHUSB_BULK in device manager and I don't see anywhere else where the driver for the phone might be. I do see the device when doing fastboot devices but again, can't see what drivers is using.
Thanks!
Click to expand...
Click to collapse
The unbrick tool is your best bet, what you need to do is follow the instructions. If its windows 10, you can go to device manager and update drivers from there. Make sure you are logged in as admin. Also some antivirus don't like the MSM tool so you may need to disable that.
Ensure the sequence is right. Connect usb wire to computer, press volume up, connect usb c to phone. Some ppl have tried pressing both volume up and down at the same time to make it work (same way as resolving Sahara error). If it boots first thing you need to do is back up efs.
Second you need to run these commands
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit.
It will save the persist.img on your phone internal memory. Save this as well as efs somewhere safe. Also share the persist.img with me cause I need it for the OPlus 5t for my phone.
Hope it helps
sn809 said:
The unbrick tool is your best bet, what you need to do is follow the instructions. If its windows 10, you can go to device manager and update drivers from there. Make sure you are logged in as admin. Also some antivirus don't like the MSM tool so you may need to disable that.
Ensure the sequence is right. Connect usb wire to computer, press volume up, connect usb c to phone. Some ppl have tried pressing both volume up and down at the same time to make it work (same way as resolving Sahara error). If it boots first thing you need to do is back up efs.
Second you need to run these commands
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit.
It will save the persist.img on your phone internal memory. Save this as well as efs somewhere safe. Also share the persist.img with me cause I need it for the OPlus 5t for my phone.
Hope it helps
Click to expand...
Click to collapse
Thanks for the help! I ended up finding a different Windows PC with no memory of the drivers for this phone so I was able to install them in the correct order and then run the MSM tool to get the phone back to stock Oreo. From there I unlocked the bootloader again to install TWRP and then my custom ROM.
Emo113 said:
Thanks for the help! I ended up finding a different Windows PC with no memory of the drivers for this phone so I was able to install them in the correct order and then run the MSM tool to get the phone back to stock Oreo. From there I unlocked the bootloader again to install TWRP and then my custom ROM.
Click to expand...
Click to collapse
That is superb. If you could do the other bit I would really appreciate it.
Thanks
sn809 said:
That is superb. If you could do the other bit I would really appreciate it.
Thanks
Click to expand...
Click to collapse
Hey there, sorry I totally mis-read the last part of your original post as something that I should do and I didn't see that you need that. Since I used the MDM tool I didn't bother to try your way first and since the phone wasn't mine to keep I already gave it to the owner so I don't have access to it anymore.
Again, very sorry about that.
No dramas. I also got it from some one else who was kind enough to lend it to me and let me root it and wipe it clean and then get the file and start using his phone again.
Thanks

emmc error? Suddenly black screen

Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
slev!n said:
Hello guys,
Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
slev!n said:
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
Click to expand...
Click to collapse
slev!n said:
Hello guys,
I've got an issue and don't know if it belongs to the build or not. I'm on the last build with my 3T and today after charging my phone I couldn't turn on WiFi or start any app. It just didn't open. So I restated my phone but it never booted. Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
Sounds to me like an hardware error involving (but not necessarily limited to) emmc access. That would explain, why the parts still in ram (like homescreen) were still working but apps won't start anymore, as well as the blank screen on device startup (even the logo needs emmc access to read the logo partition).
Try unbricking (I'm afraid your pc won't find the device, if my guess is correct), if that fails: rma or repair center.
slev!n said:
Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
150208 said:
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
Click to expand...
Click to collapse
Thanks, I'll create a post there. Just one more post here:
I used this phone just carefully at home as a media device. So this brick came totally out of nowhere. When I connect my bricked 3T now to my computer it makes the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more pop up again.
slev!n said:
I'll create a post there.
Click to expand...
Click to collapse
When you've created that post ask the moderators to move this complete conversation from this thread to the newly created on in the help forum, please. This helps to keep this thread readable and searcheble.
For your trouble: if you can't boot rom, recovery nor fastboot mode, it doesn't make sense to debug the usb connection: what should the pc connect to if none of the three is bootable? There is just nothing up to connect to. That's why I recommended unbrick tool - if that fails rma or go to a repair center.
Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
Post SS of the device manager after connecting the phone to the PC
150208 said:
Post SS of the device manager after connecting the phone to the PC
Click to expand...
Click to collapse
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
@slev!n: please ask the moderators to move the existing conversation to thos from the los16 thread here. If all postings have moved, ask the moderators to move this thread from op3/help to op3t/help.
@nvertigo67 I wanted to do so and was searching how to contact moderators but couldn't find it in my XDA app. Maybe someone can give me a hint? I'm kind of new on xda... Thanks!
@150208 And as I wrote: it's not possible to get any kind of message on windows anymore. Just the sound appears when I connect and disconnect.
@nvertigo67 I was also following your advice to use the unbrick tool. I followed the steps on oneplus forum:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
When it comes to the integrity check windows doesn't accept "TESTSIGNING ON". And so windows doesn't recognise my phone in the device manager for the next steps.
And I guess RMA or repair centres are super expensive. I don't know if it's worth it? I thought about buying a device with a broken screen on eBay and try to change the motherboard...
Log in with a web browser locate each posting of the comversation. For each posting in question use the little triangle icon at the botom on the left side, report each posting, set non-urgent and pit the link of this thread together with something like "Please move this posting to the linked thread, thanx in advance".
For disabling driver signature enforcement try method 2. from this post: http://maxedtech.com/about-testmode/
Most of tbe time xda postings are more reliable and more current then the Oneplus forums: https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722, https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722
slev!n said:
[MENTION=4405529]i thought about buying a device with a broken screen on eBay and try to change the motherboard...
Click to expand...
Click to collapse
If you already have a thought why do you keep asked here though? If you want another possible solution, at least put an effort to provide the information needed when asked by the one who tried to help you
I'm not into a guessing games, so i'm out
nvertigo67 said:
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
Click to expand...
Click to collapse
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
If it's hw problem, i'll try not to jump on MB conclussion yet, since there are still another possible reason
When talking about MSM, you need to make sure it's available first on the device manager
Otherwise, it's a waste of data for downloading the tool in these human malware days
Oh yes, the msm guide is quite lag behind. You don't need to boot into test mode anymore with the current driver for qualcomm
I flashed a lot qualcomm devices with w10 without the need to boot into test mode
150208 said:
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
Click to expand...
Click to collapse
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
For the costs of rma: maybe it's expensive - maybe oneplus will be obliging... Since you don't relay on the device as your daily driver, you can ask for an estimate of costs - so you can decide if it's worth the costs.
nvertigo67 said:
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
Click to expand...
Click to collapse
Wait, I fail to see your explanation in line with mine. I want to start debug it on the windows side, but you seems to see it on the phone side.
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
150208 said:
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
Click to expand...
Click to collapse
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc. In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side. Once this is fixed (at least fastboot mode is up again) you can utilize the "normal" usb connection again.
What do you want to do with the usb connection, if neither fastboot mode nor recovery is up amd running? What is your suggested next step, if the device is recognized? What should the pc recognize if neither fastboot nor adb os an option? Which command or procedure will fix the emmc?
nvertigo67 said:
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc.
Click to expand...
Click to collapse
Yes, there are other tools but i'm not gonna bother since it's paid
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect. There are 4 status when a device plugged into the pc.
1. detected and driver is loaded
2. detected and driver isn't loaded
3. detected but not recognized
4. no sign at all
1 and 2 is sw problem, 3 and 4 is hw problem
In order for MSM to do it's job, you need to have either problem no 1 or 2 with qualcomm qloader 9008 driver already or later detected in devmanager
So it's important to know the driver status
OP states there was sounds coming then nothing, which mean it's either 2 or 3, more like 3 but again i repeating myself i don't like guessing games
I don't understand the part why you're explaining/asking about fastboot recovery or etc, his phone is on dead state, nothing-literally-no sign of life unless he plug it to the pc and then it making sounds for the first time,
Why do you even bother thinking about it?
nvertigo67 said:
Which command or procedure will fix the emmc?
Click to expand...
Click to collapse
No procedure will fixed his phone since there are no enough information
I think your other question should be already answered. If else, i don't know what to say anymore.
150208 said:
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect.
Click to expand...
Click to collapse
If so, please explain how you can format a partition or fix the partition table if neither fastboot mode nor recovery (or a rooted system for that matter) is bootable.
@slev!n: please give a screenshot of the device manager to @150208. I'm too curious to learn how to fix a broken emmc without recovery nor fastboot mode.
Thank you so far!
I dont want to bother someone. Just thinking about further options thats why I wrote my thought about replacing the motherboard down.
I 'm in test mode now and I did this:
"Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for a few seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB (under COMs and Ports)]."
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
slev!n said:
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
Click to expand...
Click to collapse
The pic is from msm tool, not the device manager. No unknown device in device manager?

How to UNBRICK?

Hi, everybody
I had the brilliant idea to try to re-lock the bootloader after installing a custom ROM, now my Acquaris X Pro is bricked. ?
I realized that the only way to resurrect it is to use Qualcomm Flash Image Loader (QFIL) by loading the original firmware. The software starts and reveals the Qualcomm HS-USB Diagnostics 900E (COM3) interface and asks me to load the contents.xml file of the programmer.
I then downloaded the latest firmware from the official https://www.bq.com/en/support/aquaris-x-pro/support-sheet page and unpacked the archive, where I found the contents.xml file which I then uploaded to QFIL.
The status window indicates that the prog_emmc_firehose_8953_ddr.mbn file is missing and is trying to load from the BOOT.BF.3.3 folder, which clearly is not present. So I looked for this online and found the folder to download on a Git repository (https://git.szzt.com/yixing/ticai_src). I downloaded the folder and placed it in the path where QFIL expects to find it. I then reloaded the contents.xml file and it reports me the lack of an additional file: rawprogram_unsparse.xml belonging to a certain folder MSM8953.LA.3.0.1.
Unlike the first one, I can't find this last folder online. Can someone help me? ?
Hi @fede91it,
Sorry for the late answer - I have been quite inactive on xda recently
Unfortunately I don't have a solution for you right away, but I got a working X Pro with stock rom (+twrp and magisk) and a bit of experience with the "standard" tools like adb and fastboot. Never worked on such a low level like you though.
Does the tool you mentioned (QFIL) offer the possibility to grab contents from the phone instead of downloading it to it?
Maybe we can get the missing data from my phone?
Sorry for the dump/obvious question, but: What happens in the current bricked state when you turn the phone on? You can't enter fastboot and unlock..?
Another approach: have you tried contacting BQ? Maybe via their forum https://www.mibqyyo.com/. Possibly the missing files are device specific and you would need bqs help..
Thanks for your answer.
I have contacted BQ but they no longer deal with Android phones, I have no support from them.
As for you, thanks for your availability, but the files I'm looking for are for development and don't end up on my phone, so it's impossible to try to extract them from your phone.
By now I've changed phones and kept the Bq as a paperweight brick
fede91it said:
Thanks for your answer.
I have contacted BQ but they no longer deal with Android phones, I have no support from them.
As for you, thanks for your availability, but the files I'm looking for are for development and don't end up on my phone, so it's impossible to try to extract them from your phone.
By now I've changed phones and kept the Bq as a paperweight brick
Click to expand...
Click to collapse
Hey, did you recover your paperweight? I'm in the same situation but with the BQ X PRO
I could not solve it. There are some files missing for the compilation, and I can't find them
Have you tried this method by only using the firehose? forum.hovatek.com/thread-31505.html
Hey, did you recover? I made the same mistake as you. I managed to repair ...
What I did was:
- I removed the battery cable (I did not remove the battery completely)
- I pressed on VolDown button and connected the phone via usb to the pc and immediately went into fastboot mode
- I opened the BQ app on the pc, I loaded the rom and put it to install the rom. It asked to unlock the bootloader (which is what we want) ... The ROM could not be flashed, but it is not important ... As soon as you unlocked the bootloader, the phone started up without a problem
fede91it said:
Hi, everybody
I had the brilliant idea to try to re-lock the bootloader after installing a custom ROM, now my Acquaris X Pro is bricked. ?
I realized that the only way to resurrect it is to use Qualcomm Flash Image Loader (QFIL) by loading the original firmware. The software starts and reveals the Qualcomm HS-USB Diagnostics 900E (COM3) interface and asks me to load the contents.xml file of the programmer.
I then downloaded the latest firmware from the official https://www.bq.com/en/support/aquaris-x-pro/support-sheet page and unpacked the archive, where I found the contents.xml file which I then uploaded to QFIL.
The status window indicates that the prog_emmc_firehose_8953_ddr.mbn file is missing and is trying to load from the BOOT.BF.3.3 folder, which clearly is not present. So I looked for this online and found the folder to download on a Git repository (https://git.szzt.com/yixing/ticai_src). I downloaded the folder and placed it in the path where QFIL expects to find it. I then reloaded the contents.xml file and it reports me the lack of an additional file: rawprogram_unsparse.xml belonging to a certain folder MSM8953.LA.3.0.1.
Unlike the first one, I can't find this last folder online. Can someone help me? ?
Click to expand...
Click to collapse
Hello! Maybe it's too late, but I have the same problem as you and I found this post that talks about our mobile! In it you can find a lot of information, but also the links to download the stock ROMs and the flashing tool to get back to the factory Rom and unbrick the phone! I leave you the links below! Hope it also helps others with the same problem as we! Greeting
Post:
[HOW-TO] BQ Aquaris X Pro | [Stock-ROM] Unlock,Recovery,Root,Upgrade (TWRP/Magisk)
Hi everyone. :) This Post (post #1) shows the complete process of unlocking, flashing, rooting etc. in general, it may refer to old firmware and/or tool versions but the steps remain the same for newer versions. The chapters rely on each other...
forum.xda-developers.com
Link of stock ROMs and the flashing tool:
Support - Aquaris X Pro
web.archive.org
Hi,
Have you ever successfully got it to work again?
Thanks
rufus.wilson said:
Hi,
Have you ever successfully got it to work again?
Thanks
Click to expand...
Click to collapse
Hi,
I managed to get everything working properly.
I installed the Lineage OS custom rom and it works 5 *, with a custom rom you should not block the boot loader, it was the mistake I made.
The solution I used I described 2 comments above
MigSantosPT said:
Hi,
I managed to get everything working properly.
I installed the Lineage OS custom rom and it works 5 *, with a custom rom you should not block the boot loader, it was the mistake I made.
The solution I used I described 2 comments above
Click to expand...
Click to collapse
Hi,
Ah ok.
Just opened it, disconnected the battery. While pressing down VOL- button, I connected it to USB.
Nothing happens on the phone screen. I don't even see the blinking red light now.
Device manager shows it as 9008 COM port.
BQ flash tool doesn't recognise the phone.
I previously installed BQ drivers and rebooted.
Any other suggestions, before I close it back?
rufus.wilson said:
Hi,
Ah ok.
Just opened it, disconnected the battery. While pressing down VOL- button, I connected it to USB.
Nothing happens on the phone screen. I don't even see the blinking red light now.
Device manager shows it as 9008 COM port.
BQ flash tool doesn't recognise the phone.
I previously installed BQ drivers and rebooted.
Any other suggestions, before I close it back?
Click to expand...
Click to collapse
It is strange because it usually shows something on the screen right away ... Pressing the Power button also does not appear anything?
Did you install the ADB drivers? After the ADB drivers are installed, the BQ program recognizes the smartphone
and it also opens doors to use the command line to do almost anything.
rufus.wilson said:
Hi,
Ah ok.
Just opened it, disconnected the battery. While pressing down VOL- button, I connected it to USB.
Nothing happens on the phone screen. I don't even see the blinking red light now.
Device manager shows it as 9008 COM port.
BQ flash tool doesn't recognise the phone.
I previously installed BQ drivers and rebooted.
Any other suggestions, before I close it back?
Click to expand...
Click to collapse
the number 9008 sounds like the EDL mode and NOT the wanted fastboot mode which is required by the usual way of flashing via bq tool or fastboot/adb tools.
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
sorry, no solution, only confirming..

Question "Your device is corrupt" - how to unbrick with linux (or mac) ?

Yes, after a mistake of mine my phone is now bricked with the message on the screen: device is corrupt; means I also can't get into fastboot mode anymore.
I recently switched to Linux (mint) and have little experience here, I'm also not a computer nerd.
Does anyone know if or how it is possible to unbrick my device under Linux? Alternatively I would still have an old Mac.
The Internet search has really brought nothing. Am grateful for any help.
I had the same issue once.
How I fixed it was I got it into fastboot mode, I then switched slots...
If your phone is set to active on the wrong slot it will show that it is corrupt...
I'm not sure if this is your exact situation but if it is hopefully this will help.. Cheers
TENlll423 said:
I had the same issue once.
How I fixed it was I got it into fastboot mode, I then switched slots...
If your phone is set to active on the wrong slot it will show that it is corrupt...
I'm not sure if this is your exact situation but if it is hopefully this will help.. Cheers
Click to expand...
Click to collapse
Thanks. The thing is, I don´t know, how I come out of this "corrupt device mode" into fastboot mode. My case is, that I wanted to lock the bootloader; than this happened... I neither know how to get into fastboot mode, neither what to do next....
Flying Fox said:
Thanks. The thing is, I don´t know, how I come out of this "corrupt device mode" into fastboot mode. My case is, that I wanted to lock the bootloader; than this happened... I neither know how to get into fastboot mode, neither what to do next....
Click to expand...
Click to collapse
Hold all three buttons in and it should boot to fastboot mode takes like 10 to 15 sec.
That happened to my friend he tried to lock his phone and it ended up in the same situation..
So he typed in "OEM unlock" cuz it was halfway locked or bricked however you want to look at it. Lol
Then type "fastboot devices" and so on.....,
I know you can type in "fastboot getvar all"
That will show you the current slot you're in..
Then enter "fastboot set_active a or b"
That will get you on the slot that you should be able to boot into no problem...
You could try making a virtual machine, load Windows into it and try the normal MSM tool? Hopefully the USB passthrough would work:
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
TENlll423 said:
Hold all three buttons in and it should boot to fastboot mode takes like 10 to 15 sec.
That happened to my friend he tried to lock his phone and it ended up in the same situation..
So he typed in "OEM unlock" cuz it was halfway locked or bricked however you want to look at it. Lol
Then type "fastboot devices" and so on.....,
Click to expand...
Click to collapse
Tried this for so many times.. never worked... until u messaged me, thx..
Anyway still no success
TENlll423 said:
I know you can type in "fastboot getvar all"
That will show you the current slot you're in..
Then enter "fastboot set_active a or b"
That will get you on the slot that you should be able to boot into no problem...
Click to expand...
Click to collapse
Thanks so much, but unfortunately it says: device doesn´t support....
djsubterrain said:
You could try making a virtual machine, load Windows into it and try the normal MSM tool? Hopefully the USB passthrough would work:
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
Click to expand...
Click to collapse
Thx, but I think I will loose guaranty after using the tool. And I don´t know how to create a virtual machine... sounds crazy..
In worst case I will send my phone back and let it "repair".
Thanks to everybody.. nice to see how many people want to help
Keep asking around just because it's on that devices corrupt screen does not mean your phone is bricked my phone has been like that probably three different times and I've always recovered it..
Flying Fox said:
Thanks. The thing is, I don´t know, how I come out of this "corrupt device mode" into fastboot mode. My case is, that I wanted to lock the bootloader; than this happened... I neither know how to get into fastboot mode, neither what to do next....
Click to expand...
Click to collapse
I'm case this happens in the future you can split your hard drive into two partitionss and choose which os to boot when you restart. Can you get into edl?
Thanks everybody, just saw ur answers. Found my old notebook with windows 7 and linux dualboot today and tried via MSM-Tool. "Device not found". Somehow I was not able to install Qualcom drivers which could be the reason for.
Reason for bricking was my own fault. Somehow the unlock slider in the developer settings was on off and greyed out (after factory reset). Then I did the mistake in fastboot mode to type "fastboot oem lock".. U should never do this .. but I don´t know if I have any chance to get it to run in this case....
Flying Fox said:
Thx, but I think I will loose guaranty after using the tool. And I don´t know how to create a virtual machine... sounds crazy..
In worst case I will send my phone back and let it "repair".
Thanks to everybody.. nice to see how many people want to help
Click to expand...
Click to collapse
The MSM Tool does NOT void your warranty. OnePlus has confirmed this a few times. It's what they provide in the direst of circumstances but a lot of people just use it now to perform a "complete reset" back to factory settings. It should always work because it uses the primary Qualcomm bootloader.
If your phone is not being recognised then it's likely because driver signing is enabled so Windows is not recognising the EDL drivers.
Check my post here for more info : https://forum.xda-developers.com/t/completely-bricked-someone-help.4298085/post-85251113
djsubterrain said:
The MSM Tool does NOT void your warranty. OnePlus has confirmed this a few times. It's what they provide in the direst of circumstances but a lot of people just use it now to perform a "complete reset" back to factory settings. It should always work because it uses the primary Qualcomm bootloader.
If your phone is not being recognised then it's likely because driver signing is enabled so Windows is not recognising the EDL drivers.
Check my post here for more info : https://forum.xda-developers.com/t/completely-bricked-someone-help.4298085/post-85251113
Click to expand...
Click to collapse
Late answer due to personal reasons. Thanks for that info. But on my older notebook I´ve still windows 7. Try to find a solution or bring the device back when I´m "fit" again. Thx anyway!!!
EDIT: Problem solved. Couldn´t boot into the EDL-mode, therefore my phone was not recognized. Getting there was a little tricky because the display remained black... that I could not even notice that the phone was already in EDL mode,.In the end but great thanks.

Categories

Resources