I have a one xl cid rogers001 hboot 2.14, baseband 0.23a.3 2.09.29.... jb 4.1 with sense 4+
I tried unlock bootloader by htcdev => ok
install recovery => ok. and when i installed this rom: http://forum.xda-developers.com/showthread.php?t=1868236, it was stuck in bootloader. i fogot root my phone before.
so i relock my device, and tried to flash this stock rom using adb : OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip (was found in this thread: http://forum.xda-developers.com/showthread.php?t=2119610)
On cmd via fastboot i type fastboot erase cache =>ok
fastboot oem rebootRUU => ok
fastboot flash zip "filename.zip" It says " (remote: 12 signature verify fail") in the end cmd
What should i do now?
Thanks for reading and help me pls!!!!
Ok, first mistake is that you thought you needed to be rooted to flash the Viper ROM, you don't. All you need is an unlocked bootloader and custom recovery, which you had. You were probably stuck in the bootloader because you forgot to flash the boot.img from the ROM zip with fastboot, you need to do this because you're s-on.
The next mistake you made was attempting to flash an OTA. I don't know what made you think that you could do that but it definitely wasn't found in this forum (or anywhere for that matter). An OTA is only a partial OS, it relies on the correct stock OS to already be installed on the device to build on top of to update the existing OS. It failed for obvious reasons.
Unlock your bootloader again, flash a custom recovery again, and flash the ROM again. Make sure you flash the boot.img this time and it should boot right up. I'd strongly recommend you read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature. Diving into modifying your device without the proper level of knowledge is a really bad idea.
Sent from my Evita
timmaaa said:
Ok, first mistake is that you thought you needed to be rooted to flash the Viper ROM, you don't. All you need is an unlocked bootloader and custom recovery, which you had. You were probably stuck in the bootloader because you forgot to flash the boot.img from the ROM zip with fastboot, you need to do this because you're s-on.
The next mistake you made was attempting to flash an OTA. I don't know what made you think that you could do that but it definitely wasn't found in this forum (or anywhere for that matter). An OTA is only a partial OS, it relies on the correct stock OS to already be installed on the device to build on top of to update the existing OS. It failed for obvious reasons.
Unlock your bootloader again, flash a custom recovery again, and flash the ROM again. Make sure you flash the boot.img this time and it should boot right up. I'd strongly recommend you read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature. Diving into modifying your device without the proper level of knowledge is a really bad idea.
Sent from my Evita
Click to expand...
Click to collapse
fisrt, thanks for helping me. but i've flash boot boot.img file in .zip after i install rom from sdcard. after that, phone stuck in bootloader.
i've unlock bootloader and flash recovery again, and now it says can't mount sdcard. how can i copy viper rom into internal storage? sideload? flash zip? and after all, my phone still not root, can flash viper rom without root?
sorry for my english. thanks again!
somebody help me pls
veveve said:
somebody help me pls
Click to expand...
Click to collapse
Please be patient, we all have lives outside XDA.
veveve said:
fisrt, thanks for helping me. but i've flash boot boot.img file in .zip after i install rom from sdcard. after that, phone stuck in bootloader.
i've unlock bootloader and flash recovery again, and now it says can't mount sdcard. how can i copy viper rom into internal storage? sideload? flash zip? and after all, my phone still not root, can flash viper rom without root?
sorry for my english. thanks again!
Click to expand...
Click to collapse
Did you perform a factory reset from the bootloader at some point? If so you've corrupted your sd card, you should never perform a factory reset from the bootloader. If this is the case you'll need to use TWRP to wipe your sd card, then you should be able to mount it to Windows and use Windows Explorer to format. Once this is done you can for a ROM across again.
Exactly which build of Viper did you try to flash? What's the exact filename? Did you check the md5 before flashing?
Sent from my Evita
timmaaa said:
Please be patient, we all have lives outside XDA.
Did you perform a factory reset from the bootloader at some point? If so you've corrupted your sd card, you should never perform a factory reset from the bootloader. If this is the case you'll need to use TWRP to wipe your sd card, then you should be able to mount it to Windows and use Windows Explorer to format. Once this is done you can for a ROM across again.
Exactly which build of Viper did you try to flash? What's the exact filename? Did you check the md5 before flashing?
Sent from my Evita
Click to expand...
Click to collapse
yes, i did it more than once, now it's fixed, but when i mount it to Windows using TWRP, nothing happen, so i can't format it. and the same things when i tried to sideload. But in fastboot mode, it usual.
and i flashed the newest rom in this thread: http://forum.xda-developers.com/showthread.php?t=1868236 ViperXL 4.2 and i didn't check the MD5
back to my previous question, can i fash a custom rom without root?
I asked for the exact filename of the ROM for a reason, I need that please. Also, exactly which recovery are you using?
Sent from my Evita
Yes, you can flash a custom Rom without root. He already answered that. I strongly recommend reading up on your device before flashing anything else. I'd suggest starting with getting your phone s-off.
nem1yan said:
Yes, you can flash a custom Rom without root. He already answered that. I strongly recommend reading up on your device before flashing anything else. I'd suggest starting with getting your phone s-off.
Click to expand...
Click to collapse
I disagree. I think it's a better idea for him to get his head around the simple operations like flashing ROMs before attempting s-off.
Sent from my Evita
timmaaa said:
I asked for the exact filename of the ROM for a reason, I need that please. Also, exactly which recovery are you using?
Sent from my Evita
Click to expand...
Click to collapse
Full ROM:
Jelly Bean - Android 4.2.2 / Sense 5
ViperXL 4.2.0
Main Link: http://www.androidfilehost.com/?fid=23134718111254927
Mirror 1: http://goo.im/devs/Turge/ViperXL/ViperXL_4.2.0.zip
Mirror 2: http://d-h.st/z4Q
Click to expand...
Click to collapse
and at the first time, i used ClockworkMod Touch 6.0.2.8 Official from here: http://forum.xda-developers.com/showthread.php?t=2148909
after, i used this: twrp-2.7.0.8-evita.img
Thanks!
I know which ROM you're flashing, I need the filename, as it appears in your file browser or Windows Explorer or something. Like this:
Code:
Romname.zip
Sent from my Evita
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
And you should always check the md5 of anything you're about to flash. You should do that now to make sure the file isn't corrupt.
Sent from my Evita
timmaaa said:
I know which ROM you're flashing, I need the filename, as it appears in your file browser or Windows Explorer or something. Like this:
Code:
Romname.zip
Sent from my Evita
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
And you should always check the md5 of anything you're about to flash. You should do that now to make sure the file isn't corrupt.
Sent from my Evita
Click to expand...
Click to collapse
it is ViperXL_4.2.0.zip
i'll do it next time!
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
veveve said:
it is ViperXL_4.2.0.zip
i'll do it next time!
Click to expand...
Click to collapse
Did you check the md5? Does it match?
Sent from my Evita
---------- Post added at 08:49 AM ---------- Previous post was at 08:49 AM ----------
bzhmobile said:
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
Click to expand...
Click to collapse
You might be onto something.
Sent from my Evita
timmaaa said:
Did you check the md5? Does it match?
Sent from my Evita
---------- Post added at 08:49 AM ---------- Previous post was at 08:49 AM ----------
You might be onto something.
Sent from my Evita
Click to expand...
Click to collapse
I mean, i didn't do it and i will do it next time
bzhmobile said:
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
Click to expand...
Click to collapse
thanks, i will try.
Make sure you check the md5 before flashing. A corrupt zip could brick your phone.
Sent from my Evita
timmaaa said:
Make sure you check the md5 before flashing. A corrupt zip could brick your phone.
Sent from my Evita
Click to expand...
Click to collapse
but i still have trouble with mounting internal storage using TWRP on windows, should i try the older TWRP?
What version do you have installed?
Sent from my Evita
timmaaa said:
What version do you have installed?
Sent from my Evita
Click to expand...
Click to collapse
here
and at the first time, i used ClockworkMod Touch 6.0.2.8 Official from here: http://forum.xda-developers.com/show....php?t=2148909
after, i used this: twrp-2.7.0.8-evita.img
Click to expand...
Click to collapse
Related
friend gave me his one X because his dialer and sms app force close when its used and says htc xxx is not responding. I have tried to reflash a new rom/ flash boot.img and the new rom installs and the same thing occurs. I know if i flash a default rom i will have to relock the BL but i will lose the ability to flash anything in the future?
some details you wil probably need on my screen
evita pvt ship S-on RL
S-ON( i have a feeling it has to do with this)
h-boot 1.09
radio 0.17.32
i have tried clean rom and viper rom and i get the same issue. suggestions?
all htc onexl are s-on so that isnt a problem. since the phone is already unlocked you have supercid. you could relock the bootloader "fastboot oem lock" and run the 1.85 ruu. then get another unlock token from htcdev or if he gave you his token use that.
since you came from 1.85 firmware you don't need to flash boot.img separate.
before ruu you could also make sure you have the newest twrp 2.3.1.0 evita on it. you could try fixing permissions in twrp. in fastboot you could run this command "fastboot erase cache". if you still have the problem try wiping everything in twrp and reflashing the rom.
DJSYNTHVIRUS said:
friend gave me his one X because his dialer and sms app force close when its used and says htc xxx is not responding.
Click to expand...
Click to collapse
This is a known symptom of Clockworkmod being used on the phone. Change recovery to TWRP, as previously recommended.
DvineLord said:
all htc onexl are s-on so that isnt a problem. since the phone is already unlocked you have supercid. you could relock the bootloader "fastboot oem lock" and run the 1.85 ruu. then get another unlock token from htcdev or if he gave you his token use that.
since you came from 1.85 firmware you don't need to flash boot.img separate.
before ruu you could also make sure you have the newest twrp 2.3.1.0 evita on it. you could try fixing permissions in twrp. in fastboot you could run this command "fastboot erase cache". if you still have the problem try wiping everything in twrp and reflashing the rom.
Click to expand...
Click to collapse
im going to fix permissions and see if i can reflash clean rom if that doesnt work i will try to update twrp then repeat. thanks for the help
hmm i dont see a CWM icon anywhere in my OS? and i am using TWRP
redpoint73 said:
This is a known symptom of Clockworkmod being used on the phone. Change recovery to TWRP, as previously recommended.
Click to expand...
Click to collapse
can you suggest anything i cant figure out why its force closing like that? please and thank you
DJSYNTHVIRUS said:
hmm i dont see a CWM icon anywhere in my OS? and i am using TWRP
Click to expand...
Click to collapse
Boot into bootloader, then select recovery. You'll be able to tell which one you have then.
---------- Post added at 02:53 PM ---------- Previous post was at 02:51 PM ----------
DJSYNTHVIRUS said:
can you suggest anything i cant figure out why its force closing like that? please and thank you
Click to expand...
Click to collapse
CWM is not supported by the HTC One X/XL. TWRP does, which is why you're having some issues. I would recommend flashing TWRP over before you flash anything else. Doing something wrong on CWM could lead you in the path of being a proud owner of a $500 paper weight.
DJSYNTHVIRUS said:
hmm i dont see a CWM icon anywhere in my OS? and i am using TWRP
Click to expand...
Click to collapse
If its always been on TWRP since you owned it, the previous owner may have had CWM on it, then switched to TWRP. I think (not sure) the problem persists even after switching.
Not sure, but I think some folks had to jump thru some hoops to clear this bug up, involving flashing (counter-intuitively) CWM, then a AOSP ROM, then TWRP. Let me see if I can find the thread.
redpoint73 said:
If its always been on TWRP since you owned it, the previous owner may have had CWM on it, then switched to TWRP. I think (not sure) the problem persists even after switching.
Not sure, but I think some folks had to jump thru some hoops to clear this bug up, involving flashing (counter-intuitively) CWM, then a AOSP ROM, then TWRP. Let me see if I can find the thread.
Click to expand...
Click to collapse
thnx to all of you, when booting into recovery i get into TWRP so it is most likely as you say my buddy who gave it to me most likely flashed CWM then TWRP , so your suggesting doing the above in that order?
Here it is. Look at post #7: http://forum.xda-developers.com/showthread.php?t=1846657
But I'd try to confirm if your friend ever had Clockworkmod on the phone. It sounds an awful lot like the bug from the thread above. But I don't want to send you down the wrong path, either.
ill try it thanks
QUOTE=redpoint73;33819696]Here it is. Look at post #7: http://forum.xda-developers.com/showthread.php?t=1846657
But I'd try to confirm if your friend ever had Clockworkmod on the phone. It sounds an awful lot like the bug from the thread above. But I don't want to send you down the wrong path, either.[/QUOTE]
Hi all I was given a HTC One XL telstra version it had no OS not a thing on it and I have managed to flash rom and TWRP but have no idea where to go from here I can use fastboot and also mount the SD card via TWRP now how do i get an OS onto it and what am I looking for exactly?
Ok so you have TWRP recovery? If so just download a ROM on your PC, then enter recovery on your phone, connect your phone to the PC and go to the mount menu then mount usb storage. Copy a ROM to the phone. Enter the wipe menu in recovery, perform a full wipe (cache/dalvik cache/system/factory reset). Enter the install menu in recovery, locate the ROM zip you copied to your phone, swipe to install. If the phone is s-off you can reboot now and it should boot into the OS. If you're s-on you need to flash the boot.img via fastboot, so reboot to the bootloader. Locate the boot.img in the root of the ROM zip on your PC and copy it into your fastboot folder. Issue this command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the OS.
Sent from my Evita
timmaaa said:
Ok so you have TWRP recovery? If so just download a ROM on your PC, then enter recovery on your phone, connect your phone to the PC and go to the mount menu then mount usb storage. Copy a ROM to the phone. Enter the wipe menu in recovery, perform a full wipe (cache/dalvik cache/system/factory reset). Enter the install menu in recovery, locate the ROM zip you copied to your phone, swipe to install. If the phone is s-off you can reboot now and it should boot into the OS. If you're s-on you need to flash the boot.img via fastboot, so reboot to the bootloader. Locate the boot.img in the root of the ROM zip on your PC and copy it into your fastboot folder. Issue this command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the OS.
Sent from my Evita
Click to expand...
Click to collapse
Hi Mate thanks for the quick reply
yep sure do
So I have downloaded Stock Telstra JB 4.2.2 - 5.06.841.1 Rom with Root access
but already had OTA_EVITA_UL_JB_45_S_Telstra_WWE_3.17.841.2_0.23a.32.09.29_10.128.32.34a_release_2997538hizl4svcm80o4g1
as i am s-on can i use the ota file?
Sorry new to the world of HTC
No worries, if you have any problems just ask here.
Sent from my Evita
timmaaa said:
No worries, if you have any problems just ask here.
Sent from my Evita
Click to expand...
Click to collapse
if i use a stock telstra rom i need to relock the bootloader right? but if i do that it doesnt allow me to enter TWRP so i should use some other rom?
No, if you use one of the stock Telstra ROMs found within our development sections you don't need to relock your bootloader at all. You just flash it in recovery and away you go. If you're talking about an RUU it's a different story, with more preparation involved. There's really no need to run an RUU at this point though so just stick with the Telstra ROM (in zip form) and you'll get the full experience.
Sent from my Evita
timmaaa said:
No, if you use one of the stock Telstra ROMs found within our development sections you don't need to relock your bootloader at all. You just flash it in recovery and away you go. If you're talking about an RUU it's a different story, with more preparation involved. There's really no need to run an RUU at this point though so just stick with the Telstra ROM (in zip form) and you'll get the full experience.
Sent from my Evita
Click to expand...
Click to collapse
Seriously Timmaaa I could kiss you right now! you are an absolute legend! got it sorted my main issue was findint which file to use I ended up using Stock_Telstra_3.17.841.9 and flashing the boot as you explained you made my HTC noob experience so much less frustrating Thank you so much!
Lol :sly:
So you got it booted up ok?
Sent from my Evita
timmaaa said:
Lol :sly:
So you got it booted up ok?
Sent from my Evita
Click to expand...
Click to collapse
sure did! thanks mate
No problems, glad to hear it. Welcome to the community by the way, it's good to see another Aussie (I'm guessing) in here.
Sent from my Evita
---------- Post added at 07:33 PM ---------- Previous post was at 07:27 PM ----------
Oh, something I did want to mention. You're not limited to using Telstra ROMs, there are some great ROMs with great features here in our forums. We're very lucky that there are some great devs still providing us with ROMs even though the device is over 18 months old, they're keeping this phone relevant. Just make sure you stay within this device forum and you'll be super duper. Here are the links to our two development sections:
One XL Android Development (mainly Sense)
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development (mainly aosp)
http://forum.xda-developers.com/forumdisplay.php?f=1726
Sent from my Evita
MissCrittie said:
Seriously Timmaaa I could kiss you right now! you are an absolute legend! got it sorted my main issue was findint which file to use I ended up using Stock_Telstra_3.17.841.9 and flashing the boot as you explained you made my HTC noob experience so much less frustrating Thank you so much!
Click to expand...
Click to collapse
Looks like Timmaaa might get lucky! only kidding
Welcome to the XDA forums from another aussie!
Hey.
Need you help or advice..
I made a mistake when flashed my ATT One X with the latest firmware(
And now i can't do anything, I mean root or custom recovery.
I have S-OFF and super CID but I don't how to fix this.. to downgrade or to roll back to oldest firmware.
Even to have root will be perfect.
How can I manage this?
Thanks in advance!
vimev said:
Hey.
Need you help or advice..
I made a mistake when flashed my ATT One X with the latest firmware(
And now i can't do anything, I mean root or custom recovery.
I have S-OFF and super CID but I don't how to fix this.. to downgrade or to roll back to oldest firmware.
Even to have root will be perfect.
How can I manage this?
Thanks in advance!
Click to expand...
Click to collapse
According to your bootloader details you are at a good starting point. Here is what I recommend you do from here:
1. Download a custom recovery like TWRP:
http://forum.xda-developers.com/showthread.php?t=2558503
2. flash this in bootloader mode. If you don't know how here is the help thread you need to read through:
http://forum.xda-developers.com/showthread.php?t=2593382
3. Once you have a custom recovery installed, you can flash SuperSu or other root app (google is your friend.)
4. Stick with the rooted rom you have or flash another of your choosing.
Madcat8686 said:
According to your bootloader details you are at a good starting point. Here is what I recommend you do from here:
1. Download a custom recovery like TWRP:
http://forum.xda-developers.com/showthread.php?t=2558503
2. flash this in bootloader mode. If you don't know how here is the help thread you need to read through:
http://forum.xda-developers.com/showthread.php?t=2593382
3. Once you have a custom recovery installed, you can flash SuperSu or other root app (google is your friend.)
4. Stick with the rooted rom you have or flash another of your choosing.
Click to expand...
Click to collapse
Men.. thats great! Thanks a lot!
I was thinking its impossible to make root...
vimev said:
Men.. thats great! Thanks a lot!
I was thinking its impossible to make root...
Click to expand...
Click to collapse
Not impossible for you because your bootloader is unlocked and you are S-Off. You are always able to root and flash.
Hey, I have the same bootloader setup but i am unable to flash a recovery
Grinno said:
Hey, I have the same bootloader setup but i am unable to flash a recovery
Click to expand...
Click to collapse
What happens when you try to flash a recovery?
What recovery are you trying to flash?
Post your own bootloader (Don't show the IMEI)
Madcat8686 said:
Not impossible for you because your bootloader is unlocked and you are S-Off. You are always able to root and flash.
Click to expand...
Click to collapse
exad said:
What happens when you try to flash a recovery?
What recovery are you trying to flash?
Post your own bootloader (Don't show the IMEI)
Click to expand...
Click to collapse
I use EZT toolkit....It runs the commands then said fail (too many links
Grinno said:
I use EZT toolkit....It runs the commands then said fail (too many links
Click to expand...
Click to collapse
Why are you using a toolkit to flash recovery???
Just download from http://goo.im/devs/OpenRecovery/evita
or download the unofficial TWRP from the original android dev section if you plan on flashing an AOSP or CM based Rom and then fastboot flash recovery recovery_filename.img
Easy peasy. Too many links is an error that should have nothing to do with flashing recovery...
exad said:
Why are you using a toolkit to flash recovery???
Just download from http://goo.im/devs/OpenRecovery/evita
or download the unofficial TWRP from the original android dev section if you plan on flashing an AOSP or CM based Rom and then fastboot flash recovery recovery_filename.img
Easy peasy. Too many links is an error that should have nothing to do with flashing recovery...
Click to expand...
Click to collapse
Donno, Maybe fastboot/drivers or messed up. I keep getting cannot load 'recovery.img' unknown error
Grinno said:
Donno, Maybe fastboot/drivers or messed up. I keep getting cannot load 'recovery.img' unknown error
Click to expand...
Click to collapse
You need to type the filename of the recovery file you download. Either the recovery filename you are typing is wrong or the file is not in the folder you are trying to flash from.
exad said:
You need to type the filename of the recovery file you download. Either the recovery filename you are typing is wrong or the file is not in the folder you are trying to flash from.
Click to expand...
Click to collapse
Thanks, Got it to flash..... you were correct i was typing the filename wrong.
I have an AT&T HTC One x. Its ***Tampered*** ***Unlocked*** HBOOT 1 .09. 0000 S-ON
I had been running an older version of TWRP, and decided I was going to clear my phone and do a fresh start. I know, I know, I should have made a backup, but I felt pretty confident in what I was doing, and was in too much of a hurry to rationalize this.
I wiped both the OS and previous version of TWRP in order to update to the new ones. While in fastboot I flashed CLEANrom and the new version of TWRP, and my administrative command prompt confirmed that they were installed successfully. Even cleared the cache afterwards. Now is the difficult part. I've researched, and researched, and cannot find a solution for this problem. I keep having a Boot Loop.... I'm stumped guys... I need some sort of help, be it technical, or something to drink lol
Previous ROM was CM 10, with TWRP and PA GAPPS :good:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
timmaaa said:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
Click to expand...
Click to collapse
I don't see anything in your FAQ that I haven't already tried unfortunately.....
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
timmaaa said:
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
It's the newest version of TWRP that is out, and yes, I flashed it via Fastboot, and it says successful on both the recovery install and ROM install.
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
1332858898
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
Click to expand...
Click to collapse
TWRP 2.7. And yes, I have flashed about 4 Roms all succeeded according to fastboot and still getting the boot sequence.:good:
Yes I have extracted the boot.img
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
Click to expand...
Click to collapse
yes the boot.img file was extracted. I get a confirmation that it was successful when I flash it on fastboot
Exactly which ROMs have you tried to flash?
Sent from my Evita
timmaaa said:
Exactly which ROMs have you tried to flash?
Sent from my Evita
Click to expand...
Click to collapse
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
outcold32 said:
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
Click to expand...
Click to collapse
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
exad said:
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
Click to expand...
Click to collapse
If you would have read the thread, you would have noticed, that I am in bootloop, therefor I cannot access the recovery. And I have to have access to the ROM on my phone in order to flash anything via TWRP so this is moot. My question isn't how to flash roms, it's why am I getting a loop when I am successful on a clean partition and clean flash of both the recovery and ROM? And to me, fastboot is way easier than TWRP. I guess I could get a UART and try to debug the sequence myself, but I have more important things to do than that. I was posting to see if anyone had any similar problems. And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place. I ran the RUU after I re-locked the bootloader, and I'm at least out of the loop. I'm just going get to a more stable version so that this process will be more streamline when I re do my unlock and stuff.
So I guess the only solution at this point I have for any problem like this is to use the proper RUU. I tried a couple of times with no success, and it seemed the charm was to re lock the bootloader ( Fastboot oem lock) in order to properly and successfully get the RUU to work.:good:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
exad said:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
Click to expand...
Click to collapse
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Okie dokie. No point in arguing. You're right. I'm wrong. Glad it's all working now.
Sent from my One XL using xda app-developers app
outcold32 said:
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Click to expand...
Click to collapse
Exad is right in saying that the reason you're having problems is because you're attempting to flash ROMs with fastboot. That isn't how it's done. The correct way is to flash your ROM with recovery. You're barking up the wrong tree, not only that but you're arguing with experienced people who are only attempting to help get you out of the mess that you've gotten yourself into. You came here for advice, but there's no point in asking for advice if you're just going to argue and dismiss what you're being told to do.
You said you can't access your ROM so you can't flash anything, that makes absolutely no sense, which leads me to believe you don't really know what you're doing. Get out of the mindset that you need to use fastboot, it's wrong. You're dealing with people who have extensive and intimate knowledge of this device, trust us, we know what we're talking about.
Exactly why can't you access recovery? If you can issue fastboot commands that means you can access your bootloader, if you can access your bootloader that means you can use your volume keys to scroll through the options and the power button to select recovery. What happens when you do that? Exactly which recovery have you flashed to your device? I need to the full filename of the recovery that you've flashed.
Sent from my Evita
outcold32 said:
And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place.
Click to expand...
Click to collapse
S-on is a downright dangerous place to be, if the phone is also SuperCID (which is very likely, since its the AT&T variant). exad is right in recommending s-ff, as he is about a good many things.
Can somebody explain me,how can i go back to stok to apply ota update if im rooted and have opend bootloader!?
krepsz said:
Can somebody explain me,how can i go back to stok to apply ota update if im rooted and have opend bootloader!?
Click to expand...
Click to collapse
Hi,
me too i want to back to stock but i think it's to complicated, so what i know : 1st backup ur current custom rom (for safe ^^);
2nd restore stock recovery; 3th restore RUU for your A9 (hiaeuhl or hiaeul etc ... ) that all i know but i heard that we need to restore the /system partition (i dont backup this before install cm13 :/ ) if anybody know what to do exactly :fingers-crossed: :silly:
the s-on/s-off scare me too xD i dont know what to do to restore stock properly ^^' maybe we have another thread for that i look later
S-on/off has nothing to do with going back to stock (unless you want to change version).
if you flash RUU you'll be 100% stock but you'll lose everything including root
bootloader is fine i guess.
syntenza said:
S-on/off has nothing to do with going back to stock (unless you want to change version).
if you flash RUU you'll be 100% stock but you'll lose everything including root
bootloader is fine i guess.
Click to expand...
Click to collapse
I relocked bootloader and flash stock recovery,but if i want flash the RUU fil i get this:
target reported max download size invalid sparse file format at header magi
krepsz said:
I relocked bootloader and flash stock recovery,but if i want flash the RUU fil i get this:
target reported max download size invalid sparse file format at header magi
Click to expand...
Click to collapse
Verify that you have the correct RUU for your phone. If you do, and it still isn't working, try the RUU .exe while your phone is in download mode. Also, make sure you're not using a USB 3.0 port. Sometimes that can cause problems.
CSnowRules said:
Verify that you have the correct RUU for your phone. If you do, and it still isn't working, try the RUU .exe while your phone is in download mode. Also, make sure you're not using a USB 3.0 port. Sometimes that can cause problems.
Click to expand...
Click to collapse
I found just one old RUU zip file for my phone.RUU.exe i dont know where i can found.Usb port working with all command before.
krepsz said:
I found just one old RUU zip file for my phone.RUU.exe i dont know where i can found.Usb port working with all command before.
Click to expand...
Click to collapse
What A9 version do you have? (Unlocked, carrier, EU, etc.)
CSnowRules said:
What A9 version do you have? (Unlocked, carrier, EU, etc.)
Click to expand...
Click to collapse
Vodafone UK
modelid: 2PQ910000
cidnum: VODAP001
Refer to this thread by @alray.
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Download 1.27.161.6 from post #1, then follow the steps from post #2. I'd try the first method, first.
This should work unless your firmware was updated to a later version than 1.27.161.6.
CSnowRules said:
Refer to this thread by @alray.
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Download 1.27.161.6 from post #1, then follow the steps from post #2. I'd try the first method, first.
This should work unless your firmware was updated to a later version than 1.27.161.6.
Click to expand...
Click to collapse
Thank you very much,but i was try 3 times and i get always error and force closed my fastboot.See post 4 from this thread!
krepsz said:
Thank you very much,but i was try 3 times and i get always error and force closed my fastboot.See post 4 from this thread!
Click to expand...
Click to collapse
Gotcha, I'd recommend that you use the external sd/stock recovery method to return to stock. That's probably the most bulletproof way to return to stock. If you no longer have the stock recovery, no problem. It's pretty simple to extract the recovery from the RUU and flash it first.
Also, did you download the RUU again? It is possible that you may have a corrupted RUU.zip if it is crashing your fastboot.
So me i'm on CM13 nightlies with twrp and boot.img modified, to back to stock i had to flash stock recovery( * ) than flash the RUU( ** ) ? that all ?
*: i had to extract it from the RUU coresponding i'm good ? ^^"
**: my cid is HTC_034; my mid is 2PQ910000 so i had to take the 1.10.401.7 RUU i'm good ? ^^' or the 1.56.401.70 or 1.27.401.5 ? i'm lost, on my dowload mode it's say i'm on 1.10.401.7 (but i'm on cm13 latest nightlies ... >< )
Than, when i'm succefully back to stock if i choose to return to cm13 i can flash my backup(recovery+boot+/system+rom) of cm13 with twrp if firmware doesn't upgrade with OTA on stock i'm good ?
Lots of question i know ^^' thx for help.
krepsz said:
Thank you very much,but i was try 3 times and i get always error and force closed my fastboot.See post 4 from this thread!
Click to expand...
Click to collapse
If you use the sd card method (copy the RUU.zip to external sd) fastboot is no longer necessary. The RUU is flashed using the stock recovery. There's no fastboot to crash at that point.
---------- Post added at 04:01 PM ---------- Previous post was at 03:49 PM ----------
ValdOr7 said:
So me i'm on CM13 nightlies with twrp and boot.img modified, to back to stock i had to flash stock recovery( * ) than flash the RUU( ** ) ? that all ?
*: i had to extract it from the RUU coresponding i'm good ? ^^"
**: my cid is HTC_034; my mid is 2PQ910000 so i had to take the 1.10.401.7 RUU i'm good ? ^^' or the 1.56.401.70 or 1.27.401.5 ? i'm lost, on my dowload mode it's say i'm on 1.10.401.7 (but i'm on cm13 latest nightlies ... >< )
Than, when i'm succefully back to stock if i choose to return to cm13 i can flash my backup(recovery+boot+/system+rom) of cm13 with twrp if firmware doesn't upgrade with OTA on stock i'm good ?
Lots of question i know ^^' thx for help.
Click to expand...
Click to collapse
You shouldn't have any trouble returning to stock at all. I've had quite a few Heineken at this point, but flashing boot, recovery, and system of your stock rom is no problem at all if you have backups.
CSnowRules said:
If you use the sd card method (copy the RUU.zip to external sd) fastboot is no longer necessary. The RUU is flashed using the stock recovery. There's no fastboot to crash at that point.
---------- Post added at 04:01 PM ---------- Previous post was at 03:49 PM ----------
You shouldn't have any trouble returning to stock at all. I've had quite a few Heineken at this point, but flashing boot, recovery, and system of your stock rom is no problem at all if you have backups.
Click to expand...
Click to collapse
Could you state how this is done? I recently moved to the A9 from having the M7 since it came out, (which had NO external SD card support) , so this is the 1st I'm hearing of being able to apply an RUU Without fastboot... Does the RUU have to be in any specific folder, or the root of the external SD card?
Any details would be GREATLY appreciated.
bdizzle1686 said:
Could you state how this is done? I recently moved to the A9 from having the M7 since it came out, (which had NO external SD card support) , so this is the 1st I'm hearing of being able to apply an RUU Without fastboot... Does the RUU have to be in any specific folder, or the root of the external SD card?
Any details would be GREATLY appreciated.
Click to expand...
Click to collapse
This http://forum.xda-developers.com/showpost.php?p=63640734&postcount=2 explains in detail. I THINK this utilizes the stock recovery in the process. In any case, it allows flashing an RUU.zip without any fastboot involvement.
It's possible to return s-on and bootloader locked (not relocked)? Thank's.
CSnowRules said:
You shouldn't have any trouble returning to stock at all. I've had quite a few Heineken at this point, but flashing boot, recovery, and system of your stock rom is no problem at all if you have backups.
Click to expand...
Click to collapse
Yes i know but u dont understand me i think, for the RUU there 3 version for my phone 1.10 -> 1.27 -> 1.56 so witch one i had to take ? CM13 run with 1.27 ? 1.10 with cm13 isn't possible no ? because on my download mode(bootloader) it's say : OS-1.10.401.7 in theory i would take the 1.10.401.7 RUU but a man (on this forum) tell me this was a bug of cm13 and its run with 1.27 it's wrong ??
ValdOr7 said:
Yes i know but u dont understand me i think, for the RUU there 3 version for my phone 1.10 -> 1.27 -> 1.56 so witch one i had to take ? CM13 run with 1.27 ? 1.10 with cm13 isn't possible no ? because on my download mode(bootloader) it's say : OS-1.10.401.7 in theory i would take the 1.10.401.7 RUU but a man (on this forum) tell me this was a bug of cm13 and its run with 1.27 it's wrong ??
Click to expand...
Click to collapse
Any one of the three would return you to stock, as long as the version number is greater than or equal to the firmware that you have installed. (Which is the topic of this tread...)
As far as compatibility with CM, you should check that thread...but I think CM is compatible with the 1.27 firmware. If you're still s-on, you DO NOT want to upgrade the firmware to a newer version than CM supports, if you intend to use CM.
---------- Post added at 02:44 PM ---------- Previous post was at 02:39 PM ----------
CEDRIC23 said:
It's possible to return s-on and bootloader locked (not relocked)? Thank's.
Click to expand...
Click to collapse
I'm sure it's possible...just a matter of finding exactly what you need to hex edit and where it is. Experimenting with this likely carries a chance of bricking your device, since the variables would have to be used by HBOOT and/or download mode. Maybe someone else has already accomplished this?
krepsz said:
Thank you very much,but i was try 3 times and i get always error and force closed my fastboot.See post 4 from this thread!
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash a RUU, not the regular fastboot.exe from the android sdk.
CSnowRules said:
This http://forum.xda-developers.com/showpost.php?p=63640734&postcount=2 explains in detail. I THINK this utilizes the stock recovery in the process. In any case, it allows flashing an RUU.zip without any fastboot involvement.
Click to expand...
Click to collapse
The stock recovery is not used when flashing a RUU from the sdcard. The bootloader handles the process, not the recovery. Stock recovery isn't needed at all, using fastboot or the sdcard methods.
alray said:
The stock recovery is not used when flashing a RUU from the sdcard. The bootloader handles the process, not the recovery. Stock recovery isn't needed at all, using fastboot or the sdcard methods.
Click to expand...
Click to collapse
Thanks, Alray, for the clarification on the sd card method.