Database Develop

[Q] how to Downgrade HBOOT ?

-Revulutionary-
Vivo put ship S-OFF RL
HBOOT-6.13.1002
Radio-3805.06.03.03_M
eMMC-boot
i tried yesterday to make my phone S-on , i used
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe .
but now here it says s-off but i cant use recovery, could someone help me out how to fix again s-off so i could use recovery again ?
so now do i need to downgrade hboot to 1.13 or 1.09 so i can use again revulutionary to gain s-off ? (if yes how to do that ?)

help ?

So it is s off, but you cannot use recovery??
Can you boot into android and use the phone?

markj338 said:
So it is s off, but you cannot use recovery??
Can you boot into android and use the phone?
Click to expand...
Click to collapse
yeah its s-off but i cant use recovery .
i can use the phone but if i try to install the OTA UPDATE than it wont load only htc logo but i fixed that.
now i think i need to downgrade the hboot to 1.13 or 1.09 so i can s-off 100% again with Revulutionary

blerim1234 said:
yeah its s-off but i cant use recovery .
i can use the phone but if i try to install the OTA UPDATE than it wont load only htc logo but i fixed that.
now i think i need to downgrade the hboot to 1.13 or 1.09 so i can s-off 100% again with Revulutionary
Click to expand...
Click to collapse
I got s-on once just by flashing a s-on hboot via fastboot. Not sure if you can overwrite a 6.13 hboot with a 1.13 but it could work

yesterday i tried to make s-on with this
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed.exe
it was installed good i could install ota updates from my phone. but when i did install the ota than my phone didnt work only HTC logo. but i used FASTBOOT USB so i could install again RUU_Vivo_Gingerbread_S_HTC . And the phone is still s-off .
but when i go to Rom manager it says that i dont have permission cause i dont have a rooted phone ?

Random thought: can you root with gingerbreak?

markj338 said:
Random thought: can you root with gingerbreak?
Click to expand...
Click to collapse
im trying it now , but 5 minutes only loading nothing .

blerim1234 said:
-Revulutionary-
Vivo put ship S-OFF RL
HBOOT-6.13.1002
Radio-3805.06.03.03_M
eMMC-boot
i tried yesterday to make my phone S-on , i used
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe .
but now here it says s-off but i cant use recovery, could someone help me out how to fix again s-off so i could use recovery again ?
so now do i need to downgrade hboot to 1.13 or 1.09 so i can use again revulutionary to gain s-off ? (if yes how to do that ?)
Click to expand...
Click to collapse
Did you check this FAQ sticky?
http://forum.xda-developers.com/showthread.php?t=1435136
It describes why running an RUU with Revolutionary S-OFF did not work. You need to find the thread that discusses returning to S-ON from Revolutionary S-OFF.
http://forum.xda-developers.com/showthread.php?t=1359555&highlight=revolutionary+s-on

tpbklake said:
Did you check this FAQ sticky?
http://forum.xda-developers.com/showthread.php?t=1435136
It describes why running an RUU with Revolutionary S-OFF did not work. You need to find the thread that discusses returning to S-ON from Revolutionary S-OFF.
http://forum.xda-developers.com/showthread.php?t=1359555&highlight=revolutionary+s-on
Click to expand...
Click to collapse
i want now to keep s-off i have some backups but i cant restore. when i go to rom manager it says that my phone its not rooted. ??
can u tell me how to restore the backup so i can make my phone like it was ?

blerim1234 said:
i want now to keep s-off i have some backups but i cant restore. when i go to rom manager it says that my phone its not rooted. ??
can u tell me how to restore the backup so i can make my phone like it was ?
Click to expand...
Click to collapse
Don't use ROM Manager. Boot into HBOOT and then select RECOVERY from the menu. Or with the phone booted, connect the phone via USB, open up a command window and then type:
adb reboot recovery

adb server is out of date. killing .......
*daemon started successfully *
error : device not found
im doing something wrong but dont know what.
thanks for your help

this happend after i did adb reboot recovery
{
"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"
}

try reverting to Stock.)
hey wanna try this thing, may be it'll work.)
or wanna try this thing..!?)

