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
Related
Okay,
New sensation xe (Euro), CWM recovery, unlocked but not S-Off. Will only boot to HBOOT, Recovery, and its favorite, JuopunutBear. This thing will not go away. Happened when I tried the "Wire Hack". Phone boots to it unless I boot to HBOOT. Tried ....
Not ncessariliy in this order:
Wiping phone with 3 different wiping programs.
ControlBear.exe -r
Fastboot - most options
Flashing 2 different ROMs
Using Andriod Commander manually deleted every file and folder on the phone.
Others that i can't rememmber.
Two questions:
1. Is there somewhere on the file system that is totally hidden from wiping programs?
2. In the beginning, before I new what I was doing (1 week ago), I renamed a lot of files to update.zip. recovery.zip, PGxxIMG.IMG. Could I somehow be loading Juopunutbear back to the system when I reboot? If so, remedy?
Any help would really be appriciated, as I have spent days trying to work this out on my own.
Thanks!
JuopunutBear REMOVED FIXED
I got the same problem i check online and i was supposed to keep trying with the cable until it was successfull. I didnt wait that long and did exactly what you did, went to recovery and formated everything installed roms etc, none of which worked. Now as a result of all this JuopunntBear will definantly not work.
HERE IS HOW I FIXED AND GOT IT BACK UP AND RUNNING.
While trying the live CD method I downloaded a .zip file with contained the original unrooted Sprnint ROM and renamed it to PG86IMG.zip(~400mb) and placed it in the root directory of the SDCARD using CWM recovery card mount and went to fastboot menu which looked for this file and loaded the original sprint.
BEFORE YOU COPY THE FILE TO THE SD CARD YOU MUST RELOCK YOUR HBOOT you probably unlocked it while rooting the phone at some point. because if the hboot is UNLOCKED then the update will not extract and apply.
SO YOU MUST RELOCK BY: going to fast boot menu and sending the following relock command using command prompt in windows command prompt: fastboot oem lock
(this is similar to what is in the root instructions. google and find the files need to root the phone so that you can send the fastboot oem lock command (or anyother command in fastboot mode) to the phone using command prompt)(you can also use these to root the phone again once its up and running)
if in the process you cant get to the CWM recover etc you can use the command prompt and send unlock hboot and send" fastboot flash recovery xxxx.img " command to install the recovery console and access the SD card( root instructions and files http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-evo-3d-2-08-651-2-and-later-htc-unlock-method/).
After this your phone will be just as if it was on the first day you got it.
HERE IS THE FILE I RENAMED AND LOADED. THERE ARE INSTRUCTIONS TO THIS
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209 <-- THIS IS THE FILE WHICH WILL FIX EVO3D CDMA FIRST FILE ON THE PAGE
http://forum.xda-developers.com/showthread.php?t=1563342 <--- i was following these
riptide355 said:
Okay,
New sensation xe (Euro), CWM recovery, unlocked but not S-Off. Will only boot to HBOOT, Recovery, and its favorite, JuopunutBear. This thing will not go away. Happened when I tried the "Wire Hack". Phone boots to it unless I boot to HBOOT. Tried ....
Not ncessariliy in this order:
Wiping phone with 3 different wiping programs.
ControlBear.exe -r
Fastboot - most options
Flashing 2 different ROMs
Using Andriod Commander manually deleted every file and folder on the phone.
Others that i can't rememmber.
Two questions:
1. Is there somewhere on the file system that is totally hidden from wiping programs?
2. In the beginning, before I new what I was doing (1 week ago), I renamed a lot of files to update.zip. recovery.zip, PGxxIMG.IMG. Could I somehow be loading Juopunutbear back to the system when I reboot? If so, remedy?
Any help would really be appriciated, as I have spent days trying to work this out on my own.
Thanks!
Click to expand...
Click to collapse
riptide355 said:
Okay,
New sensation xe (Euro), CWM recovery, unlocked but not S-Off. Will only boot to HBOOT, Recovery, and its favorite, JuopunutBear. This thing will not go away. Happened when I tried the "Wire Hack". Phone boots to it unless I boot to HBOOT. Tried ....
Not ncessariliy in this order:
Wiping phone with 3 different wiping programs.
ControlBear.exe -r
Fastboot - most options
Flashing 2 different ROMs
Using Andriod Commander manually deleted every file and folder on the phone.
Others that i can't rememmber.
Two questions:
1. Is there somewhere on the file system that is totally hidden from wiping programs?
2. In the beginning, before I new what I was doing (1 week ago), I renamed a lot of files to update.zip. recovery.zip, PGxxIMG.IMG. Could I somehow be loading Juopunutbear back to the system when I reboot? If so, remedy?
Any help would really be appriciated, as I have spent days trying to work this out on my own.
Thanks!
Click to expand...
Click to collapse
i had same problem, i took the sdcard out of my phone and put it in my moms galaxy note and formatted, then i put it back in my phone and started it up normally so i get pounutbear then i ran controlbear again on my computer and did the wire-trick right from then everything went as it should
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'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
I'm having a problem with my One X and returning it to stock. I've been rooted with S-ON for quite some time now and had the Viper ROM installed. Now it's time to trade it in to Amazon and I wanted to return it to stock and hopefully remove the tampered text. I seem to have gotten myself in to a pickle though and I'm stuck at the bootloader.
I've been using the WinDroid Universal HTC Toolkit to install stuff, I have the unlock.bin file from HTC, and I've been able to communicate with the phone through my Windows 7 computer no problem. But after the last attempt I relocked the phone and not I'm stuck. Here's what it says on the bootloader screen:
*** TAMPERED
*** RELOCKED
*** Security Warning
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
Using the WinDroid kit it shows that it successfully unlocked the bootloader and loaded TWRP, but since it's in fastboot, WinDroid doesn't recognize the phone model and won't let me send any files to it though. When I reboot the phone in to recovery, it returns me to the bootloader.
Anyone have any advice?
First piece of advice: ditch the toolkit, you don't need it. The best way for you to go about this is to follow these steps:
1) Unlock the bootloader again.
2) Flash TWRP again.
3) Flash a ROM.
4) Get s-off (this is the most important step, and all the previous steps were all leading to this).
5) Run an at&t RUU (to return the phone to stock, I'm assuming it's the at&t model?).
6) Return the CID to the original CID.
Code:
fastboot oem writecid CWS__001
7) Relock the bootloader.
Code:
fastboot oem lock
8) Return the phone to s-on.
Code:
fastboot oem writesecureflag 3
Voila.
Sent from my Evita
Wow. Nice Tim !!!
Sent from my Inspire 4G using Tapatalk
Thanks for the help so far. Under your advice I'm using fastboot commands manually to try and get this to work. So now I'm unlocked again, but I'm having a problem flashing TWRP. I downloaded the latest TWRP for the Evita and ran fastboot flash recovery evita.img (that's what I renamed the file to). It tells me that sending and writing was OKAY, so it should work. Then I try to reboot to recovery from the bootloader menu, and it fails after this. It appears to boot something up, I get a blank screen, then it reboots again on it's own without showing the TWRP menus.
What am I doing wrong?
You can't reboot to the recovery, you can only reboot to the bootloader and then manually select recovery using the hardware buttons (volume = scroll, power = select). The whole process should go like this:
Code:
fastboot flash recovery evita.img
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can manually select recovery and it should hopefully boot into it.
Sent from my Evita
That's what I did, although I just tried these steps again. When I used the volume/power buttons and chose recovery, it reboots as it should, then it tries to load the recovery, fails, then reboots and starts up the phone. I should note, and this might be the problem, is that phone boots up totally in to the full blown OS. It's Android 4.1.1 with the 3.18 kernel.
I have SuperCID, and the phone says it is unlocked with S-ON.
Does it make sense and try to flash the 2.15 firmware at this point since my HBOOT is older?
I tried another thing since I can actually use the phone and I'm rooted, I installed GooManager from the store and let that install the recovery then rebooted. It did the same thing. At the very least, if I could only get TWRP working I could recover a TWRP backup I made.
And ultimately, the phone works at this point, I just want to remove the tampered text and keep it at stock. Since I have a working ROM, should I just follow your steps 6, 7 and 8? Do I still need to achieve S-Off and worry about the recovery?
You need s-off, otherwise running the RUU will brick your phone. Just try getting s-off without the recovery. Which ROM is currently installed?
Sent from my Evita
I have an AT&T stock deodexed ROM version 3.18.502.6.
Ok, scratch that, without root you cannot get s-off. What's the exact filename of the recovery you've tried to flash?
Sent from my Evita
Hi Everyone,
This is the first time I am playing with a mobile software.
I did the unlock bootloader as per the instructions given in htc website, and my phone status shows unlocked, but it is still S-ON.(Hboot 2.51)
I was planning to install a custom rom either CM11 or MIUI5.
After reading many threads in xda as well as in other sites, I tried to do a S-OFF to install a custom ROM.
I tried Rumrummer, Moonshine and firewater, but nothing has made my mobile as S-OFF.
I tried to restore back to the original stock rom, and followed the process in htconeforum(how-unbrick-restore-htc-one-s-stock-relocked)
So, I tried to do an oem lock and it got relocked.
Now, I tried to do an RUU, and it didn't work with data transfer error.
Only Hboot comes on my phone with the below details
***Tampered***
***Relocked***
My Phone doesn't start now; tried pushing lot of CWM and TRWM recoveries, it got stuck in sending recovery for long time, and i exit.
Can anyone please help me and let me know, how can i restore back to htc rom or go forward and install custom rom.
Thanks,
Deepak
deepak_raja20 said:
Hi Everyone,
This is the first time I am playing with a mobile software.
I did the unlock bootloader as per the instructions given in htc website, and my phone status shows unlocked, but it is still S-ON.(Hboot 2.51)
I was planning to install a custom rom either CM11 or MIUI5.
After reading many threads in xda as well as in other sites, I tried to do a S-OFF to install a custom ROM.
I tried Rumrummer, Moonshine and firewater, but nothing has made my mobile as S-OFF.
I tried to restore back to the original stock rom, and followed the process in htconeforum(how-unbrick-restore-htc-one-s-stock-relocked)
So, I tried to do an oem lock and it got relocked.
Now, I tried to do an RUU, and it didn't work with data transfer error.
Only Hboot comes on my phone with the below details
***Tampered***
***Relocked***
My Phone doesn't start now; tried pushing lot of CWM and TRWM recoveries, it got stuck in sending recovery for long time, and i exit.
Can anyone please help me and let me know, how can i restore back to htc rom or go forward and install custom rom.
Thanks,
Deepak
Click to expand...
Click to collapse
Well i got S-OFF with Rumrummer but i got it till my 7th try. you should keep trying with it
Stuck in sending recovery/sending zip flash
Some how , I managed to push CWM recovery to my phone.
But when I select install from zip, it says "Error mounting SDCard".
I tried the fastboot oem lock using all in one tool kit and now it says Tampered, Relocked.
So, i am trying to run factory RUU exe , it stuck at sending recovery.
I tried to push the .zip factory RUU, and it says sending and stuck there.
Even I tried the adb sideload, it says data transfer failed.
Looks like all the data on the SD card(in my case internal storage) is gone during erase and I don't have any flash zips on the device and I am not able to send any flash zips to the device.
The drivers are installed correctly, and my HBoot 2.15 says fastboot usb when in bootloader, but when i type adb devices, it gives no device.
Can some one please help me in getting my phone back.
Thanks,
Deepak
deepak_raja20 said:
Some how , I managed to push CWM recovery to my phone.
But when I select install from zip, it says "Error mounting SDCard".
I tried the fastboot oem lock using all in one tool kit and now it says Tampered, Relocked.
So, i am trying to run factory RUU exe , it stuck at sending recovery.
I tried to push the .zip factory RUU, and it says sending and stuck there.
Even I tried the adb sideload, it says data transfer failed.
Looks like all the data on the SD card(in my case internal storage) is gone during erase and I don't have any flash zips on the device and I am not able to send any flash zips to the device.
The drivers are installed correctly, and my HBoot 2.15 says fastboot usb when in bootloader, but when i type adb devices, it gives no device.
Can some one please help me in getting my phone back.
Thanks,
Deepak
Click to expand...
Click to collapse
I suggest you get the OTG USB cable. Load the ROM on a Flash USB and then use TWRP to install the ROM (Remember to mount the OTG in TWRP) Check Amazon, it only cost less than $3. I've never push the ROM to the phone. Saves a lot of time when you have multiple phones.