Related
Hey, first time I'm posting here. I recently was able to root, unlock bootloader, and flash a custom ROM for my AT&T HTC One X. I started with CM 10.1 and got that to work fine. I'm using the latest version of clockwork recovery and have made several backups (I'm a bit paranoid about ruining my phone).
After getting CM 10.1 to work, I wanted to try out AOKP. I've downloaded both the Milestone as well as a nightly build. I've followed the instructions carefully to try to get this ROM to work and even tried some variants. I've wiped cache, dvalrik cache, factory reset and then flashed the boot.img. And then I've gone into recovery and loaded the milestone onto my phone after rewiping the cache, dvalrik cache and factory reset. I then loaded the google apps. I've tried flashing flashing the ROM first, the boot.img first, and any number of different cache wipes and factory resets. And every time I seem to have the same problem: my touchscreen refuses to work. I get to the setup page for the ROM and all the other buttons work, but not the touchscreen. I've looked everywhere I could think of for a solution to this problem but couldn't find one. Can anybody help me out?
I also should mention that each time I've been successful in restoring my phone to CM 10.1 using a backup, and no touchscreen problem persists.
What hboot are you on? And which cm10.1 did you flash? The latest nightly?
Sent from my Evita
Additional Info:
HBoot-2.14
Radio-0.24p.32.09.06
S-On
OpenDSP-v34.1.0.45.1219
Thanks.
timmaaa said:
What hboot are you on? And which cm10.1 did you flash? The latest nightly?
Sent from my Evita
Click to expand...
Click to collapse
Flashed cm10.1-20130623-unofficial. And hboot is above.
Ok I believe the latest CM builds have been made to work with the newer touchscreen firmware, so I think that's why cm is working ok for you. You have the newer touchscreen firmware, by looking at your hboot version.
To use all other aosp ROMs you'd need to downgrade your touchscreen firmware, which means you would need to s-off first.
Sent from my Evita
timmaaa said:
Ok I believe the latest CM builds have been made to work with the newer touchscreen firmware, so I think that's why cm is working ok for you. You have the newer touchscreen firmware, by looking at your hboot version.
To use all other aosp ROMs you'd need to downgrade your touchscreen firmware, which means you would need to s-off first.
Sent from my Evita
Click to expand...
Click to collapse
Yeah I literally just found this thread: http://forum.xda-developers.com/showthread.php?t=2159863.
So that's the process I need to go through, which requires S-Off... Is there any way I can tell if I have superCID already for the facepalm s-off process?
Thanks for your help!
steffyd said:
Yeah I literally just found this thread: http://forum.xda-developers.com/showthread.php?t=2159863.
So that's the process I need to go through, which requires S-Off... Is there any way I can tell if I have superCID already for the facepalm s-off process?
Thanks for your help!
Click to expand...
Click to collapse
boot to bootloader/fastboot
do:
fastboot oem readcid
if it says 11111111 or 22222222 then supercid=yes
if its anything else then no
exad said:
boot to bootloader/fastboot
do:
fastboot oem readcid
if it says 11111111 or 22222222 then supercid=yes
if its anything else then no
Click to expand...
Click to collapse
Thanks guys! Got it all worked out now, I appreciate the help!
Just make sure you only flash ROMs from this section, if you flash an International One X ROM you'll brick your phone.
Welcome to XDA
Sent from my Evita
got any guide on how do i s-off without being able to touch the screen? android debugging was not enabled by default. however, i can get into cwm n use all the features there. im having a evita with cm10.1, when i install cm, i wipe all, so the rom loads but i cant touch anything, adb was not recognise bcos i cant turn on usb debugging.
Try flashing a Sense ROM.
Sent from my Evita
The reason im getting my hands on custom rom is bcos my stock XL(Asian version) will neve sync google contacts properly, i tried to flash ICS/JB stock RUU, but its same. then, i started to tamper my fon with unlocking bootloader via htcdev, flash cwm(twrp mess on my sdcard storage). i had experience on older htc devices but its my 1st time on the htc one series. right now, im on evita s-on, unlocked bootloader, hboot 2.14, cwm recovery(twrp mess on my sdcard storage), not-super CID. I 'm left with a non-touchable cm10.1, i can flash any rom that supports s-on. tried to relock bootloader but i cant flash stock ICS ruu.will try stock JB RUU now. my target now is to s-off n superCID.
i have read alot of posts, but most sense rom require s-off. do u know which one that i can flash with s-on?
None of the Sense ROMs "require" s-off.
Sent from my Evita
thx timmaa. i restored to sense 5 rom n then proceed to s-ooff/dgrade tpanel, all works fine. here are my ways, all credits belong to the OP, i just wanna put up my ways here, so forummers who faces same problem will find a simpler solution, i hope it has not been posted cos i cant search for the solution yest :
the XL nick is evita, X is endeavour
unlock bootloader at htcdev.com
fastboot flash recovery TWRP5.img, if it messed with storage, use CWM
fLASH CUSTOM ROM N REMEMBER TO fastboot flash boot boot.img (use Evita Sense 5 R3 if touch panel not working), custom rom already rooted
-----------------------------------------------------------------------------------------------------------------
SuperCID (must have root, usb debugging enabled)
adb shell
# su
# echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
Reboot to bootloader n
fastboot getvar cid
the cid shud be 11111111
--------------------------------------------------------------------------------------------------------------------
S-off (must have unlocked bootloader, rooted, superCID) facepalm method
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PJ8312000-OneX.zip
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
fastboot oem boot
You may see some errors, just wait for the device to boot into Android (only now, you should be booted into Android with no eMMC write protection of any kind active).
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
adb reboot bootloader
Posted my topic to incorrect thread and don't know how to move it, so re-post my question here.
Default [Q] HTC One X doesn't work, error 7 on setup any(!) ROM
Device: HTC One X AT&T USA, Android 4.0.4
HBoot 1.14 (unlocked), S-ON, cid: 11111111 (was CWS__001), rooted (CWM-SuperSU-v0.96)
Hi,
I have sim-unlocked AT&T HTC One X that I bought in USA last year and used it in 'as is' condition. A week ago it got to cyclical reboot. I made factory reset, but of course I lost all my data. In this case I decided to upgrade HBoot and setup latest CyanogenMod (yeap, I thought I have nothing to lose ).
I re-wrote cid to supercid, unlocked flashboot, rooted the phone... but made a mistake and flashed CyanogenMod boot.img before upgraded Hboot *facepalm*.
And now it's unable to load android (it just shows HTC logo with red warning text).
Of course, I tried to restore original Boot from backup, but this didn't help.
I'm able to open Bootloader and custom recovery menu (recovery-clockwork-6.0.3.1-evita.img), but unable to install any ROM (tried to use ROMs that are based on ICS, because my Hboot 1.14) - it always returns me error 7, even if all requirements are met. Tried to remove asserts from updater-script , but in this case it just shows 'Opening update package... Installing update... Installation aborted.'
I tried almost all that I found in web, used different backups and ROMs, but nothing helped.
I also tried to flash stock RUU (european, since I didn't find USA version - btw does it matter?) , but it getting Error 132 - Signature error.
Please could somebody help me to return my phone to a working state? Any advices are truly appreciated!
P.S. Unfortunately on one of the steps I lost my original backup (sdcard was formatted).
Thanks.
Click to expand...
Click to collapse
UPDATE:
I thought that since I have supercid I can use any RUU, but seems like I should use RUU exactly for CWS__001 or based on this thread I should make my phone S-Off and install any RUU. I cannot find any RUU for r CWS__001 in web, so if S-Off really helps, could you please advise correct RUU for my phone?
Thank you in advance!
Have you tried flashing a different recovery? It might help. Download TWRP 2.6 from here. Put it in your fastboot folder, connect your phone, open command prompt from within fastboot folder, issue following commands:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery and try to install your ROM again. Post results here.
Sent from my Evita
---------- Post added at 10:35 PM ---------- Previous post was at 10:34 PM ----------
PS. do not use an RUU while you have SuperCID and s-on, it will brick your phone. Try my above instructions first.
Sent from my Evita
timmaaa said:
Have you tried flashing a different recovery? It might help. Download TWRP 2.6 from here. Put it in your fastboot folder, connect your phone, open command prompt from within fastboot folder, issue following commands:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery and try to install your ROM again. Post results here.
Sent from my Evita
---------- Post added at 10:35 PM ---------- Previous post was at 10:34 PM ----------
PS. do not use an RUU while you have SuperCID and s-on, it will brick your phone. Try my above instructions first.
Sent from my Evita
Click to expand...
Click to collapse
This recovery seems pretty good, thank you!
And it looks like I understand why all ROMs gets me Error 7: all of them are for Endeavor, but my phone is Evita, isn't it?
I made all that you wrote:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
fastboot erase cache
fastboot reboot-bootloader
Also I found this ROM (MIUIandroid 3.2.22 for the EVITA version of the HTC One X/L) and ran installation from recovery. And there are no Error 7! :victory: (of course I also flashed boot - fastboot flash boot boot.img)
The instruction for this ROM also says "Install gapps; Wipe Cache and Dalvik Cache". I installed gapps (MIUI.us_evita_v4_3.1.25_Eng_mirG.zip)
BUT unable to wipe Cache and Dalvik Cache: currently my phone says "Unable to mount '/cache' and '/data'".
How can I fix this?
Oh! And thank you for warn me about RUU installation!
Sigord said:
This recovery seems pretty good, thank you!
And it looks like I understand why all ROMs gets me Error 7: all of them are for Endeavor, but my phone is Evita, isn't it?
I made all that you wrote:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
fastboot erase cache
fastboot reboot-bootloader
Also I found this ROM (MIUIandroid 3.2.22 for the EVITA version of the HTC One X/L) and ran installation from recovery. And there are no Error 7! :victory: (of course I also flashed boot - fastboot flash boot boot.img)
The instruction for this ROM also says "Install gapps; Wipe Cache and Dalvik Cache". I installed gapps (MIUI.us_evita_v4_3.1.25_Eng_mirG.zip)
BUT unable to wipe Cache and Dalvik Cache: currently my phone says "Unable to mount '/cache' and '/data'".
How can I fix this?
Oh! And thank you for warn me about RUU installation!
Click to expand...
Click to collapse
Holy crap you are so lucky you didn't brick your phone by flashing those Endeavoru ROMs. Yes, you have an Evita, it'll say that at the top of your bootloader. Don't ever flash Endeavoru ROMs again, you could brick. Only ever download your ROMs from our forum, go here for Sense ROMs or here for aosp ROMs. Don't ever download from any other forum or any other site.
I'm honestly not sure why it can't mount cache/dalvik cache though. Did you use the advanced wipe feature?
Sent from my Evita
timmaaa said:
Holy crap you are so lucky you didn't brick your phone by flashing those Endeavoru ROMs. Yes, you have an Evita, it'll say that at the top of your bootloader. Don't ever flash Endeavoru ROMs again, you could brick. Only ever download your ROMs from our forum, go here for Sense ROMs or here for aosp ROMs. Don't ever download from any other forum or any other site.
I'm honestly not sure why it can't mount cache/dalvik cache though. Did you use the advanced wipe feature?
Sent from my Evita
Click to expand...
Click to collapse
Yes, I used 'Wipe cache/Dalvik' button after installation and additionally 'Advanced wipe > Dalvik cache, Cache'.
After gaps installation it shows only "E:Unable to mount '/data'"
So the gapps installation failed?
Sent from my Evita
timmaaa said:
So the gapps installation failed?
Sent from my Evita
Click to expand...
Click to collapse
Installation says "Successful" but it shows "E:Unable to mount '/data'" in logs.
Also I'm getting the same issue when trying to wipe dalvik cache and cache.
It sounds like the recovery is needing a valid /data partition before it will let you flash.
Sent from my HTC One X using xda premium
Venomtester said:
It sounds like the recovery is needing a valid /data partition before it will let you flash.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Now on loading the phone displays colored X like in Nexus but it doesn't load (of course).
How can I set a valid /data partition?
Sigord said:
Yes, I used 'Wipe cache/Dalvik' button after installation and additionally 'Advanced wipe > Dalvik cache, Cache'.
After gaps installation it shows only "E:Unable to mount '/data'"
Click to expand...
Click to collapse
Try to manually mount it by clicking the second button from the bottom left and checking everything then reflash
You may not be able to check it
-Sugardaddy
Arrow44 said:
Try to manually mount it by clicking the second button from the bottom left and checking everything then reflash
You may not be able to check it
-Sugardaddy
Click to expand...
Click to collapse
Unfortunately I'm able to check Cache, sdcard and System in Mount menu, but not Data.
You could try formatting your sd card. Backup any important data first obviously.
Sent from my Evita
timmaaa said:
You could try formatting your sd card. Backup any important data first obviously.
Sent from my Evita
Click to expand...
Click to collapse
I formatted the sd card, but all the same unable to mount \data.
I also tried to re-install my ROM zip and gapps zip but this didn't help.
Did a factory reset through TWRP, it mounted \data and now my phone is alive!
Thank you guys for all your help!!!
Ok good. Just a note: before flashing a ROM, always wipe cache/dalvik cache/factory reset/system.
Sent from my Evita
timmaaa said:
Ok good. Just a note: before flashing a ROM, always wipe cache/dalvik cache/factory reset/system.
Sent from my Evita
Click to expand...
Click to collapse
Thank you!
And just to be sure, what are my future steps if I want to flash any ROM on Android 4.2 or higher (For example, CM 10.1)?
Could you please take a look on the steps below and tell me if I missed something or understood wrong?
1. Do S-OFF based on [S-Off] Facepalm S-Off for HTC One XL
2. Load in fastboot mode and re-lock fastboot (fastboot oem lock)
3. Go to recovery and do full wipe
4. Update to 3.18 RUU by running its .exe.
If I understand correctly, this should upgrade my HBoot and Radio and get me official HTC ROM with JB 4.1.1 (is this safely with SuperCID and S-OFF?)
6. Unlock bootloader (fastboot flash unlocktoken Unlock_code.bin)
5. Downgrade touchscreen firmware.
6. Download last stable version of CM and the appropriate gapps and push it to sdcard
7. Go to recovery and create a backup
8. Do a full wipe
9. Install CM zip from sdcard
10. Install gapps
11. Flash boot (fastboot flash boot boot.img)
Thank you in advance!
PS: Probably you can advise me any other stable ROM?
Sigord said:
Thank you!
And just to be sure, what are my future steps if I want to flash any ROM on Android 4.2 or higher (For example, CM 10.1)?
Could you please take a look on the steps below and tell me if I missed something or understood wrong?
1. Do S-OFF based on [S-Off] Facepalm S-Off for HTC One XL
2. Load in fastboot mode and re-lock fastboot (fastboot oem lock)
3. Go to recovery and do full wipe
4. Update to 3.18 RUU by running its .exe.
If I understand correctly, this should upgrade my HBoot and Radio and get me official HTC ROM with JB 4.1.1 (is this safely with SuperCID and S-OFF?)
6. Unlock bootloader (fastboot flash unlocktoken Unlock_code.bin)
5. Downgrade touchscreen firmware.
6. Download last stable version of CM and the appropriate gapps and push it to sdcard
7. Go to recovery and create a backup
8. Do a full wipe
9. Install CM zip from sdcard
10. Install gapps
11. Flash boot (fastboot flash boot boot.img)
Thank you in advance!
PS: Probably you can advise me any other stable ROM?
Click to expand...
Click to collapse
You've done very well but if you get s-off first you can actually forget some of those steps. Follow the below steps.
1. Do S-OFF based on [S-Off] Facepalm S-Off for HTC One XL
2. Update to 3.18 RUU by running its exe file. This will update your phone to 2.14 hboot, and stock at&t ROM, and stock recovery. Safe to run with SuperCID as long as you s-off first.
3. Flash TWRP 2.6 again as detailed earlier.
4. Go into recovery and create a backup.
8. Do a full wipe
9. Install ROM zip from sdcard.
10. Install appropriate gapps.
Because you'll have s-off first, you don't need to relock your bootloader before the RUU. You will also not have to flash the boot.img from fastboot anymore. Part of the beauty of having s-off.
I can't really advise any ROMs. It's against the rules to ask which ROM is best/favorite/most stable, therefore I can't really answer that question. I'd just suggest having a look at a few ROMs, checking out any bugs that are noted in the first few posts, and reading some user connects to get an idea of what's working and what's not.
Sent from my Evita
timmaaa, thank you so much!
Currently I've flashed CM 10.0 (last stable), but when I'll be ready to S-OFF I'll follow your steps.
Thank you once again for your help!
No problems at all, you're welcome.
PS. If someone helps you on here, push the thanks button.
Sent from my Evita
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.
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
i hboot 2.14 on my phone and then flashed cyanogenmod 11 latest update as of 23/6/2014 and then when i rebooted my phone it came on to the htc quietly brilliant screen then shut off and it keeps doing that. what can i do? i am writing on laptop because my phone wont turn on.
More information required, start with your bootloader details and recovery version. Also, you should probably read the Evita FAQ thread in my signature first because it'll most likely solve your problem.
Sent from my Evita
timmaaa said:
More information required, start with your bootloader details and recovery version. Also, you should probably read the Evita FAQ thread in my signature first because it'll most likely solve your problem.
Sent from my Evita
Click to expand...
Click to collapse
here's what i did first. i plugged my phone in my laptop via usb then went and installed the drivers. after that i followed the instructions below to get hboot 2.14
OPTIONAL: Installing the Firmware (Warning: You MUST be S-OFF and Super CID to flash this! Flash at own risk!)
• Reboot to bootloader (adb reboot bootloader if "USB Debugging" is enabled in Android)
• Run: fastboot oem rebootRUU
• Run: fastboot flash zip <PathToFirmware.zip>
• If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command AGAIN
• If it ends with "INFO..... OK", reboot to the bootloader: fastboot reboot-bootloader
• Verify everything was successful by running: fastboot getvar all
It was successful (said ok) so i rebooted to bootloader fastboot reboot-bootloader then i rebooted my phone and it came as fas as the htc quietly brilliant screen then went blank and the usb thingy says that the drivers failed to install. i dont know what i did wrong. i read your FAQ but i didnt see what i was looking for (atleast i think i didnt see)
bootloader information
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT 2.14.0000
RADIO-0.24a.32.45.03
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 26 2012, 18:37:14:-1
cuteyr said:
here's what i did first. i plugged my phone in my laptop via usb then went and installed the drivers. after that i followed the instructions below to get hboot 2.14
OPTIONAL: Installing the Firmware (Warning: You MUST be S-OFF and Super CID to flash this! Flash at own risk!)
•Reboot to bootloader (adb reboot bootloader if "USB Debugging" is enabled in Android)
•Run: fastboot oem rebootRUU
•Run: fastboot flash zip <PathToFirmware.zip>
•If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command AGAIN
•If it ends with "INFO..... OK", reboot to the bootloader: fastboot reboot-bootloader
•Verify everything was successful by running: fastboot getvar all
It was successful (said ok) so i rebooted to bootloader fastboot reboot-bootloader then i rebooted my phone and it came as fas as the htc quietly brilliant screen then went blank and the usb thingy says that the drivers failed to install. i dont know what i did wrong. i read your FAQ but i didnt see what i was looking for (atleast i think i didnt see)
bootloader information
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT 2.14.0000
RADIO-0.24a.32.45.03
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 26 2012, 18:37:14:-1
Click to expand...
Click to collapse
Do you mean you followed those instructions to update to the 2.15 firmware? You said 2.14 but i think you might be confused about that because no such instructions or firmware package exists for 2.14 firmware. Anyway, it didn't work because your firmware is not what it should be after following those directions. Go to my How-To Guide For Beginners thread and follow the instructions there if you still want to update your firmware.
Your original post said you got stuck after flashing CM, now you're saying you got stuck after attempting to flash firmware. Which is it? Also, you didn't answer which recovery version you have installed.
Sent from my Evita
timmaaa said:
Do you mean you followed those instructions to update to the 2.15 firmware? You said 2.14 but i think you might be confused about that because no such instructions or firmware package exists for 2.14 firmware. Anyway, it didn't work because your firmware is not what it should be after following those directions. Go to my How-To Guide For Beginners thread and follow the instructions there if you still want to update your firmware.
Your original post said you got stuck after flashing CM, now you're saying you got stuck after attempting to flash firmware. Which is it? Also, you didn't answer which recovery version you have installed.
Sent from my Evita
Click to expand...
Click to collapse
I meant after attempting to flash the firmware. I have TWRP latest version installed. Will try loading it to bootloader again and follow the instructions for 2.15. thanks so far man
timmaaa said:
Do you mean you followed those instructions to update to the 2.15 firmware? You said 2.14 but i think you might be confused about that because no such instructions or firmware package exists for 2.14 firmware. Anyway, it didn't work because your firmware is not what it should be after following those directions. Go to my How-To Guide For Beginners thread and follow the instructions there if you still want to update your firmware.
Your original post said you got stuck after flashing CM, now you're saying you got stuck after attempting to flash firmware. Which is it? Also, you didn't answer which recovery version you have installed.
Sent from my Evita
Click to expand...
Click to collapse
ok so i followed your instructions and got what u said i should get for the radio and when i did fastboot reboot it booted up to the htc quietly brilliant screen and then went blank
Please post your bootloader details and your exact recovery version number. Have you reflashed the ROM? Are you sure the install was successful? Did you check the md5?
Sent from my Evita
timmaaa said:
Please post your bootloader details and your exact recovery version number. Have you reflashed the ROM? Are you sure the install was successful? Did you check the md5?
Sent from my Evita
Click to expand...
Click to collapse
My friend thank you very much for your help it was definitely worth it. I got my phone working again by going into recovery and mounting sd card and putting the cyanogenmod zip file there then flashing it in recovery . thanks thanks thanks!
Did you successfully flash the correct firmware thou? U never stated if ya did or not.
Sent from my Inspire 4G using Tapatalk
marknoll said:
Did you successfully flash the correct firmware thou? U never stated if ya did or not.
Sent from my Inspire 4G using Taz speedspotted atalk
Click to expand...
Click to collapse
Yes I did flash 2.15. Now I have a problem where once my phone is on mobile data I keep getting 'u unfortunately the process Com.android phone has stopped. And my phone service goes off. The only time I don't see this message is when the phone is in airplane mode and if it's in airplane mode I can't receive texts and calla.
Idk if cm 11 is compatible with firmware 2.15. Maybe that's why.....?
That firmware is compatible with all current aosp ROMs. @cuteyr, did you perform a full wipe before flashing?
Sent from my Evita
timmaaa said:
That firmware is compatible with all current aosp ROMs. @cuteyr, did you perform a full wipe before flashing?
Sent from my Evita
Click to expand...
Click to collapse
@timmaaa i actually did a factory reset before flashing it.
That doesn't answer the question though, a full wipe includes cache, dalvik cache, data (factory reset), and system.
Sent from my Evita
timmaaa said:
That doesn't answer the question though, a full wipe includes cache, dalvik cache, data (factory reset), and system.
Sent from my Evita
Click to expand...
Click to collapse
In that case no i didnt. Guess i have to redo @timmaaa?
You should always perform a full wipe when flashing a ROM, so yeah, I'd flash again and see if it helps.
Sent from my Evita
timmaaa said:
You should always perform a full wipe when flashing a ROM, so yeah, I'd flash again and see if it helps.
Sent from my Evita
Click to expand...
Click to collapse
Ok will do
timmaaa said:
That doesn't answer the question though, a full wipe includes cache, dalvik cache, data (factory reset), and system.
Sent from my Evita
Click to expand...
Click to collapse
TWRP's factory reset wipes all of those automatically, so it's best to use that one when flashing ROMs. The only times I get force closes are occasionally when restoring certain phone/messaging settings from different ROMs, and there is always the possibility of a bad download. If you get force closes after a clean flash then I'd suggest downloading a different ROM or version/nightly.
The factory reset option in TWRP doesn't wipe the system partition.
Sent from my Evita
timmaaa said:
The factory reset option in TWRP doesn't wipe the system partition.
Sent from my Evita
Click to expand...
Click to collapse
@timmaaa so I wiped my phone(cache, dalvik, factory reset) then flashed the firmware again then installed cm11 rom and after that was successful I turned my phone back on and I realized the message wasn't coming back on...that is until about two and a half hours later it ppopped up ' unfortunately the process Com.android.phone has stopped and it hasn't stopped once my phone is not on airplane mode. What to do? I'm in desperate need of help as my phone is my major way of doing all sorts of things