Hello,
I am trying to flash CleanRom 7.0 or any JB rom on my HTC One X (AT&T) but always gets stuck in bootloop (phone does not go past boot screen after flashing). This is what i have done.
The phone is on AT&T 1.82 stock room (rooted, SuperCID, S-Off). The phone was on some older HBoot version so I upgraded it to 2.15. Radio is 0.17.32.09.12. And I have TWRP recovery.
So I made a nadroid backup in recovery and than tried to install AT&T 3.82 rooted (downloaded from XDA, may be without radio and all). After successful flashing when I tried to reboot the system it got stuck on AT&T boot screen. So I rebooted in recovery and wiped everything. After that I tried to install CleanROM 7.0 R2 and same thing happened and even I tried latest elemental kernel but same thing is keep happening.
Can you please help me with this?
Thanks
At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita
timmaaa said:
At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita
Click to expand...
Click to collapse
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks
alex8525 said:
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks
Click to expand...
Click to collapse
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk
phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.omg after flashing.
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
Yes I am S-Off. I will let you know the version of TWRP when I get back home since I don't have phone with me right now. By the way I used goomanager to update TWRP, if that helps.
Thanks,
phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks
K so if you are s-off then you can just flash it. If you wernt then you would need to flash boot.img. now you can try to flash the boot.img. it might not fix it but start small and work up.
Sent from my HTC Butterfly s using Tapatalk
alex8525 said:
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks
Click to expand...
Click to collapse
TWRP is the correct way to install ROMs, but I have a feeling that your current version of TWRP is your problem. Some (2.4.x, 2.5.x) are buggy and have major problems. If your TWRP version is either of those that I've just mentioned you can update it to a known bug-free version like this:
Download the modified version of TWRP*2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
That's the reason I asked what twrp version he had
Sent from my HTC Butterfly s using Tapatalk
Related
I decided to downgrade to 1.85 for a fresh start after downgrading hboot to 1.09.000. 1.85, 1.73 RUUs failed and im trying 2.20 as we speak :// if this fails what are mmy options?
thanks
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
area51avenger said:
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
yes
twistedddx said:
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
Click to expand...
Click to collapse
I did this and I keep getting error 140- per this I am stuck in bl and I cant get adb
anyone? im in need of desperate help..
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
superchilpil said:
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Kole_Ackerson said:
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Click to expand...
Click to collapse
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
superchilpil said:
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
ok, I got the unlock token but its hanging on sending (0kb)
Kole_Ackerson said:
ok, I got the unlock token but its hanging on sending (0kb)
Click to expand...
Click to collapse
Make sure you're in fastboot not hboot
If that doesn't work reset your computer to make sure not programs are interfering with it
Sent from my One X using Tapatalk 2
it is in fastboot usb so ill reset my comp.
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
superchilpil said:
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Kole_Ackerson said:
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Click to expand...
Click to collapse
Nah don't worry about it!
Just helping out where I can
Sent from my One X using Tapatalk 2
Can only boot to bootloader and all RUU failed
I am in a bit of trouble at the moment. I will try to describe what I have done to end up where I am now.
I have a Telstra HTC One XL. Recently upgraded an already unlocked, rooted HOXL to JB using the OTA update (big mistake I know now). This upgraded the hboot to 2.14 and software to 3.17.8xxx.
Spent a lot of time trying to re-root. TWRP didn't work (no touch response). So I eventually found the Interim CWM Recovery (no touch) by Modaco. This seemed to work well and I managed to root the phone.
Then i followed the instructions to flash to KingBeatZ 1.2.0 ROM. Booted fine but had no touch response too.
So I wiped KingBeatZ 1.2.0 and went for the nightly CM10. Again, booted fine but no touch response.
OK, so I figured I should just go back to my restored data. Tried that but apparently no restore data (didn't realise a wipe wiped the restore data as well, what is the point of that?)
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
I do not know what I should do now to restore any functionality to my HOXL. Any help would be greatly appreciated.
o0okiato0o said:
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
Click to expand...
Click to collapse
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
redpoint73 said:
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
Click to expand...
Click to collapse
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
superchilpil said:
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
o0okiato0o said:
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
Click to expand...
Click to collapse
Take a stock ROM and pull out the boot.img
And fastboot flash boot boot.img just to make sure it flashes
Then flash the ROM in recovery
Sent from my One X using Tapatalk 2
As the title says my phone is stuck on the "initiating swagger" bootscreen from my last ROM. So initially I was trying to try out a new 4.3 based rom, but eventually figured out it wasn't working because my HBOOT is too old (1.14.002). From what I gather in order to upgrade my HBOOT safely, I need S-OFF. I had unlocked bootloader and SUPERCID but never got S-OFF. So I tried to restore to the backup I mad in TWRP, but that wouldn't make it past the bootloader, so I downloaded another 4.1.2 ROM instead, which got me to the previously mentioned bootscreen and thats as far as I go. What can I do from here? I gone through countless times, wiping cache,data, factory reset then installing rom, the loading boot.img, but I'm stuck. Any help would be appreciated.
At&T htc one x
hboot 1.14.002
If you're s-on you need to flash the boot.img from the ROM zip via fastboot.
And yes you must have s-off to safely run the 3.18 RUU to meet the requirements for the 4.2.2 ROMs.
Sent from my Evita
timmaaa said:
If you're s-on you need to flash the boot.img from the ROM zip via fastboot.
And yes you must have s-off to safely run the 3.18 RUU to meet the requirements for the 4.2.2 ROMs.
Sent from my Evita
Click to expand...
Click to collapse
I have been flashing the boot.img through the bootloader via fastboot. No luck.
Which version of TWRP are you using?
Sent from my Evita
timmaaa said:
Which version of TWRP are you using?
Sent from my Evita
Click to expand...
Click to collapse
TWRP 2.5
That's good problem, 2.5 is full of bugs. You need to upgrade to at least the 2.6 version. Here's how:
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and try again.
Sent from my Evita
Awesome, that worked. Now in order to flash a 4.3 mod I need to get S-off and then upgrade the hboot, right? How to I upgrade the hboot?
Thanks a lot.
Actually nevermind, I put hboot 2.14 on there and am now running PACman rom. Thanks again.
Hi everyone, I've yet to successfully load a custom ROM on my ville but I have got s-off and supercid. I'm currently on relocked bootloader running the total stock android 4.1. I'd just like to check through the steps I need to take to try a new 4.4.2 ROM. I was thinking of trying twistedkat.
1. Unlock bootloader (I already have the unlock file from htcdev)
2. Load custom recovery (I have TWRP 2.6.3.0 ready to go)
3. Flash SuperSU
4. Flash Rom file (do I need to unzip or flash the zip file in the recovery?)
5. Flash 4.4 Gapps
Any other steps I've missed? I'm on hboot 2.15, kernel 3.14 from the stock updater.
Thanks very much
fatboyslimerr said:
Hi everyone, I've yet to successfully load a custom ROM on my ville but I have got s-off and supercid. I'm currently on relocked bootloader running the total stock android 4.1. I'd just like to check through the steps I need to take to try a new 4.4.2 ROM. I was thinking of trying twistedkat.
1. Unlock bootloader (I already have the unlock file from htcdev)
2. Load custom recovery (I have TWRP 2.6.3.0 ready to go)
3. Flash SuperSU
4. Flash Rom file (do I need to unzip or flash the zip file in the recovery?)
5. Flash 4.4 Gapps
Any other steps I've missed? I'm on hboot 2.15, kernel 3.14 from the stock updater.
Thanks very much
Click to expand...
Click to collapse
1- if you didn't unlock your bootloader, you have to
2- i don't know which twrp you have but you shuld use the one from twistedkat thread (it's different from official one)
3- it's unrelated with custom rom flashing
4- DON'T unzip the rom, just flash the zip from recovery
5- you have to flash g-apps if want to use google's apps (gmail, playstore, etc.)
you don't need anything else AFAIK
have fun
Sent from my One S using xda app-developers app
By the way i recommend you to change your cid back to original, because supercid has no advantage over original cid. But one day you may want to turn back to stock and if you forget that your device has supercid it will brick the device
Sent from my One S using xda app-developers app
Do not forget to flash boot.img in fastboot! To do it, you need to extract boot.img from ROM zip file to same directory with fastboot on your computer and and reboot your device to fastboot mode. Then run this in terminal/cmd: fastboot flash boot boot.img . If you don't do this, your device won't boot to OS. Flashing SuperSU with a custom ROM is unnecessary since root usually is included in custom ROM.
EDIT: You don't need to flash boot.img, because you have S-OFF. Didn't notice it first.
ka_55 said:
By the way i recommend you to change your cid back to original, because supercid has no advantage over original cid. But one day you may want to turn back to stock and if you forget that your device has supercid it will brick the device
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Oh no! I've already ran a RUU with supercid to get back to total stock and that didn't cause any problems. Problem is I don't actually know what the original cid was!
fatboyslimerr said:
Oh no! I've already ran a RUU with supercid to get back to total stock and that didn't cause any problems. Problem is I don't actually know what the original cid was!
Click to expand...
Click to collapse
I checked again, ruu doesn't seem cause a brick but ota updates may cause such thing. So i think you shouldn't install ota updates till you remember your original cid
Sent from my One S using xda app-developers app
Thanks for the replies guys. One last question. If I load Twistedkat, which is based on CM11, I'll lose Sense?
Can I have sense as well? Is there a flashable sense zip file or something?
Thanks!
You will absolutely lose sense, and there is no way to install sense with kitkat roms right now for our one s
Sent from my HTC One S
See attached screenshot. Now successfully on 4.4.2.
I did need to get SuperSU. Thanks for all the help
Help im new!
Soo i recently got my htc one x on android jelly bean 4.2.2 from at&t and is there a method or easy root method for this version? 4.2.2, with 5.18? I really want to try and root my phone but i know nothing about messing with all these types of files, and i dont want to risk destroying my phone.
Im not sure if there is already a post or something about this and if it is im sorry, these forums are a bit overwhelming and i am new.
I would very much appeircate any help or info on being able to easily root my htc one x 4.2.2, 5.18 at&t white.
The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita
timmaaa said:
The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita
Click to expand...
Click to collapse
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.
There is a perfectly easy way to unlock your bootloader on the 3.18 software, it isn't a stupid phone, nor is the exploit hard to achieve, hundreds if not thousands of people have done it. It's as simple as entering a few adb/fastboot commands.
You can't root on 5.18 because the update patched the weakness that was exploited in the 3.18 software/firmware. It takes time for devs to crack these things and the update has only just been released. It's not even sure whether the devs will want to spend any time finding a crack for a phone that's relatively old now. This is why you never take an update without first unlocking/rooting, unless you're comfortable with the fact that you won't be able to (it is a well established fact that updates patch exploits).
Sent from my Evita
5.18!to 3.18 ruu
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?
brenntard said:
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?
Click to expand...
Click to collapse
Bootloader details please.
Sent from my Evita
timmaaa said:
Bootloader details please.
Sent from my Evita
Click to expand...
Click to collapse
Tampered
Relocked
Evita put ship s-on rl
Hboot-2.18.0000
Radio-1.35a.32.45.27
Opendsp-v33.1.0.45.1128
Emmc-boot
It's weird, I tried using the all in one toolkit and was able to unlock the boot loader, get twrp recovery working and flash supersu. The only problem I ran into was when I opened supersu it said the binaries need to update. The first time I updated them and it was fine then the phone shut off and supersu would always need updated when opened...I downloaded titanium backup and was able to get root access before my phone restarted and I had to update supersu again... It is now relocked, obviously, but easy enough to unlock again using the toolkit
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Yes it says me CID is 11111111. Why would supersu be acting so funny and constantly telling me to update the binaries...supersu seems relatively useless at this point. do i need supersu to flash a custom ROM?
Forever95 said:
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.
Click to expand...
Click to collapse
Lack of research. A working root method exists for 3.18, both a "manual" method and two "Toolkits" for those that can't handle the manual method.
Also, you should never never never install an OTA update unless you know what has been patched, changed, etc. Updates frequently will patch existing root exploits, and therefore leaving you in the spot you find yourself in.
Other devices (such as the One) can be rooted with later firmware, simply because that device has more developer interest. It requires the right talented developer(s) putting in the time and effort to find the exploit method. Its still possible on this device with 5.18. All it takes is the right guy and the proper amount of motivation. But as the device is getting older, and devs are moving to other phones, those chances do get more unlikely.
UPDATE!
timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for the help. i know officially have an s-off device that is unlocked and rooted ready to run custom ROMS.
My next question would be how do i flash a kernel and why would i flash a kernel?
cant flash ROM
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?
brenntard said:
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?
Click to expand...
Click to collapse
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.
timmaaa said:
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.
Click to expand...
Click to collapse
That sounds easy enough.. I was able to gain s-off through the face palm method earlier today so now i just need to flash the 2.15 firmware. in the thread it says to "make sure you flash your current ROM's boot.img after" is this necessary if i am using the stock 4.2.2 sense 5 ROM already, does the download include the radio? do i need a different radio?
The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita
timmaaa said:
The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita
Click to expand...
Click to collapse
awesome! im gonna try that tonight.
Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita
timmaaa said:
Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for your help! i succesfully flashed the firmware and amnow running CM10.2.1. If i want to flash a 4.4 ROM do i need a different recovery? im currently using 2.5.0.0
Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) from here.
Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
timmaaa said:
Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) from here.
Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
Click to expand...
Click to collapse
I guess the all in one toolkit hasn't had an update in a while...
thanks again for all the help, really appreciated
i have been working to get a custom rom on my device for roughly a month now and today was the day it finally happened
glad to say i learned a lot thanks to help from people like you in this great forum
My HTC One X was bricked, and I need to restore it to Rogers Stock. However, I searched the entire XDA webstie + 50 pages on Google + 50 pages on other country's android site, I cant find any working download URL. Can someone please upload one RUU or Zip file for me, so I can restore my phone please?
If your phone is bricked an RUU isn't going to save it. Either way, you'll find all Evita RUUs here:
http://androidruu.com/?developer=Evita
Sent from my One XL using Tapatalk
timmaaa said:
If your phone is bricked an RUU isn't going to save it. Either way, you'll find all Evita RUUs here:
http://androidruu.com/?developer=Evita
Sent from my One XL using Tapatalk
Click to expand...
Click to collapse
The phone actually is soft brick, all I need to do is to flash it back to stock rom, so I can do a S-Off
I have this problem because I attempted to flash cyanogenmod without getting S-Off, thus it end up with black screen boot loop.
Any idea to solve it? I cant find any recovery zip that is working
I wouldn't ruu without S-off. Do you have supercid? If you do, you may brick. Best to boot to bootloader then recovery then flash a sense rom then s-off
Sent from my HTC One_M8 using xda app-developers app
voot566 said:
The phone actually is soft brick, all I need to do is to flash it back to stock rom, so I can do a S-Off
I have this problem because I attempted to flash cyanogenmod without getting S-Off, thus it end up with black screen boot loop.
Any idea to solve it? I cant find any recovery zip that is working
Click to expand...
Click to collapse
There's no such thing as a soft brick, a phone is either bricked or it isn't. Do as exad suggested and flash a Sense ROM then get s-off, then update your firmware (which is probably what was your actual problem).
Sent from my One XL using Tapatalk
exad said:
I wouldn't ruu without S-off. Do you have supercid? If you do, you may brick. Best to boot to bootloader then recovery then flash a sense rom then s-off
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
THat is another problem, there is no CID showed on the bootloader screen.
This is all happen after I get bootloader unlocked, and attempted to flash clockworkmod. It end up with boot loop with black screen, cant get into any system
What I can do right now is
1. boot into TWRP
2. Copy anyfile into phone through TWRP
3. flash zip through TWRP, but I cant find any rom that is working for my phone
4. fastboot usb with any command
voot566 said:
THat is another problem, there is no CID showed on the bootloader screen.
This is all happen after I get bootloader unlocked, and attempted to flash clockworkmod. It end up with boot loop with black screen, cant get into any system
What I can do right now is
1. boot into TWRP
2. Copy anyfile into phone through TWRP
3. flash zip through TWRP, but I cant find any rom that is working for my phone
4. fastboot usb with any command
Click to expand...
Click to collapse
The CID doesn't show on your bootloader screen unless you have s-off. What are your bootloader details? What recovery do you have installed? You can check your CID with this fastboot command:
Code:
fastboot oem readcid
Sent from my One XL using Tapatalk
timmaaa said:
There's no such thing as a soft brick, a phone is either bricked or it isn't. Do as exad suggested and flash a Sense ROM then get s-off, then update your firmware (which is probably what was your actual problem).
Sent from my One XL using Tapatalk
Click to expand...
Click to collapse
Yeah, I kind of know that I need to flash a sense rom, but I cant find any sense rom that is working on my phone.
Here is the info:
Model: PJ83100
Bootloader unlocked
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23A. 32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 26 2012, 18:37:14:-1
This is exactly what showed on my screen, no CID
Which rom I should use?
voot566 said:
Yeah, I kind of know that I need to flash a sense rom, but I cant find any sense rom that is working on my phone.
Here is the info:
Model: PJ83100
Bootloader unlocked
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23A. 32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 26 2012, 18:37:14:-1
This is exactly what showed on my screen, no CID
Which rom I should use?
Click to expand...
Click to collapse
The fact is you don't actually need s-off to flash cyanogenmod. You only need s-off to run the 3.18 RUU which updates your firmware, which you don't need to do because your firmware is fine. This brings me back to the other question you didn't answer: what recovery do you have installed?
Sent from my One XL using Tapatalk
timmaaa said:
The CID doesn't show on your bootloader screen unless you have s-off. What are your bootloader details? What recovery do you have installed? You can check your CID with this fastboot command:
Code:
fastboot oem readcid
Sent from my One XL using Tapatalk
Click to expand...
Click to collapse
I used the command
CID: BS_US001
My recovery is TWRP v2.6.3.0
THis is the only version that is working for me, I tried clockworkmod, and higher or lower version for TWRP, but I cant mount USB storage through any of those except 2.6.3.0
Recovery version please.
Sent from my One XL using Tapatalk
You just need to extract the boot.img from the rom you are flashing, put it in your adb/fastboot folder and then after flashing the rom.
fastboot flash boot boot.img
Then you will be able to boot it.
I suggest getting S-OFF using rumrunner so you don't need to take this step anymore. will also protect you in case you need to RUU.
exad said:
You just need to extract the boot.img from the rom you are flashing, put it in your adb/fastboot folder and then after flashing the rom.
fastboot flash boot boot.img
Then you will be able to boot it.
I suggest getting S-OFF using rumrunner so you don't need to take this step anymore. will also protect you in case you need to RUU.
Click to expand...
Click to collapse
But my question is, which rom I should flash????
I tried both serveral differnet rom, but they are all not working.
This is my phone: http://www.newegg.com/Product/Product.aspx?Item=N82E16875502142
voot566 said:
But my question is, which rom I should flash????
I tried both serveral differnet rom, but they are all not working.
This is my phone: http://www.newegg.com/Product/Product.aspx?Item=N82E16875502142
Click to expand...
Click to collapse
I know what phone you have. an evita. Says so in your bootloader
You need unofficial 2.6.3 from original android dev. if you want to flash cm as you need SE Linux support.
Any sense rom should work on official twrp 2.6.3
make sure you wipe system cache and dalvik cache prior to flashing.
This is what you should do to rule out every issue.
Download unofficial 2.6.3
Check the Md5 of your download
put it in your fastboot folder
fastboot erase cache
fastboot flash recovery unnoficialrecoveryfilename.img
select recovery in bootloader
wipe cache, dalvik, system in wipe, advanced wipe
then do a factory reset for safe measure
flash your rom
wipe cache and dalvik
reboot to bootloader
extract the boot.img from the rom put it in your fastboot folder
fastboot flash boot boot.img
fastboot reboot
U mean this?
http://forum.xda-developers.com/showthread.php?t=2558503
voot566 said:
U mean this?
http://forum.xda-developers.com/showthread.php?t=2558503
Click to expand...
Click to collapse
That's the one.
Qucik question, since i am just helping my friend to do it, he want to get cyanogenmod, any idea how to do it after ur method?
He already told you exactly how to do it. What are you asking?
Sent from my One XL using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1655011
This rom okay?
I thought you wanted to put cyanogenmod onto the phone...
Sent from my One XL using Tapatalk