my htc one m7 is on some type of gray screen while converting this to Google play edition i would like to get this problem solved
i am new to these root type of stuff so any info would help thanks
{
"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"
}
the phone breaker said:
my htc one m7 is on some type of gray screen while converting this to Google play edition i would like to get this problem solved
i am new to these root type of stuff so any info would help thanks
View attachment 2699760
Click to expand...
Click to collapse
Were you using the eng hboot to change mid when it occurred?
alray said:
Were you using the eng hboot to change mid when it occurred?
Click to expand...
Click to collapse
yes i was doing what it told me to do
the phone breaker said:
yes i was doing what it told me to do
Click to expand...
Click to collapse
this procedure to change mid is very outdated and there is now much easier and safer way to do it with a tool from custom recovery.
Just to be sure, you were doing this procedure to change mid right?
alray said:
this procedure to change mid is very outdated and there is now much easier and safer way to do it with a tool from custom recovery.
Just to be sure, you were doing this procedure to change mid right?
Click to expand...
Click to collapse
yeah i was using that
alray said:
this procedure to change mid is very outdated and there is now much easier and safer way to do it with a tool from custom recovery.
Just to be sure, you were doing this procedure to change mid right?
Click to expand...
Click to collapse
and also when i try to put an ruu across it says error
the phone breaker said:
and also when i try to put an ruu across it says error
Click to expand...
Click to collapse
what error? Did you sucesfully changed your MID/CID? What OS on your PC?
please post the output of ''fastboot getvar all'' except imei/sn
alray said:
what error? Did you sucesfully changed your MID/CID? What OS on your PC?
please post the output of ''fastboot getvar all'' except imei/sn
Click to expand...
Click to collapse
i dont remember it was a long time a go sorry
the phone breaker said:
i dont remember it was a long time a go sorry
Click to expand...
Click to collapse
so if you can't tell me what is your PC OS and you can't post a fastboot getvar all I can't help you.
alray said:
so if you can't tell me what is your PC OS and you can't post a fastboot getvar all I can't help you.
Click to expand...
Click to collapse
window 7
the phone breaker said:
window 7
Click to expand...
Click to collapse
fastboot getvar all
I can't be more clear, need those info.
alray said:
fastboot getvar all
I can't be more clear, need those info.
Click to expand...
Click to collapse
do i need any files or somthing?
the phone breaker said:
do i need any files or somthing?
Click to expand...
Click to collapse
you should still be able to use fastboot commands from that gray screen. So do that commands:
Code:
fastboot getvar all
copy/paste or post a screenshot except the IMEI and Serial #. See the example below:
The output of ''fastboot getvar all'' is required to determine what are the possiblities to restore your phone. I'm assuming here that you know how to use fastboot because you have used it previously to flash the eng hboot.
alray said:
you should still be able to use fastboot commands from that gray screen. So do that commands:
Code:
fastboot getvar all
copy/paste or post a screenshot except the IMEI and Serial #. See the example below:
The output of ''fastboot getvar all'' is required to determine what are the possiblities to restore your phone. I'm assuming here that you know how to use fastboot because you have used it previously to flash the eng hboot.
Click to expand...
Click to collapse
sorry for late reply
but here
the phone breaker said:
sorry for late reply
but here
Click to expand...
Click to collapse
ok so to return to dev edition:
launch the 4.19.1540.9 ruu.exe
or for google edtition do that command:
Code:
fastboot oem writecid GOOGL001
then launch google edition ruu
alray said:
ok so to return to dev edition:
launch the 4.19.1540.9 ruu.exe
or for google edtition do that command:
Code:
fastboot oem writecid GOOGL001
then launch google edition ruu
Click to expand...
Click to collapse
could you send a link for it as i have deleted all them files
also i have no baseband whats that about??
the phone breaker said:
could you send a link for it as i have deleted all them files
also i have no baseband whats that about??
Click to expand...
Click to collapse
baseband is your radio. It will be flashed back with a ruu.
latest dev edition ruu: http://www.htc1guru.com/2014/03/android-dev-ruu/
latest GPE ruu: http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
For the ruu.exe(DEV edition), just lauch the .exe file with phone in bootloader.
For the ruu.zip (GPE)
boot phone in bootloader
make sure the ruu.zip is in the same folder of adb and fastboot
Code:
fastboot oem writecid GOOGL001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip name_of_file.zip [COLOR="Red"]---> will fail first time and ask you to ''flush'' image again immediately
[/COLOR]fastboot flash zip name_of_file.zip [COLOR="red"]so do the command twice. There's no progress bar, this can take up to 20 mins[/COLOR]
fastboot reboot
Just a side note:
If you are going to use the GPE ruu, NEVER turn security back to S-ON and NEVER relock bootloader :angel:
alray said:
baseband is your radio. It will be flashed back with a ruu.
latest dev edition ruu: http://www.htc1guru.com/2014/03/android-dev-ruu/
latest GPE ruu: http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
For the ruu.exe(DEV edition), just lauch the .exe file with phone in bootloader.
For the ruu.zip (GPE)
boot phone in bootloader
make sure the ruu.zip is in the same folder of adb and fastboot
Code:
fastboot oem writecid GOOGL001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip name_of_file.zip [COLOR="Red"]---> will fail first time and ask you to ''flush'' image again immediately
[/COLOR]fastboot flash zip name_of_file.zip [COLOR="red"]so do the command twice. There's no progress bar, this can take up to 20 mins[/COLOR]
fastboot reboot
Just a side note:
If you are going to use the GPE ruu, NEVER turn security back to S-ON and NEVER relock bootloader :angel:
Click to expand...
Click to collapse
when i want to flash ruu it is sayin (waiting for device)
the phone breaker said:
when i want to flash ruu it is sayin (waiting for device)
Click to expand...
Click to collapse
try renaming the ruu with a simpler name and avoid spaces in the ruu name. renamed it i.e google.zip
Code:
fastboot oem rebootRUU
fastboot flash zip google.zip
fastboot flash zip google.zip
fastboot reboot
alray said:
try renaming the ruu with a simpler name and avoid spaces in the ruu name. renamed it i.e google.zip
Code:
fastboot oem rebootRUU
fastboot flash zip google.zip
fastboot flash zip google.zip
fastboot reboot
Click to expand...
Click to collapse
the htc is saying the same things when i put the code fastboot oem rebootRUU
Its like my phone turns off instead.
Related
i locked the bootloader and s-on'd my htc one that but i forgot to flash the RUU.
my phone is now stuck on the bootloader, what should i do, flash an RUU.zip or what?
hboot 1.54.0000
radio 4A.17.3250.20
os 2.24.401.1
was running viper 4.1
How about you start with a fastboot getvar all output (remove imei/sn) ?
Can you Soff on venom?
SaHiLzZ said:
How about you start with a fastboot getvar all output (remove imei/sn) ?
Can you Soff on venom?
Click to expand...
Click to collapse
what is the command i type in for getvar? i typed in ./fastboot getvar all output (on mac) and just got a list of commands
i got help over in the irc and they were just telling me to flash an ruu zip. which one though http://www.htc1guru.com/downloads/ruu-zip-downloads/
?
milesjohnson said:
i got help over in the irc and they were just telling me to flash an ruu zip. which one though http://www.htc1guru.com/downloads/ruu-zip-downloads/
?
Click to expand...
Click to collapse
Find the one with version of your OS (which is 2.24.401.xx)
Command is fastboot getvar all
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).
I converted this phone to Google play edition when it first possible to do so.
I relocked the bootloader and unrooted it and gave it to my sister in law.
Just got it back and need to replace the camera before I give it to my son.
I want to unlock the bootloader and root it and put twrp on it.
For some reason I have struggled to do so.
{
"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"
}
Sent from my SM-N920T
As you can see I've tried with fastboot oem unlock as well as with through htc dev. Neither wants to work for me.
Any help is greatly appreciated.
Sent from my SM-N920T
donharden2002 said:
As you can see I've tried with fastboot oem unlock as well as with through htc dev. Neither wants to work for me.
Any help is greatly appreciated.
Sent from my SM-N920T
Click to expand...
Click to collapse
Well its a well known issue with the GPE bootloader (not being able to unlock it). Luckily your phone is already S-OFF so all you have to do is the flash a custom recovery in a masked firmware.zip (I made one for you that will flash twrp see attached files at the end of my post), boot in recovery. Then you can unlock the bootloader using an adb shell from twrp recovery so its easier to flash the recovery the next time.
so with your phone in bootloader mode and showing "fastboot usb" in red:
Code:
fastboot oem rebootRUU
this will get you in RUU mode, a black screen with a silver HTC logo.
Code:
fastboot flash zip firmware.zip
First flash will probably report something like "Flush image again immediately" so do the same command again:
Code:
fastboot flash zip firmware.zip
Make sure the command window report "Sucessful" then reboot in bootloader:
Code:
fastboot reboot-bootloader
Thats how you flash a custom recovery on a locked bootloader + s-off phone.
Now, from the bootloader menu, select "recovery" and once booted in twrp recovery (main menu) use these commands to unlock the bootloader:
Code:
adb shell
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
adb reboot bootloader
and confirm your bootloader is now unlocked.
Btw you should revise your commands, I see in the first pic you are making a lot of errors
fastboot oem read cid ----> fastboot oem readcid
fastboot write cid 11111111 ----> fastboot oem writecid 11111111
alray said:
Well its a well known issue with the GPE bootloader (not being able to unlock it). Luckily your phone is already S-OFF so all you have to do is the flash a custom recovery in a masked firmware.zip (I made one for you that will flash twrp see attached files at the end of my post), boot in recovery. Then you can unlock the bootloader using an adb shell from twrp recovery so its easier to flash the recovery the next time.
so with your phone in bootloader mode and showing "fastboot usb" in red:
Code:
fastboot oem rebootRUU
this will get you in RUU mode, a black screen with a silver HTC logo.
Code:
fastboot flash zip firmware.zip
First flash will probably report something like "Flush image again immediately" so do the same command again:
Code:
fastboot flash zip firmware.zip
Make sure the command window report "Sucessful" then reboot in bootloader:
Code:
fastboot reboot-bootloader
Thats how you flash a custom recovery on a locked bootloader + s-off phone.
Now, from the bootloader menu, select "recovery" and once booted in twrp recovery (main menu) use these commands to unlock the bootloader:
Code:
adb shell
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
adb reboot bootloader
and confirm your bootloader is now unlocked.
Btw you should revise your commands, I see in the first pic you are making a lot of errors
fastboot oem read cid ----> fastboot oem readcid
fastboot write cid 11111111 ----> fastboot oem writecid 11111111
Click to expand...
Click to collapse
Thank you, worked like a charm. Greatly appreciated.
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)?
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