blerim1234 said:
this happend after i did adb reboot recovery
Click to expand...
Click to collapse
OK, so when you attempted to run the RUU, it overwrote ClockworkMod recovery with the stock recovery.
In the FAQ thread I posted, you need to reinstall ClockworkMod recovery before you will be able to restore your backup.
The easiest way to do that is to boot into FASTBOOT USB mode and then enter:
fastboot flash recovery [path to recovery image file]

tpbklake said:
OK, so when you attempted to run the RUU, it overwrote ClockworkMod recovery with the stock recovery.
In the FAQ thread I posted, you need to reinstall ClockworkMod recovery before you will be able to restore your backup.
The easiest way to do that is to boot into FASTBOOT USB mode and then enter:
fastboot flash recovery [path to recovery image file]
Click to expand...
Click to collapse
Where can i find the recovery image bro and where do i need to put it
And thnx very much for your help

blerim1234 said:
Where can i find the recovery image bro and where do i need to put it
And thnx very much for your help
Click to expand...
Click to collapse
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vivo.img
Download and put the file in the directory where you have setup adb.exe and fastboot.exe.

tpbklake said:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vivo.img
Download and put the file in the directory where you have setup adb.exe and fastboot.exe.
Click to expand...
Click to collapse
i have put adb.exe and fastboot.exe in C:android
so i have putted the file there
when i go to cmd and write
"fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img"
it says error cannot load "recovery-clockwork-5.0.2.0-vivo.img"

blerim1234 said:
i have put adb.exe and fastboot.exe in C:android
so i have putted the file there
when i go to cmd and write
"fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img"
it says error cannot load "recovery-clockwork-5.0.2.0-vivo.img"
Click to expand...
Click to collapse
Try renaming the file to
recovery.img and then type
fastboot flash recovery recovery.img
You do have the phone in FASTBOOT USB mode, right?

its on fastboot usb but still not working
it says error cannot load "recovery.img"
dont know why

