Previously i am using ARHD rom and now I would like to know how to turn S back on and how to get rid of alpharev. I already reinstalled the RUU, but alpharev is still there and S is still off. How do I fix this? Thanks!
I have the same problem. What did you installed the RUU?
You can try to reflash the recovery extracted from the RUU.
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
After reapply the RUU.
If i remeber correctly the problem is CWR
I think that it is not in recovery. because recovery is flash to stock. CWR is not there, but the S-OFF is still there, not in HBOOT?
I did it. i Have S-on
And would you tell us how you did it probably about the same as applying the eng hboot, but with the hboot from the rom
Since alpharevx changes the hboot, I would imagine its something like that
Back to s-on
This procedure is tested only AplhaRevX.
1. Install RUU ROM from: http://forum.xda-developers.com/showthread.php?t=1033922
2. Downgrade HBOOT
2a. download this file: http://alpharev.nl/vivo_downgrade.img
2aa. Connect your phone to the USB
2b.Turn your phone into FastBoot not to HBOOT!!! (VOL DOWN + POWER Button)
2c. Install over fastboot: cmd: "fastboot flash hboot vivo_downgrade.img" (you must install sdk tools)
2d. still fastboot cmd: fastboot reboot-bootloader
3. Start Installation RUU ROM, but DON´T INSTALL !!!!
3a. go tu C:\Users\%username%\AppData\Local\Temp and at last folder find rom.zip
3b. open it, and copy tu folder sdk hboot and instal the same as step 2c.
Related
Is it possible to make s- off with hboot 1.16 with 2.3.3 STOCK OPTUS ROM?
If so, can anyone link me to a proper guide?
I searched and found contradictions, some say yes, some say no....
LOSTLOGIC89 said:
Is it possible to make s- off with hboot 1.16 with 2.3.3 STOCK OPTUS ROM?
If so, can anyone link me to a proper guide?
I searched and found contradictions, some say yes, some say no....
Click to expand...
Click to collapse
There is no current method available to truly gain S-OFF status with HBOOT 1.16. However, that being said, you can use the HTCDEV site to unlock HBOOT 1.16 so that you can flash a custom recovery such as ClockworkMod and then flash a custom ROM. The thing to keep in mind with this solution is after you flash the custom ROM you will probably have to manually flash the boot.img file from the custom ROM using 'fastboot flash boot [path to image file]\boot.img'
There is also some thread posts about downgrading HBOOT 1.16 to HBOOT 1.13 and then you can use Revolutionary to get a true S-OFF HBOOT.
tpbklake said:
There is no current method available to truly gain S-OFF status with HBOOT 1.16. However, that being said, you can use the HTCDEV site to unlock HBOOT 1.16 so that you can flash a custom recovery such as ClockworkMod and then flash a custom ROM. The thing to keep in mind with this solution is after you flash the custom ROM you will probably have to manually flash the boot.img file from the custom ROM using 'fastboot flash boot [path to image file]\boot.img'
There is also some thread posts about downgrading HBOOT 1.16 to HBOOT 1.13 and then you can use Revolutionary to get a true S-OFF HBOOT.
Click to expand...
Click to collapse
I see, i will give it a try .
Thanks.
tpbklake said:
There is no current method available to truly gain S-OFF status with HBOOT 1.16. However, that being said, you can use the HTCDEV site to unlock HBOOT 1.16 so that you can flash a custom recovery such as ClockworkMod and then flash a custom ROM. The thing to keep in mind with this solution is after you flash the custom ROM you will probably have to manually flash the boot.img file from the custom ROM using 'fastboot flash boot [path to image file]\boot.img'
There is also some thread posts about downgrading HBOOT 1.16 to HBOOT 1.13 and then you can use Revolutionary to get a true S-OFF HBOOT.
Click to expand...
Click to collapse
i unlocked my hboot 1.16 with htc dev and downloaded 4ext recovery. How can i flash it ?
EDIT: Never mind, i found out how.
So basicly now i can flash any rom i want ?
LOSTLOGIC89 said:
i unlocked my hboot 1.16 with htc dev and downloaded 4ext recovery. How can i flash it ?
Click to expand...
Click to collapse
Unzip the EXT4.zip file and extract the recovery.img file to your PC. Then with your phone connect to the PC in FASTBOOT mode, type the following command:
fastboot flash recovery [path to your image file]\recovery.img
The command window on your PC should have the working directory set to where you have installed the Android SDK tools with adb.exe and fastboot.exe.
tpbklake said:
Unzip the EXT4.zip file and extract the recovery.img file to your PC. Then with your phone connect to the PC in FASTBOOT mode, type the following command:
fastboot flash recovery [path to your image file]\recovery.img
The command window on your PC should have the working directory set to where you have installed the Android SDK tools with adb.exe and fastboot.exe.
Click to expand...
Click to collapse
Ok i have it installed.
The problem now is i wiped and installed a custum rom (bliss with sense 3.5) and got a stock on htc then tried to go on fastboot usb then flash the img file and still stock at htc. Any ideas?
Edit: never mind forgot to wipe boot.works like a charm thanks again .
Not sure if I am in the right place to ask this question, well, i'll ask anyway.
I unlocked my bootloader using Revolutionary. I now need to revert to stock for warranty. I downloaded the INDIA RUU from goo manager.
I managed to replace the Revolutionary HBOOT by changing mainver. However, my radio is not getting replaced, no matter what I try. As a result, my phone bootloops though the RUU install was successful. So I had to revert to Revolutionary by installing WWE ASIA RUU. This was successful because the Radios are the same ie 3805.04.03.27_M.
I am currently on
HBOOT - 6.13.1002
Radio-3805.04.03.27_M
How can I go back to HBOOT 1.13 and Radio 38.02.01.11_M?
HBOOT - 6.13.1002 is still Revolutionary HBOOT?
I think that this is the easiest way to get stock bootloader and rom back. You need to find the latest WWE ASIA RUU for that.
Is that this one: RUU_VIVO_SENSE30_S_hTC_Asia_WWE_3.09.707.1_Radio_20.4802.30.0822U_3822.10.08.28_M_release_226940_signed.exe ?
If you have the latest RUU succesfully installed including the HBOOT, you're OK.
Inferi0r said:
HBOOT - 6.13.1002 is still Revolutionary HBOOT?
I think that this is the easiest way to get stock bootloader and rom back. You need to find the latest WWE ASIA RUU for that.
Is that this one: RUU_VIVO_SENSE30_S_hTC_Asia_WWE_3.09.707.1_Radio_20.4802.30.0822U_3822.10.08.28_M_release_226940_signed.exe ?
If you have the latest RUU succesfully installed including the HBOOT, you're OK.
Click to expand...
Click to collapse
thanks for the reply...but i don't think i explained my problem properly.
I first downloaded PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip from Goo Manager. This is India RUU, but Froyo. This was what was installed on my phone first.
I first changed the mainver and renamed this RUU to PG32IMG.zip and let the bootloader install it. The HBOOT flashed perfectly, so my HBOOT became 1.09 but my radio was stuck at the same. This led the phone to bootloop because of incompatible radios.
So i tried extracting radio.img from PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip and renamed to PG32IMG.zip and bootloader flash it. But it does not flash. My question is how do I replace the current radio with 38.02.01.11_M? The current radio is 3805.04.03.27_M.
craynet said:
thanks for the reply...but i don't think i explained my problem properly.
I first downloaded PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip from Goo Manager. This is India RUU, but Froyo. This was what was installed on my phone first.
I first changed the mainver and renamed this RUU to PG32IMG.zip and let the bootloader install it. The HBOOT flashed perfectly, so my HBOOT became 1.09 but my radio was stuck at the same. This led the phone to bootloop because of incompatible radios.
So i tried extracting radio.img from PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip and renamed to PG32IMG.zip and bootloader flash it. But it does not flash. My question is how do I replace the current radio with 38.02.01.11_M? The current radio is 3805.04.03.27_M.
Click to expand...
Click to collapse
If you currently have a GB ROM on your phone you also have a GB radio. If you attempt to flash the Froyo RUU you have downloaded, you are going to brick your phone because you cannot flash an older Froyo radio over a GB radio. This is a sure way to brick your phone.
fastboot....
tpbklake said:
If you currently have a GB ROM on your phone you also have a GB radio. If you attempt to flash the Froyo RUU you have downloaded, you are going to brick your phone because you cannot flash an older Froyo radio over a GB radio. This is a sure way to brick your phone.
Click to expand...
Click to collapse
yeah, you are right...i now remember that this will brick my phone, a risk not worth taking.
just a quick question, my phone is factory unlocked (the user I bought if from bought it on amazon.de) and currently I have an ICS rom with ICS radio, can I flash the GB RUU and then update to oficial ICS?
Do I still have to make goldcards and stuff?
skinniezinho said:
just a quick question, my phone is factory unlocked (the user I bought if from bought it on amazon.de) and currently I have an ICS rom with ICS radio, can I flash the GB RUU and then update to oficial ICS?
Do I still have to make goldcards and stuff?
Click to expand...
Click to collapse
With Revolutionary S-OFF, the RUU will not successfully overwrite the HBOOT and you will end up with a phone that won't boot past the HTC screen.
You would need to follow this procedure to allow the GB RUU to run successfully:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
This would leave you with a stock, unrooted phone. You woud be able to use HTCDEV.com to ulock the bootloader so you could root, but you are much better off staying S-OFF and using custom ICS ROMs.
tpbklake said:
With Revolutionary S-OFF, the RUU will not successfully overwrite the HBOOT and you will end up with a phone that won't boot past the HTC screen.
You would need to follow this procedure to allow the GB RUU to run successfully:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
This would leave you with a stock, unrooted phone. You woud be able to use HTCDEV.com to ulock the bootloader so you could root, but you are much better off staying S-OFF and using custom ICS ROMs.
Click to expand...
Click to collapse
Well I was stupid enought to flash the RUU so ended like you said.
I have macOs, downloaded fastboot and did fine till 2d.
I have the rom.zip but when I try to do
"fastboot flash hboot rom.zip"
it says:
cannot load 'rom.zip'
and the same if I try the vivo_downgrade.img
But if I do fastboot reboot-bootloader
It works..any suggestions?
exnerjan said:
This procedure is tested only AplhaRevX.
1. Install RUU ROM from: http://forum.xda-developers.com/show....php?t=1033922
2. Downgrade HBOOT
2a. download this file: http://alpharev.nl/vivo_downgrade.img
2aa. Connect your phone to the USB
2b.Turn your phone into FastBoot not to HBOOT!!! (VOL DOWN + POWER Button)
2c. Install over fastboot: cmd: "fastboot flash hboot vivo_downgrade.img" (you must install sdk tools)
2d. still fastboot cmd: fastboot reboot-bootloader
3. Start Installation RUU ROM, but DON´T INSTALL !!!!
3a. go tu C:\Users\%username%\AppData\Local\Temp and at last folder find rom.zip
3b. open it, and copy tu folder sdk hboot and instal the same as step 2c.
Click to expand...
Click to collapse
skinniezinho said:
Well I was stupid enought to flash the RUU so ended like you said.
I have macOs, downloaded fastboot and did fine till 2d.
I have the rom.zip but when I try to do
"fastboot flash hboot rom.zip"
it says:
cannot load 'rom.zip'
and the same if I try the vivo_downgrade.img
But if I do fastboot reboot-bootloader
It works..any suggestions?
Click to expand...
Click to collapse
Make sure that you have vivo_downgrade.img in the same folder where you run fastboot from.
Also, you cannot flash a ROM.zip file using the command fastboot flash hboot.
tpbklake said:
Make sure that you have vivo_downgrade.img in the same folder where you run fastboot from.
Also, you cannot flash a ROM.zip file using the command fastboot flash hboot.
Click to expand...
Click to collapse
So I do I do?
edit:
Just found it:
6. Rename this "rom.zip" file to "PG32IMG.zip"
7. Now take your SD card from Phone and connect it to your PC using a card reader or some other phone.
8. Paste that renamed "PG32IMG.zip" at the root of your SD Card.
9. Now power off your phone. Pull out the battery.
10. Insert the SD Card back in the phone. Insert the battery.
11. Now hold your volume down key and press power button. Keep the volume down key pressed. It will start your phone in boot-loader menu.
12. Select FASTBOOT if its not already selected and press power button.
13. It will search your SD Card for files and will find "PG32IMG.zip" file and will ask if you want to update.
14. Press the volume up button as instructed to continue and then sit back and relax.
Once finished it will ask you to reboot. Once rebooted, you'll be back on stock ROM with S-On.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1705913
Guys just a quick question.
Is any way to remove the "relocked" status of the bootloader?
My phone came from warranty,downgraded hboot with htcdev+alpharevx, now I must go to stock again because I need to send it again, did the whole thing but the bootloader says "relocked"
skinniezinho said:
Guys just a quick question.
Is any way to remove the "relocked" status of the bootloader?
My phone came from warranty,downgraded hboot with htcdev+alpharevx, now I must go to stock again because I need to send it again, did the whole thing but the bootloader says "relocked"
Click to expand...
Click to collapse
The only way is to load a stock RUU/ROM that has bootloader 1.13. If you have a ROM that uses HBOOT 2.00-2.02 then it will always show RELOCKED or UNLOCKED.
tpbklake said:
The only way is to load a stock RUU/ROM that has bootloader 1.13. If you have a ROM that uses HBOOT 2.00-2.02 then it will always show RELOCKED or UNLOCKED.
Click to expand...
Click to collapse
do you know wich one is it?for wwe phone.
skinniezinho said:
do you know wich one is it?for wwe phone.
Click to expand...
Click to collapse
wwe -> 2.30.405.1
Hey guys I badly need help!!! I was able to convert my HTC One GSM to Google Edition just last week, but today I want to restore it to its factory ROM so I can also restore the warranty. Now the problem became visible when I tried to flash a stock ROM (not the GPE ROM). Listed below are the problems I am facing at the moment:
1. Stuck in FASTBOOT USB, and cannot boot to ROM.
2. Can't boot to recovery. Everytime I highlight and select recovery the phone just shows up the "Google" logo, then vibrates, then back fastboot USB.
3. Factory Reset not working, again shows up "Google" then restarts to fastboot usb mode.
4. I ran cmd in sdk-tools, typed in "fastboot devices", and my phone is detected. But when I type "adb devices", my phone is not listed.
5. I tried flashing CWM or TWRP through fastboot in cmd but the reply is"remote: signature verify fail", as wellas flashing a RUU for my device.
6. On bootloader is written:
*** TAMPERED ***
*** RELOCKED ***
M7_UK PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v30.120.3274.0520
OS-2.14.1700.15
eMMC-boot 2048MB
Guys I really badly need help to fix my phone. I don't wanna spend for repairs or throw it in the garbage. I am very sure there's a way to fix this and get it to work, but I am rookie in android as I've been an iOs user for a couple of years.
ClydeWinux said:
Hey guys I badly need help!!! I was able to convert my HTC One GSM to Google Edition just last week, but today I want to restore it to its factory ROM so I can also restore the warranty. Now the problem became visible when I tried to flash a stock ROM (not the GPE ROM). Listed below are the problems I am facing at the moment:
1. Stuck in FASTBOOT USB, and cannot boot to ROM.
2. Can't boot to recovery. Everytime I highlight and select recovery the phone just shows up the "Google" logo, then vibrates, then back fastboot USB.
3. Factory Reset not working, again shows up "Google" then restarts to fastboot usb mode.
4. I ran cmd in sdk-tools, typed in "fastboot devices", and my phone is detected. But when I type "adb devices", my phone is not listed.
5. I tried flashing CWM or TWRP through fastboot in cmd but the reply is"remote: signature verify fail", as wellas flashing a RUU for my device.
6. On bootloader is written:
*** TAMPERED ***
*** RELOCKED ***
M7_UK PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.33250.14
OpenDSP-v30.120.3274.0520
OS-2.14.1700.15
eMMC-boot 2048MB
Guys I really badly need help to fix my phone. I don't wanna spend for repairs or throw it in the garbage. I am very sure there's a way to fix this and get it to work, but I am rookie in android as I've been an iOs user for a couple of years.
Click to expand...
Click to collapse
try flashing the appropriate firmware files for an particular RUU before flashing RUU n check?
Harish_Kumar said:
try flashing the appropriate firmware files for an particular RUU before flashing RUU n check?
Click to expand...
Click to collapse
Yes I have tried flashing the appropriate RUU file but in CMD it returns "remote: signature verify fail"
ClydeWinux said:
Yes I have tried flashing the appropriate RUU file but in CMD it returns "remote: signature verify fail"
Click to expand...
Click to collapse
not RUU...i am talking about firmware files
for instance if you are about to flash an 4.3 sense 3.22 rom..flash its firmware in RUU mode before flashing the actual RUU
Harish_Kumar said:
not RUU...i am talking about firmware files
for instance if you are about to flash an 4.3 sense 3.22 rom..flash its firmware in RUU mode before flashing the actual RUU
Click to expand...
Click to collapse
Oh my, are the firmware files included inside the RUU.zip? or should I download the firmware files separately? @Harish_Kumar
ClydeWinux said:
Oh my, are the firmware files included inside the RUU.zip? or should I download the firmware files separately? @Harish_Kumar
Click to expand...
Click to collapse
RUU Zip will be encrypted..you cant extract files from it
you have to download firmware files seperately...you can find them in android development section
check here -> http://forum.xda-developers.com/showthread.php?t=2182823
I almost forgot... you should be S-off in order to flash the firmware
and even RUU Flashing requires S-off
Harish_Kumar said:
RUU Zip will be encrypted..you cant extract files from it
you have to download firmware files seperately...you can find them in android development section
check here -> http://forum.xda-developers.com/showthread.php?t=2182823
I almost forgot... you should be S-off in order to flash the firmware
and even RUU Flashing requires S-off
Click to expand...
Click to collapse
Ok I have flashed the firmware for my phone and now it's on 3.58.1700.5. Should I download a RUU.zip version 3.58.1700.5 and flash it on my phone? because until now I can't flash CWM or TWRP. @Harish_Kumar
ClydeWinux said:
Ok I have flashed the firmware for my phone and now it's on 3.58.1700.5. Should I download a RUU.zip version 3.58.1700.5 and flash it on my phone? because until now I can't flash CWM or TWRP. @Harish_Kumar
Click to expand...
Click to collapse
arent you able to flash custom recovery like CWM or TWRP even after flashing firmware files? if everything's right you should be able to
56562336461
Harish_Kumar said:
arent you able to flash custom recovery like CWM or TWRP even after flashing firmware files? if everything's right you should be able to
Click to expand...
Click to collapse
Everytime I tried to flash custom recovery (CWM/TWRP) in cmd it returns "remote: signature verify fail", I used command "fastboot flash recovery cwm.img". And now I tried to load up recovery from menu, and it's stuck on a 'dead-android-icon-with-exclamation-error' logo. @Harish_Kumar
I want to return to stock so I can take an OTA. I am currently running Sprint 4.3, rooted, unlocked bootloader, S-ON, software version 3.04.651.2.
I have been reading up on the proper way to return to stock and just want to double check that I have the right information before i break something.
1. Download 3.04.651.2 RUU (or do I want 4.06.651.4 or 4.06.651.2?)
2. USB debugging turned on
3. nandriod
4. go into fastboot
5. Connect phone to computer and go to Andriod SDK folder platform-tools and open a command window
6. type fastboot oem lock in the command window
7. go back to fastboot and run the RUU (how exactly do I run the RUU?)
8. Am I done now? Will these steps give me the stock rom, locked bootloader and stock recovery?
is this how I flash the RUU from the command window?
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip (if filename = firmware.zip)
Fastboot reboot
Thanks for the clarification.
Kev1jm2 said:
I want to return to stock so I can take an OTA. I am currently running Sprint 4.3, rooted, unlocked bootloader, S-ON, software version 3.04.651.2.
I have been reading up on the proper way to return to stock and just want to double check that I have the right information before i break something.
1. Download 3.04.651.2 RUU (or do I want 4.06.651.4 or 4.06.651.2?)
2. USB debugging turned on
3. nandriod
4. go into fastboot
5. Connect phone to computer and go to Andriod SDK folder platform-tools and open a command window
6. type fastboot oem lock in the command window
7. go back to fastboot and run the RUU (how exactly do I run the RUU?)
8. Am I done now? Will these steps give me the stock rom, locked bootloader and stock recovery?
is this how I flash the RUU from the command window?
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip (if filename = firmware.zip)
Fastboot reboot
Thanks for the clarification.
Click to expand...
Click to collapse
If you have a (S-ON) device you can go to OMJ's thread and run the RUU.exe for instructions:
http://forum.xda-developers.com/showthread.php?t=2658910
read the instructions under the image on the page...
If you want to flash the modified firmware you need (S-OFF), then you would follow these instructions:
I downloaded 4.06.651.4..
then renamed 4.06.651.4.zip to "firmware.zip"..
then moved firmware.zip to 'where-ever fastboot & adb are installed'..
then open command prompt in that folder..
then rebooted to bootloader..
plug phone through USB port, phone should say FASTBOOT USB
cmd: "fastboot oem rebootRUU" (without quotes of course)
cmd: "fastboot flash zip firmware.zip"
cmd: "fastboot reboot" (to reboot)
Hope this helps!
predator1584 said:
If you have a (S-ON) device you can go to OMJ's thread and run the RUU.exe for instructions:
http://forum.xda-developers.com/showthread.php?t=2658910
read the instructions under the image on the page...
If you want to flash the modified firmware you need (S-OFF), then you would follow these instructions:
I downloaded 4.06.651.4..
then renamed 4.06.651.4.zip to "firmware.zip"..
then moved firmware.zip to 'where-ever fastboot & adb are installed'..
then open command prompt in that folder..
then rebooted to bootloader..
plug phone through USB port, phone should say FASTBOOT USB
cmd: "fastboot oem rebootRUU" (without quotes of course)
cmd: "fastboot flash zip firmware.zip"
cmd: "fastboot reboot" (to reboot)
Hope this helps!
Click to expand...
Click to collapse
The OMJ thread says its for 4.06.651.4. I have 3.04.651.2. Is that a problem or can I still use it?
Kev1jm2 said:
The OMJ thread says its for 4.06.651.4. I have 3.04.651.2. Is that a problem or can I still use it?
Click to expand...
Click to collapse
The 4.06.651.4 RUU is the same as taking the OTA but...it will wipe your device
I would suggest getting s-off before you go any further it will save you headaches down the road.
Kev1jm2 said:
The OMJ thread says its for 4.06.651.4. I have 3.04.651.2. Is that a problem or can I still use it?
Click to expand...
Click to collapse
no luck with the s-off way. got a file size error in cmd. trying the s-on version now.
Nope, got another error. Something about using an incorrect ruu. Bootloader is locked now though...And now its unlocked again. going to try OMJ's tool with the 3.04.651.2 ruu
OMJ's tool worked when my software version matched the tool's version. getting the OTA now. Apparently you cant jump software versions.
Thanks for your help.
Kev1jm2 said:
no luck with the s-off way. got a file size error in cmd. trying the s-on version now.
Nope, got another error. Something about using an incorrect ruu. Bootloader is locked now though...And now its unlocked again. going to try OMJ's tool with the 3.04.651.2 ruu
OMJ's tool worked when my software version matched the tool's version. getting the OTA now. Apparently you cant jump software versions.
Thanks for your help.
Click to expand...
Click to collapse
I did not have to relock my phone to RUU it for a repair at HTC. If you run into trouble just reapply your token.bin file to re unlock dev mode and try again. I agree though S-OFF is the way to go if you can sort it out.
hi all
i was tried to flash my M7 from 4.3 to 4.4.2
downloaded the OTA update 4.19.401.7
contained :
DATA
META-INF
PATCH
System
Firmware.zip
Fotaboot
Skin_fota
the wrong step is : extracted the Firmware.zip file only
and flashed it only by :
fastboot oem rebootRUU
fastboot flash zip firmware.zip
now the phone is bricked, only boot to the HTC logo and black screen
when i try to press power bottom, the (Back & Home) led blinking
i was boot to bootloader and copy this information to you :
***LOCKED***
M7_UL PVT SHIP S-ON
HBOOT-1.56.0000 (it was 1.55 before)
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-4.19.401.9 (it was 3.62.401.1)
eMMC-boot 2048MB
Feb 7 2014,01:06:01.0
i was try to rename the OTA file to Firmware.zip and flash it again, but always failed
i was try to flash downgrade Firmware (3.62.401.1) also failed
i was try to flash RUU.exe (1.28.401.7) from the Fastboot screen and from the rebootRUU screen also failed
i was try to wipe and re-flash the same Firmware.zip file, it's flashed with no failed steps, but still bricked and no system to boot into
can you help me ?
My suggestion:
You are acting nervous, don´t know, from where you got the solutions you´ve tried. Your phone is not bricked if you have access to your bootloader as you wrote but yo can´t flash the needed things with a locked bootloader. Would be better to ask before every step, if you don´t know what to do.
1st you can send your device to HTC for repair...i think you have to pay for that
or 2nd (read and think about the warranty):
Unlock your bootloader via HTC.Dev. http://www.htcdev.com/devcenter
With locked bootloader it won´t run. If you have access to your bootloader, you are able to flash a recovery via Fastboot-USB and have access to adb. With S-On you can´t run the RUU you´ve tried, because you can´t downgrade your phone. S-Off would be the solution, but at the moment you can´t get it with your high HBoot version.
I think, the correct firmware is ready on your phone and you should
- unlock your bootloader with your Unlock_code.bin from HTC.Dev, flash it via Fastboot-USB fastboot flash unlocktoken Unlock_code.bin, accept the message on your phone, then
- flash TWRP 2.6.3.3 m7 recovery via fastboot, fastboot erase cache then fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
- sideload Maximus Rom or ARHD 52.0 via adb in recovery adb sideload HTC_One_-_MaximusHD_32.0.0.zip (if other rom, you have to replace the correct filename of the zip)
- or sideload the stock odexed rom 4.19.401.9 from the same download area at ARHD for the One
- check the MD5 sum before sideload! http://www.flashplayerpro.com/MD5Checksum/downloadMD5Checksum.htm
(even saw, the links of ARHD are down at the moment - the server problems of mike 1986 are not gone. Try it tomorrow or read the last sites of the thread to find alternative links),
- wipe data, system, dalvik cache and cache in recovery (not sd card)
- install the rom.zip via recovery, reboot into bootloader and
- flash the boot.img copied out of the rom via fastboot. fastboot erase cache then fastboot flash boot boot.img then fastboot erase cache
Then your device hopefully will boot again.
If the steps of flashing roms with TWRP are after reading this not really known, read the FAQ before.
If you are able to go to bootloader then give it a try. Unlock bootloader then try to flash firmware.
Sent from my HTC One using xda app-developers app
manishvy said:
If you are able to go to bootloader then give it a try. Unlock bootloader then try to flash firmware.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Correct me if i'm wrong but with S-ON you need the bootloader to be locked/re-locked to flash the firmware.zip
alray said:
Correct me if i'm wrong but with S-ON you need the bootloader to be locked/re-locked to flash the firmware.zip
Click to expand...
Click to collapse
Dont care about anything.. just goto HTC dev website, follow the steps and unlock the boot loader and flash the firmware..
alray said:
Correct me if i'm wrong but with S-ON you need the bootloader to be locked/re-locked to flash the firmware.zip
Click to expand...
Click to collapse
naresh_r said:
Dont care about anything.. just goto HTC dev website, follow the steps and unlock the boot loader and flash the firmware..
Click to expand...
Click to collapse
alray is correct mate! with S-On you need to have bootloader locked/relocked to be able to flash anything in ruu mode.
moha_moha20106 said:
hi all
i was tried to flash my M7 from 4.3 to 4.4.2
downloaded the OTA update 4.19.401.7
can you help me ?
Click to expand...
Click to collapse
OP, didn't we agree that you were going to wait??
I'm not entirely sure if stock recovery will read an OTG cable + stick, but worth a try:
if you haven't unlocked yet, get yourself an OTG cable + stick, put the OTA.ZIP (yes all of it, not just firmware), on the stick. connect it to your phone, and reboot into stock recovery, then press POWER + VOLUP (and hope it sees the otg), and use the "apply from sdcard" option to install the OTA.
Neo XL said:
My suggestion:
You are acting nervous, don´t know, from where you got the solutions you´ve tried. Your phone is not bricked if you have access to your bootloader as you wrote but yo can´t flash the needed things with a locked bootloader. Would be better to ask before every step, if you don´t know what to do.
1st you can send your device to HTC for repair...i think you have to pay for that
or 2nd (read and think about the warranty):
Unlock your bootloader via HTC.Dev. http://www.htcdev.com/devcenter
With locked bootloader it won´t run. If you have access to your bootloader, you are able to flash a recovery via Fastboot-USB and have access to adb. With S-On you can´t run the RUU you´ve tried, because you can´t downgrade your phone. S-Off would be the solution, but at the moment you can´t get it with your high HBoot version.
I think, the correct firmware is ready on your phone and you should
- unlock your bootloader with your Unlock_code.bin from HTC.Dev, flash it via Fastboot-USB fastboot flash unlocktoken Unlock_code.bin, accept the message on your phone, then
- flash TWRP 2.6.3.3 m7 recovery via fastboot, fastboot erase cache then fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
- sideload Maximus Rom or ARHD 52.0 via adb in recovery adb sideload HTC_One_-_MaximusHD_32.0.0.zip (if other rom, you have to replace the correct filename of the zip)
- or sideload the stock odexed rom 4.19.401.9 from the same download area at ARHD for the One
- check the MD5 sum before sideload! http://www.flashplayerpro.com/MD5Checksum/downloadMD5Checksum.htm
(even saw, the links of ARHD are down at the moment - the server problems of mike 1986 are not gone. Try it tomorrow or read the last sites of the thread to find alternative links),
- wipe data, system, dalvik cache and cache in recovery (not sd card)
- install the rom.zip via recovery, reboot into bootloader and
- flash the boot.img copied out of the rom via fastboot. fastboot erase cache then fastboot flash boot boot.img then fastboot erase cache
Then your device hopefully will boot again.
If the steps of flashing roms with TWRP are after reading this not really known, read the FAQ before.
Click to expand...
Click to collapse
Dear , i will send my phone to the HTC Maintenance center and ask them to resolve it with my warranty
if i UNLOCK my phone and S-OFF , i think i will loose my 9months warranty
if they told my the problem is by you (me), i will ask them to maintain it and pay money
thank you very much
nkk71 said:
alray is correct mate! with S-On you need to have bootloader locked/relocked to be able to flash anything in ruu mode.
OP, didn't we agree that you were going to wait??
I'm not entirely sure if stock recovery will read an OTG cable + stick, but worth a try:
if you haven't unlocked yet, get yourself an OTG cable + stick, put the OTA.ZIP (yes all of it, not just firmware), on the stick. connect it to your phone, and reboot into stock recovery, then press POWER + VOLUP (and hope it sees the otg), and use the "apply from sdcard" option to install the OTA.
Click to expand...
Click to collapse
Dear, i'm sorry for that
yes, we agreed before for waiting...
but the HTC MEA always lier
i was try to connect the OTG cable, but the bootloader didn't read it, i think the OTG function is by system, not by bootloader
thank you very much dear