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:

Moto Z play stuck on bootloader

Hello,
at first - I would like to apologize to moderators, if this topic is out of category, I tried to find some troubleshooting category but didnt. So please if Im blind, move it. At second, sorry for my english, Im not native speaker.
Model XT1635-02 Reteu dual sim 32GB
Trouble description:
I unlock bootloader, flash twrp and tested some custom rom. After that, I want to go back to stock rom. I flashed the stock rom, but forget to do NOT ota update. Ok - brick the phone. After few hours of searching, I relive a phone with right flashblank and had an access to bootloader again. But tried to flash a stock rom again, and that was a main fail again. So - I have a stock rom in phone, but doesnt work. And (from my point of view) I have a nonworking stock rom with locked USB debuging mode, I cannot unlock it, becasuse it doesnt work and I cannot flash twrp, because USB debug is locked. If I try to boot recovery twrp, phone restart but no twrp popup. vol up + pwr do nothing. So Im catch in some crappy circle at this moment. I tried fastboot erase system, but result is:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.006s
Click to expand...
Click to collapse
So question is: Is there some command in fastboot for deleting everything? Or other way how to delete a rom from fastboot? (idea is delete rom to skip locked USB debug)
Other thing to do, to test? Some tips, helps?
Thank you so much everyone who spend a time try to help me...

You can install twrp again? If you can, just do a advanced wipe. Because MZP Bootloader doens't allow to delete any part of system.

Unlocking bootloader for LEX727

