Hi
I flashed my HTC One M7 firmware to OS-7.19.401.2 (Unfrotunately wasn't in S-Off when I did it).
This is what it looks lke at the moment:
*** RELOCKED ***
M7-UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.19.401.2 (7.19.401.2)
I did it after I tried to update to Lollipop from Android 4.4.3 which crashed on me. Being impatient I terminated the update after taking so long.
I tried relashing but am not having any luck getting it to return to normal(when I do reflash it the second time with the same command it stalls at the silver htc logo screen), I do have the unlock.bin file but it's not working and I can't access the SDcard on the phone either.
Thanks for any help!
klaymeb said:
Hi
I flashed my HTC One M7 firmware to OS-7.19.401.2 (Unfrotunately wasn't in S-Off when I did it).
This is what it looks lke at the moment:
*** RELOCKED ***
M7-UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.19.401.2 (7.19.401.2)
I did it after I tried to update to Lollipop from Android 4.4.3 which crashed on me. Being impatient I terminated the update after taking so long.
I tried relashing but am not having any luck getting it to return to normal(when I do reflash it the second time with the same command it stalls at the silver htc logo screen), I do have the unlock.bin file but it's not working and I can't access the SDcard on the phone either.
Thanks for any help!
Click to expand...
Click to collapse
seems your using a custom firmware, try this one >> https://www.androidfilehost.com/?fid=95916177934533542
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
So I changed the zip folder name to firmware, And reflashed it again as per above instructions, And it worked...
The only thing is I keep ending back at the same point again, of the phone not going back into Anfroid (I haven't put a Sim card back in yet)...
What else do I need to do to get it back into Android? Stuck in Bootloader....
klaymeb said:
So I changed the zip folder name to firmware, And reflashed it again as per above instructions, And it worked...
The only thing is I keep ending back at the same point again, of the phone not going back into Anfroid (I haven't put a Sim card back in yet)...
What else do I need to do to get it back into Android? Stuck in Bootloader....
Click to expand...
Click to collapse
This is my fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3688mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
klaymeb said:
This is my fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3688mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
!!!!read all steps first!!!!
1. unlock your bootloader
2. flash custom recovery TWRP 2.8.5.0 ("fastboot flash recovery twrp.img" then "fastboot erase cache" finally "fastboot reboot-bootloader")
3. download this rom https://basketbuild.com/dl/devs?dl=Artur0588/M7_7.19.401.2.zip and put it on the fastboot/adb folder
4. extract firmware.zip (thread #2) and copy boot.img in the fastboot folder
5. extract from the firmware.zip (that you've downloaded in thread #2) recovery.img and paste in the fastboot/adb folder
6. "adb devices" to verify that your device is connected, then "adb push rom.zip /sdcard/" it will take about 5 min.
7. now "fastboot flash boot boot.img" then "fastboot reboot-bootloader"
8. enter to recovery mode and make full wipe (data/dalvick/chache)
9. choose install >> select rom.zip and swipe.
10. when installation finish up flash the stock recovery "fastboot flash recovery recovery.img" , "fastboot erase cache" , "fastboot oem lock" and "fastboot erase cache"
Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.
klaymeb said:
Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.
Click to expand...
Click to collapse
Write the unlock command that you are using here, and the error message too.
klaymeb said:
Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.
Click to expand...
Click to collapse
Are you using the correct drivers for Windows 8.1?
In your device manager is your phone detected?
When your phone is in bootloader is it detected by fastboot? Type fastboot devices into your command prompt and it should list the serial no of your device.
Also, use USB 2.0 rather than 3.0
VoynichJimmy said:
Write the unlock command that you are using here, and the error message too.
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin (as per HTCdev instructions)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1492578304 bytes
error: cannot load 'Unlock_code.bin': No error
klaymeb said:
fastboot flash unlocktoken Unlock_code.bin (as per HTCdev instructions)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1492578304 bytes
error: cannot load 'Unlock_code.bin': No error
Click to expand...
Click to collapse
The command looks like it's ok. The unlock code is definitely in your fastboot folder
When you go to device manager when your phone is connected at the bootloader screen is your phone detected there? Does the command fastboot devices show your serial no?
stovie_steve said:
Are you using the correct drivers for Windows 8.1?
Driver Version: 2.0.7.27
In your device manager is your phone detected?
Yes.
When your phone is in bootloader is it detected by fastboot? Type fastboot devices into your command prompt and it should list the serial no of your device.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
FA426W904521 fastboot
Also, use USB 2.0 rather than 3.0
Click to expand...
Click to collapse
Ok Thanks, I thought that might be the case with it.
stovie_steve said:
The command looks like it's ok. The unlock code is definitely in your fastboot folder
When you go to device manager when your phone is connected at the bootloader screen is your phone detected there?
Does the command fastboot devices show your serial no?
Click to expand...
Click to collapse
Only thing I can think of if your drivers are working, fastboot detects your phone and you are running the right command is to start it again and request a new unlock code
stovie_steve said:
Only thing I can think of if your drivers are working, fastboot detects your phone and you are running the right command is to start it again and request a new unlock code
Click to expand...
Click to collapse
I just tried that, but no luck...
This is what I'm getting at the moment:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
I think the SDCard is not working.
klaymeb said:
I just tried that, but no luck...
This is what I'm getting at the moment:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
I think the SDCard is not working.
Click to expand...
Click to collapse
The sdcard wouldn't have any effect on this working...
The unlock code should be in your adb folder on your PC
stovie_steve said:
The sdcard wouldn't have any effect on this working...
The unlock code should be in your adb folder on your PC
Click to expand...
Click to collapse
I have put it in a ADB_Windows folder which was created when I installed Minimal ADB and Fastboot software, so I'm not sure why it's not running at this stage.
Do I need to reinstall ADB and Fastboot on the PC again and create a new folder for it?
klaymeb said:
I have put it in a ADB_Windows folder which was created when I installed Minimal ADB and Fastboot software, so I'm not sure why it's not running at this stage.
Do I need to reinstall ADB and Fastboot on the PC again and create a new folder for it?
Click to expand...
Click to collapse
What is the folder directory where you have your adb and fastboot files?
stovie_steve said:
What is the folder directory where you have your adb and fastboot files?
Click to expand...
Click to collapse
Just figured out that I wast trying to use the Unlock file in the wrong place, This is what I've just done now:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unloc
k_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.151s
klaymeb said:
Just figured out that I wast trying to use the Unlock file in the wrong place, This is what I've just done now:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unloc
k_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.151s
Click to expand...
Click to collapse
And I just tried this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.033s]
finished. total time: 0.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (551346 KB)...
OKAY [ 20.471s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 72.998s
klaymeb said:
And I just tried this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.033s]
finished. total time: 0.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (551346 KB)...
OKAY [ 20.471s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 72.998s
Click to expand...
Click to collapse
As you are s-on, your bootloader needs to be locked to flash firmware, unlock it after the flash, but just to be sure, as you struggled to even unlock your bootloader, which firmware are you trying to flash, because if its the wrong one, you'll hard brick your phone.
if your looking to upgrade to Lollipop, just flash this, it will make you full stock Lollipop, it will also wipe your device, so make sure you backup anything you want to keep
https://www.androidfilehost.com/?fid=95916177934537475
just rename the file once its downloaded to RUU and put it in the same folder as adb, fastboot, your unlock code etc on your computer and then follow these instructions:
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip RUU.zip - fully automated so no need to do it twice
fastboot reboot-bootloader
fastboot reboot
after your first setup, you can do what you want, unlock your bootloader at this point, flash a custom recovery, root etc.
Seanie280672 said:
As you are s-on, your bootloader needs to be locked to flash firmware, unlock it after the flash, but just to be sure, as you struggled to even unlock your bootloader, which firmware are you trying to flash, because if its the wrong one, you'll hard brick your phone.
if your looking to upgrade to Lollipop, just flash this, it will make you full stock Lollipop, it will also wipe your device, so make sure you backup anything you want to keep
https://www.androidfilehost.com/?fid=95916177934537475
just rename the file once its downloaded to RUU and put it in the same folder as adb, fastboot, your unlock code etc on your computer and then follow these instructions:
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip RUU.zip - fully automated so no need to do it twice
fastboot reboot-bootloader
fastboot reboot
after your first setup, you can do what you want, unlock your bootloader at this point, flash a custom recovery, root etc.
Click to expand...
Click to collapse
So this is what I did, And I still end up back at the bootloader.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Device was already locked!
OKAY [ 0.001s]
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.032s]
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1264453 KB)...
OKAY [ 41.892s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 122.212s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.035s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Something messed up with my phone from last night. All of sudden it was dead and no signs of wake up expect battery led notification while charging. System showed.= qhsusb_bulk driver failed and I managed to fix it using SDK studio. Later it detected as Qualcomdevice loader. I did Blankflash, after few sec rebooted to fastboot mode. Downloaded the latest GPT files for the version NPJS25.93-14-8 and executed the below commands (pasted the result below)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
be51d16 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
error: cannot load 'gpt.bin': No such file or directory
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootlo
ader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
error: cannot load 'bootloader.img': No such file or directory
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.020s
Can you please hep to fix it.
Thanks
Suhi77 said:
Something messed up with my phone from last night. All of sudden it was dead and no signs of wake up expect battery led notification while charging. System showed.= qhsusb_bulk driver failed and I managed to fix it using SDK studio...
Click to expand...
Click to collapse
I don't have this device but, I believe that one or both of the following threads may be helpful for what you need and don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=3475832
https://forum.xda-developers.com/showthread.php?t=1770816
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Thanks Ibuprophen for the reply. As I was travelling last week I find no time to check this.
I downloaded the latest unviersal adroid flasher to troubleshoot my phone.
However I failed in first step. My phone is not recognized under devices.
I think its coz of the issue
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot partition: not found
error: cannot load 'gpt.bin': No such file or directory
Is there anyway I can get my device listed on the list.
Thanks.
Hi, I was trying to unlock the bootloader of my Moto Z3 play (xt1929-4). I had the latest adb and fastboot installd, latest drivers installed. Tried on different computer, linux and win with no success. Below is the error from a linux machine.
fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Click to expand...
Click to collapse
And sometimes it says:
fastboot oem get_unlock_data
(bootloader) slot-countxes: not found
(bootloader) slo: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Click to expand...
Click to collapse
Here is the getvar
fastboot getvar all
(bootloader) slot-countta: not found
(bootloader) slot-suffi: not found
(bootloader) allt-suffixes: not found
getvar:all FAILED (remote failure)
finished. total time: 0.000s
Click to expand...
Click to collapse
Other than not being able to unlock bootloader, do not have any concerns with the device and works great. Any help is greatly appreciated.
same issue
have you been able to solve it?
Hello
I just purchased a cheap new Moto G7 Plus, only to install LineageOS on it. The phone is brand new and I just upgraded it to the latest Android 10.
I followed all instructions so far, and I am stuck, can't unlock the bootloader and/or install a recovery.
To unlock the bootloader I carefully followed instructions on the LineageOS wiki
Then I followed instructions on Motorola website
I received an email from Motorola with the unlock code
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock CODE_RECEIVED_IN_THE_MAIL
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: 0.016s
Despite the fact that it says OKAY, when I reboot in fastboot flash mode, I still see the message "oem_locked". So I am not totally sure that the unlock succeeded.
Then whatever I try, I can't install TWRP, see below :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
Z*****F5RR fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock CODE_RECEIVED_IN_THE_MAIL
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp-3.4.0-0-lake.img
target reported max download size of 536870912 bytes
sending 'boot' (30080 KB)...
OKAY [ 0.686s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.708s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.4.0-0-lake.img
downloading 'boot.img'...
OKAY [ 0.686s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.702s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I obviously googled a few time but can't find any working solution. Some says its because my OEM is still locked, others because the USB port or cable might be problematic. I tried on 5 USB ports and a USB hub and I have the same issue, and my cable is brand new. I also restarted the whole unlocking procedure, received another mail from Motorola, with exactly the same unlock key, unlocked 10 times, nothing changes.
Any hint ?
Cheers
Ok forget it, its solved. I am an idiot I forgot to activate developer mode in the settings
Fastboot boot twrp 3.4 infinitely?
Unlocked my oem, adp whenever I fastboot boot twrp 3.4 it just gets stuck on downloading. No fail code just stays on downloading infinitely. Would love some help!
same
Richard2707 said:
Unlocked my oem, adp whenever I fastboot boot twrp 3.4 it just gets stuck on downloading. No fail code just stays on downloading infinitely. Would love some help!
Click to expand...
Click to collapse
trying on my xt1965-2 and having this same issue, did you manage a workaround?
The twrp file needs to be in the correct location and the name needs to be exact.
I use linux so check up on which locations to use in windows.
But on linux I open a terminal in the folder where twrp is located.
So if the filename for twrp is for instance "twrp-3.3.1-0-lake.img", the command needs to be:
fastboot boot twrp-3.3.1-0-lake.img (NO spaces in the file name!)
Fastboot then pushes the file to the phone and boots it.
Hello guys!
I have an XT1929-4 on android pie and I am having issues with unlocking my bootloader.
I am using the fastboot unlock method and I am always getting stuck with the "fastboot oem get_unlock_data" command. "fastboot devices" shows my device serial number. OEM unlock and USB debugging is also turned on in the devices settings. The tool I am using is the minimal ADB and Fastboot software. Tools mode config is enabled when I do the fastboot commands, If 'fastboot oem help' should work, then maybe all 'fastboot oem' commands are not working for me.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY2268BV45 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-countta: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.002s
^I did the fastboot oem get_unlock data twice here.
I was planning to flash pixelexperience rom when I saw the thread here. Thank you in advance and I hope somebody can help.
FIXED: i used all three usb A ports of my laptop. I tried using the usb c port of the laptop by using a usb c to usb a adapter. fastboot oem get_unlock_data worked.