Develop Bugs

Soft Bricked (Locked / S-Off / Recovery broken?)

Hey guys!
I really hope anyone can help me out with this.
So, today I thought "Why not upgrading to 5.1 and unbranding it?". I followed a tutorial on a german android forum to unbrand it.
But I was unlocked and rooted so I had to return the changes in order to update it. I changed the CID to HTC__102, made it S-ON again and even locked it, then tried flashing a non branded european RUU via my microSD card, which somehow failed and I ended up having a bootloop. So I upgraded my firmware aswell to 2.10.401.1 but now the recovery is not even working i only get a red triangle, which might be a common problem with 5.1 on our M9, as I read later on.
Download mode, fastboot etc is working fine
edit: stock recovery is working as well
Can anybody help me get my M9 going again?
I thought about try another flash with a unlocked ROM via microSD card but I'm not sure which one as the one I mentioned failed.
Here are some more details about my current situation:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: XXXXX
(bootloader) version-main: 2.10.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__102
Click to expand...
Click to collapse
edit: In another thread I read how to boot into the stock recovery and it's working. But still not booting

easy...soff again unlock bootloader, then download dev 2.8 zip rom, place it on sdcard and enter download mode, press volume up to start flash and you will have a brand new developer edition 2.8 (you will loose all info) you must have mid 0JPA11000 cid BS_US001., read a topic on this on xda how to change att to developer...

LLegion said:
easy...soff again unlock bootloader, then download dev 2.8 zip rom, place it on sdcard and enter download mode, press volume up to start flash and you will have a brand new developer edition 2.8 (you will loose all info) you must have mid 0JPA11000 cid BS_US001., read a topic on this on xda how to change att to developer...
Click to expand...
Click to collapse
Thanks, but how do i set it to S-Off again? I've used Sunshine's S-Off app before. But I'm not able to boot anymore.

At first never post your IMEI number online.
If you are not S-OFFed any more you cannot flash anything to recovery partition as long as you are not at least htc_dev unlocked.
The only thing that could help you now is to flash a custom recovery in boot partition and then to try to fix the recovery partition from it.
In order to do this you should unlock your bootloader again by using Unlock_code.bin
Code:
fastboot flash unlocktoken Unlock_code.bin
or if it has "relocked" status you could possibly use the command
Code:
fastboot oem unlock
then you should reboot in download mode again
Code:
fastboot oem rebootRUU
and flash the boot partition with a custom recovery
Code:
fastboot flash boot recovery.img
Now logically you should be able to boot into recovery (probably from bootloader) or by using the command
Code:
fastboot reboot recovery
If for some reason you cannot flash a custom recovery on boot partition you could try to extract the system.img from (probably any German RUU [HTC-GER] as long as you have HTC__102 cid number) and flash it with fastboot command
Code:
fastboot flash system system.img
By this way you could probably fix your breaked system partition
You should also erase the /cache and /data partitions so you could avoid the bootloop (even without to flash an original system.img)

