i everyone, i did a terrible mistake, tried to root without proper knowledge.
i have a htc one XL (international version). details below;
evita pvt ship S-OFF RL
cid- 11111111
hboot-2.15.0000
radio-1.30a.32.45.18
opendsp-v33.1.0.45.1128
emmc-boot
july 16 2013, 19.27.23.12895
Hboot
-----------------
fastboot
recovery
factory reset
clear storage
simlock
image crc
power down
show barcode
i used htcdev to unlock the bootloader and it went smoothly. next i htc one x aio kit by hasoon and tried to flash cwm but it did not work. out of desperration i downloaded r3 endeavor insecurebootandroot and clicked on the install-insecure-windows.bat file. it did something and while restarting under htc logo phone says 'this build is for development purposes only do not distribute outside of htc without written permission. Failure to comply may lead to legal action.'
i tried factory resetting from the boot screen(power button+volume down) but it did not work.
i dont know what to do, im exhausted and desperate. i know its not the XL forum but many say one x and xl can be rooted in the same way.
please someone help, what do i need to do? im a student and i cannot leave this one and buy another.
edit: phone was running on JB 4.2.2
The One XL and One X cannot be rooted in the same way, none of their exploits/firmware/software is compatible with each other. My suggestion is to run an Evita RUU to take it back to stock and start again. Stay within this forum, do not wander anywhere else, you're extremely lucky you haven't bricked your phone.
Sent from my Evita
timmaaa said:
The One XL and One X cannot be rooted in the same way, none of their exploits/firmware/software is compatible with each other. My suggestion is to run an Evita RUU to take it back to stock and start again. Stay within this forum, do not wander anywhere else, you're extremely lucky you haven't bricked your phone.
Sent from my Evita
Click to expand...
Click to collapse
thannk you, thank you. as you already know im a noob, can you please tell me what is evita RUU and where to get it? also how to RUN it?
Ok, Evita is the codename for the One XL, that's why it's displayed at the top of your bootloader. RUU is an acronym and it stands for Rom Update Utility, basically what it does is install a fully stock system on your phone, including ROM, recovery, hboot etc. The RUU will remove any dodgy firmware/software from your phone and replace it with the right ones. Here is the link for Evita RUU's:
http://androidruu.com/?developer=Evita
It's an exe program so all you need to do is connect your phone to your pc in fastboot mode and run the exe file, follow a few prompts on the PC and it's done. Make sure you don't have HTC Sync Manager installed, make sure no other programs are running, and make sure screen saver / hibernation is turned off. Once it's finished you can either stay stock or you can install a custom recovery (I'd suggest TWRP 2.6) and then custom ROMs. Just make sure your stay within this forum from now on and you'll be fine.
PS. Stay away from anything with Endeavoru in the filename, that's for the One X. If you need instructions on how to install TWRP recovery let me know.
Sent from my Evita
timmaaa said:
Ok, Evita is the codename for the One XL, that's why it's displayed at the top of your bootloader. RUU is an acronym and it stands for Rom Update Utility, basically what it does is install a fully stock system on your phone, including ROM, recovery, hboot etc. The RUU will remove any dodgy firmware/software from your phone and replace it with the right ones. Here is the link for Evita RUU's:
http://androidruu.com/?developer=Evita
It's an exe program so all you need to do is connect your phone to your pc in fastboot mode and run the exe file, follow a few prompts on the PC and it's done. Make sure you don't have HTC Sync Manager installed, make sure no other programs are running, and make sure screen saver / hibernation is turned off. Once it's finished you can either stay stock or you can install a custom recovery (I'd suggest TWRP 2.6) and then custom ROMs. Just make sure your stay within this forum from now on and you'll be fine.
PS. Stay away from anything with Endeavoru in the filename, that's for the One X. If you need instructions on how to install TWRP recovery let me know.
Sent from my Evita
Click to expand...
Click to collapse
thank you so much, I feel much better now.
from that list which one you think I should download ?
also in current state, will my phone charge from a wall charger ?
christo_tj said:
thank you so much, I feel much better now.
from that list which one you think I should download ?
Click to expand...
Click to collapse
With S-off, you can run any RUU. You might pick a more recent version (3.1x)
christo_tj said:
also in current state, will my phone charge from a wall charger ?
Click to expand...
Click to collapse
If the screen comes on, it should charge. Plug it in, and if the red or green charge LED comes on, its charging.
redpoint73 said:
If the screen comes on, it should charge. Plug it in, and if the red or green charge LED comes on, its charging.
Click to expand...
Click to collapse
when I plug the wall charger, the red led lights up for a couple of seconds and goes off.
Try a different USB cable?
Sent from my One Xl using xda app-developers app
to use RUU do I need to relock the bootloader?
exad said:
Try a different USB cable?
Sent from my One Xl using xda app-developers app
Click to expand...
Click to collapse
but I used the same charger to charge the phone before I screwed it up.
christo_tj said:
to use RUU do I need to relock the bootloader?
Click to expand...
Click to collapse
You're s-off so you don't need to relock the bootloader.
Sent from my Evita
---------- Post added at 10:04 AM ---------- Previous post was at 10:03 AM ----------
christo_tj said:
but I used the same charger to charge the phone before I screwed it up.
Click to expand...
Click to collapse
Leave it plugged in for a few hours, overnight if possible.
Sent from my Evita
timmaaa said:
You're s-off so you don't need to relock the bootloader.
Sent from my Evita
---------- Post added at 10:04 AM ---------- Previous post was at 10:03 AM ----------
Leave it plugged in for a few hours, overnight if possible.
Sent from my Evita
Click to expand...
Click to collapse
thanks for the tips.
I'll be trying to run RUU today.
things I'm gonna do;
uninstall htc sync.
install necessary drivers for fastboot
put phone in fastboot mode and connect the USB, where it will hopefully say 'fastboot USB'
then run the RUU.
fingers crossed, hop I won't get any errors. I'll update here whatever happens
and I'll be using OTA_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1 (3rd one on that list) is it ok ?.
No problems, and yes that all sounds right to me. Good luck.
Sent from my Evita
timmaaa said:
:
Make sure you don't have HTC Sync Manager installed, make sure no other programs are running, and make sure screen saver / hibernation is turned off.
Click to expand...
Click to collapse
sorry to go a bit off topic but why to NOT have HTC sync manager.
cause i had it installed when i RUUd my device nothing went wrong!?
It can get in the way and disrupt communications between the PC and the phone. While running an RUU it's suggested that no other programs are running at the same time, and while you can exit Sync Manager it has a habit of opening by itself randomly. The last thing you want to happen while running an RUU is any kind of disruption as this can cause a brick.
Sent from my Evita
timmaaa said:
It can get in the way and disrupt communications between the PC and the phone. While running an RUU it's suggested that no other programs are running at the same time, and while you can exit Sync Manager it has a habit of opening by itself randomly. The last thing you want to happen while running an RUU is any kind of disruption as this can cause a brick.
Sent from my Evita
Click to expand...
Click to collapse
what if the power supply fails?
ill go to some cyber cafe with power backup just to be on the safer side.
btw how much time does the RUU take to finish the job ?
I'm gonna do it tomorrow.
A power supply failure would be pretty rare, but yeah if it stops halfway through you'd be in trouble. The process usually takes about 15-20 minutes.
Sent from my Evita
timmaaa said:
A power supply failure would be pretty rare, but yeah if it stops halfway through you'd be in trouble. The process usually takes about 15-20 minutes.
Sent from my Evita
Click to expand...
Click to collapse
and the worst thing happened.
phone isn't switching on anymore. I kept it in my drawer all day and in the night tried to charge. the led blinked twice and turned off as usual. I kept it charging for an hour, then tried turning on by pressing and holding down the power button *nothing*
tried pressing the button for ten mins, nothing happened. tried holding down power key + volume down = same story. tried holding down power key + volume for 2 min = nothing.
I screwed it :'( can't bear the loss :'(
It's probably salvageable via a jtag repair, all is not lost yet. It usually costs about $60 USD.
Sent from my Evita
timmaaa said:
It's probably salvageable via a jtag repair, all is not lost yet. It usually costs about $60 USD.
Sent from my Evita
Click to expand...
Click to collapse
I'll be sending the phone back to the ebay seller. I've opened a claim some days ago as the phone was having some issues(yellow spots on screen, overheating, long charging time).
if all goes well, I'll get a new phone in two weeks.
btw thanks a lot for helping me out, I'll probably need more to root my (hopefully) comin evita
Related
Hey
I just got a huge bootloop while attempting to flash new Venom Room to my HTC One X. http://forum.xda-developers.com/showthread.php?t=1868236
I cannot access the recovery.. After restart (power button+volume down) i can get to bootloader section, but when i try to get into recovery, the phone just restart and stop on the white htc screen.
I already tried to reinstall recovery. Installation was successful, but the problem persists..
Before i had Incert Coins room.
The phone is unlocked, new recovery is installed
Please, help
If you had Insert Coin working on your phone, you have an international (Tegra3) version of the One X. This forum (and the Venom ROM you linked) are for the Snapdragon S3 version. Completely different hardware.
If I'm correct, you flashed a ROM for the wrong phone. Try running the RUU for your phone, but if that doesn't work you may be screwed. Recovery partitions are not the same for the versions. The ROM overwrote the recovery partition of your phone.
You are right.. It WAS the wrong rom.. I have tegra3 processor and this rom comes from american section..
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Senbration said:
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Click to expand...
Click to collapse
RUU just returns your phone to the stock condition. Stock ROM and stock recovery. There should be nothing dangerous about it. Just use the right one for your version, carrier, etc. But the CID check should ensure that you don't run the wrong RUU (if RUU is for a different CID, the RUU will not run).
Only thing with RUU, is that it wipes all user data. That may be why you heard its "dangerous". But in the condition you are in, this is not even a consideration anymore.
RUU is not dangerous, and it may be your only hope at this point.
You will need to lock your bootloader before running the RUU.
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
I'm assuming you meant relocked bootloader and now has security warning relocked if this what you meant then you are fine flash the ruu
Sent from my Nocturnalized One XL using Forum Runner
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
You mean relocked and not reloaded? If so, you should be good to run the RUU. Redpoint, sorry for highjacking your help session
Sent from my One X using xda premium
ohh, its Relocked.. Im just a bit nervous right now hoping it will unbrick this phone..
Just 3min to complete RUU download.
Do U guys think this stock RUU will rewrite the partitions back?
I've noticed another problem.
Cannot load RUU because the battery level is lower then 30%.
But when i plug the charger the light doesnt flash. It starts to flash when i switch on the phone.
Also cannot switch the phone with the power button. It restart all the time. Only can do that from bootloader command "power down". But when the phone is off the power light doesnt flash..
Does it mean that the battery is not charging at all? Because the light can flash only because the power is low..
The phone shut down completly now.. Does not charge the battery at all.. Power gone off and i cannot even turn on the phone..
Is there any solution how to make it charge?
Ok, the problem is that the wrong ROM i tried to install changed partition and also it seems it destroyed Recovery..
Without recovery the phone cannot charge while being in bootloader mode...
Is there any way to make phone charging when Recovery doesnt work and cannot be flashed?
Please help
Take the phone apart. I mean all the way spart and hardwire a charger to the phone/ battery. Its a pain but you can do it.
Ohh..
I found a treat http://forum.xda-developers.com/showthread.php?t=1658084
There is a way to charge battery by running the script, which makes phone reinstalling constantly. Each time it is reinstalled, the battery is charged a little bit more.
After mayby 40min i went up from 3686 V to 3720 V.
It seems that my only hope is to reinstall RUU. I tried to flash wrong ROM, from wrong model and as one user wrote above, it has rewritten my partition. Same time it destroyed recovery.. I cannot flash recovery now because the partition is rewritten...
And without working recovery i cannot charge the battery being in bootloader.. If i understand it all correctly.
I already tried to install RUU with 3710 V. It started to install, but stopped after few min with information that battery is too low..
So i think ill leave this script running for a whole night, and hope, in the morning battery will be charged just enough to install RUU eventually..
Uff
Okey, finally its fixed..
After 7 hours of constant reinstalling the phone by the script, the battery was loaded enough to finish RUU instalation process.. (battery went to about 3830mV power)
After oryginal RUU was installed, everything went fine.
Now i already re-unlocked the bootloader, re-rooted the phone and all works correctly.
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Amazingly impressive to me.
Thanks for following up with your success.
WR
Sent from a CleanRom-V OneX
THAT is AWESOME
Senbration said:
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Click to expand...
Click to collapse
Your welcome, and no problem really. It was an easy problem to recognize, as I've seen it several times before on here.
Nice job getting the phone charged. Haven't seen that solution before.
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Sent from my HTC One X using Tapatalk 2
Senbration said:
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Click to expand...
Click to collapse
Sh1T! Did I forget to do that???? I must have been in a good mood . . .
Heh it must have been so
Sent from my HTC One X using Tapatalk 2
A little foreshadow. I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install. I was silly and decided to clear the system... Which erased my OS completely.
For a while I was able to get to the TWRT(?) screen where I could mount my sd card, etc. While researching the problem I came across this:
a solution of fastbooting a recovery.img
I ran the fastboot recovery.img. The only problem is the only screen I can now access is the bootloader. I have bootloader 1.14.0002 loaded onto my phone if that helps.
Is there anyway to try to get a operating system or flash a rom onto this phone still or is it bricked for good? Also if I was able to put a rom onto it, what do you sugggest?
When I try to go to Recovery or Factory Reset, I get the HTC screen with the red text underneath it and it never goes any further.
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
That is the information listed in my bootloader as of now. I am not showing it listed as a drive in my computer when connected to USB. Also when I 'power off' I am in a reset cycle that doesn't stop.
I really appreciate any help in advance. This was a big wake up call to myself about how I should be a lot more careful when messing with these things.
Thank you to everyone that answers!
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
You might be hosed. Can you get into bootloader?
Sent from my One X using xda premium
Read before doing anything. Such a simple task. It's easy to read, it's hard to come back from a brick.
Sent from my One XL using XDA Premium
You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer. http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.0-evita.img
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2
Not only does fastboot erase cache not take long it avoids many stupid little issues. I would say it's a must when flashing a new recovery.
Sent from my One X using xda app-developers app
sinkthehalffoot said:
I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install.
Click to expand...
Click to collapse
The reason it went to recovery is very simple. The OTA needs to have stock recovery in order to install. You don't have stock recovery on your phone anymore, you have custom recovery (TWRP). So the OTA stalled there, when it didn't find stock recovery.
sinkthehalffoot said:
I was silly and decided to clear the system... Which erased my OS completely.
Click to expand...
Click to collapse
Of course it did, what were you expecting to happen? Wiping the OS is the very definition of what happens when you wipe system. If you didn't know what wiping system would do, you shouldn't have done it. For that matter, you shouldn't be doing anything on your phone if you don't know what its for.
A lot of this points to a fundamental lack of reading and understanding:
- Don't know the name of the custom recovery installed on the system
- Wiping things without knowing what they are
- Basic rule (that many folks here seem to ignore, for reasons unknown): Don't install any OTA on a rooted device without first researching what will happen
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
You aren't bricked. With very few exceptions (and this isn't one of those) if the screen turns on, and you can get into hboot, the phone is recoverable. And probably fairly easily so, with the right steps. But you need to do some homework before proceeding.
redpoint73 said:
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
Click to expand...
Click to collapse
+1000
This is exactly the kind of situation that occurs when people get in over their heads and start blundering around.
http://forum.xda-developers.com/showthread.php?t=2232141
InflatedTitan said:
You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer.
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
In case anyone ends up stumbling here with a similar issue, this solution worked to a 'T'. Thank you again InflatedTitan.
To everyone else, yes I know, I should of read more than I had. I saw the jellybean update and have been wanting it for a while and acted with haste. I learned a valuable lesson from it all.
Lol this "solution" was around before you posted. You just didn't read or search enough.
Sent from my One X using xda app-developers app
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Lol :beer:
Sent from my HTC One X using xda app-developers app
Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I thought I was the only one. In fact I just rooted a nook tablet and installed twrp. Slides to flash... And I could swear I was on cloud 9.
But bravo on the explanation sir. Love a good write up. Even though i already know it, feels good to read it.
Sent from my Carbon-ize Evita using xda-developers app
[HELP] Not sure if bricked or hardware issue?
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
pharrjw said:
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Click to expand...
Click to collapse
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?
exad said:
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?
Click to expand...
Click to collapse
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?
If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Sent from my HTC One X using xda app-developers app
pharrjw said:
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?
Click to expand...
Click to collapse
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.
Thanks again for the replies guys.
31ken31 said:
If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Click to expand...
Click to collapse
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
exad said:
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.
Click to expand...
Click to collapse
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.
pharrjw said:
Thanks again for the replies guys.
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.
Click to expand...
Click to collapse
factory reset in bootloader corrupts the SD card. We wont worry about that just yet as there's nothing we can do about it until we can get recovery on there.
You're going to have to be very careful because it sounds like your EMMC partitions might have some issues. if you can get it to bootlaoder KEEP IT AT THAT SCREEN. don't power it off or anything, leave it there. Because one wrong move could be a perma brick. If we can get a rom on there to S-OFF with, we can RUU to restore your emmc partitions.
UPDATE
=========
I just wanna say that tomy1986.nt is the man!!!! If you have a bricked device send it to this guy, worth the money! He fixed my device within an hr! It wouldn't power on at all!
http://forum.xda-developers.com/member.php?u=4116958
Dropped it off at his house and he worked his magic!
=========
Ok got an HTC One X..... ran the RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe to update the device after running "fastboot oem lock" and the program said it had completed successfully, the phone turned off and never came back on. I unplugged the device and attempted to turn it on, no lights, no nothing.
The only thing that happens is if I plug it into my computer I hear the sound you hear when a driver is attempting to install. The HTC drivers are indeed on my computer.
Any hope for unbricking this thing or am I screwed?
Thanks!
Do you have the One X (Endeavor) or the One XL (Evita)?
Sent from my Evita
I have the one x but my understanding was the roms were interchangeable. It's the AT&T One X.
You're just a bit mixed up with your terminology. Your phone is the the at&t One X / HTC One XL (Evita), the HTC One X is the Endeavor.
Being that the at&t One X and HTC One XL are the same phone (Evita), the ROMs are the same. But HTC One X (Endeavor) ROMs are not for our phone and can brick it if flashed.
Was your phone second hand? Do you know if it had SuperCID? And whether it is s-on or s-off? If it has SuperCID and is s-on, running an RUU causes a brick.
Does the phone show up as QHSUSB_DLOAD in device manager on pc when you connect it? If so you have a brick, and still need to get a jtag repair done.
Sent from my Evita
If the phone was S-on and SuperCID, you have a true hard brick. As timmaaa mentioned, if you get QHSUSB_DLOAD when you connect to PC, this pretty much confirms it.
Sounds like either you, or the original owner unlocked the bootloader, since you went through the step of relocking it (or at least you suspected it may be unlocked). So my guess is that you are another victim of the S-on + SuperCID + Jellybean RUU/OTA combo.
http://forum.xda-developers.com/showthread.php?t=2181929
Actually I only used evita roms/ruu's.
Here is exactly what I did:
1) Rooted / S-OFF / Flashed Recovery / Unlocked Bootloader / Super CID 111111111 (how many ever 1's)
2) Locked Bootloader and refreshed with 2.20 RUU which was successful
3) Rebooted phone, enabled debugging
4) Ran 3.18 RUU (AT&T One X) and it said successful.
5) Device powered off and i waited, never came back on so i unplugged it
6) Makes driver noise when plugging to pc but does not power on visually, no lights etc
I found a guy locally who can try the jtag.
You could try charging it for a few hours and try holding power + volume down to see if it boots. Every now and again these phones have a power management issue where it loses power (or thinks it does) completely.
If that doesn't work it looks like you might be one of the very unlucky people who has had an RUU brick their phone for no apparent reason.
Sent from my Evita
ssconceptz said:
Here is exactly what I did:
1) Rooted / S-OFF / Flashed Recovery / Unlocked Bootloader / Super CID 111111111 (how many ever 1's)
Click to expand...
Click to collapse
Ok, so it wasn't the combo of S-on, SuperCID and Jellybean RUU that caused the brick then.
But any flashing of hboot has some small possibility of bricking the phone, if everything does not go exactly right (such as corrupt RUU file). You can look into the unbricking thread in General:
http://forum.xda-developers.com/showthread.php?t=1966850
You can see if you can enumerate the partitions with Linux. If the parititions can't be found, JTAG is your next option.
Nobody has been able to unbrick this way from the S-on, SuperCID, RUU combo, that I know of. But your case is slightly different, so maybe you still have a chance.
---------- Post added at 11:18 AM ---------- Previous post was at 11:13 AM ----------
timmaaa said:
You could try charging it for a few hours and try holding power + volume down to see if it boots. Every now and again these phones have a power management issue where it loses power (or thinks it does) completely.
Click to expand...
Click to collapse
Yes, its a good idea to try that.
Although the fact it went dark right after running the RUU, doesn't have me very hopeful.
Yeah I'm not hopeful at all either, but it's worth a try.
Sent from my Evita
timmaaa said:
Yeah I'm not hopeful at all either, but it's worth a try.
Click to expand...
Click to collapse
Absolutely! Always good to try the easy stuff first, before resorting to more drastic measures.
Thanks for the tips. Will try the unbrick hardware method, if doesn't work maybe i'll find a busted up device and use this one for parts.
I just wanna say that tomy1986.nt is the man!!!! If you have a bricked device send it to this guy, worth the money! He fixed my device within an hr! It wouldn't power on at all!
http://forum.xda-developers.com/member.php?u=4116958
Dropped it off at his house and he worked his magic!
I really screwed up, I was installing a new OP and was wiping Cache, Dalvik ect... when I accidently wiped my external storage. Well I mounted my SD card and put an OP back on the sd card, installed through TWRP and I'm just stuck in a boot loop. Have tried several differnt OP's and all I get is the boot loop. Can someone please help me correct what I screwed up. Everything is gone, when I look under Android secure there is nothing.
I'm not sure what you mean by OP? Maybe you mean ROM? Anyway you need to give more information, what are your bootloader details?
Sent from my Evita
timmaaa said:
I'm not sure what you mean by OP? Maybe you mean ROM? Anyway you need to give more information, what are your bootloader details?
Sent from my Evita
Click to expand...
Click to collapse
Your correct, I was half asleep when I posted my question. I do mean ROM. What kind of information from the bootloader would you like?
S-off
CID-111111111
HBOOT-1.09.0000
OpenDSP-v34.1.0.45.1219
Well you're s-off, so the boot.img isn't the problem. Which ROMs in particular have you tried installing? What version of TWRP are you using?
Sent from my Evita
timmaaa said:
Well you're s-off, so the boot.img isn't the problem. Which ROMs in particular have you tried installing? What version of TWRP are you using?
Sent from my Evita
Click to expand...
Click to collapse
VenomXL 4.0.0 Sense 5, VenomXL 3.2.7, HatkaXL-evita-v4.7.1. These are all ROM's that I have previously run on my phone. TWRP is v2.3.3.1.
Thank you for your help.
You might need to try running an RUU.
Sent from my Evita
timmaaa said:
You might need to try running an RUU.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaaa are you going for the record of "how many people can you help!" on the Evita forums :silly:
scrappy1959 listen to this guy as he knows what he is talking about! :laugh:
radavs said:
Hey timmaaa are you going for the record of "how many people can you help!" on the Evita forums :silly:
scrappy1959 listen to this guy as he knows what he is talking about! :laugh:
Click to expand...
Click to collapse
Lol I have a lot of spare time on my hands recently, I can't work right now due to health problems so I spend a lot of time on here. I've taken a lot from the XDA community over the years so I feel it's the right thing to do to try to give back and help people where my knowledge permits. I love learning, especially when it comes to Android and I think this is the best place to do it. I think the next step is to actually try to learn how to develop a ROM, but that'll have to wait until I get a new PC.
Sent from my Evita
---------- Post added at 02:37 PM ---------- Previous post was at 02:25 PM ----------
By the way, radavs, it's great to see you throw another Telstra ROM on here for the Aussies :thumbup:
Sent from my Evita
timmaaa said:
You might need to try running an RUU.
Sent from my Evita
Click to expand...
Click to collapse
What would be a good RUU and how would you flash it? I don't want to lose root. Went through to much to achive it.
Root isn't the thing you should be worried about, the unlocked bootloader and custom recovery are what you actually need to flash custom ROMs. All root does is give you administrative access to the root directories on your phone.
You are s-off so it doesn't matter which RUU you use, click the link in my signature and you'll find RUU links in there. Your bootloader will remain unlocked and you will retain your s-off status through the RUU process. You don't "flash" an RUU, it's an exe file so you run it like you would run any other exe program on a pc. An RUU returns your phone to being completely stock, including recovery, so you'll need to flash TWRP again afterwards.
Sent from my Evita
timmaaa said:
I have a lot of spare time on my hands recently, I can't work right now due to health problems so I spend a lot of time on here. I've taken a lot from the XDA community over the years so I feel it's the right thing to do to try to give back and help people where my knowledge permits.
Click to expand...
Click to collapse
I love this attitude, as this is what XDA is all about. Contribute however you can, whenever you can!
timmaaa said:
Root isn't the thing you should be worried about, the unlocked bootloader and custom recovery are what you actually need to flash custom ROMs. All root does is give you administrative access to the root directories on your phone.
You are s-off so it doesn't matter which RUU you use, click the link in my signature and you'll find RUU links in there. Your bootloader will remain unlocked and you will retain your s-off status through the RUU process. You don't "flash" an RUU, it's an exe file so you run it like you would run any other exe program on a pc. An RUU returns your phone to being completely stock, including recovery, so you'll need to flash TWRP again afterwards.
Sent from my Evita
Click to expand...
Click to collapse
Would you be willing to explain the steps of installing the RUU. I think I know, just don't want to screw that up also. Once I get that far I should be fine flashing TWRP.
No worries, it's an exe file so it's pretty easy. Put your phone into fastboot mode and connect it to your pc, then run the RUU exe program, it's as simple as that. Just follow the prompts on the pc, you just need to say ok a couple of times.
Just make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off.
Just make sure you don't disconnect your phone while the RUU is running, sometimes it might look like the process is freezing (it sat on 27% for a while when I did it) but just let it continue, it should be fine.
Sent from my Evita
timmaaa said:
No worries, it's an exe file so it's pretty easy. Put your phone into fastboot mode and connect it to your pc, then run the RUU exe program, it's as simple as that. Just follow the prompts on the pc, you just need to say ok a couple of times.
Just make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off.
Just make sure you don't disconnect your phone while the RUU is running, sometimes it might look like the process is freezing (it sat on 27% for a while when I did it) but just let it continue, it should be fine.
Sent from my Evita
Click to expand...
Click to collapse
Just tried running the RUU and it was not able to connect with my OneXL, it had been so long since I have done any of this I forgot when I was flashing TWRP almost a year ago, both my laptop and desktop were not able to connect to the phone, something to do with the USB ports (Windows 8). However, I have an old laptop with XP that will connect to the phone. I am leaving for work at this point and will not be able to run the RUU until late tonight. I will let you know how it works out. Thanks
scrappy1959 said:
Just tried running the RUU and it was not able to connect with my OneXL, it had been so long since I have done any of this I forgot when I was flashing TWRP almost a year ago, both my laptop and desktop were not able to connect to the phone, something to do with the USB ports (Windows 8). However, I have an old laptop with XP that will connect to the phone. I am leaving for work at this point and will not be able to run the RUU until late tonight. I will let you know how it works out. Thanks
Click to expand...
Click to collapse
Thanks so much timmaaa, got out my old windows xp laptop and the RUU is loading on the phone right now (@29%). For some reason my newer laptop and desktop will not put my phone into Fastboot USB. I think it has something to do with the newer technolgy of the high speed USB. But, soon as I hook up my old XP laptop it picks it up right away and switches into Fastboot USB. It's done, now all I have to do is put TWRP back on the phone and I should be back in business. Thanks
Okay, I ran the new RUU 1.85. I can't seem to get TWRP installed. I downloaded super user# and it says I do not have root. However when I boot into bootloader it says
***UNLOCKED***
EVITA PUT SHIP S-OFF RL
CID-111111111
HBOOT-2.14.0000
S
Didn't think I would need help getting TWRP reinstalled but I do. If you could give me a little more help getting TWRP back on my phone. Thank you
scrappy1959 said:
Okay, I ran the new RUU 1.85. I can't seem to get TWRP installed. I downloaded super user# and it says I do not have root. However when I boot into bootloader it says
***UNLOCKED***
EVITA PUT SHIP S-OFF RL
CID-111111111
HBOOT-2.14.0000
S
Didn't think I would need help getting TWRP reinstalled but I do. If you could give me a little more help getting TWRP back on my phone. Thank you
Click to expand...
Click to collapse
I forgot, the phone is just unlocked. I need to re-ROOT. Thanks for your help.
Hi All!
Recently i flashed TWRP and Cynogenmod 10.2.1 stable to my HTC Telestra One XL (evita)
I unlocked boot-loader
I successfully rooted
But I shut down once, and when i tried to boot, it got stuck in a boot-loop
Upon many retries, it suddenly wont turn on
when I charge it it only has a flashing red light but it wont even turn on, no screen not buttons; nothing!
And if I plug it in to my PC, the pc keeps sounding the USB Connected sound multiple times over a short period of 30 seconds to 2 minutes and then it gives off multiple shaky beeps
I hope this is enough info to let anyone help out!
Thank You in Advance
EDIT:
when connected to a pc it shows drivers is ready to use but tries to install QHUSB_DLOAD but fails and latest RUU does not detect
Thx again
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
timmaaa said:
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
Click to expand...
Click to collapse
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
So does it power on at all?
Sent from my Evita
timmaaa said:
So does it power on at all?
Sent from my Evita
Click to expand...
Click to collapse
nope
when plugged in it only has a red LED that flashes once every once in a while and thats it
pc recognises it but wants to install qhusb_dload (as mentioned) and it just sais no driver found
i am researching and i found something called a "RIFF Box" but unsure if its worth it, plus i dont know where to jtag it (if its possible at all)
PS: hi from sydney!
Al-Dazzlez said:
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
Click to expand...
Click to collapse
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Hi from Canada!... I just wanted to be part of the greetings.. :laugh:
exad said:
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
Click to expand...
Click to collapse
he placed the cyanogen mod on the phones sd card, then he wiped sd card, after that he used the install function on twrp it gave him a message that his phone is not rooted and if he would like to root it, he accepted, then it rebooted into twrp, and he tried again to install, same message appeared and then he gave up and shut it down...(sorry for vague terms, please bear with me, still trying to learn the ropes of talking on this forum)
I gotta say, this is all very odd :/ How did he install anything if he wiped the SD card after copying it over? :/ hmmmm In any case, you CAN try he jet tool as per my last post before getting a jtag. You'll need a linux install or Bootable USB stick/CD/DVD though.
My guess is that the only thing he installed was SuperSU. That'd be why it booted straight back into TWRP.
Sent from my Evita
timmaaa said:
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Click to expand...
Click to collapse
i researched..nothing..just some videos of people who do it (jtag)in the US and US only......
but still asking 'round the shops wont hurt i guess:laugh:
ill keep ya posted about using that tool you mentioned!
and exad; SUP!
and yeah.. it sounds weird to me too but i mainly play around with stuff like the galaxy series samsung's so the htc stuff is still new...and i have to admit...i am hating it so far.... but still experience cant hurt :laugh:
Hi guys!
im back
I JTAG'd the phone overseas, and it came back, surely enough, working, but now another problem arises,
the guy apparently unlocked the bootloader, S-Off, and installed CM with android 4.3.1. the phone boots, everything is well, but for times from 10 seconds to minutes of usage it just turns off, the Hboot shows
***tampered***
***relocked***
any idea wth is wrong with it now?
it does not reboot from power menu, and does not do anything really since I cant keep it on for more than a few minutes at most. I cannot keep it on long enough to unlock the bootlaoder anymore, and I cannot boot into TWRP (as the guy told me he put it on)
da hell do I Do now? any help appreciated
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
timmaaa said:
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Al-Dazzlez said:
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Click to expand...
Click to collapse
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
timmaaa said:
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
Click to expand...
Click to collapse
I Just ran one, Unlocked bootloader, on Cm11 snapshot after re-root and all that crap done, should be alright now