Hello, all. I am a pretty experienced flasher, and I have been running HatkaXL on my device for quite some time now. I saw where a new ROM had developed, and tried to flash it last night (with no luck). My device is S-ON (I would consider going S-OFF, I just do not understand the terminology with SuperCID and all that good stuff). Anyway, I downloaded the ROM, patch, and wiped (completely). I formatted /system, performed a factory data reset, wiped the cache and dalvik cache. I installed the ROM and patch, and tried to reboot afterwards. I went into a bootloop. I did a restore, downloaded both files again, but I put the boot.img file aside and flashed it separately (after the ROM and patch the next time). I still got a bootloop. Any suggestions?
Worked fine for me. I flashed it a few times due to trying to mod it and being unsuccessful lol.
Sent from my HTC One XL using Tapatalk 2
Method of Recovery
InflatedTitan said:
Worked fine for me. I flashed it a few times due to trying to mod it and being unsuccessful lol.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Just out of curiosity, were you using TWRP or CWM? I have been running the supported version of CWM (I have always liked it better for some reason). I think it's the cool hat and orange eye, but just wanted to see if maybe you used TWRP?!? Note: HatkaXL has been flashing flawlessly on CWM, so...just wondering.
mikenjen0524 said:
Just out of curiosity, were you using TWRP or CWM? I have been running the supported version of CWM (I have always liked it better for some reason). I think it's the cool hat and orange eye, but just wanted to see if maybe you used TWRP?!? Note: HatkaXL has been flashing flawlessly on CWM, so...just wondering.
Click to expand...
Click to collapse
I would use TWRP 2.3.3.1 or below (no issues and is compatible with all roms) If you intend to switch, after flashing a new recovery you should always fastboot erase cache.
When you say you flashed the boot.img seperately did you flash it in CWM or using fastboot? It should be done with fastboot.
SuperCID is just a changed CID to 11111111 or 22222222 from default. Default CID is different from carrier to carrier. If you have an AT&T phone and had to root/unlock bootloader, you have SuperCID.
Thanks
exad said:
I would use TWRP 2.3.3.1 or below (no issues and is compatible with all roms) If you intend to switch, after flashing a new recovery you should always fastboot erase cache.
When you say you flashed the boot.img seperately did you flash it in CWM or using fastboot? It should be done with fastboot.
SuperCID is just a changed CID to 11111111 or 22222222 from default. Default CID is different from carrier to carrier. If you have an AT&T phone and had to root/unlock bootloader, you have SuperCID.
Click to expand...
Click to collapse
I never knew about the fastboot erase cache thing (thanks). I got it just a few minutes ago. It would not go with just flashing the two files and then rebooting. I had to manually boot into bootloader, reboot my computer (to get fastboot to recognize my device), and then flashed the boot.img via adb. I don't know why it was such a bugger, but I finally got it.
Related
I'm having problems flashing my Desire S with ICS based roms. GB roms work fine, but any ICS rom I flash gets stuck on boot on a lit up black screen. I have tried a variety of roms, flashed both on CWM and 4EXT but the issue persists. Is there some kind of special procedure for ICS roms ?
Did you
1. Wipe all partitions except SD
2. Wipe dalvik + cache
Edit : And the procedures same for flashing ics and gb roms, unless the OP specifically tells you to do otherwise
I did all possible wipes and It's still the same. Any more ideas ?
tomkow4 said:
I did all possible wipes and It's still the same. Any more ideas ?
Click to expand...
Click to collapse
did u u unlock with HTCDEV.com ? if u did just flash the boot.img inside the rom you want if u never then either the rom takes a long time to boot or your not doing the wipe properly
give me some specs of your phone
Ok, I'll run through my process. I did unlock my phone via HTCDEV, then rooted it via SuperOneClick (meaning I still have HBoot 2.00.0002 and S-ON), then flashed it by flashboot with CWM, now I have 4EXT. What I always did whas do a wipe data/factory reset and flashed. Now inspired by vodka69er I did that and clear dalvik, cache, format all but sd - and then flashed - still the same.
tomkow4 said:
Ok, I'll run through my process. I did unlock my phone via HTCDEV, then rooted it via SuperOneClick (meaning I still have HBoot 2.00.0002 and S-ON), then flashed it by flashboot with CWM, now I have 4EXT. What I always did whas do a wipe data/factory reset and flashed. Now inspired by vodka69er I did that and clear dalvik, cache, format all but sd - and then flashed - still the same.
Click to expand...
Click to collapse
If you unlocked via htcdev you need to extract the boot.img from your desired ROM. After flashing the ROM you need to flash the boot.img manually via adb. You have to do this each time you flash a new ROM.
Sent by my fingers to your head.
He's been able to flash the gb based roms , only trouble with the ics ones. That means he already knows to flash the boot img separately(unlocked with htcdev) or am I missing something
Vodka69er said:
He's been able to flash the gb based roms , only trouble with the ics ones. That means he already knows to flash the boot img separately(unlocked with htcdev) or am I missing something
Click to expand...
Click to collapse
This. Exactly. I mean I have a MIUI GB rom so, I guess it's not about flashing a rom but trouble with ICS ones. So I figured that those must have something different about them or have a specific prerequisite. Others have flashed their D S's, so I'm kind of lost.
Can you post what you see on your bootloader
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT - 2.00.0002
Radio - 3822.10.08.04_M
eMMC - boot
Aug 22 2011, 15:22:13
@op
I know that this is covering old ground, but I've not seen an actual answer
Have you ever used 'fastboot flash boot NAME.IMG' command?
Swyped from my DesireS
http://www.androidauthority.com/desire-s-root-s-off-hboot-2-00-0002-superoneclick-74470/ - this is the guide I followed.
On a side note, I did a full wipe of everything I could and still no luck with ICS roms. I think I'll leave it alone.
You still didn't answer the question that I asked in the above post, the guide that you have doesn't cater for separately flashing the boot , which is what you need to do. The guide only tells you gore to instal recovery and root
Which (as people have been saying) means that i suspect that your ICS installs have no kernels and therefore don't/can't boot
What ROM are you running now?
As after wiping all nothing should boot, unless CWM wipe all doesn't wipe boot?
Swyped from my DesireS
ben_pyett said:
You still didn't answer the question that I asked in the above post, the guide that you have doesn't cater for separately flashing the boot , which is what you need to do. The guide only tells you gore to instal recovery and root
Which (as people have been saying) means that i suspect that your ICS installs have no kernels and therefore don't/can't boot
What ROM are you running now?
As after wiping all nothing should boot, unless CWM wipe all doesn't wipe boot?
Swyped from my DesireS
Click to expand...
Click to collapse
To answer directly - I don't remeber/don't think so. But honestly didn't care much since my roms ran. Right now I'm on MIUI.
But the remark on the kernel got me thinking - I don't really know how to approach this, should I find some kernel and flash it?
On your pc you need to open the ICS ROM zip file and take out a file called boot.img
After flashing the Rom you must then use the fastboot command from your PC, as you did when you flashed your recovery.
You must then issue the command 'fastboot flash boot boot.img'
see below for the full instructions
HappyEmu said:
If you unzip your ROM's Zip-file (the one you want to flash, you'll find a file called "boot.img". Move it into the same folder as your adb and fastboot executables (Android SDK) and flash it using fastboot.
To be a little more specific:
1. Extract boot.img from ICS rom zip file and move it in the same folder as your fastboot.exe (Android SDK) on your PC
2. Flash the ICS Rom as usual from recovery (don't forget to first perform the full wipe/format including the boot partition)
3. Boot into fastboot mode, connect your phone to your PC and flash boot.img using fastboot
Code:
fastboot flash boot $pathToYourBootIMG\boot.img
4. Reboot
Click to expand...
Click to collapse
Swyped from my DesireS
Your GB room worked as they were running on the stock kernel
ICS won't work this way.
As Ben has mentioned you need to flash the boot.img
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
eyahl said:
If you unlocked via htcdev you need to extract the boot.img from your desired ROM. After flashing the ROM you need to flash the boot.img manually via adb. You have to do this each time you flash a new ROM.
Sent by my fingers to your head.
Click to expand...
Click to collapse
*Bump*
Sent by my fingers to your head.
suku_patel_22 said:
Your GB room worked as they were running on the stock kernel
ICS won't work this way.
As Ben has mentioned you need to flash the boot.img
Click to expand...
Click to collapse
4EXT seems to flash the kernel upon installation of specific roms, but I still did it manually and ... nothing. It still goes into a coma upon boot. Maybe I'll do a video of what I'm doing when I get back from work, cause now I'm having problems with some other roms - they freeze on bootscreen. Maybe it has something to do with my phone being S-ON?
tomkow4 said:
4EXT seems to flash the kernel upon installation of specific roms, but I still did it manually and ... nothing. It still goes into a coma upon boot. Maybe I'll do a video of what I'm doing when I get back from work, cause now I'm having problems with some other roms - they freeze on bootscreen. Maybe it has something to do with my phone being S-ON?
Click to expand...
Click to collapse
I suspect that you're suffering the problem on other ROMS now as you're wiping the boot partition and therefore have no kernel.
[Q] How long do you wait on boot? you must be patient as first boot can take a while (although not longer than 10minutes).
A video would be a great way of showing the problem...Try to capture everything....
Your bootloader screen....
All the partition wipes
The Rom flash
The fastboot boot.img flash
and then what happens after...
Kind of noobish on my end, but as I was making the video - and did everything according to protocol just as earlier - it worked . I flashed BlackICE 5.5. Christ. Thanks anyway for the patience guys (I assume )
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
herzbert said:
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
Click to expand...
Click to collapse
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
el_smurfo said:
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
Click to expand...
Click to collapse
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Checked MD5?
torxx said:
Checked MD5?
Click to expand...
Click to collapse
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Same here... But fine now
herzbert said:
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Click to expand...
Click to collapse
Hey there,
I was having the same problems as you messioned. I flashed the boot.img through fastboot myself and some how it then worked Did not have an problems with flashing the boot.img before. But maybe its worth a try.
Of course you need to use fastboot!!
Did not try yet to flash the RUU. There was an update of CM10 yesterday. The heavy battery drain is gone with this update and there is no urgent need to go back to TrickDroid right now.
herzbert said:
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Click to expand...
Click to collapse
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Sent from my HTC VLE_U using Xparent SkyBlue Tapatalk 2
LikeaG2root said:
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Alright, so, what are these special steps? Can you tell? If its not flashing the within recovery and push the boot.img via fastboot to the phone I would be very interested. My previous HBoot version was 1.13. Flashing ROMs was never a big deal. Also not going to CM9 and back to sense based ROMs.
Click to expand...
Click to collapse
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
HighRoIIer said:
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
Click to expand...
Click to collapse
I did also flash the boot.img via fastboot. Why do you say that anyway? Is there another method to flash a boot.img?
you didn't mention wiping System as part of the full wipe--needs done
Partially solved
rugmankc said:
you didn't mention wiping System as part of the full wipe--needs done
Click to expand...
Click to collapse
Right, I did not mention it because system is wiped by TWRP during flashing the ROM. So there was no need to wipe it seperately. But maybe my mistake was not to wipe data and the new "asec" folder messed things up.
I'll never know because yesterday I did a complete wipe including the SDCard. Afterwards I was able to install TrickDroid flawlessly.
Thank you all for your efforts.
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Wipe flash Rom flash boot IMG sit back enjoy
ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Different kernel. it is using the 2.41 RUU. So go ahead and flash the boot.img
Here's what you should do for any new ROM with a different kernel.
Wipe System
Factory Reset
Flash boot.img
Flash the ROM
flash gapps (if AOSP based)
reboot and have fun
When doing a nandroid backup, it is only necessary to backup
System
Data
Boot
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
You backed up fine, it just takes up a little more space.
You have to extract the boot.img from the ROM and put it in the same folder as fastboot.exe
open command prompt, and navigate to the folder fasboot.exe is in and do the following command
fasboot flash boot boot.img
If it gets stuck at waiting for device, reboot into your bootloader, boot into fastboot from there. and then try again.
ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
Viper is the Rom u flash it from twrp it's. azip file that's fkashable so make it easy and flash viper there and than flash the boot IMG from fastboot the command is all over the forums I thinks it fastnoot flash boot.img
don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read
DvineLord said:
don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read
Click to expand...
Click to collapse
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.
ImagioX1 said:
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.
Click to expand...
Click to collapse
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom.
If you want true stock 2.20 then you will have to relock your bootloader and then run the 2.20 RUU. You would only want to do this if making a warranty claim or something. If you want stock rooted, then yes, do what I said above
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ok got it. I do appreciate your help. Flashing now.
downgrading only refers to the ruu not the zipped roms. so you can't run 1.85 ruu after running 2.20 ruu/ota but you can still flash a rom based on 1.85.
if you are reflashing the same rom you don't have to reflash boot.img but if you are flashing a new rom then you need to flash boot.img. 7-zip will tell you the crc32 of files so you see tell if it's a different checksum.
Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?
ImagioX1 said:
Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?
Click to expand...
Click to collapse
That's because you flashed the Voodoo mod, it's apart of the mod, theres a chinese part and a english one called "Dolby Digital" or "Dolby Surround"
When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?
CrossFire78 said:
When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?
Click to expand...
Click to collapse
Most people have good luck w/out flashing another radio.
ronnie498 said:
Most people have good luck w/out flashing another radio.
Click to expand...
Click to collapse
Hmm. Might there be a patch I'm missing out on? I just flashed one file -ViperXL 3.1.0 JB - Android File Host (692MB)
edit- Works now after another reinstall installed boot image first this time.
So my At&t One X (evita) has been rooted and the bootloader has been unlocked for some time now. I came from the old Htc Hero on Sprint, so I am use to rooting and flashing roms. The issue is I decided to try Cm10 and I flashed it correctly through the flash gui app. An update appeared at the top so I (like a noob) decided to install it.. I realized after the fact how I had messed up by not using flash gui (boot.img ,etc..) , So it would boot to the Htc logo and then just blackness would occur. I could and still could go to the bootloader successfully though. My mistake was doing a whole factory reset from the phone so no more TWRP recovery unit... I went back to the utility that I rooted and unlocked my bootloader on and relocked it just in case I needed to flash something such as a RUU (whatever that is) but I do have one ready to be installed. I tried to do it myself and kept getting the sentence in the picture posted... Can anyone help me??
that picture doesn't help much, my not relock bootloader run the .exe ruu. then reunlock and flash twrp then flash a rom? also flashimagegui doesnt flash a rom all it does it flash boot.img and modules or recovery. you still have to reboot into recovery and flash the rom zip. since youve used android before it is an easy fix. so fix it already =)
hrrsncrawford14 said:
So my At&t One X (evita) has been rooted and the bootloader has been unlocked for some time now. I came from the old Htc Hero on Sprint, so I am use to rooting and flashing roms. The issue is I decided to try Cm10 and I flashed it correctly through the flash gui app. An update appeared at the top so I (like a noob) decided to install it.. I realized after the fact how I had messed up by not using flash gui (boot.img ,etc..) , So it would boot to the Htc logo and then just blackness would occur. I could and still could go to the bootloader successfully though. My mistake was doing a whole factory reset from the phone so no more TWRP recovery unit... I went back to the utility that I rooted and unlocked my bootloader on and relocked it just in case I needed to flash something such as a RUU (whatever that is) but I do have one ready to be installed. I tried to do it myself and kept getting the sentence in the picture posted... Can anyone help me??
Click to expand...
Click to collapse
Had that happen to me. But just had to flash a kernel for it to boot properly. Everything fine after that.
Sent from my HTC One X using Tapatalk 2
THANKS!!! I have it working now thanks to the suggestions! :laugh::laugh:
DvineLord said:
that picture doesn't help much, my not relock bootloader run the .exe ruu. then reunlock and flash twrp then flash a rom? also flashimagegui doesnt flash a rom all it does it flash boot.img and modules or recovery. you still have to reboot into recovery and flash the rom zip. since youve used android before it is an easy fix. so fix it already =)
Click to expand...
Click to collapse
glad u got it working again. i would recommend doing s-off so you don't have to flash boot.img separately anymore.
I've spent hours, and obviously am not smart enough.
ATT One X, Followed the x-factor root exploit, but didn't realize how important the "and use a recovery ADB shell or install from an update.zip to install Superuser and su" sentence is.
Tried to install a custom ROM, TWRP works great but I wiped it and went for a new Viper install, flashed the boot.img, which I now realize probably won't boot because I don't have S-Off. It just circles. I run the latest SU.zip but it still won't work
I keep trying to install older ROM's but they don't work either. All I get is a black screen and it locks up. I assume because I have Hboot 1.14
So now I have a new hboot, new TWRP, it's "tampered" and "unlocked" but I can't boot up into an old OS, and I'm not S-Off'd so I can't boot into a new OS. The new GUI for S-Off looks like what I should have used, but it would appear that I need to boot into Android first.
What do I do?
You have to flash boot.img from fastboot
Download rom, check md5
Extract rom, copy boot.img
Paste boot.img in folder with fastboot
Copy rom zip to SD card
Wipe cache, dalvik cache, system, factory reset.
Flash rom
Reboot to bootloader
Fastboot flash boot boot.img
Reboot.
If 2.14 hboot, cm10.1 with 3.4 kernel is the only aosp rom with which the touchscreen will work.
All sense roms will work.
Sent from my HTC One X using xda app-developers app
---------- Post added at 08:00 PM ---------- Previous post was at 07:52 PM ----------
RollTribe said:
You have to flash boot.img from fastboot
Click to expand...
Click to collapse
I put the whole thing cut its also possible he didn't wipe properly or something
Sent from my HTC One X using xda app-developers app
exad said:
Download rom, check md5
Extract rom, copy boot.img
Paste boot.img in folder with fastboot
Copy rom zip to SD card
Wipe cache, dalvik cache, system, factory reset.
Flash rom
Reboot to bootloader
Fastboot flash boot boot.img
Reboot.
If 2.14 hboot, cm10.1 with 3.4 kernel is the only aosp rom with which the touchscreen will work.
All sense roms will work.
Click to expand...
Click to collapse
Ok, I did that and I get a variety of problems.
use TWRP to send over the .zip ROM
wipe cache (I let the ROM install do it and manually in TWRP, both the default and advanced and clicking the default "factory reset"
use "install" to select the correct zip with the boot.img copied to my HD for fastboot
reboot into bootloader, fastboot, use DOS, fastboot says "OKAY" twice
bulletproof and cleanROM both just lock up at the white HTC menu with the red developer font. ViperXL3.2.7 just reboots back into recovery mode.
Do I need to do something with SU or Superuser or is that after I actually get a ROM installed? My CID is nothing but 1's and these ROMS are double checked for the Evita
EDIT: Viper 2.4 loads another HTC boot screen with a snake, but then reboots.
Also, I'd be fine with putting it back to stock and starting over, but I've got a CID of 11111111 (didn't write down the original), S-On and software is 2.20, I keep reading about bricks when people tried that.
I have followed the various guides at least 5 times, such as this one http://forum.xda-developers.com/showthread.php?t=1957193 and nothing, I guess I need a way to step backwards.
chris948 said:
Do I need to do something with SU or Superuser or is that after I actually get a ROM installed? My CID is nothing but 1's and these ROMS are double checked for the Evita
Click to expand...
Click to collapse
You don't need SU to flash a ROM. Once the ROMs get booted up properly, they will be rooted by default.
What version of TWRP? The newer builds have been known to be problematic, with 2.5 not working at all with CleanROM (maybe others). Recommend version 2.3, or latest official CWM.
redpoint73 said:
You don't need SU to flash a ROM. Once the ROMs get booted up properly, they will be rooted by default.
What version of TWRP? The newer builds have been known to be problematic, with 2.5 not working at all with CleanROM (maybe others). Recommend version 2.3, or latest official CWM.
Click to expand...
Click to collapse
bingo, that's what I get for logging into a website and downloading the latest version. 2.3.3 and 2.3.1 didn't help but CWM and a different ROM finally did.
thanks
chris948 said:
Also, I'd be fine with putting it back to stock and starting over, but I've got a CID of 11111111 (didn't write down the original), S-On and software is 2.20, I keep reading about bricks when people tried that.
I have followed the various guides at least 5 times, such as this one http://forum.xda-developers.com/showthread.php?t=1957193 and nothing, I guess I need a way to step backwards.
Click to expand...
Click to collapse
I had this same problem, here's what I did:
1. wrote CID back to AT&T's CID (CWS__001), here's a list: http://droider.eu/infodocs/CID list.pdf
2. relocked bootloader
3. ran 2.20 RUU
4. unlocked booloader/ got superCID
5. installed TWRP custom recovery
6. Got S-OFF -THIS WAS THE STEP I SKIPPED THE FIRST TIME
7. ran 3.18 RUU
8. install whatever you want
Hope that helps