Related
i rooted my sisters white Evo yesterday.i followed up on Hboot 2.02 S-Off Like a Boss! guide, and it worked and everything. it flashed Stock 2.2 Rooted and i followed up on updating PRL/Profile and what not, but i was still in the process of picking a rom for her. i tried to enable wifi, wasnt working, 4G, wasnt working either. i was like wtf? then i got an update for 3.30 somehow and it was like 6mbs. my dumbass installed it, got wifi and eveyrthing to work, but! i lost my recovery and hboot aint pikcking up any PC36IMG file either.
djtoonjr said:
i rooted my sisters white Evo yesterday.i followed up on Hboot 2.02 S-Off Like a Boss! guide, and it worked and everything. it flashed Stock 2.2 Rooted and i followed up on updating PRL/Profile and what not, but i was still in the process of picking a rom for her. i tried to enable wifi, wasnt working, 4G, wasnt working either. i was like wtf? then i got an update for 3.30 somehow and it was like 6mbs. my dumbass installed it, got wifi and eveyrthing to work, but! i lost my recovery and hboot aint pikcking up any PC36IMG file either.
Click to expand...
Click to collapse
Have you tried using Rom Manager to install a recovery?
xNotta said:
Have you tried using Rom Manager to install a recovery?
Click to expand...
Click to collapse
i run rom Manager and get the following screen.
First Screen:
you must root your phone for ROM Manager to function Superuser was not found at "/system/bin/su" or system/xbin/su". Use google search on your computer to find instructions to root your phone.
superuser from the market is installed...
Then i go and click Flash Alternate Recovery(RA Recovery v1.8.0) and it force closes.
Then i try to flash clockwork and it takes a long time too and i get a message An error occured while attempting to run privileged commands.
If the phone downloaded the OTA update for 3.30, as your first post suggests, then it became unrooted and you'll have to root it again.
djtoonjr said:
i run rom Manager and get the following screen.
First Screen:
you must root your phone for ROM Manager to function Superuser was not found at "/system/bin/su" or system/xbin/su". Use google search on your computer to find instructions to root your phone.
superuser from the market is installed...
Then i go and click Flash Alternate Recovery(RA Recovery v1.8.0) and it force closes.
Then i try to flash clockwork and it takes a long time too and i get a message An error occured while attempting to run privileged commands.
Click to expand...
Click to collapse
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Scratch that, I just noticed you don't have a recovery to flash from. :-/
Is your HBoot S-Off?
xNotta said:
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Click to expand...
Click to collapse
i cant get to recovery lol
i go to the bootloader, scans for a PC36IMG file but it donesnt find it, even tho the file is there! lol. maybe i shold format my sdcard. hmm.
but i scroll down to recovery, and it senss me to the default recovery, not clockwork or amen ra. the stock htc recovery. lol.
xNotta said:
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Scratch that, I just noticed you don't have a recovery to flash from. :-/
Is your HBoot S-Off?
Click to expand...
Click to collapse
lmfao. yeah i have S-off.
drmacinyasha said:
If the phone downloaded the OTA update for 3.30, as your first post suggests, then it became unrooted and you'll have to root it again.
Click to expand...
Click to collapse
ive been trying dat but when it comes to the part to flash the first PC36IMG, it doesnt find it, i formatted my sdcard and trying it again.
I am really failing at reading tonight, lol.
Can you boot into the bootloader and use ADB?
Could try ADB Push-ing the files extracted from the Superuser's flashable .zip to their respective locations.
Not sure how that would work out though, never tried it.
Get files "su" from su-2.3.6.1-ef-signed.zip\system\bin
and "Superuser.apk" from su-2.3.6.1-ef-signed.zip\system\app
put both files in the folder with ADB.
open adb command prompt and
Code:
ADB push Superuser.apk /system/app (Press Enter)
ADB push su /system/bin (Press Enter)
Then reboot back into the rom.
You might need to use a file explorer to navigate to /system/app and click Superuser.apk to install it.
(Uninstall old SuperUser from the market before installing.)
Worth a try if no one else has any fixes.
xNotta said:
I am really failing at reading tonight, lol.
Can you boot into the bootloader and use ADB?
Could try ADB Push-ing the files extracted from the Superuser's flashable .zip to their respective locations.
Not sure how that would work out though, never tried it.
Get files "su" from su-2.3.6.1-ef-signed.zip\system\bin
and "Superuser.apk" from su-2.3.6.1-ef-signed.zip\system\app
put both files in the folder with ADB.
open adb command prompt and
Code:
ADB push Superuser.apk /system/app (Press Enter)
ADB push su /system/bin (Press Enter)
Then reboot back into the rom.
You might need to use a file explorer to navigate to /system/app and click Superuser.apk to install it.
(Uninstall old SuperUser from the market before installing.)
Worth a try if no one else has any fixes.
Click to expand...
Click to collapse
OMG! ORGASM! lolwell i didnt try ur method YET, but i formatted sdcard, and it picked up the PC36IMG file. so im re-rooting it against, hopefully trying to re-root it wont fk things up u know. will post bak on progress. thanks alot tho man. i know the last couple of times, couldnt get anyone to help me out lol
djtoonjr said:
OMG! ORGASM! lolwell i didnt try ur method YET, but i formatted sdcard, and it picked up the PC36IMG file. so im re-rooting it against, hopefully trying to re-root it wont fk things up u know. will post bak on progress. thanks alot tho man. i know the last couple of times, couldnt get anyone to help me out lol
Click to expand...
Click to collapse
if you are s-off all you have to do is flash a rooted pc36img in bootloader and then flash a recovery. no need for the entire process again.
t3project said:
if you are s-off all you have to do is flash a rooted pc36img in bootloader and then flash a recovery. no need for the entire process again.
Click to expand...
Click to collapse
lmfao. damn. now u tell me haha.
well i went ahead and re-rooted and got it woking now but thxs for the help.
if PC36IMG isnt getting picked up by boot loader, just format SDCARD and run it again lol
Hi I plan to unroot my phone for warranty purposes.
I'm using a Desire Z with
baseband: 12.28b.60.140eU_26.03.02.26_M
build: 1.34.707.5 CL273326 release-keys
I've rooted the phone using gfree method.
This is what I plan to do:
1) Restore back to stock ROM (done)
2) Restore stock recovery.
- i have extracted the recovery.img from this RUU:
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M_release_155556_signed.exe
- Will be flashing using this guide:
http://forum.xda-developers.com/showthread.php?t=902493&highlight=flash_image
-Yet to flash that .img
3) S-on.
- Using this guide:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Turning_S-On
4) Restore factory settings.
I have extracted the .img from the RUU i mentioned. My question is whether that .img is flashable on all Desire Zs because it is the same RUU that was featured in the rooting procedure for build 1.72.
I understand that there has been a lot of unrooting threads, but none seem to deal specifically with the compatibility of the recovery image.
Any help is much appreciated.
I'm not sure that if I just skip to S-on then the custom recovery (CWM in this case) will not show up. Does it?
Can anyone help?
I just need to know whether recovery images from different Vision RUUs (except TMOUS ones) are identical and flashable on any Desire Z.
As mentioned I already have a stock recovery.img from a 1.34 RUU, but the location ID might not be the same. Are stock recovery images dependent on location IDs?
The recovery should be completely independent from the CID. If the partitioning scheme is the same (and you can check that by verifying if the sizes of the images that make up your original ROM and those of the RUU are identical) you should be fine.
Cool. I went ahead with flashing the stock recovery and sure enough my phone isn't bricked and when I boot into recovery, it is of a red triangle.
Weirdly enough ROM Manager still tells me I have CWM 2.5.1.3 though...
Guess ppl can start using that recovery.img as a stock recovery.
Thanks a thousand times!
EDIT:
I tried to S-On using the guide on the Wiki but it did not work.
So i tried using terminal emulator to do the following:
# cd /data/local
# chmod 777 gfree
# ./gfree -s on
Click to expand...
Click to collapse
sure enough when i booted into (trackpad + power button) i see it say s-on.
Am i officially 'unrooted' now?
There was supposed to be a 'sync' command after './gfree -s on', but I forgot to do it. Am I still good to go?
You're okay. The sync command makes sure the caches are written to disk, but since you are S-ON it means they were written.
so if it so happened this phone gets returned to me after warranty claims, so I just
# cd /data/local
# chmod 777 gfree
# ./gfree -s off
to turn it s-off again? Or do I need to go through running rage again?
UPDATE: Got my phone back. Had to re-root the phone all the way from running rage.
weirdly enough, although the bootloader screen shows S-on, I am still able to use shootme? This means I'm still rooted, am I right?
Yup. Remove the Superuser app and it at least shouldn't be as obvious that you're rooted
hrmm superuser doesn't seem to be removable by conventional means... I don't remember installing it either. When I push it to the phone, I pushed it to the sdcard. Now i booted the phone without the sdcard, but superuser is still there...
Do I restore factory settings instead?
EDIT: nvm, Factory reset-ed. Everything looked factory. Wish me luck.
Nice, glad everything worked out...
djfoo000, glad it all worked out for you.
I have a Bell Desire Z, like yours and wanted to do something similar. While your steps are clear, i just wanted to confirm a few points:
1. In your very first post, when you said "Restore back to stock ROM (done)" i am guessing (99% sure) you meant that you restored back the ROM which you had backed up right after you installed ClockworkMod? Or did you use some other ROM image?
2. So even after you used gfree to turn back S-ON, you still had root privileges because of Superuser. How about after you did the factory reset, which presumably removed Superuser - did you still have root privileges?
3. Would it be possible for you to upload the stock recovery img file somewhere? If not, its okay as well.
Thanks
1) Yes. That stock ROM i mentioned was of a nandroid backup that restored everything prior to flashing a ROM that restored everything including apps and an unfinished Angry Birds (haha), instead of a clean one.
2) Yeah weirdly enough ShootMe still snaps screenshots. My guess is that root access is needed to install shootme as a system app and is not required beyond that. So even after s-on, shootme continues to operate due to it already being in the system app folder.
After I factory reset-ed, superuser and terminal emulator was gone. Since I was in a hurry to return the phone to the dealer I did not bother to download terminal emulator to input the 'su' command to check for root privileges. Sorry if it did not answer your question regarding root after factory reset.
3) Here's the file I extracted:
http://www.megaupload.com/?d=K8DVSNLX
I'm not 100% sure if it'll work on other Desire Zs since mine was not a carrier branded Desire Z.
Best of luck!
Excellent. Thanks djfoo000.
Couple of more questions -
1. do you know of any way for me to backup my existing recovery? I still havent installed CwM or other recovery image on my Desire Z (still stock).
Fastboot has commands to erase the recovery or flash a new one, but nothing that i could find to backup current recovery.
2. Also, would having S-ON and CID as 111111111 have any impact on doing a factory reset through stock recovery on the stock ROM? I dont think it will turn S-OFF and even more unlikely that it will change the CID, but will it do anything else? like go into a boot loop or some other weird thing?
lol i'm a noob user just like you. I just happen to gather enough info to do what I wanted to do.
1) I have no idea of a way to backup the stock recovery. Maybe searching the phone for a recovery.img (if there ever is one in the phone) and pull that?
2) I dunno anything about CIDs...
Might need help from other senior users from the forums.
testerman123 said:
1. do you know of any way for me to backup my existing recovery? I still havent installed CwM or other recovery image on my Desire Z (still stock).
Fastboot has commands to erase the recovery or flash a new one, but nothing that i could find to backup current recovery.
2. Also, would having S-ON and CID as 111111111 have any impact on doing a factory reset through stock recovery on the stock ROM? I dont think it will turn S-OFF and even more unlikely that it will change the CID, but will it do anything else? like go into a boot loop or some other weird thing?
Click to expand...
Click to collapse
1. There may well be a stock ROM/RUU image that you can pull that stock recovery from, as you've mentioned above. Or if not, you could always "dd" the recovery partition to back it up, though I double that will be necessary.
2. Did you mean S-OFF ? No, it won't have any impact, the factory reset won't touch the radio config partition, which is where S-OFF, SuperCID etc are stored.
Thanks djfoo000 for trying - you have been helpful.
Steviewevie, thanks for responding.
I think dd would be the answer as well, now the only question is where is the recovery located? like the "if=" parameter.
After that off to the races with CwM (and a nandroid backup of my existing firmware, of course), and a custom ROM! Steviewevie and djfoo000 - didnt notice a mention of any custom roms you guys were using. any suggestions?
Edit:
Looked around a little bit to see what the if parameter would be.
when i did
$ su
# cat /proc/mtd
under adb shell and terminal emulator, i did not get a list of partitions.
BUMP!! anyone?
testerman123 said:
Looked around a little bit to see what the if parameter would be.
when i did
$ su
# cat /proc/mtd
under adb shell and terminal emulator, i did not get a list of partitions.
Click to expand...
Click to collapse
The G2 does not use raw flash, so partitions will not show up as mtd devices. You should be able to do a
# cat /proc/emmc
if you are just trying to see the partition map...
Thanks ianmcquinn! That worked great.
Got my hboot, recovery and boot backed up just in case.
The curious thing, though, is that the stock unbranded recovery from 1.34.405.5 RUU that djfoo uploaded is only 3.85MB, while my backed up recovery is 8.5MB. whats up with that?
i can confirm that when I flash the recovery.img i uploaded, the unrooting works fine. And it is 3.85MB as mentioned.
Hi everyone,
I'm using a HTC Wildfire and am considering changing from stock (HTC non-branded) to CyanogenMod for a number of minor reasons. Could anyone just confirm that I got a few points right before I get started:
- Recovery is totally independent from the ROM itself, right? So I can flash ClockWorkMod Recovery only, continue to use the stock ROM, but have the additional features of ClockWorkMod available, such as backup, with which I can create a complete backup of the stock ROM. In case I don't like CyanogenMod, I can restore the stock image and be exactly where I left it, Apps, Settings and everything (of course the new Recovery will still be installed.) Is this correct?
- I'm planning to do the following steps (I read about the details, just want to confirm the basics):
x use the Revolutionary way to S-OFF and install new Recovery
x create full image backup of the stock ROM using the new Recovery
x install new ROM (ClockWorkMod)
x if I don't like CM: restore image created before to return to stock
-> This should work, shouldn't it?
- One more: What will happen if the the phone is S-OFF, an alternative Recovery is installed, and a HTC Firmware-Update is attempted? Will this work at all, will it update just the ROM, or will it update the Recovery, too? S-OFF will not be changed back to S-ON, right?
Thanks for your help.
Regards
1. Yes, the recovery is in it's own partition and is independent from the ROM
2. The recovery creates a "snapshot" of your current ROM. So when you restore, it'll be just the way you left it.
3. There's no need to do any HTC Firmware updates after installing a custom ROM (infact, I'm almost 100% sure that it won't work)
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
As for HTC firmware update question,if your talking about the over the air updates I'm not sure but I think it would update your hboot thus reverting back to s-on status again so best not accept it if you do get one (turn off in settings)
Edit : ninja'd lol
Sent from my HTC Wildfire using XDA App
slymobi said:
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
Click to expand...
Click to collapse
Yes, of course.
As for HTC firmware update question,if your talking about the over the air updates [...]
Click to expand...
Click to collapse
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
150d said:
Yes, of course.
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
Click to expand...
Click to collapse
Ah sorry never dealt with any firmware updates. There are ruu.exe to help get back to stock if something goes wrong I think.
Sent from my HTC Wildfire using XDA App
You can go completely back to stock, s-on and all but believe me once you have cwm installed there really is no point unless its for warranty reasons, backup fails are rare with the latest recoveries + if it does fail with your first backup you can always post here and we will explain how to extract a stock Rom from an ruu to put things back to how they where before or you can flash a custom sense Rom and modify it to your liking.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
You can go completely back to stock, s-on and all
Click to expand...
Click to collapse
That's great.
[...] but believe me once you have cwm installed there really is no point unless its for warranty reasons[...]
Click to expand...
Click to collapse
Yea, exactly. I'm a little on the paranoid side, I know... ;-)
Ok, I'm on my way now. I've performed the "Revolutionary" S-OFF and am now running "Revolutionary CWM v4.0.1.4". Is this an out-of-date version?
I've read about ROM-Manager being able to auto-check for and flash a new Clockworks Recovery, but I've also read that ROM-Manager needs root. I have not yet flashed a new ROM, so I assume that I'm not yet rooted, am I? Can I find a ZIP of CWM that I can directly flash from the SD-card?
Does the CWM-version I'm running have any effect on the "quality" of the image backup? In other words, if I create a backup now, will I be able to restore it later running a different version of CWM?
The "different version backup restore" is a bit wonky and won't always work.
To flash a different recovery from the SD card do this:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
2. Boot into the bootloader
3. Wait a bit and then it should prompt you to update
4. Click the volume+ key to update
5. Remove SD card
6. Boot into the new recovery and insert the SD card
7. Go under mounts and select Mount USB storage
8. Delete the PCIMG file from your computer
nejc121 said:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
Click to expand...
Click to collapse
I tried to, but I couldn't use the link. The whole domain seems to be down - maybe another holy crusade of Big Content, who knows. They sure leave fans in their wake, don't they.
Since you indicated that updating would be ok for the wildfire I went to http://www.clockworkmod.com/rommanager and downloaded the file recovery-clockwork-5.0.2.0-buzz.zip.
However, I'm not sure how to handle it: If I put it on the card under this name, nothing happens on bootloader-start. In recovery, I can select the file and install it, and then I immidiatly get a newly colored menu with the new CWM version 5.something. However, once I restart, the old CWM (v4.x) is there again.
I assume I need to use a magic filename so that the bootloader performs the update, not the (already running) recovery. Right?
**EDIT: Ah, disregard. I believe I found the answer myself.
Do you have fastboot?
If you do I can give you the recovery.img I'm using, which you can flash via fastboot.
Yes, fastboot is available.
Thank you.
Okay, here's how you flash a recovery via fastboot.
1. Extract the .zip I attached to the location where you fastboot is
2. Reboot phone in the bootloader
3. Select fastboot and attach USB cable
4. Open up the command prompt and type in "cd [location of fastboot]
5. Type in "fastboot flash recovery recovery.img"
6. You're done
Oh and by [location of fastboot] I mean that you type in the location of fastboot.
Wow - this was fun. There was something really curious going on with my device: Whatever I tried, no "official" way worked to modify CWM v4 to v5. In every case, the menu of the new version showed up and was usable, but was gone again after restart. After the file-on-card method got me nowhere (file was not recognized), I tried the high road and installed ROM-Manager. This complained about missing su. So I installed su. After that ROM-Manager downloaded CWM v5 and put it onto the card (into a file named update.zip - ahh... ) On restart, the CWM-install-screen came up, then the v5 menu.
And after restart, it was gone again. Even ROM-Manager was confused: He showed v5 as "installed", when in fact it was still v4. ;-)
So finally I downloaded the Android SDK (to get fastboot.exe) and performed the flash as you suggested in the first place. And it worked. First try, without hitch, permanently.
Thank you very much for your help!
Regards
The problem with ROM Manager's version is that it's only temporary and can only be accessed from the ROM Manager itself
Hey Guys. I've been trying to root my Evo 4g for over a year and I am either messing up horribly or my EVO is just unrootable. I attempted flash/root it with revolutionary, but all I have is S-OFF.
The H-Boot Screen reads:
-Revolutionary-
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.12.19
MAR 8 2011, 17:02:15
I really hope I can get some help, I've wanted this badly for over a year.
If you need any other information, please just ask.
Dude! You are already rooted! Revolutionary flashes a recovery for you, so all you need to do is flash a rom if you want.
Hit the thanks button if i have helped you in any way today !
+1 The Revolutionary tag means your bootloaded is unlocked and you have s off. Your good to go. Just do a Nandroid Backup. And then flash away.
But when I try to flash a rom over, it never works. Not even superuser works. I downloaded Terminal Emulator and typed su, but it doesnt do anything.
Yunq Millz said:
But when I try to flash a rom over, it never works. Not even superuser works. I downloaded Terminal Emulator and typed su, but it doesnt do anything.
Click to expand...
Click to collapse
Do u have a custom recovery?
Sent from my PC36100 using xda premium
First, you probably need a custom recovery. Search for "amon ra evo" or "clockwork mod evo" follow the instructions on their page and that will get you a custom recovery. Do a "nandroid backup" so you have a backup of your original os
Second, look up SU evo, download the zip, and flash that in your recovery. That will give you su.
PS if you don't understand any or all of these terms, look up xda rooting for dummies
Sent from my PC36100 using xda premium
I tried all the steps on the recoveries, and they are all saying that I do not have access to superuser. Terminal emulator does not respond positive to su either.
Yunq Millz said:
I tried all the steps on the recoveries, and they are all saying that I do not have access to superuser. Terminal emulator does not respond positive to su either.
Click to expand...
Click to collapse
You flashed the superuser zip in recovery right?
klharalson said:
You flashed the superuser zip in recovery right?
Click to expand...
Click to collapse
I've tried, but with no success.
Yunq Millz said:
I've tried, but with no success.
Click to expand...
Click to collapse
what does it say when you flash it? Successful, errors??
klharalson said:
what does it say when you flash it? Successful, errors??
Click to expand...
Click to collapse
It doesn't even recognize the file.
klharalson said:
what does it say when you flash it? Successful, errors??
Click to expand...
Click to collapse
Maybe a bad download, try this one...this is the one that I have used successfully...also, what recovery are you using right now? I have had issues with clockworkmod on occassion that has aborted installation of zips...
superuser http://dl.dropbox.com/u/30295084/CM9/Superuser-3.0.7-efghi-signed.zip
amon ra recovery that you flash through bootloader, just rename zip to PC36IMG http://dl.dropbox.com/u/30295084/CM9/PC36IMG_ra-supersonic-4.3-smelkus-ics.zip
So try recovery first, then try flashing the superuser zip I linked above and see where that gets you.
klharalson said:
Maybe a bad download, try this one...this is the one that I have used successfully...also, what recovery are you using right now? I have had issues with clockworkmod on occassion that has aborted installation of zips...
superuser http://dl.dropbox.com/u/30295084/CM9/Superuser-3.0.7-efghi-signed.zip
amon ra recovery that you flash through bootloader, just rename zip to PC36IMG http://dl.dropbox.com/u/30295084/CM9/PC36IMG_ra-supersonic-4.3-smelkus-ics.zip
So try recovery first, then try flashing the superuser zip I linked above and see where that gets you.
Click to expand...
Click to collapse
It says no image or wrong image.
Yunq Millz said:
It says no image or wrong image.
Click to expand...
Click to collapse
ok, so it doesn't then say checking PC36IMG.zip?
edit: did you make sure to not put the zip in a folder on your sd card? it has to be on the root of your sdcard to be found.
klharalson said:
ok, so it doesn't then say checking PC36IMG.zip?
edit: did you make sure to not put the zip in a folder on your sd card? it has to be on the root of your sdcard to be found.
Click to expand...
Click to collapse
I made sure I put it in the root, its not in any folder. The bootloader does say checking for PC36IMG.zip, but it can't find it. And I am 100% sure it is spelled correctly.
Yunq Millz said:
I made sure I put it in the root, its not in any folder. The bootloader does say checking for PC36IMG.zip, but it can't find it. And I am 100% sure it is spelled correctly.
Click to expand...
Click to collapse
Either open up a file manager on your phone or mount to computer to look at the name if you added zip, delete that...I am stumped as to what else the issue would be...
This might be overkill, but you might want to ruu back to stock...redo revolutioanry and after you type yes download clockworkmod recovery in revolutioanry...boot into recovery, flash superuser zip and then boot the phone...it should work for you, but also should be working now.
klharalson said:
Either open up a file manager on your phone or mount to computer to look at the name if you added zip, delete that...I am stumped as to what else the issue would be...
This might be overkill, but you might want to ruu back to stock...redo revolutioanry and after you type yes download clockworkmod recovery in revolutioanry...boot into recovery, flash superuser zip and then boot the phone...it should work for you, but also should be working now.
Click to expand...
Click to collapse
I am ruu back to stock right now. I will tell you if I can reroot it. Btw, should I use revolutionary or unrevoked?
Yunq Millz said:
I am ruu back to stock right now. I will tell you if I can reroot it. Btw, should I use revolutionary or unrevoked?
Click to expand...
Click to collapse
I have always used revolutionary, thats not to say the other isn't good, just never used it.
Thank you so much. I restored it to 2.2 with the ruu. My phone was still S-off, but the recovery finally flash. Checked the terminal emulator and I am granted Superuser permissions. I can not thank you enough.
Yunq Millz said:
Thank you so much. I restored it to 2.2 with the ruu. My phone was still S-off, but the recovery finally flash. Checked the terminal emulator and I am granted Superuser permissions. I can not thank you enough.
Click to expand...
Click to collapse
its no problem...glad you were able to get it working finally
I'm trying to root my phone to install CM 10.2. I've been searching for a few hours and am getting more and more frustrated. I've read that Firewater is the easiest way to unlock the bootloader on my phone. I've downloaded Firewater, but I don't know what to do with it. Its just a file called "Firewater" with no extension. I don't know how to run it.
I've also tried RumRunner, and have had no success.
I'm not sure what ADB and Fastboot are, but I think I have some ADB stuff installed on my comp [ C:\Program Files (x86)\Minimal ADB and Fastboot ] and I have that path in my Environment Variables>path directory. I don't know what to do with it.
Please help me get started. Step by step instructions would be great. I saw a thread that isn't very old where someone was having root trouble w/ KitKat but they were able to run Firewater. I need help getting that started at least. Thank you.
Edit: Fastboot is Off
USB Debugging Enabled
HTC Sync (can't find it anywhere on my comp, or in the programs list ((control panel)) so I assume its not installed)
Drivers are installed on my comp.
I've downloaded an ADB toolkit, and have it pathed. I opened the command prompt and ran "adb devices" to check. My phone showed up with no problem.
I then moved firewater to the current directory cmd was using c:\Users\MYNAME.
adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
after this it displays:
127:[email protected]:/ $
I entered "su"
/system/bin/sh: su: not found
Could anyone explain what I'm doing exactly by following these directions, and explain what I can do next to correct the problem?
Edit: su means Super User, correct? I've tried installing SuperSU, but It says that there is no SU binary installed. I haven't found out how to install the binary.
Pharva said:
I've downloaded an ADB toolkit, and have it pathed. I opened the command prompt and ran "adb devices" to check. My phone showed up with no problem.
I then moved firewater to the current directory cmd was using c:\Users\MYNAME.
adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
after this it displays:
127:[email protected]:/ $
I entered "su"
/system/bin/sh: su: not found
Could anyone explain what I'm doing exactly by following these directions, and explain what I can do next to correct the problem?
Edit: su means Super User, correct? I've tried installing SuperSU, but It says that there is no SU binary installed. I haven't found out how to install the binary.
Click to expand...
Click to collapse
you need temp root... goto http://firewater-soff.com/ everything is right there. If you have kitkat from the OTA the other day, i dont believe it works on kitkat yet.
Thanks. I've read that temproot doesn't work on KitKat either. For now, it would seem that my only option is to wait, right?
Pharva said:
Thanks. I've read that temproot doesn't work on KitKat either. For now, it would seem that my only option is to wait, right?
Click to expand...
Click to collapse
Yes you are correct temp root method does not work for the newest OTA update and unfortunately there is no method for the CDMA version of the htc one so hopefully we will see a new method soon!
S-Off not working
nty123 said:
Yes you are correct temp root method does not work for the newest OTA update and unfortunately there is no method for the CDMA version of the htc one so hopefully we will see a new method soon!
Click to expand...
Click to collapse
I am having this problem also. I am trying to s-off with firewater and can't get past the SU also...it tells me SU can't be found.
Debugging enabled
Developer Mode enabled
Network band set to LTE/CDMA
No passcode or other security lock
My Fastboot and ADB are working fine. I am able to run the Temproot instructions, but it stops at SU. WHY?
payrovi2 said:
I am having this problem also. I am trying to s-off with firewater and can't get past the SU also...it tells me SU can't be found.
Debugging enabled
Developer Mode enabled
Network band set to LTE/CDMA
No passcode or other security lock
My Fastboot and ADB are working fine. I am able to run the Temproot instructions, but it stops at SU. WHY?
Click to expand...
Click to collapse
just what the above post's stated, you need temp-root to, along with firewater. and if you are on the newest ota (kitkat 4.4.2) then you have no other choice but to wait. that mean's no downgrading either.
nty123 said:
just what the above post's stated, you need temp-root to, along with firewater. and if you are on the newest ota (kitkat 4.4.2) then you have no other choice but to wait. that mean's no downgrading either.
Click to expand...
Click to collapse
Thanks. Yes, I was able to temproot and firewater and get s-off.
I'm trying to load Cyanogenmod for my HTC One Verizon ( cm-10.2.0-RC1-m7vzw.zip ) through clockworkmod recovery 6.0.4.7
When I wiped the data/factory reset...it seemed to get stuck for >20minutes. I powered down and up...and it looked like some partial factory reset had happened.
I went ahead with the cyanogenmod zip update, through cwm recovery, and it seems to be stuck at Installing Update. Nothing is happening or moving.
Any thoughts?
Thanks for all the developer help.
payrovi2 said:
Thanks. Yes, I was able to temproot and firewater and get s-off.
I'm trying to load Cyanogenmod for my HTC One Verizon ( cm-10.2.0-RC1-m7vzw.zip ) through clockworkmod recovery 6.0.4.7
When I wiped the data/factory reset...it seemed to get stuck for >20minutes. I powered down and up...and it looked like some partial factory reset had happened.
I went ahead with the cyanogenmod zip update, through cwm recovery, and it seems to be stuck at Installing Update. Nothing is happening or moving.
Any thoughts?
Thanks for all the developer help.
Click to expand...
Click to collapse
can you power off device and boot into recovery? (not sure what the problem is yet but you could try using a different recovery, twrp instead of cwm. before you try out twrp (if you do) make sure you have the latest version of cwm installed
nty123 said:
can you power off device and boot into recovery? (not sure what the problem is yet but you could try using a different recovery, twrp instead of cwm. before you try out twrp (if you do) make sure you have the latest version of cwm installed
Click to expand...
Click to collapse
I can boot into recovery, but can't boot the phone up.
payrovi2 said:
I can boot into recovery, but can't boot the phone up.
Click to expand...
Click to collapse
ok, what i would try is backup to the rom you have before you tried installing CM( only if you made a backup). if you didn't then i would try clearing all data and that rom and try installing a different one, maybe the one you have has a bug and is not working properly.
nty123 said:
ok, what i would try is backup to the rom you have before you tried installing CM( only if you made a backup). if you didn't then i would try clearing all data and that rom and try installing a different one, maybe the one you have has a bug and is not working properly.
Click to expand...
Click to collapse
It kept getting stuck at "installing update" no matter whether it was a previous rom or the Cyanogenmod rom. I tried it numerous times...and then finally once it said "...update complete"
I'm rebooting and loading cyanogenmod now...hope that it moves past this CM boot screen.
payrovi2 said:
It kept getting stuck at "installing update" no matter whether it was a previous rom or the Cyanogenmod rom. I tried it numerous times...and then finally once it said "...update complete"
I'm rebooting and loading cyanogenmod now...hope that it moves past this CM boot screen.
Click to expand...
Click to collapse
Nope. still stuck at this boot loop.
Any ideas?
payrovi2 said:
Nope. still stuck at this boot loop.
Any ideas?
Click to expand...
Click to collapse
try restoring from you backup again but this time wipe all your data and factory reset before yo restore
payrovi2 said:
Nope. still stuck at this boot loop.
Any ideas?
Click to expand...
Click to collapse
I would do a decrypted RUU at this point, it will at least get you back on a sense rom (as long as you download the decrypted one, it wont break your SOFF and bootloader unlock). then from there i would reinstall PHILZ or TWRP, then make sure the MD5 is right on the rom you want to install