Related
Initially I was running stock froyo 2.2.1 and 2.28xxx Radio and it was running fine with the below mentioned hboot info
my bootloader info is something like
Blackrose
vivo pvt ship s-off rl
radio-3805.04.03.27_m
eMMC-boot
june 02 2012. 00:00:54
I then flashed a different radio version (corresponding to Froyo ROM) but after that It continously boot loop .
I can only enter into hboot and fastboot etc menus but cannot go to recovery anymore. when i go to recovery it again starts boot loop.
I unlocked and s-offed hboot an year back and i hardly remember those methods and my memory card is changed recently.
I tried flashing recovery using fastboot but problem persists. Still no recovery.( previously ClockwoodMod )
I have stock rom backup so once i can get into clockwood recovery i can restore those settings. Please help me out Guys . I did a huge mistake coming into custom roms after 1 year . lost all info .Now i'm pretty confused with all those terms and methods.
The only option is to flash recovery image. This is the reason you are not able to get into recovery.
What is the command you are using to flash recovery image?
Try to flash recovery image again.
Don't worry your phone is not bricked.
Sent from my HTC Incredible S using xda app-developers app
@di said:
The only option is to flash recovery image. This is the reason you are not able to get into recovery.
What is the command you are using to flash recovery image?
Try to flash recovery image again.
Don't worry your phone is not bricked.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
1.on a freshly installed win 7 - 64 bit
2.installed java working
3.installed android-sdk installer_r20.0.3-windows.exe
4.opened sdk manager and installed platform tools
5.downloaded cwm recovery image and placed it in the platform tools folder
6.open cmd and inside platform tools folder
7.conned htc in fastboot mode and it showed fastboot usb after connecting
8.i typed follwing commands
fastboot flash recovery cwm-4.0.1.4.img
sending ' recovery ' <3700 kb>....
OKAY [1.150s]...
writing 'recovery'...
OKAY [0.799s]...
finished total time 1.947s
the fastboot usb in mobile stayed the same and i rebooted into hboot and went recovery . It rebooted into htc logo and boot loop continous . dint see any recovery. Where have i done wrong ? .. do i need any specific HTC Incredible S drivers for the PC ? ... what should i do now ? ...otherwise can i flash any ROM directly from fastboot usb mode ?
Thank you very much bro .. please help me out ..
What is your hboot version? 2.02.002?
Did you try flashing boot.IMG also?
If not then try that also...
Sent from my HTC Incredible S using xda app-developers app
@di said:
What is your hboot version? 2.02.002?
Did you try flashing boot.IMG also?
If not then try that also...
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
yes hboot version is 2.02. and which boot.img ? i dont get u .. of any ROM ?
Try a more recent recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vivo.img
and erase cache in fastboot
Code:
fastboot erase cache
Nonverbose said:
Try a more recent recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vivo.img
and erase cache in fastboot
Code:
fastboot erase cache
Click to expand...
Click to collapse
i tried the recent recovery image too but still it boots the moment it shows HTC logo( 2 secs logo and boot ) ... going to recovery after flashing also does the same boot loop. Do i need any adb drivers to detect vivo specifically ? .. i installed htc sync but dint connect vivo after that (when incS was actually working ).
also flashing boot.img from backed up froyo rom says FAILED writing. Battery is draining out on the otherside . It goes to boot loop when i charge it switched off too.
BTW Like i said I was running froyo stock rom which was also restored from backup but when i flashed the Radio maybe md5 or something dint match up and the firmware got corrupted . there's any bruteforce method to flash a custom or stock ROM or RUU ? ... I tried flashing nik_auro sense _4a ROM in fastboot usb but it says FAILED writing ! ... Can i solve this ? or my device is gone forever ?
I flashed boot.img of the backed up clockworkmod backup (froyo)
fastboot flash boot boot.img
it says
OKAY
Writing 'boot.img'
Finished.
Then i flashed recovery again
it says OKAY
Writing
Finished.
But same problem no difference.
BTW Everytime the usb is connected while booting up and al ... Windows 7 says USB driver not recognized ... ?? but flashing actually shows in cmd and hboot !!
You should install the driver correctly. Install htcsync and then uninstall it. Try flashing the recovery again. If that doesn't work, go into fastboot mode and type
Code:
fastboot getvar all
and post result here minus imei and serial number so we can get an ruu for you to flash.
boot loop
1.Exact boot loop time from vibration : 5 secs
2.i removed and reinstalled HTC Sync application but then it says
It popped up " HTC Sync Driver installed " when I went to Fastboot USB mode first time but also says
"USB Device not recognized . one of the USB devices attached to this has Malfunctioned . click for assistance " when connected in HBOOT mode as well as normal boot loop.
3.Tried flashing latest CWM recovery again and boot.img of backed up file. but still no difference .
4.IMEI and serial u mean the one in this below screenshot right ?
5.Previously i was on Codename Jellybean ROM and it worked fine then i wanted to get back to stock so i restored previous stock back up and it worked fine too and when i flashed this Froyo radio after which this problem started ( last froyo radio in the list )
Radio : From the 1.47.1400.3 RUU:
20.28.30.0802U_38.04.01.07
md5: eb83213f5a093a7baf7571409c9c2498
other info:
Blackrose
HBOOT 2.02.0002
Radio - 3805.04.03.27_M
jun 02 2012
I sent you PM, but it's nice to know that most problems connected to recoveries, boot.imgs and permissions get fixed with RUU. Of course it's easiest for s-off users (Revolutionary and BlackRose) cause all they need is to run RUU, and their phone will stay s-off and hboot won't be touched. For Alpharev and HTC unlocked users it's a bit different, Alpharev will lose their s-off cause hboot will be overwritten, and HTC unlocked have to relock their bootloader before RUU.
After successful RUU:
-S-off user have to flash recovery via fastboot
-HTC unlocked, so as Alpharev, have to unlock bootloader again (Alpharev for the first time) and flash recovery
The rest is magic...
Also, remember that flashing Froyo radio can cause you leaving with an expensive construction material (a hard brick)...
EDIT:
As I understood the last RUU is the same for all regions (same ruu.exe inside package One_Generic_code_Vivo.zip), so no need for gold cards anymore and the rest is handled with RUU itself. I already experienced that with Desire's 2.3 RUU.
n4naveen said:
1.Exact boot loop time from vibration : 5 secs
2.i removed and reinstalled HTC Sync application but then it says
It popped up " HTC Sync Driver installed " when I went to Fastboot USB mode first time but also says
"USB Device not recognized . one of the USB devices attached to this has Malfunctioned . click for assistance " when connected in HBOOT mode as well as normal boot loop.
3.Tried flashing latest CWM recovery again and boot.img of backed up file. but still no difference .
4.IMEI and serial u mean the one in this below screenshot right ?
5.Previously i was on Codename Jellybean ROM and it worked fine then i wanted to get back to stock so i restored previous stock back up and it worked fine too and when i flashed this Froyo radio after which this problem started ( last froyo radio in the list )
Radio : From the 1.47.1400.3 RUU:
20.28.30.0802U_38.04.01.07
md5: eb83213f5a093a7baf7571409c9c2498
other info:
Blackrose
HBOOT 2.02.0002
Radio - 3805.04.03.27_M
jun 02 2012
Click to expand...
Click to collapse
The last official Rom you had installed on your phone was not froyo, that may be why you're getting bootloops. You're actually extremely lucky you didn't get bricked but it seems only the phones shipped with gingerbread have that issue. Your main version shows you had a HK 2.3.3 ruu installed but that doesn't match your cid (india). Do you have a goldcard?
Try flashing a gb radio. That will likely fix your issue.
Here's the ruu matching your main version. http://www.filefactory.com/file/c0a...5AU_3805.04.03.27_M_release_189979_signed.exe
Nonverbose said:
The last official Rom you had installed on your phone was not froyo, that may be why you're getting bootloops. You're actually extremely lucky you didn't get bricked but it seems only the phones shipped with gingerbread have that issue. Your main version shows you had a HK 2.3.3 ruu installed but that doesn't match your cid (india). Do you have a goldcard?
Try flashing a gb radio. That will likely fix your issue.
Here's the ruu matching your main version. http://www.filefactory.com/file/c0a...5AU_3805.04.03.27_M_release_189979_signed.exe
Click to expand...
Click to collapse
Main version shows HK because i might've installed it before jellybean version or i also flashed GB boot.img after boot loop problem .
India is correct . My original ROM came with mobile is froyo in india .I have the back up of this Froyo ROM but dont know the exact RUU details . I have goldcard but it was made with another SDCARD dont know if that works with new SDCARD ...
Is it ok to flash this rom in fastboot usb mode for my mobile ?
ROM : HTC RUU Latin american version 4.14.405.2 ? ( it has file named One_generic_code_viva.zip) actually i need asia RUU but that link has incomplete file.
Mobile details : http://dl.xda-developers.com/attach...f7c459e3/50857d5a/1/4/1/9/7/4/1/vivo-info.jpg
I tried to flash HTC Canadian RUU(one_generic_code_vivo.zip ) in fastboot usb since i required asian RUU was a broken file in the link. ROM Update utility started , it identified my firmware version/ hboot so on .. like something like 2.12.xx to update latest 4.14.x so on .. but when i started to flash .. it started to show progress bar 1% .. but then immediately it changed to ----sending--- Bar(on PC) ......... (on mobile screen it showed HTC with black background without any progress bar ) it kept showing sending for 30 mins then i removed it and nothing flashed . same boot loop yet. any comments ? ... do i have to lock bootloader before flashing stock RUU ?... or can i flash a custom ROM ? ... I've no idea whats going on .. this is my device info http://www.4shared.com/photo/bgN6aHfQ/vivo-info.html?
It doesn't look like you flashed the gb radio like I suggested. Or even the ruu that I linked. You cannot flash a Canadian ruu because of the fact its a different model id.
Nonverbose said:
It doesn't look like you flashed the gb radio like I suggested. Or even the ruu that I linked. You cannot flash a Canadian ruu because of the fact its a different model id.
Click to expand...
Click to collapse
How am i supposed to flash the RUU which u gave ? cos none of these methods work ...
from PC in fastboot usb ... The rom update utility keeps showing sending ........ and on mobile HTC black screen logo without a progess bar .. i waited for 30 mins.
I made PG32IMG.zip and added my CID in android-txt file and placed it on SDCARD ... in Hboot mode it loaded the file ... showed parsing--for 1/10th of a sec and gone and the red progress bar dint appear. and the writing dint happen.
I extracted the rom.zip from RUU and flashed in fastboot flash zip file-name.zip . it says sending....and then stopped REMOTE : not allowed !
I also fastboot usb flashed 3805.4.03.27 radio of GB of my main version ... says the same error REMOTE : not allowed !
Ok, to cut all this nonsense, since you have blackrose you should be able to run any ruu cause it disables cid checking, but it, obviously, doesn't work for you.
Just flash newest radio via fastboot and install some custom rom.
nlooooo said:
Ok, to cut all this nonsense, since you have blackrose you should be able to run any ruu cause it disables cid checking, but it, obviously, doesn't work for you.
Just flash newest radio via fastboot and install some custom rom.
Click to expand...
Click to collapse
Not entirely true but thanks anyway.
boot loop
nlooooo said:
Ok, to cut all this nonsense, since you have blackrose you should be able to run any ruu cause it disables cid checking, but it, obviously, doesn't work for you.
Just flash newest radio via fastboot and install some custom rom.
Click to expand...
Click to collapse
I flashed the Latest GB Radio . says REMOTE : NOT ALLOWED)
I flashed CUstom ZIP nik_rebirth says REMOTE : NOT ALLOWED
it pretty much says the same except for cwm backed up boot.img
I flashed boot.img and it was written !!
I also changed modelid , cidnum , mainversion hbootpreupdate values same as my device details before flashing some GB radio and latest generic rom.zip but all it says is REMOTE : NOT ALLOWED !!
commands im using
fastboot flash zip PG32IMG.zip
fastboot flash zip rom-name.zip
fastboot flash boot boot.img
other conditions :
Cable is not the one provided by HTC
battery is around 10% now 3722mV
sdcard is not the goldcarded sdcard but i have the goldcard file with me.
below are the images before applying Blackrose HBOOT and running GB successfully
Hi guys,
My phone is S-off and I recently reset the locked flag on my phone using this method: http://forum.xda-developers.com/showthread.php?t=2475914. I changed my cid back to stock and then flashed a stock RUU.
Today I got my phone back and want to unlock it again but have been running into problems. The first thing I did was change back to supercid 11111111 which was fine. Now I need to have SuperSU to run the commands from the thread above to unlock, but the only way to install SuperSU is by flashing through recovery. I can't seem to get the recovery to flash via fastboot. Everytime I get the error FAILED <remote: not allowed>.
I then tried to flash from the rebootRUU screen using the method from this thread: http://forum.xda-developers.com/showthread.php?t=2441299 but I get the error FAILED <remote: 41 model id check fail>.
I'm not sure what to do now, any help would be really appreciated!
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
misterasset said:
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
Click to expand...
Click to collapse
You've had an htc one for two years?
BableMan said:
You've had an htc one for two years?
Click to expand...
Click to collapse
No. Started out with my Nexus S, then moved to a Nexus 4, then gave that to my wife and got an HTC One. I love this phone so much I wish I'd had it for two years already, but no.
Do you have any idea of a new path I can try?
misterasset said:
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
Click to expand...
Click to collapse
Just to know.. Did you try to flash a RUU.exe or a RUU.zip? I had a lot of problems with the .exe files, while flashing the RUU.zip from command line usually work like a charm to me.
Sent from my HTC One using Tapatalk
Delgra said:
Just to know.. Did you try to flash a RUU.exe or a RUU.zip? I had a lot of problems with the .exe files, while flashing the RUU.zip from command line usually work like a charm to me.
Click to expand...
Click to collapse
I have tried both actually. I used Hansoon2000's (I'm at work so hopefully I'm referencing that correctly) all in one toolkit to try to flash the RUU.zip file back to the device. It fails while transferring to the device every single time.
So next I tried to use the RUU.exe, both a newer and older version, for my CID and I get the mysterious Error 155 Unknown Error.
How do I flash the RUU.zip from the command line? I have tried using "Install zip from sideload" but I get a Status Error 7 when trying to flash ROM.zip files, and I have tried using ADB PUSH to push the ROM.zip over to the phone but since there's no file structure it doesn't really ever end up anywhere on the phone. (I'm using ROM.zip generically here for my CM ROMs, not RUU) Is there a command line or ADB function to flash the RUU.zip file that I'm not aware of?
Thanks,
Chris
misterasset said:
So next I tried to use the RUU.exe, both a newer and older version, for my CID and I get the mysterious Error 155 Unknown Error.
Thanks,
Chris
Click to expand...
Click to collapse
Error 155 -> you're probably on hboot 1.55+, so you need to downgrade hboot separately first, (to hboot 1.44) then you can run the RUU. download here: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot reboot-bootloader
-> confirm hboot is 1.44
and run RUU.
PS: you have to be s-off obviously.
nkk71 said:
Error 155 -> you're probably on hboot 1.55+, so you need to downgrade hboot separately first, (to hboot 1.44) then you can run the RUU. download here: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot reboot-bootloader
-> confirm hboot is 1.44
and run RUU.
PS: you have to be s-off obviously.
Click to expand...
Click to collapse
Thanks for the info. I'm actually on HBOOT 1.44 already luckily. But I am not S-Off. Is that why the RUU is not working? I tried to use the All-In-One Toolkit to achieve S-Off now, but without a file structure it didn't work.
Any direction on achieving S-Off while it's so messed up?
Thanks,
Chris
misterasset said:
Thanks for the info. I'm actually on HBOOT 1.44 already luckily. But I am not S-Off. Is that why the RUU is not working? I tried to use the All-In-One Toolkit to achieve S-Off now, but without a file structure it didn't work.
Any direction on achieving S-Off while it's so messed up?
Thanks,
Chris
Click to expand...
Click to collapse
Please:
1- date of bootloader
2- a "fastboot getvar all" (remove IMEI and s/n)
3- link to the RUU you are trying to use.
Don't forget pressing the little thanks button for people who have helped
No offense but it sounds as if you simply aren't running an ruu.zip correctly. I'm not understanding all this hensonn2000 or toolkit talk that you have going on. You flash ruu.zip while the phone is in fastboot oem RUU mode. Not that complicated. Also the error 155 was the bootloader being unlocked if I recall correctly. You have to relock it before flashing or running the appropriate RUU. Specially if youre s-on.
Thanks guys. I ended up getting it all working. I did not have the Bootloader relocked and that was why the RUU kept failing.
Thanks again for the extra direction,
Chris
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
*UPDATE* - Sorry, forgot to mention that I've idiotically re-locked the bootloader. Unlocking the bootloader would probably get rid of the "signature verify fail" message. I'm unable to flash the recovery because the bootloader is locked and I can't get into the filesystem because the phone needs to go into the OS for that.
When I try to unlock the bootlader by using "fastboot flash unlocktoken Unlock_code.bin" it gives me the error: "cannot open 'Unlock_code.bin'."
I need to be able to access and make changes to the file system by using fastboot commands and I have no idea how to do this.
*UPDATE #2* - I've managed to re-unlock the bootlader (I didn't have the Unlock_code.bin file in the same directory as the current directory in my cmd window). I've re-flashed the recovery successfully. Now when I reboot, it goes into recovery mode (still can't boot into the OS). I'm using ClockWorks for the recovery.
Now I'm unable to root the phone. I'm trying to write SuperSU v1.65 to the phone by using the command: "fastboot flash zip UPDATE-SuperSU-v1.65.zp" and I get the error message: "remote: not allowed."
I can flash the recovery.img and boot.img (can't flash system.img because there's "not enough space"), but I can't flash .zip files
When I try flashing another boot.img, I still get the same thing. The phone goes to the boot screen and can't boot. Then, it reboots and goes automatically into recovery (I can still get into the bootloader and recovery).
Any suggestions to get past these permissions?
bkhosh2 said:
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
Click to expand...
Click to collapse
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
superbellefleche said:
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
Click to expand...
Click to collapse
I'm sorry, but I'm kind of a noob. How exactly do I re-flash a recovery. do I do this using the command: "fastboot flash recovery recovery.img" or should I try "fastboot flash zip filname.zip" (RUU.zip) again?
*UPDATE* - I've tried erasing the cache and re-flashing the recovery and I still get the error message: "signature verify fail."
I'm still waiting for someone to help me. Is anyone going to help me fix my problem or is my HTC One doomed?
If you are on Telus
Download http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
SaHiLzZ said:
If you are on Telus
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
Click to expand...
Click to collapse
I've already tried that. When the bootloader is locked, I get the error: "signature verify fail."
OK.. Unlock bootloader, flash custom recovery, adb push this file: http://www.htc1guru.com/2013/11/guru-reset-3-22-661-1/, and install it from recovery.
SaHiLzZ said:
OK.. Unlock bootloader, flash custom recovery, adb push this file
Click to expand...
Click to collapse
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
bkhosh2 said:
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
Click to expand...
Click to collapse
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
clsA said:
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Click to expand...
Click to collapse
I Installed the TWRP recovery instead of the ClockWorkMod and adb command work! Never using ClockWork ever again!
SaHiLzZ said:
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
Click to expand...
Click to collapse
I Installed TWRP and went into the TWRP recovery and noticed the adb commands work.
That file didn't work, however the Guru file you mentioned earlier did (with the "adb push" command)! Thanks so much for your help! Everything is working perfectly again!
Thanks for posting back. Edit your title to [SOLVED]! and enjoy!
I Have my HTC ONE m7 Dual Sim rom updated about 6 month ago.
1) Unlocked
2) S-Off with moonshine
3) ClockWork 3.0.3.x installed
4) MaximusHD 2 rom installed http://llabtoofer.com/2014/03/24/htc-one-dualsim-maximushd-2-0-0/
Recently I decided to update to MaximusHD 3 http://llabtoofer.com/2014/07/31/htc-one-dualsim-maximushd-3-0-0/
After using ClockWork to install the rom I've got an error 'set_metadata_recursive: some changes failed` and the OS wont load. http://android.stackexchange.com/qu...et-set-metadata-recursive-some-changes-failed
As they said I need to update ClockWork to the recent version so I followed that video http://www.youtube.com/watch?v=Wg6B659PBnk to update ClockWork with CVM script. But it won't work for me...
Then I spend a lot of time trying to install drivers on Windows 8.1 (I did it 6 month ago on my old Windows 7 PC but didn't have that any more... ) I didn't make drivers work on Windows 8.1.
So then finally I boot to MAC and install everything by following this video http://www.youtube.com/watch?v=V0MyTvgfO7s
After I install ClockWork via flashboot I've got very scary screen (http://forum.xda-developers.com/attachment.php?attachmentid=2973598&stc=1&d=1413487336)
Then after few seconds mobile trying to boot ClockWork (http://forum.xda-developers.com/attachment.php?attachmentid=2973599&stc=1&d=1413487336) and gets in to infinity loop (->boot OS->Boot ClockWork->) Only I can do is manually boot to bootloader by pressing "power button+vol down".
What would you suggest for me in such situation?
Currently I will be trying to install stock rom from here http://forum.xda-developers.com/showthread.php?t=2617159 using this article http://marrkdaviid.com/2013/11/retu...re-on-the-htc-one-dual-sim-802w/#.VD_36itgnEA it is only what I think I can do.
What do you think?
p.s
adb not working on Mac only I've got flashboot to work....
HeartKiller said:
I Have my HTC ONE m7 Dual Sim rom updated about 6 month ago.
1) Unlocked
2) S-Off with moonshine
3) ClockWork 3.0.3.x installed
4) MaximusHD 2 rom installed http://llabtoofer.com/2014/03/24/htc-one-dualsim-maximushd-2-0-0/
What would you suggest for me in such situation?
Currently I will be trying to install stock rom from here http://forum.xda-developers.com/showthread.php?t=2617159 using this article http://marrkdaviid.com/2013/11/retu...re-on-the-htc-one-dual-sim-802w/#.VD_36itgnEA it is only what I think I can do.
What do you think?
p.s
adb not working on Mac only I've got flashboot to work....
Click to expand...
Click to collapse
Try TWRP 2.8.0.2, I can not find an update to CWM for your phone.
On the MaximusHD site did you flash the firmware? I could not find the instructions but I would think you would need to flash the firmware first then the ROM especially since the ROM is based on that version.
There is a RUU.zip for your phone: PN07IMG_M7C_DUG_K44_SENSE60_MR_HTCCN_CHS_CU_5.15.1 402.3_Radio_1237.28.34.0106_release_373024_signed_ 2.zip. You will have to scroll down the site to find it but it is there and the RUU just prior to this version. RUU will normally reset your phone to stock but you will retain S-OFF and you don't have to lock the bootloader to run it, at least, that is the case for single SIM phones.
ADB will work in the boot OS with USB Debugging enabled or in Recovery. It will not work if the phone is in FASTBOOT USB.
majmoz said:
Try TWRP 2.8.0.2, I can not find an update to CWM for your phone.
On the MaximusHD site did you flash the firmware? I could not find the instructions but I would think you would need to flash the firmware first then the ROM especially since the ROM is based on that version.
There is a RUU.zip for your phone: PN07IMG_M7C_DUG_K44_SENSE60_MR_HTCCN_CHS_CU_5.15.1 402.3_Radio_1237.28.34.0106_release_373024_signed_ 2.zip. You will have to scroll down the site to find it but it is there and the RUU just prior to this version. RUU will normally reset your phone to stock but you will retain S-OFF and you don't have to lock the bootloader to run it, at least, that is the case for single SIM phones.
ADB will work in the boot OS with USB Debugging enabled or in Recovery. It will not work if the phone is in FASTBOOT USB.
Click to expand...
Click to collapse
Currently downloading the latest RUU that you mentioned.
Then I will unlock bootloader but then I might get an issue because I wont be able to use http://moonshine.io/ because ADB wont work on FASTBOOT USB that is required to install moonshine. Would ClockWork run without moonshine S-OFF?
HeartKiller said:
Currently downloading the latest RUU that you mentioned.
Then I will unlock bootloader but then I might get an issue because I wont be able to use http://moonshine.io/ because ADB wont work on FASTBOOT USB that is required to install moonshine. Would ClockWork run without moonshine S-OFF?
Click to expand...
Click to collapse
If you have been doing everything with moonshine S-OFF, then leave it. Run the RUU and you should be back where you want to be.
majmoz said:
If you have been doing everything with moonshine S-OFF, then leave it. Run the RUU and you should be back where you want to be.
Click to expand...
Click to collapse
Yeah but in order to install MaximusHD 3 I do need to unlock bootloader + to install moonshine S-OFF isn't it?
HeartKiller said:
Yeah but in order to install MaximusHD 3 I do need to unlock bootloader + to install moonshine S-OFF isn't it?
Click to expand...
Click to collapse
I guess I don't understand.
Why don't you unlock your bootloader using the HTCDev Method? It doesn't require adb.
Does moonshine S-OFF have some command in ADB to unlock your bootloader?
It is obvious that I don't know your phone but here is a [GUIDE] HTC Dual Sim 802w, 802t, 802d S-Off, Recovery, Updates 4.2.2, ROOT, Google that explains a lot of the issues.
Now I am getting error when trying to install latest RUU Firmware
.Getting error not able to install this:
PN07IMG_M7C_DUG_K44_SENSE60_MR_HTCCN_CHS_CU_5.15.1402.3_Radio_1237.28.34.0106_release_373024_signed_2.zip
./fastboot oem rebootRUU
/fastboot flash zip firmware.zip
sending 'zip' (1150783 KB)...
OKAY [ 46.761s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 49.531s
Was trying to download multiple times
But able to install this PN07IMG_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.39.1402.1_Radio_1237.25.32.0717_release_338991.zip
Why latest RUU failing?
UPDATE:
Bascally I reinstall correct latest ClockWork recovery and then I successfully Installed MaximusHD 3 rom.
Thank you everyone for help.