I have an odd problem that I never experienced before, maybe some have? Using Linux (Arch with android-tools installed), I'm trying to unlock my XZ2C like I have done lots of time with "sudo fastboot oem unlock 0x". But, this time it just wont run. The cursor jumps about 30 characters (spaces I guess) and just sits there, nothing else happens. Have to pull the cable to the phone to "abort" fastboot. It looks like this (the FAILED part is what I get after I pull the cable);
Code:
*#*sudo fastboot oem unlock 0x9366CB600ED6A33C
[sudo] lösenord för zynex:
< waiting for any device >
FAILED (Status read failed (No such device))
fastboot: error: Command failed
I have tried change the cable, but still the same. Any ideas?? I read in the twrp thread about a bootloader bug, not sure if that have something to do with it. I'm on latest fw (52.0.A.10.6).
PS, yes I have OEM unlock checked, ADB debug etc etc...
-- Mike
zynexx said:
I have an odd problem that I never experienced before, maybe some have? Using Linux (Arch with android-tools installed), I'm trying to unlock my XZ2C like I have done lots of time with "sudo fastboot oem unlock 0x". But, this time it just wont run. The cursor jumps about 30 characters (spaces I guess) and just sits there, nothing else happens. Have to pull the cable to the phone to "abort" fastboot. It looks like this (the FAILED part is when what I get after I pull the cable);
Code:
*#*sudo fastboot oem unlock 0x9366CB600ED6A33C
[sudo] lösenord för zynex:
< waiting for any device >
FAILED (Status read failed (No such device))
fastboot: error: Command failed
I have tried change the cable, but still the same. Any ideas?? I read in the twrp thread about a bootloader bug, not sure if that have something to do with it. I'm on latest fw (52.0.A.10.6).
PS, yes I have OEM unlock checked, ADB debug etc etc...
-- Mike
Click to expand...
Click to collapse
Latest is 11.3
I would update first
Do you use at least platform tools v29.0.4?
Is the phone in the blue led fastboot mode?
MartinX3 said:
Latest is 11.3
I would update first
Do you use at least platform tools v29.0.4?
Is the phone in the blue led fastboot mode?
Click to expand...
Click to collapse
Ah, seems that 11.3 hasn't been released here yet then, still says I'm up to date. Not sure if that's the issue here thou?
Yep, use android-tools v29.0.4-2, that's the latest release on Arch Linux.
Yes, it's blue. It finds the device when running fastboot devices, and continues after the "waiting for any device" part, but get stuck after that. Never had this issue before, so I'm not sure where to start. Maybe an issue with the bootloader itself?
zynexx said:
Ah, seems that 11.3 hasn't been released here yet then, still says I'm up to date. Not sure if that's the issue here thou?
Yep, use android-tools v29.0.4-2, that's the latest release on Arch Linux.
Yes, it's blue. It finds the device when running fastboot devices, and continues after the "waiting for any device" part, but get stuck after that. Never had this issue before, so I'm not sure where to start. Maybe an issue with the bootloader itself?
Click to expand...
Click to collapse
The bootloader didn't change since months
Do you use the correct code or only "0x"?
And does "fastboot getvar all" gives you output?
(Bootloader version should be 118)
Can't install TWRP on XZ2C
Guys, trying to install TWRP recovery in Fastboot, posting that code: "fastboot flash boot twrp-3.2.3-0-xz2p.img" and it says that "twrp-3.2.3-0-xz2p.img not found", although i've put .img file in ADB directory. Can't figure it out
MartinX3 said:
The bootloader didn't change since months
Do you use the correct code or only "0x"?
And does "fastboot getvar all" gives you output?
(Bootloader version should be 118)
Click to expand...
Click to collapse
I used the code I got from Sony. Maybe should check so I entered the correct IMEI?
Yep, did get a bunch of stuff from it. Can post it if it would help?
m4ikl1983 said:
Guys, trying to install TWRP recovery in Fastboot, posting that code: "fastboot flash boot twrp-3.2.3-0-xz2p.img" and it says that "twrp-3.2.3-0-xz2p.img not found", although i've put .img file in ADB directory. Can't figure it out
Click to expand...
Click to collapse
Bit of topic here, but check so you have read permission for the file (if using Linux). Not sure what you mean by ADB directory, but I guess you mean the directory you have the binary in? You will need to provide the full path to the image file (if you are not in the same directory), fx ~/Download/yourimage.img.
MartinX3 said:
The bootloader didn't change since months
Do you use the correct code or only "0x"?
And does "fastboot getvar all" gives you output?
(Bootloader version should be 118)
Click to expand...
Click to collapse
Not sure why, but I think I entered the wrong IMEI last time. Although, I get the same problem. Running the command, the cursor just jumps like 30-35 characters to the right and stays there, not additional text. Have to pull the cable to abort the command.
This is some of the output from getvar (omitted the partition part);
(bootloader) hw-revision:20001
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4015
(bootloader) version-baseband:1311-5320_52.0.A.10.6
(bootloader) version-bootloader:1310-7079_X_Boot_SDM845_LA2.0_P_118
(bootloader) erase-block-size: 0x1000
(bootloader) logical-block-size: 0x1000
(bootloader) variant:SDM UFS
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:BH901602BZ
(bootloader) serial:28b51f27
(bootloader) product:H8324
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
Click to expand...
Click to collapse
Ok, this was pretty odd. While typing the last comment here, I had run the unlock command and it was just sitting there in the backgrund for a couple of minutes, nothing happened. Pulled the cable, and then the bootloader was magically unlocked anyway. So problem fixed. Not sure why I didn't get any output from the command though
One question though, when rebooting I get a lock pad icon and the text "You device software can't be checked for corruption. Please lock your bootloader". Never seen that on a Sony device before. Is his a new thing?
m4ikl1983 said:
Guys, trying to install TWRP recovery in Fastboot, posting that code: "fastboot flash boot twrp-3.2.3-0-xz2p.img" and it says that "twrp-3.2.3-0-xz2p.img not found", although i've put .img file in ADB directory. Can't figure it out
Click to expand...
Click to collapse
Please follow the TWRP instructions in the TWRP thread.
Your command is wrong.
---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------
zynexx said:
Ok, this was pretty odd. While typing the last comment here, I had run the unlock command and it was just sitting there in the backgrund for a couple of minutes, nothing happened. Pulled the cable, and then the bootloader was magically unlocked anyway. So problem fixed. Not sure why I didn't get any output from the command though
One question though, when rebooting I get a lock pad icon and the text "You device software can't be checked for corruption. Please lock your bootloader". Never seen that on a Sony device before. Is his a new thing?
Click to expand...
Click to collapse
Nice to hear that it works now.
I never saw a android device which doesn't mention on boot that it got unlocked.
So it isn't new for me.
Ahh btw
Since you unlocked on 9.0 your camera will still work in stock.
(In custom rom anyway but there the camera is under construction and get its next update this or next month, but only on android 10.0 with 4.14 kernel).
MartinX3 said:
Please follow the TWRP instructions in the TWRP thread.
Your command is wrong.
---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------
Nice to hear that it works now.
I never saw a android device which doesn't mention on boot that it got unlocked.
So it isn't new for me.
Ahh btw
Since you unlocked on 9.0 your camera will still work in stock.
(In custom rom anyway but there the camera is under construction and get its next update this or next month, but only on android 10.0 with 4.14 kernel).
Click to expand...
Click to collapse
Tried the camera, and it works like a charm
Oh, I never saw anything like it on my other Xperias, just the normal Sony logo The only device I seen it on is Samsungs.
Althougt, I still having problem now that I'm about to flash TWRP. Get the same problem as before, just
hangs there without anything happens.
Code:
Sending 'boot.img' (30904 KB) #FAILED (remote: 'unknown command')
fastboot: error: Command failed
The # is where the cursor is, and when i pull the cable I get FAILED. This is pretty odd.
zynexx said:
Tried the camera, and it works like a charm
Oh, I never saw anything like it on my other Xperias, just the normal Sony logo The only device I seen it on is Samsungs.
Althougt, I still having problem now that I'm about to flash TWRP. Get the same problem as before, just
hangs there without anything happens.
Code:
Sending 'boot.img' (30904 KB) #FAILED (remote: 'unknown command')
fastboot: error: Command failed
The # is where the cursor is, and when i pull the cable I get FAILED. This is pretty odd.
Click to expand...
Click to collapse
Did you follow the twrp instructions carefully including the correct booting into the fastboot mode?
MartinX3 said:
Did you follow the twrp instructions carefully including the correct booting into the fastboot mode?
Click to expand...
Click to collapse
Yep, I read about the bug and booted into fastboot with adb. But still hangs the same way when I tried unlocking the bootloader itself. Also downloaded the platform tools from Google and tried the fastboot from there, but still same outcome.
Is there another way to flash TWRP, think I seen a app of some kind long ago. But I guess I need to have it rooted before I can use it. Think I have a moment 22 situation here :/
zynexx said:
Yep, I read about the bug and booted into fastboot with adb. But still hangs the same way when I tried unlocking the bootloader itself. Also downloaded the platform tools from Google and tried the fastboot from there, but still same outcome.
Is there another way to flash TWRP, think I seen a app of some kind long ago. But I guess I need to have it rooted before I can use it. Think I have a moment 22 situation here :/
Click to expand...
Click to collapse
That's a very weird situation
Did you try it with another computer?
Or with linux instead of windows?
Or switched the slot to slot A with "fastboot --set-active=a" ?
That also requires to flash the newest 11.3 stock firmware again.
(With xperifirm and newflasher from XDA since OTA won't work any longer.)
MartinX3 said:
That's a very weird situation
Did you try it with another computer?
Or with linux instead of windows?
Or switched the slot to slot A with "fastboot --set-active=a" ?
That also requires to flash the newest 11.3 stock firmware again.
(With xperifirm and newflasher from XDA since OTA won't work any longer.)
Click to expand...
Click to collapse
Just tried with another one, running KDE Neon. Same problem. Always using Linux, don't even own a Windows system
Tried fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img, but that one got stuck to. Nothing happens. I will try flash 11.3 and see is that might solve the issue I have.
zynexx said:
Just tried with another one, running KDE Neon. Same problem. Always using Linux, don't even own a Windows system
Tried fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img, but that one got stuck to. Nothing happens. I will try flash 11.3 and see is that might solve the issue I have.
Click to expand...
Click to collapse
So weird.
You use google plattform tools v29.x and I assume a up to date linux distribution? (I tested it with at least kernel 4.15, running 5.0 now).
Since we both use the same bootloader, it must be something in your hardware or usb cable which disturbs the communication.
MartinX3 said:
So weird.
You use google plattform tools v29.x and I assume a up to date linux distribution? (I tested it with at least kernel 4.15, running 5.0 now).
Since we both use the same bootloader, it must be something in your hardware or usb cable which disturbs the communication.
Click to expand...
Click to collapse
Yep, downloaded the latest one from Google to but got the same error. Using Arch, so it's very up to date Using kernel 5.3.7-arch1-2-ARCH. Have tried another USB cable to, I will see if I can dig out a third one and try.
Btw, seems that NCB firmware are still at 10.6, that' why I haven't gotten any update yet.
zynexx said:
Yep, downloaded the latest one from Google to but got the same error. Using Arch, so it's very up to date Using kernel 5.3.7-arch1-2-ARCH. Have tried another USB cable to, I will see if I can dig out a third one and try.
Btw, seems that NCB firmware are still at 10.6, that' why I haven't gotten any update yet.
Click to expand...
Click to collapse
No woories, the 11.3 is only relevant for the TWRP installation.
A "fastboot boot twrp.img" should still work.
Maaaaybe the kernel is too new and contains a driver bug?
MartinX3 said:
No woories, the 11.3 is only relevant for the TWRP installation.
A "fastboot boot twrp.img" should still work.
Maaaaybe the kernel is too new and contains a driver bug?
Click to expand...
Click to collapse
I downloaded Customized DE 11.3 and flashed it, but still have problem trying fastboot boot twrp.img.
This is very odd indeed. Don't think it's the kernel, the other computer has kernel 4.4.
Starting to think there's an problem with the phone itself, whatever that could be!?
MartinX3 said:
No woories, the 11.3 is only relevant for the TWRP installation.
A "fastboot boot twrp.img" should still work.
Maaaaybe the kernel is too new and contains a driver bug?
Click to expand...
Click to collapse
It seems that I can't do anything regarding fastboot, except rebooting it. Nothing else work, tried fastboot --set-active=a, but nothing happens at all. Tried fastboot flash boot twrp.img, same thing. Fastboot executes, but then nothing. Have to pull the cable to abort the program.
Have never in all the years I played with Android phones run into this stuff. Fastboot has always worked.
Code:
*# sudo fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.051s
*# sudo fastboot --set-active=a
<no output after this>
Related
Hello
My device is running on Marshmellow [arm64-v8a] with locked bootloader [i cant able to unlock due to getting unknown command error]
so today i found that OTA which can able to upgrade my marshmellow to android N
so i think if i somehow inject superuser apk in OTA/system/priv-app and then i update my phone using that modified OTA, will it work to gain full root access?
or should i something try another method to inject super user in ota.zip?
so how to do?
Thank you
tcpcd said:
Hello
My device is running on Marshmellow [arm64-v8a] with locked bootloader [i cant able to unlock due to getting unknown command error]
so today i found that OTA which can able to upgrade my marshmellow to android N
so i think if i somehow inject superuser apk in OTA/system/priv-app and then i update my phone using that modified OTA, will it work to gain full root access?
or should i something try another method to inject super user in ota.zip?
so how to do?
Thank you
Click to expand...
Click to collapse
Mostly likely not, bootloader is locked meaning you can only run verified images.
Let's see why you can't unlock the bootloader instead.
What steps have you done, etc.
Matt07211 said:
Mostly likely not, bootloader is locked meaning you can only run verified images.
Let's see why you can't unlock the bootloader instead.
What steps have you done, etc.
Click to expand...
Click to collapse
FIrst i enable usb debugging and oem unlocker in developer setting
then i enter 'adb reboot bootloader' to boot into bootloader
after i entered 'fastboot oem unlock' so i got an error that 'unknown command'
so i guess my device manufacture somehow changed unlocking code.
after googling i found that oem unlock code saved in aboot.img file [https://www.reddit.com/r/Android/comments/54wz8j/how_to_discover_hidden_fastboot_commands/]
therefore i try to grab aboot from /dev/block using dirtycow, but BIG FAILURE
so i thought maybe in OTA Chinese company always hide their backdoor. so what if i inject superuser in my OTA.zip.
EDIT:
File content in OTA.zip
Code:
+media
+app
+etc
+fake-libs
+fake-libs64
+fonts
+framework
+lib
+lib64
+bin
+nv
+presetapp
+priv-app
+tts
+usr
+vendor
+xbin
Description about my OTA [1.7gb]
- It can upgrade Marshmellow to Android N, by open recovery mode and choose OTA.zip file from mmc.
- It contain lots of system apk and device mfg apk.
tcpcd said:
FIrst i enable usb debugging and oem unlocker in developer setting
then i enter 'adb reboot bootloader' to boot into bootloader
after i entered 'fastboot oem unlock' so i got an error that 'unknown command'
so i guess my device manufacture somehow changed unlocking code.
after googling i found that oem unlock code saved in aboot.img file [https://www.reddit.com/r/Android/comments/54wz8j/how_to_discover_hidden_fastboot_commands/]
therefore i try to grab aboot from /dev/block using dirtycow, but BIG FAILURE
so i thought maybe in OTA Chinese company always hide their backdoor. so what if i inject superuser in my OTA.zip.
EDIT:
File content in OTA.zip
Description about my OTA [1.7gb]
- It can upgrade Marshmellow to Android N, by open recovery mode and choose OTA.zip file from mmc.
- It contain lots of system apk and device mfg apk.
Click to expand...
Click to collapse
What's your device model?
Have you tried searching for <device model> root?
No copy of aboot.img or bootloader etc name I'm a full firmware image?
Is your device the kinda of device where you need to request a unlock code from manufacturers website (I think it's Sony who does that, not sure who else).
Can you give me any more info to work with?
Matt07211 said:
What's your device model?
Have you tried searching for <device model> root?
No copy of aboot.img or bootloader etc name I'm a full firmware image?
Is your device the kinda of device where you need to request a unlock code from manufacturers website (I think it's Sony who does that, not sure who else).
Can you give me any more info to work with?
Click to expand...
Click to collapse
Model is Coolpad Note5
yes i searched everywhere to find root solution, even in official forum, but no success.
no my device dont need unlock code.
im sending you OTA.zip extracted link so you can see whats inside.
tcpcd said:
Model is Coolpad Note5
yes i searched everywhere to find root solution, even in official forum, but no success.
no my device dont need unlock code.
im sending you OTA.zip extracted link so you can see whats inside.
Click to expand...
Click to collapse
I'm wondering, is your device MediaTek based?
Matt07211 said:
I'm wondering, is your device MediaTek based?
Click to expand...
Click to collapse
no its qualcomm/snapdragon based
tcpcd said:
no its qualcomm/snapdragon based
Click to expand...
Click to collapse
Can you be specific?
What fastboot commands work and don't?
Matt07211 said:
Can you be specific?
What fastboot commands work and don't?
Click to expand...
Click to collapse
Code:
fastboot getvar all
^^work only this one
Code:
fastboot reboot
^^this is not woking even. just got output "reboot..." but fone actually not rebooting.
i tried fastboot oem unlock,unlock-go,flashing unlock << all Failed
tcpcd said:
^^work only this one
^^this is not woking even. just got output "reboot..." but fone actually not rebooting.
i tried fastboot oem unlock,unlock-go,flashing unlock << all Failed
Click to expand...
Click to collapse
Not even
Code:
fastboot boot boot.img
?
I've sadly never had a device with fastboot, so it ain't my area of expertise
Matt07211 said:
Not even
Code:
fastboot boot boot.img
?
I've sadly never had a device with fastboot, so it ain't my area of expertise
Click to expand...
Click to collapse
i think that command is working, but i didnt checked
i only checked oem commands with fastboot
tcpcd said:
Not even
i think that command is working, but i didnt checked
i only checked oem commands with fastboot
Click to expand...
Click to collapse
If you can boot custom boot.img then you can root it.
I personally rooted the xCover3 by modifying the boot.img
Matt07211 said:
If you can boot custom boot.img then you can root it.
I personally rooted the xCover3 by modifying the boot.img
Click to expand...
Click to collapse
no i cant boot custom images
tcpcd said:
no i cant boot custom images
Click to expand...
Click to collapse
Okay. Can you detail, EVERY method you've tried (any apps, fastboot commands Cave's (E.g. Dirty Cow) etc.) So we can get a clear overview and saves us both time as we are not going over the same stuff
Matt07211 said:
Okay. Can you detail, EVERY method you've tried (any apps, fastboot commands Cave's (E.g. Dirty Cow) etc.) So we can get a clear overview and saves us both time as we are not going over the same stuff
Click to expand...
Click to collapse
OKay
I tried Kingroot, kingoroot << Failed
Using dirtycow << Got success :cyclops: for temp root
Used farm-root to pull boot.img << termination after long wait
VIKIROOT << Working but not spawn shell
I only check fastboot oem commands but << failure
Code:
fastbooot oem unlock
fastbooot oem unlock-go
fastbooot oem unlock_go
fastbooot oem flashing unlock
fastbooot flashing unlock
fastbooot oemunlock
Output: FAILED (remote: unknown command)
Big 0
But one command work:
Code:
[stark]:~|$ fastboot getvar all
(bootloader) yl_udiskname:userdata
(bootloader) version:REFRESH_emmccid_new
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4199000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5a7bfbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x140000000
(bootloader) serialno:366da886
(bootloader) kernel:lk
(bootloader) product:MSM8952
all:
finished. total time: 0.022s
So I believe using dirtycow will probably be your chance at getting root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
Unless you figure out the correct fastboot commands
Matt07211 said:
So I believe using dirtycow will probably be your chance at getting root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
Unless you figure out the correct fastboot commands
Click to expand...
Click to collapse
Well dirtycow is only option for temp root
would this work on specific firmware, for example a combination firmware (factory binary on samsung) then install a custom recovery from there...?
tcpcd said:
Well dirtycow is only option for temp root
Click to expand...
Click to collapse
Well it's better then nothing, you can work Frkm there if roots such a bug deal for you
I think DC Unlocker Tool Maybe Work.
Update twrp within twrp is the goal. I am new to this, very new.
I am downloading from a different phone to my sd-card wich I then switch into the htc.
1How many files do I need to download on to my sd card? The twrp image, the md5 file and maybe a signature? Where do I need to look out for?
2 where can I get the right twrp download, right now it's version 2.7 something, 2.7.0.3 I think.
After this I am searching for a stock operating system. I thought to use roodjunky. Many files though wich I can't make any sense of. I can spot the .img file but thats it..
Help please!
Update
I am trying to use adb commands with my phone to update twrp/and put an os on it. So far no succes but it is connected. Connection tested with command "adb devices".
I'll keep trying to get the phone working.
Qrsimon said:
Update twrp within twrp is the goal.
Click to expand...
Click to collapse
Updating TWRP within TWRP requires v2.8.4 or later already installed, as clearly stated on the official TWRP website: https://twrp.me/htc/htconem8gsm.html
Qrsimon said:
I am trying to use adb commands with my phone to update twrp/and put an os on it. So far no succes but it is connected. Connection tested with command "adb devices".
Click to expand...
Click to collapse
For flashing TWRP, it isn't adb you want, it is fastboot. adb and fastboot are related, but 2 different things. For fastboot to work, you want to be on the bootloader screen (not TWRP or OS) with "fastboot USB" selected. Then use the command to test: fastboot devices
Keep in mind, what TWRP version you update to, depends on what OS version you are trying to restore. What OS number does it indicate on the bootloader screen (or if blank, what hboot number and what radio number?).
If you can get fastboot working, do fastboot getvar all, then post the output (delete IMEI and serial number) so we can see more info about the device.
---------- Post added at 09:54 AM ---------- Previous post was at 09:46 AM ----------
Qrsimon said:
After this I am searching for a stock operating system. I thought to use roodjunky. Many files though wich I can't make any sense of. I can spot the .img file but thats it..
Click to expand...
Click to collapse
That is one main reason I discourage folks using these random "root" websites (unless you know it is correct and reputable), and/or following YouTube videos to mod your phone. These things almost always are lacking a lot of critical nuance and detail. And they show you just enough to get yourself into trouble, without the proper tools or knowledge to get out of that trouble.
XDA is the best place for knowledge about custom recovery, root, etc. Not only is all the info you need on here, but we have a healthy active community, that is willing to help you when you have troubles or questions.
Case in point, the stock TWRP backup OS files are all right here, sticky thread at the top of this forum section: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Qrsimon said:
? The twrp image, the md5 file and maybe a signature? Where do I need to look out for?
Click to expand...
Click to collapse
You should disable MD5 and signature checking when flashing TWRP. But that is irrelevant flashing with fastboot, anyway (which you have to do, as mentioned).
fastboot getvar all
redpoint73 said:
Updating TWRP within TWRP requires v2.8.4 or later already installed, as clearly stated on the official TWRP website: https://twrp.me/htc/htconem8gsm.html
For flashing TWRP, it isn't adb you want, it is fastboot. adb and fastboot are related, but 2 different things. For fastboot to work, you want to be on the bootloader screen (not TWRP or OS) with "fastboot USB" selected. Then use the command to test: fastboot devices
Keep in mind, what TWRP version you update to, depends on what OS version you are trying to restore. What OS number does it indicate on the bootloader screen (or if blank, what hboot number and what radio number?).
If you can get fastboot working, do fastboot getvar all, then post the output (delete IMEI and serial number) so we can see more info about the device.
---------- Post added at 09:54 AM ---------- Previous post was at 09:46 AM ----------
That is one main reason I discourage folks using these random "root" websites (unless you know it is correct and reputable), and/or following YouTube videos to mod your phone. These things almost always are lacking a lot of critical nuance and detail. And they show you just enough to get yourself into trouble, without the proper tools or knowledge to get out of that trouble.
XDA is the best place for knowledge about custom recovery, root, etc. Not only is all the info you need on here, but we have a healthy active community, that is willing to help you when you have troubles or questions.
Case in point, the stock TWRP backup OS files are all right here, sticky thread at the top of this forum section: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
outcome: "fastboot getvar all"
adb server version (31) doesn't match this client (40); killing...
* daemon started successfully
C:\Users\Jan Jacob\Documents\platform-tools_r28.0.0-windows\platform-tools>fastb
oot devices
HT44JWM01035 fastboot
C:\Users\Jan Jacob\Documents\platform-tools_r28.0.0-windows\platform-tools>fastb
oot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Finished. Total time: 0.113s
redpoint73 said:
Updating TWRP within TWRP requires v2.8.4 or later already installed, as clearly stated on the official TWRP website: https://twrp.me/htc/htconem8gsm.html
For flashing TWRP, it isn't adb you want, it is fastboot. adb and fastboot are related, but 2 different things. For fastboot to work, you want to be on the bootloader screen (not TWRP or OS) with "fastboot USB" selected. Then use the command to test: fastboot devices
Keep in mind, what TWRP version you update to, depends on what OS version you are trying to restore. What OS number does it indicate on the bootloader screen (or if blank, what hboot number and what radio number?).
If you can get fastboot working, do fastboot getvar all, then post the output (delete IMEI and serial number) so we can see more info about the device.
---------- Post added at 09:54 AM ---------- Previous post was at 09:46 AM ----------
That is one main reason I discourage folks using these random "root" websites (unless you know it is correct and reputable), and/or following YouTube videos to mod your phone. These things almost always are lacking a lot of critical nuance and detail. And they show you just enough to get yourself into trouble, without the proper tools or knowledge to get out of that trouble.
XDA is the best place for knowledge about custom recovery, root, etc. Not only is all the info you need on here, but we have a healthy active community, that is willing to help you when you have troubles or questions.
Case in point, the stock TWRP backup OS files are all right here, sticky thread at the top of this forum section: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
I succesfully updated twrp to 2.8.3.0. It's not the 2.8.4.0 but it was my goal to make an update anyway. I was able to make this change through you, thanks! Stock os marshmallow is next~
You have the US AT&T version M8. When you say you want the stock OS, do you mean you want the AT&T branded stock ROM, or something unbranded?
If you want the AT&T branded OS, then easiest way is to use the RUU (ROM update utility). Simply download to PC (PC required), connect phone to PC, and run the RUU executable, which will walk you through the rest.
RUU will wipe everything on the phone, so plan accordingly as needed.
http://dl3.htc.com/application/RUU_...5.1494626502.1528829820-1877063669.1469710847
redpoint73 said:
You have the US AT&T version M8. When you say you want the stock OS, do you mean you want the AT&T branded stock ROM, or something unbranded?
If you want the AT&T branded OS, then easiest way is to use the RUU (ROM update utility). Simply download to PC (PC required), connect phone to PC, and run the RUU executable, which will walk you through the rest.
RUU will wipe everything on the phone, so plan accordingly as needed.
http://dl3.htc.com/application/RUU_...5.1494626502.1528829820-1877063669.1469710847
Click to expand...
Click to collapse
It's non responsive atm when running ruu wizzard. Stuck at updating logo with no bar status. Ehm it keeps saying sending on my laptop screen. Something I missed?
Qrsimon said:
It's non responsive atm when running ruu wizzard. Stuck at updating logo with no bar status. Ehm it keeps saying sending on my laptop screen. Something I missed?
Click to expand...
Click to collapse
i can't really communicate with the phone but I got this:
C:\Users\Jan Jacob\Documents\platform-tools_r28.0.0-windows\platform-tools>fastb
oot
fastboot: usage: no command
C:\Users\Jan Jacob\Documents\platform-tools_r28.0.0-windows\platform-tools>reboo
t fastboot
reboot wordt niet herkend als een interne
of externe opdracht, programma of batchbestand.
C:\Users\Jan Jacob\Documents\platform-tools_r28.0.0-windows\platform-tools>adb c
onnect devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
unable to connect to devices:5555: cannot resolve host 'devices' and port 5555:
Host is onbekend. (11001)
C:\Users\Jan Jacob\Documents\platform-tools_r28.0.0-windows\platform-tools>reboo
t fastboot
reboot wordt niet herkend als een interne
of externe opdracht, programma of batchbestand.
Qrsimon said:
i can't really communicate with the phone but I got this:
C:\Users\Jan Jacob\Documents\platform-tools_r28.0.0-windows\platform-tools>fastb
oot
fastboot: usage: no command
C:\Users\Jan Jacob\Documents\platform-tools_r28.0.0-windows\platform-tools>reboo
t fastboot
reboot wordt niet herkend als een interne
of externe opdracht, programma of batchbestand.
C:\Users\Jan Jacob\Documents\platform-tools_r28.0.0-windows\platform-tools>adb c
onnect devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
unable to connect to devices:5555: cannot resolve host 'devices' and port 5555:
Host is onbekend. (11001)
C:\Users\Jan Jacob\Documents\platform-tools_r28.0.0-windows\platform-tools>reboo
t fastboot
reboot wordt niet herkend als een interne
of externe opdracht, programma of batchbestand.
Click to expand...
Click to collapse
it says so 6.20.502.5 but does not load any os
Qrsimon said:
it says so 6.20.502.5 but does not load any os
Click to expand...
Click to collapse
It runs openrecoveryscript when the phone restarts.
Qrsimon said:
i can't really communicate with the phone but I got this:
C:\Users\Jan Jacob\Documents\platform-tools_r28.0.0-windows\platform-tools>fastboot
fastboot: usage: no command
C:\Users\Jan Jacob\Documents\platform-tools_r28.0.0-windows\platform-tools>reboot fastboot
Click to expand...
Click to collapse
The PC can communicate with the phone just fine. You were able to do fastboot devices (returned phone ID) and fastboot getvar all. The problem is the command quoted above are not valid fastboot commands. Did you see these somewhere, as it seems like you just made them up (you can't do that)!
So is this correct: you have the phone connected to PC in fastboot-bootloader mode, then you run the RUU executable on the PC, the phone goes to black screen with HTC logo, but no progress bar (just freezes)? This is the type of detail you should supply from the start, otherwise we waste time having to guess or ask you questions on what exactly happened.
---------- Post added at 10:30 AM ---------- Previous post was at 10:27 AM ----------
Qrsimon said:
C:\Users\Jan Jacob\Documents\platform-tools_r28.0.0-windows\platform-tools>adb connect devices
Click to expand...
Click to collapse
You can't run fastboot and adb commands at the same time, by definition. adb commands only work when the phone is booted to OS, or alternately they will work in TWRP. Fastboot commands only work when the phone is in bootloader-fastboot mode, and adb command will not work at that time.
---------- Post added at 10:33 AM ---------- Previous post was at 10:30 AM ----------
Qrsimon said:
it says so 6.20.502.5 but does not load any os
Click to expand...
Click to collapse
Having on OS listed on the bootloader screen, and version-main on getvar all, simply means that firmware is installed (hboot, radio baseband, etc.). The OS (system partition) can be wiped or corrupted/damaged, and it will still say an OS version number.
So you need to restore system partition, as you already figured from the start. But since the AT&T version has RUU tool, it is not typical for stock TWRP backup to be posted on these forums.
redpoint73 said:
The PC can communicate with the phone just fine. You were able to do fastboot devices (returned phone ID) and fastboot getvar all. The problem is the command quoted above are not valid fastboot commands. Did you see these somewhere, as it seems like you just made them up (you can't do that)!
So is this correct: you have the phone connected to PC in fastboot-bootloader mode, then you run the RUU executable on the PC, the phone goes to black screen with HTC logo, but no progress bar (just freezes)? This is the type of detail you should supply from the start, otherwise we waste time having to guess or ask you questions on what exactly happened.
---------- Post added at 10:30 AM ---------- Previous post was at 10:27 AM ----------
You can't run fastboot and adb commands at the same time, by definition. adb commands only work when the phone is booted to OS, or alternately they will work in TWRP. Fastboot commands only work when the phone is in bootloader-fastboot mode, and adb command will not work at that time.
---------- Post added at 10:33 AM ---------- Previous post was at 10:30 AM ----------
Having on OS listed on the bootloader screen, and version-main on getvar all, simply means that firmware is installed (hboot, radio baseband, etc.). The OS (system partition) can be wiped or corrupted/damaged, and it will still say an OS version number.
So you need to restore system partition, as you already figured from the start. But since the AT&T version has RUU tool, it is not typical for stock TWRP backup to be posted on these forums.
Click to expand...
Click to collapse
It was my goal to share everyting. I will try it the correct way with the RUU.
So is this correct: you have the phone connected to PC in fastboot-bootloader mode, then you run the RUU executable on the PC, the phone goes to black screen with HTC logo, but no progress bar (just freezes)? This is the type of detail you should supply from the start, otherwise we waste time having to guess or ask you questions on what exactly happened.
Is there a solution for the fact that there is no progress bar?
Qrsimon said:
Is there a solution for the fact that there is no progress bar?
Click to expand...
Click to collapse
Hard to answer your subsequent questions, when you didn't answer the question I asked, which you quoted. Twice.
Try starting over and running the RUU again. Sometimes it gets stuck for unknown reasons. Maybe you already tried multiple times. Who knows. It's hard to help when you don't provide sufficient info.
redpoint73 said:
Hard to answer your subsequent questions, when you didn't answer the question I asked, which you quoted. Twice.
Try starting over and running the RUU again. Sometimes it gets stuck for unknown reasons. Maybe you already tried multiple times. Who knows. It's hard to help when you don't provide sufficient info.
Click to expand...
Click to collapse
Sorry I did not read it correctly.
Fixed
Qrsimon said:
Update twrp within twrp is the goal. I am new to this, very new.
I am downloading from a different phone to my sd-card wich I then switch into the htc.
1How many files do I need to download on to my sd card? The twrp image, the md5 file and maybe a signature? Where do I need to look out for?
2 where can I get the right twrp download, right now it's version 2.7 something, 2.7.0.3 I think.
After this I am searching for a stock operating system. I thought to use roodjunky. Many files though wich I can't make any sense of. I can spot the .img file but thats it..
Help please!
Update
I am trying to use adb commands with my phone to update twrp/and put an os on it. So far no succes but it is connected. Connection tested with command "adb devices".
I'll keep trying to get the phone working.
Click to expand...
Click to collapse
The origin of error 170 ore 155 when running the RUU on my windows 7 laptop is due to the fact that the phone reboots a couple times, ore better: dissconects. For security reasons my laptop didn't allow any of that within. You can alter the notification level by run the RUU by double click it and when the administrator notification pops up, open the details.
The easiest way to acces the level of protection is by typing "uac" in the start search box. This leads to the uac(user acount control) settings.
Hello everybody,
once again I'm in trouble.
With help of Marcowe I updated my phone with no OS to Oreo
HTML:
https://forum.xda-developers.com/z2-force/help/z2-os-help-to-t3837577
I wanted to give it another try and here I my attempts to install LOS.
1. oem unlock
2. I booted into current twrp (fastboot boot twrp-3.2.3-2-nash.img
3. adb push of lineange onto internal sd card
4. In TWRP under advanced wipe I pressed format data (If I now think about it, in the progress windows there was some red text probably not a good sign)
5. I installed LOS with now error
6. There was an option to delete dalvik cache which I pressed
7 . System reboot
8. Black screen Device Manager shows me Qualcomm HS-USB QDLoader 9008 (COM6)
I tried a blankflash file from here
HTML:
https://unbricks.com/unbrick-motorola-moto-z2-force-update-fix-issues/
but it shows me an error. Log file will be at end of post.
QFIL does not find a corresponding MBN nor an XML file in stock rom
HTML:
https://forum.xda-developers.com/z2-force/development/factory-image-moto-z2-force-nash-retail-t3699306
If you have got any idea to get my phone back, I would be happy and would like to contribute.
Regards,
Bew
Log file:
[ 0.001] Opening device: \\.\COM6
[ 0.003] Detecting device
[ 34.009] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.009] Check qboot_log.txt for more details
[ 34.009] Total time: 34.011s
[ 34.009]
[ 34.009] qboot version 3.85
[ 34.009]
[ 34.009] DEVICE {
[ 34.009] name = "\\.\COM6",
[ 34.009] flags = "0x64",
[ 34.009] addr = "0x28FD74",
[ 34.009] api.bnr = "0x372FD8",
[ 34.009] }
[ 34.009]
[ 34.009]
[ 34.009] Backup & Restore {
[ 34.009] num_entries = 0,
[ 34.009] restoring = "false",
[ 34.009] backup_error = "not started",
[ 34.009] restore_error = "not started",
[ 34.009] }
[ 34.009]
Try this, power the phone back on. If you get that screen again cover the power button (don't press yet) with one finger, then cover the volume down button (don't press yet) with another.. Then press the power button, until the screen goes blank, then right after it does, (while still holding down the power button) Press the volume down button, until it comes on again.. Hopefully it will give you the bootloader instead.. If it does, Then find a flashll file for your carrier.
doubledragon5 said:
Try this, power the phone back on. If you get that screen again cover the power button (don't press yet) with one finger, then cover the volume down button (don't press yet) with another.. Then press the power button, until the screen goes blank, then right after it does, (while still holding down the power button) Press the volume down button, until it comes on again.. Hopefully it will give you the bootloader instead.. If it does, Then find a flashll file for your carrier.
Click to expand...
Click to collapse
Hello doubledragon5,
the screen is blank all the time. It stays black if I try to turn it on or off. The phone gives no sign if its on or off.
Regards,
Bew
b.bew said:
Hello doubledragon5,
the screen is blank all the time. It stays black if I try to turn it on or off. The phone gives no sign if its on or off.
Regards,
Bew
Click to expand...
Click to collapse
Sorry miss read your post.
Unbrick yo Brick quick ish
Here are the signed diag drivers for win
Qualcomm Diag Drivers Signed
attached is the blankflash zip
Unplug your phone, install diag drivers, replug and wait for the everything to recognize and settle.
Unzip the blankflash to a folder and run the bat file, after it's done you should be back in bootloader where you can re-flash the latest firmware for your phone.
Use 2.0 usb ports from your motherboard, not a hub like the front of your pc; and use the oem cable.
If you have trouble getting this to work then unplug your phone from your pc, uninstall your moto drivers and the qualcomm drivers. Restart. Reininstall the drivers, reboot; then plug your phone and wait for the drivers to recognize, install, and settle. You may need to try to run the blankflash a couple of times to get it to take. You may need to try alternate usb ports, even 3.0+
This phone can be super picky about ports, cables, and even adb/fastboot versions. For most they won't have to worry about most of this, but for others this is the basic setup that works for the majority of users.
*Note - To get into blankflash/edl mode manually...
from bootloader prompt 'fastboot oem blankflash' w/o quotes
via adb command 'adb reboot edl' w/o quotes
41rw4lk said:
Here are the signed diag drivers for win
Qualcomm Diag Drivers Signed
attached is the blankflash zip
Unplug your phone, install diag drivers, replug and wait for the everything to recognize and settle.
Unzip the blankflash to a folder and run the bat file, after it's done you should be back in bootloader where you can re-flash the latest firmware for your phone.
Click to expand...
Click to collapse
Thank you very much.
I was able to start in bootloader again. I was not able to flash the firmware via the procedure described by Marcowe (see link in first post, it mentioned that they are no sectors _a _b or something like that, I will recheck.). Still I was able too boot in Oreo.
I guess because its an A/B device? Does this mean that one is corrupted now?
Regards,
Bew
b.bew said:
Thank you very much.
I was able to start in bootloader again. I was not able to flash the firmware via the procedure described by Marcowe (see link in first post, it mentioned that they are no sectors _a _b or something like that, I will recheck.). Still I was able too boot in Oreo.
I guess because its an A/B device? Does this mean that one is corrupted now?
Regards,
Bew
Click to expand...
Click to collapse
So you're able to boot and use your phone, correct? If so, don't worry about the other slot, it'll get sorted when a new update comes out, or you flash a custom rom (if you choose to). If you followed Marcowe's flashing instructions from that other post you linked, then the same firmware is flashed on both slots. As for slot _a _b messages, could have been an out of date bootloader session depending on what you were doing and what, if anything, you flashed prior to trying to flash the firmware. A few different things could be going on there, so unless you can't boot I wouldn't trip on it at the moment.
Either way, if you can boot and use your phone I wouldn't worry about it, unless there is something specific you're trying to do. Alternatively, you can boot into bootloader mode and run the command 'fastboot getvar all' w/o quotes and get a little info about the state of your phone.
41rw4lk said:
So you're able to boot and use your phone, correct? If so, don't worry about the other slot, it'll get sorted when a new update comes out, or you flash a custom rom (if you choose to). If you followed Marcowe's flashing instructions from that other post you linked, then the same firmware is flashed on both slots. As for slot _a _b messages, could have been an out of date bootloader session depending on what you were doing and what, if anything, you flashed prior to trying to flash the firmware. A few different things could be going on there, so unless you can't boot I wouldn't trip on it at the moment.
Either way, if you can boot and use your phone I wouldn't worry about it, unless there is something specific you're trying to do. Alternatively, you can boot into bootloader mode and run the command 'fastboot getvar all' w/o quotes and get a little info about the state of your phone.
Click to expand...
Click to collapse
I'm able to boot and use my phone. I would like to use lineageos but my last two attempts where disasters.
I copied the last part of the info state which gives information about the slots since I'm not sure wat to delete besides of serial number.
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
b.bew said:
I'm able to boot and use my phone. I would like to use lineageos but my last two attempts where disasters.
I copied the last part of the info state which gives information about the slots since I'm not sure wat to delete besides of serial number.
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
Click to expand...
Click to collapse
You weren't on the correct build when you flashed Lineage OS. It explicitly says which one to be on in the OP.
http://download.invisiblek.org/nash/unbrick.zip -- this has instructions in it. We've done it hundreds of time, and I know it works.
Best of luck.
fastboot oem fb_mode_set
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash oem_a oem.img
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_b adspso.bin
fastboot flash logo_b logo.bin
fastboot flash boot_b boot.img
fastboot flash system_b system.img_sparsechunk.0
fastboot flash system_b system.img_sparsechunk.1
fastboot flash system_b system.img_sparsechunk.2
fastboot flash system_b system.img_sparsechunk.3
fastboot flash system_b system.img_sparsechunk.4
fastboot flash system_b system.img_sparsechunk.5
fastboot flash oem_b oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
Put this as your flashall.bat with your correct firmware
hello i have the same problem all time, first install qualcom drivers, then i uninstall motorola drivers and reboot, is very difficult to detect my phone in my pc, dont know why, but when detects it says unknown device, then i manually update the driver to Qualcomm HS-USB QDLoader 9008 (COM6), and its ok, run bat file blankflash, but it says waiting for device all time i did on my windows 7 pc and my windows 1 pc is the same, can anyone help me?
XxeAgLeAnGeLxX said:
hello i have the same problem all time, first install qualcom drivers, then i uninstall motorola drivers and reboot, is very difficult to detect my phone in my pc, dont know why, but when detects it says unknown device, then i manually update the driver to Qualcomm HS-USB QDLoader 9008 (COM6), and its ok, run bat file blankflash, but it says waiting for device all time i did on my windows 7 pc and my windows 1 pc is the same, can anyone help me?
Click to expand...
Click to collapse
You have to stop thread jumping and posting bits and pieces of your problem here and there, it makes it difficult to help you and it clutters the thread making it hard to reference for other users. Are we to back track through 3-4 different threads to see what the original problem is and what you've tried? Plus this thread is almost a year old and I'm sure isn't relevant to what your problem is.
41rw4lk said:
You have to stop thread jumping and posting bits and pieces of your problem here and there, it makes it difficult to help you and it clutters the thread making it hard to reference for other users. Are we to back track through 3-4 different threads to see what the original problem is and what you've tried? Plus this thread is almost a year old and I'm sure isn't relevant to what your problem is.
Click to expand...
Click to collapse
sorry
41rw4lk said:
Here are the signed diag drivers for win
Qualcomm Diag Drivers Signed
attached is the blankflash zip
Unplug your phone, install diag drivers, replug and wait for the everything to recognize and settle.
Unzip the blankflash to a folder and run the bat file, after it's done you should be back in bootloader where you can re-flash the latest firmware for your phone.
Use 2.0 usb ports from your motherboard, not a hub like the front of your pc; and use the oem cable.
If you have trouble getting this to work then unplug your phone from your pc, uninstall your moto drivers and the qualcomm drivers. Restart. Reininstall the drivers, reboot; then plug your phone and wait for the drivers to recognize, install, and settle. You may need to try to run the blankflash a couple of times to get it to take. You may need to try alternate usb ports, even 3.0+
This phone can be super picky about ports, cables, and even adb/fastboot versions. For most they won't have to worry about most of this, but for others this is the basic setup that works for the majority of users.
*Note - To get into blankflash/edl mode manually...
from bootloader prompt 'fastboot oem blankflash' w/o quotes
via adb command 'adb reboot edl' w/o quotes
Click to expand...
Click to collapse
I tried multiple methods to get into edl mode to do a blankflash , but I am not succesful. I tried the manual commands you mentioned but "fastboot oem blankflash" throws an error "command restricted".
adb reboot edl simply reboots multiple times and then boots normally to os, doesn't get detected as Qualcomm 9092 device.
I tried qcom method from bootloader which just normally boots the device to android but my laptop does detect it as qualcomm 9092 device. but then your blank-flash file doesn't work on it and stays on "waiting for device" .
Reason I want to blankflash is I accidentally flashed stock pie retail rom on my TMO 1789-04 device and now I dont have network/no sim error. Although baseband and imei are visible I dont have network or shows no sim error. I did manage to install TMO stock oreo but still no luck. As a last try I want to do blankflash and see if it helps.
can you please help me to get into edl mode or help blankflash my moto XT 1789-04?
latadswapnil said:
I tried multiple methods to get into edl mode to do a blankflash , but I am not succesful. I tried the manual commands you mentioned but "fastboot oem blankflash" throws an error "command restricted".
adb reboot edl simply reboots multiple times and then boots normally to os, doesn't get detected as Qualcomm 9092 device.
I tried qcom method from bootloader which just normally boots the device to android but my laptop does detect it as qualcomm 9092 device. but then your blank-flash file doesn't work on it and stays on "waiting for device" .
Reason I want to blankflash is I accidentally flashed stock pie retail rom on my TMO 1789-04 device and now I dont have network/no sim error. Although baseband and imei are visible I dont have network or shows no sim error. I did manage to install TMO stock oreo but still no luck. As a last try I want to do blankflash and see if it helps.
can you please help me to get into edl mode or help blankflash my moto XT 1789-04?
Click to expand...
Click to collapse
Blankflash won't solve that problem. Once you flash a pie modem you're stuck with it. The only solution is a pie modem which doesn't exist for TMO. No one has found a work around for this and with this phone being as old as it is now, it's unlikely that anything useful will be provided. Sorry. If you look around the forum you see dozens of warnings and examples of flashing the wrong firmware to your phone, most notably pie firmware. I think the only solution would be a pie modem that works for TMO too or a way to overwrite the modem nv value, both are pretty far out there.
41rw4lk said:
Blankflash won't solve that problem. Once you flash a pie modem you're stuck with it. The only solution is a pie modem which doesn't exist for TMO. No one has found a work around for this and with this phone being as old as it is now, it's unlikely that anything useful will be provided. Sorry. If you look around the forum you see dozens of warnings and examples of flashing the wrong firmware to your phone, most notably pie firmware. I think the only solution would be a pie modem that works for TMO too or a way to overwrite the modem nv value, both are pretty far out there.
Click to expand...
Click to collapse
is there a way we can erase flash memory and reinstall bootloader and everything from scratch?
Also, can you please help blankflashing the phone? any steps that I can take to be in edl mode?
41rw4lk said:
Blankflash won't solve that problem. Once you flash a pie modem you're stuck with it. The only solution is a pie modem which doesn't exist for TMO. No one has found a work around for this and with this phone being as old as it is now, it's unlikely that anything useful will be provided. Sorry. If you look around the forum you see dozens of warnings and examples of flashing the wrong firmware to your phone, most notably pie firmware. I think the only solution would be a pie modem that works for TMO too or a way to overwrite the modem nv value, both are pretty far out there.
Click to expand...
Click to collapse
So it seems that the problem is flashing a newer modem that is not compatible with Tmobile. Can you expand on where the info is written and why it cannot be reverted?
Sackgi said:
So it seems that the problem is flashing a newer modem that is not compatible with Tmobile. Can you expand on where the info is written and why it cannot be reverted?
Click to expand...
Click to collapse
The problem is TMO stopped with oreo, never made pie. So if you flashed a pie modem on TMO you're out of luck. When you flash a new modem most times it bumps your revision number up, so you can't roll back. You can typically only flash within the same revision or higher. Meaning you can't rollback to a lower revision modem.That info and warnings are all over this forum, and a lot of it is just anti-rollback.
Even on oreo whenever someone would flash the wrong oreo firmware, if it had a higher revision than what the proper firmware had, they would have to wait for an update that had an equal or higher revision modem to recover. Since TMO never and won't ever make pie firmware, going back is just not possible.
41rw4lk said:
The problem is TMO stopped with oreo, never made pie. So if you flashed a pie modem on TMO you're out of luck. When you flash a new modem most times it bumps your revision number up, so you can't roll back. You can typically only flash within the same revision or higher. Meaning you can't rollback to a lower revision modem.That info and warnings are all over this forum, and a lot of it is just anti-rollback.
Even on oreo whenever someone would flash the wrong oreo firmware, if it had a higher revision than what the proper firmware had, they would have to wait for an update that had an equal or higher revision modem to recover. Since TMO never and won't ever make pie firmware, going back is just not possible.
Click to expand...
Click to collapse
So what you are telling me is that there is no way to rollback once the revision number is higher. I question how is that no one has figured it out how to overcome this. Is it not possible to write a script to trick the system to install the old modem using the new modem file? In other words, if what needs to be verified is that the revision number matches, would it be possible to modify the new modem file with the old modem one?
Nothing is ever impossible, this site is a testament to that. Those revision numbers are most likely stored as nv values. How easy it is to edit those, idk. Can it be done without bricking your phone, idk. I do know that plenty of members have thrown everything they can think of at this problem to no avail, several of them just completely bricking their phone entirely.
What you're saying makes sense on paper, but you're talking about hijacking the boot process and injecting data long before android even enters the picture. That's qualcomm stuff, like blankflashing.
The reality is, it's an android 9 problem on a phone that's stuck on 8 while the rest have moved on to 10 and 11. Not a big market of players to delve into this problem, sorry. As for just editing a modem, not so easy. I've seen others trying in other forums. Not to mention what gets flagged and tripped trying to flash something like that. Once you edit an officially signed package, it's no longer officially signed. Sorry to be the bad news bear.
Basically I tried to install TWRP from https://forum.xda-developers.com/razer-phone/how-to/razer-phone-android-9-0-pie-cheryl-p-t3974325
Long story short (I can give details if it helps). I got into fastboot and tried to switch slots and reboot recovery. Instead it rebooted and the message that my bootloader is unlocked is gone, just bootlooping on the android logo. I can get to fast boot and it shows I'm not on either slot:
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4077
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:1
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:181801V00403118
(bootloader) product:cheryl
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) version:0.0
all:
Finished. Total time: 0.060s
I have no idea how to even just load TWRP and reflash the stock boot.img. (I'd like to preserve my phone data)
Any help would be greatly appreciated. Thank you very much.
If you can get into fastboot try to flask stock factory images and start over.
guillermohs9 said:
If you can get into fastboot try to flask stock factory images and start over.
Click to expand...
Click to collapse
I tried this:
fastboot flash boot twrp-3.2.2-0-cheryl.img && fastboot reboot
fastboot: error: Failed to identify current slot
Leprechaun7 said:
I tried this:
fastboot flash boot twrp-3.2.2-0-cheryl.img && fastboot reboot
fastboot: error: Failed to identify current slot
Click to expand...
Click to collapse
Download the stock image over at razer website. Unzipped the firmware and flash it using platform tool.
sinkoo1979 said:
Download the stock image over at razer website. Unzipped the firmware and flash it using platform tool.
Click to expand...
Click to collapse
Thanks for the help!! I ran flash_all.bat, some files wrote, some failed writes (I can post a long log, if that helps). I'm at least out of my latest dug hole, I can get to the bootloader screen. I'm still stuck at selecting a slot to do anything, still no slot selected. I guess that's the next step for me. I can't find anything about a phone with no slot selected. Any help from anyone would be appreciated.
Leprechaun7 said:
Thanks for the help!! I ran flash_all.bat, some files wrote, some failed writes (I can post a long log, if that helps). I'm at least out of my latest dug hole, I can get to the bootloader screen. I'm still stuck at selecting a slot to do anything, still no slot selected. I guess that's the next step for me. I can't find anything about a phone with no slot selected. Any help from anyone would be appreciated.
Click to expand...
Click to collapse
You should definitely post the log. I suppose you can attach it rather than flood the thread.
guillermohs9 said:
You should definitely post the log. I suppose you can attach it rather than flood the thread.
Click to expand...
Click to collapse
Here is the log (attached). Thanks!
Leprechaun7 said:
Here is the log (attached). Thanks!
Click to expand...
Click to collapse
Those are a lot of FAILED commands. I'm surprised it booted at all.
Did you issue the command
Code:
fastboot flashing unlock_critical
after
Code:
fastboot flashing unlock
?
guillermohs9 said:
Those are a lot of FAILED commands. I'm surprised it booted at all.
Did you issue the command
Code:
fastboot flashing unlock_critical
after
Code:
fastboot flashing unlock
?
Click to expand...
Click to collapse
No, I just ran flash_all.bat. I assume I should run those commands first then flash_all.bat?
My bootloader is already unlocked. Thanks for helping.
Leprechaun7 said:
Those are a lot of FAILED commands. I'm surprised it booted at all.
Did you issue the command after
No, I just ran flash_all.bat. I assume I should run those commands first then flash_all.bat?
My bootloader is already unlocked. Thanks for helping.
Click to expand...
Click to collapse
From the logs I'd say it's not fully unlocked. The 2 commands I quoted are necessary for that.
guillermohs9 said:
From the logs I'd say it's not fully unlocked. The 2 commands I quoted are necessary for that.
Click to expand...
Click to collapse
Good news: Thanks so much!, reunlocking the bootloader and then running flash_all.bat (2x, the first time didn't work right for some reason). It's back up and booting.
Bad news: I'm stuck at a "to start android enter your password" screen. I assume it's the pin to unlock the phone when you reboot. It doesn't seem to work. It might be a problem with the OS (https://www.reddit.com/r/razerphone/comments/bf7qes/restarted_phone_and_get_wrong_pin_when_prompted/)
I've tried all possible passwords I would have used, no luck. Now I've got limited attempts before the device wipes. Of course I think everything is wiped since I re-unlocked the bootloader and flash_all.bat
Leprechaun7 said:
Good news: Thanks so much!, reunlocking the bootloader and then running flash_all.bat (2x, the first time didn't work right for some reason). It's back up and booting.
Bad news: I'm stuck at a "to start android enter your password" screen. I assume it's the pin to unlock the phone when you reboot. It doesn't seem to work. It might be a problem with the OS (https://www.reddit.com/r/razerphone...arted_phone_and_get_wrong_pin_when_prompted/)
I've tried all possible passwords I would have used, no luck. Now I've got limited attempts before the device wipes. Of course I think everything is wiped since I re-unlocked the bootloader and flash_all.bat
Click to expand...
Click to collapse
Mm that doesn't sound right. The data partition should be formatted. There is a fastboot command to format user data. I don't know it by heart but it's on this forum.
guillermohs9 said:
Mm that doesn't sound right. The data partition should be formatted. There is a fastboot command to format user data. I don't know it by heart but it's on this forum.
Click to expand...
Click to collapse
um...cough..cough... I may have deleted the "%fastboot_cmd% erase userdata" command in a feeble attempt to save my data...
I'm guessing I should just pull the trigger on deleting my user data.
Leprechaun7 said:
um...cough..cough... I may have deleted the "%fastboot_cmd% erase userdata" command in a feeble attempt to save my data...
I'm guessing I should just pull the trigger on deleting my user data.
Click to expand...
Click to collapse
That may be it. Always back up first. Anyway, it may be worth the shot to try enter a PIN. Did you use a pattern or pin? You can translate a pattern to a PIN, it worked for me on recoveries on other devices...
When it asks for decryption by PIN and you've been using a pattern, I was able to "translate" pattern to pin using the following matrix:
1 2 3
4 5 6
7 8 9
So a diagonal line from bottom left to top right would translate to a pin "753" unless 5 is already used by another line in which case you'd go directly from 7 to 3.
guillermohs9 said:
That may be it. Always back up first. Anyway, it may be worth the shot to try enter a PIN. Did you use a pattern or pin? You can translate a pattern to a PIN, it worked for me on recoveries on other devices...
When it asks for decryption by PIN and you've been using a pattern, I was able to "translate" pattern to pin using the following matrix:
1 2 3
4 5 6
7 8 9
So a diagonal line from bottom left to top right would translate to a pin "753" unless 5 is already used by another line in which case you'd go directly from 7 to 3.
Click to expand...
Click to collapse
Thanks so much. I have a pin and have tried it many times, no luck. I actually bricked my phone in the first place trying to get TWRP and root (for Titanium Backup). I'm backup crazy. I might try to get TWRP working again and backup before I mess with the password anymore.
Leprechaun7 said:
Thanks so much. I have a pin and have tried it many times, no luck. I actually bricked my phone in the first place trying to get TWRP and root (for Titanium Backup). I'm backup crazy. I might try to get TWRP working again and backup before I mess with the password anymore.
Click to expand...
Click to collapse
Well, good luck. Last resort, flash_all without modifications and start from there.
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
I also had issues booting the boot.img. I took the risk of flashing it and it worked.
Airwolf79 said:
I also had issues booting the boot.img. I took the risk of flashing it and it worked.
Click to expand...
Click to collapse
Using what command? Just fastboot flash boot rootedimage.img?
Kind of reticent to do that cos there's no linux MSM tool
djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
Also having that issue on the NA varient. So f-ing annoying.
djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
Go into recovery and factory reset. That happen to me once when flashing in fastboot from bootloader.
djsubterrain said:
Using what command? Just fastboot flash boot rootedimage.img?
Kind of reticent to do that cos there's no linux MSM tool
Click to expand...
Click to collapse
Yeah, I know. I'm on a Mac, so, same boat. Yes, I flashed with "fastboot flash boot boot.img", specifically renaming the patched img to boot.img. This used to be the standard way of doing it, although I realize it's safer to boot the img.
My mistake, you are trying to get root, correct?
TheGhost1951 said:
My mistake, you are trying to get root, correct?
Click to expand...
Click to collapse
Try fastboot enhanced maybe? Nope, sorry, that is for windows only I believe.
TheGhost1951 said:
Try fastboot enhanced maybe? Nope, sorry, that is for windows only I believe.
Click to expand...
Click to collapse
Being on a MAC, I really don't have a clue bud..
Actually found the linux version of MSM tool (It's really just a Qualcomm tool) so I might try flashing directly, will need to grab the appropriate MSM image just in case.
Made a guide here for anyone else in Linux but I haven't tested yet
djsubterrain said:
Actually found the linux version of MSM tool (It's really just a Qualcomm tool) so I might try flashing directly, will need to grab the appropriate MSM image just in case.
Made a guide here for anyone else in Linux but I haven't tested yet
Click to expand...
Click to collapse
Did root work?
If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.
mustangtim49 said:
If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.
Click to expand...
Click to collapse
You did actually read my post, right?
mustangtim49 said:
If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.
Click to expand...
Click to collapse
I'm still getting a bootloop
LuckyTheCoder said:
I'm still getting a bootloop
Click to expand...
Click to collapse
Of course, once it goes wrong, it stays wrong. Did you use the fastboot flash boot command? Either way, msn tool and start from scratch.
mustangtim49 said:
Of course, once it goes wrong, it stays wrong. Did you use the fastboot flash boot command? Either way, msn tool and start from scratch.
Click to expand...
Click to collapse
I did, yes. MSN tool? Like fully reset?
LuckyTheCoder said:
I did, yes. MSN tool? Like fully reset?
Click to expand...
Click to collapse
It will!
TheGhost1951 said:
It will!
Click to expand...
Click to collapse
:/
LuckyTheCoder said:
:/
Click to expand...
Click to collapse
I can't count the number of times I have started from scratch just from trying different things and crashing!
TheGhost1951 said:
I can't count the number of times I have started from scratch just from trying different things and crashing!
Click to expand...
Click to collapse
How in the world am I supposed to back it up?