Related
I could really use some help here guys. Last night I flashed a new ROM - ThunderShed-v1.6_CM7.2-tbolt using Rom Manager/ClockworkMod (had been using CM7.1 without issue). I also updated the kernal to imoseyon_leanKernel_v6.2.1AOSP (didn't change ANY kernal settings) after reboot and install gapps. Everything seemed fine, however after powering off and back on again. I am now stuck in a boot loop. HTC screen phone vibrates, black screen, then HTC screen. I then attempted to boot into HBoot screen which I was able to do. Clicked on recovery and attempted to get into clockwork mod and restore the backup I'd created. Phone just reboots don't get to recovery and continuous HTC Screen black HTC Screen. This isn't my first rodeo with flashing roms (no expert by any stretch, but I'm pretty familiar with the process). Somehow I've screwed something up badly. I did attempt factory reset. I've also tried to downgrade to an older RUU although the RUU is loaded in HBOOT and seems to install (other than Bootloader is bypassed, due I believe because of Revolutionary ERROR - Can not roll back hboot version). Everything else Boot, recovery, system, splash1, userdata, etc all appear to update and show oK. After rebooting I'm back in the boot loop. I've tried installing stock roms rooted and unrooted without resolving the problem. ADB doesn't help either just never returns the device serial number. Loopfix just sits there waiting for device.
I'm am S-OFF (via Revolutionary)
-Revolutionary-
MECHA XD SHIP S-OFF
HBOOT-6.04.1002
MICROP-/
RADIO-1.16.00.0402w_1
eMMC-boot
Feb 23 2011,20:42:55
There is no PG05IMG.zip file on my SD card. (apparently can cause boot looping)
I googled to my hearts content, browsed every forum and blog I could to find a solution. Found similar issues but was not able to use any of the know fixes out there. Part of the problem is ADB doesn't see my phone. I've looked at 'loop fix' and 'thunderbolt all in one tool' these don't work for me. Any suggestions would be welcome. I'd prefer not to have to throw money at the problem to fix it.
I know I screwed the pooch on this one, maybe someone has the skills to help me unscrew it.
Thanks much in advance!
Rem
What happens when you connect the phone via USB? Does the computer detect it? You could try flashing cwm through hboot
sent from my jellybolt courtesy of the jester
dizzyman1180 said:
What happens when you connect the phone via USB? Does the computer detect it? You could try flashing cwm through hboot as PG05IMG. See if that works and you can get into recovery.
sent from my jellybolt courtesy of the jester
Click to expand...
Click to collapse
sent from my jellybolt courtesy of the jester
dizzyman1180 said:
What happens when you connect the phone via USB? Does the computer detect it? You could try flashing cwm through hboot
sent from my jellybolt courtesy of the jester
Click to expand...
Click to collapse
Windows 7 does signal that it sees a USB device but it shows unknown device. I've tried the HTC Drivers and the android USB drivers from google. Nothing doing. I am currently trying to install CWM via hboot (PG05IMG.zip). Got into CWM once tried to restore back to my backup but after the restore process same thing.
Thank you for your suggestions!
Rem
No problem. Report back with your progress.
sent from my jellybolt courtesy of the jester
dizzyman1180 said:
No problem. Report back with your progress.
sent from my jellybolt courtesy of the jester
Click to expand...
Click to collapse
UPDATE: Unable to get CWR through HBOOT.
Rem
I have the same problem.
I have a brand new(refurbished) thunderbolt. I recently installed
*07-25-2012* JELLYBLUR *V1.3* CM7.2 - SPJESTER Production
I completely wiped and cleared the device. All was running fine, until I unplugged it from the charger then poof, boot loop. I can also access hboot but nothing seems to work. I have flashed a few roms, but I'm out of my depth here.
I will try putting and image on the sd card, since it does try to flash a radio when it boots.
Either of you tried an RUU. Download 605.9 or 605.19, change it PG05IMG.zip and flash it through hboot, see if it goes through.
Sent from my ADR6400L using xda premium
I have successfully flashed both recovery, and the latest mr4 radio from hboot.
Without the sd card, I was able to get it booted once after each flash. Unplugging it forced it right back into boot loop(whether card was in or not).
The only options that work are hboot, and fast boot. Neither connects to adb, or the all in one tool.
Can I flash a regular rom from hboot? I have previous version of thundershed, and various stock roms on the SD card?
dizzyman1180 said:
Either of you tried an RUU. Download 605.9 or 605.19, change it PG05IMG.zip and flash it through hboot, see if it goes through.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I've tried RUU both .9 and .19 both seem to flash fine. But after reboot same boot loop. After trying a few more times flashing various RUU I flashed .19 again. After rebooting the phone I was able to get into the phone, everything setup fine, google account, wireless, etc. But after rebooting again. Back in same boot loop. I've also tried using 2 different SD card to rule out a bad SD. Unfortunately same thing. Starting to think this is hardware not a bad rom or firmware.
Rem
Ok I tried a factory wipe, no go either....
Tried installing regular rom renamed as "pg....." that didn't work.
So I've been told as long as you have hboot you can fix anything...Not sure whats next? At this point I'd be happy to start over.
Okay, I'm gonna try and see if I can get a dev to check out this thread for you guys. Because I am not sure what to tell you to do next at this point. Its exceeded my knowledge.
Sent from my ADR6400L using xda premium
dizzyman1180 said:
Okay, I'm gonna try and see if I can get a dev to check out this thread for you guys. Because I am not sure what to tell you to do next at this point. Its exceeded my knowledge.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Dizzyman any help is appreciated. Thanks for taking an interest and trying to help!
Rem
ok, I am not exactly sure what happened...I left my phone with no sim, no memory card and no battery alone for about 7 hours.
I came home with the intent to flash twrp from fastboot usb. I plugged it into usb port, put memory card and battery in. The phone on its own turned on, and voila it was in Clockwork.
Note the SIM card was not in the phone. I accidentally left it in the other tbolt I am replacing.
I factory wiped, cleared cache, and then installed thundershed from zip on SD. It has booted twice and seems to be running as it should be.
I put the sim card in and now its boot looping again. Removing the sim it boots and runs fine. The sim works fine on another thunderbolt, so I must assume the sim is fine.
I compared phones both were running the same rom and same radios. Kernels were different so I flashed imoseyon kernel to match the working phone. No go still boot looping.
Assurion sent me a "new" retail sim. Verizon told me to use my old one in the new phone. However the "new" phone will boot loop continuosly with old sim card. I have verified that the rom, radios, etc are all the same.
The mystery deepens...
tonyagee said:
ok, I am not exactly sure what happened...I left my phone with no sim, no memory card and no battery alone for about 7 hours.
I came home with the intent to flash twrp from fastboot usb. I plugged it into usb port, put memory card and battery in. The phone on its own turned on, and voila it was in Clockwork.
Note the SIM card was not in the phone. I accidentally left it in the other tbolt I am replacing.
I factory wiped, cleared cache, and then installed thundershed from zip on SD. It has booted twice and seems to be running as it should be.
I put the sim card in and now its boot looping again. Removing the sim it boots and runs fine. The sim works fine on another thunderbolt, so I must assume the sim is fine.
I compared phones both were running the same rom and same radios. Kernels were different so I flashed imoseyon kernel to match the working phone. No go still boot looping.
Assurion sent me a "new" retail sim. Verizon told me to use my old one in the new phone. However the "new" phone will boot loop continuosly with old sim card. I have verified that the rom, radios, etc are all the same.
The mystery deepens...
Click to expand...
Click to collapse
Attempted the above on my device but no luck. Just same reboot loop. Just FYI. Thanks for the tip.
Rem
Even the different sim, eventually led to the same issue. I finally just convinced assurian that my replacement phone is defective (which is may be).
The only thing I can think of is that the jelly rom, combined with the all in one root tool somehow made a bad situation or the phone is simply defective.
Now my task is to see if I can flash something to make this stock...lol...I really don't want to send back a phone to assurion with clockwork and revolution on it if I can help it.
I suspect its going to be tricky as ADB doesn't work..
Here is where I stand.
1. Flashed a stock room, through hboot
2. Flashed a stock hboot through hboot. (this didn't work, revolution is locked)
3. I rebooted back to hboot.
4. removed sim card, and sd car.
5. Then I selected "Recovery" it went into standard recovery i let it sit for a bit, then it rebooted on its own back to stock, unactivated state.
I used the files from this thread
After this is seems to function perfectly normal, except I still have a revolutionary boot loader, and soff.
I let the phone reboot, and once it loaded I was able to get adb to work perfectly fine. I then returned to the above guide and fixed the boot loader, and s-off as directed. Its now completely stock. I mean it might be a version or so from whats current but a simple ota update would take care of it.
Its all brand new...Of course, I am still going to return it to asurian as I have no idea if it had a hardware issue, or what it was.
tonyagee said:
Here is where I stand.
1. Flashed a stock room, through hboot
2. Flashed a stock hboot through hboot. (this didn't work, revolution is locked)
3. I rebooted back to hboot.
4. removed sim card, and sd car.
5. Then I selected "Recovery" it went into standard recovery i let it sit for a bit, then it rebooted on its own back to stock, unactivated state.
I used the files from this thread
After this is seems to function perfectly normal, except I still have a revolutionary boot loader, and soff.
I let the phone reboot, and once it loaded I was able to get adb to work perfectly fine. I then returned to the above guide and fixed the boot loader, and s-off as directed. Its now completely stock. I mean it might be a version or so from whats current but a simple ota update would take care of it.
Its all brand new...Of course, I am still going to return it to asurian as I have no idea if it had a hardware issue, or what it was.
Click to expand...
Click to collapse
Tonyagee that's for the step by step. Tried on my Tbolt. Still boot looping. I appreciate you documenting what you did THANK YOU!
Your welcome...I definitely was on the edge of my skill set for sure....
So my thunderbolt is is in the same boat. The main cause for the boot looping seems to come from unplugging the usb from charging.
Mine will randomly stop the infinite boot looping and boot up. Sometimes it's quick. Sometimes it will take hours.
Most of the time when I manage to get it to run it is very difficult to get back into a custom recovery. It has to reboot the phone to get into recovery which most of the time just puts it into the infinite boot loop again.
If I plug mine into a computer it will charge but will not recognize the phone.
I've tried every fix known to man. No luck. I've come to deal with it as I've had this problem for two or three months now.
Sent from my ADR6400L using Tapatalk 2
---------- Post added at 08:09 PM ---------- Previous post was at 07:37 PM ----------
tonyagee said:
ok, I am not exactly sure what happened...I left my phone with no sim, no memory card and no battery alone for about 7 hours.
I came home with the intent to flash twrp from fastboot usb. I plugged it into usb port, put memory card and battery in. The phone on its own turned on, and voila it was in Clockwork.
The mystery deepens...
Click to expand...
Click to collapse
Mine has done the same thing. I read that one of the failsafe ways to boot up clock work mod recovery is that it will automatically boot up after a battery pull and turn the phone back on with it plugged in.
If I plug the phone in while it is completely shut down it automatically powers it on and 9 times out of 10 it randomly reboots but sometimes it will boot up into recovery.
Sent from my ADR6400L using Tapatalk 2
i just upgraded to 2.2.1 and now my phone keeps rebooting when i try to do anything with system (wipe or write a new rom). phone continually rebooting, if my current rom tries to load phone reboots again.
when i plug in light does not come on...
any ideas or is this thing dead? i can still get into recovery and have some battery life just not sure what to do... already reflashed recovery
seems like my /system/ is hosed not sure how to fix if possible
tried nandroid restore.. it reboots
tried to reflash existing.. it reboots
i can still get into recovery though but if i do anything with 'system' it reboots
any ideas how to get that fixed or probably have to replace? i cant even overwrite my custom boot logo. ugh lol
Try relocking the bootloader, then fast boot the ruu
Sent from my EVO using xda app-developers app
jdizzle316 said:
Try relocking the bootloader, then fast boot the ruu
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
thanks im downloading the RUU..
How exactly did you update to the newest base?
Figured I would update this thread in hopes of helping someone else if they get stuck here.
I had upgraded to the new base with PJ75IMG and that went well - had used other ROMs on that new base.
What had happened was I was flashing venom on TWRP 2.2.0 and it rebooted phone when it hit system (why system was damaged in first place not sure, i had just rebooted into recovery).
I had to oem lock, ruu, oem unlock (even though it said s-off for lazypanda it was not working) and then i was able to re-flash twrp (this time pushed 2.2.1 through fastboot).
I've put a lot of evo's in bad spots but the behavior I saw on this was new for me.. Anything I touched 'system' from twrp or if my rom tried to load, phone would cycle. Light would NOT go on when plugged in.
Either way rocking new rom and am good! thanks guys
I went to OTA update MeanRom from 3.1 to 3.2 and after the rom install and reboot my phone kept rebooting, I waited for about 45 minutes just make sure it wasnt going to take.
I then used fastboot to install my last recovery however, the recovery install froze at installing /system for over an hour. I had no choice but to try and reboot as none of the buttons worked. I am now stuck at the HTC screen and can not get into fastboot or phone.
I've tried searching for a solution for a day and still have had no luck. Cant run RUU as it has a USB error which I expected as the phone never boots.
Any help is greatly appreciated.
I am/was on latest radio/firmware/s-off.
Thanks for looking!
evoman said:
I went to OTA update MeanRom from 3.1 to 3.2 and after the rom install and reboot my phone kept rebooting, I waited for about 45 minutes just make sure it wasnt going to take.
I then used fastboot to install my last recovery however, the recovery install froze at installing /system for over an hour. I had no choice but to try and reboot as none of the buttons worked. I am now stuck at the HTC screen and can not get into fastboot or phone.
I've tried searching for a solution for a day and still have had no luck. Cant run RUU as it has a USB error which I expected as the phone never boots.
Any help is greatly appreciated.
I am/was on latest radio/firmware/s-off.
Thanks for looking!
Click to expand...
Click to collapse
Have you tried getting into recovery from the boot loader and flashing a rom
Sent from my EVO using xda premium
evoman said:
I went to OTA update MeanRom from 3.1 to 3.2 and after the rom install and reboot my phone kept rebooting, I waited for about 45 minutes just make sure it wasnt going to take.
I then used fastboot to install my last recovery however, the recovery install froze at installing /system for over an hour. I had no choice but to try and reboot as none of the buttons worked. I am now stuck at the HTC screen and can not get into fastboot or phone.
I've tried searching for a solution for a day and still have had no luck. Cant run RUU as it has a USB error which I expected as the phone never boots.
Any help is greatly appreciated.
I am/was on latest radio/firmware/s-off.
Thanks for looking!
Click to expand...
Click to collapse
I'm confused...You were flashing a recovery from fastboot? Or were you doing a nandroid restore? You tried holding volume down + power to get into the bootloader right?
Sent from my EVO LTE
I can not get past the first HTC screen. Holding power and volume down wont work as it wont get past the first screen. I was using a Nandriod.
Thank you.
evoman said:
I can not get past the first HTC screen. Holding power and volume down wont work as it wont get past the first screen. I was using a Nandriod.
Thank you.
Click to expand...
Click to collapse
Did you do the restore from recovery (TWRP) or did you use fastboot? I ask because fastboot isn't typically used to restore from a nandroid backup, so just trying to understand your description. Do you have adb on your pc?
Sent from my EVO LTE
premo15 said:
Did you do the restore from recovery (TWRP) or did you use fastboot? I ask because fastboot isn't typically used to restore from a nandroid backup, so just trying to understand your description. Do you have adb on your pc?
Sent from my EVO LTE
Click to expand...
Click to collapse
I apologize I really wasnt clear. I was using TWRP. I just uninstalled it a couple of weeks ago I will go grab it again right now.
evoman said:
I apologize I really wasnt clear. I was using TWRP. I just uninstalled it a couple of weeks ago I will go grab it again right now.
Click to expand...
Click to collapse
Gotcha...then this is very strange. Once you have adb installed, try plugging the phone into your pc, power it on and when it's at the HTC screen try the "adb reboot recovery" command and see if that gets you into TWRP. I've never tried using adb from that screen so not sure if the phone is capable of communicating at that point, but worth a shot...
Sent from my EVO LTE
Ok installed r20.0.3 of Andriod SDK. I installed Andriod SDK platform tools REV 14. Now what should I do?
premo15 said:
Gotcha...then this is very strange. Once you have adb installed, try plugging the phone into your pc, power it on and when it's at the HTC screen try the "adb reboot recovery" command and see if that gets you into TWRP. I've never tried using adb from that screen so not sure if the phone is capable of communicating at that point, but worth a shot...
Sent from my EVO LTE
Click to expand...
Click to collapse
Premo, I tried that but I get an error device not found. However, I do hear my laptop make the usb connecting noise when I plug in my phone.
Any other suggestions?
Thank you
evoman said:
Premo, I tried that but I get an error device not found. However, I do hear my laptop make the usb connecting noise when I plug in my phone.
Any other suggestions?
Thank you
Click to expand...
Click to collapse
That's what I was afraid of...the only other thing I can think of is to maybe try flashing a new boot image, but you may have the same problem you had with adb in not being able to communicate with the phone. What you would need to do is pull the boot.img file out of the MeanROM zip, put it somewhere on your PC, then with your phone plugged in open the command prompt and type:
Code:
fastboot flash boot <path_to_boot_img>boot.img
It's basically the same process as installing a new kernel on the new hboot version, which is outlined here:
http://forum.xda-developers.com/showthread.php?t=1794867
Typically you have to be in the bootloader for this, but it's worth a try from the HTC screen. I've been successful with the fastboot command when adb does not see the device, so may work in this case as well. If not, then I'm out of ideas. Since you can't get to the bootloader, you should be able to take it into sprint or best buy without them knowing you tampered with it. Just tell them you took the latest OTA and the battery died during the installation or something. Hopefully they will exchange it, but you run the risk of getting one with the new hboot and losing S-OFF Better than no phone at all though, I suppose...
Not too sure if u have a recovery installed but regardless you should be able to simulate a battery pull by holding power button for 10 seconds or until the captive button lights flash 12 times I think. When the phone powers down press and hold volume down only and you should boot into boot loader. From here you should have a better chance of using adb or fastboot or recovery if you have twrp installed. If you can get to boot loader you have options especially since your s-off.
Good luck man
Sent using my LTEVO
Ok I was able to get into bootloader and tried to flash MeanRom after wiping cache/dalvik/factory reset/system three times each with a new download of MeanRom and it said it flashed successfully. I rebooted and it keeps getting almost to setup then reboots. Should I try an RUU again? If so what version should I use?
Bootloader says:
Jewel PVT SHIP S-OFF RL
CID-SPSC_001
HBOOT-1.12.111
RADIO-1.05.11.0606
Thanks again!
evoman said:
Ok I was able to get into bootloader and tried to flash MeanRom after wiping cache/dalvik/factory reset/system three times each with a new download of MeanRom and it said it flashed successfully. I rebooted and it keeps getting almost to setup then reboots. Should I try an RUU again? If so what version should I use?
Thanks again!
Click to expand...
Click to collapse
That's good you can get into the bootloader, as previous poster said, you have a lot more options. I would save RUU as a last resort. See if you can flash a different ROM, like viper 4g or clean ROM. Or maybe an older version of mean ROM.
Sent from my EVO LTE
That's odd that after a full wipe mean ROM won't boot. Wasn't there issues with mean ROM if your recovery wasn't up to date. I would do a full wipe and try to restore a nandroid. Someone with more knowledge than me can defo help you . You can access bootloder, you have a recovery installed so you should be fine.
Sent using my LTEVO
are you on the latest version of TWRP? version 2.2.2, mean rom has had some issues with older versions...
bog3nator said:
are you on the latest version of TWRP? version 2.2.2, mean rom has had some issues with older versions...
Click to expand...
Click to collapse
No I wasnt so I just updated and will try again. Let you know soon. Thank you
Ok upgraded to the latest TWRP and tried MeanROM again. No go so now I will try CM10 to see if that works
Great news CM10 works and so does an old version of MeanROM guess I just cant run version 3.2 or 3.3. Thanks again for all of the help everyone! This place is the best.
Your phone must not like the new kernel.
Sent from my EVO using Tapatalk 2
thicklizard said:
Your phone must not like the new kernel.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I am not sure if that is all it is. I tried to install 3.3 and then flashed the stock kernel over it and still couldn't boot properly. Its ok it forced me to try CM10.
I unlocked my bootloader, flashed with Trickdroid, found some bug, then I decided to try the Renovation HD Rom. Got frozen during Aroma twice. Then I rebooted twice. Now my device is half-bricked. I can't get into recovery anymore. Tried CWM, TWRP. doesn't work. everytime I tried to get in recovery, it will just jump to the HTC screen. and after the HTC screen, it will reboot itself, and keep looping...
I want to try to restore using RUU, but there is NO RUU for AT&T version now.
I can't get in recovery, I can't get in the system.... I am stuck. Hopeless now.
Am I the first to brick a HTC ONE?
After 5 hours of struggling, IT got into the recovery again!!!!!!!!! didn't know what I did to make it work. and flashed with Renovation HD Rom and working now.
Update: If you keep getting boot loop, or can't get into recovery, try the ALL IN ONE kit and use the "erase cache", that fix my problem, and I learned it the hard way..
birdcarrie said:
I unlocked my bootloader, flashed with Trickdroid, found some bug, then I decided to try the Renovation HD Rom. Got frozen during Aroma twice. Then I rebooted twice. Now my device is half-bricked. I can't get into recovery anymore. Tried CWM, TWRP. doesn't work. everytime I tried to get in recovery, it will just jump to the HTC screen. and after the HTC screen, it will reboot itself, and keep looping...
I want to try to restore using RUU, but there is NO RUU for AT&T version now.
I can't get in recovery, I can't get in the system.... I am stuck. Hopeless now.
Am I the first to brick a HTC ONE?
Click to expand...
Click to collapse
Can you still get into Fastboot?
Use android debugging USB push over image may need to add time delay to allow next available time there is an opening to load image.
Good luck
HiddenSanctum said:
Can you still get into Fastboot?
Click to expand...
Click to collapse
Yes, I can still get in Hboot, and fastboot
Hi I am a complete noob and just got my HTC one and went way to fast with rooting my phone and may have a bricked phone as well. I unlocked the bootloader and flashed the clockwork mod recovery using the all in one kit. I proceeded to boot into the bootloader, and then went into the recovery. I backed up my phone at the point using clock work mod. I then wiped my phone to factory settings and wiped the cache. At that point I forgot that I had not put my ROM that I wanted to use on the phone storage. So i pressed reboot now. Obviously this was a mistake because there is nothing on the phone to boot off of. Now I have an HTC One that is not turning on no matter what I do and I have no idea where to start. Anybody know where I can start? It is also worth mentioning that I made another noob mistake by starting this process with 35% on my phone so is it possible that it is out of battery and not able to charge?
Charge battery copy ROM to SD card press volume up and power look for clockwork mod recovery go to SD card and install rom . Hopefully nothing more is required. Don't panic if clockworkmod is giving you brick sign usually its a sign you have wrong clockwork mod installed.
Sent from my Nexus 4
So I was trying to root/rom flash my wife's X+ to the Viper rom. I unlocked the bootloader from HTC, downloaded the all-in-one app, but it only had CWM on it, so I flashed CWM, pushed SU and installed SU with CWM, everything was fine. \
Loaded Viper rom on to internal memory, rebooted into CWM, installed Viper rom with full wipe. Phone rebooted, got Viper start up screen, booted to Viper lock screen, but when I unlock it, it shows a white screen with HTC on it, and wont let me get into anything. If I hold the home button, it says set up stopped responding, wait or close. I then reboot and all I get is a black screen with the battery, wrong time, and no signal at the top and then it resets it's self after about 2-3 mins. I cant get into the memory card or debugging before it reboots. What can I do to get the phone back functioning?
1. What method did you use to try to root? see above
2. Do have twrp or cwm installed? If so can you boot to recovery? CWM, yes
3. Can you boot to bootloader? Yes
4. What software version is phone on? 4.1.1
4. Does you pc recognize the phone when plugged in?
5. Does the phone boot at all? Yes
6. Can still get to fastboot? Yes
Do you flash boot.img?
HTC One X+ with Elegancia Rom Jelly Bean 4.1.1
rameriitoh said:
Do you flash boot.img?
HTC One X+ with Elegancia Rom Jelly Bean 4.1.1
Click to expand...
Click to collapse
yes, I pulled the one from the rom zip and flashed it
Mmm repeat the process flash the boot.img and flash the rom again, do you have a nandroid backup?
Sorry for my english :/
HTC One X+ with Elegancia Rom Jelly Bean 4.1.1
rameriitoh said:
Mmm repeat the process flash the boot.img and flash the rom again, do you have a nandroid backup?
Sorry for my english :/
HTC One X+ with Elegancia Rom Jelly Bean 4.1.1
Click to expand...
Click to collapse
i've tried, but i will try again when i get home from work tonight. and no, i didnt get a nandroid backup ...
Download other rom and try again
If you like flash the twrp 2.4, I had no problems with that
HTC One X+ with Elegancia Rom Jelly Bean 4.1.1
If you've updated the phone to the new firmware ( AT&T/Telus) the only roms you can flash are the one with new base.
@Turge posted two stock roms in the developer section.
http://forum.xda-developers.com/showthread.php?t=2235248&nocache=1
Sent from my HTC One X+ using Tapatalk 2
garmig said:
If you've updated the phone to the new firmware ( AT&T/Telus) the only roms you can flash are the one with new base.
@Turge posted two stock roms in the developer section.
http://forum.xda-developers.com/showthread.php?t=2235248&nocache=1
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
I've been "mentioned".. lol
Twiztidunreal said:
So I was trying to root/rom flash my wife's X+ to the Viper rom. I unlocked the bootloader from HTC, downloaded the all-in-one app, but it only had CWM on it, so I flashed CWM, pushed SU and installed SU with CWM, everything was fine. \
Loaded Viper rom on to internal memory, rebooted into CWM, installed Viper rom with full wipe. Phone rebooted, got Viper start up screen, booted to Viper lock screen, but when I unlock it, it shows a white screen with HTC on it, and wont let me get into anything. If I hold the home button, it says set up stopped responding, wait or close. I then reboot and all I get is a black screen with the battery, wrong time, and no signal at the top and then it resets it's self after about 2-3 mins. I cant get into the memory card or debugging before it reboots. What can I do to get the phone back functioning?
1. What method did you use to try to root? see above
2. Do have twrp or cwm installed? If so can you boot to recovery? CWM, yes
3. Can you boot to bootloader? Yes
4. What software version is phone on? 4.1.1
4. Does you pc recognize the phone when plugged in?
5. Does the phone boot at all? Yes
6. Can still get to fastboot? Yes
Click to expand...
Click to collapse
I assume you wiped data if you got the setup screen?
As @garmig said, if you updated the firmware and are on the latest HBOOT, you won't be able to flash ViperXL+ until I update it to the latest build. Did you take the OTA update?
Turge said:
I've been "mentioned".. lol
I assume you wiped data if you got the setup screen?
As @garmig said, if you updated the firmware and are on the latest HBOOT, you won't be able to flash ViperXL+ until I update it to the latest build. Did you take the OTA update?
Click to expand...
Click to collapse
yes, i wipped all data, cache, etc.
if that was the update that came out about a week or so ago, then yes i remember her saying something about an update from ATT.. How can I get another rom on there to flash if i cant get into ADB and debugging mode? ive tried the side load in CWM but i cant get it to connect, and the phone just sits there waiting.
I've always flashed galaxys and such, so im use to being able to remove the memory card and put what ever i needed on with a card reader. I just got my HTC One and now she wanted her OneX+ flashed for more options. Guess I didnt read close enough about the update.. and of course she is mad because she doesnt have a working phone at the moment, lol, GO ME!!!
Twiztidunreal said:
yes, i wipped all data, cache, etc.
if that was the update that came out about a week or so ago, then yes i remember her saying something about an update from ATT.. How can I get another rom on there to flash if i cant get into ADB and debugging mode? ive tried the side load in CWM but i cant get it to connect, and the phone just sits there waiting.
I've always flashed galaxys and such, so im use to being able to remove the memory card and put what ever i needed on with a card reader. I just got my HTC One and now she wanted her OneX+ flashed for more options. Guess I didnt read close enough about the update.. and of course she is mad because she doesnt have a working phone at the moment, lol, GO ME!!!
Click to expand...
Click to collapse
You can use the RUU from here keeping in mind that it will wipe your phones internal memory COMPLETELY!
or you could flash this rooted and deodexed version from here
Both are the new build 1.19.502.1
Twiztidunreal said:
yes, i wipped all data, cache, etc.
if that was the update that came out about a week or so ago, then yes i remember her saying something about an update from ATT.. How can I get another rom on there to flash if i cant get into ADB and debugging mode? ive tried the side load in CWM but i cant get it to connect, and the phone just sits there waiting.
I've always flashed galaxys and such, so im use to being able to remove the memory card and put what ever i needed on with a card reader. I just got my HTC One and now she wanted her OneX+ flashed for more options. Guess I didnt read close enough about the update.. and of course she is mad because she doesnt have a working phone at the moment, lol, GO ME!!!
Click to expand...
Click to collapse
First thing's first, what hboot version are you on? you can see that in the booloader screen. Mine is 1.32.0000 which is the previous version.
Anyways, ADB works in TWRP. I'm running 2.4.4.0 and I noticed it can take up to 30 seconds for it to start. You may want to start with that version: http://techerrata.com/browse/twrp2/evitareul
Once in TWRP, you can either use "adb push" or "adb sideload":
ADB Push:
Run "adb devices" until your serial # shows up
run "adb push c:\somefolder\rom.zip /sdcard/" to push the rom zip to your phone's sdcard. It can take up to 10 mins to transfer it this way. You can use one of these: http://forum.xda-developers.com/showthread.php?t=2235248
ADB Sideload:
While in TWRP, select Advanced then ADB Sideload
Type "adb sideload c:\somefolder\rom.zip"
Once flashed, reboot to bootloader and flash the boot.img then reboot your phone.
His wife is prob pissed lol I know mone would be
Sent from my HTC One X+ using XDA Premium HD app
TheJokah said:
You can use the RUU from here keeping in mind that it will wipe your phones internal memory COMPLETELY!
or you could flash this rooted and deodexed version from here
Both are the new build 1.19.502.1
Click to expand...
Click to collapse
so the first one i see is an .exe, so does that mean that is all i would need to wipe it? and the second one, how would i flash it, using which utility?
Twiztidunreal said:
so the first one i see is an .exe, so does that mean that is all i would need to wipe it? and the second one, how would i flash it, using which utility?
Click to expand...
Click to collapse
Yes, the first is an .exe and can be run from Windows. However, you may need to flash stock recovery( which can be found here ) first.
The second file can be flashed like any other rom as well as the boot.img
ac3kill said:
His wife is prob pissed lol I know mone would be
Sent from my HTC One X+ using XDA Premium HD app
Click to expand...
Click to collapse
you have no idea..... lol kinda glad im at work so i dont have to hear about it, but kinda wish i was home so i could fix it faster, lol
i should be home in about 3 or 4 hours though, and i will try a few things and let you guys know the status. I appreciate all the help so far, hope i can get it back up and running asap!
before going back to stock, i would flash a different rom mate. latest viper as a known issue where it leaves you stuck at that very point I'm sure while its stuck on the htc screen you should be able to connect it to your pc and drag a new rom across, if not flash TWRP 2.4.4.0 and "sideload" or "push" your rom. Trust me theres no need to go back to stock.
http://forum.xda-developers.com/showpost.php?p=40497069&postcount=1191
Turge said:
First thing's first, what hboot version are you on? you can see that in the booloader screen. Mine is 1.32.0000 which is the previous version.
Anyways, ADB works in TWRP. I'm running 2.4.4.0 and I noticed it can take up to 30 seconds for it to start. You may want to start with that version: http://techerrata.com/browse/twrp2/evitareul
Once in TWRP, you can either use "adb push" or "adb sideload":
ADB Push:
Run "adb devices" until your serial # shows up
run "adb push c:\somefolder\rom.zip /sdcard/" to push the rom zip to your phone's sdcard. It can take up to 10 mins to transfer it this way. You can use one of these: http://forum.xda-developers.com/showthread.php?t=2235248
ADB Sideload:
While in TWRP, select Advanced then ADB Sideload
Type "adb sideload c:\somefolder\rom.zip"
Once flashed, reboot to bootloader and flash the boot.img then reboot your phone.
Click to expand...
Click to collapse
hboot is 1.40.0000 so yeah, its updated... i will try the earlier version of TWRP, as the 2.5 didnt work for me either
ratcom said:
latest viper as a known issue where it leaves you stuck at that very point [/url]
Click to expand...
Click to collapse
What are you talking about?
Sent from my HTC One X using Tapatalk 2
Turge said:
What are you talking about?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
If you install the international 1.0.7 from a full wipe you get stuck at that very point.
I'll follow up with m0n then see if he knows anything about it.
However, I'm pretty sure we're talking about the AT&T variant of the HOX+
Sent from my HTC One X using Tapatalk 2