Gatosbil said:
At first never post your IMEI number online.
Click to expand...
Click to collapse
Thanks. I've corrected it.
Gatosbil said:
In order to do this you should unlock your bootloader again by using Unlock_code.bin
Code:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
I can't generate a new one because OEM unlock is turned off :\
Same goes with reflashing the previous Unlock_code.bin
> htc_fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... (bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY
Execution time is 20(ms)
Click to expand...
Click to collapse
Gatosbil said:
or if it has "relocked" status you could possibly use the command
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Indeed, it is "relocked". But when I'm using the command I'll get "[ERR] Command error !!!"
Any suggestions for that? I'll try the other steps once I solved this.
Edit: I can't use ADB because I'm using the stock recovery atm.
Also there is no RUU for 2.10.401.1 yet so I guess I have to sent it in?
Btw: I'm already hating the new 5.1 oem lock feature.

This was your mistake:
Army92 said:
made it S-ON again
Click to expand...
Click to collapse
I don't care what anyone tells you, don't ever, ever go back to s-on once you are s-off. It's totally unnecessary and a potential risk, as you've discovered. By doing it, you've locked your phone into a bad configuration. You can't unlock unless you can boot to the OS and check "allow OEM unlocking." You can't flash a recovery because you're locked. You can't run a RUU because none exists for your CID. You're going to have to return it and hope HTC will fix it.

iElvis said:
This was your mistake:
I don't care what anyone tells you, don't ever, ever go back to s-on once you are s-off. It's totally unnecessary and a potential risk, as you've discovered. By doing it, you've locked your phone into a bad configuration. You can't unlock unless you can boot to the OS and check "allow OEM unlocking." You can't flash a recovery because you're locked. You can't run a RUU because none exists for your CID. You're going to have to return it and hope HTC will fix it.
Click to expand...
Click to collapse
That's what I thought. Thanks, I'll contact HTC and see if they can fix it.
Edit: I'm sending it to HTC today. Just a warning to all users out there: Do not lock your bootloader and uncheck "Enable OEM unlocking" because you are not able to do anything about it when your devices isn't working properly!

Army92 said:
Just a warning to all users out there: Do not lock your bootloader and uncheck "Enable OEM unlocking" because you are not able to do anything about it when your devices isn't working properly!
Click to expand...
Click to collapse
If it's any consolation, you're far from the first person to get tripped up by this new feature. Lots of Nexus 6s got bricked when it first rolled out because of situations just like yours.

iElvis said:
If it's any consolation, you're far from the first person to get tripped up by this new feature. Lots of Nexus 6s got bricked when it first rolled out because of situations just like yours.
Click to expand...
Click to collapse
Yeah I've read that too. Thanks for your condolence. Will report again when I get my M9 back in 2 weeks (I hope).

Update: So today I got my lovely One M9 back it lasted 10 days until I got it back in my hands.
They changed the mainboard and haven't charged anything. My phone status went back to official, S-Off and locked bootloader.

Army92 said:
Update: So today I got my lovely One M9 back it lasted 10 days until I got it back in my hands.
They changed the mainboard and haven't charged anything. My phone status went back to official, S-Off and locked bootloader.
Click to expand...
Click to collapse
They sent you an s-off phone?

iElvis said:
They sent you an s-off phone?
Click to expand...
Click to collapse
Oh, sorry my bad. I meant S-On of course

soft breaked htc one m9 s-off please help
hy
rom: cm13 himaul
device:htc one m9 unlocked/developer edition
statue:s-off
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) version-main: 1.32.617.30
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BS_US001
ok i have rooted cm13 20160603 nighties by supersu 2.74 beta with xposed 85 arm 64
yesterday i was disabling my boot image when it restarted by itself and never boot in to system again so i went to my custom recovery twrp latest version to reflash the whole cm13 again it didnt work then i wiped the whole internal storage and reflashed the cm13 and it said fail cant flash cm thats when my battery died so i charged it after 3 hours i came back went to bootloader menu then clicked on custom recovery it didnt even start so i plugged it to usb used fastboot to flash custom frimware from here (used the no wipe zip)
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
it flashed but custom frimware didnt fix it so i used the wipe zip version with viper one latest system image to flash it failed so now i am stock in bootloader (download mode works) without access of recovery and no system.img or recovery and i cant find a way to fix it
websites i visited just in case
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
any help would be appreciated
:crying::crying::crying:

Please Anyone im Soft-bricked and cant RUU

Like the title says I'm soft bricked and no ruu will work beacuse my boot loader is unlocked and "fastboot oem lock" doesn't work. I'm S-On and I have access to the bootloader, download mode, and twrp, but twrp wont mount any partitions and shows internal storage as 0mb. P.S. this is a Tmobile HTC One M9. Please anyone I need help and I'm leaving for a trip tomorrow. Thanks!

Heres what i get from getvar all
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>htc_fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:REDACTED
all:
Execution time is 135(ms)
(bootloader) kernel: lk
(bootloader) product: htc_himaul
(bootloader) version: 1.0
(bootloader) imei: REDACTED
(bootloader) version-main: 3.39.531.7
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA12000
(bootloader) cid: T-MOB010
all:
finished. total time: 0.067s

You tried sideloading a rom via TWRP?
Sent from my HTC 10 using XDA Labs

squ89r97 said:
You tried sideloading a rom via TWRP?
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ill try that and get back to you. one minute.

Fails everytime I try to sideload this is what I get.
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload stock-deodex.zip
loading: 'stock-deodex.zip'
* cannot read 'stock-deodex.zip' *
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload viperone.zip
loading: 'viperone.zip'
* cannot read 'viperone.zip' *
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload firmware.zip
loading: 'firmware.zip'
* cannot read 'firmware.zip' *

Try renaming the file in windows without the .zip sounds random I know, but I experienced this a long long time ago. So if you have a file called firmware.zip rename it firmware. But still use firmware.zip in your adb command.
Sent from my HTC 10 using XDA Labs

squ89r97 said:
Try renaming the file in windows without the .zip sounds random I know, but I experienced this a long long time ago. So if you have a file called firmware.zip rename it firmware. But still use firmware.zip in your adb command.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
ok Ill try that.

I renamed the file. I also tried renaming the file in the command. It fails the same way as before.
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload stock-deodex.zip
loading: 'stock-deodex.zip'
* cannot read 'stock-deodex.zip' *
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload stock-deodex
loading: 'stock-deodex'
* cannot read 'stock-deodex' *