Hi All.
I just bought the leeco pro 3 and want to unlock the bootloader. I followed the steps outlined in "X727 (US Model) Persistent bootloader unlock from 5.8.019s". I turned on USB debugging, permanently added USB device, and turned on the "allow oem unlocking option". Then, i rebooted to fast boot and tried the following commands and received an error.
Code:
:~$[B] fastboot oem device-info[/B]
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
:~$ [B]fastboot oem unlock-go[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.008s
:~$ [B]fastboot oem unlock[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.004s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.007s
My phone came with 5.8.020S (I think) and I tried the above steps with that version. Then i updated to 5.8.021S and tried again and received the same issue. I checked for more updates but none were found.
I am sure this issue has been solved somewhere but I just want to make sure I do not brick this device. Please help.

Developer Options ---> usb debug ---> open ..
Developer Options ---> Oem unlock ---> open ..
Have you enabled them?

lazye53 said:
Developer Options ---> usb debug ---> open ..
Developer Options ---> Oem unlock ---> open ..
Have you enabled them?
Click to expand...
Click to collapse
Thanks for the reply.. Yes. Both of those options are on. I have tried multiple times to turn them off and on and redo the unlock at fast boot, but i get the same error

sagarc88 said:
Hi All.
I just bought the leeco pro 3 and want to unlock the bootloader. I followed the steps outlined in "X727 (US Model) Persistent bootloader unlock from 5.8.019s". I turned on USB debugging, permanently added USB device, and turned on the "allow oem unlocking option". Then, i rebooted to fast boot and tried the following commands and received an error.
Code:
:~$[B] fastboot oem device-info[/B]
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
:~$ [B]fastboot oem unlock-go[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.008s
:~$ [B]fastboot oem unlock[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.004s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.007s
My phone came with 5.8.020S (I think) and I tried the above steps with that version. Then i updated to 5.8.021S and tried again and received the same issue. I checked for more updates but none were found.
I am sure this issue has been solved somewhere but I just want to make sure I do not brick this device. Please help.
Click to expand...
Click to collapse
For 5.8.021S, go to page 26 ....

sagarc88 said:
Thanks for the reply.. Yes. Both of those options are on. I have tried multiple times to turn them off and on and redo the unlock at fast boot, but i get the same error
Click to expand...
Click to collapse
I had this issue also this I solved it.
Undo the OEM allow to unlock reboot then enable OEM to unlock bootloader.
Still had the problem.
I ended up flash the bootloader then then ran the bootloader unlock commander and it worked.
Sent from my LEX727 using xda premium

mchlbenner said:
I had this issue also this I solved it.
Undo the OEM allow to unlock reboot then enable OEM to unlock bootloader.
Still had the problem.
I ended up flash the bootloader then then ran the bootloader unlock commander and it worked.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
You need to flash 2 files via adb first, then run the unlock command.
I did it successfully for 021s
Sent from my LEX727 using Tapatalk

kukuteku said:
For 5.8.021S, go to page 26 ....
Click to expand...
Click to collapse
This worked perfectly!! Thank you very much.

Flashing Critical Locked
I'm just a dabbler in this stuff, but I think I understand everything required to get LineageOS on my LEX727. The problem is, in the process of learning, I think I locked the ability to flash aboot, and now I can't get the twrp recovery onto my phone. Does anyone have any ideas or know what to do? If I can do anything from here?
Thanks for any help!

MAHawbs said:
I'm just a dabbler in this stuff, but I think I understand everything required to get LineageOS on my LEX727. The problem is, in the process of learning, I think I locked the ability to flash aboot, and now I can't get the twrp recovery onto my phone. Does anyone have any ideas or know what to do? If I can do anything from here?
Thanks for any help!
Click to expand...
Click to collapse
What did locked ability flash abootd it d relock bootloader.
What did you ?
Sent from my SM-A730F using xda premium

Question [SOLVED] - Bootloop with completely new OPO9pro after oem unlock

Hello,
just received the phone (EU), updated latest online udpate. (no Google account etc added, just fast setup)
Enabled developer options, OEM unlocking and USB debugging.
After update, 1*reboot.
then another reboot to bootloader, and executed "fastboot oem unlock".
Phone rebooted to recovery. Wiped data, another reboot, now i have only the Red & white dots.....
Any suggestions/hints?
Thanks
Edit:
Entered fastboot mode, did a fastboot oem lock -> same, Red and white dots.

When I unlocked the bootloader I had to wait a much longer time than normal (about 8 minutes) for the dot splash screen to transition to the setup screen and for the phone to boot up fully.
I apologize if this is sort of a "duh I already did that" suggestion. Hope it can help.

Unfortunately not, i waited around 1 hour.
But thanks 4 your comment!

Booting the stock boot.img posted here on XDA -> same result.
Tried to swap the boot slot -> FAILED (remote: Slot Change is not allowed in merging state)
(bootloader) has-slot:system:no
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:3d12cbee
(bootloader) product:lahaina
(bootloader) snapshot-update-status:merging
(bootloader) is-userspace:no
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
all:
finished. total time: 0.605s

Waiting msm

empty.cad said:
Waiting msm
Click to expand...
Click to collapse
Regarding MSM: if i understood correctly, this is something OPO does not provide, but is "extracted" by some guys here? (key extraction etc??)
So this may take some time.... Probably RTM (cancel order) next week.

yeah once I unlocked BL in fastboot and rebooted, the subsequent next boot took close to 10 minutes, but did boot into a wiped device after

Regarding the error "FAILED (remote: Slot Change is not allowed in merging state)" when swapping the slot, i found tha a
snapshot-update merge — Completes a merge operation, booting to recovery/fastbootd if necessary. This command is valid only if snapshot-update-status is merging, and is only supported in fastbootd.
May help.
But they talk also about
If merging or snapshotted, issue snapshot-update cancel.
But i prefer to ask here before executing, as i have no idea what this does

Well, i could not wait.
After doing a fastboot snapshot-update merge
i rebooted. Same issue.
Booted stock kernel -> issue
Swapped active slot -> Qualcom crash dump
Rebooted to fastboot, oem lock -> phone boots again.
Rebooted twice normally to confirm
Again fastboot oem unlock
Boot fine now. No idea what happened on first oem unlock.

I haven't tried this yet, but I found this link which seems to give a different fastboot command to use. Not sure how much difference it'll make for other users but thought I'd link to it just in case it helps others. I'll probably try it either tomorrow or over the weekend.

I did not use the fastboot oem unlock but the fastboot flashing unlock on the OP9P Global and worked the first time.

Can not unlock my bootloader anymore after flashed stock firmware

I've unlock my bootloader of my XT1789-03(Sprint) with Android 7. Then I flashed stock firmware of Android 8. Now the bootloader is locaked, and I cannot flash any firmware anymore.
The Motorola webside said "Your device does not qualify for bootloader unlocking.". The old unlock key does not work.
When I try to unlock with my old UNIQUE_KEY, I got the following prompt.
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.011s]
finished. total time: 0.013s
Click to expand...
Click to collapse
How can I unlock the bootloader?
Thanks!

Unfortunately, this is not possible

Thanks for your quick answer.
Guess I'm stuck with this firmware.