Database Develop

[Q] S-OFF & Locked ?

Hi Everyone,
I got my second One today, first one had microphone issues.
I asked my cousin from UK to send me a new one, I got it today and I want to use a custom rom.
But when I opened the bootloader I saw something strange, it was s-off.
My build number is 1.29.206.11 (O2 UK).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I want to install this firmware 1.29.401.12 and a custom recovery after it.
Can I install this firmware directly?
Do I have to unlock my bootloader from htcdev to flash a custom recovery? (Its written locked)
It would be great if someone can tell me what should I do.
P.S.
-fastboot oem unlock doesnt work
-fastboot flash recovery recovery.img doesnt work
Thanks

You have to register with htcdev and unlock your phone that way when you get the unlock_code.bin and AFAIK there is no way to unlock the bootloader without going through htcdev.
Until you do this you won't be able to flash any custom recoveries etc.

mehmetolgungun said:
Hi Everyone,
I got my second One today, first one had microphone issues.
I asked my cousin from UK to send me a new one, I got it today and I want to use a custom rom.
But when I opened the bootloader I saw something strange, it was s-off.
My build number is 1.29.206.11 (O2 UK).
I want to install this firmware 1.29.401.12 and a custom recovery after it.
Can I install this firmware directly?
Do I have to unlock my bootloader from htcdev to flash a custom recovery? (Its written locked)
It would be great if someone can tell me what should I do.
P.S.
-fastboot oem unlock doesnt work
-fastboot flash recovery recovery.img doesnt work
Thanks
Click to expand...
Click to collapse
You have to unlock with htcdev site.
After you can do all what you want

uhhh...he can flash the firmware directly through
Code:
fastboot oem rebootRUU
fastboot flash zip FIRMWARE.zip
fastboot reboot

Indirect said:
uhhh...he can flash the firmware directly through
Code:
fastboot oem rebootRUU
fastboot flash zip FIRMWARE.zip
fastboot reboot
Click to expand...
Click to collapse
Yes, sure
But:
mehmetolgungun said:
I want to install this firmware 1.29.401.12 and a custom recovery after it.
Click to expand...
Click to collapse
For the custom recovery he have to unlock the bootloader

false. He's s-off so he can add the recovery.img to the flashable firmware zip and then he has both.

Yep, just use the fastboot command
fastboot flash recovery recovery.img
where recovery.img is the name of CWM/TWRP. Nice and easy!
EDIT: Re-read the OP, strange that it doesn't work as it should do. What error do you get?

EddyOS said:
Yep, just use the fastboot command
fastboot flash recovery recovery.img
where recovery.img is the name of CWM/TWRP. Nice and easy!
EDIT: Re-read the OP, strange that it doesn't work as it should do. What error do you get?
Click to expand...
Click to collapse
I cant tell the error now, because I already unlocked my bootloader from htcdev.
As the poeople said that I cant do it, I made it from htcdev

I wouldn't have done anything until people had a chance to properly answer you...oh well

EddyOS said:
I wouldn't have done anything until people had a chance to properly answer you...oh well
Click to expand...
Click to collapse
I had a simil case with my evo 3D.
I had it in s-off and locked after the reparation in warranty by htc, i tried to flash a recovery but nothing.
So i unlocked my bootloader with htcdev and all worked fine...

But that defeats the point of S-OFF...with S-OFF you should have free access to everything without having to unlock, unless HTC have changed something in which case S-OFF is useless unless you want to flash an older RUU

You have access if you flash through a zip. That's the only way s-off devices can flash while still locked.
Sent from my hidden jewel

To the OP, you lucky man!!

mehmetolgungun said:
Hi Everyone,
I got my second One today, first one had microphone issues.
I asked my cousin from UK to send me a new one, I got it today and I want to use a custom rom.
But when I opened the bootloader I saw something strange, it was s-off.
My build number is 1.29.206.11 (O2 UK).
I want to install this firmware 1.29.401.12 and a custom recovery after it.
Can I install this firmware directly?
Do I have to unlock my bootloader from htcdev to flash a custom recovery? (Its written locked)
It would be great if someone can tell me what should I do.
P.S.
-fastboot oem unlock doesnt work
-fastboot flash recovery recovery.img doesnt work
Thanks
Click to expand...
Click to collapse
If you are s-off, that's all you need, don't worry about the bootloader being locked, it's immaterial with s-off.

