So My phone is constantly freezing and rebooting in apps every 5-15 minutes and I am going to try going back to stock and seeing if this occurs. My question is do i have to wipe my current rom? Or do i only have to fastboot oem lock and run ruu? Help would be appreciated. Think it is getting worse..
WhatTheAndroid? said:
So My phone is constantly freezing and rebooting in apps every 5-15 minutes and I am going to try going back to stock and seeing if this occurs. My question is do i have to wipe my current rom? Or do i only have to fastboot oem lock and run ruu? Help would be appreciated.
Click to expand...
Click to collapse
Yes, just run fastbook oem lock and then run the ruu. Make sure that you have the latest drivers from HTC (use htc sync if you can). Good luck!
For ruu grab the appropriate one .... Relock your bl like you Saud and run the ruu from you bl mode ...no need to wipe anything the ruu will do that for you
Skeeterdrums said:
Yes, just run fastbook oem lock and then run the ruu. Make sure that you have the latest drivers from HTC (use htc sync if you can). Good luck!
Click to expand...
Click to collapse
and i run the command in fastboot on my htc one x? ive did it once before.
WhatTheAndroid? said:
and i run the command in fastboot on my htc one x? ive did it once before.
Click to expand...
Click to collapse
Yessir head over to gunnymans thread in general forum to clear any confusion that remains
phone is going haywire.....Not being detected..rebooting every second..cant even get into an app...got into twrp and going to charge it ill 70 and restore to a better backup then hopefully ruu...thanks for the help
WhatTheAndroid? said:
phone is going haywire.....Not being detected..rebooting every second..cant even get into an app...got into twrp and going to charge it ill 70 and restore to a better backup then hopefully ruu...thanks for the help
Click to expand...
Click to collapse
Usually, the phone doesn't get detected if the drivers aren't up to date. Is it rebooting even from bootloader? You should be able to install everything from there, hopefully meaning restarts aren't an issue.
HTC One X using CleanRom 5.1 with BeastKernel 4.4
Skeeterdrums said:
Usually, the phone doesn't get detected if the drivers aren't up to date. Is it rebooting even from bootloader? You should be able to install everything from there, hopefully meaning restarts aren't an issue.
HTC One X using CleanRom 5.1 with BeastKernel 4.4
Click to expand...
Click to collapse
finally got it recognized and successfully ruu'd.It was very odd, like the phone was progressively getting worse for some reason.i am not not getting rebooted on stock rooted so it had to do something with my settings on the rom..like i said i under clocked and overclocked it, hot rebooted it, wiped cashe and dalvik...nothing was working and it finally just kept rebooting and freezing at home screen..Maybe a bad successful flash lol.. im not really sure.. or flashing over a bad flash had something to do with it..I might wait till jellybean comes out.
Have you tried to simply factory reset?
i personally like ruu'ing. i should do the same soon just to clean house. in the end it's pretty easy to get fluent on this phone.
i would say immediately after unlocking bootloader to ruu. i noticed some differences in the 1.85 to 2.20 ota vs the 2.20 ruu. it will also clean up any mess that might of been left on the phone. im also pretty ocpd =)
also htc sync imo is useless, i just use the standalone htc drivers haven't had any issues with them.
OP... What rom/kernel combo were you running?
Only time I've seen another phone go that nuts is when my cousin flashed rohans kernel in viper lol
Sent from my One X using Tapatalk 2
InflatedTitan said:
OP... What rom/kernel combo were you running?
Only time I've seen another phone go that nuts is when my cousin flashed rohans kernel in viper lol
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Viper and beastmode. My phone was going nuts....froze at the start screen 3 times and reset it self into a bootloop, then went back to freezing when start screen appeared..one of the times all I could see is the notification bar but I couldn't drag it Down. Lots of other crazy stuff happened on it as well...to much to tell. But I heard cleanrom is pretty stable, do I have to wipe stock rooted(no custom Rom yet) trying to find a good one and do I have to flash boot IMG if I'm on 1.14 or is it Included in the cleanrom installer? Might try elemental with cleanrom..see how that works out.
Related
Man, this sucks big time lol. Only got it yesterday cheap.... done the s-off and rooted, installed Cyanogenmod 9 rc1, it just kept loading in the crashing out and restarting in a loop. So i thought it might be because i didnt have an upto date firmware, so i flashed the 3.32 TMOUS not realising its T-Mobile or some sh1t. NOW cyanogenmod wont even load to the home screen like it did before..... i cant flash a diff firmware cause the CID isnt acurate or some crap. Just flashed Revo HD (latest) hope this works but i doubt it So how the hell do i get a diff firmware on there or get cyanogenmod 9 rc1 working. My misses will be PISSED when she gets home lol HELP!
TIA
Fox!
foxorroxors said:
Man, this sucks big time lol. Only got it yesterday cheap.... done the s-off and rooted, installed Cyanogenmod 9 rc1, it just kept loading in the crashing out and restarting in a loop. So i thought it might be because i didnt have an upto date firmware, so i flashed the 3.32 TMOUS not realising its T-Mobile or some sh1t. NOW cyanogenmod wont even load to the home screen like it did before..... i cant flash a diff firmware cause the CID isnt acurate or some crap. Just flashed Revo HD (latest) hope this works but i doubt it So how the hell do i get a diff firmware on there or get cyanogenmod 9 rc1 working. My misses will be PISSED when she gets home lol HELP!
TIA
Fox!
Click to expand...
Click to collapse
Do you have SuperCID? You can check by booting into fastboot (bootloader) and typing this in...
fastboot oem readcid, if it doesn't say 11111111 then you aren't SuperCID.
Type in:
fastboot oem writecid 11111111
then
adb reboot-bootloader
and last
Type fastboot oem readcid, if it says 11111111 then you have SuperCID and you should be able to flash any rom.
Daiskei said:
Do you have SuperCID? You can check by booting into fastboot (bootloader) and typing this in...
fastboot oem readcid, if it doesn't say 11111111 then you aren't SuperCID.
Type in:
fastboot oem writecid 11111111
then
adb reboot-bootloader
and last
Type fastboot oem readcid, if it says 11111111 then you have SuperCID and you should be able to flash any rom.
Click to expand...
Click to collapse
dude i dunno what you mean lmao. Vol- + Power , then select fastboot, now what? Plug in usb and adb ? It cant find the device if so
foxorroxors said:
dude i dunno what you mean lmao. Vol- + Power , then select fastboot, now what? Plug in usb and adb ? It cant find the device if so
Click to expand...
Click to collapse
Yeah, sorry man, vol- and power into fastboot. You may need to install the drivers.
foxorroxors said:
dude i dunno what you mean lmao. Vol- + Power , then select fastboot, now what? Plug in usb and adb ? It cant find the device if so
Click to expand...
Click to collapse
lol i bet you mean use fastboot in the cmd
am all over the place trying to do this look after my twins and panicing cause the misses is having an op in hosp today
Do you have the drivers properly installed ? Get htc sync from htc website it will give you the drivers then try again whit adb..
If that doesn't work grab a RUU run it on your computer you'll be back to stock s-on but you'll have to redo everything tho..
Sent from my HTC Sensation 4G using xda app-developers app
shahkam said:
Do you have the drivers properly installed ? Get htc sync from htc website it will give you the drivers then try again whit adb..
If that doesn't work grab a RUU run it on your computer you'll be back to stock s-on but you'll have to redo everything tho..
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
ok changed the CID its now 1111111
reflash the rom? Cause i rebooted and it didnt load into it :/
foxorroxors said:
ok changed the CID its now 1111111
reflash the rom? Cause i rebooted and it didnt load into it :/
Click to expand...
Click to collapse
Ok now that your supercid first make sure you have enough charge left like 50% Then flash the rom should boot..
Sent from my HTC Sensation 4G using xda app-developers app
shahkam said:
Ok now that your supercid first make sure you have enough charge left like 50% Then flash the rom should boot..
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
rebooting fingers crossed!
shahkam said:
Ok now that your supercid first make sure you have enough charge left like 50% Then flash the rom should boot..
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
rebooting fingers crossed! well it loaded into the Cyanogenmod 9 RC2 and its at home then it crashes and restarts..... :/ now what lol
foxorroxors said:
rebooting fingers crossed! well it loaded into the Cyanogenmod 9 RC2 and its at home then it crashes and restarts..... :/ now what lol
Click to expand...
Click to collapse
Seeing as your CID has changed, you probably have to boot to recovery and flash a new rom OR reflash over the current CM9RC2.
Daiskei said:
Seeing as your CID has changed, you probably have to boot to recovery and flash a new rom OR reflash over the current CM9RC2.
Click to expand...
Click to collapse
just did a full format, well everything u can in fastboot, reinstalled cm9 and a cm9 kernal still doing the same loads into ICS home screen is on for like 5-10 seconds then resets and loops this damnit **** **** **** ****. Maybe i need to reflash teh firmware aswell???
foxorroxors said:
just did a full format, well everything u can in fastboot, reinstalled cm9 and a cm9 kernal still doing the same loads into ICS home screen is on for like 5-10 seconds then resets and loops this damnit **** **** **** ****. Maybe i need to reflash teh firmware aswell???
Click to expand...
Click to collapse
thing is lol if i dont load into the homescreen, the phone unluck screeb DOESNT crash wtf is going on lol...
foxorroxors said:
thing is lol if i dont load into the homescreen, the phone unluck screeb DOESNT crash wtf is going on lol...
Click to expand...
Click to collapse
That is strange... try another rom seeing as CM9 isn't working, I mean... maybe something is happening with that... I don't know what it could be but it's always worth trying something else. Maybe after another rom you could flash back to CM9 and it'll work? I would definitely try flashing the FW again.
foxorroxors said:
rebooting fingers crossed! well it loaded into the Cyanogenmod 9 RC2 and its at home then it crashes and restarts..... :/ now what lol
Click to expand...
Click to collapse
The problem is that you've done so many different things now that the real problem could be burried somewhere and hard to trace.
At this point, since nothing is making this better, you may try the full RUU total wipe and start over method described in one of the posts above.
It'll take a little longer that to do it than simple reflashing a new ROM since you'll have to reroot and everything but it will almost certainly work. And it might take less time than trying 15 other things that 'might work'.
It's also got your highest probably of success since you don't know what the cause of the problem is. The RIL method WILL work unless it's a hardware fault.
Also check the website the Rom is on and see if that particular Rom requires 3.33 firmware ?
Although most run on both 3.32 and 3.33. It's worth checking. I wish you the best. I'm sure you will get it up and running soon. Best wishes.
Sent from my HTC Sensation 4G using xda premium
Skipjacks said:
The problem is that you've done so many different things now that the real problem could be burried somewhere and hard to trace.
At this point, since nothing is making this better, you may try the full RUU total wipe and start over method described in one of the posts above.
It'll take a little longer that to do it than simple reflashing a new ROM since you'll have to reroot and everything but it will almost certainly work. And it might take less time than trying 15 other things that 'might work'.
It's also got your highest probably of success since you don't know what the cause of the problem is. The RIL method WILL work unless it's a hardware fault.
Click to expand...
Click to collapse
Agreed. I was fairly sure that the SuperCID would fix it but since it's still crashing it might be best to try a full RUU wipe and just start things over.
Daiskei said:
Agreed. I was fairly sure that the SuperCID would fix it but since it's still crashing it might be best to try a full RUU wipe and just start things over.
Click to expand...
Click to collapse
You guys are right ive spent the time from my last post trying diff roms done 4 roms and 3 firmwares and lost about a lb of hair (lol) bloody anoying, nothing even wrong with the stock haha it was plenty fast enough for me, just the geek inside me wanted to piss about with it bad fox
going back to stock everything, RUU as advised.
Will let peeps know how i get on later, i gotta eat some food :'(
foxorroxors said:
You guys are right ive spent the time from my last post trying diff roms done 4 roms and 3 firmwares and lost about a lb of hair (lol) bloody anoying, nothing even wrong with the stock haha it was plenty fast enough for me, just the geek inside me wanted to piss about with it bad fox
going back to stock everything, RUU as advised.
Will let peeps know how i get on later, i gotta eat some food :'(
Click to expand...
Click to collapse
Sounds good man, looking forward to hearing whether it worked for ya. *fingers crossed*
The bootloop thingy can either be because you dont have 4ext and flashed the rom whit cwm.. or you didnt wipe...
Have you checked the md5 hash of the rom if it matches ? Corrupted downloads can happen even tho its uncommon.
Sent from my HTC Sensation 4G using xda app-developers app
Hey
I just got a huge bootloop while attempting to flash new Venom Room to my HTC One X. http://forum.xda-developers.com/showthread.php?t=1868236
I cannot access the recovery.. After restart (power button+volume down) i can get to bootloader section, but when i try to get into recovery, the phone just restart and stop on the white htc screen.
I already tried to reinstall recovery. Installation was successful, but the problem persists..
Before i had Incert Coins room.
The phone is unlocked, new recovery is installed
Please, help
If you had Insert Coin working on your phone, you have an international (Tegra3) version of the One X. This forum (and the Venom ROM you linked) are for the Snapdragon S3 version. Completely different hardware.
If I'm correct, you flashed a ROM for the wrong phone. Try running the RUU for your phone, but if that doesn't work you may be screwed. Recovery partitions are not the same for the versions. The ROM overwrote the recovery partition of your phone.
You are right.. It WAS the wrong rom.. I have tegra3 processor and this rom comes from american section..
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Senbration said:
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Click to expand...
Click to collapse
RUU just returns your phone to the stock condition. Stock ROM and stock recovery. There should be nothing dangerous about it. Just use the right one for your version, carrier, etc. But the CID check should ensure that you don't run the wrong RUU (if RUU is for a different CID, the RUU will not run).
Only thing with RUU, is that it wipes all user data. That may be why you heard its "dangerous". But in the condition you are in, this is not even a consideration anymore.
RUU is not dangerous, and it may be your only hope at this point.
You will need to lock your bootloader before running the RUU.
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
I'm assuming you meant relocked bootloader and now has security warning relocked if this what you meant then you are fine flash the ruu
Sent from my Nocturnalized One XL using Forum Runner
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
You mean relocked and not reloaded? If so, you should be good to run the RUU. Redpoint, sorry for highjacking your help session
Sent from my One X using xda premium
ohh, its Relocked.. Im just a bit nervous right now hoping it will unbrick this phone..
Just 3min to complete RUU download.
Do U guys think this stock RUU will rewrite the partitions back?
I've noticed another problem.
Cannot load RUU because the battery level is lower then 30%.
But when i plug the charger the light doesnt flash. It starts to flash when i switch on the phone.
Also cannot switch the phone with the power button. It restart all the time. Only can do that from bootloader command "power down". But when the phone is off the power light doesnt flash..
Does it mean that the battery is not charging at all? Because the light can flash only because the power is low..
The phone shut down completly now.. Does not charge the battery at all.. Power gone off and i cannot even turn on the phone..
Is there any solution how to make it charge?
Ok, the problem is that the wrong ROM i tried to install changed partition and also it seems it destroyed Recovery..
Without recovery the phone cannot charge while being in bootloader mode...
Is there any way to make phone charging when Recovery doesnt work and cannot be flashed?
Please help
Take the phone apart. I mean all the way spart and hardwire a charger to the phone/ battery. Its a pain but you can do it.
Ohh..
I found a treat http://forum.xda-developers.com/showthread.php?t=1658084
There is a way to charge battery by running the script, which makes phone reinstalling constantly. Each time it is reinstalled, the battery is charged a little bit more.
After mayby 40min i went up from 3686 V to 3720 V.
It seems that my only hope is to reinstall RUU. I tried to flash wrong ROM, from wrong model and as one user wrote above, it has rewritten my partition. Same time it destroyed recovery.. I cannot flash recovery now because the partition is rewritten...
And without working recovery i cannot charge the battery being in bootloader.. If i understand it all correctly.
I already tried to install RUU with 3710 V. It started to install, but stopped after few min with information that battery is too low..
So i think ill leave this script running for a whole night, and hope, in the morning battery will be charged just enough to install RUU eventually..
Uff
Okey, finally its fixed..
After 7 hours of constant reinstalling the phone by the script, the battery was loaded enough to finish RUU instalation process.. (battery went to about 3830mV power)
After oryginal RUU was installed, everything went fine.
Now i already re-unlocked the bootloader, re-rooted the phone and all works correctly.
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Amazingly impressive to me.
Thanks for following up with your success.
WR
Sent from a CleanRom-V OneX
THAT is AWESOME
Senbration said:
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Click to expand...
Click to collapse
Your welcome, and no problem really. It was an easy problem to recognize, as I've seen it several times before on here.
Nice job getting the phone charged. Haven't seen that solution before.
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Sent from my HTC One X using Tapatalk 2
Senbration said:
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Click to expand...
Click to collapse
Sh1T! Did I forget to do that???? I must have been in a good mood . . .
Heh it must have been so
Sent from my HTC One X using Tapatalk 2
Here is what I did....
HTC One X (ATT). Unlocked and rooted yesterday. (TWRP)
Today tried to install CM10 and GApps, got stuck on CM bootscreen, then I flashed the boot.img and it still did not work....then my immediate next step (probably stupidly) was to flash modded boot...still did not work....I just got to HTC screen with the red writing on the bottom and nothing else....
So I got into TWRP and restored to my backup (which I was able to do before the above) and just got to the same HTC screen with red type on the bottom......now I started to panic.
I tried to relock the phone...and I did but now I cant go anywhere but the fastboot screen!!!!
Please Help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
If you relocked already just run the ruu in fastboot and restore to stock.
davezaff said:
If you relocked already just run the ruu in fastboot and restore to stock.
Click to expand...
Click to collapse
I am downloading the RUU....we'll see
Many Thanks
davezaff said:
If you relocked already just run the ruu in fastboot and restore to stock.
Click to expand...
Click to collapse
Many thanks....it worked!!!!!
Now the question is...do I try again? (Not today anyway)
trevorb21 said:
Many thanks....it worked!!!!!
Now the question is...do I try again? (Not today anyway)
Click to expand...
Click to collapse
Just read read and read more..be comfortable first than you'll be fine and know how to get out of any situation
Just read up and give it another go.....like anything else, sometimes you need certain thing to happen to learn....good luck.
Just saying, you flashed the boot.img after flashing the rom and gapps? The boot.img is flashed before flashing the rom
It can be done either way.
ive been seeing alot of new members soft bricking this way should read though this post http://forum.xda-developers.com/showthread.php?t=1957193 it explains every thing for ppl on hboot 1.14 and higher.
trevorb21 said:
I tried to relock the phone...and I did but now I cant go anywhere but the fastboot screen!!!!
Click to expand...
Click to collapse
That is what is supposed to happen. Once you relock, you need to run the RUU. It won't boot otherwise.
I am unlocked and rooted again.....ready to try again...
I want to leave the phone alone but I cant help myself.......Anyone else have this issue???
I know what you mean, when i first got my one x and learned of rooting, i felt i was claustrophobic with normal stock. I Read and read and read some more, before I even thought about flashing roms. But I Recommenced flashing Viper JB 3.1.0 As it basically installs the boot img in the boot-loader for you. I also recommend Cm 10.1, except it does not have camera working as of yet. If you dont mind not having a camera, cm 10.1 is a very smooth rom. Also remember if flashing certain roms like cm 10. dalvik, cache and factory reset, as well as flashing the boot img are required for the rom to work. Good luck
trevorb21 said:
I am unlocked and rooted again.....ready to try again...
I want to leave the phone alone but I cant help myself.......Anyone else have this issue???
Click to expand...
Click to collapse
I've had this problem since may 6th, 2012 lol.. good god you should here my wife when I tell her I didn't get her messages or calls because I was in recovery lol!
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
I've had this problem since may 6th, 2012 lol.. good god you should here my wife when I tell her I didn't get her messages or calls because I was in recovery lol!
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I'm livin in the same life man been though 4 android phone and a tablet in a year o and rooted all my friends phones
Thanks a ton this thread helped me save my phone
I looked around and didn't see a solution to my problem. I might have missed it because I'm kind of panicked right now.
My HOXL was dying really fast. Within a few hours, it falls from 80% to 0%. I wanted to factory reset because I heard that it helps the battery life.
So I followed the process I always have (I'm unlocked, rooted, and had pacman's evita ROM installed) and did a factory reset, wiped cache and dalvik cache. Then I re-flashed pacman's ROM and the gapps. When I rebooted though, it went to the HTC screen and in a few seconds it just went black. I think it might have still been on or something, but nothing was happening for like 30 minutes. I tried it over and over again, flashing new ROMs and kernels, but now all that's happening is that it's stuck on that very first HTC screen.
I downloaded the latest JB RUU for evita to try it out. But if I can't get past that first screen, is there a way to connect it? I can still get into TWRP's recovery. My HBoot is 1.09. I'm really starting to feel nervous about having to buy a new phone, yet I feel like there should be a way to fix this. Could flashing the stock kernel be all I need? I tried to download from Viper's hub, but the download just stops at 99% and doesn't finish.
Please, I would really, really appreciate any help!
I would run the 3.18 RUU (which you can do in fastboot).
Try a complete wipe: Factory reset, system, cache and dalvik cache in twrp or if it is not wiping correctly due to twrp version " 2.3......" is best fro our phones, try downloading and installing twrp again or use adb commands to wipe and flash rom again.
I've tried a complete wipe, but I just noticed that my TWRP version is 2.2.0. I tried the wipe like five or more times and it didn't work. My PC isn't reading the HOXL in the adb command window. I rooted a Sero Pro 7 this way, so I think I should have the drivers installed for it... I'm going to try installing the HTC Sync drivers and seeing if I can send adb commands to my HOXL. If this doesn't work, I'm going to try the 3.18 RUU. I heard that some people have bricked their HOXL completely doing this, but I didn't change my SuperCID and s-on (?), so would I be fine? Or would it be safer to just use the latest ICS one (RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio _0.19as.32.09.11_2_10.105.32.25L_release_271865_si gned.exe)?
So you have no way to flash boot image separately? I would definitely try to get device recognition so adb can be used before running ruu.
Sent from my HTC One X using xda premium
Yeah, I went through the noob way of unlocking and rooting this phone, so there was no need to use adb commands. I would have liked to try that first before running RUU, but I just want to have a working phone again, even if I have to go through the whole process of unlocking and rooting.
Sent from my Nexus 7 using XDA Premium HD app
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium
Venomtester said:
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is what I'm worried about:
SERooted wrote: Note to OP: You really should add to the 1st post that it is not wise to flash the 3.18 firmware over super cid and s-on.. its not a good thing for most people to have a qhsb_dload turn their phone into a paper weight before finding out that they shouldn't have used that file to begin with. i had to find out the hard way. i would have flashed the ics firmware on my phone but decided to go with the big JB only to find out that it turns it into a paperweight. I understand this is no fault but my own, however this would greatly help people when choosing which ruu to run.
http://forum.xda-developers.com/showthread.php?t=2191477
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium
Venomtester said:
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Huh...I just tried flashing the UrDroid ROM because of its aroma installer, but it didn't happen in recovery, like I thought it would. It said it was successful, so I rebooted the system. It got past the initial screen with an AT&T boot img and htc one img. Now I'll have to see if it actually loads past this.
EDIT: It worked! I'm going to have to try to see if I can load boot img some other way than just an aroma installer.
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium
Venomtester said:
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Second Flash GUI....works like a charm
I've been flashing custom roms to my asus transformer for a couple years now so I'm fairly accustomed to the process. Now that my warranty has expired on my one s I decided to go custom to try and get a bit more battery life and performance from my phone.
steps I took:
unlocked bootloader successfully
installed twrp successfully
installed su and rooted successfully
changed to supercid successfully
S-off unsuccessful. I wasnt paying as much attention as I should have and for whatever reason I thought I had s-off
flashed maximushd rom
then attempted to flash the kernel for maximus obviously didnt work because I had s-on
then I was stuck at the point where my phone was basically a black screen and all I could do is get the buttons on the bottom of the screen to flash. Eventually I made it into the bootloader, twrp was gone or corrupted. Managed to reinstall twrp from fastboot and get it working.
within twrp I was able to push a rom into the internal sd and flash it (cant remember which one atm). phone restarted and was then stuck in a 30ish second bootloop of the htc quietly brilliant screen. tried a couple other roms which wouldnt flash. at this point I went home (i dont have a computer at my house, just android based tablet and xbmc box).
At home I got the idea the roms i'm trying to flash might not be compatible with hboot 2.15. I downloaded and tried older roms that would match my hboot of 2.15. Varying success on these but still unable to boot to phone os.
Here is what ive tried and what results i had with them:
zenrom_v1.05_2.31RUUbased.zip = Wont flash just gives failed message
Toasted_marshmellow-ville.zip = This one flashed, reboot phone goes past htc screen to the custom boot.img then endlessly replays the .gif (highly disaapointed at this point)
mdob_ville_bm_deodex_2.40.zip = phone stays off and can only get lights to flash if i hold power
Blackout_ics_sense_plus_RC2.zip = phone hangs on white htc screen
Anyone got any idea where I can go from here? Am i hooped or am I just missing something obvious?
u need to re install your stock firmware again...
Sent from my GT-I9082 using XDA Premium 4 mobile app
jeevan000 said:
u need to re install your stock firmware again...
Sent from my GT-I9082 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
any idea where i can get it?
do i flash that just like a rom or is it a ruu?
I tried to install my stock ruu but it kept throwing back an error. it couldnt even tell what verson my phone was when i attempted it.
mikeinaus said:
any idea where i can get it?
do i flash that just like a rom or is it a ruu?
I tried to install my stock ruu but it kept throwing back an error. it couldnt even tell what verson my phone was when i attempted it.
Click to expand...
Click to collapse
I read that you have supercid, you can download this RUU
Insecret said:
I read that you have supercid, you can download this RUU
Click to expand...
Click to collapse
Ended up bringing my phone to a shop which fixed it and installed a new power button as my old one was shot for $65. One thing he did which pissed me off though is install cm 10.1 instead of maximushd like i asked him. not that big of a deal but my signal is horrible now. with stock I used to get 2-3 bars in my rom now im lucky to get 1, and infront of my house where i constantly had full sigal i'm lucky to get 2 or 3 with drops of no signal and dropped calls. Is this because of the rom or the radio? Tried the ota update to 10.2 which freezes the phone on startup, then had to go back and get him to reflash the rom again. its a 10min walk each way and I'm tired of walking back and forth in the rain!
mikeinaus said:
Ended up bringing my phone to a shop which fixed it and installed a new power button as my old one was shot for $65. One thing he did which pissed me off though is install cm 10.1 instead of maximushd like i asked him. not that big of a deal but my signal is horrible now. with stock I used to get 2-3 bars in my rom now im lucky to get 1, and infront of my house where i constantly had full sigal i'm lucky to get 2 or 3 with drops of no signal and dropped calls. Is this because of the rom or the radio? Tried the ota update to 10.2 which freezes the phone on startup, then had to go back and get him to reflash the rom again. its a 10min walk each way and I'm tired of walking back and forth in the rain!
Click to expand...
Click to collapse
Are you still s-off?
You don't need to be s-off to install custom rom's like cyanogenmod but you will need to flash boot.img after the rom is flashed.
foxtrot_lima said:
Are you still s-off?
You don't need to be s-off to install custom rom's like cyanogenmod but you will need to flash boot.img after the rom is flashed.
Click to expand...
Click to collapse
Nah I'm s-on. I don't have a PC so not going to bother flashing a diff ROM because of the boot.IMG. I'm thinking my problem was because I never v flashed boot.IMG last time. Never had to do that before. Is it just an HTC thing?
mikeinaus said:
Nah I'm s-on. I don't have a PC so not going to bother flashing a diff ROM because of the boot.IMG. I'm thinking my problem was because I never v flashed boot.IMG last time. Never had to do that before. Is it just an HTC thing?
Click to expand...
Click to collapse
Yeah it's because s-on and it's HTC only.