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.
Related
Especially for people who rooted their phones recently using X-Factor root exploit
"If you have the newer HBOOT 1.14 (you probably do if coming from stock 2.20), boot.img's will have to be flashed separately via fastboot. Extract the boot.img from you ROM zip of choice and put it in the same directory as fastboot. Reboot your device into boot loader and run "'fastboot flash boot boot.img' (no quotes)
You can then flash the ROM" - thanks to
Guylncognito721
How to flash Custom Recovery and ROM after 2.20 root - http://forum.xda-developers.com/showthread.php?p=33179690
More information
"if you are flashing similar ROMs ( having same kernel ).. there is no need to flash boot.img separately. But say if you wanna switch from sense to aosp you must do that as they have different kernels.
Again if you are just upgrading from older version to newer version of same ROM and if there are no kernel changes no need to flash it" (thanks kancherlapraneeth)
I have seen so many topics in Q&A thread regarding this issue, thought this would help ppl
Butchered my name...
Sent from my One X using xda app-developers app
GuyIncognito721 said:
Butchered my name...
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Sorry bro.. Corrected it
If you have flashed viperROM from stock 2.20 do you still have 1.14 boot? Do I still have to flash boot separate?
And would it be worth it to just ruu to 1.85
Sent from my HTC One XL using xda app-developers app
Kole_Ackerson said:
If you have flashed viperROM from stock 2.20 do you still have 1.14 boot? Do I still have to flash boot separate?
And would it be worth it to just ruu to 1.85
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yes.
Yes.
You can't ruu to 1.85 as downgrading hboot is not possible.
Sent from my One X using xda app-developers app
GuyIncognito721 said:
Yes.
Yes.
You can't ruu to 1.85 as downgrading hboot is not possible.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Oh wait, s-off is needed to downgrade isn't it.. haha blonde moment
Sent from my HTC One XL using xda app-developers app
Bumping this.
WR
Sent from my HTC One X
So what happens if you don't? I did the exploit and then installed Calkulin's ROM and it seems to be going fine without flashing the boot.img. Maybe this is why another ROM I tried didn't work (got stuck on the Paranoid Android screen).
ChummyDays said:
Because it stays on the stock kernel. Paranoidandroid got stuck because it probably can't run on the stock kernel... calkulin's ROM is somewhat close to the stock ROM (4.0.4 and sense)
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Aha, good to know. Thanks!
Ok I am getting "sending 'boot' (6156 KB)... FAILED (status read failed (Too many links)) any help?
The_new_user said:
Ok I am getting "sending 'boot' (6156 KB)... FAILED (status read failed (Too many links)) any help?
Click to expand...
Click to collapse
did you type
fastboot flash boot boot.img
absolutelygrim said:
did you type
fastboot flash boot boot.img
Click to expand...
Click to collapse
Yes I am in the correct directory and have my boot.img there I am typing fastboot flash boot boot.img I even tried fastboot erase cache but I am still getting the too many links error.
Going to try rebooting the computer and phone to see what happens I will report back if it fixes it.
Ok a reboot of the phone and comp was no help.
" OK I fixed it. All I did was change usb ports on my computer and it went straight through. " Hope this helps someone else later on.
need help
Can i please get some need some help
I'm currently on paranoid android 2.51 jb ROM. I did the root exploit since I was stuck on 2.20
And before I flashed paranoid android I made a twrp backup of stock sense.
Ok this is what I need help on because I was on 2.20 I had to flash the boot.img along with the custom ROM to get it working, now what I need to know is if I restore my twrp backup do I need to flash the boot.img so I can go back to stock? If so how can I get the boot.img from my backup that I made? I copied backup to my computer to look for the boot.img but there's nothing there
I wanted to post here before I make a new thread
TWRP restore does not boot
I used TWRP 2.3.1 to back up the rooted stock rom on my AT&T One X firmware 2.20. I then proceeded to flash Viper X 2.6.0 but the phone was stuck in boot loop even after I flashed the boot.img in the Viper zip file. I was able to get back into TWRP and run the restore. However, the phone continues to be in a boot loop even after the restore.
Did I miss any steps in the restore process for TWRP?
ViperX isn't for you phone. Your lucky you can get back into twrp. You need to flash your boot.img backup in fastboot.
For people trying to flash the style backup and can't find the boot.img you should be able to fastboot boot.emmc.win just as a normal boot.img.
http://forum.xda-developers.com/showthread.php?p=33743517
Sent from my One X using xda premium
Boot.img and now no image display
hello friends, was trying to root the One X att and for several times but reading the roms were not entered into the system, just by downloading the boot.img boot.img_1.88.707.2 and sent only the boot.img via fastboot, now put the original system goes, but not no picture on display, I can hear the sound of the system by opening and receiving emails but no picture. please help me because I do not know what else to do.
irosemberg said:
hello friends, was trying to root the One X att and for several times but reading the roms were not entered into the system, just by downloading the boot.img boot.img_1.88.707.2 and sent only the boot.img via fastboot, now put the original system goes, but not no picture on display, I can hear the sound of the system by opening and receiving emails but no picture. please help me because I do not know what else to do.
Click to expand...
Click to collapse
Can you give more details on what version are you on (2.20?)and are you able to boot??
Create a separate post in Q&A and many people will respond ,this not appropriate place to ask
Sent from my Nexus 4 using xda premium
I think I know what my problem was. I flashed the rom first THEN the boot.img. Which caused it to get stuck at the boot animation and I would have to go to the boot loader and flash the boo.img.
---------- Post added 12th February 2013 at 12:16 AM ---------- Previous post was 11th February 2013 at 11:40 PM ----------
sschrupp said:
So what happens if you don't? I did the exploit and then installed Calkulin's ROM and it seems to be going fine without flashing the boot.img. Maybe this is why another ROM I tried didn't work (got stuck on the Paranoid Android screen).
Click to expand...
Click to collapse
Ya same issue here too. My mistake was i flashed the boot.img after I flashed the rom. So now I'm rooting and flashing again and see if flashing boot.img the first time works.
I feel so stupid now. I kept doing fastboot boot boot.img. Not fastboot flash boot boot.img. No wonder it always stuck in the boot animation screen all the time. So I flash the boot img then i flash the rom from recovery? What do I wipe in TWRP?
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.
Hi everyone.
I have a TMOUS HTC One S (S4, mentioning because of some crazy people). I tried to install CyanogenMod 10 on it, but it fails. It just starts the splash screen.
Normally, I would flash an RUU, but now, the CID is HTC__001, and the Modelid PJ4011000. I am not allowed to install both European ROM and the stock TMOUS one. Oh, and to make things worse, it is relocked. Can someone help me, please???
mr_verystock
Unlock it, install custom recovery if you dont have it already, reflash the rom, fastboot flash the boot.img and it should start just fine.
Remember to wipe /system/, /data/, cache and dalvik-cache. Edit: Before you flash the rom, obviously.
Goatshocker said:
Unlock it, install custom recovery if you dont have it already, reflash the rom, fastboot flash the boot.img and it should start just fine.
Remember to wipe /system/, /data/, cache and dalvik-cache. Edit: Before you flash the rom, obviously.
Click to expand...
Click to collapse
Seems no one knows how to read any more... I'm pretty sure all ROM pages say flash boot.IMG... All these ROMs on this site flash and boot just fine if you follow directions...
Sent from my HTC One S using xda premium
$droyd$ said:
Seems no one knows how to read any more... I'm pretty sure all ROM pages say flash boot.IMG... All these ROMs on this site flash and boot just fine if you follow directions...
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Very true... I think Ive written around 400 posts in the S section now, and it feels like at least 350 of them contains "fastboot flash the boot.img" lol
Thank you all you guy's help!!! Yes, I did it by watching a video online(noob!!!), and followed your hints. Thanks!!! 10 thank to you.
mr_verystock said:
Thanks, but it fails to wipe dalvik-cache(remote: not allowed). Please help once more.
Click to expand...
Click to collapse
Re install twrp recovery.IMG with fast boot. Flash boot.IMG with fast boot.. Then wipe everything including SD card... Mount phone to PC with twrp and copy ROM to phone.. Flash ROM and wipe both caches again...
Sent from my HTC One S using xda premium
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.
Hello guys,
I've been looking around for CM11 for my HTC One X+.
Now I've found the original CM11 on their website for HOX+, but there is one little question I got about this.
http://download.cyanogenmod.org/?device=enrc2b
That's the link where I've found it by the way.
There is no boot.img download, how safe is it to just install the ROM? In my opinion it isn't.
So let me know what you guys think.
Sent from my HOX+
NiZii. said:
Hello guys,
I've been looking around for CM11 for my HTC One X+.
Now I've found the original CM11 on their website for HOX+, but there is one little question I got about this.
http://download.cyanogenmod.org/?device=enrc2b
That's the link where I've found it by the way.
There is no boot.img download, how safe is it to just install the ROM? In my opinion it isn't.
So let me know what you guys think.
Sent from my HOX+
Click to expand...
Click to collapse
Its on the official website, and It should work. Make a backup though.
The boot.img download isn't there because the boot.img is probably inside the .zip.
So open the zip and you'll have your boot.img.
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Its on the official website, and It should work. Make a backup though.
The boot.img download isn't there because the boot.img is probably inside the .zip.
So open the zip and you'll have your boot.img.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, already found it.
Thanks though.
One small question, if I'm going to put the .zip file on my SD card I can just leave the boot.img in the .zip right?
Sent from my HOX+
NiZii. said:
Yeah, already found it.
Thanks though.
One small question, if I'm going to put the .zip file on my SD card I can just leave the boot.img in the .zip right?
Sent from my HOX+
Click to expand...
Click to collapse
Well is your device s-off or s-on?
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Well is your device s-off or s-on?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
S-On, after hours of searching how to put S-Off I gave that up. Since I can't find it for my HTC One X+.
Sent from my HOX+
NiZii. said:
S-On, after hours of searching how to put S-Off I gave that up. Since I can't find it for my HTC One X+.
Sent from my HOX+
Click to expand...
Click to collapse
Oh okay, you will need to flash the boot.img alone then as flashing the ROM zip won't just work. So boot into bootloader, and flash the new boot.img you had extracted from the .zip
Once yo uhave flashed the .img boot into recovery mode and perform a gull wipe, including cache. Once done simply flash the zip and reboot.
First reboot takes a bit so be patient. I also recommend you getting a band backup in case.
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Oh okay, you will need to flash the boot.img alone then as flashing the ROM zip won't just work. So boot into bootloader, and flash the new boot.img you had extracted from the .zip
Once yo uhave flashed the .img boot into recovery mode and perform a gull wipe, including cache. Once done simply flash the zip and reboot.
First reboot takes a bit so be patient. I also recommend you getting a band backup in case.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ye I know it takes a lot of time since I've been flashing a ROM once before, but I can just leave the file in the .zip when flashing it in recovery?
Sent from my HOX+
NiZii. said:
Ye I know it takes a lot of time since I've been flashing a ROM once before, but I can just leave the file in the .zip when flashing it in recovery?
Sent from my HOX+
Click to expand...
Click to collapse
Yeah I suppose you can. Nothing will happen.
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Yeah I suppose you can. Nothing will happen.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Okay thanks.
Sent from my HOX+
NiZii. said:
Okay thanks.
Sent from my HOX+
Click to expand...
Click to collapse
No worries.
All the best.
Sent from my Nexus 5 using Tapatalk
If you're coming from a Sense ROM you can't just flash the zip without flashing the boot.img. It wouldn't even boot. And sometimes it boots but without mobile signal or WiFi signal.
So just place the zip on your sdcard, take the boot.img out of the zip on your computer.. Then boot into bootloader and connect it to the computer using USB then type
"fastboot flash boot boot.img"
Then "fastboot erase cache"
(you must have fastboot installed and configured on your computer)
Then boot into recovery and flash the zip file and gapps. Oh don't forget a wipe is mandatory if you're coming from sense ROM. But if you're coming from an AOSP ROM it's recommended but you can go without wiping. I flashed cyanogen over paranoid android without wiping data and had no issues at all. But I wiped the system partition.
And you cannot S-OFF an HTC One X+.. If it's S-ON then it stays that way. Only a few amount of people have S-OFF on their HOX+.
Oh and I don't think TWRP recovery is compatible with CM11 on HOX+.. So I recommend you flash philz recovery. Flash it by using the fastboot command "fastboot flash recovery recovery.img"
(recovery.img should be replaced with the name of the recovery you downloaded)
It doesn't take a lot of time. I change ROMs almost every week.
Please press the thanks button if I helped!
Sent from my One X+ using XDA Premium 4 mobile app
backb0ne5p1d0r said:
If you're coming from a Sense ROM you can't just flash the zip without flashing the boot.img. It wouldn't even boot. And sometimes it boots but without mobile signal or WiFi signal.
So just place the zip on your sdcard, take the boot.img out of the zip on your computer.. Then boot into bootloader and connect it to the computer using USB then type
"fastboot flash boot boot.img"
Then "fastboot erase cache"
(you must have fastboot installed and configured on your computer)
Then boot into recovery and flash the zip file and gapps. Oh don't forget a wipe is mandatory if you're coming from sense ROM. But if you're coming from an AOSP ROM it's recommended but you can go without wiping. I flashed cyanogen over paranoid android without wiping data and had no issues at all. But I wiped the system partition.
And you cannot S-OFF an HTC One X+.. If it's S-ON then it stays that way. Only a few amount of people have S-OFF on their HOX+.
Oh and I don't think TWRP recovery is compatible with CM11 on HOX+.. So I recommend you flash philz recovery. Flash it by using the fastboot command "fastboot flash recovery recovery.img"
(recovery.img should be replaced with the name of the recovery you downloaded)
It doesn't take a lot of time. I change ROMs almost every week.
Please press the thanks button if I helped!
Sent from my One X+ using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey i have htc one m7_ul and when ever i tried to flash cyanogenmod i ended up with so error like some binary problem do you know the fix for it???
Aisfkhan said:
Hey i have htc one m7_ul and when ever i tried to flash cyanogenmod i ended up with so error like some binary problem do you know the fix for it???
Click to expand...
Click to collapse
Whats the error exactly ? and where did you get the error ?
backb0ne5p1d0r said:
Whats the error exactly ? and where did you get the error ?
Click to expand...
Click to collapse
Its in twrp 2.6.3.3 and about some extracting binary failed error but now solved i flashed the boot.img file from cm11.zip file then flashed from philz recovery and everything goes fine