Brick - No OS, Recovery and fastboot problems

Hey Guys, I was wondering if any of you could help me with this....
Background - My HTC One was having issues with the touchscreen, and I was going to hand it in to EE to get it repaired tomorrow. But *naturally* I need to restore it to stock settings first...
What did I do?
1) Installed a ZIP file with the stock recovery/ROM via an AROMA installer from TWRP
2) Tried to relock bootloader, succeeded, but somewhere something went wrong and my ROM got corrupted
3) managed to re-install TWRP via fastboot, but I couldn't get system to mount so I couldn't install any ROM at all
4) Used fastboot to try to wipe system and reformat it, didn't work
5) Managed to remove the tampered flag (still S-OFF at this point though) so my plan was to S-ON and then give it to HTC being all "durr it no werk" and get them to sort everything out on it
6) S-ON'd the phone, only to have the tampered flag appear at this point, so I can't hand it back in and protest my innocence anymore
7) Can no longer S-OFF, install any ROM because I get a remote: signature invalid error for any stock ROM or recovery that I try to install despite my CID being HTC__001 which is the same as the stock ROM I'm trying to push via fastboot
8) Can no longer get into TWRP either
Bottom line - phone is S-ON, bootloader is locked (and won't accept my Unlock_code.bin), tampered flag is on, fastboot won't let me install anything because of a file signature error, No operating system, no working recovery.
If you can help me in any way at all, I'd be eternally grateful!
Dropbox link to potato-cam photos

Da Vikster said:
Hey Guys, I was wondering if any of you could help me with this....
Background - My HTC One was having issues with the touchscreen, and I was going to hand it in to EE to get it repaired tomorrow. But *naturally* I need to restore it to stock settings first...
What did I do?
1) Installed a ZIP file with the stock recovery/ROM via an AROMA installer from TWRP
2) Tried to relock bootloader, succeeded, but somewhere something went wrong and my ROM got corrupted
3) managed to re-install TWRP via fastboot, but I couldn't get system to mount so I couldn't install any ROM at all
4) Used fastboot to try to wipe system and reformat it, didn't work
5) Managed to remove the tampered flag (still S-OFF at this point though) so my plan was to S-ON and then give it to HTC being all "durr it no werk" and get them to sort everything out on it
6) S-ON'd the phone, only to have the tampered flag appear at this point, so I can't hand it back in and protest my innocence anymore
7) Can no longer S-OFF, install any ROM because I get a remote: signature invalid error for any stock ROM or recovery that I try to install despite my CID being HTC__001 which is the same as the stock ROM I'm trying to push via fastboot
8) Can no longer get into TWRP either
Bottom line - phone is S-ON, bootloader is locked (and won't accept my Unlock_code.bin), tampered flag is on, fastboot won't let me install anything because of a file signature error, No operating system, no working recovery.
If you can help me in any way at all, I'd be eternally grateful!
Dropbox link to potato-cam photos
Click to expand...
Click to collapse
The correct steps to Getting back to stock are here >> http://forum.xda-developers.com/showthread.php?t=2541082

Sunshine Soff...

I can't use either of those because I don't have a working OS and I can't flash one via bootloader because of a file signature verification error

Da Vikster said:
I can't use either of those because I don't have a working OS and I can't flash one via bootloader because of a file signature verification error
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (excluding IMEI and s/n)

nkk71 said:
can you post a "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
here you go

Da Vikster said:
here you go
Click to expand...
Click to collapse
Since you are now S-ON and LOCKED, you need to use signed RUU
for PN0710000 + HTC__001, try this one:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
http://androidruu.com/getdownload.p...31.27_10.31.1131.05_release_310878_signed.exe
remember to check MD5 of the download to make sure it's not corrupt
let me know how that goes
oh, and charge your battery

writing 'recovery' FAILED (remote: command not allowed)

Hi o/
Since I have formatted the system of my NEM-L51, I re-installed the stock rom at the last version, but it appears that I have to reinstall TWRP and re-root my phone. But when I do:
Code:
fastboot flash recovery twrp.zip
It returns me
Code:
writing 'recovery'...
FAILED (remote: Command not allowed)
My bootloader is unlocked.
Any solution?
(and sorry if my english is bad)

Akioru said:
Hi o/
Since I have formatted the system of my NEM-L51, I re-installed the stock rom at the last version, but it appears that I have to reinstall TWRP and re-root my phone. But when I do:
Code:
fastboot flash recovery twrp.zip
It returns me
Code:
writing 'recovery'...
FAILED (remote: Command not allowed)
My bootloader is unlocked.
Any solution?
(and sorry if my english is bad)
Click to expand...
Click to collapse
Hm.
I think I know
fastboot flash recovery twrp.zip not zip but img, and the recovery in ADB folder needs to be img not zipped

ConradP said:
It returns me
My bootloader is unlocked.
Any solution?
(and sorry if my english is bad)
Hm.
I think I know
fastboot flash recovery twrp.zip not zip but img, and the recovery in ADB folder needs to be img not zipped
Click to expand...
Click to collapse
Oh, thanks. Im gonna try

ConradP said:
Hm.
I think I know
fastboot flash recovery twrp.zip not zip but img, and the recovery in ADB folder needs to be img not zipped
Click to expand...
Click to collapse
Doesn't work, here's a screen of my cmd
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Akioru said:
Hi o/
Since I have formatted the system of my NEM-L51, I re-installed the stock rom at the last version, but it appears that I have to reinstall TWRP and re-root my phone. But when I do: It returns me
My bootloader is unlocked.
Any solution?
(and sorry if my english is bad)
Click to expand...
Click to collapse
Just unlock ur bootloader again, and it will work.

also you should run cmd as admin, it might help

Shubho20 said:
Just unlock ur bootloader again, and it will work.
Click to expand...
Click to collapse
Doesn't work, i still have the failed (remote: command not allowed

Akioru said:
Doesn't work, i still have the failed (remote: command not allowed
Click to expand...
Click to collapse
Have u enabled oem unlock in developers settings?

thelous said:
also you should run cmd as admin, it might help
Click to expand...
Click to collapse
Doesn't work

Maybe my experience can help : https://forum.xda-developers.com/showpost.php?p=71730671&postcount=106

romroro said:
Maybe my experience can help : https://forum.xda-developers.com/showpost.php?p=71730671&postcount=106
Click to expand...
Click to collapse
So if I understood well, I should put the recovery image into the dload folder?

Akioru said:
So if I understood well, I should put the recovery image into the dload folder?
Click to expand...
Click to collapse
No, you need to put update.app in dload folder. Also have you installed the hi suite app on your computer/laptop? It contains the drivers you need to communicate with your device. I think this might solve your error message when tying to use adb or fastboot.
Sent from my NEM-L51 using XDA Labs

iantechie1979 said:
No, you need to put update.app in dload folder. Also have you installed the hi suite app on your computer/laptop? It contains the drivers you need to communicate with your device. I think this might solve your error message when tying to use adb or fastboot.
Click to expand...
Click to collapse
Hisuite is installed but I don't have an uppdate.app file, just a twrp.img

Akioru said:
Hisuite is installed but I don't have an uppdate.app file, just a twrp.img
Click to expand...
Click to collapse
get the .zip file from here
http://hwmt.ru/oth/HWFF/info/view.php?find_model=
and extract it you will have update.app in it .
By the way did you accept permission prompt in the phone when connected to PC? for RSA key?

miststudent2011 said:
get the .zip file from here
http://hwmt.ru/oth/HWFF/info/view.php?find_model=
and extract it you will have update.app in it .
By the way did you accept permission prompt in the phone when connected to PC? for RSA key?
Click to expand...
Click to collapse
But why about the rsa key ?

gopinaidu77 said:
But why about the rsa key ?
Click to expand...
Click to collapse
What is the prompt you get when you connect your device for pc while using ADB?
Its RSA prompt.

miststudent2011 said:
What is the prompt you get when you connect your device for pc while using ADB?
Its RSA prompt.
Click to expand...
Click to collapse
Yeah , but why about it ?

gopinaidu77 said:
Yeah , but why about it ?
Click to expand...
Click to collapse
because if you dont authorize you get remote command not allowed or something like unauthorized error you will get.

Oh my ****ing god, first of all you have to fastboot oem relock 0123456789(your code), and then unlock.

SCUZZY1337 said:
Oh my ****ing god, first of all you have to fastboot oem relock 0123456789(your code), and then unlock.
Click to expand...
Click to collapse
Did he unlocked his bootloader before ?

Hard reset. What to do now?

So frist i did a usual factory reset and it just went recovery and like what happend before didn't do a clean reset, just apps gone and that's it. So i did it manually by checking all "partitions" including "Cache, Data, Internal Storage, System" and all. Now TWRP is all i got on my phone. I didn't know what i'm doing and it was a noob move, i know. But now i managed to copy a custome ROM (Viper One 9.0.0) to my sdcard via adb push command.
Now all i need is to flash it.
TWRP says "This operaion may install incompatible software and render your device unusable"
Is it safe to do so?
I also wanted to go back to Stock ROM and actually downloaded one from HERE. It's the one provided in METHOD 2 .
The only reason i want to flash Viper One again is that i flashed it before without any problem.
If i make sure that it's safe to flash the Stock ROM i'd do it. Please let me know what should i do. Thanks.

Harry_ei8ht said:
So frist i did a usual factory reset and it just went recovery and like what happend before didn't do a clean reset, just apps gone and that's it. So i did it manually by checking all "partitions" including "Cache, Data, Internal Storage, System" and all. Now TWRP is all i got on my phone. I didn't know what i'm doing and it was a noob move, i know. But now i managed to copy a custome ROM (Viper One 9.0.0) to my sdcard via adb push command.
Now all i need is to flash it.
TWRP says "This operaion may install incompatible software and render your device unusable"
Is it safe to do so?
I also wanted to go back to Stock ROM and actually downloaded one from HERE. It's the one provided in METHOD 2 .
The only reason i want to flash Viper One again is that i flashed it before without any problem.
If i make sure that it's safe to flash the Stock ROM i'd do it. Please let me know what should i do. Thanks.
Click to expand...
Click to collapse
-Post your "fastboot getvar all" output (hide your imei/sn)
-What is your twrp version?

alray said:
-Post your "fastboot getvar all" output (hide your imei/sn)
-What is your twrp version?
Click to expand...
Click to collapse
Here it is sir
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP is 3.0.2-2
and btw, seems like i can't flash anything with twrp now. keep saying "zip signature failed"!

And please guide me through on how can i go back to stock rom safely.
Of course i can find tons of articles about it but there are few confusions and since it can end in a brick i can't risk it. For example is THIS ONE legit? for flashing RUU, is the one i mentioned above will do it? I mean THIS ONE
or if there's any better guide here (sure there's, i know!) please link it here. Thanks