narms72 said:
I renamed the file. I also tried renaming the file in the command. It fails the same way as before.
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload stock-deodex.zip
loading: 'stock-deodex.zip'
* cannot read 'stock-deodex.zip' *
C:\Users\Noah\Desktop\Minimal ADB and Fastboot>adb sideload stock-deodex
loading: 'stock-deodex'
* cannot read 'stock-deodex' *
Click to expand...
Click to collapse
Are you running cmd with administration rights? You can also type adb sideload command, then drag and drop your firmware into the cmd window.
Not sure where your firmware is saved, but it should be in the same folder as your adb, in your case. C:\Users\Noah\Desktop\Minimal ADB and Fastboot
Sent from my HTC 10 using XDA Labs

squ89r97 said:
Are you running cmd with administration rights? You can also type adb sideload command, then drag and drop your firmware into the cmd window.
Not sure where your firmware is saved, but it should be in the same folder as your adb, in your case. C:\Users\Noah\Desktop\Minimal ADB and Fastboot
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Unfortunately I get the exact same response.

I think the reason ruus fail is because my bootloader is unlocked, but whenever I try fastboot oem lock it doesnt work.

Rather than troubleshoot what you're doing, your best bet is to access Flippy498’s spreadsheet and read through his instructions in the RUU section. He's got a simple walkthrough that should set you on the right path.

computerslayer said:
Rather than troubleshoot what you're doing, your best bet is to access Flippy498’s spreadsheet and read through his instructions in the RUU section. He's got a simple walkthrough that should set you on the right path.
Click to expand...
Click to collapse
Ive read it. My bootloader wont lock though so ruus fail.

