Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?
sideshow03 said:
Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?
Click to expand...
Click to collapse
Okay so can someone confirm then that I am out of luck on this one:?
sideshow03 said:
Okay so can someone confirm then that I am out of luck on this one:?
Click to expand...
Click to collapse
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:
tivofool said:
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:
Click to expand...
Click to collapse
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?
sideshow03 said:
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?
Click to expand...
Click to collapse
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.
tivofool said:
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.
Click to expand...
Click to collapse
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks
sideshow03 said:
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks
Click to expand...
Click to collapse
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard
tivofool said:
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard
Click to expand...
Click to collapse
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere
sideshow03 said:
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere
Click to expand...
Click to collapse
Is your bootloader locked? Can't install recoveries with locked bootloader.
tivofool said:
Is your bootloader locked? Can't install recoveries with locked bootloader.
Click to expand...
Click to collapse
No I am Unlocked S-off CID 11111111
sideshow03 said:
No I am Unlocked S-off CID 11111111
Click to expand...
Click to collapse
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img
tivofool said:
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip
sideshow03 said:
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip
Click to expand...
Click to collapse
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.
Solved
tivofool said:
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.
Click to expand...
Click to collapse
Yes it was a bad download. Thanks for all of your help I really appreciate your time to help me get back up and running. :victory:
Related
Hi Trev here,I am a New member and hope this is posted in the correct place,I have a HTC ONE S S3 Version chip,No SD card version,has OPTUS AU Firmware on it with CID OPTUS_001,My system stopped booting when i tried to get Nova 3 game working,at the moment its not compatible for my device,but i read on the forums if i edited my Build prop I could get it working again,but sadly enough,it stopped booting the OS and i can sometimes get into the boot loader,Now the only way i can see to fix this is to get the original optus ruu and flash it but i cant find it any where,and i cannot install any of the other stock s3 roms because i don't have super CID,do you guys have any ideas,cheers Trev.
Do you know exatcly what you have changed in build.prop? You could try to boot your phone into bootloader. Adn than try to access it with adb shell. Pull the build.prop, change it back the way it was, and push it back on the phone, replacing the not working one. This might work.
+1 to the above, and if you can't remember your edits maybe grab a build.prop from one of those S3 roms. Also are you sure you can't get supercid on your phone just because it doesn't boot, are there even steps needing to be done while booted?
adb shell
qzem said:
Do you know exatcly what you have changed in build.prop? You could try to boot your phone into bootloader. Adn than try to access it with adb shell. Pull the build.prop, change it back the way it was, and push it back on the phone, replacing the not working one. This might work.
Click to expand...
Click to collapse
Thanks for your reply,how do i change the build prop through adb shell,cheers.
build prop from one s s3 ruu
frdd said:
+1 to the above, and if you can't remember your edits maybe grab a build.prop from one of those S3 roms. Also are you sure you can't get supercid on your phone just because it doesn't boot, are there even steps needing to be done while booted?
Click to expand...
Click to collapse
how do i get the build prop from RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed as i dont know how to access the file within the ruu,cheers.
trevor3737 said:
Thanks for your reply,how do i change the build prop through adb shell,cheers.
Click to expand...
Click to collapse
Code:
adb pull /system/build.prop c:\wherever
edit build.prop
adb remount
adb push c:\wherever\build.prop /system/
adb reboot
trevor3737 said:
how do i get the build prop from RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed as i dont know how to access the file within the ruu,cheers.
Click to expand...
Click to collapse
You have to be on Windows to run RUU, if you are just click it and let it run for a while. It'll make a zip file in a new random-named folder, similar to c:\users\username\{*******-*******-*******-*******-*****}\rom.zip check here for build.prop
re build prop
frdd said:
Code:
adb pull /system/build.prop c:\wherever
edit build.prop
adb remount
adb push c:\wherever\build.prop /system/
adb reboot
You have to be on Windows to run RUU, if you are just click it and let it run for a while. It'll make a zip file in a new random-named folder, similar to c:\users\username\{*******-*******-*******-*******-*****}\rom.zip check here for build.prop
Click to expand...
Click to collapse
Does the phone have to be connected in fastboot while the ruu is running to find the zip file,because i started the ruu up without the phone connected and i cannot find the zip file,so i can look at the build.prop,cheers.
trevor3737 said:
Does the phone have to be connected in fastboot while the ruu is running to find the zip file,because i started the ruu up without the phone connected and i cannot find the zip file,so i can look at the build.prop,cheers.
Click to expand...
Click to collapse
You just try the first method with pulling and pushing. It is to complicated to extract build.prop from ruu.
re adb pull
qzem said:
You just try the first method with pulling and pushing. It is to complicated to extract build.prop from ruu.
Click to expand...
Click to collapse
is where ever the place i send the build prop to,and when i run adb it say device not found,cheers.
Go into recovery hopefully adb will work there, if not you're limited to fast boot commands. You have to be in bootloader for fastboot to work, it'll say fastboot USB on screen if cable is plugged in. Maybe you have to have phone connected for RUU to run, and also click a few times until the "View readme" button appears until the zip is extracted to the temp dir. When I wrote wherever I mean anywhere you want the stuff
re
frdd said:
Go into recovery hopefully adb will work there, if not you're limited to fast boot commands. You have to be in bootloader for fastboot to work, it'll say fastboot USB on screen if cable is plugged in. Maybe you have to have phone connected for RUU to run, and also click a few times until the "View readme" button appears until the zip is extracted to the temp dir. When I wrote wherever I mean anywhere you want the stuff
Click to expand...
Click to collapse
Hi thanks for your time on this,i am so frustrated with this,When i go into recovery,i get the white screen with the Htc logo,Quietly brilliant logo and red writing about being used by developers,and it stays on there and nothing else happens,I did flash try a recovery Team Win Recovery Project but i found out it was for s4 devices only so i bet that screwed my recovery up,I am limited to fast boot commands,I suppose i will have to wait till a recovery comes out for the one s s3 chip or i find the correct optus ics branded ruu.
trevor3737 said:
Hi thanks for your time on this,i am so frustrated with this,When i go into recovery,i get the white screen with the Htc logo,Quietly brilliant logo and red writing about being used by developers,and it stays on there and nothing else happens,I did flash try a recovery Team Win Recovery Project but i found out it was for s4 devices only so i bet that screwed my recovery up,I am limited to fast boot commands,I suppose i will have to wait till a recovery comes out for the one s s3 chip or i find the correct optus ics branded ruu.
Click to expand...
Click to collapse
Hmm tricky one this...
Just so we're talking about the same things, this is what the bootloader looks like:http://www.geeky-gadgets.com/wp-content/uploads/2012/05/bootloader-unlock-htc-one.jpg
I have no idea how the HTC recovery looks, flashed CWM in a heartbeat on my VilleU...
You have read the "The Ville C (HTC One S with S3 chips) and development" thread I guess? Some guys there apparantly flashed S4 recovery and got boot issues that were fixed. check on page 5 http://forum.xda-developers.com/showthread.php?t=1719911&highlight=ruu+help&page=5
Have you unlocked the bootloader via htcdev.com? I guess so since you flashed that S4 recovery... I dont think you need more than fastboot access to do it anyways IIRC. http://htcdev.com/bootloader/preview_unlock_process
If you have, you could try paulobriens boot.img that roots your S3 device, which is neat and all but more importantly it might perhaps hopefully maybe god willing if Cthulu allows it let your phone boot once and that time it'll have insecure adb access...
http://www.modaco.com/topic/355509-testing-villec-superboot/
Also I havent run an RUU myself for a long time so dont remember if you have to be on stock recovery but I think you have to relock your bootloader, this can be done in fastboot. I think you can run any RUU no matter what CID you have, but also you have to have phone running, or else flash it in stock recovery somehow...
re recovery
frdd said:
Hmm tricky one this...
Just so we're talking about the same things, this is what the bootloader looks like:http://www.geeky-gadgets.com/wp-content/uploads/2012/05/bootloader-unlock-htc-one.jpg
I have no idea how the HTC recovery looks, flashed CWM in a heartbeat on my VilleU...
You have read the "The Ville C (HTC One S with S3 chips) and development" thread I guess? Some guys there apparantly flashed S4 recovery and got boot issues that were fixed. check on page 5 http://forum.xda-developers.com/showthread.php?t=1719911&highlight=ruu+help&page=5
Have you unlocked the bootloader via htcdev.com? I guess so since you flashed that S4 recovery... I dont think you need more than fastboot access to do it anyways IIRC. http://htcdev.com/bootloader/preview_unlock_process
If you have, you could try paulobriens boot.img that roots your S3 device, which is neat and all but more importantly it might perhaps hopefully maybe god willing if Cthulu allows it let your phone boot once and that time it'll have insecure adb access...
http://www.modaco.com/topic/355509-testing-villec-superboot/
Also I havent run an RUU myself for a long time so dont remember if you have to be on stock recovery but I think you have to relock your bootloader, this can be done in fastboot. I think you can run any RUU no matter what CID you have, but also you have to have phone running, or else flash it in stock recovery somehow...
Click to expand...
Click to collapse
I have uploaded a pic of the boot loader,i have root access via pauls super boot,boot loader is unlocked and i know how to re lock if i have to ,cheers.
trevor3737 said:
When i go into recovery,i get the white screen with the Htc logo,Quietly brilliant logo and red writing about being used by developers
Click to expand...
Click to collapse
Are you sure this is when you go into recovery? Thats how it looks when trying to boot, and where the phone gets stuck when your boot.img is f-d up or you flash a new ROM and forgot/failed to flash boot.img or TWRP randomly fails to do this for you... try
Code:
fastboot boot boot.img
(replace boot.img with actual filename), you must be in the directory on PC where you have downloaded a boot.img for the VilleC2, or use the one I linked before from paulobrien, just extract the boot.superboot.img from the superboot.zip. This is of course the same thing as just running install-superboot-windows.bat now that I think about it, duh time for coffee here it seems. Good luck!
(you could also just send it in for service to HTC, and not take unnecessary risks with your expensive new hardware... root what? Whats a recovery? Fix my iphone damnit I just bought it and its already broken??)
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
Yup thats a bootloader Maybe try pauls again, did it boot normally last time you ran it?
re recovery
[/ATTACH]
frdd said:
Are you sure this is when you go into recovery? Thats how it looks when trying to boot, and where the phone gets stuck when your boot.img is f-d up or you flash a new ROM and forgot/failed to flash boot.img or TWRP randomly fails to do this for you... try
Code:
fastboot boot boot.img
(replace boot.img with actual filename), you must be in the directory on PC where you have downloaded a boot.img for the VilleC2, or use the one I linked before from paulobrien, just extract the boot.superboot.img from the superboot.zip. This is of course the same thing as just running install-superboot-windows.bat now that I think about it, duh time for coffee here it seems. Good luck!
(you could also just send it in for service to HTC, and not take unnecessary risks with your expensive new hardware... root what? Whats a recovery? Fix my iphone damnit I just bought it and its already broken??)
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
Yup thats a bootloader Maybe try pauls again, did it boot normally last time you ran it?
Click to expand...
Click to collapse
thats what happens when i hit recovery from the bootloader screen.
that is because you flashed wrong recovery. Here in this rar file it is original stock recovery for your phone (ignore othere files). Flash recovery_signed.img one just like you did twrp! And the attached build.prop from my HTC One S (S3), if it is any help. Juste remove the .txt ant the endo of build.prop. I had to add it to make it "valid" upload file.
re flash recovery
qzem said:
that is because you flashed wrong recovery. Here in this rar file it is original stock recovery for your phone (ignore othere files). Flash recovery_signed.img one just like you did twrp! And the attached build.prop from my HTC One S (S3), if it is any help. Juste remove the .txt ant the endo of build.prop. I had to add it to make it "valid" upload file.
Click to expand...
Click to collapse
it says remote not allowed
re
trevor3737 said:
it says remote not allowed
Click to expand...
Click to collapse
C:\Android>fastboot boot recovery_signed.img
creating boot image...
creating boot image - 6103040 bytes
downloading 'boot.img'...
OKAY [ 1.188s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.188s
Try fastboot flash recovery recovery-signed.img instead if you want to flash new recovery, fastboot boot will just boot from the image assuming its a boot.img with a ramdisk and kernel inside it
re flash recovery
frdd said:
Try fastboot flash recovery recovery-signed.img instead if you want to flash new recovery, fastboot boot will just boot from the image assuming its a boot.img with a ramdisk and kernel inside it
Click to expand...
Click to collapse
C:\Android>fastboot boot recovery_signed.img
creating boot image...
creating boot image - 6103040 bytes
downloading 'boot.img'...
OKAY [ 1.172s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.188s
C:\Android>fastboot flash recovery recovery-signed.img
error: cannot load 'recovery-signed.img'
the fastboot boot recovery_signed.img way and the fastboot flash recovery recovery-signed.img way
I attempted to place a ROM on the phone using CWM recovery and something messed up. Now, I can boot into screen that says fastboot, recovery, etc. However, when I select recovery, nothing happens. Anyone point me in the right direction...im back to using my Blackberry!
From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast
E.Cadro said:
From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
This is where I am stuck. Unfortunately, I'm not all that familiar with Fastboot. When connecting the phone to the PC with a USB, I see that the phone says Fatboot USB. From there I'm lost. I've not been able to find a guide that describes how to install a ROM using fastboot. Lots of posts says that it can be done, but none describing how its done. Anyone pointing me in the right direction?
http://forum.xda-developers.com/showthread.php?t=1754018
gunnyman said:
http://forum.xda-developers.com/showthread.php?t=1754018
Click to expand...
Click to collapse
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?
rpritch said:
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?
Click to expand...
Click to collapse
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?
rpritch said:
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?
Click to expand...
Click to collapse
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1
veritas2884 said:
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1
Click to expand...
Click to collapse
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast
E.Cadro said:
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Our devices will not boot. All we can get is either the white HTC Screen or get into the menu that allows fastboot/recover/ect...
Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app
c5satellite2 said:
Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:
Recommended process for fixing strange issues like what you were experiencing. Glad it helped you guys out!
Sent from my HTC One XL using xda app-developers app
veritas2884 said:
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:
Click to expand...
Click to collapse
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?
rpritch said:
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?
Click to expand...
Click to collapse
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!
veritas2884 said:
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!
Click to expand...
Click to collapse
I cant seem to find a stock Rogers Ruu...will continue searching. Anyone out there have it?
http://http://forum.xda-developers.com/showthread.php?p=27882810#post27882810
Finally got it working...the above link is what worked. Here is the summary...
I was having this same problem and it took a while before I could get it to work. Try opening a command window in the same location of your adb tools.
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
Hopefully this helps you out!
Berserk87 said:
I'm stock right now (rooted) , but the updates keep failing, so i want to reflash stock rom.
I'm lost as to how to do this.
I downloaded ARUwizard and the stock rogers rom (PJ83IMG) but its still failing. I dont get all this adb tools stuff.
Click to expand...
Click to collapse
do this:
1.Put Rogers stock zip (keep it in zip form) in your platform-tools folder (you need to download Android SDK). This is the rogers file I downloaded...http://rapidlibrary.com/files/pj83i...elease-254934-signed-zip_ulc8eyefx8i89on.html
2. Boot phone into fastboot (hold power button and volume down key)
3. Used command window to relock bootloader by doing the following:
use command window to get to location on your computer where you have saved SDK stuff, continue with command window to the platform-tools folder then enter the following commands:
fastboot devices <enter>
fastboot oem lock <enter>
Phone will restart and reboot into fastboot again
4. type 'fastboot oem rebootRUU'.
5. Next, make sure you have the .zip RUU file in the same folder (see step 1) and type 'fastboot flash zip XXX.zip' (replace XXX with whatever the rogers stock zip is called, I changed it to "rogersstock.zip")
Phone will reboot to a HTC screen. If you see "re-flush image immediately", repeat fastboot flash zip XXX.zip command. You may have to do this 2 or 3 times.
After doing this, I was able to download and install the Rogers firmware update
BTW...I didn't discover any of this stuff on my own...I researched a bunch of different posts and put it together. Hopefully, someone else finds have all this in one post useful.
Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.
slash178 said:
Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.
Click to expand...
Click to collapse
What you are doing wrong is flashing the recovery for the wrong phone. Any file with "enveavoru" in it is for the international (Tegra3) version. Our phone is "evita".
Only install things in our Dev forum:
http://forum.xda-developers.com/forumdisplay.php?f=1541
To see everything in an organized list, go to my index: http://forum.xda-developers.com/showthread.php?t=1671237
Also, TWRP is recommended. CWM does not officially support our device, and therefore is just a port, and buggy. TWRP officially supports our device.
im getting the same error and im using the recovery ending on evita
i was rooting my htc one x that when well when i tried to flash a rom to it i somehow deleted everything stock os everything i can still get to the bootloader and root screen please some one help me get my phone back and working again??????
What hboot do u have 1.14?
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
And don't worry your phone isn't close to being bricked :victory:
If you want to return to stock unrooted just lock the bootloader via fastboot and install the ruu for your device.
boot into bootloader, run "fastboot oem lock", then run the ruu afterwards
I'm sure someone can provide you your devices ruu download, just be patient.. or if you want a rom installed I'm pretty sure you have to install the boot.IMG first then rom after that after clearing caches.
what is a ruu and can someone give me a step by step process im using the bootloader from onexroot.com i have hboot 1.14 yes
im using team win recovery project v2.3.1.0
The reason your phone didn't boot up all the way was because 1 you flashed wrong Rom or 2 you dint flash the boot IMG separately because your on hboot 1.14
---------- Post added at 02:22 AM ---------- Previous post was at 02:21 AM ----------
Do. you know how to flash the boot IMG through fastboot?
omario8484 said:
The reason your phone didn't boot up all the way was because 1 you flashed wrong Rom or 2 you dint flash the boot IMG separately because your on hboot 1.14
---------- Post added at 02:22 AM ---------- Previous post was at 02:21 AM ----------
Do. you know how to flash the boot IMG through fastboot?
Click to expand...
Click to collapse
no i do not i just downloaded the ruu file
C:\Users\NJHCphotography2012>fastboot erase cache
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
this is a message i am currently getting so i think this is hindering me from recovery any solutions?
If u want to run the ruu go into fastboot from there in command prompt type fastboot OEM lock
Locks your bootloader than go into bl mode and run the ruu... But al you have to do is flash the boot IMG from the Rom and your device will be functional and running that Rom you should read a bit.more
omario8484 said:
If u want to run the ruu go into fastboot from there in command prompt type fastboot OEM lock
Locks your bootloader than go into bl mode and run the ruu... But al you have to do is flash the boot IMG from the Rom and your device will be functional and running that Rom you should read a bit.more
Click to expand...
Click to collapse
C:\Users\NJHCphotography2012>fastboot OEM lock
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
im still getting this message in the command prompt when i try to do it
randyarenz said:
im still getting this message in the command prompt when i try to do it
Click to expand...
Click to collapse
Whoa, there, slow down, hoss.
It's obvious from this thread that you're in way over your head. You should not even be rooting before you even know what a RUU or bootloader is, or how to run fastboot correctly.
First, make sure you have the HTC drivers installed on your computer.
Second, you have to run the command in command prompt from the same directory that you put fastboot.exe.
When you relock and run the RUU, you will be stock, locked, and unrooted. Stay there until you've done a lot more reading and understand what it is you're doing to your phone.
Also, stay away from onexroot.com, which is mainly for the international version. Stuff from there may brick your phone.
iElvis said:
Whoa, there, slow down, hoss.
First, make sure you have the HTC drivers installed on your computer.
Second, you have to run the command in command prompt from the same directory that you put fastboot.exe.
Click to expand...
Click to collapse
Should've said that too thanks for putting that out there
I have a feeling he doesn't even have the sdk installed..... If you do OP open the folder where your android sdk platform-tools folder and hold shift on your keyboard right click on your mouse and chose open command prompt here it will open the cmd window where you need to type your commands like the others told you.... GL and please make sure you read and understand everything before doing ANYTHING
Sent from my Nexus 7 using xda app-developers app
Try this tread may be easier for you to lock bootloader.
Just make sure you read carefully
http://forum.xda-developers.com/showthread.php?t=1952426
Make your way to Onex general and find gunnymans quick and dirty adb and fastboot thread. Download adb. extract. RIGHT CLICK ON THE ADB FOLDER and choose "open command prompt here"
Nowwww you can type fastboot oem lock
That will lock bootloader. Now run the ruu, but you have to have HTC sync or it won't work :/
Good luck and have patience
Sent from my One X using Tapatalk 2
Thanks for all the advice my manager helped me out I had everything right except for a working rom
InflatedTitan said:
Make your way to Onex general and find gunnymans quick and dirty adb and fastboot thread. Download adb. extract. RIGHT CLICK ON THE ADB FOLDER and choose "open command prompt here"
Click to expand...
Click to collapse
As an addendum, you will have to hold down the shift key and then right click for the "open command prompt here" option to appear in the context menu.
Ok new help
I've been trying to install new roms I have backups I'm not worried about losing the stuff but when ever I flash the rom it says mdk5 file not found then proceeds and confuses me to boot up but it just stays on the rom screen and doesn't do anything I know that's because the mdk5 file is needed to run it I'm using viperxl and I also have a clean Rom that works and thoughts? Or aybe missing a step or not getting the right download for the rom? Thanks in advance.
randyarenz said:
I've been trying to install new roms I have backups I'm not worried about losing the stuff but when ever I flash the rom it says mdk5 file not found then proceeds and confuses me to boot up but it just stays on the rom screen and doesn't do anything I know that's because the mdk5 file is needed to run it I'm using viperxl and I also have a clean Rom that works and thoughts? Or aybe missing a step or not getting the right download for the rom? Thanks in advance.
Click to expand...
Click to collapse
I'm also using twrp recovery if that helps
i do this in winxp might work on any windows os.
make a file named "install adb fastboot.bat"
add these lines to it then save and run, if you are in vista/7/8 run as admin.
@echo off
cls
copy adb.exe %systemroot%\system32\
copy AdbWinApi.dll %systemroot%\system32\
copy AdbWinUsbApi.dll %systemroot%\system32\
copy fastboot.exe %systemroot%\system32\
pause
exit
make sure those 4 files are in the same folder when you run the .bat file
this will allow you to use adb/fastboot from anywhere you open the command prompt
So I flash the stock rom on it without thinking and now it wont let me flash a recovery to the tablet threw fastboot or goomanager and it wont update throguh asus update but its booting fine and wont take any updates at all i need help being pointed in the right direction!
I flashed the wrong bootloader i think and how do i flash the correct bootloader without a recover?
in fastboot im getting the error: cannot load 'file name' :no error weather its cm or twrp it wont load it and i dont know what to do please help
First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?
berndblb said:
First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?
Click to expand...
Click to collapse
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess
Skittleskitty said:
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess
Click to expand...
Click to collapse
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.
berndblb said:
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.
Click to expand...
Click to collapse
thank you so much that fixed it!!
ok i did all that but it removed fastboot what do i do to get it back?
Skittleskitty said:
ok i did all that but it removed fastboot what do i do to get it back?
Click to expand...
Click to collapse
Read the text in the upper left corner - current bootloaders enable fastboot in the bootloader menu automatically.
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
Then maybe it's not in your current directory.
Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial
berndblb said:
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial
Click to expand...
Click to collapse
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.
ok ive re installed fastboot and adb sdk and did the environment variable path and it still wont recognize the blob it wont recognize cwm .img files ether and what does key driver not found..booting os
Skittleskitty said:
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.
Click to expand...
Click to collapse
It has to be in your *current* directory.
_that said:
It has to be in your *current* directory.
Click to expand...
Click to collapse
thankyou it moved directorys on me that was the issue
After update to cm-11-20140413 and instal newest kernel (Sultan-kernel-Pure-v1.4.0) my htc stuck at cyanogen loading screen. I don't know where's the problem. Maybe someone know the solution.
chmiela1991 said:
After update to cm-11-20140413 and instal newest kernel (Sultan-kernel-Pure-v1.4.0) my htc stuck at cyanogen loading screen. I don't know where's the problem. Maybe someone know the solution.
Click to expand...
Click to collapse
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
rzr86 said:
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
Click to expand...
Click to collapse
Thanks flashing new boot helped
rzr86 said:
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
Click to expand...
Click to collapse
I have the same problem, but i cant find the command in the bootloader
Noam_Nissel said:
I have the same problem, but i cant find the command in the bootloader
Click to expand...
Click to collapse
actually you type the command from pc
connect your device to pc in fastboot mode(in the hboot screen should say fastboot usb)
extract the boot.img from the rom and place it in your adb/fastboot folder
then open a cmd window in that folder and type the command
press enter
rzr86 said:
actually you type the command from pc
connect your device to pc in fastboot mode(in the hboot screen should say fastboot usb)
extract the boot.img from the rom and place it in your adb/fastboot folder
then open a cmd window in that folder and type the command
press enter
Click to expand...
Click to collapse
i don't fully understand what to do, can you be more detailed?
Noam_Nissel said:
i don't fully understand what to do, can you be more detailed?
Click to expand...
Click to collapse
ok
boot your device to the bootloader and select fastboot
then connect it to pc
now in your pc navigate to the folder where you have adb and fastboot(i assume you have installed sdk tools)
in that folder press shift + right click
you will see an option open a command window here
then a black window will appear
in that window type the command and press enter
but don't forget first to place the boot.img to the adb/fastboot folder
rzr86 said:
ok
boot your device to the bootloader and select fastboot
then connect it to pc
now in your pc navigate to the folder where you have adb and fastboot(i assume you have installed sdk tools)
in that folder press shift + right click
you will see an option open a command window here
then a black window will appear
in that window type the command and press enter
but don't forget first to place the boot.img to the adb/fastboot folder
Click to expand...
Click to collapse
i have this problem agian, and it doesnt help this time
Noam_Nissel said:
i have this problem agian, and it doesnt help this time
Click to expand...
Click to collapse
what kind of problem and what did you do now?
rzr86 said:
what kind of problem and what did you do now?
Click to expand...
Click to collapse
every rom im installing is getting me into bootloop, i've tried to install from revcovery and from fastboot, and it always the same problem
Noam_Nissel said:
every rom im installing is getting me into bootloop, i've tried to install from revcovery and from fastboot, and it always the same problem
Click to expand...
Click to collapse
i replied in the other thread
Does S-on and S-off matter for this issue?
Hi,
I am facing the same issue, my Sensation z710e is stuck in Cyanogenmod boot logo. following are the details.
bootloader unlocked
s-on
rooted
cwm recovery installed
tried latest CM10 for pyramid devices
I didnt try 'fastboot flash boot boot.img' command yet but i would like to know if s-on matters, my device is already rooted with cwm recovery.
I am having a similar issue as well. I have followed the instructions in this thread [ROM][STABLE][Android 4.4.4] CyanogenMod 11 with 3.0.16 kernel [July 18, 2014]. I have followed all the steps including doing a full wipe, flashed the ROM zip, gapps zip, and the aroma installer for the flash kernel several times with the same result. My screen keeps getting stuck on the white HTC loading screen.
Currently I have restored my phone to my previous ROM using a backup through 4ext recovery (v1.0.0.6 RC2). My HTC Sensation 4G T-mobile is unlocked and rooted with s-on. I have smartflash enabled on 4ext and my ROM is currently stock android 4.0.3. I did search the above mentioned thread for similar issues and a potential solution but none of the things I tried worked.
I would appreciate any help on how to fix this problem. If you need additional information I would be glad to provide it.
Tried another re-install today and everything worked fine, I guess the 5th time is the charm? I still don't know why it didn't work the other times, I did the exact same thing each time.