Harry_ei8ht said:
And please guide me through on how can i go back to stock rom safely.
Of course i can find tons of articles about it but there are few confusions and since it can end in a brick i can't risk it. For example is THIS ONE legit? for flashing RUU, is the one i mentioned above will do it? I mean THIS ONE
or if there's any better guide here (sure there's, i know!) please link it here. Thanks
Click to expand...
Click to collapse
Linked guide is for M8 and does not apply to your situation.
reflash the stock recovery, relock the bootloader and flash the 7.19.401.51 RUU
Code:
fastboot flash recovery M7_UL_Stock_Recovery_7.19.401.51.img
fastboot erase cache
fastboot reboot-bootloader
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
fastboot reboot
You must use this fastboot version at least for the "fastboot flash zip" command.

alray said:
Linked guide is for M8 and does not apply to your situation.
reflash the stock recovery, relock the bootloader and flash the 7.19.401.51 RUU
Code:
fastboot flash recovery M7_UL_Stock_Recovery_7.19.401.51.img
fastboot erase cache
fastboot reboot-bootloader
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
fastboot reboot
You must use this fastboot version at least for the "fastboot flash zip" command.
Click to expand...
Click to collapse
Thanks a ton, alray. I'll let know you how it goes

alray said:
Linked guide is for M8 and does not apply to your situation.
reflash the stock recovery, relock the bootloader and flash the 7.19.401.51 RUU
Code:
fastboot flash recovery M7_UL_Stock_Recovery_7.19.401.51.img
fastboot erase cache
fastboot reboot-bootloader
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
fastboot reboot
You must use this fastboot version at least for the "fastboot flash zip" command.
Click to expand...
Click to collapse
So it went all good till the "fastboot oem rebootRUU" command. It reboots and then htc logo shows up and nothing after that. I have to reboot it by Power+V- in order to go in bootloader again?
Is something wrong? Or should i run the next command there in bootloader?
P.S: Bootloader is relocked, by the way.

