i tried searching for help for this phone and nothing. i managed to get twrp 2.6 running but cant boot. i was doing fine till i updated twrp to 2.6 and flashed the cm10 boot.img with cm10 roms zip and had bootloop on htc screen. i tried erasing some stuff on the build prop that the cm10 thread said to erase for other carriers, still nothing. Now i cant even boor to my restore data still bootlooping the stock rom. i tried searching for the ruu but htcs website is broken. i can try and ruu using the verizon ruu but am not sure if it will have all verizon bloat and would lock my device to verizon. please help on this
Related
Ok,
A little back story is that I very recently downgraded my Hboot from 1.50 to 1.40 using the new downgrad methods that have come out. Before that I used the HTC Dev unlock with S-on, and now I am S-off by way of the Revolutionary unlock method.
I have always used clockwork recovery for flashing since it was the only one that was compatible with phones that were on Hboot 1.50 when I first rooted. I have never had any issues flashing any roms previously, and I have done so many many times before.
I noticed a few days ago when trying to flash the newest version of Viper rom, which I have had on my phone before on 1.50, that it would not flash. It gave me an error saying that the file was bad, and it would abort. I re-downloaded the file thinking it was corrupted and kept getting the same results.
I went on and found yet another new rom that I was intersting in trying that was an AOSP rom. This time it would get the majority of the way through flashing the rom and then fail with a status 1 error message when it got to the step of writing permissions.
Unlike the error with Viper rom this left my phone in a state where it could only boot to recovery since the rom that was on the phone was only partially installed.
The only instances I have seen on here where others have had this issue is when people are trying to flash roms that aren't for their phone, or they have a gsm evo 3D trying to flash a cdma rom. This is not the case for me as I am certain that the roms I am trying to flash are for the cdma 3D, and I am also sure that I have the cdma version.
For some reason Mean Rom is the only rom that will allow me to flash successfully at this point, and even that fails sometimes with the status 1 error message if I try to install it immediately after another rom has failed even if I wipe data/cache before attempting it. I have to reboot the phone into recovery again in order to get it to work.
I am very frustrated at this point considering the only reason I downgraded my Hboot was to have more freedom to flash roms without the extra wear and tear of having to use the computer or HTC Dumblock to get past Fastboot and into recovery.
Anyone have any ideas on this one? Any suggestions are greatly appreciated.
I mean no insult by this question, but have you tried a Modified Superwipe before flashing the ROMs? I usually clear Dalvik/Cache, install Modified superwipe, then clear D/C, then install the ROM, then clear D/C one more time for good measure.
I've also heard the people have trouble with CWM not flashing ROMs properly on the Evo3d. I was using TWRP 2.0 and switched to 4ext (see my sig) and have not had trouble with either. Have you tried switching recoveries?
The old CWM 4.0 something works well for the CDMA when it comes to wipe and flashing..
TWRP 2.0 even the later newer one had funky issues after a few days of using no full wipes to roms flashing funky to themes and icons showin up missing.
Always do a full wipe ..
Hey XDA,
I need some help with my HTC Amaze. I just installed the Android Revolution ROM for my phone, and I am now unable to get past the boot screen. I've been sitting here waiting for it to boot for 1/2 hour, before I took the battery out and tried booting again. Waited 1/2 hour again. Still no progress.
I had just made my phone S-OFF with SuperCID, and had flashed a new radio.img to my phone as recommended in the thread. After doing that, I went and used SuperWipe, and then I installed Android Revolution. Installation encountered no errors, so i was surprised when I was unable to boot.
I can still access 4ext recovery luckily.
Could some one help a noob out? Thanks.
Robert
EDIT: Wanted to point out that I was able to boot into my old rom after S-OFF, SuperCID and radio.img, but not after installing revolution rom.
Bro, why don't you try clearing data and cache from recovery, and then reboot.
Hope that helps, thanks
Thanks for the reply, but I figured out the problem.
I didn't flash the given ph85img which was the problem. So i flashed it, and now it works.
Only issue now is the mobile network wont connect and I am now unable to flash radio.img
Thanks
Ok so heres the deal. I have an HTC Evo 3D from Rogers in Canada and I had an unlocked bootloader and S-OFF (currently (re)locked and S-OFF). I was running the stock Rogers Rom but with CWM recovery. Yesterday I downloaded the new OTA update for android 4.0 with sense 3.6 and of coarse I found out that custom recoveries won't flash stock HTC zips, and I wanted this new update. So I downloaded the official stock RUU and tried to reflash to a "true stock" form so I could update the phoen. First error I encountered when trying to use the RUU was "error 131 Customer ID error", which I found out was a problem with the CID of the phone (don't know how it was changed). Tried setting the CID to ROGER001, which is supposedly the default CID, but the RUU still would still get the CID error. So I changed the CID to 11111111 (superCID) through fastboot and tried the RUU again. It worked this time but now I'm stuck at the HTC sceen and the phone will not boot.
I have tried manually flashing the boot.img from the RUU through fastboot. Also since I'm still S-OFF and i tried reflashing CWM recovery and tried flashing an assortment of ROMs including the backup of the stock ROM that I was just on and NO rom would boot. Roms with custom boot animations would get past the HTC logo but then just sit loading forever but never actually finish booting. Also tried flashing the RUU via the bootloader by renaming the rom.zip to PG86IMG.zip and still nothing. I still have access to the bootloader and fastboot and recovery. RUU flash completes everytime I try it but never boots, and nobody seems to have had the same problem as me after using an RUU.
I am at a complete loss for what to try next and really need help.
Hboot of my phone is 1.49.08
SOLVED
Finally got the phone working again today. Looks like the RUU I was using may have been corrupt and wasn't playing nice with the ROGER001 CID. Finally was able to sucessfully download the 3.28 RUU and tried loading that after changing the CID back to ROGER001 and BAM! phone booted up after that. Crappy thing was I thought it was dead for good so I ended up going out and buying the new Galaxy S III for $650+tax :laugh:. Oh well the GS3 is a better phone anyways haha.
Point is my original problem is now solved so mods can delete this or move it or whatever.
Hello all,
I am brand new to the android community, and have come accross a problem that I can't seem to get fixed. I previously rooted/rom'd my EVO lte with mean rom a while back. I started to have wireless issues so I decided to spend some time learning/fixing the problems that I'm sure my noobness created.
I relocked my phone and unrooted it back to factory 2.13.651.1. After doing that I updated my phone via Sprints OTA updater. I recieved an update that took me to 3.16.561.3. After that was completed I preceeded to unlock my bootloader again and installed TWRP 2.4.1.0. When I try to install any ROM it appears to go well in TWRP, but it reboots right after it says "updating kernel, this may take a while". When it reboots it sits at the HTC white startup screen, it doesnt even flash the red developer letters under the HTC logo like it normally does when continuing to boot into recovery or the old ROM.
I did some search and have found that others had issues with TWRP 2.4.1.0 (http://forum.xda-developers.com/showthread.php?t=2048229&page=573). They rolled back to 2.4.0.0. The problem is that with the OTA update the touch sence in TWRP is broken unless you run 2.4.1.0.
Anyone else run across ths issue?
The solution is probably staring me in the face but my noob aura is blocking it. :silly:
TWRP 2.4.1.0 broke something with flashing so you might have to relock and ruu to get back to normal. The problem is there is no ruu out for 3.16 and running the ruu for 3.15 may mess up your phone. I would try to flash the kernel separately by flashing with fastboot or flashgui and see if that allows it to boot into the rom. You may be able to run dirty racun and gain s-off since the hboot didn't change with the latest update.
Waterheeter said:
Hello all,
I am brand new to the android community, and have come accross a problem that I can't seem to get fixed. I previously rooted/rom'd my EVO lte with mean rom a while back. I started to have wireless issues so I decided to spend some time learning/fixing the problems that I'm sure my noobness created.
I relocked my phone and unrooted it back to factory 2.13.651.1. After doing that I updated my phone via Sprints OTA updater. I recieved an update that took me to 3.16.561.3. After that was completed I preceeded to unlock my bootloader again and installed TWRP 2.4.1.0. When I try to install any ROM it appears to go well in TWRP, but it reboots right after it says "updating kernel, this may take a while". When it reboots it sits at the HTC white startup screen, it doesnt even flash the red developer letters under the HTC logo like it normally does when continuing to boot into recovery or the old ROM.
I did some search and have found that others had issues with TWRP 2.4.1.0 (http://forum.xda-developers.com/showthread.php?t=2048229&page=573). They rolled back to 2.4.0.0. The problem is that with the OTA update the touch sence in TWRP is broken unless you run 2.4.1.0.
Anyone else run across ths issue?
The solution is probably staring me in the face but my noob aura is blocking it. :silly:
Click to expand...
Click to collapse
So u was on 3.16 and unlocked it? Did u use dirty racun? Did it work? Sorry I accepted ota and want s-off rooted if possible.
Sent from my EVO using xda app-developers app
polar2792 said:
So u was on 3.16 and unlocked it? Did u use dirty racun? Did it work? Sorry I accepted ota and want s-off rooted if possible.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I didnt use dirty racun to unlock, I used the fastboot method. I'm not developed enough in my knowledge to be s-off atm.
cruise350 said:
TWRP 2.4.1.0 broke something with flashing so you might have to relock and ruu to get back to normal. The problem is there is no ruu out for 3.16 and running the ruu for 3.15 may mess up your phone. I would try to flash the kernel separately by flashing with fastboot or flashgui and see if that allows it to boot into the rom. You may be able to run dirty racun and gain s-off since the hboot didn't change with the latest update.
Click to expand...
Click to collapse
On your notes I did some searching to learn what you were saying. First I tried to use the fastboot update 'meanbean-rom.zip' file but it produced errors:
archive does not contain 'android-info.txt
archive does not contain 'android-product.txt
error: update package has no android-info.txt or android-product.txt
I tried fastboot flash boot boot.img after extracting the boot.img from the .zip. After rebooting the phone stays on the white HTC logo screen but now populates the red dev notice. Looks like I'm going in the right direction
Thanks for your help so far.
I believe I have it figured out. I searched for an unofficial version of CWM recovery (all the XDA links for the evo lte have been removed for now due to bugs). I'll deal with those bugs as I was stuck without a phone until I got it figured out
Installed CWM 5.8.3.5 and flashed Meanbean Rom. Problem fixed
I'll put TWRP back on when they release a patch.
*Edit* spoke too soon. The touch interface doesnt work with meanbean due to the driver update (I'm guessing). Atlease I can see any missed calls now. lol
*Edit* Thanks to the D3rps I was able to get my phone up and going again. They had posted the stock 3.16 rom here: http://forum.xda-developers.com/showthread.php?t=2127947, with *Removed* recovery I was able to flash that rom. Now I just have to keep an eye out for the Meanbean update that will make it work with 3.16 touch.
**Edit** I removed the reference to the recovery I was using due to problems my noob self was not aware of. Thanks to Bigdaddy619 for his guidance, I now realize why no one is using it on the evo lte.
This is last resort. I've been at this for a while so please someone help out.
Got the phone.
Did the OTA update to Telus 1.20.661.1.
Unlocked and Rooted with AIO Toolkit.
Tryed to install a few roms to get rid of Sense (Venom XL+ 1.2.7). None worked and confirmed by others users with newer software.
Trying to get back to stock and can't do that either. Downloaded the "RUU_EVITARE_UL_JB_45_TELUS_WWE_1.15.661.11_Radio_1.09.55.17_18.20.95.55L_release_290307_signed" and get either USB or general errors 155/159
Can't figure out how to get back to an older firmware and stock rom/boot image.
Can someone please help?
HTC One X+ Telus unlocked
Soft. 1.20.661.1
kernel 3.1.10-g262c6aa
BB 2.14.55.11_18.21.95.55L
Build 1.20.661.1 CL164725
I have the same issues after the AT&T firmware update, I can't flash any ROM. The only one I can use is the stock nandroid backup.
I've tried everything with no avail.
I'll try with CWM recovery and let you know.
Sent from my HTC One X+ using Tapatalk 2
I was able to use CMW recovery and reinstall a backed up rom but since trying the RUU exe it worked just enough to wipe that so I don't have it anymore.
Where do I find a stock backup?
I'm reading in other threads that the RUU's don't work with hboot versions above 3.5. Not sure if that's why the RUU exe won't work for me or not.
Seems like very outdated files on HTCdev. Nice of them to break their last resort recovery tools and not bother updating them.
garmig said:
I have the same issues after the AT&T firmware update, I can't flash any ROM. The only one I can use is the stock nandroid backup.
I've tried everything with no avail.
I'll try with CWM recovery and let you know.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Did actually get it out of boot loop.
Had to catch it at a very specific position during start up to be detected long enough to flash the boot image.
Got it on the AT&T 1.19 rom now but really want to get rid of sense and get the Venom rom working. Wish I hadn't hit that upgrade button..
meboy said:
I was able to use CMW recovery and reinstall a backed up rom but since trying the RUU exe it worked just enough to wipe that so I don't have it anymore.
Where do I find a stock backup?
I'm reading in other threads that the RUU's don't work with hboot versions above 3.5. Not sure if that's why the RUU exe won't work for me or not.
Seems like very outdated files on HTCdev. Nice of them to break their last resort recovery tools and not bother updating them.
Click to expand...
Click to collapse
Because you have the new hboot, you cannot go back to an earlier rom. If you flash the rom from this thread http://forum.xda-developers.com/showthread.php?t=2235248 you should have updated stock. You will need to push the zip from the link to your phone with adb. You can then use TWRP or CWM to install rom and fastboot to flash the updated boot.img.
Thanks. I noticed others mention the hboot and RUU issue.
That's the rom I ended up getting to work. But it's stock only.
I haven't tried it yet but others are reporting that the AT&T 1.19 doesn't work with custom roms either.
artiemon said:
Because you have the new hboot, you cannot go back to an earlier rom. If you flash the rom from this thread http://forum.xda-developers.com/showthread.php?t=2235248 you should have updated stock. You will need to push the zip from the link to your phone with adb. You can then use TWRP or CWM to install rom and fastboot to flash the updated boot.img.
Click to expand...
Click to collapse
meboy said:
Thanks. I noticed others mention the hboot and RUU issue.
That's the rom I ended up getting to work. But it's stock only.
I haven't tried it yet but others are reporting that the AT&T 1.19 doesn't work with custom roms either.
Click to expand...
Click to collapse
HI, I've the AT&T's HOX+ with AT&T 1.19 boot, working with Viper+-v2.0.0; yes, with some lacks in the boot. I tested it with hxore_v1.0_ATnT.img (Kernel) and also with the embbeded in Viper, the Kernel boot-1.19.502.1, when the boot is sucess the device works fine ...