I have an AT&T One XL and have had problems recently. I unlocked my bootloader last year on the 2.20 firmware, which is how the phone came. I was able to flash ROMs no problem. About 3 weeks ago I decided to go S-Off with the whole thing. The S-Off was successful, I immediately flashed a new splashscreen and it is confirmed in bootloader that I am S-off. Last week I tried to flash the stable CM10 build, but it was unsuccessful. I found that the only ROMs I am able to flash are Sense ROMs 4.1.1 and above, or AOSP ROMs that are 4.2.x or above. I am on hboot 1.14 and I am very confused as to why I cannot flash properly. I am on TWRP 2.4.1.0, but have used various recoveries trying to solve the problem. I have also RUU'd trying to fix the problem, but to no avail. Any help would be much appreciated!
Twrp 2.4 has issues with wiping properly. Have you tried a different version or wiping with adb in fastboot?
Sent from my HTC One X using xda premium
From what I understand twrp 2.4.1 should be working but I would flash 2.3.x just in case, then do fastboot erase cache. Then wipe cache, dalvik, system, factory reset.
If you RUUd and are s-off why are you still on 1.14? You may as well go up to 2.14 then downgrade touchscreen to use AOSP. Super easy.
Since S-OFF is just a security flag, I am 100% sure it's not the cause of your issue.
Sent from my One X using xda app-developers app
exad said:
From what I understand twrp 2.4.1 should be working but I would flash 2.3.x just in case, then do fastboot erase cache. Then wipe cache, dalvik, system, factory reset.
If you RUUd and are s-off why are you still on 1.14? You may as well go up to 2.14 then downgrade touchscreen to use AOSP. Super easy.
Since S-OFF is just a security flag, I am 100% sure it's not the cause of your issue.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I haven't wiped in fastboot because I thought that's what wiping in recovery was for, I really appreciate all of the input and I will be trying both of these things as soon as I'm done with dinner. Man's gotta eat, ya know :laugh:
Lol. Yep.
Sent from my HTC One X using xda premium
Only fastboot erase cache! The rest of the wiping is done in recovery!
Sent from my One X using xda app-developers app
exad said:
Only fastboot erase cache! The rest of the wiping is done in recovery!
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
As a question, what is the difference between wiping cache in recovery and the fastboot command?
Downgrade twrp to 2.3.3.1
Sent from the HOXL dimension of S-OFF
The fastboot command wipes a cache related to the recovery. Wiping cache in recovery wipes a cache relating to the rom.
Sent from my One X using xda app-developers app
exad said:
The fastboot command wipes a cache related to the recovery. Wiping cache in recovery wipes a cache relating to the rom.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
So I wiped cache via fastboot, and flashed the ROM like i normally would (wipe everything in recovery), but nothing has changed. I still get hung up on the splashscreen when trying to boot the new ROM. ViperXL boots fine when I restore my NANDroid backup, though.
Did you try flashing the boot.img after? You're still on hboot 1.14 afterall. I haven't seen first hand if you can skip flashing the boot.img with s-off, in your case, it seems not.
Sent from my One X using xda app-developers app
exad said:
Did you try flashing the boot.img after? You're still on hboot 1.14 afterall. I haven't seen first hand if you can skip flashing the boot.img with s-off, in your case, it seems not.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Even without flashing the boot.img, it should go past the splashscreen to the boot animation, am I wrong?
You are wrong. It may depending on the kernel previously installed
Sent from my One X using xda app-developers app
exad said:
You are wrong. It may depending on the kernel previously installed
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Sorry to sound like a complete noob, I've been rooting ect for 2.5 years and never seen this problem. Could you please explain a bit more what you mean by the previous post. Are you saying it's the kernel or the boot.img not being installed correctly?
WeiblezWobble said:
Sorry to sound like a complete noob, I've been rooting ect for 2.5 years and never seen this problem. Could you please explain a bit more what you mean by the previous post. Are you saying it's the kernel or the boot.img not being installed correctly?
Click to expand...
Click to collapse
flashing the boot.img is flashing the kernel. you don't sound like a complete noob so don't worry.
I'm going to try again right now to flash the boot.img and then the ROM like normal, reporting back in 15 mins
WeiblezWobble said:
I'm going to try again right now to flash the boot.img and then the ROM like normal, reporting back in 15 mins
Click to expand...
Click to collapse
wipe everything first of course. cache dalvik system and factory reset. i dont mean to treat you like a noob but its better to be extra specific than not specific enough
exad said:
wipe everything first of course. cache dalvik system and factory reset. i dont mean to treat you like a noob but its better to be extra specific than not specific enough
Click to expand...
Click to collapse
Alright, tried it all exactly how you said and it had the same response, got stuck on splashscreen. I am completely puzzled
WeiblezWobble said:
Alright, tried it all exactly how you said and it had the same response, got stuck on splashscreen. I am completely puzzled
Click to expand...
Click to collapse
alright so just to be sure. first off youre on twrp 2.3.x right?
you wipe cache, dalvik, system and factory reset right?
then you flash the rom and the boot.img right? (doesnt matter what order these are flashed)
and still bootlooping?
exad said:
alright so just to be sure. first off youre on twrp 2.3.x right?
you wipe cache, dalvik, system and factory reset right?
then you flash the rom and the boot.img right? (doesnt matter what order these are flashed)
and still bootlooping?
Click to expand...
Click to collapse
Exactly, but just to be 100% clear, I am getting stuck at the splashscreen, and it just sits there infinitely.
Related
First of all, I heard that Google had an API error in 4.1.2 that causes the mobile data or internet data to consume twice as fast. Which means you use 2x more data compared to normal. Is this true? and has it been fixed in CM10?
Secondly, if I am going to flash a new ROM, do I have to flash the ROM first then flash the boot.img separately? Or just flash everything together in the recovery? When should I flash the boot.img separately? I am kinda new to this new phones I so don't know about much these things.
Sent from my One X using xda premium
You only need to flash boot.img separately if you are on hboot 1.14 or higher. Otherwise, it will just flash in TWRP automatically when you flash the ROM.
Don't know about your other questions.
That's "tons" of questions??? That's just 2!
CalamitySir said:
First of all, I heard that Google had an API error in 4.1.2 that causes the mobile data or internet data to consume twice as fast. Which means you use 2x more data compared to normal. Is this true? and has it been fixed in CM10?
Secondly, if I am going to flash a new ROM, do I have to flash the ROM first then flash the boot.img separately? Or just flash everything together in the recovery? When should I flash the boot.img separately? I am kinda new to this new phones I so don't know about much these things.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Where did you hear that? Seems like bs because your carrier measures the amount of data on their servers
If you have hboot 1.14 then you have to flash the boot.IMG separately after you flash the ROM
Otherwise you flash everything in recovery all at once
Sent from my One X using Tapatalk 2
superchilpil said:
Where did you hear that? Seems like bs because your carrier measures the amount of data on their servers
If you have hboot 1.14 then you have to flash the boot.IMG separately after you flash the ROM
Otherwise you flash everything in recovery all at once
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Then how do I downgrade the hboot?
Another question is that when I tried to flash 4.1.1 ROMs when coming from 4.1.2 Roms, it stuck in the boot logo.
Sent from my One X using xda premium
You'll pretty much have to flash boot.IMG seperate every time... Or it will boot loop.
Sent from my One X using Tapatalk 2
InflatedTitan said:
You'll pretty much have to flash boot.IMG seperate every time... Or it will boot loop.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
ok now the question is, do i flash the boot.img first then flash the rom or flsah the rom first then the boot.img??!! The latter method was reccomendded by devs in the HOX section and the former one was used in ours?
I tried ROM then kernel on my cousins phone... Bootlooped.. Started fresh, flashed kernel then ROM and works perfectly every time
Sent from my One X using Tapatalk 2
Another question is the ss below, the total amount of data doesn't add up correctly....is this a bug or was it already predetermined like this?
Sent from my One X using xda premium
CalamitySir said:
Then how do I downgrade the hboot?
Click to expand...
Click to collapse
Tool here (but requires a Linux machine): http://forum.xda-developers.com/showthread.php?t=1982442
The total amount of data doesn't add up. Is this a bug in CM10?
Sent from my One X using xda premium
I'm still not seeing the "tons" of questions.
iElvis said:
I'm still not seeing the "tons" of questions.
Click to expand...
Click to collapse
maybe u cna help me answer the question regarding the data in page one, i have 2 screenshots for that.
Another question is how do i flash the b6 kernel for cm10? flash like normal in twrp or flash the boot.img? i am messed up!
CalamitySir said:
maybe u cna help me answer the question regarding the data in page one, i have 2 screenshots for that.
Another question is how do i flash the b6 kernel for cm10? flash like normal in twrp or flash the boot.img? i am messed up!
Click to expand...
Click to collapse
I have heard only that there may be a bug in CM that makes your data usage appear to be worse. That's all I know.
I have never used CM so I can't help with the kernel. If you're on 1.14 you have to flash it separately in fastboot.
iElvis said:
I have heard only that there may be a bug in CM that makes your data usage appear to be worse. That's all I know.
I have never used CM so I can't help with the kernel. If you're on 1.14 you have to flash it separately in fastboot.
Click to expand...
Click to collapse
ok. does fastboot makes me unable to downgrade the android version, i tried to flash 4.1.1 from 4.1.2, i did it separately and it didnt work, stuck at bootloop... any idea?
Well you have to flash the boot.img from the 4.1.1 rom. Maybe try flashing the older gapps http://goo.im/gapps/gapps-jb-20120726-signed.zip I would also wipe cache, dalvik and system. Use flashimagegui for kernel flashing so you dont need to use fastboot and a pc http://forum.xda-developers.com/showthread.php?t=1963896
Here's what I do and I have flashed every ROM in this section without a single boot loop.
Flash boot IMG in fast boot
Reboot to recovery
Wipe dalvik and cache
Wipe system
Factory reset
Flash rom and gapps or just ROM (sense)
Reboot system
Do I do steps I don't need? Perhaps. But the results are hard to argue
Sent from my One X using xda app-developers app
smolck said:
Here's what I do and I have flashed every ROM in this section without a single boot loop.
Flash boot IMG in fast boot
Reboot to recovery
Wipe dalvik and cache
Wipe system
Factory reset
Flash rom and gapps or just ROM (sense)
Reboot system
Do I do steps I don't need? Perhaps. But the results are hard to argue
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
do i have to follow this sequence to wipe everytime?
Usually if its same rom u dont need to factory reset[wipe data] but ive been wiping system alot each time though.
I recently unlocked my HTC One s tmo, HBoot 1.14.004, I recently flashed twrp 2.3.3.0 and it won't flash or wipe roms...it boots into recovery half the time...I tried flashing TD 9.0 and fastboot flashing the boot.IMG......to no avail.. please help
Sent from my HTC VLE_U using xda app-developers app
Please list the exact steps you took, and explain the exact problem.
That way it will be easier to nail down the issue and give you help.
Unlocked phone via HTC...flashed twrp 2.3.3.0 via fastboot, booted into fastboot did a full wipe, flashed trickdroid 9.0 and it wouldn't finish flashing at the point when it was trying to flash the kernel, I rebooted to fastboot and flashed the boot.img.....did that multiple times..just bootloops to recovery
Sent from my HTC VLE_U using xda app-developers app
handman29 said:
Unlocked phone via HTC...flashed twrp 2.3.3.0 via fastboot, booted into fastboot did a full wipe, flashed trickdroid 9.0 and it wouldn't finish flashing at the point when it was trying to flash the kernel, I rebooted to fastboot and flashed the boot.img.....did that multiple times..just bootloops to recovery
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Do full wipe and the use the recovery to reboot back into it then flash rom without the wipe.
handman29 said:
Unlocked phone via HTC...flashed twrp 2.3.3.0 via fastboot, booted into fastboot did a full wipe, flashed trickdroid 9.0 and it wouldn't finish flashing at the point when it was trying to flash the kernel, I rebooted to fastboot and flashed the boot.img.....did that multiple times..just bootloops to recovery
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Wipe and try again... You got impatient the boot.IMG part takes a long time... Just start the flash and put your phone down... Leave it alone until its done...if you don't get an error it will finish just wait...
Sent from my HTC One S using xda premium
Yeah, dont interrupt the installer. It installs some other important stuff after the boot.img.
And yes, it takes a long time. If nothing has happened after 15min or so, then it might be something wrong.
For me, the boot.img part seems to take between 5 and 10min, depending on the weather outside, the alignment of the stars etc
Hi all, I just wanted to start by saying that xda is the shizz and has helped me through thick n thin. Anywho, I have a custom Rom and am trying to go to a different Rom. ViperX to be specific. I've tried before, but with little success. Extracted boot.img, fastboot flash boot boot.img in the command, put the Rom on my sd and installed via TWRP. Problem is, is that it never boots, only the HTC boot screen with the red writing. Anyone have any suggestions on what I need to do? I'm still S-on, but from what I understand, that doesn't matter if you fastboot the boot.img via command prompt. I also have Hboot 1.14.
Thanks.
Chuckles850 said:
Hi all, I just wanted to start by saying that xda is the shizz and has helped me through thick n thin. Anywho, I have a custom Rom and am trying to go to a different Rom. ViperX to be specific. I've tried before, but with little success. Extracted boot.img, fastboot flash boot boot.img in the command, put the Rom on my sd and installed via TWRP. Problem is, is that it never boots, only the HTC boot screen with the red writing. Anyone have any suggestions on what I need to do? I'm still S-on, but from what I understand, that doesn't matter if you fastboot the boot.img via command prompt. I also have Hboot 1.14.
Thanks.
Click to expand...
Click to collapse
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Will do thank you
Sent from my HTC One XL using xda app-developers app
exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Apparently there's a TWRP 2.4.4 out, would it hurt me to flash the latest version?
Sent from my HTC One XL using xda app-developers app
Yes. It would hurt anyone with a one xl as 2.4 does not wipe our device properly. I tested 2.4.4 myself.
Sent from my HTC One X using xda app-developers app
ok, well I found another problem you might be able to help me with, but I'll shoot it to you anyway. I just found out my phone was originally a One X when I got it from the ATT store. Now apparently after I flashed the Rom I got (odex-JB-Sense4+.zip), It's saying my phone is an XL. Seems to me I have a whole new set of issues. Did I flash the wrong Rom? I though I did enough research to find a compatible Rom. How do I find out for sure what's going on with my phone and how to fix it properly?
Chuckles850 said:
ok, well I found another problem you might be able to help me with, but I'll shoot it to you anyway. I just found out my phone was originally a One X when I got it from the ATT store. Now apparently after I flashed the Rom I got (odex-JB-Sense4+.zip), It's saying my phone is an XL. Seems to me I have a whole new set of issues. Did I flash the wrong Rom? I though I did enough research to find a compatible Rom. How do I find out for sure what's going on with my phone and how to fix it properly?
Click to expand...
Click to collapse
No problem you have the correct ROM, if you had flashed wrong one it would have not worked correctly. Depending on the ROM sometimes it will show XL instead of X.
One xl is the proper model name, code named Evita, not to be confused with the real HTC One X international quad core version.
So in other words, nothing is wrong. This is normal. If you flashed the wrong rom you would know as you would now have a paperweight
Sent from my HTC One X using xda app-developers app
ok cool, I was kinda confused there for a sec lol. Ok, now for the TWRP. I'm assuming you were referring to 2.3.0.0? just because there is a 2.3.0.0, 2.3.1.0, 2.3.3.0, and a 2.3.3.1. I just want to make sure I have the correct one for Hboot 1.14
Doesn't matter which one. I use 2.3.3.1 myself.
Sent from my HTC One X using xda app-developers app
You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium
ok, downloading it now. I'll keep you updated.
bkmo said:
You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Ah I didn't catch that in the first post! Good eye.
bkmo said:
You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
ok, I'll keep that in mind. Thank you!!
exad said:
Ah I didn't catch that in the first post! Good eye.
Click to expand...
Click to collapse
it's ok bud, just downloaded and installed TWRP 2.3.3.1 successfully, now i'm downloading ViperXL and hope everything comes out ok
exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Should I need to be thinking about Kernels of any sort?
Chuckles850 said:
Should I need to be thinking about Kernels of any sort?
Click to expand...
Click to collapse
Yeah.......give bulletproof 1.1 a shot. Gonna give you better performance and battery, plus a no brainer install and its stable.
Sent from my Transformer TF101 using xda premium
bkmo said:
Yeah.......give bulletproof 1.1 a shot. Gonna give you better performance and battery, plus a no brainer install and its stable.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Ok cool. Any links?
Sent from my HTC One X using xda app-developers app
It's in Android development page. if not the first page then the second.
exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
Click to expand...
Click to collapse
Except for ViperXL (and old builds of CleanROM, which may also happen with future builds if/when scrosler gets AROMA back in there) which is intended to flash the boot.img in AROMA.
Although, it doesn't always work for some folks, so they have had to flash boot.img manually. So yes, if at all in doubt (and you have a boot loop) flash boot.img manually.
Okay so Im trying to install miui v5 but im having isuues getting it to boot...again. ok so when v4 3.2.22 first came out I couldnt get it to boot. I would install the rom, then gapps and could not get it to boot past the optimizing apps screen. it would just stay at starting apps. I was told by another user to flash rohans kernel version b5 as that has worked for him on a different rom, and it worked for me. Now trying to install V5 its been a nightmare. when just installing the rom, then gapps I could not get it to boot past the splash screen. it would load it for a second then just go to a black screen. I then tried installing rohans kernel version b5 but now I get stuck at the starting apps screen I tried wiping cache and dalvik and that did nothing. tried installing different kernels and most I tried wouldnt let me get past the boot animaion Im using twrp 2.3.1.0, Im s-off and I even tried lowering my hboot from 1.14 to 1.09 just incase that might be it but nope. im no sure what else to do and help would be greatly appreciated
avery.0 said:
Okay so Im trying to install miui v5 but im having isuues getting it to boot...again. ok so when v4 3.2.22 first came out I couldnt get it to boot. I would install the rom, then gapps and could not get it to boot past the optimizing apps screen. it would just stay at starting apps. I was told by another user to flash rohans kernel version b5 as that has worked for him on a different rom, and it worked for me. Now trying to install V5 its been a nightmare. when just installing the rom, then gapps I could not get it to boot past the splash screen. it would load it for a second then just go to a black screen. I then tried installing rohans kernel version b5 but now I get stuck at the starting apps screen I tried wiping cache and dalvik and that did nothing. tried installing different kernels and most I tried wouldnt let me get past the boot animaion Im using twrp 2.3.1.0, Im s-off and I even tried lowering my hboot from 1.14 to 1.09 just incase that might be it but nope. im no sure what else to do and help would be greatly appreciated
Click to expand...
Click to collapse
Wipe everything. Install your rom only. Does it boot?
exad said:
Wipe everything. Install your rom only. Does it boot?
Click to expand...
Click to collapse
no. It loads the splash screen for a second then goes to a black screen.
You've verified the md5 right?
Boot to bootloader/fastboot and do fastboot erase cache in command prompt then wipe everything cache, dalvik, system, factory reset, then flash rom.
Does it boot?
Sent from my HTC One X using xda app-developers app
exad said:
You've verified the md5 right?
Boot to bootloader/fastboot and do fastboot erase cache in command prompt then wipe everything cache, dalvik, system, factory reset, then flash rom.
Does it boot?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
redownloaded 3 times. erased cache. wiped everything and same problem as before loads splash screen then back screen
Redownloading != checking md5 you could Redownload 500 times and all 500 downloads could have corruption of some sort.
You did fastboot erase cache?
If you're positive your download is good and after fastboot erase cache and wiping everything isn't working. Your last step is to s-off if you're not already and ruu to the latest version then flash twrp then wipe everything then flash the rom.
Sent from my HTC One X using xda app-developers app
exad said:
Redownloading != checking md5 you could Redownload 500 times and all 500 downloads could have corruption of some sort.
You did fastboot erase cache?
If you're positive your download is good and after fastboot erase cache and wiping everything isn't working. Your last step is to s-off if you're not already and ruu to the latest version then flash twrp then wipe everything then flash the rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Just making sure since I have only researched slightly, since im s-off If i run the latest unrootable RUU Id still be able to unlock bootloader and regain root?
What other roms have you tried to flash? Is Mui the only ones giving you problems? Try other ones to see if it is not a bad twrp. It may not be wiping correctly.
Sent from my HTC One X using xda premium
Venomtester said:
What other roms have you tried to flash? Is Mui the only ones giving you problems? Try other ones to see if it is not a bad twrp. It may not be wiping correctly.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
every other rom ive flashed boots fine its only miui that gives me problems. It boots for other people fine so I dont think its the rom and I tried to install on CWM and still have issues
I had the same problem with Chameleon. Took four different downloads to get it. Avatar took a few too lol. Take above advice. Check sum. Might even try wiping cache in adb.
Sent from my HTC One X using xda premium
Venomtester said:
I had the same problem with Chameleon. Took four different downloads to get it. Avatar took a few too lol. Take above advice. Check sum. Might even try wiping cache in adb.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
noob question but how do I find the md5?
avery.0 said:
noob question but how do I find the md5?
Click to expand...
Click to collapse
Search MD5 Sum Checker. It's a program that is pretty self explanatory and will check it for you. The MD5 is attached to the download. You copy it from the site and past it in the checker.
And after you s-off you don't need to re lock to ruu so you won't lose bootloader unlock
Sent from my HTC One X using xda app-developers app
Running the 3.18 RUU fixed my problems. Thank you both for the help
Sent from my HTC One X using xda premium
(Sorry if this is in the wrong forum, someone told me to come over here)
So yesterday, I was unlocking bootloader on my phone. (I'm noob at this)
Everything went fine. I was wanting to install JellyBean...
Then, I had to root my phone, I downloaded a program called ClockWorkMod and used it.
So I rooted my phone and it kept restarting, over and over again.
I can't use it, it keeps shutting off and restarting. (With red text under the HTC logo telling me about HTC's legal terms or something)
What do I do?
:crying:
Thank you!
Try wiping the cache and the davlik cache and then install jelly bean again!!! After doing this, again wipe the cache and davlik cache...good luck!!
Sent from my SK17i using xda premium
binoyw said:
Try wiping the cache and the davlik cache and then install jelly bean again!!! After doing this, again wipe the cache and davlik cache...good luck!!
Sent from my SK17i using xda premium
Click to expand...
Click to collapse
How do I do that??!?!
You rooted your phone and you don't know how to wipe cache and dalvik cache? That's messed up
Sent from my One X using xda app-developers app
binoyw said:
Try wiping the cache and the davlik cache and then install jelly bean again!!! After doing this, again wipe the cache and davlik cache...good luck!!
Sent from my SK17i using xda premium
Click to expand...
Click to collapse
Okay I did that, didn't work.
I saw on how to do it.
At the top of my screen it says
TAMPERED
RELOCKED
Security Warning.
You're bootloader is locked..
You can't install any recovery with a locked bootloader. What carrier are you with?
You're playing a dangerous game messing with this without knowing the basics my friend.
Sent from my One X using xda app-developers app
committed esornnic
exad said:
You're bootloader is locked..
You can't install any recovery with a locked bootloader. What carrier are you with?
You're playing a dangerous game messing with this without knowing the basics my friend.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I'm with TELUS,
I managed to find a thread, http://forum.xda-developers.com/showthread.php?t=2063949&page=8
I unlocked bootloader on HTCDev.
I followed the steps on the thread I just linked.
Still bootlooping
What should I do?
What hboot are you on? What recovery/version did you flash?
Sent from my One X using xda app-developers app
exad said:
What hboot are you on? What recovery/version did you flash?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
HBOOT- 2.14.0000
I got the latest from this link,
http://get.cm/?device=endeavoru
I'm pretty sure it's like the latest
jelly bean.
AndroidSoldier said:
HBOOT- 2.14.0000
I got the latest from this link,
http://get.cm/?device=endeavoru
I'm pretty sure it's like the latest
jelly bean.
Click to expand...
Click to collapse
What does it say on the bootloader screen? Do you see "evita" or "endeavor"?
You flashed rom for the Tegra One X/Endeavour. If you have a One XL/Evita, that's not going to work.
iElvis said:
What does it say on the bootloader screen? Do you see "evita" or "endeavor"?
You flashed rom for the Tegra One X/Endeavour. If you have a One XL/Evita, that's not going to work.
Click to expand...
Click to collapse
Yes! It says EVITA, the full thing says EVITA PVT SHIP S-ON RL.
What should I do then?
Is there roms that are similar to jellybean
that I can install?
Sense roms: http://forum.xda-developers.com/forumdisplay.php?f=1541
Aosp ROMs: http://forum.xda-developers.com/forumdisplay.php?f=1726
I recommend using twrp 2.3.3.1 or under instead of cwm. After flashing a new recovery always do fastboot erase cache
Sent from my One X using xda app-developers app
exad said:
Sense roms: http://forum.xda-developers.com/forumdisplay.php?f=1541
Aosp ROMs: http://forum.xda-developers.com/forumdisplay.php?f=1726
I recommend using twrp 2.3.3.1 or under instead of cwm. After flashing a new recovery always do fastboot erase cache
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Thanks, Ill see if I can use those.
By the way, is TWRP something I have to install on my phone?
Or do I do that after. Cause' I can't get passed the boot loop on my phone.
You need a recovery to flash roms
You should be able to boot to bootloader then fastboot flash recovery recoveryfilename.img then fast boot erase cache then fastboot reboot-bootloader then select recovery on your phone then you can mount USB wipe and flash ROMs from there
Sent from my One X using xda app-developers app
exad said:
You need a recovery to flash roms
You should be able to boot to bootloader then fastboot flash recovery recoveryfilename.img then fast boot erase cache then fastboot reboot-bootloader then select recovery on your phone then you can mount USB wipe and flash ROMs from there
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Still stuck on boot loop.
exad said:
You need a recovery to flash roms
You should be able to boot to bootloader then fastboot flash recovery recoveryfilename.img then fast boot erase cache then fastboot reboot-bootloader then select recovery on your phone then you can mount USB wipe and flash ROMs from there
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Oh nevermind! It works!!! I just had to wait.
Thank YOU so much! Now I just have to see on how to root my HTC One XL properly and how to
get custom roms.
If this happens again I can just use your method.
THANK YOU!!