Hi, so I just got a refurb One to replace my other One which is defective, and i have only been ablr to install twrp 2.6.3.3, every other version hangs on "entering recovery". And most roms completely fail to install woth this version, like for ex cm11 with L. Its bern completely frustraiting since something that shouldve taken me 10 mins (unlock,root,install rpm,s-off) took me over 7 hours (reflahing ruu, trying all versions of twrp & cwm, installing vm to run xp and be able to run htc tools, installing 8.1 and running htc tools to no avail)and i still cant flash a rom or aquire s-off. These are some of the specs of the replacement phone:
Hboot: 1.57
SWV: 6.10.531.9
Related
I have The sprint CDMA EVO 3D it was running the latest version of gingerbread and i had the bootloader unlocked running Hboot 1.50. I had team win recover version 2.0 installed as my recovery on the phone. All of the rest on the phone was all left at stock so there were no extra roms, it was the original HTC rom on the phone. So i was trying to flash the update through Teamwin 2.0 and it gave an error message after it unpacked everything saying "E: unknown command [firmware]". So i rebboted the system and now it will not even go past the HTC bootloader but it will still boot into fastboot and recovery. Is there anything i can do to get my phone back or what should i do!?!? Thanks for all your help!
jerwolfe said:
I have The sprint CDMA EVO 3D it was running the latest version of gingerbread and i had the bootloader unlocked running Hboot 1.50. I had team win recover version 2.0 installed as my recovery on the phone. All of the rest on the phone was all left at stock so there were no extra roms, it was the original HTC rom on the phone. So i was trying to flash the update through Teamwin 2.0 and it gave an error message after it unpacked everything saying "E: unknown command [firmware]". So i rebboted the system and now it will not even go past the HTC bootloader but it will still boot into fastboot and recovery. Is there anything i can do to get my phone back or what should i do!?!? Thanks for all your help!
Click to expand...
Click to collapse
I really don't know how else to say this, DON'T TAKE OTA'S IF YOU'RE ROOTED! OR UNLOCKED! lmao. you need to download the CD. http://forum.xda-developers.com/showthread.php?t=1563342
Since you can get into recovery, try flashing a different rooted ROM.
Save the Drama for your Mama with Tapatalk 2
If you can't get into fastboot or recovery, then I think your on your way to a sticky at the top of the development thread about being able to recover your phone.
I would also remove the battery for 10 min, hold down the power button. Reinsert battery, try to get into hboot and recovery and flash a backup.
The RUU.exe always fails and says error 170 USB device can't be found
Using windows 7 x64
I can't for the life of me get this damned thing to flash successfully.
http://forum.xda-developers.com/showthread.php?t=2004928//
I have tried reinstalling usb drivers
Installing htc sync manager
Using AIO toolkit to flash ruu from zip
flashing stock att recovery and then doing flash ruu from zip using aio tookit
Sideloading the zip provided by hasoon via twrp (assert failed write_raw_image status 7)
copying rom to phones internal storage and flashing via twrp
Unlocking and relocking the bootloader and retrying all methods previously stated
flashing boot.img provided in hasoon's recovery zip and retrying all methods.
I really need my phone back to stock so that I can make sure that my wifi low signal issue is infact hardware and not software.
Currently bootloader is unlocked and I have Evitare_UL PVT SHIP S-ON RL
HBOOT 1.32
What do I do? I feel like i'm all out of options.
sorry for my lack of contribution here, but mtp and this phone have me sooo [email protected]$$ed. I haven't been able to even establish a USB connect in about 2 months. I'm at the point of just throwing my phone at the wall and making a claim for a new one, sell the new one and pick up a something from Samsung. HTC can @&_$(& &4=(=! ! !!! !!! !!! 1! ! 1 !!!! 111!
/ rant
Managed to get it recovered after literally six hours.
This is what worked for me.
Have windows 7 x64 installed
Install HTC one x+ drivers from the product support page officially from htc
Install HTC Smart sync.
Boot into the boot loader and do a "fastboot oem lock"
Then run the proper RUU.exe
It managed to work. The wifi issue was definitely hardware. Just got a refurbished HOX+ from AT&T. Seriously want to trade for an S3 or something because this phone has given me nothing but issues.
I have a SPRINT HTC Evo 4G LTE and while trying to install CM10. It stayed on the custom boot screen. I found out that I needed a Kernal but I tried to figure it out on my own and I believe I deleted my OS in the process. SPECS - In bootloader my devices says "Tampered, Unlocked, S-On, HBOOT 2.09, Radio 1.12.11.1210" Inside TWRP 2.5.0.0 if trying to reboot it says NO OS Installed, and then it ask to install SuperSU, that my device is not rooted. Oooh, P.S. I never made a backup either. Stupid I Know. All I want is my stock OS back if anything. I hear about RUU but I'm having trouble doing anything. Trying to flash a rom, reroot the phone, nothing works. <<<<<<<<PLEASE HELP>>>>>>>
P.S. I did manage to install bootloader without a problem and at the time installed SuperSU. I saw it as an app. I never clicked on it or anything tho. I just processed to then install CM10 which all went well until waiting for it to boot and it never got off the custom boot screen.
So, I tried rooting my device with the WinDroid tool. It all worked out fine until I got a custom recovery in.
I got the bootloader unlocked just fine. I'm not sure where I went wrong, but it wiped everything off my device (including the stock ROM. I was going to make a backup this time too... I usually forget).
So, I spent a heck of a long time just trying to get something on. The RUU for Telus is 1.5x and my current device is at 1.2.
I've pretty much resigned myself to waiting for the 1.2 RUU for telus to be released, but until then, is there a way that I can get at least a custom ROM on?
After some mucking I can finally get a .zip pushed to my SD and start to install it. My /system wouldn't mount for the longest time. I had to do a full wipe/format on all partitions to a) get access to my system partition and b) get access even to the internal memory.
I downloaded Elegancia 7.2 and I can get the installer to start and it seems to run just fine and it should be installed.
I fastboot'ed the boot.img. However I'm still just stuck at the white HTC screen.
What device info would you like besides what I've already stated? Am I just using the wrong ROM? If so, what roms are compatible with hboot 1.4?
My CID is TELUS001.
Also, when I try to reboot TWRP it's saying that there is no OS installed....
Rev.Tyler said:
So, I tried rooting my device with the WinDroid tool. It all worked out fine until I got a custom recovery in.
I got the bootloader unlocked just fine. I'm not sure where I went wrong, but it wiped everything off my device (including the stock ROM. I was going to make a backup this time too... I usually forget).
So, I spent a heck of a long time just trying to get something on. The RUU for Telus is 1.5x and my current device is at 1.2.
I've pretty much resigned myself to waiting for the 1.2 RUU for telus to be released, but until then, is there a way that I can get at least a custom ROM on?
After some mucking I can finally get a .zip pushed to my SD and start to install it. My /system wouldn't mount for the longest time. I had to do a full wipe/format on all partitions to a) get access to my system partition and b) get access even to the internal memory.
I downloaded Elegancia 7.2 and I can get the installer to start and it seems to run just fine and it should be installed.
I fastboot'ed the boot.img. However I'm still just stuck at the white HTC screen.
What device info would you like besides what I've already stated? Am I just using the wrong ROM? If so, what roms are compatible with hboot 1.4?
My CID is TELUS001.
Also, when I try to reboot TWRP it's saying that there is no OS installed....
Click to expand...
Click to collapse
Update -----------------
I'm a tool. I was using the international version of Elegancia.
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
simonsgray said:
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
Click to expand...
Click to collapse
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Thanks man. sig is a little out of date, i havent' needed xda as much since jumping to nexus. TWRP and i didn't do the s-off stuff. it says it needs a stock rom and i just havea spinning cyanogen mod. i will try install the 4ext and see if that changes the results.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
simonsgray said:
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
Click to expand...
Click to collapse
If you want to flash back to the stock ICS image you need to first relock your bootloader. When you relock it will say relocked when in hboot. The procedure is to place the image in the root of your external SD card and select from hboot. It should recognize and flash back to stock, however everything other than your external SD gets wiped in the process. So you need to make sure you have a good recent backup. Also, you remember when you first HTC dev unlocked they sent you an image to push to unlock? Well, I hope you saved it, because you'll need it again to re-unlock the bootloader after flashing the firmware image, but before attaining s-off.
However, if you were already on your carrier's latest ICS firmware before you started flashing different ROMs, you probably already have their latest radio. If you install the latest 4ext and enable smart flash, you'll probably succeed in installing any of the source built ROMs (ASOP, CM, PACman, evervolv) without s-off, because ROMs built from the source don't have the CID flag in their binaries.
If you still decide to go back and attain s-off the procedure is as follows: 1) relock your bootloader 2) flash the latest stock firmware for the carrier that sold your device. 3) Unlock your bootloader again using the image and commands you previously did to HTC dev unlock the first time, 4) get s-off using the wire-trick 5) flash the hacked hboot (and another radio if you desire, but not required for most ROMs) 6) super CID to remove all carrier locked file / partition limitations and protections 7) Flash your preferred recovery. Because you're now s-off you can use TWRP, CWM, or 4ext since the protected partitions are no longer an issue. 8) Flash any ROM you want provided it's based on ICS or later (below won't work because the radio is incompatible).
Edit: One other thing to note before starting any of this make sure your battery is fully charged. Also, the first time you boot after installing CM or any ASOP based ROM it can take quite some time to go through the process before you get to the login screen. For me it usually takes a little under 10 mins. It may at first appear to be a little sluggish until the rom settles, usually about 10-15 mins.
I hope this helps