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
Related
I have an att htc one x that has 4.01 and 2.20 software. I was able to successfully root the phone and now I'm trying to install CM10 but it's failing when trying to install.
It says it missing a MD5 File and says theres an error in the SD card/download/ the cm 10 file.
What am I doing wrong? Thank you
Make sure the Rom is for our phone and check the md5 sum it might be a bad download
I've tried redownloading the file several times and I'm still getting the same error message.
I'm downloading CM10 from here http://get.cm/?device=endeavoru
kswannabe said:
I've tried redownloading the file several times and I'm still getting the same error message.
I'm downloading CM10 from here http://get.cm/?device=endeavoru
Click to expand...
Click to collapse
Wrong version, endeavoru is the international (Tegra3) One X. Our phone is code named evita.
Just stick to the Development forum here, to avoid flashing ROMs for the wrong version of the One X:
http://forum.xda-developers.com/forumdisplay.php?f=1726
Thanks for the information.
Was able to successfully flash to CM10 but I'm stuck at the CM10 boot screen. Circle going counter clock wise around. What should I do?
kswannabe said:
Thanks for the information.
Was able to successfully flash to CM10 but I'm stuck at the CM10 boot screen. Circle going counter clock wise around. What should I do?
Click to expand...
Click to collapse
If you flashed an international rom, there's a good possibility you messed something up. Factory reset, wipe /system, and try flashing the correct CM10 rom again.
Ok. I'm trying to do a factory reset from bootloader but whenever I do, it goes to the CM10 boot screen where I was earlier. How can I do a factory reset?
kswannabe said:
Ok. I'm trying to do a factory reset from bootloader but whenever I do, it goes to the CM10 boot screen where I was earlier. How can I do a factory reset?
Click to expand...
Click to collapse
A guy I was working with had the boot screen splash. If you've flashed the correct one, then wipe your caches. if that doesn't work reflash.
kswannabe said:
Ok. I'm trying to do a factory reset from bootloader but whenever I do, it goes to the CM10 boot screen where I was earlier. How can I do a factory reset?
Click to expand...
Click to collapse
Don't do it from bootloader, it can corrupt your sdcard. Do it from recovery.
Go into recovery, wipe cache, dalvik cache, factory reset and system. Then install the CORRECT rom.
Sent from my One X using xda premium
How can I reflash?
Thanks
-edit-
I was able to get back into TWRP. There I tried to do a factory reset but it tells me it failed. And after installing CM10, do I have to go back into bootloader and flash boot.img from the CM10 nightly zip file?
And there goes my stock rom... Factory reset is not working on TWRP and tried system reset thinking it would get rid of CM10 but instead erased my stock rom.
Please help, need a working phone soon..
kswannabe said:
How can I reflash?
Thanks
-edit-
I was able to get back into TWRP. There I tried to do a factory reset but it tells me it failed. And after installing CM10, do I have to go back into bootloader and flash boot.img from the CM10 nightly zip file?
Click to expand...
Click to collapse
There are stickies and tuts around here for this.. but, the reason why it's not working for you is you didn't flash the boot.img first. before you installed the .zip. Also, you'll need the latest gapps for that ROM as well.
Not familiar with the forums around here, so if you could link me some of these stickies or tutorial it would be great.
Have a look here
Sent from my One X using xda premium
timmaaa said:
Have a look here
Sent from my One X using xda premium
Click to expand...
Click to collapse
or here http://forum.xda-developers.com/showthread.php?t=1952076
I have this problem. i went to the thread you posted, loaded TWRP, I've factory reset and what not, but now I'm stuck in TWRP without any real viable options. When I try to reboot to system, it brings me back to TWRP menu.
mfc1288 said:
I have this problem. i went to the thread you posted, loaded TWRP, I've factory reset and what not, but now I'm stuck in TWRP without any real viable options. When I try to reboot to system, it brings me back to TWRP menu.
Click to expand...
Click to collapse
Do you have a rom flashed? If so, wipe both caches and reboot. If that doesn't work, reflash and do a system wipe from TWRP.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Rooted SGH-T989D trying to flash CM10
kswannabe said:
How can I reflash?
Thanks
Click to expand...
Click to collapse
hi. i have fallowed all the steps to root my phone from this site. when i go down to how to flash a rom i have some issues.
i am trying to flash CM10. when i go to install on (step 8) i get an errer. my screen says
Updating partition details...
Running boot script...
Finished running boot script.
E:Unable to open zip file.
Error flashing zip /external_sd/cm-10.1-hercu
Updating partition derails...
then it shows the home butten. failed in red than wipe cach/dalvik and reboot system buttons
anyone have any idea what im doing wrong?
Exactly which phone do you have? It looks like it says Hercules in the cm file name you wrote, which I think is a Samsung.
Sent from my Evita
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.
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.
Background details. I have TWRP 2.4.4.0 installed, rooted, S-OFF. I had Viper XL installed, but wanted to try a stock JB rom. I downloaded CleanROM, booted into recovery. From here:
-wiped cache
-wiped dalvik cache
-System reset
-wiped system
From here, I go to install CleanROM. It runs aroma installer, I choose my options, and follow on screen prompts. It seems to flash too quickly (like it's not installing). It says successful, and gives me the option to go home, wipe cache/dalvik, or reboot. If I click reboot, it says No OS installed, are you sure you want to reboot?
I tried rebooting, and it stops in the white bootup screen. Not sure what step I am missing here. I didn't think that I needed to flash boot.img since I have S-OFF, but is that the case? Any help would be great - THANKS!
opto_isolator said:
Background details. I have TWRP 2.4.4.0 installed, rooted, S-OFF. I had Viper XL installed, but wanted to try a stock JB rom. I downloaded CleanROM, booted into recovery. From here:
-wiped cache
-wiped dalvik cache
-System reset
-wiped system
From here, I go to install CleanROM. It runs aroma installer, I choose my options, and follow on screen prompts. It seems to flash too quickly (like it's not installing). It says successful, and gives me the option to go home, wipe cache/dalvik, or reboot. If I click reboot, it says No OS installed, are you sure you want to reboot?
I tried rebooting, and it stops in the white bootup screen. Not sure what step I am missing here. I didn't think that I needed to flash boot.img since I have S-OFF, but is that the case? Any help would be great - THANKS!
Click to expand...
Click to collapse
Flash twrp 2.3.3.1 and reflash rom. Also verify md5 of Rom download. And if you want a great jb Rom give magio Rom a run. It's my daily driver and is amazing
Sent from my HTC One XL using xda premium
THANKS! That seemed to work. Why do some roms work with newer versions of TWRP, and some do not? That's odd. I installed Viper XL with 2.4.
opto_isolator said:
THANKS! That seemed to work. Why do some roms work with newer versions of TWRP, and some do not? That's odd. I installed Viper XL with 2.4.
Click to expand...
Click to collapse
All versions of twrp past 2.3.3.1 have issues. Be it wiping or flashing on the evita.
And if it helped just hit the thanks button
Sent from my HTC One XL using xda premium
31ken31 said:
All versions of twrp past 2.3.3.1 have issues. Be it wiping or flashing on the evita.
And if it helped just hit the thanks button
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
This.... Reflash 2.3.3.1 or previous. Had ypur issue months back, drove me balls crazy for a few weeks.
Sent from my HTC One XL using xda premium
Hi guys
I keep getting stuck on the the htc boot screen with the red text underneath when trying to install the 4.3.1 carbon rom for my Htc one s3.
Steps I've taken not necessarily in this order:
]I've unlocked my bootloader.
Downloaded the rom and gapps cm 10.2 to my sd card
flashed twrp 2.7.1 recovery
flashed the boot file
entered recovery clicked the recommended option for wipe
installed the rom and then gapps
cleared cache
reboot (Although just before rebooting it says that my phone is not rooted, would I like to install supersu to root it, which I did)
Am i missing something?
You are maybe forget to intick the fast boot it always make problem
Just boot to recovery and do a full wipe data cash and dalvic and reboot your phone
Sent from my HTC J One using XDA Free mobile app
zivenchy said:
You are maybe forget to intick the fast boot it always make problem
Just boot to recovery and do a full wipe data cash and dalvic and reboot your phone
Sent from my HTC J One using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
I had to untick the fastboot as it wasn't loading the bootloader. I did a factory wipe, flashed boot image, factory wipe again, installed cm10.2 but during installation I'm getting a failed error. Anyone know why this is?
Could it possibly be because I have no superuser app on my phone? is superuser needed?
Because you are not rooted that's why
Sent from my HTC J One using XDA Free mobile app
zivenchy said:
Because you are not rooted that's why
Sent from my HTC J One using XDA Free mobile app
Click to expand...
Click to collapse
Haha thanks that's part of the problem, I'm a noob to all this. I am now rooted using superSU v1.9x but still getting same problems.
I'm also trying to use sideload but it's just stuck saying 'starting adb sideload feature stuck'
Sorry for spamming the forum, but I just don't seem to be getting anywhere after hours trying..
My plan now is to go back to the stock rom, I just want to make sure I'm flashing the correct one
I think my phone is actually an S4 rather than S3.
hboot: 2.13.0000
radio: 1.11.50.05.28
tmob005
would this RUU be the correct one to install:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4 .exe
You're on Tmobile, i gues...
Search one for you're phone company, for you're country.