Someones help would be greatly appreciated.
I spent about 8 hours trying to root my phone last night.....the first time I ran the 4-step root, it went flawlessly. After that however, I downloaded Rom Manager and clockwork wouldn't download (repeated error). I then downloaded Titanium Backup and the program said I didn't have root access.
Fast forward 6 hours later and many additional attempts to re-root (each time hanging up at step 4)........I decided to try and see if my phone was rooted already.
I did a search and based on that search I typed cmd in the search bar (vista), then typed adb shell.....hit enter......and got #.
If I understand right, this means that I'm rooted.
So, 1) Am I rooted?
2) If yes, why can't I proceed from here?
3) How do I proceed from here (In noob terms)?
4) Did I screw anything up or do I need to delete some files as a result of trying to re-root over and over?
Assistance would be greatly appreciated, and I'll be sure to do the same once I have this figured out.
Few more questions.
1) If I'm rooted and all, do I need to install a rooted rom before Rom Manager (clockworkmod) and Titanium Backup will work? I was trying to use Rom Manager to perform a backup before I flashed any ROMS.
2) Is there some superuser file that needs to be downloaded and could that be my problem?
Thanks again.
Just a hunch, but your probably running the pre-release software build. You need to flash the latest rooted software version 147
651.1. The thread is in the development forum.
Sent from my PC36100 using XDA App
BrianBusby2038 said:
Just a hunch, but your probably running the pre-release software build. You need to flash the latest rooted software version 147
651.1. The thread is in the development forum.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
No sure what you mean, but I originally had 147 before attempting root and now I have 1.17.651.1. If I need to flash the software you are referencing could you please provide the link to the forum....I've looked but I'm not entirely sure of what I should be looking for.
I don't know the link but the thread is in the Android Development section and is titled fully rooted stock version 147.651. 1 no adb. Will probably be on page 2nd of the forum. After running the 2 files linked in that thread you'll be all set to run a customer rom.
Sent from my PC36100 using XDA App
Ok, found it.
However, I have the file PC36IMG already on my SD card (it's zipped). Should I replace it with the one you're referring to, use it, or just leave it alone?
I've tried everything.
If someone wants to give me a hand getting all of this worked out and fresh flashed, I'll shoot them some $$ via paypal.
I'm almost 100% my phone is rooted, just can't make a backup, upgrade to the rooted 147 stock rom, download the SU, or flash a custom ROM.
First, remove any zip files you downloaded for rooting purposes from your sd card (place them on your computer for safekeeping). Then, power off your phone and power it back on while holding volume down. At the top it'll give you an HBOOT VERSION. Which version do you get?
Says 0.76.2000
kirk1978 said:
Says
Click to expand...
Click to collapse
Excellent..suggest you follow the "starting over" method by whitslack which can be found in the development section...very easy...
Success at last.
Thanks a ton!
kirk1978 said:
Success at last.
Thanks a ton!
Click to expand...
Click to collapse
Glad you resolved that. Feel free to seek any more help if you need it!
I have this same issue, however my hboot version is 0.79.0000. Suggestions?
aceintheh0l3 said:
I have this same issue, however my hboot version is 0.79.0000. Suggestions?
Click to expand...
Click to collapse
Your nand is still locked. Depending on your software version you will have to root then nand unlock. Let's see if I can help you. What version is your Software Number?
Menu->Settings->About Phone->Software Information->Software Number
Thanks for the response.
I've actually made a good amount of progress. I've followed toastcfh's post about unlocking my nand and it is currently reflashing.I'll give you my versions and suck when everything is said and done
Related
I got myself into a interesting situation. A quick answer would be greatly appreciated:
1. I'm rooted.
2. Trying to install the OTA so I can run 2.2 the right way.
3. I started a thread asking for help because I was confused on unrooting my phone. Didn't get much help, a quick flame, and last someone chimed in to install the OTA from Rom Manager. I asked if I could do this with Root and the thread was killed.
4. I did. The boot screen was the new one. But the radio wasn't updated.
5. I then attempted to unroot my phone. Followed the PB31IMG.zip method. Phone booted normally. Root was lost.
6. This is where I am now.
7. My question is, if I install the OTA now renamed update.zip on my SD card, will I run the chance of bricking my phone because I installed it once from Rom Manager while I had root (#3/#4)??????
Please advise so I don't MOD EDIT up my phone.................
And if you're going to flame and insist I should of just followed the 2.2 leak instructions, you're correct. But I took someone's quick answer and tried it assuming they knew a better method.
mapko11 said:
I got myself into a interesting situation. A quick answer would be greatly appreciated:
1. I'm rooted.
2. Trying to install the OTA so I can run 2.2 the right way.
3. I started a thread asking for help because I was confused on unrooting my phone. Didn't get much help, a quick flame, and last someone chimed in to install the OTA from Rom Manager. I asked if I could do this with Root and the thread was killed.
4. I did. The boot screen was the new one. But the radio wasn't updated.
5. I then attempted to unroot my phone. Followed the PB31IMG.zip method. Phone booted normally. Root was lost.
6. This is where I am now.
7. My question is, if I install the OTA now renamed update.zip on my SD card, will I run the chance of bricking my phone because I installed it once from Rom Manager while I had root (#3/#4)??????
Please advise so I don't MOD EDIT up my phone.................
And if you're going to flame and insist I should of just followed the 2.2 leak instructions, you're correct. But I took someone's quick answer and tried it assuming they knew a better method.
Click to expand...
Click to collapse
Wat is the hboot versoin?
Sent from my Incredible using XDA App
Where do I find that out?
mapko11 said:
Where do I find that out?
Click to expand...
Click to collapse
In the bootloader it should say.
Sent from my Incredible using XDA App
Hboot-0.79.0000
mapko11 said:
2. Trying to install the OTA so I can run 2.2 the right way.
Click to expand...
Click to collapse
Well, "the right way" would be to wait for the actual OTA. Verizon would also have your back if you brick. But, anyway...
If you're still on the 1.00.03.04.06 radio, you can probably follow the instructions in that thread now that you've flashed back to the stock ROM. However, there still seem to be a few cases of people bricking their phones or being stuck in a bootloop after flashing leaks.
If you are confused/concerned/afraid of bricks then you just shouldn't flash the leaked OTA. This is not a flame, this is sound advice. Wait for the real one.
I'm fine with flashing. I just keep hearing about this "double install OTA and brick your phone" issue and I'm trying to avoid doing that. If the one guy didn't chime in with the suggestion to use ROM Manager, I wouldn't of had this issue.
My radio is still 1.00.03.04.06. I just want to make sure I don't run a risk of bricking.
If the hboot updated, i would say not to apply again. If it didnt update then i would say to see what happens, but dont take my word for it 100%
Sent from my Incredible using XDA App
jdkoreclipse said:
If the hboot updated, i would say not to apply again. If it didnt update then i would say to see what happens, but dont take my word for it 100%
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
How do I know if the HBOOT has been updated? I posted my version above?
mapko11 said:
How do I know if the HBOOT has been updated? I posted my version above?
Click to expand...
Click to collapse
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App
jdkoreclipse said:
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Anyway to undo this and go back?
mapko11 said:
Anyway to undo this and go back?
Click to expand...
Click to collapse
Try the PB13IMG.
Sent from my Incredible using XDA App
jdkoreclipse said:
Try the PB13IMG.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
And you needed to un root before applying the ota
Sent from my Incredible using XDA App
jdkoreclipse said:
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I personally have had a .77 HBOOT since I got my phone in April. My mom's phone, on the other hand, had the .79, which she has had since May, and she sure as hell didn't have no 720p camcorder. I don't think that the OP's phone having .79 means with any certainty that the OTA already applied once. I think the radio version listed on the HBOOT screen would be a better indicator.
But absolutely, running the PB13IMG should ensure that he's as far back as he can go, so why not try it just to be safe...
jdkoreclipse said:
Try the PB13IMG.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
That's what I just did before I posted this thread. I installed the PB13IMG and restored everything back to stock. You asked about the HBOOT version and that's .79. I'm comfortable flashing and doing the update. What should HBOOT say? Has anyone successfully updated the OTA from .79 HBOOT?
Thank you for the help. Sorry for the questions. I completely comfortable with rooting, flashing roms, and kernals. This is going back to unroot stock is just new.
I want to install the OTA and I'm good to go. Just making sure it's safe now....
alexdw369 said:
I personally have had a .77 HBOOT since I got my phone in April. My mom's phone, on the other hand, had the .79, which she has had since May. I don't think that the OP's phone having .79 means with any certainty that the OTA already applied once. I think the radio version listed on the HBOOT screen would be a better indicator.
Click to expand...
Click to collapse
Thats a high possibility that hboot means nothing in this scenaroi, but im not gonn. Be risky with someome elses phone. I only provide methods of doing things that i would use on my phone too.
Sent from my Incredible using XDA App
jdkoreclipse said:
Thats a high possibility that hboot means nothing in this scenaroi, but im not gonn. Be risky with someome elses phone. I only provide methods of doing things that i would use on my phone too.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Agreed, however, I noticed after running the PB13IMG, my HBOOT was also .79, which could have only come from the PB13IMG since I hadn't tried to do the OTA yet. Just trying to add pieces to the puzzle to get a better picture for future reference...I'm sure this guy wont be the last to ask...
alexdw369 said:
Agreed, however, I noticed after running the PB13IMG, my HBOOT was also .79, which could have only come from the PB13IMG since I hadn't tried to do the OTA yet. Just trying to add pieces to the puzzle to get a better picture for future reference...I'm sure this guy wont be the last to ask...
Click to expand...
Click to collapse
I appreciate the help guys. I guess my question would be if I ran PB13IMG, lost my root, back to stock, my HBOOT is .79 and my radio is still 1.00.03.04.06 and not 2.05.00.06.11, I should be at the same point as everyone else for installing the OTA from my SD card. Right or wrong?
When you read these threads and people are installing the OTA twice and bricking, are they installing the OTA again when the radio is already updated to 2.05.00.06.11?
Yep. I think you can flash it again, but be real cautious, as this is your second time flashing it, but if the radio is still the old versoin, you should be safe.
Sent from my Incredible using XDA App
I have the newest cyanogen 6.1 on my g2 and I dont have the stock zip anymore, How do I go back to stock, I need a stock froyo download, I dont care if I lose root...
Go to the development section and look at the sticky. You'll find one that has the how to revert back to stock using a hex editor. In the 6th page of the how to thread I posted a link to a hex editor. It's cake.
Sent from my HTC Vision using XDA App
ddgarcia05 said:
It's cake.
Click to expand...
Click to collapse
Mmhhh.... Tasty
Did it.... But now superuser is still there lol ... I want to go back to CM 6 but what should I do so if I ever want to go back to stock it will be there, also what should I do to get all my apps over on CM 6.1
and now my wifi doesnt work, It just says error when I click the check box on in settings
Stock image did you use? I used the one linked in the how to and had no problem.
Sent from my HTC Vision using XDA App
I used that one as well, also did superuser still show up when you were back to stock?
Your probably didn't flash all the way. After restoring from an official image you should be completely stock.
how do I flash all the way? I did what the steps said, and this is what im running now:
Android 2.2
Baseband:
12.22.60.09bU_26.02.01.15_M2
Kernel Version:
[email protected]#1
build number:
1.19.531.1 CL255798 release-keys
I see that it still says cyanogen mod on the kernel version...
But when I boot up it boots regular and does not have the CM 6.1 screen and has the G2 screen instead, and looks like stock froyo....
I try using the method stated above and get the error, then Im stuck on this part I guess:
"**IMPORTANT**
If the flash has failed you must reboot back into the OS and use HexEditor which i have attached to the thread. DO NOT PROCEED UNTIL YOU HAVE DONE THIS!!
Open up an ADB Shell and run the following command:
dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img
this will then export the misc.img file we need to edit to the root of the sdcard.
Mount your sdcard and save the misc.img file to your PC and Open the file with HexEditor.
You should now see the version number on the right hand side of the application and it should read "1.22.531.8" YOU MUST CHANGE THIS TO "1.19.531.1" you can now save the file as miscnew.img and place it on the root of your sdcard and then unmount the sdcard from windows.
Now go back to your ADB Shell and run the following command
dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p17
you can now make sure you have copied the PC10IMG.zip file to the root of your SDCARD and power off your phone and proceed to step 2."
I am using terminal emulator and it says "cannot open for readermission denied, " when I enter this in the emulator "dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img"
NVM forgot to su lol silly me
will keep updated on my progress
Okay, I am back to stock, thanks to you all who pointed me in the right direction... Now If I go back to CM 6.1, what should I do to back up my phone in its stock state?
icolorado303 said:
Okay, I am back to stock, thanks to you all who pointed me in the right direction... Now If I go back to CM 6.1, what should I do to back up my phone in its stock state?
Click to expand...
Click to collapse
You can only back up the phone from it's stock rooted state. Correct?
Anyways, if you going to reroot the phone I highly suggest you use rage instead of visionary.
where do I get rage from? and Is it a similar process.... and IDK you tell me lol, I am new to the android scene, coming from an iphone 4 on tmobile.... I have read lots and lots before attempting to root, lots of stickies etc, all I ever heard about was visionary nothing about rage...
icolorado303 said:
where do I get rage from? and Is it a similar process.... and IDK you tell me lol, I am new to the android scene, coming from an iphone 4 on tmobile.... I have read lots and lots before attempting to root, lots of stickies etc, all I ever heard about was visionary nothing about rage...
Click to expand...
Click to collapse
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Start here. The instructions and files are all there and work. I've just done 3 G2s using this method and had no problems at all.
Also, you'll need to get adb working on your PC to be able to use rage.
See this guide on adb - http://forum.xda-developers.com/showthread.php?t=865685
will the method discussed work for me? I'm on the current build of cyanogenmod and used the gfree method to free all (super cid, sim unlock, real s-off). I need to revert to stock to send phone back because I'm getting a replacement due to signal issues. Any help is appreciated thanx.
anyone? 10char
mcp2009 said:
will the method discussed work for me? I'm on the current build of cyanogenmod and used the gfree method to free all (super cid, sim unlock, real s-off). I need to revert to stock to send phone back because I'm getting a replacement due to signal issues. Any help is appreciated thanx.
Click to expand...
Click to collapse
You're on a G2, right ?
This should work for you - http://forum.xda-developers.com/showthread.php?t=831398
steviewevie said:
You're on a G2, right ?
This should work for you - http://forum.xda-developers.com/showthread.php?t=831398
Click to expand...
Click to collapse
yea using g2 thnx man I'll try when my replacement gets here. Is it a sure thing? Says for temp root and I'm perm rooted. Gosh I feel like a noob lol.
mcp2009 said:
yea using g2 thnx man I'll try when my replacement gets here. Is it a sure thing? Says for temp root and I'm perm rooted. Gosh I feel like a noob lol.
Click to expand...
Click to collapse
That guide will let you downgrade to the stock ROM, yes. There's a note at the bottom saying it's not a rooting method (not sure why that note is there really), is that what you mean ?
Hey All,
I am trying to install CyanogenMod 6.1 onto my DHD. I have successfully rooted, but when I try to install ClockworkMod Recovery via Rom Manager, It says that the flash was successful, but when I attempt to reboot into recovery I get a red triangle with an exclamation mark. I'd upload a picture but as I am new I'm not allowed yet
So obviously it hasn't installed properly even when it says it has. I have tried uninstalling and re-installing, and when I try to install older/newer versions of CWM, it says that an error has occurred.
Does anybody know how to fix this? or alternatively is another recovery firmware available, such as Amon_RA for the DHD?
Thanks in advance guys
on the sdcard in the Clockwork directory, delete the .settings file and the download directory.
Try again it will flash now.
I have already 'reported' the problem here.
leppie said:
on the sdcard in the Clockwork directory, delete the .settings file and the download directory.
Try again it will flash now.
I have already 'reported' the problem here.
Click to expand...
Click to collapse
Hey there leppie,
I did as you instructed, I closed the application, deleted the .settings file and download directory inside the clockwork directory, and it reinstalled. No difference, still getting the phone icon with the red triangle and exclamation mark
do you any other suggestions I could try?
Kako Je? Testing ...
Sent from my Desire HD using XDA App
kufertreger said:
Kako Je? Testing ...
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I'm sorry, but I don't understand your post. Does it have something to do with the discussion?
I'm getting the same red triangle and I've also tried your solution but still no joy
You are rooted, but are you s-off? You need s-off to bypass the emmc lock on your phones memory.
If you have only root, anything you flash will disappear back to stock whenever you reboot.
Sent from my performance enhanced Desire HD.
dr.m0x said:
You are rooted, but are you s-off? You need s-off to bypass the emmc lock on your phones memory.
If you have only root, anything you flash will disappear back to stock whenever you reboot.
Sent from my performance enhanced Desire HD.
Click to expand...
Click to collapse
Thanks for your reply, I am currently S-ON, which probably explains the issues I'm having. Could you point me in the direction of a straightforward guide for turning S-OFF for the DHD?
You can take a look here, here or here, for example. Or maybe next time you could try to use that funny button with "SEARCH THIS FORUM" written on it.
capt_harlock77 said:
You can take a look here, here or here, for example. Or maybe next time you could try to use that funny button with "SEARCH THIS FORUM" written on it.
Click to expand...
Click to collapse
I have managed to get S-OFF and I'm successfully running CyanogenMod 6.1.2 It feels like i've set my phone free, it's much faster and the additional options and tweaks are very much appreciated!
Now it's time for a faster kernel
Thanks has been given to all who helped in the thread
Happy New Year to you all tomorrow!
Is it possible to install the new update with s-off. I have a stock rom and read the new update supposed to fix the battery threshold and I like the look. I know its not rootable yet but ive been reading some have been successful and just put amon ra recovery on it.Anyone know?
Sent from my HTC Evo using XDA Premium App
My cousin installed it and his WiFi tether works and he is able to nand backup
Sent from my PC36100 using XDA Premium App
You can just get the rooted version of it on this site if you do the ota you will lose root and so far there is no way to get it back yet .
Sent from my PC36100 using XDA App
Why install the OTA when there are complete ROMS here that are better than what you're gonna have with stock 2.3.3???
mizzouse said:
Is it possible to install the new update with s-off. I have a stock rom and read the new update supposed to fix the battery threshold and I like the look. I know its not rootable yet but ive been reading some have been successful and just put amon ra recovery on it.Anyone know?
Sent from my HTC Evo using XDA Premium App
Click to expand...
Click to collapse
It is possible if you're s-off with Unrevoked Forever on Froyo. I had to switch to Amon Ra in order to install the update and then reflash Amon Ra after the update. Had to update Superuser after that but after that was fully rooted on the update.
There are several stock rooted versions of the OTA available, there's no reason that you need to lose root just to have the latest update.
If you are keen on losing root though, then go for it. You can install it with S-Off just fine, and since it'll remain S-Off you'll be able to flash a recovery on there and re-root by flashing a rooted rom.
If your intent is to have the latest update but also have root, then just flash one of the already-rooted stock roms available in the Android Development forum.
To hip kat, I actually don't like any custom roms, I'm an ogee only person and I tweak what I want or need myself. To tempe, how did you get clockwork off first assuming you had it? Also I used the unrevoked3 method but since mine is sprint, it automatically does a perm nand unlock.
Sent from my PC36100 using XDA Premium App
mizzouse said:
To tempe, how did you get clockwork off first assuming you had it?
Click to expand...
Click to collapse
Well, easiest is to just use Rom Manager to flash alternate recovery, that's what I did before running the OTA. After, you'll need to do it manually. If you search here on "recovery" you should find threads that have the pc36img.zip files for both Clockworkmod and Amon Ra. After installing the OTA, turn off the fastboot option under Settings/Applications. Copy the pc36img.zip file for the recovery you want to use to the SD card, shut down your phone and then hold volume down while turning it back on. Just follow the prompts on the screen from there. After the recovery is installed you should be able to boot up and have root. If the Superuser app give you FC's search around here for the fixed superuser zip and flash it.
You can go S-on with the Unrevoked S-On tool....
I don't want s-on hip, trying to keep s-off. And thanks tempe for your help.
Sent from my HTC Evo using XDA Premium App
Ok turns out im having problems installing the update, I forgot I deleted system apps. Here's the error:
assert failed: apply_patch_check /system/app/Blockbuster_htc.apk 2eE:unknown command etc etc, ideas?
mizzouse said:
Ok turns out im having problems installing the update, I forgot I deleted system apps. Here's the error:
assert failed: apply_patch_check /system/app/Blockbuster_htc.apk 2eE:unknown command etc etc, ideas?
Click to expand...
Click to collapse
According to the error you posted, it's just the blockbuster app that your missing. Did you uninstall other system apps? Or just that. You need to have all your system apps installed for it to work. I'll attatch the blockbuster app for you. You'll need to install it to /system/app using ADB or using Root Explorer. If adb, do this
adb remount
adb push Blockbuster_htc.apk /system/app
adb reboot
If using root explorer, just copy the apk to the /system/app folder and set the permissions the same as all the other apps in the system folder.
Also, it would be much easier for you just to flash a rooted stock rom. Here's a link for ya. You'd just flash the rom like normal, from within recovery. It'd save you some hassle.
http://forum.xda-developers.com/showthread.php?t=1038701
mizzouse said:
Ok turns out im having problems installing the update, I forgot I deleted system apps. Here's the error:
assert failed: apply_patch_check /system/app/Blockbuster_htc.apk 2eE:unknown command etc etc, ideas?
Click to expand...
Click to collapse
You do know there are rooted stock versions out there and like others have said no need to unroot then root again... SMH
playya said:
You do know there are rooted stock versions out there and like others have said no need to unroot then root again... SMH
Click to expand...
Click to collapse
NOOOOO, you're not suppose to tell him..lol! I would of love for him to flash the new update and then complain about how he can't root his phone and how he wants to come back..haha
skcussrepolevedadx said:
NOOOOO, you're not suppose to tell him..lol! I would of love for him to flash the new update and then complain about how he can't root his phone and how he wants to come back..haha
Click to expand...
Click to collapse
As much as I would love to see that happen (for my own amusement), I do believe in bad karma and if you let someone do that knowing what they're about to get into then you're properly gonna get the bone too......who knows, your phone might just blow up on the way to work while you're playing angry birds or some crap...hahahaha
I've already chosen to just do the rooted ota but I'm trying to figure out if I need to flash the radio. The second link in the topic is showing 2.15.00.04.08 but mine is higher at 00.11.19. The combined link with pri and wimax is the one I don't know yet
Sent from my PC36100 using XDA Premium App
mizzouse said:
I've already chosen to just do the rooted ota but I'm trying to figure out if I need to flash the radio. The second link in the topic is showing 2.15.00.04.08 but mine is higher at 00.11.19. The combined link with pri and wimax is the one I don't know yet
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I don't believe flashing the radio is necessary if you're doing the stock ota, I didn't have any issues with my current radio while I was using stock 2.3.3 (or any other ROM that I've used so far)
Alright I did the de-odex rooted ota but now the problem is once booted up, I cant update the prl or profile, it gives me an error. Im re-wiping the dalvik cache to see if that fixes it but is there any other steps I should try?
Side question, is a stock rom that came with the phone or an ota update a odex or de-odex?
Thanks for this thread, I have been searching high & low to see if S-Off would stay off or automatically turn back on. Thanks for the clarification!
Verified!
pnewgaard said:
Thanks for this thread, I have been searching high & low to see if S-Off would stay off or automatically turn back on. Thanks for the clarification!
Click to expand...
Click to collapse
I ended up testing myself to know for sure and S-Off will stay off if you do the OTA update. If you want to start rooting again, just download Amon_Ra Recovery, and Bam, flash any Rom you want! Thanks for the starting of the thread! Confirmed!
First I wanted to say hi to all of you. Evo 4G is my second Android phone. I'm still a noob in training but I'm getting by.
I'm having a bit of a issue with trying to use some apps for root only and keep getting that I need to be rooted. Yes S-Off is displayed but I'm still running into this issue no matter what. Did I miss something? I'm still searching the forum to find a answer but I haven't found anything as of yet.
Let me know what you guys think.
Thanks
Z3r0
Edit: I figured out what the problem was. Me being stupid and not reading enough. Mods go ahead and lock/delete this thread.
to double check, there is an app in the market called "root check" by joeykrim.
and for apps to gain access to the phone you should have the app "superuser" it gives other apps permission to access root.
As someone previously stated, you'll need an app called "superuser" to allow apps to use root permissions.
Greenfieldan said:
As someone previously stated, you'll need an app called "superuser" to allow apps to use root permissions.
Click to expand...
Click to collapse
This.
Running Revolutionary Roots your phone, but you need superuser to give programs root access. To give programs root access, you will need a rooted ROM with the superuser application or just download the superuser app.
oldwesterncowboy said:
to double check, there is an app in the market called "root check" by joeykrim.
and for apps to gain access to the phone you should have the app "superuser" it gives other apps permission to access root.
Click to expand...
Click to collapse
Yeah I figured that out after reading the sticky at the beginning. My fault for not paying attention. I'm now rooted and loving it.
Thanks for the reply's guys.
I really did it now!!!
Ok so I'm back to ask some questions due to a noob mistake. Now I have been reading many of the threads that are available to fix my actual issues that I'm dealing with. I'm going to be very detailed so I apologize in advance.
So like a dumb dumb I decided to unroot my Evo as I was sure/ uncomfortable using the rooted OTA update to up date. So now I did some more reading and I did not need to unroot. Sorry I dont' know what I was thinking.
I've tried to run Revolutionary but all it does is aborts the operation everytime. I tried to change the recovery from Clockwork to Amon RA as I read that it is better so I tried to do that too. Nope that doesn't work either.
I was able to update the root OTA update but that was all that was done. So now I'm here asking for more help as I did more reading how to fix the current issue I'm having and its not working.
PLEASE Help me or guide me in the right direction to fix this.
This is all I am trying to accomplish:
1. Figure out why and what happend and get my Evo rooted
2. Apply the Amon RA recovery
Now if I need to completely wipe my phone I will do it if that is what you think is needed to be done. I know how to back up my app/ contacts etc. So just assist this dumb dumb please!
Anyone have any ideas?
Sent from my PC36100 using xda premium
So are you s on or s off when you go into hboot?
Sent from my PC36100 using Tapatalk
revolutionary s-off
Another noob here.... Ok I used revolutionary.io to root my 2.3.3
Hboot says s-off, downloaded superuser app, and astro file
Why does it say can't delete file when I try to delete pre installed files like Amazon mp3, ect
Ran root checker app from market said
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.5 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location:
/sbin/su: Permission denied
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
tommytomatoe said:
So are you s on or s off when you go into hboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
s on which I know is not rooted. No matter what I try it refuses to accept the revolutionary root program. Should I try a different root method or is Revolutionary for 2.3.3 the only method? I've looked and can't find any other way.
z3r0t0l0rEnCe said:
s on which I know is not rooted. No matter what I try it refuses to accept the revolutionary root program. Should I try a different root method or is Revolutionary for 2.3.3 the only method? I've looked and can't find any other way.
Click to expand...
Click to collapse
What is your HBOOT version, when you go into Bootloader?
Last I checked revolutionary won't s-off anything besides hboot 2.15 & 2.16. Not even the revolutionary hboot 6.xx
tapatalk signature here. lovely.
2.16
Sent from my PC36100 using xda premium
z3r0t0l0rEnCe said:
2.16
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
First, I would flash an unrooted stock ROM - the latest, if possible (see this post).
Then, try rooting via Revolutionary again (revolutionary.io). Sometimes during the unrooting process, everything isn't completely restored to stock, so you might just need to flash a completely stock ROM to get back to the point where Revolutionary will work again.
Captain_Throwback said:
First, I would flash an unrooted stock ROM - the latest, if possible (see this post).
Then, try rooting via Revolutionary again (revolutionary.io). Sometimes during the unrooting process, everything isn't completely restored to stock, so you might just need to flash a completely stock ROM to get back to the point where Revolutionary will work again.
Click to expand...
Click to collapse
Thanks for the heads up on this info. Now with the Stock RUU being RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15 .00.0808_NV_2.15_release, does the 2.15 represent the HBOOT? As mine is the 2.16 or does that not matter?
z3r0t0l0rEnCe said:
Thanks for the heads up on this info. Now with the Stock RUU being RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15 .00.0808_NV_2.15_release, does the 2.15 represent the HBOOT? As mine is the 2.16 or does that not matter?
Click to expand...
Click to collapse
The file name has nothing to do with the HBOOT version. It doesn't matter. If the HBOOT version you currently have is newer than the version in the RUU, it will simply skip updating it.
Ok ill test it when I get home from work tonight.
Sent from my PC36100 using xda premium
z3r0t0l0rEnCe said:
I've tried to run Revolutionary but all it does is aborts the operation everytime. I tried to change the recovery from Clockwork to Amon RA as I read that it is better so I tried to do that too. Nope that doesn't work either.
Now if I need to completely wipe my phone I will do it if that is what you think is needed to be done. I know how to back up my app/ contacts etc. So just assist this dumb dumb please!
Click to expand...
Click to collapse
All you need to is flash another hboot for the evo. (Any of them will work. Doesn't really matter. Look around for the files and a guide is out there I'm sure. If not, PM me. Anyway, flash it. And then run revolutionary. It should work then.
I did not know that, tommytomatoe. But regardless, what I suggested would work if my thinking is correct.
IamNotSureX said:
All you need to is flash another hboot for the evo. (Any of them will work. Doesn't really matter. Look around for the files and a guide is out there I'm sure. If not, PM me. Anyway, flash it. And then run revolutionary. It should work then.
I did not know that, tommytomatoe. But regardless, what I suggested would work if my thinking is correct.
Click to expand...
Click to collapse
He said he has Hboot 2.16. If I'm not mistaken you cannot downgrade your Hboot version from something like 2.16 to 2.15 or 2.10. Either way, Revolutionary will be able to root 2.16 just fine. Seems like all he needs to do is follow Captain Throwbacks advice to get his phone out of "What the hell are you doing to me" mode.
I have yet to perform the flash. I got caught up at work late last night. I'll do it tonight for sure when I get off work.
Thank you all for the input and I'll let you all know if my Evo will let me get it out of ""What the hell are you doing to me" mode.