[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.

[GUIDE] Return to Stock with hboot 1.56+ (M7) - Telstra Australia (no ruu avail)

Due to the massive inconvenience/time this has caused me, having little experience initially with android devices and coupled with the fact Telstra Australia will not release an RUU to make things easy, I thought I would document my method for those currently on hboot 1.5x+ who are wanting to roll their device back to complete stock. This process is specifically for people who want a Telstra branded rom for warranty and does require sunshine if you have hboot 1.57. This is for the HTC one M7 although I suspect the process is the same on the M8..
This method was performed in Windows 7 as Windows 8 seems to have issue with fastboot commands. If you have a different carrier, are performing this on Mac or plan to use a Nandroid please see nkk71’s superguide for more details. Unfortunately the only 2 Telstra Nandroids I could find both failed for me.
*Please make sure fastboot is unchecked and usb debugging is turned on in developer options
I have packaged all of the tools needed including the RUU.zip I used in the link below. The Guru files are hosted separately.
http://1drv.ms/1AVZvMF
The Guru files are hosted here, you will need both of these.
Stock Rom – Guru Reset
http://www.htc1guru.com/dld/guru_reset_m7_2-24-841-1-zip/ - download
http://www.htc1guru.com/downloads/stock-rom-downloads/ - info
Bootloader to remove tamper/lock bootloader
http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/ - download
http://forum.xda-developers.com/showthread.php?t=2527194 - info
1. S-off must be achieved. If you have it already you are in luck, proceed. This table also appears in nk771's superguide showing what you can or cannot achieve with S-off for reference.
{
"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"
}
Methods:
a) If you’re on hboot 1.44 use revone -
http://forum.xda-developers.com/showthread.php?t=2314582
http://revolutionary.io/
b) If you are hboot 1.54/1.55 you can attempt rumrunner
http://forum.xda-developers.com/showthread.php?t=2488772
http://rumrunner.us/
c) If you are in hboot 1.56/1.57 you will need sunshine for $25usd as I did. As far as I am aware there is currently no way around it. However I am very happy with this application and support. Firewater is discontinued.
http://theroot.ninja/
2. Reboot into bootloader/fastboot usb and perform getvar
fastboot getvar all
Note the following:
version-bootloader: 1.57.0000– hboot version
cidnum: TELST001 - CID
modelid: PN0714000 – MID
version-main: 5.11.841.9 – firmware
All Telstra devices should have a modelid of PN0714000. If for some reason you do not have this MID see nkk71’s superguide for different MID/CID RUUs and download a different version.
BOOT LOOP
The firmware will be reset to a 1.29.x base when you flash the RUU which is fine for OTA updates. If you have previously experienced boot loop it is because the firmware coming out in the OTA updates is lower than the firmware already installed on your device. Firmware can only be upgraded not downgraded by OTAs.
3. Provided your MID is PN0714000 proceed to change your CID to match RUU CID. The CID associated with the RUU provided is HTC__044
fastboot oem writecid HTC__044
fastboot reboot-bootloader
*confirm CID is now HTC__044 – see bootloader or getvar
4. Flash the RUU.
fastboot oem rebootRUU (silver htc will appear)
fastboot flash ruu.zip (it will report failed flush, repeat command)
fastboot flash ruu.zip (success)
fastboot reboot-bootloader
*bootloader should now read hboot 1.44
5. Change CID back to stock (TELST001)
fastboot oem writecid TELST001
fastboot reboot-bootloader
6. Mount and Launch TWRP custom recovery
fastboot boot openrecovery-twrp-2.8.4.0-m7
7. Once in TWRP your phone become available as a mass storage device. Run an ADB command to check the phone is being recognized in windows and then push the guru reset rom to the device.
adb devices
adb push Guru_Reset_M7_2.24.841.1.zip /data/media
If your device does not display a serial number executing an adb devices command you will need to install the drivers in device manager, it is likely an unrecognized device post RUU flash. See nk771s FAQ for instructions.
8. In TWRP recovery hit install, navigate to the data/media folder and select the Guru_Reset_M7_2.24.841.1.zip
Run through the installer and select the options as seen in this video
https://www.youtube.com/watch?v=Gqfly8XVw6w
When complete hit – do not add root and reboot the device. If it gives option to wipe cache, do so.
9. Boot your phone as normal into the now stock 4.2.2 Rom, set up wireless and install the first two small OTA updates to confirm they are working. If successful uncheck fastboot/enable usb debugging again and reboot phone back into boot loader with adb command.
abd reboot bootloader
10. In fastboot USB mount/launch TWRP recovery then adb push the Guru Boot Loader tool to the device.
fastboot boot openrecovery-twrp-2.8.4.0-m7
adb push Guru_Bootloader_Reset_1.0.zip /data/media
11. Hit Install, Navigate to the folder and launch Guru_Bootloader_Reset_1.0.zip. Run through the wizard and select remove tamper and lock function then wipe cache. Video here for clarification.
https://www.youtube.com/watch?v=yimzmt23E6Q
12. Reboot the phone a few times into bootloader to make sure lock/tamper does not return
fastboot reboot-bootloader
If unlocked/tamper returns or the installer fails you may have to use the manual method, exercise caution. See nk771's FAQ for instructions.
13. Set S-on
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Fastboot into bootloader a few times to make sure everything is fine before proceeding to final OTA updates.
14. Boot phone normally and proceed to do all of the remaining OTA updates to bring your software/firmware up to latest version. Sometimes the phone will boot into stock recovery mode first time after S-on, just reboot it, it will come good.
If you would prefer to use a Nandroid backup (although I am not sure why), start from step 7 and restore it via TWRP or CWM (depending on the backup type) in place of Guru Reset. After this is complete you can proceed with the remaining steps.
This all came about from Telstra being unwilling to repair my purple haze issue (which is clearly a sensor/camera module hardware defect) while having my bootloader unlocked/tampered. The purple haze issue occurred when my device was factory locked. I understand unlocking the boot loader voids warranty but this issue is hardware related which happens on stock software/firmware. I find it a little dishonest that HTC/Telstra want to charge me to have my unit replaced/repaired when it's a known hardware defect unless I am willing to go back through the process of making this device look like it's stock. I hope this can help some of the Telstra customers in the same position as RUU/Nandroids are almost non existent. Thank god for guru!

