Hello everyone. I have a T-Mobile HTC One M7. I had Viper One installed on it and then decided to restore it to stock, and ship it to my lill bro in Europe. I accidentally wiped the whole system on the phone. Now it shows:
***Tampered***
***Relocked***
***Security Warning***
and I can only get into the bootloader and recovery modes. I am a noob when it comes to this. PLease help me put a stock system on my phone!!
Thank you much!!!
Shtehla said:
Hello everyone. I have a T-Mobile HTC One M7. I had Viper One installed on it and then decided to restore it to stock, and ship it to my lill bro in Europe. I accidentally wiped the whole system on the phone. Now it shows:
***Tampered***
***Relocked***
***Security Warning***
and I can only get into the bootloader and recovery modes. I am a noob when it comes to this. PLease help me put a stock system on my phone!!
Thank you much!!!
Click to expand...
Click to collapse
This is the latest RUU for your phone. Just follow the instructions on the page. The "Security Warning" may go away but the other two will more than likely remain.
Rom update utility gives me low battery error
I downloaded the RUU from the link u gave me. I made sure there's a usb driver in place, for my htc one. When i start the rom update thing, and i go through the "agree" and check boxes....the rom utility gives me error 120, saying that my main battery power is low (less than %30), though my phone is fully charged and my laptop is fully charged.... Please advice
Got past the battery error message
Shtehla said:
I downloaded the RUU from the link u gave me. I made sure there's a usb driver in place, for my htc one. When i start the rom update thing, and i go through the "agree" and check boxes....the rom utility gives me error 120, saying that my main battery power is low (less than %30), though my phone is fully charged and my laptop is fully charged.... Please advice
Click to expand...
Click to collapse
now I cant go past error 170 within the RUU instalation process... can figure out how to get past that...
Shtehla said:
now I cant go past error 170 within the RUU instalation process... can figure out how to get past that...
Click to expand...
Click to collapse
Try this process for getting past error 170. If this doesn't work then try this procedure:
Start the RUU.EXE, it will creat a temporary directory in %TEMP%, and within that folder you will find a 1GB+ file called ROM.ZIP <- this is the full ruu.zip which you can flash using fastboot.
After starting the RUU.EXE, when it's on the first screen, in Windows Explorer type %TEMP% in the location box that will jump you to the folder, sort by date modified, and find the newest folder within that, it's going to have a weird long alpha numeric name, and within that you'll find plenty of files, but one very large file called ROM.ZIP, that's the one you want.
Copy rom.zip into your fastboot/adb folder.
At this point just Cancel and quit out of the ROM Update Utility.
Open a command window in your fastboot/adb folder and
Go to your bootloader. Type:
Code:
adb reboot bootloader
Type:
Code:
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time.
Code:
fastboot flash zip rom.zip
Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
Now, you can reboot. Type:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
I get an error right when getting to the step to flash ROM unto phone.
Start the RUU.EXE, it will creat a temporary directory in %TEMP%, and within that folder you will find a 1GB+ file called ROM.ZIP <- this is the full ruu.zip which you can flash using fastboot.
After starting the RUU.EXE, when it's on the first screen, in Windows Explorer type %TEMP% in the location box that will jump you to the folder, sort by date modified, and find the newest folder within that, it's going to have a weird long alpha numeric name, and within that you'll find plenty of files, but one very large file called ROM.ZIP, that's the one you want.
Copy rom.zip into your fastboot/adb folder.
At this point just Cancel and quit out of the ROM Update Utility.
Open a command window in your fastboot/adb folder and
Go to your bootloader. Type:
Code:
adb reboot bootloader
Type:
Code:
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time.
Code:
fastboot flash zip rom.zip
Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
Now, you can reboot. Type:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
[/QUOTE]
I follow the steps just fine, and I get to step "fastboot flash zip rom.zip" and it gives me an error. see file attached
Shtehla said:
Start the RUU.EXE, it will creat a temporary directory in %TEMP%, and within that folder you will find a 1GB+ file called ROM.ZIP <- this is the full ruu.zip which you can flash using fastboot.
After starting the RUU.EXE, when it's on the first screen, in Windows Explorer type %TEMP% in the location box that will jump you to the folder, sort by date modified, and find the newest folder within that, it's going to have a weird long alpha numeric name, and within that you'll find plenty of files, but one very large file called ROM.ZIP, that's the one you want.
Copy rom.zip into your fastboot/adb folder.
At this point just Cancel and quit out of the ROM Update Utility.
Open a command window in your fastboot/adb folder and
Go to your bootloader. Type:
Code:
adb reboot bootloader
Type:
Code:
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time.
Code:
fastboot flash zip rom.zip
Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
Now, you can reboot. Type:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
Click to expand...
Click to collapse
I follow the steps just fine, and I get to step "fastboot flash zip rom.zip" and it gives me an error. see file attached[/QUOTE]Could you post a fastboot getvar all (except for imei and serialno)? Also, open up the rom.zip and post the contents of the android-info.txt file. Were there two rom.zip files?
Here's teh getvar all results
majmoz said:
[/HIDE]
there was only one zip file.
Click to expand...
Click to collapse
Here's what I get when trying to open the rom.zip
See attachement
Shtehla said:
See attachement
Click to expand...
Click to collapse
Let try the RUU 5.14.531.1 it is the next one up from your version.
I relocked the bootloader
majmoz said:
If you remember I had my bootloader relocked through oem relock. I did unlock it yesterday, would that make a difference in the whole process?
Not it says ***tempered*** and ***unlocked*** on the top of the screen.
Click to expand...
Click to collapse
Shtehla said:
majmoz said:
If you remember I had my bootloader relocked through oem relock. I did unlock it yesterday, would that make a difference in the whole process?
Not it says ***tempered*** and ***unlocked*** on the top of the screen.
Click to expand...
Click to collapse
Yes, since you are S-ON your bootloader needs to be locked/relocked to run RUU and OTA.
Click to expand...
Click to collapse
Here's what I get
majmoz said:
Let try the RUU 514.531.1 it is the next one up from your version.
Click to expand...
Click to collapse
when I flash the ruu it starts with the same message, but then it continues and has a finish. Not the one I need I gues. See attachement.
after i started RUU to create the ROM file in TEMP, it did create 2 rom files (rom_01, rom_02) the rom_02 was the 1.5gb one, and I renamed it to "rom.zip" and i continued with original instructions....
P.S thank you for helping me
Shtehla said:
when I flash the ruu it starts with the same message, but then it continues and has a finish. Not the one I need I gues. See attachement.
after i started RUU to create the ROM file in TEMP, it did create 2 rom files (rom_01, rom_02) the rom_02 was the 1.5gb one, and I renamed it to "rom.zip" and i continued with original instructions....
P.S thank you for helping me
Click to expand...
Click to collapse
Did you try the 5.14.531.1 RUU.exe?
Yes I did.
majmoz said:
Did you try the 5.14.531.1 RUU.exe?
Click to expand...
Click to collapse
Those are the results with this new ruu
Shtehla said:
Those are the results with this new ruu
Click to expand...
Click to collapse
Did you try it as a windows executable file not as a rom.zip?
Yep
majmoz said:
Did you try it as a windows executable file not as a rom.zip?
Click to expand...
Click to collapse
the exe file creates the rom zip. I didn't touch the zip, except i copied it in the fastboot folder
Shtehla said:
the exe file creates the rom zip. I didn't touch the zip, except i copied it in the fastboot folder
Click to expand...
Click to collapse
Yes, I know you pull the rom zip out of the %TEMP% folder. Did you Cancel the update in Windows or did you select Next to allow it to continue?
I
majmoz said:
Yes, I know you pull the rom zip out of the %TEMP% folder. Did you Cancel the update in Windows or did you select Next to allow it to continue?
Click to expand...
Click to collapse
I canceled it, after I copied the rom.zip from temp into fastboot folder.
Shtehla said:
I canceled it, after I copied the rom.zip from temp into fastboot folder.
Click to expand...
Click to collapse
Try to run it completely through in Windows.
Related
Hello, I am unable to get into recovery or in my rom. I can getting into the bootloader, but cannot get into recovery. I am on 1.50 HBOOT and phone is unlocked. I would like to get back to stock so I can do an OTA update. Any help would be great, please let me know if you need more information.
XcsaS said:
Hello, I am unable to get into recovery or in my rom. I can getting into the bootloader, but cannot get into recovery. I am on 1.50 HBOOT and phone is unlocked. I would like to get back to stock so I can do an OTA update. Any help would be great, please let me know if you need more information.
Click to expand...
Click to collapse
What happend to your recovery? Also you need to fastboot oem lock while in hboot using adb
If you wanna go stock you will need the RUU exe you can find this in footballs post in the dev section...
reaper24 said:
What happend to your recovery? Also you need to fastboot oem lock while in hboot using adb
If you wanna go stock you will need the RUU exe you can find this in footballs post in the dev section...
Click to expand...
Click to collapse
not sure what happened with recovery, just wouldn't boot. will I be able to use the RUU exe while in fastboot?
XcsaS said:
Hello, I am unable to get into recovery or in my rom. I can getting into the bootloader, but cannot get into recovery. I am on 1.50 HBOOT and phone is unlocked. I would like to get back to stock so I can do an OTA update. Any help would be great, please let me know if you need more information.
Click to expand...
Click to collapse
if you have a copy of your boot.img and/or your recovery.img file flash that through your fastboot usb screen and reboot you should be ok pending your /system and /data partitioms are ok... if not follow the rest....
ok im goignt to guess youre new to flashing and the android development... but first thing is first... download the stock recovery zip on the other listed thread and rename it PG86IMG.zip... then reboot into your hboot/bootloader.... this will install a stock rom and recovery AFTER that you must reboot then shut down and reboot into your hboot again and from there go to fastboot and plug in the usb cable so your prompt says fastboot usb and then relock your boot loaderafter that finishes reboot again to the ROM and then run your updates... after you get the updates you want you can unlock again and then reinstall superuser and proceed as you want....
wloftus said:
if you have a copy of your boot.img and/or your recovery.img file flash that through your fastboot usb screen and reboot you should be ok pending your /system and /data partitioms are ok... if not follow the rest....
ok im goignt to guess youre new to flashing and the android development... but first thing is first... download the stock recovery zip on the other listed thread and rename it PG86IMG.zip... then reboot into your hboot/bootloader.... this will install a stock rom and recovery AFTER that you must reboot then shut down and reboot into your hboot again and from there go to fastboot and plug in the usb cable so your prompt says fastboot usb and then relock your boot loaderafter that finishes reboot again to the ROM and then run your updates... after you get the updates you want you can unlock again and then reinstall superuser and proceed as you want....
Click to expand...
Click to collapse
Ok following your instructions I downloaded the RUU (two of them infact) changed the name to PG86IMG.zip, when booting into the bootloader, it starts checking the PG86IMG.zip file, there is a blue status bar on the top right, when it fills completely in, it just starting checking the SD card for files again, and then goes back to the normal bootloader screen with options to select fastboot, factory reset, etc... Is there something I missed? I believe there should be some more options.
EDIT: the football post http://forum.xda-developers.com/showthread.php?t=1334473 only goes to .exe files, I had downloaded a .zip file from a different source with the same name, Should I have changed the .exe to PG86IMG.zip?
After using the command flashboot oem lock
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 66977136 (0x3FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.937s
Now showing
*** RELOCKED ***
*** Security Warning ***
XcsaS said:
Ok following your instructions I downloaded the RUU (two of them infact) changed the name to PG86IMG.zip, when booting into the bootloader, it starts checking the PG86IMG.zip file, there is a blue status bar on the top right, when it fills completely in, it just starting checking the SD card for files again, and then goes back to the normal bootloader screen with options to select fastboot, factory reset, etc... Is there something I missed? I believe there should be some more options.
EDIT: the football post http://forum.xda-developers.com/showthread.php?t=1334473 only goes to .exe files, I had downloaded a .zip file from a different source with the same name, Should I have changed the .exe to PG86IMG.zip?
Click to expand...
Click to collapse
no...do not install the exe file at all.... the zip file if it is a trusted source should work...after it loads the files it finishes booting into the hboot screen...from there you can boot into the rom to verify that there is no superuser program and then power down and boot into your hboot again and relock your bootloader then reboot to the rom and update....when you boot back into the rom after installing the zip file it should look like the way it was when you first got it...if not you may have the wrong zip file
Ok I found out there was a zip on that page, I will download that and see where I get. Thank you so much for the help so far.
Ok issue is solved. I guess I needed to be relocked before I could update with PG86IMG.zip. So I guess in the future make sure you are not rooted when trying to update
After attempting s-off my sd card is not recognized. It happened to 2 of them. My computer wont read them and control bear cannot write to them. And now im stuck on juopunutBear logo. ANy help would be great considering I cant use my phone now.
iflawdya said:
After attempting s-off my sd card is not recognized. It happened to 2 of them. My computer wont read them and control bear cannot write to them. And now im stuck on juopunutBear logo. ANy help would be great considering I cant use my phone now.
Click to expand...
Click to collapse
Download this:
http://dl.dropbox.com/u/14779955/jb_hboot.zip MD5: b05336c08f709bf0a909205bcb95b951
but the file in the adb folder where you use cmd
Put the phone in fastboot mode, then run the follwoing commands:
Code:
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
fastboot reboot
iflawdya said:
After attempting s-off my sd card is not recognized. It happened to 2 of them. My computer wont read them and control bear cannot write to them. And now im stuck on juopunutBear logo. ANy help would be great considering I cant use my phone now.
Click to expand...
Click to collapse
You haven't got s-off right? You got stuck there while trying to?
Sent from my HTC Vigor
Andro X said:
You haven't got s-off right? You got stuck there while trying to?
Sent from my HTC Vigor
Click to expand...
Click to collapse
Correct. Not there and screwed up 2 16gb cards in the process.
iflawdya said:
Correct. Not there and screwed up 2 16gb cards in the process.
Click to expand...
Click to collapse
You should only have used the one. It seems others have been able to correct the issue by simply reformatting the card with the phone, not via a USB connection to a computer.
a.mcdear said:
You should only have used the one. It seems others have been able to correct the issue by simply reformatting the card with the phone, not via a USB connection to a computer.
Click to expand...
Click to collapse
How would I reformat the card with the phone? I am stuck at juopunutbear screen. I can only get to fastboot screen. From there it says no image.
iflawdya said:
How would I reformat the card with the phone? I am stuck at juopunutbear screen. I can only get to fastboot screen. From there it says no image.
Click to expand...
Click to collapse
download a kernel, flash it from fastboot. Then reboot, and your ROM will load. Then fix the SDCARD, and try again.
cflo360 said:
Download this:
http://dl.dropbox.com/u/14779955/jb_hboot.zip MD5: b05336c08f709bf0a909205bcb95b951
but the file in the adb folder where you use cmd
Put the phone in fastboot mode, then run the follwoing commands:
Code:
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
fastboot reboot
Click to expand...
Click to collapse
cflo360 when I get to fastboot flash zip jb_hboot.zip it gets an erroe that says failed remote: 99 unknown fail. Any ideas? Would it be possible to just put a rom on another sd card and flash it?
a.mcdear said:
download a kernel, flash it from fastboot. Then reboot, and your ROM will load. Then fix the SDCARD, and try again.
Click to expand...
Click to collapse
sorry I was typing a question and did not see what you wrote before I sent it.
a.mcdear said:
download a kernel, flash it from fastboot. Then reboot, and your ROM will load. Then fix the SDCARD, and try again.
Click to expand...
Click to collapse
I know im asking alot but could you tell me how to flash a kernel from fastboot. I have only done it from the phone.
Thanks
iflawdya said:
I know im asking alot but could you tell me how to flash a kernel from fastboot. I have only done it from the phone.
Thanks
Click to expand...
Click to collapse
Pull your battery.. reinsert and hold volume down and the power button. Make sure phone is plugged in or replug in phone if you took it off to reboot. Should be in Hboot now, press power to select fastboot if it is white lettering over blue background. If it is red background your already in fastboot and if connected should say fastbootusb.
1. open a copy of the rom your on either with 7 zip or since your not adding anything to it unzip it .
2. find the folder that says kernel, now you will either see a PH98IMG.zip or you will see a file that his white with a silver circle called boot. That is the raw boot.img. If it is the ph zip simply unzip it and you will see the boot.img.
3. Now , remove the boot.img and place it in the same folder your fastboot is located , generally the place you unlocked with.
4. Then, bring up a command prompt the same way you did to unlock. change directory if needed by cd c:\thenthenameofthefoldrecontainingfastboot.
5. Simply type fastboot boot boot.img
6. you will see sending " size of img".. receiving "size of img ", then writing .. and it will end and tell you how many seconds it took.
Now, simply use the reboot selection from bootloader or with the command prompt type abd reboot and your phone should reboot and you will be back on your rom.
The reason you keep booting to the jBear screen is because the jBear process replaced your KERNEL. You need to find the kernel img file for YOUR operating system or ROM. If you are on GB, find a GB kernel. If on the ICS Leak, you need to find the ICS Leak kernel. If on a ROM, get that ROM's kernel file.
Then the commands on the PC are:
fastboot flash boot boot.img
fastboot reboot
Another option is to use Hansoon's Rezound All-in-one-kit to flash the stock kernel for you.
Howard
iflawdya said:
I know im asking alot but could you tell me how to flash a kernel from fastboot. I have only done it from the phone.
Thanks
Click to expand...
Click to collapse
no offense, but if you honestly cannot at least search to figure out how to do a fastboot command as simple as fastboot flash, then you should stay clear of s-off...
but that's my opinion.
and I'm really not saying this to be an ass.
just don't want to see you brick your phone.
mjh68 said:
Pull your battery.. reinsert and hold volume down and the power button. Make sure phone is plugged in or replug in phone if you took it off to reboot. Should be in Hboot now, press power to select fastboot if it is white lettering over blue background. If it is red background your already in fastboot and if connected should say fastbootusb.
1. open a copy of the rom your on either with 7 zip or since your not adding anything to it unzip it .
2. find the folder that says kernel, now you will either see a PH98IMG.zip or you will see a file that his white with a silver circle called boot. That is the raw boot.img. If it is the ph zip simply unzip it and you will see the boot.img.
3. Now , remove the boot.img and place it in the same folder your fastboot is located , generally the place you unlocked with.
4. Then, bring up a command prompt the same way you did to unlock. change directory if needed by cd c:\thenthenameofthefoldrecontainingfastboot.
5. Simply type fastboot boot boot.img
6. you will see sending " size of img".. receiving "size of img ", then writing .. and it will end and tell you how many seconds it took.
Now, simply use the reboot selection from bootloader or with the command prompt type abd reboot and your phone should reboot and you will be back on your rom.
Click to expand...
Click to collapse
mjh68 I LOVE YOU MAN!! Thank you so much.
HowardZ said:
The reason you keep booting to the jBear screen is because the jBear process replaced your KERNEL. You need to find the kernel img file for YOUR operating system or ROM. If you are on GB, find a GB kernel. If on the ICS Leak, you need to find the ICS Leak kernel. If on a ROM, get that ROM's kernel file.
Then the commands on the PC are:
fastboot flash boot boot.img
fastboot reboot
Another option is to use Hansoon's Rezound All-in-one-kit to flash the stock kernel for you.
Howard
Click to expand...
Click to collapse
I tried the all in one and it did not work. I was stuck at htc splash screen.
andybones said:
no offense, but if you honestly cannot at least search to figure out how to do a fastboot command as simple as fastboot flash, then you should stay clear of s-off...
but that's my opinion.
and I'm really not saying this to be an ass.
just don't want to see you brick your phone.
Click to expand...
Click to collapse
None taking but if I don't know whats wrong how am I gonna search? Instead of telling me about the search button which yields thousands of threads how about helping me out. As you can see I have been a member for a long time. I didn't just pop on this site because I screwed up. I was up till 4 am trying to figure this out before asking for help.
I was on 4.0.3 and I flashed the zip through AromRa recovery.
Now, when booting up, its stuck at the 4G screen.
The update was the OTA update released to update radios to Global. THIS
It didn't gave any error at all, it said "Reboot to complete installation or update". But when I clicked the reboot option, I saw a line saying something like "Can't write....." then the screen went off and it rebooted. This line was not there, or atleast not visible before I clicked the reboot option.
I am new to rezound and android, so please let me know what I can do. I wasn't able to get a nandroid backup before doing this, had no ext. SD card.
All I did before flashing the zip was flashing the custom recovery. Nothing else. No SU or anything else.
Can I RUU 4.0.3 to fix this problem?
Yes you need to ruu to get it back. I'm assuming your s on. You need to be s off in order to flash radios by themselves.
Sent from my ADR6425LVW using xda app-developers app
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
lamborg said:
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
Click to expand...
Click to collapse
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
feralicious said:
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
Click to expand...
Click to collapse
I relocked but then tried flashing the zip twice.
Here's what comes in cmd:
sending....
OKAY
writing
<bootloader>adopting sig ....
<bootloader>checking sig
failed <remote: not allowed>
finished
After rebooting, it gets stuck on the white HTC screen.
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
mike7728 said:
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
Click to expand...
Click to collapse
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You have to fastboot oem rebootRUU first
then fastboot flash zip PH98IMG.zip
you may have to flash the zip twice.
Code:
androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
(I can't link yet)
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You don't flash this in fastboot since it's a zip file.
EDIT: Looks like you can flash in fastboot as mentioned in the above post. Cool, I like that. I would flash it twice as I've read several times that you need to to make sure it gets all the system files.
If htat doesn't work for whatever reason, just put it on the sd card of your phone, detach your phone from your pc and reboot. hboot should find it (it looks for the PH98IMG.zip file) and flash it. Flash it twice to be sure it gets all the system files.
When it's done and you're rebooted use a file explorer and delete the PH98IMG file so it doesn't flash again on the next reboot.
Okay, here we go. I am new to rooting and I have already unlocked the bootloader on my device (HTC Evo 4G LTE). It still has S-on. After I unlocked my bootloader, I continued on to flash TWRP Recvovery onto my phone using fastboot. My phone does not have an SD card. However, no matter how many times I download the newest version of TWRP or rename the file or change the directory in the command prompt...it says "error: cannot load recovery image". When I attempt to restart in recovery mode, I get this red triangle with an explanation point! I have tried over and over again, but since I cant flash this recovery, i have an unlocked bootloader for practically no reason. I need to get past this step in order to start flashing custom ROM's. I even used RegawMOD EVO 4G LTE Rooter. After i click "Root Me" it puts my device into fastboot and attempts to submit the unlock token to HTCDev.com even though I already did that! I am stuck :crying:
Go here and download the recovery to your ADB tools folder.
http://techerrata.com/file/twrp2/jewel/openrecovery-twrp-2.3.3.0-jewel.img
You can rename the file "twrp" without the quotation marks. Make sure the file doesn't have an extra img extension or it won't work. Once you do this reboot your phone to the bootloader. Connect your phone to your computer via USB cable. You should see the word Fastboot in red highlights change to Fastboot USB. Open up ADB and type "fastboot flash recovery twrp.img" (without quotation marks) then press enter. At this point TWRP recovery should be installed on your phone.
If these are the steps you have followed, disregard.
The advice is free....the bandwidth, not so much
Thank You for Replying Good Sir!
1)when i download any twrp file and try to open it on my computer, it says "the disc image file is corrupted"
2)when i attempt to open ADB , it flashes up then off. I cant read what it says
3)i entered the command in the command prompt and it just says waiting for device
gratealex8 said:
1)when i download any twrp file and try to open it on my computer, it says "the disc image file is corrupted"
2)when i attempt to open ADB , it flashes up then off. I cant read what it says
3)i entered the command in the command prompt and it just says waiting for device
Click to expand...
Click to collapse
Download this extract it to your desktop and run your commands from that folder by pressing shift and right clicking on an empty spot inside the folder and choose open cmd window here.
There is a readme.txt inside follow the instructions on how to fastboot flash twrp (Copy and paste is the easiest way to do this that way there are no typo's)
Use v2.4.1.0 if you are on the latest OTA
Use v2.3.1.0 otherwise
idk whats wrong!!
I did exactly as you said, yet the command prompt just says waiting for device. I'm not sure what to do anymore because regardless of following these instructions, I CANT FLASH TWRP RECOVERY TO MY PHONE. I believe the problem is with my phone but Im running out of options. its beginning to look like I unlocked my bootloader for nothing :/
gratealex8 said:
I did exactly as you said, yet the command prompt just says waiting for device. I'm not sure what to do anymore because regardless of following these instructions, I CANT FLASH TWRP RECOVERY TO MY PHONE. I believe the problem is with my phone but Im running out of options. its beginning to look like I unlocked my bootloader for nothing :/
Click to expand...
Click to collapse
Try these drivers.Install them and reboot your PC once rebooted go to add/remove programs and delete HTC Sync
Getting frustrated
bigdaddy619 said:
I did this and again all I get in the command prompt is waiting for device. No more ideas huh?
Click to expand...
Click to collapse
Long story short I f'd up trying to install cyanogen. The only thing I can do on my phone currently is enter the bootloader. I've tried going back to stock by using the ruu zip through cmd, yet it always gives me a signature verify fail. When I've ran ruu.exe from my pc it gets to the final step but gives me an error when trying to find my phone.
I'm hoping since I can at least get in to fast boot that there is still hope.
also sorry for clogging the forum with another troubled phone story.
What did you do on the install? Cyan installer, download and install from recovery? A little more info please
Sent from my One using XDA Premium 4 mobile app
nwmn9386 said:
Long story short I f'd up trying to install cyanogen. The only thing I can do on my phone currently is enter the bootloader. I've tried going back to stock by using the ruu zip through cmd, yet it always gives me a signature verify fail. When I've ran ruu.exe from my pc it gets to the final step but gives me an error when trying to find my phone.
I'm hoping since I can at least get in to fast boot that there is still hope.
also sorry for clogging the forum with another troubled phone story.
Click to expand...
Click to collapse
This is the instructions posted by Scotty85
I'm just re-posting it for you
Quote:
http://androidforums.com/t-one-all-t...ml#post5864243
Quote:
here is how you extract rom.zip:
Quote:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,youre done with it.
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Quote:
here are some directions to flash "rom.zip"
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboot oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writing, and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.
Click to expand...
Click to collapse