narms72 said:
Ive read it. My bootloader wont lock though so ruus fail.
Click to expand...
Click to collapse
I'm certain bootloader status doesn't matter to RUUs. What method of applying the RUU have you attempted (fastboot, sd card or executable)?
Is your phone a US T-Mobile variant? Besides the RUU in zip form, there is a Windows executable RUU (you'll need to install HTC Sync Manager first) available.
Edit: Well I was certain....ly wrong! Thank you Flippy498 for the correction (see post below)

computerslayer said:
I'm certain bootloader status doesn't matter to RUUs.
Click to expand...
Click to collapse
It does matter if you use fastboot or an *.exe (which actually does nothing more than using fastboot for you ). Both require a locked or relocked bootloader if you're S-ON. On the other hand for S-OFF users or if you use the SD card method the bootloader status doesn't matter.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
It does matter if you use fastboot or an *.exe (which actually does nothing more than using fastboot for you ). Both require a locked or relocked bootloader if you're S-ON. On the other hand for S-OFF users or if you use the SD card method the bootloader status doesn't matter.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I have the developer edition of the phone (still S-ON) and the RUU executable install even though it has an unlocked bootloader - I concluded that RUUs ignored bootloader status. Thank you for the correction.

The developer edition is (as far as I know) an exception due to its factory unlocked bootloader.
Sent from my HTC One S using XDA Labs

Flippy498 said:
The developer edition is (as far as I know) an exception due to its factory unlocked bootloader.
Click to expand...
Click to collapse
I'm guessing that's the reason the bootloader cannot be locked in this instance? Another bit of knowledge in the memory banks.
Sent from my HTC 10 using XDA Labs

As far as I know the bootloader can always be relocked. That's the reason for all the issues people have if they don't enable oem unlock and relock although their system is not completely stock (e.g. TWRP is still installed). The phone's security checks will prevent the phone from booting because it notices that the system is manipulated. If you don't have a compatible RUU in that situation or if your phone isn't S-OFF you're unable to solve the problem on your own. The only solutions are a java card/xtc clip or llabtoofers RUU service.
However you can't re-S-ON always due to some other security checks.
It might be helpful if the OP could post the error that appears when he tries to relock the bootloader.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
As far as I know the bootloader can always be relocked. That's the reason for all the issues people have if they don't enable oem unlock and relock although their system is not completely stock (e.g. TWRP is still installed). The phone's security checks will prevent the phone from booting because it notices that the system is manipulated. If you don't have a compatible RUU in that situation or if your phone isn't S-OFF you're unable to solve the problem on your own. The only solutions are a java card/xtc clip or llabtoofers RUU service.
However you can't re-S-ON always due to some other security checks.
It might be helpful if the OP could post the error that appears when he tries to relock the bootloader.
Click to expand...
Click to collapse
@Flippy498 the font of knowledge, thanks for all you expertise.
I know this sounds like sarcasm, but it's truly not.
Sent from my HTC 10 using XDA Labs

[FIXED] rip lg g4?

READ THE COMMENTS OR POST AND I MIGHT BE ABLE TO HELP
So, i tried to use this method: https://forum.xda-developers.com/g4/general/managed-to-relock-bootloader-t3660282 to relock my bootloader. Had the rom 29a installed, so I tried to use the command line. The lock was successful. When I did the reboot a red message shows up: "Your device is corrupt. It cannot be trusted and may not work properly". When I try to boot into recovery or download mode this message shows up anyway. I guess there is nothing I can do right?
---------------------------------------------------------------------------------------------------------------------------------------
The problem was:
Re-locked bootloader
No download mode access
No recovery access
No system
OEM toggled off
Solutions tried:
SDCard method
fastboot erase/format/flash
Since the bootloader got relocked none of the options above worked. However, I found a solution, thanks to @steadfasterX using the Qdloader 9008 to unbrick the phone. This was the only method that worked.

Anyone knows a method to fix the IMEI using fastboot, or a method to re-unlock the bootloader without using official methods?

If you have a backup of your misc partition while your boot loader was unlocked, then you can flash it with the patched LG UP, and that should should unlock it again.
-- Brian

runningnak3d said:
If you have a backup of your misc partition while your boot loader was unlocked, then you can flash it with the patched LG UP, and that should should unlock it again.
-- Brian
Click to expand...
Click to collapse
How can I do that? Recovery and Download mode not working

I missed the part about download mode not working. Just curious, what does the device show up as in Windows?
-- Brian

runningnak3d said:
I missed the part about download mode not working. Just curious, what does the device show up as in Windows?
-- Brian
Click to expand...
Click to collapse
It doesnt shows up. It bootloops the red message, only fastboot is working. Tried to flash the unlock.bin but this occurs:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.037s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.059s

Try this method to live your download mode - https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853

kingtm said:
Try this method to live your download mode - https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853
Click to expand...
Click to collapse
SD necessary? 8GB?

The method above works. Writes a workable rom to the device using the SD card. I used a 8gb and it worked fine for me.

https://forum.xda-developers.com/showpost.php?p=73506152&postcount=20

kingtm said:
Try this method to live your download mode - https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853
Click to expand...
Click to collapse
Not working aswell

pedrogcsb said:
Anyone knows a method to fix the IMEI using fastboot, or a method to re-unlock the bootloader without using official methods?
Click to expand...
Click to collapse
Do you have made a full backup with the dl backup method as I wrote everywhere?
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Do you have made a full backup with the dl backup method as I wrote everywhere?
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes. Nothing is working since I can't access either dl mode or recovery mode. My last hope is to discover a way to toggle on oem using fastboot

pedrogcsb said:
Yes. Nothing is working since I can't access either dl mode or recovery mode. My last hope is to discover a way to toggle on oem using fastboot
Click to expand...
Click to collapse
Perfect then we can try to flash the efs back in fastboot. I dunno if it will work but as those are not modified they should be accepted.
When you took the backup on what exact ROM version have you been?
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Perfect then we can try to flash the efs back in fastboot. I dunno if it will work but as those are not modified they should be accepted.
When you took the backup on what exact ROM version have you been?
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
6.0, but I can't flash or erase anything via fastboot since the bootloader is now locked and I can't reunlock since the OEM is not activated.

pedrogcsb said:
6.0, but I can't flash or erase anything via fastboot since the bootloader is now locked and I can't reunlock since the OEM is not activated.
Click to expand...
Click to collapse
What device model do you have?
What have you tried to *flash* which partitions?
What have you tried to *erase* which partitions?
and what do the following commands return:
fastboot oem device-id
fastboot getvar all
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
What device model do you have?
What have you tried to *flash* which partitions?
What have you tried to *erase* which partitions?
and what do the following commands return:
fastboot oem device-id
fastboot getvar all
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
H815. Tried to flash or erase every single one.
(bootloader) ----------------------------------
(bootloader) Device-ID
(bootloader) 89B299BCE263958E7349073FD257505E
(bootloader) 5E4CD9C0917AB0AD5977F7DB0D2A265C
(bootloader) ----------------------------------
OKAY [ 0.069s]
finished. total time: 0.069s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x4d000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5cc000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x102c00000
(bootloader) serialno:LGH815c8b1a80e
(bootloader) kernel:lk
(bootloader) product:MSM8992_P1_GLOBAL_COM
(bootloader) unlocked:no
all:
finished. total time: 0.196s

pedrogcsb said:
H815. Tried to flash or erase every single one
Click to expand...
Click to collapse
fsg? modemst1 and modemst2?
what about the other questions I asked?
.

steadfasterX said:
fsg? modemst1 and modemst2?
what about the other questions I asked?
.
Click to expand...
Click to collapse
I replied after that in the same post sir

pedrogcsb said:
I replied after that in the same post sir
Click to expand...
Click to collapse
good
did you tried this?
fastboot erase modemst1
fastboot erase modemst2
and
fastboot flash fsg fsg.image
?

Unable to unlock bootloader

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>

Help, Bricked, stuck at android logo boot loop, trying to install TWRP/Magisk

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.