Swattysin said:
This table shows what you can or cannot achieve with S-off for reference. Cannot remember exactly where I found this.
Click to expand...
Click to collapse
its also from nkk71's guide
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2 "not so FAQ 2)"
and also here: http://forum.xda-developers.com/showpost.php?p=49832723&postcount=388

alray said:
its also from nkk71's guide
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2 "not so FAQ 2)"
and also here: http://forum.xda-developers.com/showpost.php?p=49832723&postcount=388
Click to expand...
Click to collapse
Ohh rad, cheers , I will update. The second post is where I saw it

Swattysin said:
I have packaged all of the tools needed including the RUU.zip I used in the link below. The Guru files are hosted separately.
http://1drv.ms/1AVZvMF
Click to expand...
Click to collapse
Hey Swattysin. Do you still have the RUU.zip? I couldnt get your link to work.
Thanks for your guide!

I checked the file on my onedrive and it appears to be fine. Does the rar fail to open once downloaded or you cannot download the link period?
Try this one
http://1drv.ms/1AVZvMF
If downloading that file fails let me know and I will upload it to dropbox instead
Deuser said:
Hey Swattysin. Do you still have the RUU.zip? I couldnt get your link to work.
Thanks for your guide!
Click to expand...
Click to collapse

Swattysin said:
Try this one
http://1drv.ms/1AVZvMF
Click to expand...
Click to collapse
Thanks for that Swattysin. Looks like it was just my computer, tried the link on another computer and it worked fine!
Thanks again!

Swattysin said:
4. Flash the RUU.
fastboot oem rebootRUU (silver htc will appear)
fastboot flash ruu.zip (it will report failed flush, repeat command)
fastboot flash ruu.zip (success)
fastboot reboot-bootloader
Click to expand...
Click to collapse
Cheers for the instructions, still going through it but one correction, the command fastboot flash ruu.zip needs to be fastboot flash zip ruu.zip

chrysilis said:
Cheers for the instructions, still going through it but one correction, the command fastboot flash ruu.zip needs to be fastboot flash zip ruu.zip
Click to expand...
Click to collapse
Will recommend you to directly follow instructions from nkk71's superguide to return stock (linked in my sig).

Soft Brick on HTC One (m7)

Hi everyone,
I have an HTC One (m7), carrier H3G Italy, unlocked, tampered, S-ON, wtih TWRP 3.0 installed. I had CyanogenMod installed (version 12.x). Recently my phone stopped working without any reason and when I tried to reboot it simply didin't work.
Following some guides I found in this site, I tried to flash a new recovery (the update of TWRP) and the stock recovery, I also tried to flash a new ROM with adb sideload, but nothing worked.
Please help me :angel:.
Thank you a lot

TRenghia said:
Hi everyone,
I have an HTC One (m7), carrier H3G Italy, unlocked, tampered, S-ON, wtih TWRP 3.0 installed. I had CyanogenMod installed (version 12.x). Recently my phone stopped working without any reason and when I tried to reboot it simply didin't work.
Following some guides I found in this site, I tried to flash a new recovery (the update of TWRP) and the stock recovery, I also tried to flash a new ROM with adb sideload, but nothing worked.
Please help me :angel:.
Thank you a lot
Click to expand...
Click to collapse
can you please post the output of "fastboot getvar all" (hide your imei and sn)?
What do you mean by "stopped working" and "tried to reboot it simply didn't work"
The phone doesn't boot in the ROM or it doesn't boot at all (i.e not even in bootloader) ?
Please post a link to the rom you are trying to flash and to the twrp version you are using.
Also you don't need to use sideload anymore when using recent twrp version. TWRP now support MTP so you can simply boot in twrp with your phone connected to your computer and you'll see your phone internal storage from your computer (like a usb thumb drive). Simply drag and drop the rom.zip from you computer to your phone then use the "install" menu of twrp to flash it. From my experience, adb sideload isn't always reliable...

