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
I recently got the One X because I became to impatient for the One X+.
After flashing cm10 on it I decided to try and flash back to stock to see if i could return it to ATT because i was within 14 days.
I accidentally bricked my phone by deleting my system from the recovery and now I cant boot into recovery.
It turns on but goes as far as the "HTC quietly brilliant 'this build is for development purposes...'" screen and stops.
I can turn the phone off and on but it gets stuck at this screen.
I've tried button combos to get into recovery and I've tried adb and the one x tool kit.
I've also tried the recovery from the RUU OTA update but no dice.
Any way to fix this?
Ectosock said:
I recently got the One X because I became to impatient for the One X+.
After flashing cm10 on it I decided to try and flash back to stock to see if i could return it to ATT because i was within 14 days.
I accidentally bricked my phone by deleting my system from the recovery and now I cant boot into recovery.
It turns on but goes as far as the "HTC quietly brilliant 'this build is for development purposes...'" screen and stops.
I can turn the phone off and on but it gets stuck at this screen.
I've tried button combos to get into recovery and I've tried adb and the one x tool kit.
I've also tried the recovery from the RUU OTA update but no dice.
Any way to fix this?
Click to expand...
Click to collapse
Which ruu were you using?
Did you relock your boot loader before running ruu?
Sent from my One X using xda app-developers app
Myrder said:
Which ruu were you using?
Did you relock your boot loader before running ruu?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I used "htc_one_x_RUU_2.20.502.7_att_us_08022012" to revert back to stock because i was originally on 2.20.
I did not relock my boot loader before running RUU.
Ectosock said:
I used "htc_one_x_RUU_2.20.502.7_att_us_08022012" to revert back to stock because i was originally on 2.20.
I did not relock my boot loader before running RUU.
Click to expand...
Click to collapse
There is your problem.
Fastboot oem lock
Type that into your fastboot cmd window to ruu
Sent from my One X using xda app-developers app
Myrder said:
There is your problem.
Fastboot oem lock
Type that into your fastboot cmd window to ruu
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
still no dice
error: device not found or < waiting for device >
One thing though is the phone shows up in my device manager as Android but is an unknown and does not have the drivers.
I have the usb drivers, and android SDK installed so I dont know what drivers it is missing.
Okay I can get into the bootloader but im still getting no ADB connection
[EDIT]
from the bootloader i went into fastboot USB and relocked the bootloader
RUU is running!
Ectosock said:
Okay I can get into the bootloader but im still getting no ADB connection
[EDIT]
from the bootloader i went into fastboot USB and relocked the bootloader
RUU is running!
Click to expand...
Click to collapse
Glad you're back up and running.
I wonder if att will even take back his phone because of the relocked status, why do you want the one x + so much? You just said you couldn't wait so you tampered with it and changed your mind, but I mean the one x + is only a second faster.. you can just overclock HTC one x anyways. But I'm glad you phone is back.
Keep the Xl.
WR
Sent from my HTC One X
WhatTheAndroid? said:
I wonder if att will even take back his phone because of the relocked status, why do you want the one x + so much? You just said you couldn't wait so you tampered with it and changed your mind, but I mean the one x + is only a second faster.. you can just overclock HTC one x anyways. But I'm glad you phone is back.
Click to expand...
Click to collapse
WarRaven said:
Keep the Xl.
WR
Sent from my HTC One X
Click to expand...
Click to collapse
64gb plus better battery is enough for me to switch.
Also can the store employees actually tell if it was bootloader tampered? The last time I traded in my stock flashed Samsung Captivate for return all they did was a factory reset and took it back.
Though, better battery life is questionable.
WR
Sent from my HTC One X
They can just go into fastboot if they wanted to and just deny your return. I doubt they will do that. Although it would suck if the phone malfunctions on the next person and he returns it back to att and I guess that would be suspicious but I think your fine. I guess more space is nice on a phone but I don't think I have used that much space on my laptop haha, mabye 50 gigs of bloatware and some music and some fps games. I was just wondering why the switch. Oh and did the ruu go as planned? Oh and also if you decide to get insurance for your phone you should think about squaretrade...they protect against a lot..drops spills..and if you factory reset to stock Rom they will fix it even though you may have rooted..and they will pay you the no commitment price if they can't fix it.(drops,spills,etc)
Here in Los Angeles and surrounding cities the ATT reps are now trained to get into the boot loader to check for a tampered and unlocked device. A few months ago they were not but many devices have come back where someone screwed it up and returned it.
WhatTheAndroid? said:
They can just go into fastboot if they wanted to and just deny your return. I doubt they will do that. Although it would suck if the phone malfunctions on the next person and he returns it back to att and I guess that would be suspicious but I think your fine. I guess more space is nice on a phone but I don't think I have used that much space on my laptop haha, mabye 50 gigs of bloatware and some music and some fps games. I was just wondering why the switch. Oh and did the ruu go as planned? Oh and also if you decide to get insurance for your phone you should think about squaretrade...they protect against a lot..drops spills..and if you factory reset to stock Rom they will fix it even though you may have rooted..and they will pay you the no commitment price if they can't fix it.(drops,spills,etc)
Click to expand...
Click to collapse
The RUU worked perfectly and I returned it with no hassle; they didn't even factory reset it in front of me.
I now have the One X+ and I'm glad i switched. It runs so well I don't think I'll need a custom rom for a while.
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.
Hey guys, I just picked up a Inspire as a play toy since my cousin upgraded.. What in looking for is a RUU for the latest update if there is any.. 2.3.5, firmware 3.20 if I'm not mistaken. (Its not in front of me at the moment).. I've tried numerous sites and it seems as though they don't exist anymore..
Quick history, phone worked fine. Bone stock, never rooted or unlocked. So she took the latest update, and ever since then it has problems... Main thing is when the screen goes black, it reboots. EVERY SINGLE TIME. So I decided to unlock via htcdev, fastbooted twrp 2.4.4.0, and flashed a rom to see if it fixed it. Flashed jellytime and respective gapps, no dice. Phone is still rebooting upon locking. Last resort is a ruu... I've tried over clocking, overvolting, etc... No go. I'm not ruling out hardware 100%, but bc it didn't do this before the update makes it last on my list... Any advice?
Sent from my One X using Tapatalk 2
Test it without the sd card.
Reflash the ruu.
Sent from a dream.
I don't have the ruu lol. That's why I posted here... It seems like every site has it taken down...
Sent from my One X using Tapatalk 2
InflatedTitan said:
I don't have the ruu lol. That's why I posted here... It seems like every site has it taken down...
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
https://www.google.com/#hl=en&output=search&sclient=psy-ab&q=htc_inspire4g_att_RUU_3.20.502.52_US&oq=htc_inspire4g_att_RUU_3.20.502.52_US&gs_l=hp.3...3147.3147.0.4546.1.1.0.0.0.0.204.204.2-1.1.0.les%3B..0.0...1c.2.6.psy-ab.m3erFIGkS8Q&pbx=1&bav=on.2,or.r_cp.r_qf.&bvm=bv.43828540,d.eWU&fp=c539a620ba7dec8b&biw=1366&bih=641
There seems to be a link with the files, haven't checked if it's in it. As well, I have a copy of the last inspire update but no where to upload it and in case you can't find it via the provided link.
Hey thanks man. I'll give that a shot .
One more question, if I flash the stock lower firmware zip, would that be enough to run the aahk to s-off? Or is there more to it than that? Last time I tried it said the firmware was not supported up to that version
Sent from my One X using Tapatalk 2
InflatedTitan said:
Hey thanks man. I'll give that a shot .
One more question, if I flash the stock lower firmware zip, would that be enough to run the aahk to s-off? Or is there more to it than that? Last time I tried it said the firmware was not supported up to that version
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I wouldn't recommend flashing a lower firmware.... Not sure if anything bad will happen but it does not seem like a good idea. Besides, aahk has been retired. There is no support for it and it is only for advanced users.
You can try glevitans tool in the development section to unlock your bootloader but he two has left these forums due to too many self rightious (or however you spell that) noobs.
Sent from a dream.
Right... I'm already unlocked and rooted.. So there's no way to s-off without jumping through hoops? Lol... I can throw out some fastboot and adb commands... But as far as DD'ing blck partitions I'll just give up on s-offing
Sent from my One X using Tapatalk 2
Hopefully someone could give a few more opinions before I throw this thing in the trash can... I'm still having the reboot issue... I can use it for hours on end as long as the screen is on. It will stay on if its connected to any power source... But when its not plugged in and the screen locks it reboots about 3 seconds later...
Didn't do this before I took the 2.35 ota.. I've tried 15 different ROMs, different kernels, I tried overclocking and trying to get rid of deep sleep. Don't know what else to do. I'd love to try to raise the voltage but every kernel/ROM I use doesn't give me that option.
Also I'd like to mention when I boot into bootloader it immediately searches for pd98img.zip. is this normal? I never seen another boot loader look for a certain file..
Anyway, any help will be appreciated... I'd hate to get rid of this phone if its fixable...
This is the bootloader
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Hopefully someone could give a few more opinions before I throw this thing in the trash can... I'm still having the reboot issue... I can use it for hours on end as long as the screen is on. It will stay on if its connected to any power source... But when its not plugged in and the screen locks it reboots about 3 seconds later...
Didn't do this before I took the 2.35 ota.. I've tried 15 different ROMs, different kernels, I tried overclocking and trying to get rid of deep sleep. Don't know what else to do. I'd love to try to raise the voltage but every kernel/ROM I use doesn't give me that option.
Also I'd like to mention when I boot into bootloader it immediately searches for pd98img.zip. is this normal? I never seen another boot loader look for a certain file..
Anyway, any help will be appreciated... I'd hate to get rid of this phone if its fixable...
This is the bootloader
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I can't give you any other advice to the first problems you had but yes when you boot into hboot. It automatically searches for a pd98img.zip.. That is completely normal
Sent from my Inspire 4G using xda premium