Related
So I've tried about 5 different RUU's to get my phone back to 2.2 with no luck.
Either a signature error or bootload mismatch or something or another.
I have a Sprint HTC Evo with 2.3.3.
Can someone help me get this thing back and running on 2.2?
I recently tried to use Unrevoked on it...which caused some issues with the bootloader .
Thanks, guys/gals
If you aren't s-off then you can't run an RUU for an older version. If you are s-off, just flash a rooted stock 2.2 rom. You can try a different RUU if you're already s-off, just make sure that you follow the directions closely.
If you're trying to root by downgrading, it won't work unless the phone is already s-off. If the phone is s-off and you're trying to gain root access, just flash a PC36IMG of a recovery then flash a rooted rom from there.
If you're taking it in for repair, keep s-off so you can re-root if you get the phone back (if you're already rooted and want to stay that way).
Sent from my PC36100 using Tapatalk
plainjane said:
If you aren't s-off then you can't run an RUU for an older version. If you are s-off, just flash a rooted stock 2.2 rom. You can try a different RUU if you're already s-off, just make sure that you follow the directions closely.
If you're trying to root by downgrading, it won't work unless the phone is already s-off. If the phone is s-off and you're trying to gain root access, just flash a PC36IMG of a recovery then flash a rooted rom from there.
If you're taking it in for repair, keep s-off so you can re-root if you get the phone back (if you're already rooted and want to stay that way).
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for the reply .
I'm not sure what you mean by S-OFF/S-ON however .
Also, I've tried probably five or six different RUU's, none of them want to run.
Hi,
I unlocked my desire with HTCDev so i have to flash the boot.img file every time i install a rom with a different kernel.
I was wondering if there another way, without connecting the phone to the pc, to flash this file.
I'm afraid not but i would like to be sure !
Nope, afaik not
There is a test feature on Sensation in 4EXT recovery, that allows doing it, activating bootloader upon reboot in some way.
I'm not sure if 4EXT recovery for Desire S has the same feature. Worth checking.
In any case, that's your only hope. The other way would be to relock, downgrade and S-OFF, to avoid all this unnecessary mess of flashing boot.img.
That feature doesn't work on desire s .
So the only way is via a pc using fastboot
Tapatalked from a Desire S waiting for Kernel 3 sources. WAKE UP HTC!!!!!!
Hi, Noob here!!!
I've been trying to install a custom ROM onto my HTC desire s , 2.00.0002, 3 branded device for 2 days now.
Super one click sticks at stage 7, tried all the deselect and reselect debugging fixes.
Done the HTCdev unlock, thinking this would help.
Tried to downgrade to use revolution, done all the zergRush and misc_version commands but nothing happens when trying to change version, still had $ in command line instead of #
I've installed Clockworkmod and can boot into recovery, have backed up, deleted and formatted and recovered succesfully.
My main question is.....Can I flash CyanogenMod without rooting?
if so, what other roms can I flash via clockworkmod?
If I have to root...how do I manage it? because I've been right round 3 circles of the net and these pages trying to find an answer!!!
Hope someone can help.
The guides here are really detailed. If you can't follow them - I suggest you leave the phone as is until you can, since you're likely to cause way more damage going down the road. And in the meantime, read the guides until you figure out what things do.
Hurley71 said:
Hi, Noob here!!!
I've been trying to install a custom ROM onto my HTC desire s , 2.00.0002, 3 branded device for 2 days now.
Super one click sticks at stage 7, tried all the deselect and reselect debugging fixes.
Done the HTCdev unlock, thinking this would help.
Tried to downgrade to use revolution, done all the zergRush and misc_version commands but nothing happens when trying to change version, still had $ in command line instead of #
I've installed Clockworkmod and can boot into recovery, have backed up, deleted and formatted and recovered succesfully.
My main question is.....Can I flash CyanogenMod without rooting?
if so, what other roms can I flash via clockworkmod?
If I have to root...how do I manage it? because I've been right round 3 circles of the net and these pages trying to find an answer!!!
Hope someone can help.
Click to expand...
Click to collapse
Since you have already been able to install CWM recovery, means that your device is already rooted? Check whether you have SuperUser installed, download the free version of Titanium backup and run the app once, it will tell you whether or not you are rooted. If it is, then I suggest you to follow the link below to downgrade and S-OFF your device (since you already unlocked it using HTCDev anyway).. Or you can stay S-On but i'm afraid you need to use your PC to flash the boot.img everytime you flash a ROM..
If it's not rooted, then try to root it with the same link below.. HTCDev unlock is different with root..
But locked down to 3 network is another thing, I'm afraid you need to pay to get it carrier-unlocked..
mongox7 said:
Hi,
I unlocked my desire with HTCDev so i have to flash the boot.img file every time i install a rom with a different kernel.
I was wondering if there another way, without connecting the phone to the pc, to flash this file.
I'm afraid not but i would like to be sure !
Click to expand...
Click to collapse
Try to follow this thread to downgrade, I was in the same situation like you before, and did almost all the downgrade threads but only this works out:
http://forum.xda-developers.com/showthread.php?t=1318919
Hurley, there are two methods to exploit Saga. Try both. For me, zerg method works after fail trying the other method. I think you need to relock it first if you root using htcdev. ( am not remember the steps )
After root, downgrade to the earliest RUU, yes, im on asia region, but i used euro ruu, it works. Confirm your hboot downgraded to 98 after flash ruu. Then, go on to revolutionary. S-Off for good
All guides can be found on Index Thread, at HTC Desire S Development forum. ( im on phone, cant give links )
Sent from my HTC Desire S CoolDroid v6.0 via XDA Premium
anazhd said:
Hurley, there are two methods to exploit Saga. Try both. For me, zerg method works after fail trying the other method. I think you need to relock it first if you root using htcdev. ( am not remember the steps )
After root, downgrade to the earliest RUU, yes, im on asia region, but i used euro ruu, it works. Confirm your hboot downgraded to 98 after flash ruu. Then, go on to revolutionary. S-Off for good
All guides can be found on Index Thread, at HTC Desire S Development forum. ( im on phone, cant give links )
Sent from my HTC Desire S CoolDroid v6.0 via XDA Premium
Click to expand...
Click to collapse
M'I the only one that get this feeling like people stop hitting the thanks button?!
For example this answer!
It does deserves thanks!
When i has S-OFF must i flash the Boot.img still manualy?
Gesendet von meinem HTC Desire S mit Tapatalk 2
Specimann said:
When i has S-OFF must i flash the Boot.img still manualy?
Gesendet von meinem HTC Desire S mit Tapatalk 2
Click to expand...
Click to collapse
no just flash zip file .
Nothing hard here. I've flashed 4-5 roms up to now. All running without a hiccup. Here's how you do-
Extract boot.img from the rom you are flashing
Put adb.exe, fastboot.exe, adb.dll and boot.img in a folder
Flash everything normally through recovery
And when it's done DON"T REBOOT just power off
Open up cmd, run as admin and go to your folder( cd c:\folder_name
type adb reboot bootloader
And finally fastboot flash boot boot.img
Everything should be okay.
First off here's what I'm working with:
Rogers HTC One X
Cyanogenmod from http://forum.xda-developers.com/showthread.php?t=2205183
Recovery - TWRP 2.5
Hboot - 2.14
radio - 0.23a.32.09.29
Rooted - I don't think so
SuperCID - 22222222
S-OFF - No
Lock status - Unlocked with HTCDev after SuperCID
Story time:
After deciding to install cyanogenmod on the weekend I've run in to a myriad of issues. I was able to unlock, flash CWM recovery, and install Cyanogen fairly easily, but I ran into the issue where the touch screen doesn't work.
What I've done:
I've found the fix detailed here: http://forum.xda-developers.com/showthread.php?t=2159863, but have been unable to get all the prerequisites going. From the screen fix thread linked above I need to be rooted, s-offed, and superCIDed.
I believe I got the superCID working by following the steps in this post: http://forum.xda-developers.com/showpost.php?p=41482419&postcount=2 and fastboot oem readcid returns 22222222
After that I was unlocked before but locked and relocked with a new unlockcode from htcdev
For rooting, I've looked at the methods listed under Root on http://forum.xda-developers.com/showthread.php?t=1671237, but I'm not too sure where to find which firmware I'm on. That would be the version of cyanogen would it not. I've tried the x-factor method using All-In-One Toolkit from http://forum.xda-developers.com/showthread.php?t=1952426 to no avail, as well as SuperSU from http://forum.xda-developers.com/showthread.php?t=1673935 and this one: http://forum.xda-developers.com/showthread.php?t=1644167, but I don't think any method has worked so far.
In order to use S-Off I'm pretty sure you need to be rooted, so it of course it didn't work, what made me think I wasn't rooted was when I was going through the Facepalm S-Off guide here: http://forum.xda-developers.com/showthread.php?t=2155071 when I ran "adb shell su -c "/data/local/tmp/soffbin3" it would just me the error su: not found, which means your not in as root according to: http://forum.xda-developers.com/showthread.php?p=38278577#post38278577
I've also tried going back to stock using the RUU RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe from http://ruu.androidfiles.org/getdown...9.28L_10.103.32.24L_release_268972_signed.exe, but when I run it I get error 99: Unknown Error, and I if I look in the log it creates it says error 44 HBOOT mismatch. I'm running after relocking, and I've tried just grabbing the rom.zip from %temp%, extracting it and flashing the boot and system imgs, but it says the system.img is too big.
At this point I'd just like to get my phone to work. If I can get it with CM that'd be cool, but stock would be good too. Any help would be appreciated.
Thanks!
In cyanogenmod you have to allow adb root access in developer options.
To ruu without s-off you need to change your cid back to the default but you will brick if you update to 3.18 after. Best to s-off since you changed your cid.
Sent from my Sony Tablet S using xda app-developers app
exad said:
In cyanogenmod you have to allow adb root access in developer options.
Click to expand...
Click to collapse
The touchpad doesn't work in cyanogenmod though, that's the root of the issue
exad said:
To ruu without s-off you need to change your cid back to the default but you will brick if you update to 3.18 after. Best to s-off since you changed your cid.
Click to expand...
Click to collapse
I was trying to RUU before changing CID, but was running in to "FAILED (remote: 44 hboot version check fail)", when running the RUU mentioned in the OP
Ah I see the ruu must have had an older hboot version than the one on your phone. You cant downgrade firmware without s-off.
To fix your issue you will need to flash a sense rom and then s-off and then downgrade your touchscreen firmware. Then you can flash whatever evita rom you like.
Sent from my Sony Tablet S using xda app-developers app
exad said:
Ah I see the ruu must have had an older hboot version than the one on your phone. You cant downgrade firmware without s-off.
To fix your issue you will need to flash a sense rom and then s-off and then downgrade your touchscreen firmware. Then you can flash whatever evita rom you like.
Click to expand...
Click to collapse
Thank you very much!
I flashed the Sense build from http://forum.xda-developers.com/showthread.php?t=2293032 and was then able to S-Off. After that I was able to down grade the touchpad firmware and install cyanogenmod.
Thanks again for pointing me in the right direction
:victory:
Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...
Ayahuascaa said:
Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...
Click to expand...
Click to collapse
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.
watameron said:
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.
Click to expand...
Click to collapse
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.
Ayahuascaa said:
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.
Click to expand...
Click to collapse
What HBOOT version do you have?
Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.
redpoint73 said:
Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.
Click to expand...
Click to collapse
ViperXL JB
and my hboot is 2.14
Ayahuascaa said:
ViperXL JB
and my hboot is 2.14
Click to expand...
Click to collapse
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.
exad said:
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.
Click to expand...
Click to collapse
Hmm.. I could have. I did it last night after two hours of frustration.
And I just did that to a new install of Nocturnal's rom, but with no luck. It still just hangs at the HTC dev warning screen. I'm going to try re downloading the ViperXL rom and hope I just had a bad copy..
heh. I did that without thinking last night and spent an hour trying to reverse the damage I did. Not only did I have s-on, but my cid was still "1111111".
./
Androidfilehost is only giving me ~50Kbps, so viper's rom has 3 hours left,
but Cleanrom is almost done.
Is there anyway to s-off the evita without booting into an os?
If not, can someone point me to a thread explaining how to manually s-off?
It seems that it's the cause for all this trouble I'm having and I've never had to do manually.
Thank you everyone for your help,
my phone still doesn't have a working os but I do feel like I'm getting somewhere.
Edit: How many of you have had problems installing roms with twrp 2.5.5.0? I'm thinking about trying 2.3.3.1. I thought this was what I flashed last night, but my touchscreen didn't work and according to exad's post I probably had the wrong one.
Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
exad said:
Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.
Ayahuascaa said:
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.
Edit: Can you point me to a link for twrp 2.3.3.1? The only thread on xda for that build doesn't have working download links
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app
exad said:
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
CleanRom boots!
Thanks again to everyone who helped and exad for the 2.3.3.1 link,
Hi everyone,
This is my very first post and I'll admit I am a NOOB.
As I've searched XDA and Google for my questions, I am really at a loss and thought I would pose my question(s) to the community.
I have a Rogers HTC One X(Evita) running CM 10.0, I am currently S-ON, with TWERP 2.3.1
I would like to install the latest CM but it would seem my HBOOT (1.11) needs to be upgraded.
My first question is if my CID is Roger001 is this similar to being SuperCID?
If so, which firmware is recommended? Which is the latest HBOOT I should upgrade to?
I guess this brings me to my next question, what exactly do I need to be able to upgrade my HBOOT?
I've seen a few walkthroughs but none mention Roger001 as CID and I'd rather not risk bricking my phone.
If you need any other information, please let me know.
Any assistance is greatly appreciated.
You definitely need to update your phone in order to flash the latest cm ROM. But, with your phone in its current state you'll brick it. You don't have SuperCID (11111111), you'll definitely need to get that first, then get s-off, then you can RUU up to the latest. Links to everything you need are in this thread.
Sent from my Evita
Thanks Tim.
I'll give that a whirl and let you know how it turns out.
Another silly question, what exactly is RUU?
Sent from my One X using xda app-developers app
RUU stands for ROM Update Utility. It basically takes your phone back to being completely stock, including recovery. The beauty of being s-off when you run an RUU is the s-off status survives the process, and so will your unlocked bootloader. So all you need to do when it's finished is flash TWRP again via fastboot, then flash your ROM via TWRP.
Sent from my Evita
Ahh
That makes perfect sense!
If I wanted to stay stock, I could?
Sent from my One X using xda app-developers app
Yeah there's nothing stopping you. Then if you change your mind it's as simple as following the steps I mentioned before.
Sent from my Evita
I haven't had a chance to try anything as of yet but I've been doing some reading, could I use the One X Att all-in-one kit 3.0.1 to obtain SuperCID as well S-Off?
I tried another apparently popular program yesterday but it didn't work, as my CID is still Roger001.
Thanks!
Sent from my One X using xda app-developers app
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Yes!
timmaaa said:
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Spoke too soon.. :S
asarrecchia said:
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Click to expand...
Click to collapse
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
asarrecchia said:
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
Click to expand...
Click to collapse
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
timmaaa said:
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps from the link you gave me, under the RUU section, as there was a guide on how to install an RUU for Rogers HTC One X.
It said to relock the phone, so, I did.
ARWizard was part of the guide.
The weird thing is, I didn't flash CM, I flashed the Rogers RUU, so, I'm not even sure how CM10 is even on my phone.
I can get to the Bootloader but I can't launch TWERP and my windows PC now doesn't recognize my phone, it says installing drivers but never does. I had HTC Sync installed in hopes that it would help, it didn't.
Is my only option to do a Factory Reset in Hboot? I've read ill lose all my info on the SD card.
Thanks
Which RUU did you run? Something has gone wrong.
Sent from my Evita
timmaaa said:
Which RUU did you run? Something has gone wrong.
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps in the below thread to help me flash the RUU
http://forum.xda-developers.com/showthread.php?t=1658929&nocache=1
I went to this site to get the Stock image:
http://forum.xda-developers.com/showthread.php?p=37227608
It's 3.17.631.2
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
I really do appreciate the help, by the way.
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
timmaaa said:
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
Click to expand...
Click to collapse
I am 2.14 HBOOT and S-off.
The problem is that while my Windows PC recognizes my phone, it doesnt load the drivers and therefore, I cant send any ADB commands.
I am not even able to go into TWERP.
How will I be able to run the AT&T if I cant push any ADB commands from my PC?
You don't need any adb commands to run an RUU, but you do need the pc to recognize the phone. I'd try uninstalling all drivers, then installing them again to see if it helps.
Sent from my Evita
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files, evita ones get the name pj83img.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
If you follow the "or" method for flashing the zip it actually should work. The better correct answer is once s-off to download/install the latest ruu available that you want and ota up from there.
twistedddx said:
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
Click to expand...
Click to collapse
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
timmaaa said:
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
Click to expand...
Click to collapse
Thanks guys.
I'll try uninstalling the phone drivers and reinstall them, hopefully, it'll allow my PC to see my phone.
Worse case scenario, if my computer doesn't load the drivers for my phone, what are my options?
What if I select factory reset from HBOOT?