I've looked everywhere for something like this, and so far no one has experienced this.
Okay, so check this out:
I've already rooted and S-Off and SuperCID and all of that, the works. Had ViperROM XL and everything. I got curious to try out KarbonRom 4.4, and tried to flash it in TWRP, didn't work obviously, blah blah blah, short story is, I RELOCKED and installed the AT&T 3.18 RUU. At that point, TAMPERED was gone, and I had RELOCKED there instead, S-Off and SuperCID persisted.
I used the WinDroid Toolkit to originally root and S-Off my Evita. I tried it again. I succeeded in unlocking the bootloader, no problems there. When I go to flash TWRP on it, it says it succeeds. Now, here's when things get weird: I go to push Superuser, and at first it gave me all kinds of hassle, saying the toolkit wasn't detecting my phone, to saying it failed and to try again in a few moments. It was only until I booted back to stock and tried pushing Superuser that it gave me a success message and began to reboot to recovery. It's here that the phone fails to do this, every time. The screen goes black, and when plugged into my PC a Found New Hardware message pops up, asking me to search for drivers for QHSUSB_DLOAD, or something or other. I'm like, "no, that's not right." So after figuring out the 2-button reset to go back to HBOOT, I try to manually boot into recovery; no dice. Same results. So basically, I cannot access any recovery. Furthermore, my HBOOT says UNLOCKED and S-Off and CID-11111111, but TAMPERED is MIA. Not sure if that has anything to do with this, but I certainly did not have this problem the first time I unlocked everything. For your information, I'm on 2.14 HBOOT, 3.18 RUU. Thanks for any points in the right direction.
First thing, you didn't need to relock your bootloader to run the RUU, having s-off means that isn't necessary. Secondly, ditch the toolkit, it's unnecessary and causing problems.
I think you're possibly a bit confused about what you need to be doing. If your end goal was to flash a KitKat ROM why were you attempting to root the stock ROM? The tampered flag is missing from your bootloader because you don't have a custom recovery installed. Exactly which version of TWRP did the toolkit say it was installing? Hopefully all you need to do is flash a working recovery, then you can flash a ROM.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now hopefully you can enter recovery.
Sent from my Evita
timmaaa said:
First thing, you didn't need to relock your bootloader to run the RUU, having s-off means that isn't necessary. Secondly, ditch the toolkit, it's unnecessary and causing problems.
I think you're possibly a bit confused about what you need to be doing. If your end goal was to flash a KitKat ROM why were you attempting to root the stock ROM? The tampered flag is missing from your bootloader because you don't have a custom recovery installed. Exactly which version of TWRP did the toolkit say it was installing? Hopefully all you need to do is flash a working recovery, then you can flash a ROM.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now hopefully you can enter recovery.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the swift reply, I'm gonna go ahead and give this a try. To answer your question, through trying to flash KarbonRom, I wiped and factory reset without backing anything up, silly, I know, but I live a little too dangerously I suppose. I tend to get to cocky with this stuff, through all the devices I've rooted and so on. After failing to flash it, I knew I was stuck, which is why I came to the conclusion the only way out was to revert to stock RUU. If there was anything else I could do, I wasn't thinking of it. In hindsight, I suppose I could have ADB Sideloaded Viper XL again. Also, I was unaware that I didn't need to relock the bootloader to install the stock RUU, this is news to me, so thank you for that. I'll reply again after trying your link.
EDIT: This worked, thank you again. You've made me wiser in the ways.
One thing I forgot to mention. The QHSUSB_DLOAD that your phone was showing up as when connected to your PC usually means that a device is bricked. So, under no circumstances should you use that toolkit ever again, because whatever it was doing wasn't good at all.
Sent from my Evita
timmaaa said:
One thing I forgot to mention. The QHSUSB_DLOAD that your phone was showing up as when connected to your PC usually means that a device is bricked. So, under no circumstances should you use that toolkit ever again, because whatever it was doing wasn't good at all.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the heads up, I'll keep it in mind. It seems the most reliable way to do this stuff is just do it yourself. I'm still green to the ways of adb and fastboot, I've always let one-clicks and toolkits do the work for me, but I'm learning that just doing it yourself is the most reliable method. Thanks again, man, your insight has always helped me out of tough situations.
Doing it yourself is definitely the most reliable method. It might seem daunting at first, but I can assure you it's totally simple, and once you've done it a couple times you'll see that. The manual way is the best way, hands down. A bonus is that it feels great to learn something and to have an extra bit if control over your device.
Sent from my Evita
Related
This may have been posted before but this just SERIOUSLY saved my ass this morning.
Only use this method if you phone will not:
Boot into your:
Recovery
ROM
Anything else besides HBOOT (hold vol. down and turn on phone)
Get an RUU from somewhere and pull the rom.zip file
Rename it to HERCIMG.zip
Put on ROOT of sdcard
Reboot to hboot as per instructions above
If you renamed it right it will say:
SD Checking...
Loading.....[HERCDiag.zip]
No image!
etc.etc.etc
then
Loading...[HERCIMG.zip]
You will see a progress bar on the upper right of the screen.
It will ask you if you want to upgrade. Press Action (trackball btn) for yes.
***YOU WILL LOSE EVERYTHING! Root/files/etc. just like if you flashed it with the RUU setup file***
After it finishes you now have a working hero again
Very helpful post. Saved me once.
Also, a tad off topic, but if you are S-OFF, you can flash the recovery only (clockworkmod tested). This might save some time vs a total reflash.
google clockwork recovery, find the 2.5.0.1 img file for the heroc. Get an android-info.txt from an exisiting HERCIMG.zip (either find one on xda in this forum, or follow OP instructions and get it from ROM.zip) and zip it along with the clockwork recovery .img file. Rename it to HERCIMG.zip and flash from hboot.
You can also create custom RUU with a clockwork recovery by replacing the stock recovery img in an HERCIMG.zip with the clockwork recovery .img, and then flashing. You will get sprint stock but with clockwork recovery instead of the stock recovery.
Just a few tips I've learned. Remember mine requires S-OFF, which is opposite of what the OP is working with.
Well this is very helpful.
BUT! Here is the issue I am now having...
My phone wont boot into android... OR recovery (stock).
I know the recovery is stock since I just flashed the RUU from the carrier.. So I am thinking maybe a corrupt partition?
Major worry I am having is I did flash the engineering spl however it is still in s-on mode (dunno why) so I cant even boot into a custom recovery to flash back the old spl. Is it possible to flash the spl with the method you mentioned? If so I will do that and then if it still doesn't boot (I know it wont btw) I will take it in store.
hexskrew said:
Well this is very helpful.
BUT! Here is the issue I am now having...
My phone wont boot into android... OR recovery (stock).
I know the recovery is stock since I just flashed the RUU from the carrier.. So I am thinking maybe a corrupt partition?
Major worry I am having is I did flash the engineering spl however it is still in s-on mode (dunno why) so I cant even boot into a custom recovery to flash back the old spl. Is it possible to flash the spl with the method you mentioned? If so I will do that and then if it still doesn't boot (I know it wont btw) I will take it in store.
Click to expand...
Click to collapse
I tried the eng-spl also to get fastboot working but that didn't seem to work either. Not sure why. I used the other S-OFF method flashed via clockwork.
This wouldn't be an issue if we could use fastboot on our phones (I always get access denied). I think the eng-spl was supposed to enable the use of fastboot.
If you think the eng-spl worked, try using fastboot to wipe your partitions. I think there was talk about this in the firerat mod thread. I don't recall the exact commands, but it's run like adb is from the command line. I think fastboot system -w erase but I could be wrong... probably best to check the firerat mod thread.
btw about your question, I am not sure if you can flash anything else via hboot other than what I tried. At least I think this is what you were asking.
Porkrinds said:
I tried the eng-spl also to get fastboot working but that didn't seem to work either. Not sure why. I used the other S-OFF method flashed via clockwork.
This wouldn't be an issue if we could use fastboot on our phones (I always get access denied). I think the eng-spl was supposed to enable the use of fastboot.
If you think the eng-spl worked, try using fastboot to wipe your partitions. I think there was talk about this in the firerat mod thread. I don't recall the exact commands, but it's run like adb is from the command line. I think fastboot system -w erase but I could be wrong... probably best to check the firerat mod thread.
btw about your question, I am not sure if you can flash anything else via hboot other than what I tried. At least I think this is what you were asking.
Click to expand...
Click to collapse
What I was wondering is if I could flash either an original HBOOT, or to put it back to S-On by the method you described.
OR....
Does the original hboot have the option for fastboot? If so then I will just bring the phone in for service
hexskrew said:
What I was wondering is if I could flash either an original HBOOT, or to put it back to S-On by the method you described.
OR....
Does the original hboot have the option for fastboot? If so then I will just bring the phone in for service
Click to expand...
Click to collapse
Well, if you are S-ON right now, you can't flash anything that isn't signed with HTC's private key I believe.
You should be able to get to fastboot via hboot menu... just boot into hboot (power off, vol dwn + power on) and see if there is an option to get to fastboot (I think it's home key? I forget). Thing is... we can't do anything using fastboot (as end users) because it's turned off. The eng-spl was/is supposed to turn that on as well as S-OFF if I understand correctly.
Since you tried the eng-spl, have you tried hooking up to USB, booting into HBOOT and then jumping to fastboot and seeing if you can do any fastboot commands?
Sadly, the only two ways I know to flash something is either via a recovery like clockwork, or via S-OFF via HBOOT. Fastboot is possible, but like I said before it seems to have been turned off..
fastboot works after you flash the eng-spl. you'll have to look for the commands to use it though. ive used it once after flashing the eng-spl just to verify it worked.
Well, I did flash the ENG-SPL like I said and I did try to use fastboot from HBOOT, however nothing ever worked except for the fact that I could see that fastboot detected it when using "fastboot devices".. fastboot reboot wouldn't even work though. It would say that it worked but it actually did not.
No biggie though, as like I said I flashed the RUU to wipe it. It still wouldnt boot but that's ok cause I got a replacement today
Awesome post, thanks. I'm tagging this should the unfortunate event happen.
hunterd13 said:
fastboot works after you flash the eng-spl. you'll have to look for the commands to use it though. ive used it once after flashing the eng-spl just to verify it worked.
Click to expand...
Click to collapse
Good info thanks. I think I might have been S-OFF via unrevoked already so maybe that is why the eng-spl didn't work for me (as far as being able to use fastboot, I still got access denied errors).
OP: glad you got it fixed the easy way
This is my saga thus far:
1. Followed the guide ... more or less. For some reason it wouldn't install CWM as PG58IMG.zip via fastboot automatically (it detected it, said it was parsing, then just went back to the menu), but I was able to install the img using fastboot flash recovery recovery.img (where recovery.img was the CWM img). Anyway, everything worked properly, I had the SuperUser app, I could use 'su' in the terminal, etc.
2. I flashed 4EXT Recovery. Also worked perfectly.
3. Played around a bit, whatever.
4. Did a backup via 4EXT.
5. I bought this phone used from eBay, so I wanted to ensure there was nothing malicious hiding in the system partition. So I used RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe, which is precisely what was installed before. That was successful too.
6. Then, when I set things up, Google started "recovering" my apps, i.e., downloading a bunch of apps I had on my old phone. I was not impressed by this. So I went to Settings > Storage > Factory Reset.
7. Then I reinstalled the RUU. I'm not sure if it was necessary or not.
Now I seem to be stuck. I'm not bricked -- I can do everything an unrooted user can do. But I'm pretty sure I'm NOT rooted. The Superuser app's gone, and when I type su in the terminal, it says "permission denied" (which is interesting, shouldn't it say it can't find it at all?). In the bootloader/fastboot, it says S-OFF. It also says **LOCKED** above that. I'm not sure whether that refers to system access (i.e., root permissions) or the SIM (phone was unlocked before). But the strangest part is with ADB. When the phone is on in normal mode, I can install apps, push/pull, etc. But within the bootloader, adb's not recognizing the device at all! What's particularly weird is that the fastboot command IS recognizing it! And when I do fastboot getvar cid, it's still 11111111. But it won't let me flash a custom recovery.
So, I seem to be stuck. It seems to be S-OFF, but I can't flash a recovery. I can't even restore my backup, since I need the custom recovery to do that!
Any ideas as to what I can do to re-root my phone?
EDIT: I'm watching a YouTube vid of the phone being S-OFF'd. When he started off, his bootloader screen looked identical to mine except it said S-ON. When he finished, it said S-OFF, but it also said **Revolutionary** instead of **LOCKED**. OK, so, if I try running Revolutionary again, will it fix things, or will it do nothing or even brick my phone? Will I have to do the S-ON procedure and then start anew?
You have s-off with a locked 1.27 hboot. That's ok, at least you have s-off so you have access. Don't worry about the "locked" bootloader! adb will not connect in bootloader. That is normal. You must use fastboot when in bootloader. As far as a recovery goes, you'll need a PG58IMG with the correct mid in order for it to flash. From bootloader:
Code:
fastboot getvar mid
You can use 7zip to extract the PG58IMG and notepad++ to view the android-info.txt. Make sure your mid is listed... If it's not listed then you can add it, pack it all back up, put on root of sd and flash through bootloader.
Once you have your recovery you will have to flash superuser to regain root access.
I had this exact issue the other day on a gingerbread RUU, to fix it I ran revolutionary even though I was s off already, then rebooted the phone, and flashed this recovery from bootloader
http://db.tt/CElPBgty
This is the only one I managed to get to work, others just said 'parsing' then did nothing
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Hey all,
So tonight I attempted to install the Unofficial AOKP Jelly Bean posted here: http://forum.xda-developers.com/showthread.php?t=1862156
Before doing that, I followed the instructions to Unlock, Recovery, and Root my One S here: http://forum.xda-developers.com/showthread.php?t=1583427
After following those instructions, I then followed the instructions for AOKP Jelly Bean however my sdcard couldn't be mounted and the phone was in a boot loop if I didn't boot into fastboot by holding down the volume - and power buttons.
I attempted these instructions below however I couldn't get a stock recovery flashed.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Click to expand...
Click to collapse
Still caught in the reboot loop, I relocked and tried to run an RUU file found here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html
I was able to successfully re-lock the phone however every time I try to run the RUU file it comes back with an error about 3-5 minutes into the process.
At this point, my phone boots into fastboot. At the top I have "Tampered, Relocked, Security Warning." My HBOOT is 1.14.0004 and my Radios is 1.08ts.50.02.16
I would appreciate any help if there is a solution. Thank you for your time!
Update: Not sure if this is helpful or not, but whenever I try to do something with The All in one toolkit the cmd window says device not found. Also, when I try to boot into recovery from fastboot, I get a green downward and circular arrows before getting the red triangle and exclamation point.
Update: Running the RUU mentioned above fails at the Signature stage and the cmd prompt when trying to write recovery returns "signature verify fail"
Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app
whozilla said:
Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I am pretty sure I am S4 (tmobile USA). I am on a windows 7 home build, and the drivers should be installed (at least, I could use HTC sync before all of this). I'll definitely try again tonight. If anyone has any other suggestions they would be much appreciated!
Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app
whozilla said:
Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help!
Here are my results:
HTC Sync is not running. Fastboot devices returns a device ID so that seems good. When trying to flash a stock recovery (that I got on this forum somewhere, but can't remember where) it sends it ok but I still get "remote: signature verify fail"
I unlocked the device and flashed TWRP 2.2.2.0 with the all in one tool kit. This put me back into the boot loop mentioned above. Once I manually got back into the bootloader and selected recovery, I was able to get into the TWRP recovery. At this point, I am kind of worried about doing anything. I would like to be able to push AOKP Unofficial JB if at all possible. Any further guidance would be appreciated!
Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville
usaff22 said:
Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
It is clear to me that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!
You have to fastboot push the AOKP zip through the bootloader I think.
Sent from my locked, tampered ville
Veritas327 said:
It is clear to fme that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!
Click to expand...
Click to collapse
Just like the post above mine says, you have to adb push the file onto the sd card. I'm not to familiar with TWRP (using it actually got me into a bit of a dilemma) so I only know the process for CWM. If TWRP is anything like CWM then you have to be in recovery to adb push and have sdcard and system set to "unmont". It's pretty easy and there's a couple threads explaining how to do it. The command basically is :: adb push romname.zip /sdcard/romname.zip:: Note the space before "/sdcard" I'dpn't know if this ill help you or if you've solved your problem already but this is just my 2 cents, good luck!
Sorry for my late reply; I was rushed to the ER last night in excruciating pain. Looks like I'll be dealing with a kidney stone over the next few days.
So far, I have tried to push AOKP through fastboot. ADB says "no devices found" and when I type adb devices, I get "List of devices attached" and nothing under it. However, when I type fastboot devices, I do get a device ID. As of now, I am downloading the TWRP 2.3 recovery and will try to sideload with adb with that.
Update:
I was able to successfully install TWRP 2.3 and adb sideload the AOKP zip file. The phone then went back into a reboot loop, and I was able to get into recovery to install the .zip. The phone then rebooted, showed the HTC with red text screen very briefly, went to black, showed the HTC with red text screen again, went black, and now the aokp boot animation is repeating over and over. It has been doing so for about 5-7 minutes. I haven't yet installed gapps as mentioned in the AOKP post (I'm honestly not even sure what that is). Where should I go from here?
As a side note, the phone is plugged into power though the LED is not lighting up. It was at 98% when I flashed the .zip, but I obviously don't want it to die on me. Should I turn the phone off or is it still charging?
Veritas327 said:
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Click to expand...
Click to collapse
The newer hboot versions (1.13 and up) don't let you flash boot images in recovery, even if it reports success.
So there is technically no difference, except fastboot always works and recovery depends on hboot version.
Did you fastboot flash the boot image that comes with your rom?
-Jobo
Edit to add: So it seems that following the recipe in your post #1 did in fact make your sdcard mountable again, or did you do something else as well for that?
Fixed!
I ended up flashing the boot.img with fastboot and then going into recovery, factory resetting and then re-installing the rom (and gapps which I now know stands for google apps). I'll be playing around with the ROM but at least I have a working phone again!
I think, in the end, it came down to my sd card not being mounted and my lack of knowledge about how to fix it.
Hey, First post and it going to be about whether my phone is bricked for good or not. =/ I'd really appreciate some help as I've clearly not researched enough into this.
-My Rogers HTC One X had previously been rooted and unlocked to hboot 1.09 with cyanogenmod.
-I wanted to install Android Revolution HD, so i figure I needed an hboot update. I went ahead and flashed the phone with the 'firmware.zip' in 'OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip' (HUGE MISTAKE)
-After flashing, I tried to install Android Revolution HD but it had crashed mid way.
-Im able to access hboot and Im also able to go into fastboot and recovery (recovery-clockwork-6.0.2.8-evita).
-Rebooting the phone results in a blank screen after the HTC loading screen. So no adb.
My hboot shows this:
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO - 23a.32.09.29
OPENDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012,18:37:14:-1
I've tried locking it, flashing it with PJ83IMG.zip but it says: 'FAILED (remote: 44 hboot version check fail)'.
I've tried running 'RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe' but it gets half way and has Error 155.
Can anyone recommend a rom that will work in this configuration?
Any chance that I can still get S-off on the phone?
Any way to recover the phone at all? Just to be clear, I've flashed my Rogers phone with a Rogers OTA.
Thanks!
Dude you are ****ed! no way to recover from that!..
J/K
All joking aside.
Download TWRP 2.3.3.1 It is compatible with the most ROMS and isn't buggy. Check MD5 and fastboot flash recovery twrprecovery.zip <-- replace with actual zip file name.
then fastboot erase cache
Boot to recovery
Wipe cache dalvik system and factory reset and flash any ROM designed for evita.
Because you're S-ON and on an HBOOT >= 1.14, you'll also have to extract the boot.img from the rom and flash it separately "fastboot flash boot boot.img", unless otherwise indicated on the ROM's thread, usually in the OP.
As a side note, you shouldn't have rooted, you have a lot of reading to do.
Nevermind
Sent from my One XL using XDA Premium
Also that Rom is for the international HTC one x if the install hadn't crashed it would have bricked your phone
Sent from my HTC One X using Tapatalk 2
exad, Thanks for taking the time to write up the instructions for me. I've been able to get the phone to boot again. =) I do have some reading to do haha.
Given whats already done, did I put my phone in a situation where I've limited myself for future modding? What I'm really wondering is if I should be trying to get S-off so I can downgrade my firmware? Will I run into any issues with just running the phone as it is?
certitude said:
exad, Thanks for taking the time to write up the instructions for me. I've been able to get the phone to boot again. =) I do have some reading to do haha.
Given whats already done, did I put my phone in a situation where I've limited myself for future modding? What I'm really wondering is if I should be trying to get S-off so I can downgrade my firmware? Will I run into any issues with just running the phone as it is?
Click to expand...
Click to collapse
If you are going to s off, no need to really downgrade. This because you are turning security checks off. So it actually makes things a bit easier, and decreases the chances of bricking. I'm s off and on hboot 1.14 and was able to flash plenty of roms without a computer.
Sent from my Carbon-ize Evita using xda-developers app
You're not limited. You just need to fastboot flash boot boot.img any time you flash a ROM. If you're not a flashaholic like most of us, it's no big deal.
I wouldn't RUU with S-ON though, even though you didn't supercid, I bricked without supercid running an RUU after rooting.
So, if you don't plan to RUU you don't need to S-OFF either.
If you do intend to S-OFF, since you didn't need to supercid to unlock your bootloader, you would need to hex edit your CID to 11111111 if you wanted to S-OFF.
If you have any other questions, don't hesitate to ask but I suggest reading the stickies in all the sections. Good Luck
Thanks for the info everyone. I'll be keeping that in mind.
exad said:
Dude you are ****ed! no way to recover from that!..
J/K
All joking aside.
Download TWRP 2.3.3.1 It is compatible with the most ROMS and isn't buggy. Check MD5 and fastboot flash recovery twrprecovery.zip <-- replace with actual zip file name.
then fastboot erase cache
Boot to recovery
Wipe cache dalvik system and factory reset and flash any ROM designed for evita.
Because you're S-ON and on an HBOOT >= 1.14, you'll also have to extract the boot.img from the rom and flash it separately "fastboot flash boot boot.img", unless otherwise indicated on the ROM's thread, usually in the OP.
As a side note, you shouldn't have rooted, you have a lot of reading to do.
Click to expand...
Click to collapse
I got a Telus HTC one x yesterday. Spent all day reading about rooting etc and finally went ahead and did it. The unlocking part went without a hitch. I then went to install the clockwork recovery and I think I used an outdated one, because after I did it, it wouldn't boot into recovery. I could get into the bootloader, but checking anything else it wouldn't do anything. At that time I was still able to boot up my phone as normal. I then saw an updated clockwork recovery and tried that one, and it still wouldn't respond when I clicked on recovery. Now I can't do anything except get into the bootloader. My screen says the exact same thing as the original poster in terms of
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO - 23a.32.09.29
OPENDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012,18:37:14:-1
I'm so upset right now. I read your instructions on what you suggested to the OP but theirs was Rogers and mines Telus, and I never did have a custom ROM on there, and I don't have a clear cache option, just a 'clear storage'
Even selecting the 'reset phone' doesn't work. I'm ready to cry lol. I don't want to touch anything without guidance so I don't screw it up even further. I know this is the rogers forum but it's what came up when doing a google search.
Please help me. Please tell me this can be fixed. :crying:
Don't use CWM, use TWRP instead. Find version 2.3.3.1 at goo.im (just Google TWRP 2.3.3.1 evita download). Check the md5 of the download is correct. I'm assuming you have fastboot on your pc.
Put the TWRP recovery.img in your fastboot folder
Boot phone into bootloader, wait for it to say "fastboot usb" on the screen of your phone
Open a command prompt in that folder on your pc
Type in the following command:
fastboot flash recovery openrecovery-TWRP-2.3.3.1-evita.img (whatever the name of the recovery image is, I think that's right)
It will now write the recovery to your phone, wait for it to finish, it should only take a few seconds
Now type the following command in:
fastboot erase cache
fastboot reboot-bootloader
Now you should be able to disconnect your phone and flash superuser.zip in your new recovery and have root access.
Sent from my HTC One XL using xda premium
omg!!!!! TY TY TY TY TY!!!!!!!!
It flashed into recovery!!!!!
I can't find where my superuser went...is there a way I can get it onto my phone? At this point I'm so nervous about screwing anything up that I'm afraid to play (which is rare for me as I'm normally quite good at all this stuff)
Do I really need the superuser? I'm planning on putting the ViperXL 3.2.7 rom on my phone. Can I just go straight to installing the rom?
I know where I went wrong now though. I used the international root instructions and not the AT&T ones as I assumed since I was Telus instead of Rogers or AT&T that that was the one I needed. Ugh! I feel like such an idiot!! I had android for quite a while then went to iphone for a little while (mistake) and had gotten so good at doing everything with those and forgot most of the steps involved with rooting android and the terminology. I'm happy to be back home with android!
You can just go ahead and flash ViperXL, that is pre-rooted so you'll be good to go. I just assumed you had a ROM running, so flashing the superuser zip would have just given that ROM root access.
Now, just make sure you stay here in the One XL (AT&T) forum. Make sure you only flash ROMs from here, because flashing one of the International ROMs can brick your phone, and we don't want that.
Sent from my HTC One XL using xda premium
I will be staying here!! lol
Just to be sure I have this correct...
I downloaded Viper and the boot img.
I'm going to go back to my cmd prompts, install the boot img
I'm getting hung up with understanding how to place the zip on my phone storage...My computer isn't showing it as being a separate drive.
I keep getting 'failed' errors with everything in TWRP. If I try to mount as USB storage, my computer says it needs to be formatted...
When I try to do anything else it shows up with failed.
Ok here's what you'll need to do:
Boot your phone into the bootloader (hold power and volume down key together, release power after a second but keep holding volume down until you're in bootloader)
Select recovery
Once recovery boots up, connect to pc with usb cable, select mount in recovery menu, then select mount storage
Your phone should now show up on your pc as a drive, copy the entire ROM zip to your phone
Once it's copied, do eject and safely remove the drive from your pc, and hit unmount on your phone screen
Hit the home button (little house on bottom left) in recovery
From main recovery select wipe, once in wipe menu you must wipe cache, dalvik cache, factory reset, and system
Once you've wiped all those, hit the home button again
Select install from the main recovery menu, then find the ROM you previously copied to your sd card and select it, then swipe to install, let the install finish (please note: if you're installing viper, it will have a few options to select during the install, select the ones you want. But right at the end of the install process there will be a checkbox for "reboot device now" and it will be checked, make sure you uncheck that before you hit finish/done)
Now you'll see two options, wipe cache/dalvik is one, do that, once that's done hit the home button again
From the main menu, hit reboot, and then bootloader, your phone will now boot back into the bootloader and fastboot usb should show up in red text on your screen if your usb cable is still connected
Now back to the pc, Copy the boot.img from the ROM zip and place it in your fastboot folder
Make sure you're connected with usb and fastboot usb is showing on your phone screen
Open a command prompt in your fastboot folder on pc and type in:
fastboot devices
You should see a device number return in the command prompt, if that shows up you're connected properly, so now type in the following command:
fastboot flash boot boot.img
This will flash the boot.img to your phone, let it finish
Once that's done you can reboot and you should be able to reboot into your new ROM
Sent from my Evita
It's not mounting...just keep getting a message from my computer that the drive needs to be formatted before I can use it...
btw, ty for all your help on this you've been amazingly helpful!
You may have corrupted your sd card. You'll have to format it, which means you'll lose all your data off it unfortunately. Do that first and then start again.
Sent from my Evita
It worked!!!!!! It booted up into Viper!!!!! TY a million times over!!!!!!!!!!
Awesome, so glad to see you got it going :thumbup:
And no problem at all, my pleasure, this is what XDA is all about.
Sent from my Evita
I'm posting this in a single thread to minimize clutter.
I recently ran Easy Ace Root tool as instructed on my inspire. The bootloader unlocked, CWM flashed, but there was an error during superuser flash.
After a reflash of superuser things looked okay, but superuser began not responding. I re-flashed superuser twice in attempt to fix it using the Easy Ace Root Tool.
EDIT: I have discovered that superuser will only function with "USB debug mode" enabled. I've tried it on and off several times, and each time it malfunctions but function returns without a problem.
The backup I have been restoring seems to work because it was created with the debug mode enabled. Took a while to see it.
Second, CWM started to exhibit the "power off, charge" recovery bug where CWM opens.
Last, I attempted to install/flash 4ext Recovery Touch twice to address the CWM bug. Both times it hung at "flashing recovery" (approx 20 mins. both times). Eventually, it indicated that 4ext was installed. However, booting into recovery shows that I still have CWM. I used two different versions (RC8 & RC 7) in the attempt.
I'm now using the restored and working ROM. Solutions to the superuser debug issue I haven't seen posted
The failure to flash 4ext is troubling.
Questions
1. Could these issues be related? Or, what should I be looking for?
2. The recovery issue seems to be the most important. What might be the cause of 4ext to fail in this manner?
3. Can the Easy Ace Root Tool be rerun on the unlocked bootloader, and would that fix anything?
4. Is there reason to worry about flashing with CWM?
I see a number of possible solutions, the main one is to flash a new ROM, which I have already downloaded a couple, but doesn't adress the recovery problems.
The issue with CWM and 4ext leave me less than confident in using it to flash with, although CWM seems okay. The other item is that some ROMs indicate that S-off in required, but many of the threads are a couple years old.
5. Is it correct that S-off is not required to flash ROMs (I read it somewhere)?
I found an answer: NO, YOU DON'T NEED S-OFF TO FLASH ROMS....
Solving the issues are good lessons
Stock AT&T ROM
Android 2.3.5, Sense 3.0
Bootloader screen indicates-
UNLOCKED
S_ON
I know that's a lot for one thread but I'm just looking for a direction and I'll do the search.
If anyone has suggestions, directions, or ideas fire away.
Thanks
I think the fact that you are still S-ON is causing problems with the recovery flashing, since S-ON basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-ON still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)
Evil_ryan said:
I think the fact that you are still S-OFF is causing problems with the recovery flashing, since S-OFF basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-OFF still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)
Click to expand...
Click to collapse
Thanks, I think you meant to say the fact that I am still S-ON? The S_ON part shouldn't be an issue from all that I've gathered. In fact, that's how I have CWM. The Easy Ace Root Tool does CWM, with an unlocked bootloader S_ON. Nothing I have come across states that S_OFF is required to flash 4ext recovery.
Other noobs might find this other thread useful as there is some info and links to recovery images. http://forum.xda-developers.com/showthread.php?p=22489317#post22489317
No I haven't tried the fastboot yet. That is an option, I've got it and adb setup on my computer already. I have looked at AAHK, but as it says its no longer supported, and I don't think I need of S_OFF. Taking it slow to sort out the problems so I don't do sumthin stooopid.
How are you flashing 4ext? From fastboot?
Right, S-ON, that's what I get for writing this at 12 AM.
Don't bother with AAHK, it's discontinued, and even if you still had a copy it couldn't download the necessary files.
bananagranola said:
How are you flashing 4ext? From fastboot?
Click to expand...
Click to collapse
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.
Cremnomaniac said:
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.
Click to expand...
Click to collapse
Try doing it from fastboot.
bananagranola said:
Try doing it from fastboot.
Click to expand...
Click to collapse
I thought that would be next.
Can you confirm for me that the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1848846 are correct for the Inspire 4G?
It's the EVO 3D forum. And I have some other links to using fastboot I'll check before doing it.
Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.
Evil_ryan said:
Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.
Click to expand...
Click to collapse
Okay, great. This is the only recovery .img that I have found 4EXT-recovery-2.2.7_RC5.img - 3.33 MB
If I install the 4ext recovery Updater after flashing it should work okay?
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?
Cremnomaniac said:
If I install the 4ext recovery Updater after flashing it should work okay?
Click to expand...
Click to collapse
Probably. But I don't think it really matters, since if you can flash a recovery using fastboot, you can do everything that 4ext updater otherwise would.
Cremnomaniac said:
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?
Click to expand...
Click to collapse
See above.
If 4ext doesn't work, you can also try CWM and TWRP (TeamWin Recovery Project). I use the latter with my Inspire 4g.
I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.
bananagranola said:
I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.
Click to expand...
Click to collapse
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?
Cremnomaniac said:
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?
Click to expand...
Click to collapse
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.
bananagranola said:
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.
Click to expand...
Click to collapse
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?
Cremnomaniac said:
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?
Click to expand...
Click to collapse
No.
bananagranola said:
No.
Click to expand...
Click to collapse
Solved the 4EXT flashing issue. Looks like 4ext flashed okay with fastboot, and the 4EXT Recovery Control works. Rebooted into recovery a couple times just to be sure. That kills 2 birds the CWM bug and the recovery flash.
Thanks for the help and suggestions all.
Some notes from a noobs experience -
Setting up ADB and Fastboot is very easy.
If your cautious as I am run some basic commands in ADB and Fastboot that won't do damage [devices, reboot, reboot-bootloader, etc.]
If you get "error: cannot load 'recovery.img" make sure you navigate to folder that recovery.img is located. Then run "Fastboot flash recovery [Filename]." Even though I set system variables on my desktop to point to adb and fastboot, it won't find the recovery image if you start from the wrong directory in terminal (i.e., C:\)
If you're in ADB and you use the command "adb reboot-bootloader" it will boot the device straight to "Fastboot USB".
Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.
bananagranola said:
Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.
Click to expand...
Click to collapse
Thanks for the reminder. I just spent an hour looking at 4EXT "smartflash no available". I hav some links for doing fastboot flash of the boot.img. I think I'm good there.
One question from my OP remains. Superuser only works (i.e., grants root access) when I have USB debug mode selected. When it's off superuser says the app (e.g., Titanium BU) is granted permission but just hangs until I force close it and re-enable USB debug. i can't find anything on this problem.
Is it an issue to run my phone in USB debug mode all the time? Or, any clue to the problem?