NVM. Just ran the command again and it's working now!

It worked man... AWESOME!!

Alright just one more question. If i ever want to root my device again, it will be ok?
And if you have the time, please link the right thread for it. Your work is much appreciated mate. Thanks a billion!

Harry_ei8ht said:
Alright just one more question. If i ever want to root my device again, it will be ok?
And if you have the time, please link the right thread for it. Your work is much appreciated mate. Thanks a billion!
Click to expand...
Click to collapse
You're welcome
Unlock your bootloader again htcdev.com/bootloader
flash latest TWRP for M7
Flash latest Supersu.zip or Magisk

[Q] Recover P10 after mistaken Oreo update to P10+

Hi.
I wanted to upgrade to Oreo manually, but mistakenly downloaded files for P10 Plus VKY-L29C432. The Update was successful and I had a phone with P10+ firmware (DPI was way off).
After update I successfully flashed TWRP over stock recovery. Then I tried to flash the correct Oreo update for VTR-L29C432 but it did not work.
Now I am stuck in ERROR MODE.
Fastboot is working and bootloader is unlocked.
Flashing TWRP does not work.
Is there any way to recover P10 firmware?
https://forum.xda-developers.com/p10/help/help-please-error-mode-recovery-t3757571
This guy successfully flashed recovery by flashing kernel.img first. But there is no kernel.img after extracting Oero`s update.app.

There is a kernel image in the update.app from the update.zip.

There is a kernel.img in P10+ update.app, but not in P10 (Oreo)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

So nothing has helped so far.
Flashed kernel first then TWRP, but I cannot boot into it.
Is there a way I can flash all those IMGs from UPDATE.APP from bootloader?

Hi Cesedy, I'm in the exact same situation as you (https://forum.xda-developers.com/showpost.php?p=75791054&postcount=36) and am out of ideas. I even tried manually flashing the system.img via fastboot but not joy.
There must be a way of recovering the device, but I'm not sure where to go next...:crying:

Hi.
I am out of options as well.
But, there is a saying in this forum, that if bootloader is unlocked and fastboot is working, there is a way out.
Still waiting for it.
Anyway, I opened a thread in this forum too - https://forum.hovatek.com/thread-22218.html

Are we having the same problem?
Thread
I found the kernel.img in the update.app of the FULL-OTA of the oreo update but it was not helpful nor a solution!

The same.

Out of curiousity? does everybody get their previous version for fastboot oem get-build-number?
maybe we should update the bootloader?

Update and a suggestion from the manual updating thread: https://forum.xda-developers.com/showpost.php?p=75800881&postcount=40.

martindoublem said:
Out of curiousity? does everybody get their previous version for fastboot oem get-build-number?
maybe we should update the bootloader?
Click to expand...
Click to collapse
I get:
Code:
D:\>fastboot oem get-build-number
...
(bootloader) :System 8.0.0.046(062P)
OKAY [ 0.003s]
finished. total time: 0.004s

martindoublem said:
Out of curiousity? does everybody get their previous version for fastboot oem get-build-number?
maybe we should update the bootloader?
Click to expand...
Click to collapse
I get this with that command:
Code:
(bootloader) :System 8.0.0.046(04W5)
OKAY [ 0.008s]
finished. total time: 0.010s
grockstar said:
Update and a suggestion from the manual updating thread: https://forum.xda-developers.com/showpost.php?p=75800881&postcount=40.
Click to expand...
Click to collapse
Aw, man, that is not good. Should never lock bootloader if phone is not working.

cesedy said:
Aw, man, that is not good. Should never lock bootloader if phone is not working.
Click to expand...
Click to collapse
Yeah, desperation took over from brains. However no harm appears to have done as the bootloader is actually still unlocked (if the warning splash screen is to be believed).
I've now also managed to get back into fastboot after letting the battery drain completely.

That command is not for locking the bootloader, it is for finding the version. Pretty harmless but useful to find which version we have.

The funky Huawei Unbrick tool did the trick for me on this one. I know it is a pay option but for $50 seems to be worse it.
I was able to boot in the system again, Grockstar was able to get into erecovery so that was progress in both cases!

If anyone needs, can use my DC-Phoenix account, I don`t need it anymore.
Your username is: cesedy
Your password is: dnL4eHEm