Hello, I've bought the HTC U Ultra for my birthday at a very good price (250€) and I'm very satisfied about this phone!
Only, it's been 3 months since I try to root without any success. I can not find the "fastboot" mode in the bootloader and I do not know how.
Yet I followed all the tutorials to the letter (French expression I do not know if you go to understand ... x)) but I have never reached that point. I have the ADBs and all the other files needed.
Also, I made all the updates at the first launch of the phone. Is that why it's blocked?
Thank you in advance.
PS: I also unlocked the bootloader in the development options.
PS n°2: I post here because the French forums are desperate desert for this phone.
Hold both volume down + power together for around 10 seconds. Your phone will vibrate after that. You will then enter download mode, which is actually fastboot.
bc Yume said:
Hold both volume down + power together for around 10 seconds. Your phone will vibrate after that. You will then enter download mode, which is actually fastboot.
Click to expand...
Click to collapse
Ok, but when I want to unlock the bootloader using htcdev, I have < waiting for device > when i enter fastboot oem get_identifier_token.
SofianeLasri said:
Ok, but when I want to unlock the bootloader using htcdev, I have < waiting for device > when i enter fastboot oem get_identifier_token.
Click to expand...
Click to collapse
The computer is unable to recognise your phone. Maybe another port.
bc Yume said:
The computer is unable to recognise your phone. Maybe another port.
Click to expand...
Click to collapse
my device is recognize when it's start, but when it reboot to bootloader, abd / fastboot lost the connection. :/
I've tried with all of my ports.
SofianeLasri said:
my device is recognize when it's start, but when it reboot to bootloader, abd / fastboot lost the connection. :/
I've tried with all of my ports.
Click to expand...
Click to collapse
Are you sure you have USB Debugging on and you are using ADB driver from Google, not the one comes from HTC Sync?
bc Yume said:
Are you sure you have USB Debugging on and you are using ADB driver from Google, not the one comes from HTC Sync?
Click to expand...
Click to collapse
I use minimal adb 1.4.2 and i don't installed htc sync.
I use adb command line directly from Android Developers and have absolutely no problem. Maybe uninstall minimal adb and try that one. I can't help you with something I am not familiar with.
bc Yume said:
I use adb command line directly from Android Developers and have absolutely no problem. Maybe uninstall minimal adb and try that one. I can't help you with something I am not familiar with.
Click to expand...
Click to collapse
Yes but I must to download a lot of GB to user these abd. :/
I've just install htc sync, I tell you more if it work.
UPDATE : Oh it work! x) I never thought it would work! I thought htc sync was a software like those samsull that block the phone.
cool but i've now s-on and a i can"t install twrp with this. x)
SofianeLasri said:
cool but i've now s-on and a i can"t install twrp with this. x)
Click to expand...
Click to collapse
You can install TWRP as long as your bootloader is unlocked, regardless of the status of S-ON or S-OFF
SofianeLasri said:
cool but i've now s-on and a i can"t install twrp with this. x)
Click to expand...
Click to collapse
double check "Allow USB debugging" for the computer. From Developers "Revoke USB debugging Auth" . Unplug & plug back USB cable should come up with dialog box for auth. You may (not sure) this from cmd: adb reboot fastboot which could come up with error msg: "error: device unauthorized. This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device."
You cant find fastboot mode because it is now called download mode...
Related
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse
alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.
Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.
Q Mobile X 32
bootloader oem unlock problem
plz help
Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32
Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?
Here's what the guide says...
Not working anymore.
Sorry.
Do you mean that you had your old tablet already killed, and then you recovered it following these steps?
You can see it here, in my Twitter
https://twitter.com/victorcangil16/status/642389331768942592
Can anyone confirm this on a separate dead tablet? if so its a pretty damn good find.
Hi Victorcangil 16,
Could you exactly discribe how did you make this miracle (which drivers...) ?
Thanks
jo2e said:
Hi Victorcangil 16,
Could you exactly discribe how did you make this miracle (which drivers...) ?
Thanks
Click to expand...
Click to collapse
I used Windows 10 with the NVIDIA Family USB Drivers. I made the process I described in the first post
Victorcangil 16 said:
I used Windows 10 with the NVIDIA Family USB Drivers. I made the process I described in the first post
Click to expand...
Click to collapse
Ok,
Thx for your reply Victorcangil 16.
But how did your device was recognized by windows before done this process ? APX or something else
It was reconized as normal device by Windows, like if I plug my phone to the PC. And the drivers I had to configure them manually, if not, It gives me error when doing FastBoot
Victorcangil 16 said:
It was reconized as normal device by Windows, like if I plug my phone to the PC. And the drivers I had to configure them manually, if not, It gives me error when doing FastBoot
Click to expand...
Click to collapse
It stay on :"<waiting for device>"
And my tablet is not reconized as normal device but as "APX"
What does APX mean?
Change the ADB drivers interface using the next process:
Search in Windows: Device Manager
If the ADB interface has a Yellow alert, Right Click, Update Drivers, Select from Computer, Use Disk, Use all, and then select the file in the NVIDIA Drivers folder (in my case, Downloads). Accept,
Victorcangil 16 said:
What does APX mean?
Click to expand...
Click to collapse
I don't known. My tablet appears like that in the peripherics manager ...
If you hace skype, I can help you easily
Victorcangil 16 said:
If you hace skype, I can help you easily
Click to expand...
Click to collapse
Yes i have skype.
But i think i got the problem : my tablet wasn't rooted and the bootloader was locked...
I think you saved your shield because it was rooted...
I thinks is that. If is has not unlocked bootloader, you can't change nothing. But to unlock it, just type in Fastboot: "fastboot oem unlock" (tablet will Factory Reset)
Victorcangil 16 said:
I thinks is that. If is has not unlocked bootloader, you can't change nothing. But to unlock it, just type in Fastboot: "fastboot oem unlock" (tablet will Factory Reset)
Click to expand...
Click to collapse
Same thing with this command : <waiting for device>
:/ I think something is going on with Drivers
Hi, one question for such kind of reactivation - root is required ?
Yes, Root and Unlocked Bootloader are required ro recover the "killed" Tablet
Just bought by mistake deactivated Shield...is it possible to make root via fastboot ?
Hi
sorry if post is duplicated , i search but not found on this topic
When i connect my mobile to pc and then run command to go to bootloader ,
it shows Daemon not running. Starting it now on port 5037
then goes to bootloader
in bootloader no command work there , means only adb reboot bootloader works
even fastboot devices shows nothing
please advise me what i have to do
Sorry for my bad English
Thanks
if from your pc you type:
adb reboot bootloader
does it go to the bootloader?
If so, while the bootloader is displayed, from the pc if you type:
fastboot devices
Are you saying it responds with nothing?
minhas4all said:
Hi
sorry if post is duplicated , i search but not found on this topic
When i connect my mobile to pc and then run command to go to bootloader ,
it shows Daemon not running. Starting it now on port 5037
then goes to bootloader
in bootloader no command work there , means only adb reboot bootloader works
even fastboot devices shows nothing
please advise me what i have to do
Sorry for my bad English
Thanks
Click to expand...
Click to collapse
So I'm confused.
If I type "adb reboot bootloader" with my phone connected; it boots into fast boot mode and will accept fastboot commands.
it shows the "Fastboot" screen with the option to start the device if the power buttoned is pressed.
What are you trying to do?
Are you saying you don't get the screen?
Zargone said:
if from your pc you type:
adb reboot bootloader
does it go to the bootloader?
If so, while the bootloader is displayed, from the pc if you type:
fastboot devices
Are you saying it responds with nothing?
Click to expand...
Click to collapse
Thanks
when i enter fastboot devices
it does nothing just go to next prompt
nothing happen
i want to unlock bootloader and root
Thanks once again
tech_head said:
So I'm confused.
If I type "adb reboot bootloader" with my phone connected; it boots into fast boot mode and will accept fastboot commands.
it shows the "Fastboot" screen with the option to start the device if the power buttoned is pressed.
What are you trying to do?
Are you saying you don't get the screen?
Click to expand...
Click to collapse
Thanks
with me when I type "adb reboot bootloader" with my phone connected; it boots into fast boot mode but in fastboot no command works
i want to unlock bootloader and root
thanks
Did you remember to go into the developer options and enable USB Debugging and OEM Unlock?
jhs39 said:
Did you remember to go into the developer options and enable USB Debugging and OEM Unlock?
Click to expand...
Click to collapse
That was my next question.
jhs39 said:
Did you remember to go into the developer options and enable USB Debugging and OEM Unlock?
Click to expand...
Click to collapse
Yes
tech_head said:
That was my next question.
Click to expand...
Click to collapse
Yes
I root many phones
its easy
even i try other cables and 3 different laptops and pc
and the result was same
minhas4all said:
Yes
I root many phones
its easy
even i try other cables and 3 different laptops and pc
and the result was same
Click to expand...
Click to collapse
What drivers are you using.
I presume you are on a Windows laptop?
yes on windows 10
Sent from my PH-1 using XDA Free mobile app
Sounds like you're using an older fastboot, so you'll need to do fastboot -i 0x2e17 <whatever_command>
Or you can get the latest platform tools from https://developer.android.com/studio/releases/platform-tools#downloads
Did you install the essential phone drivers?
not sure about version but download some days back from links provided.. any ways thanks download from ur link then let u know
thanks
Sent from my PH-1 using XDA Free mobile app
ziddey said:
Sounds like you're using an older fastboot, so you'll need to do fastboot -i 0x2e17 <whatever_command>
Or you can get the latest platform tools from https://developer.android.com/studio/releases/platform-tools#downloads
Click to expand...
Click to collapse
not sure about version but download some days back from links provided.. any ways thanks download from ur link then let u know
thanks
crixley said:
Did you install the essential phone drivers?
Click to expand...
Click to collapse
Thinks so but can u provide me the links? thanks
I've tried several times to unlock the bootloader and it will not respond to any commands once in fastboot mode. I've tried to follow this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ but whenever I type "fastboot oem unlock" it just says "waiting for any device" and nothing happens. I have usb debugging enabled and oem unlocking on so I don't know what I'm doing wrong. I have the platform tools from Google installed. I can run adb and type "adb reboot bootloader" and it responds, but after that, no fastboot commands work. I mainly just wanted to root so I could restore my apps and data via Titanium Backup. Is there a temp root solution I can use? Or has anyone else experienced this?
Let me know if you need more info. Hopefully this is an easy one.
What do you get if you run "adb devices"?
thedrizzle said:
What do you get if you run "adb devices"?
Click to expand...
Click to collapse
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
blockhead428 said:
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
Click to expand...
Click to collapse
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes ? I'm not sure if I can put a link on here
DinarQ8 said:
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I've done that also. Developer options are enabled, USB debugging, and OEM unlocking. Are there newer drivers I need? But if that was an issue, it wouldn't allow me to do "adb reboot bootloader". It'll reboot to fastboot mode, but after typing "fastboot oem unlock" it just says waiting for any device.
blockhead428 said:
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
Click to expand...
Click to collapse
In the picture it shows you typed your commands all capitals letters
Dr8ven said:
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes I'm not sure if I can put a link on here
Click to expand...
Click to collapse
Try and post it. It let me post the link to the guide in the initial posting. You could be on to something.
This is where I got my version of ADB. https://developer.android.com/studio/releases/platform-tools It's not so much an "install" as it is unpacking a zip archive.
twinnfamous said:
In the picture it shows you typed your commands all capitals letters
Click to expand...
Click to collapse
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
blockhead428 said:
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
Click to expand...
Click to collapse
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
I used the adb installer from the same video. Once you unzip it. It's an .exe file which I granted administrator rights to install... it installs adb and drivers and it worked for me
That's the video and did it to a T
Another thing don't use power shell use command
twinnfamous said:
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
Click to expand...
Click to collapse
I'm following a video now. I'm thinking I didn't have the ADB drivers installed so I'm trying that now.
Let us know how it turned out ?
Dr8ven said:
Let us know how it turned out
Click to expand...
Click to collapse
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
blockhead428 said:
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
Click to expand...
Click to collapse
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
blockhead428 said:
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
Click to expand...
Click to collapse
I was thinking that maybe the latest OTA broke the bootloader unlock process, but someone else in this thread said they just unlocked theirs. I don't understand what the issues is. I've followed this video so closely I could re-enact it in my sleep.
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Nice! For a noob I wasn't too far off lol it just had to be one of those two issues
Enjoy happy rooting ?
blockhead428 said:
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Click to expand...
Click to collapse
Hi I have the same problem, when fastboot it says waiting device. I also had rooted my other phone, so how to find my other driver phone in device manager because I can't find it
Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!
ZSparda said:
Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!
Click to expand...
Click to collapse
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?
Wolfcity said:
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?
Click to expand...
Click to collapse
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.
ZSparda said:
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.
Click to expand...
Click to collapse
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?
PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.
Wolfcity said:
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?
Click to expand...
Click to collapse
I tried to attach a couple of screenshots but I get the "bad request" message here. Anyways, when we do a normal boot we get the validation error message and we are sent directly to fastboot menu, but there we cannot choose any options because all of them lead to the error message again.
It's been a couple of weeks now but the last time we tried doing something, the device wasn't showing up in device administrator nor being recognized by adb.
As regards to the battery, we've left it charge up for some hours, so I guess that's not a problem, although we cannot see the percentage.
[email protected] said:
PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.
Click to expand...
Click to collapse
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?
ZSparda said:
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?
Click to expand...
Click to collapse
This thread is long, but alot of good info on hard bricked Moto G5 plus devices.
Code:
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
To get PC in test mode
Code:
Here is how to turn on or off the Test Mode feature in Windows 10.
IMPORTANT: Please remember that turning off the Test Mode feature may force the program/driver which is not digitally signed stop working.
Step 1: Open Command Prompt as administrator. To do so, type CMD in Start menu search to see Command Prompt in the search result. Right-click on Command Prompt entry and then click Run as administrator option. Click Yes button when you see the User Account Control screen.
Step 2: At the Command Prompt window, execute the following commands:
To enable the Test Mode:
Bcdedit.exe -set TESTSIGNING ON
To disable the Test Mode:
Bcdedit.exe -set TESTSIGNING OFF
If the above command didn’t work, this one must work:
Bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
Bcdedit.exe -set TESTSIGNING OFF
You may exit the Command Prompt now.
[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Thanks! I'll send him all these so he can try. I'll update as soon as possible.
[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.
ZSparda said:
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.
Click to expand...
Click to collapse
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about
Code:
fastboot devices
? It should show the device #. ADB doesn't always show devices.
[email protected] said:
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about ? It should show the device #. ADB doesn't always show devices.
Click to expand...
Click to collapse
Yes! Fastboot devices shows the device! So now we have to procede with the flashblank.zip and all that from the other post right? Also sorry for the late reply, I've been pretty busy these past days so I left him with all the work.