alray said:
can you please post the output of "fastboot getvar all" (hide your imei and sn)?
What do you mean by "stopped working" and "tried to reboot it simply didn't work"
The phone doesn't boot in the ROM or it doesn't boot at all (i.e not even in bootloader) ?
Please post a link to the rom you are trying to flash and to the twrp version you are using.
Also you don't need to use sideload anymore when using recent twrp version. TWRP now support MTP so you can simply boot in twrp with your phone connected to your computer and you'll see your phone internal storage from your computer (like a usb thumb drive). Simply drag and drop the rom.zip from you computer to your phone then use the "install" menu of twrp to flash it. From my experience, adb sideload isn't always reliable...
Click to expand...
Click to collapse
Hi alray,
Thank you for your help. With "stopped wroking", I mean that the phone doesn't boot in the ROM, and when I said "reboot", I mean just switch off and on. I can boot in the bootloader and the recovery .
Now I am using TWRP version 3.0.0-0 and I'd like to flash this ROM.
{
"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"
}

TRenghia said:
Hi alray,
Thank you for your help. With "stopped wroking", I mean that the phone doesn't boot in the ROM, and when I said "reboot", I mean just switch off and on. I can boot in the bootloader and the recovery .
Now I am using TWRP version 3.0.0-0 and I'd like to flash this ROM.
Click to expand...
Click to collapse
Are you sure your phone wasn't running a newer version than 7.19.771.1? Like maybe 7.19.771.21, 7.19.771.31 or 7.19.771.51? Hard to know since your version-main is blank
Better to edit your version-main to 7.19.771.1 to be 100% sure the RUU will work.
Boot in twrp main menu then open a command window on your computer and type:
Code:
adb shell
echo -ne "7.19.771.1\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
Make sure there is no typo in the long command (copy/paste if needed)
When back in bootloader mode check your version-main is now 7.19.771.1
Code:
fastboot getvar all
Then re-lock your bootloader
Code:
fastboot oem lock
and flash the 7.19.771.1 ruu (make sure the RUU zip file is in the same folder where you have fastboot on your computer. You MUST use the fastboot version linked in the OP of the ruu collection thread to flash the RUU https://androidfilehost.com/?fid=95916177934539737. The "regular" fastboot from the android sdk tool won't work.
Code:
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420805_signed.zip
fastboot reboot

alray said:
Are you sure your phone wasn't running a newer version than 7.19.771.1? Like maybe 7.19.771.21, 7.19.771.31 or 7.19.771.51? Hard to know since your version-main is blank
Better to edit your version-main to 7.19.771.1 to be 100% sure the RUU will work.
Boot in twrp main menu then open a command window on your computer and type:
Code:
adb shell
echo -ne "7.19.771.1\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
Make sure there is no typo in the long command (copy/paste if needed)
When back in bootloader mode check your version-main is now 7.19.771.1
Code:
fastboot getvar all
Then re-lock your bootloader
Code:
fastboot oem lock
and flash the 7.19.771.1 ruu (make sure the RUU zip file is in the same folder where you have fastboot on your computer. You MUST use the fastboot version linked in the OP of the ruu collection thread to flash the RUU https://androidfilehost.com/?fid=95916177934539737. The "regular" fastboot from the android sdk tool won't work.
Code:
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420805_signed.zip
fastboot reboot
Click to expand...
Click to collapse
Hi alray,
I've done what you suggested, but I couldn't change my version-main (I copied the command) and, when I tried ti flash the new ROM this is what I got

TRenghia said:
Hi alray,
I've done what you suggested, but I couldn't change my version-main (I copied the command) and, when I tried ti flash the new ROM this is what I got
Click to expand...
Click to collapse
I don't really understand why you jumped to step 3 if step 1 didn't worked... Now that the bootloader is relocked you can't boot in twrp anymore to write the correct version-main (might be problematic). What was the problem when changing the version-main? Why not posting it and waiting for help instead of jumping to step #3?
After doing "fastboot oem rebootRUU" did your phone rebooted in ruu mode (a black screen with silver HTC logo on it)?

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