So I screwed up and cleared my wiped my phone then when I went to flash CM 11 from Pacman I got a failure so I couldn't flash the ROM and it cleared out my Pacman as well so I didn't have any ROMs on my phone and no ROM installed so it would just boot to recovery (i use TWRP). When i tried to put a ROM on to my phone through my computer I got an error and when I tried to use the ADB Sideloader but it just got stuck saying"waiting for device." So I went ahead and re-locked my boot loader and tried to restore the phone with the stock RUU but it just fails every time and I have let it run for an entire day before. So at this point I have an AT&T HTC One that boots to a boot loader then says tampered, re-locked and security warning on the top i can use fast boot (but not sure what to do with it) no ROM to boot to, and cant get to TWRP (unless I unlock boot loader again). Any recommendations would be very helpful.
crabbymonkey said:
So I screwed up and cleared my wiped my phone then when I went to flash CM 11 from Pacman I got a failure so I couldn't flash the ROM and it cleared out my Pacman as well so I didn't have any ROMs on my phone and no ROM installed so it would just boot to recovery (i use TWRP). When i tried to put a ROM on to my phone through my computer I got an error and when I tried to use the ADB Sideloader but it just got stuck saying"waiting for device." So I went ahead and re-locked my boot loader and tried to restore the phone with the stock RUU but it just fails every time and I have let it run for an entire day before. So at this point I have an AT&T HTC One that boots to a boot loader then says tampered, re-locked and security warning on the top i can use fast boot (but not sure what to do with it) no ROM to boot to, and cant get to TWRP (unless I unlock boot loader again). Any recommendations would be very helpful.
Click to expand...
Click to collapse
Unlock it again, run the ruu exe.
Only reason to go through the relock **** is to warranty it.
Sent from my One using Tapatalk
crabbymonkey said:
So I screwed up and cleared my wiped my phone then when I went to flash CM 11 from Pacman I got a failure so I couldn't flash the ROM and it cleared out my Pacman as well so I didn't have any ROMs on my phone and no ROM installed so it would just boot to recovery (i use TWRP). When i tried to put a ROM on to my phone through my computer I got an error and when I tried to use the ADB Sideloader but it just got stuck saying"waiting for device." So I went ahead and re-locked my boot loader and tried to restore the phone with the stock RUU but it just fails every time and I have let it run for an entire day before. So at this point I have an AT&T HTC One that boots to a boot loader then says tampered, re-locked and security warning on the top i can use fast boot (but not sure what to do with it) no ROM to boot to, and cant get to TWRP (unless I unlock boot loader again). Any recommendations would be very helpful.
Click to expand...
Click to collapse
what ruu are you trying that fails? when does it fail ?
go here and get the correct way to reset you phone to stock
http://www.htc1guru.com/downloads/stock-rom-downloads/ Guru Reset
Thats the same one and I downloaded the RUU for the forth time and it worked I guess I got unlucky. all is good now thanks for the help.
Related
I am having one hell of a time installing the new 4.0.3 Android (Ice Cream Sandwich) update. Everything was going smoothly, downloaded update, atempted to install, but then it got stuck on the HTC logo loading screen when I first boot the phone.
Attempted factory reset, did not work. Attempted recovery, which i was prompted with a phone logo with a red exclimation mark. From there, i help Vol up and power button to get to another screen, wiped cache and attempted another factory reset. Nothing.
I have been looking into re-flashing the phone manually ( i know that this may void the warranty, but due to my location, sending it out is NOT an option). I have downloaded a ripped version of the OEM ROM that the phone came stock with, placed it in a freshly reformatted SD card, then i went back into the boot loader. Immediately, the phone picked it up, and I let the phone do its thing, still nothing.
Am I doing something wrong, or is my phone complete botched past the point of no return?
Any help regarding this issue is GREATLY appreciated. Don't make me go back to using my BB Torch >.>
I talked to a rogers customer support agent, who transfered me to a technician. The reason my phone will load the new ROM, but fail to reboot is because the internal memory is fried. The reason the phone failed during an update and not from regular use is because i NEVER shut off my phone, and the OS was always loaded.
Good thing flashing the phone dosen't void the warranty
Akutalji said:
I talked to a rogers customer support agent, who transfered me to a technician. The reason my phone will load the new ROM, but fail to reboot is because the internal memory is fried. The reason the phone failed during an update and not from regular use is because i NEVER shut off my phone, and the OS was always loaded.
Good thing flashing the phone dosen't void the warranty
Click to expand...
Click to collapse
I had the same issue, but could easily pass through.
The thing is that my original rom was android 2.3, and i wanted to update to ics 4
So i restored the original rom then done, like you the htc update.Wehn the phone has reboot, i faced the same problem as yours.
To make the phone boot correctly, i simply get the boot.img from the latest "TeamGenesis3DRom" then "fastboot flash boot boot.img"
then "fastboot reboot" ans the phone starts correctly.
Hope it will help you.
If you are on s-on you will alwais need to flash new roms using fastboot. You need to upload the boot.img in cmd on your computer. I would open the rom and copy it over to the folder that i used to unlockboot loader then open cmd on your computer then type cd \rootevo3dnew then type fastboot flash boot boot.img. Before you download anny other roms you need to get 4ext recovery from play store. That recovery will work every time you want to flash new roms when your on s-on without having to use your computer.
Install Custom Rom
I didnt read ur second post. I was suggesting u to install custom ROM. I hope ur poblem solved by now.
Arceo85 said:
If you are on s-on you will alwais need to flash new roms using fastboot. You need to upload the boot.img in cmd on your computer. I would open the rom and copy it over to the folder that i used to unlockboot loader then open cmd on your computer then type cd \rootevo3dnew then type fastboot flash boot boot.img. Before you download anny other roms you need to get 4ext recovery from play store. That recovery will work every time you want to flash new roms when your on s-on without having to use your computer.
Click to expand...
Click to collapse
I totally agree with.
But this case is very particular.
I can tell because i'm S-OFF and can flash any rom i wanr whithout fastboot.
But in this particular case, even with taking the boot.img from the rom deployed by HTC and then flash it through fastboot, the phone didn't passed the HTC screen.
As i said, i had to take the boot.img from a custom rom (in his case it was a predator or genesis rom).
Akutalji said:
I am having one hell of a time installing the new 4.0.3 Android (Ice Cream Sandwich) update. Everything was going smoothly, downloaded update, atempted to install, but then it got stuck on the HTC logo loading screen when I first boot the phone.
Attempted factory reset, did not work. Attempted recovery, which i was prompted with a phone logo with a red exclimation mark. From there, i help Vol up and power button to get to another screen, wiped cache and attempted another factory reset. Nothing.
I have been looking into re-flashing the phone manually ( i know that this may void the warranty, but due to my location, sending it out is NOT an option). I have downloaded a ripped version of the OEM ROM that the phone came stock with, placed it in a freshly reformatted SD card, then i went back into the boot loader. Immediately, the phone picked it up, and I let the phone do its thing, still nothing.
Am I doing something wrong, or is my phone complete botched past the point of no return?
Any help regarding this issue is GREATLY appreciated. Don't make me go back to using my BB Torch >.>
Click to expand...
Click to collapse
the easiest way to fix your issue is to download the latest RUU from here then just rename it to PG86IMG, but first you have to relock your bootloader, vol down + power, then go to fast boot and type in command prompt "fastboot oem lock" and once you have the RUU on the root of your SD card boot back into bootloader and it will say **relocked** and then it will recognize the "PG86IMG" and it will check the file and ask you if you want to update, it will then install and everything should be hunky dory, I recommend after that, unlock your bootloader again via the HTCdev method and then make your phone s-off and then start flashing roms as often as you want without any issues
Arceo85 said:
If you are on s-on you will alwais need to flash new roms using fastboot. You need to upload the boot.img in cmd on your computer. I would open the rom and copy it over to the folder that i used to unlockboot loader then open cmd on your computer then type cd \rootevo3dnew then type fastboot flash boot boot.img. Before you download anny other roms you need to get 4ext recovery from play store. That recovery will work every time you want to flash new roms when your on s-on without having to use your computer.
Click to expand...
Click to collapse
Just for the hell of it, I tried it.
I downloaded fastboot, and got my hands on the stock .img for the evo. Still the same issue, the bootloader loads the new image but never asks to reboot.
Memory is fried They are now sending me a new phone
First of all i've been searching for a way to fix this for hours now without a solution.
My problem is as follows:
i installed official miui beta and got stuck with a boot loop, i was running 4text recovery but i wanted to try something different so i flashed twrp recovery in fastboot. however whenever i try to go into recovery now it just reboots and goes into boot loop again, so i cannot access recovery or boot into my rom.
I have tried flashing several recoverys via fastboot but each time it just reboots and does not enter recovery.
i have also tried rebooting into recovery using fastboot reboot recovery and adb reboot recovery but still it didn't work.
i have flashed another boot.img but now it just gets stuck on miui screen instead of boot loop
is there any way i can get any recoverys to work? i have tried looking for a 4text recovery.img as 4text was the last recovery to work but i can only seem to find the app that flashes it.
i have also tried flashing a rom through fastboot by typing fasboot flash zip rom.zip but it just says failure.
i am now downloading RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_radio_11.77.3504.00U_11.25.3504. and am going to try rename it to PG86IMG and update through bootloader after relocking it and then unlocking it again but i am not sure that will work.
in short i flashed a new recovery but it just reboots device when i try and enter it and the rom i am on happens to be stuck on boot loop so i cannot get in rom or recovery and flashing a new recovery does not work.
BTW i am S-ON HBOOT-1.49.0018
sorry for the lengthy post and also any grammatical errors as i am tired
Comments withdrawn
zcink said:
The whole problem, which is always the problem is you are S-ON. The MIUI rom will NOT run unless you install the newest firmware. You cannot install the newest firmware with S-ON because it is locked up in a partition that you cannot access unless you go s-off.
Has nothing to do with the recovery. I've been using 4ext recovery pretty much the whole time I've owned my EVO 3d and never had one single problem with it.
There are roms you can run with s-on but not the MIUI one.
Click to expand...
Click to collapse
cool, didn't know that, my problem now then is how can i reflash a different rom, bearing in mind that i cannot access recovery? do you think putting the pg86img stock ruu thingy on my sd and letting bootloader install that will work?
powellyable said:
cool, didn't know that, my problem now then is how can i reflash a different rom, bearing in mind that i cannot access recovery? do you think putting the pg86img stock ruu thingy on my sd and letting bootloader install that will work?
Click to expand...
Click to collapse
I do believe that if you are s-on, you should be able to relock the phone and then run the rru from your computer.
sonza said:
I do believe that if you are s-on, you should be able to relock the phone and then run the rru from your computer.
Click to expand...
Click to collapse
My next step was to relock it and run the ruu through bootloader, can you do it through computer/fastboot?
Sorry, I haven't been on the forum for a while.
Read the following link,
http://forum.xda-developers.com/showthread.php?t=1194053&highlight=relock
It should help you with the process.
The rru file you have should be an executable file that the name ends with "signed.exe" if memory serves. I do believe you can run this from your windows desktop if you are using windows. The link above has the adb command to use to relock the phone.
Once you are up and running again, you can install an ics rom even if you have s-on. I am running one but there are a few steps you need to do in the correct order so you don't end up where you are.
Good luck and have a great weekend!
Here is another good link to do what you are wanting to do.
http://forum.xda-developers.com/showthread.php?t=1578977
This might be even easier for you.
Comments withdrawn
I'm trying to help my friend get his Amaze up and running again. When he gave it to me it would not boot past the bootloader. You could get into recovery but were unable to flash anything as it said there was an error mounting the internal sd.
I read through some threads here and attempted to reinstall recovery, which didn't go so well. Now I am unable to get into recovery, which means i have no adb now , unable to flash the ruu through the hboot. It will load the ruu but will just reboot to the bootloader again.
Hboot - 1.93.0002
S-on
CID - Telus001
He told me that he had tried to flash the new faux kernel, after which he was in the spot he's in. He has already replaced with an S3, but would like to get this phone up and running to sell and recoup some of his upgrade costs, plus get pictures off the Amaze (if that's at all possible)
Update: got it working, had to flash the non touch cwm, 4ext twrp and touch cwm all would not work. Afterwhich i was able to flash a rom, then flashed a kernel through fastboot. Downside is the internal was blank upon booting back....but it at least works again.
SOLVED
Hey, I have htc evo 3d gsm (shooteru). I unlocked the bootloader using htcdev.com and installed clockworkmod recovery. Then I changed cid to HTC__001 and tried to flash a gingerbread ROM in preparation for using the flashmaniac tool to downgrade my hboot (1.53.0007 -> 1.49.0007).
But when I tried to flash the gb rom the recovery said that installation finished but the phone did nothing after reboot. So I took out the battery and went into bootloader and everything looked the same as before the flash attempt. So I tried once again with same result. Then I powered off the phone and now when I turned it on again it only shows the HTC logo for a few seconds and then nothing (the buttons at the bottom have their lights turned on though).
Any ideas?
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
randomguyhtc said:
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
Click to expand...
Click to collapse
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I know , it just didn't work for some reason before.
So I flashed the boot.img and now it's stuck in a boot loop. Tried going to cwm recovery and wiping various caches etc and flashing again, and flashing boot.img again but it still goes into boot loop.
I would just use the flashmaniac's tool anyway because I don't care about any data on the phone or anything, but it seems that it requires the phone to be booted before it can start the downgrade.
What should I do? Try to flash other roms maybe? The one that I have now is EU_Shooter_U-1.20.401.8_ROOTED.
So I extracted a rom.zip from a RUU but it won't flash from cwm "Can't open /sdcard/rom.zip (bad)", should I try to flash it with adb/fastboot? I'm worried that the zip may be broken (even though archive manager integrity check says its fine).
Would this work with shooteru/GSM?
[TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset)
I'm thinking it might be a way to sidestep the boot loop problem that I have now, just relock the bootloader and follow the instructions until I get HBoot 1.40.something like the guy in the video?
Do I need some special drivers when using the RUU executables on Windows?
So I've got it to work. The problem was what jcfunk said (both of the things he mentioned, actually), I was trying to flash a GB rom when I should have tried an ICS rom instead (lol). After going to ICS RUU, I did the wire trick (unlimited.io) and now everything works nicely and I can get the latest roms.
Glad to hear.
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
geek-x said:
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
Click to expand...
Click to collapse
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
geek-x said:
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
Click to expand...
Click to collapse
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
es0tericcha0s said:
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
Click to expand...
Click to collapse
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
geek-x said:
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
Click to expand...
Click to collapse
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
es0tericcha0s said:
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
Click to expand...
Click to collapse
I tried flashing the firmware.zip file from the thread but I got a FAILED: (remote: not allowed) error in command prompt at the end of the process, what did I do wrong?
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
UPDATE:
Thank you so much es0tericcha0s, I really appreciate the support, I got the /data mount issue fixed finally. I just had to flash an older twrp recovery image and then reflashed the new one in fastboot and I could then flash CM successfully.
I can't believe I finally unbricked this phone, its been bricked since Sunday. Once again, es0tericcha0s, Thank you!
geek-x said:
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
Click to expand...
Click to collapse
You might need to RUU back then. If you have issues with the RUU exe, then you can extract the rom.zip and install it like you did the firmware. There are quite a few tutorials on how to extract it, or there might already be a version floating around for your phone.