ok. ive used the one click root... ive used the script root method... downloaded the correct files. but i can't seem to get root.... both methods says i have root and its good to go but no superuser icon and i even tried using the one on the market just incase i need to... nothing still and ive tried over hours and hours... i don't know what else to do... anyone?
Use the fixed superuser posted on these forums.
Sent from my ADR6400L using XDA App
i can't even get root permission to log into cwk. to flash it.
dadsterflip said:
i can't even get root permission to log into cwk. to flash it.
Click to expand...
Click to collapse
i didn't do the one click root, but, in the long root version, and I am sure it is the same, you need to install SU from the market, and then if you do not get SU access right away, reboot the phone a couple times.
If you turn your phone off, and then back on while holding vol down and power, does it say MECH S-OFF at the top? If it still says S-ON or security warning, you didn't root your phone right, if it says S-OFF your rooted, and you just need to get SU working by rebooting a few times.
nosympathy said:
i didn't do the one click root, but, in the long root version, and I am sure it is the same, you need to install SU from the market, and then if you do not get SU access right away, reboot the phone a couple times.
If you turn your phone off, and then back on while holding vol down and power, does it say MECH S-OFF at the top? If it still says S-ON or security warning, you didn't root your phone right, if it says S-OFF your rooted, and you just need to get SU working by rebooting a few times.
Click to expand...
Click to collapse
Hope that works for them. I wonder if fastboot, where it doesnt shut the phone down 100% and suspends the phone in memory, could be an issue or no?
nosympathy said:
i didn't do the one click root, but, in the long root version, and I am sure it is the same, you need to install SU from the market, and then if you do not get SU access right away, reboot the phone a couple times.
If you turn your phone off, and then back on while holding vol down and power, does it say MECH S-OFF at the top? If it still says S-ON or security warning, you didn't root your phone right, if it says S-OFF your rooted, and you just need to get SU working by rebooting a few times.
Click to expand...
Click to collapse
ill redo it and do this. thx
the only problems root wise i ran into (and i did it the adb way) was super user wouldnt initially give rights. I solved this each and everytime by one reboot. (clockwork i didnt have rights) restarted phone superuser came up with the box for me to give cw rights. Then i installed Tit backup form the market. No rights again, a restart and problem solved. Dont know why it was buggy but try that.
is it normal to see. usb device not recognized? while its on the hboot loading the update through? it only says that while its updating the hboot or loading the PG05IMG.zip. otherwise i have all the right drivers for it.
update.... still not luck. i used the script root... at the end i have s-on.... on the first downgrade i have s-off but at the very end of the script to add the other update ppg05img, it turns the s-on back... sooooo whats wrong with it or what am i doing wrong?
if your having that many issues with the quick root method (ill be honest I havent looked at the instructions for it) i really would suggest doing it manually (the method that was first released). I wanted to post the links for you but i dont have enough posts yet to do so. The instructions i used are on droid-life . com. Once your there go to search and type in thunderbolt root. Another one click root method will be the first topic. Go there and youll see two hyperlinks (here) and (here) in the first paragraph.Click the second one and youll see the list of instructions and a link to a video, showing you how to do it. The original video is very fast but once it starts playing it will give you step one and step two links. This video is very helpful and very detailed. Anyway hope that helps.
Any questions leave a post.
update. finally got root... manual way. thx for the help guys.
dadsterflip said:
update. finally got root... manual way. thx for the help guys.
Click to expand...
Click to collapse
no problem man hope i was a help.
dadsterflip said:
update. finally got root... manual way. thx for the help guys.
Click to expand...
Click to collapse
now you can rest easy that in the future if you screw up your tbolt you understand how adb works enough to probably fix it comfortably.
Amen to that.
Sent from my ADR6400L using XDA Premium App
Related
Rooted last night, superuser was working fine but this morning I lost all superuser access. Uninstalled SU and reinstalled it. Rom manager gained access but others won't. Now even when I try to flash CWM recovery it says "an error occurred while attempting to run privileged commands!". Any ideas?
you might have to look in this thread, and get the working SU that way
http://forum.xda-developers.com/showthread.php?t=1003088
magneticzero said:
you might have to look in this thread, and get the working SU that way
http://forum.xda-developers.com/showthread.php?t=1003088
Click to expand...
Click to collapse
Thanks, I was reading over that a few minutes ago. I'll give it a try
Tried to flash that patch but I can't boot into recovery. It boots into the bootloader, I select recovery and it just goes back to the white bootloader screen. Am I missing something?
since su works with rom manager, press menu and clear cache and try to push clockwork back on your phone. also there is a option to wipe clockwork mod everytiem you update it. alot of people have success with that.
magneticzero said:
since su works with rom manager, press menu and clear cache and try to push clockwork back on your phone
Click to expand...
Click to collapse
I did that, rebooted like 10 times trying to get into recovery and for some reason I know have su permissions again.... I dunno what happened.
But how do I get into cwm to install rom's and backup/restore? I keep getting the white bootloader screen for some reason.
Sorry, double post....
ugadroid said:
I did that, rebooted like 10 times trying to get into recovery and for some reason I know have su permissions again.... I dunno what happened.
But how do I get into cwm to install rom's and backup/restore? I keep getting the white bootloader screen for some reason.
Click to expand...
Click to collapse
there is an option in rom manager to boot into clockwork recovery, but i edited my last post.. maybe you need to push clockwork again if it isnt going into recovery the manual way, might not be loading the files properly
magneticzero said:
there is an option in rom manager to boot into clockwork recovery, but i edited my last post.. maybe you need to push clockwork again if it isnt going into recovery the manual way, might not be loading the files properly
Click to expand...
Click to collapse
Seems like something might have gotten messed up. Now I lost all su permissions again. lol. I probably should unroot and do the process over again. I've tried the option in rom manager but it takes me to the bootloader screen and when I select recovery it just takes me right back.
I also had this same exact problem. The reason was I had messed something up during the root process. What happened to me is I switched the RUU's around and ended up with the wrong one. My opinion would be to re-root using the original ADB method and make sure you are using the correct RUU. If you need assistance just PM me and I will guide you step through step to re-rooting your T-Bolt.
stedrocklp said:
I also had this same exact problem. The reason was I had messed something up during the root process. What happened to me is I switched the RUU's around and ended up with the wrong one. My opinion would be to re-root using the original ADB method and make sure you are using the correct RUU. If you need assistance just PM me and I will guide you step through step to re-rooting your T-Bolt.
Click to expand...
Click to collapse
I thought for sure I used the right RUU files but it was late so I could have messed up. I would appreciate any help, I used the windows one click method. Not too familar with ADB but I have played with it a lil. PM me when ever you get a chance. Thanks bro.
Mad props to stedrocklp for all the help last night. The help that people give on this site is why it's the best.
read this before you brick your device. It will only take 5 mins of your time. THIS DOES NOT INSTALL ROOT only s-off and it is permanent on the 3vo and sensation. Root can be downloaded from the link, as well as instructions/
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
thanks and hope this helps some of you
I am s-off, rooted, and have a working recovery that is nandroiding my phone as we speak
*MODS*
I am only starting this thread to help, i see a lot of people having issues/ Please move if you need too.
Thanks,
welrope said:
read this before you brick your device. It will only take 5 mins of your time. THIS DOES NOT INSTALL ROOT only s-off and it is permanent on the 3vo and sensation. Root can be downloaded from the link, as well as instructions/
http://unrevoked.com/rootwiki/doku.p.../revolutionary
thanks and hope this helps some of you
I am s-off, rooted, and have a working recovery that is nandroiding my phone as we speak
*MODS*
I am only starting this thread to help, i see a lot of people having issues/ Please move if you need too.
Thanks,
Click to expand...
Click to collapse
your link is broken. error 404
bradbusa said:
your link is broken. error 404
Click to expand...
Click to collapse
Thanks for the heads up, it works now!
It only says to flash su zip from recovery but doesn't say how to get recovery, any tut on how to get recovery?
Sent from my PG86100 using XDA Premium App
-eVo- said:
It only says to flash su zip from recovery but doesn't say how to get recovery, any tut on how to get recovery?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1192245
good directions in the first post
The root file is not downloading for me from the goo.me site. Will someone please post a different link for the su file to root. Thanks
TheMike1 said:
The root file is not downloading for me from the goo.me site. Will someone please post a different link for the su file to root. Thanks
Click to expand...
Click to collapse
http://dl.dropbox.com/u/26733192/su-2.3.6.3-efgh-fixed-unsigned.zip
here ya go....this one worked for me....all apps work now
How to Enter Recovery/Clockworkmod
1. Unplug USB
2. Turn the device off
3. Hold volume down button (HOLD IT) and press power
4. Hboot will start. Navigate to recovery with the vol down button. Press power to select and enter recovery.
Regards,
JDC4429
also make sure htc sync is uninstalled, simply being disabled will not help.
franky_402 said:
also make sure htc sync is uninstalled, simply being disabled will not help.
Click to expand...
Click to collapse
That's not true. I just exited out of it in the taskbar and everything worked.
mwalt2 said:
That's not true. I just exited out of it in the taskbar and everything worked.
Click to expand...
Click to collapse
so then if it is just disabled it still must have some processes running that is interfering with revolution. Fully exiting must close everything then. As long as it works.
Just so everyone knows when my wouldnt work it was sitting at
acquiring root (method 3)...
so if that is happening to anyone make sure htc sync is fully exited or uninstalled! I never used htc sync i had just installed it for drivers so it was no big deal to me to uninstall!!
I have uninstalled HTC sync and am still stuck at acquiring root (method 3)
Sorry for the subject. Didn’t know how to summarize what happened.
I rooted my phone successfully about a year ago. It worked fine, no problems. A few months later I went to use the WiFi Tether app, and it said tethering started with errors. When I clicked the error it said - Wi-Fi Tether has been denied by SuperUser permissions.
I immediately logged into Titanium Backup Pro and it said root access has failed, followed by this error: Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted and included BusyBox, and try again. This attempt was made using the "/system/bin/su" command.
I really haven’t had time to troubleshoot this before, but I have a few days free and was bored. However it's been so long that (1) I can't remember what steps I took to root it the first time, and (2) I’m not sure how to fix it from this point? I started researching how to update to Jellybean, but I need to figure this out before I possibly brick it trying JB.
I'm a little confused as to why a root would no longer work out the blue? Does the carrier (Sprint) send updates similar to iOS? What really confused me is when I power down and plug in the power cord, I still get that black screen, green font, which prompts me to reboot, boot from SD, etc. Assuming that means I can use that screen to boot a ROM and try to re-root it?
I'm a bit lost and not sure where to start...again.
First of all check superuser application.
may be you deleted it accidentally.
Sent from my MB855 using Tapatalk 2
pradeeppk said:
First of all check superuser application.
may be you deleted it accidentally.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
When I checked Superuser, it said "Last allowed on 6/23/2012 at 4:47"
The log showes Titanium Backup & WiFi Tether denied.
Is there a user guide for using this SuperUser. I am an IT guy, but need to be approached like a noob.
6thSense said:
When I checked Superuser, it said "Last allowed on 6/23/2012 at 4:47"
The log showes Titanium Backup & WiFi Tether denied.
Is there a user guide for using this SuperUser. I am an IT guy, but need to be approached like a noob.
Click to expand...
Click to collapse
Whenever this happened to me I just typically reflashed. I think it's a kernal thing. I'm not too sure, but after updating everything all was better. I think I flashed a different kernal by this point. Hope this helps.
krnfrk6663 said:
Whenever this happened to me I just typically reflashed. I think it's a kernal thing. I'm not too sure, but after updating everything all was better. I think I flashed a different kernal by this point. Hope this helps.
Click to expand...
Click to collapse
Dumb question, but the kernal is the ROM, correct? I'm not even sure which one I used. Sad, huh? Any way I can see that through that initial screen or through Titanium?
6thSense said:
Dumb question, but the kernal is the ROM, correct? I'm not even sure which one I used. Sad, huh? Any way I can see that through that initial screen or through Titanium?
Click to expand...
Click to collapse
Kernals are separate from the Rom, stock has their own, developers had custom ones as well. You can see the kernel type you have in about phone. If a Rom comes with a kernel, they usually point that out. Look into it. I'm not 100% knowledgeable on it.
I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
antisomnic said:
I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
Click to expand...
Click to collapse
Cool! Glad you are up and running.
The MI1 root method flashed a MI1 ROM, so if you are on MJ7, you create a soft brick by trying to root.
Don't do that!!!!
Right. I figured that out the hard way. At least there is a solution
Sent from my SCH-I545 using xda app-developers app
Were you able to boot into android recovery while soft bricked? I experienced the same issue and booted into recovery (volume up, center button, and power button while power is off) and simply did a factory reset. I was able to keep root and fix whatever had gone wrong.
Nevermind, read wrong.
Can be deleted.
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
slackwaresupport said:
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
Click to expand...
Click to collapse
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
just tried to flash ml1.. failed on system.img.ext4
slackwaresupport said:
just tried to flash ml1.. failed on system.img.ext4
Click to expand...
Click to collapse
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
-Lawless said:
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
Click to expand...
Click to collapse
I was in that boat. Took the OTA and foolishly tried Root de la Vega. Couldn't flash back to MI1 (failed as described) but the new no-wipe MJ7 Odin file saved the day. Good as new (but still unrooted).
http://forum.xda-developers.com/showthread.php?t=2507217
I got root with this post: http://forum.xda-developers.com/showpost.php?p=47187227&postcount=84
As other say, it seems to be bad.
I cleared this post and if you wish, you can check the first line and open the post to see how it goes.
TheJumpingBean said:
You will prolly get banned for this! LOL Either way, it does work. I did it on mine, and all of that is true.
Click to expand...
Click to collapse
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Trak-X said:
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Click to expand...
Click to collapse
No there were some xda admins or w/e that said the links 2 this root arent allowed on XDA ne more. Not sure why... I used it and it worked perfectly. oh well. Sowwy
Moderator @Naddict posted this one post prior in that thread. Read up and learn about the risk you are exposing yourself to.
Be aware that as of this moment XDA has deemed the Kingo root method and Vroot method are not allowed on XDA. There are concerns with the information which is collected during the root method by the exploit. It is not about a continuous malware which may affect your device but about important information shared about your device, serial numbers etc during the root process which could be huge securities issues. You have all been warned.
Click to expand...
Click to collapse
This post, courtesy of open1your1eyes, provides some detail from the bright guys that keep us rooted and happy.
We finally have some details on these root methods:
https://twitter.com/TeamAndIRC/status/397767301811802112
TLDR: Uses "Romaster" root method
Click to expand...
Click to collapse
I would take their caution to heart if I was in your position.
--OctOS Powered VZW GS4 Dev Edition
Nice to see the wheels turning here guys. Thumbs up
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
Im go the problem where it says Firmware upgrade encountered an issue. how do i fix this? and can u provide a link for the stock firmwares please the mi1 and mj7.
TheJumpingBean said:
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
Click to expand...
Click to collapse
How'd you get supersu to work and remove Chinese superuser?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hey all, I got a Verizon Galaxy S4 16 gigs. I did the 4.3 OTA, then tried to go back to 4.2.2. I guess that soft bricked it. So do I have to use the MJ7 firmware to make my phone usable again? And if that works, is there any way to go back to 4.2.2? What do I do if it doesn't work?
Update: This worked beautifully, I'm now back to 4.3.
It has been over a year since I got this phone. Normally, I rooted the day I received a new phone. But I didn't think that I had any reason to do so this time until I bought a Chromebook. Now I really need to tether.
Can someone show me where to start? It seems that most the threads I have looked at are pretty old and just spent a couple of hours going no where.
Current software is 4.4.2.
Thanks.
realsol said:
It has been over a year since I got this phone. Normally, I rooted the day I received a new phone. But I didn't think that I had any reason to do so this time until I bought a Chromebook. Now I really need to tether.
Can someone show me where to start? It seems that most the threads I have looked at are pretty old and just spent a couple of hours going no where.
Current software is 4.4.2.
Thanks.
Click to expand...
Click to collapse
http://rumrunner.us
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Does rumrunner work on 4.4.2? If not you may need to use firewater instead.
Drunkula said:
Does rumrunner work on 4.4.2? If not you may need to use firewater instead.
Click to expand...
Click to collapse
Firewater definitely works. I just got a DNA last night, running 4.4.2 and locked up. Temp rooted and ran Firewater and literally about 5 mins later I am unlocked and S-Off. :good:
OP did rumrunner work for you? I'm in the same situation trying to get hotspot to work after the KitKat update. Thanks
vjetti said:
OP did rumrunner work for you? I'm in the same situation trying to get hotspot to work after the KitKat update. Thanks
Click to expand...
Click to collapse
You could use pdanet
Sent from my HTC6600LVW using XDA Premium 4 mobile app
I rooted and unlocked the bootloader on the OTA Kit Kat. I thought it wasn't possible at first, but Weaksauce and Firewater will do it.
mulhiny said:
Firewater definitely works. I just got a DNA last night, running 4.4.2 and locked up. Temp rooted and ran Firewater and literally about 5 mins later I am unlocked and S-Off. :good:
Click to expand...
Click to collapse
Could you possibly give me more details on how you did this. It has been more then 2 years since I rooted anything and I don't want to do anything wrong. Since you were successful with the same phone and software I have I would really appreciate it.
realsol said:
Could you possibly give me more details on how you did this. It has been more then 2 years since I rooted anything and I don't want to do anything wrong. Since you were successful with the same phone and software I have I would really appreciate it.
Click to expand...
Click to collapse
Hi there. First thing is making sure you have all the proper drivers installed and HTC Sync uninstalled.
I then installed the app to temp root and ran Firewater. The terminal commands are on the firewater site....if you need more detail or even a step by step, I'm happy to help and write something up. I just can't tonight as I have an obligation to attend to.
Let me know how you make out and if you need additional assistance I'll write something up tomorrow around this time.
Sent from my thumbs
mulhiny said:
Hi there. First thing is making sure you have all the proper drivers installed and HTC Sync uninstalled.
I then installed the app to temp root and ran Firewater. The terminal commands are on the firewater site....if you need more detail or even a step by step, I'm happy to help and write something up. I just can't tonight as I have an obligation to attend to.
Let me know how you make out and if you need additional assistance I'll write something up tomorrow around this time.
Click to expand...
Click to collapse
Thanks for the reply. I have the instructions for Weaksauce and Firewater, but I don't want to make any mistakes here.
Where can I find the latest HTC DNA drivers without installing the HTC Sync program?
Where can I find the latest ADB download?
It looks like these are the last things I need to find before continuing.
I'm at work, but this evening I'll either find you a link or upload them to my dropbox. Hang in there...I'll help ya out lol...soon as you have everything, its literally like a 5 min process.
Sent from my thumbs
mulhiny said:
I'm at work, but this evening I'll either find you a link or upload them to my dropbox. Hang in there...I'll help ya out lol...soon as you have everything, its literally like a 5 min process.
Sent from my thumbs
Click to expand...
Click to collapse
Thanks. You have been very helpful. I have rooted 6 devices without a problem, but always rooted when the device was new along with the tools to root. Alwayw made me nervous though.
Thanks again...
realsol said:
Thanks. You have been very helpful. I have rooted 6 devices without a problem, but always rooted when the device was new along with the tools to root. Alwayw made me nervous though.
Thanks again...
Click to expand...
Click to collapse
Haven't forgotten ya...I'm just getting home. Have a few things to attend to.
You can get the HTC drivers from this post right here : http://forum.xda-developers.com/showthread.php?t=2000896
Ok, download the SDK from here : http://developer.android.com/sdk/index.html?hl=sk
Make sure USB debugging is turned on. Install the attached weaksauce apk for temp root. You can verify you're rooted by downloading superSU and root checker from the play store.
Unpack the SDK and you'll want to put the firewater file in the folder titled : adt-bundle-windows-x86_64-20140321
Open a terminal from this folder by holding down shift and right clicking the folder, "open command window here"
Follow the commands given on the firewater site.
Profit.
Once S-off and unlocked go to the TWRP thread in original development and download a recovery. Flash that via fastboot.
Then flash super user zip for root...again, search that out. I'm running out of time so I can't right now...lol
This is all I did. Collect all your files first. Make sure your drivers are good to go before starting. Install the drivers, reboot the pc and plug the phone into the usb. Likely a driver install thingy will pop up with like 5 little circles...let it finish before you begin.
Good luck bro...I'll check in tomorrow or later tonight to see how you made out.
**I take no credit for any files linked or attached.**
Sent from my living room
Good luck bro...I'll check in tomorrow or later tonight to see how you made out.
**I take no credit for any files linked or attached.** [/QUOTE said:
Thanks much. I will get started tonight and let you know how it goes. Thanks for taking the time on a Friday night.
Click to expand...
Click to collapse
mulhiny said:
Haven't forgotten ya...I'm just getting home. Have a few things to attend to.
You can get the HTC drivers from this post right here : http://forum.xda-developers.com/showthread.php?t=2000896
Ok, download the SDK from here : http://developer.android.com/sdk/index.html?hl=sk
Make sure USB debugging is turned on. Install the attached weaksauce apk for temp root. You can verify you're rooted by downloading superSU and root checker from the play store.
Unpack the SDK and you'll want to put the firewater file in the folder titled : adt-bundle-windows-x86_64-20140321
Open a terminal from this folder by holding down shift and right clicking the folder, "open command window here"
Follow the commands given on the firewater site.
Profit.
Once S-off and unlocked go to the TWRP thread in original development and download a recovery. Flash that via fastboot.
Then flash super user zip for root...again, search that out. I'm running out of time so I can't right now...lol
This is all I did. Collect all your files first. Make sure your drivers are good to go before starting. Install the drivers, reboot the pc and plug the phone into the usb. Likely a driver install thingy will pop up with like 5 little circles...let it finish before you begin.
Good luck bro...I'll check in tomorrow or later tonight to see how you made out.
**I take no credit for any files linked or attached.**
Sent from my living room
Click to expand...
Click to collapse
Well, didn't work for me. I am guessing I might have tried to root months ago. I drank a lot back then. When I ran WeakSauce, it said I was already rooted and did nothing. Then I ran Root Check, and it said I wasn't rooted. But I moved on through the steps. But when I got to the last step in FireWater, it said I need to run as root.
I noticed I had SuperSU app installed. So I uninstalled that, uninstalled WeakSauce, re-installed both and started over, but got the same results.
Not sure where to go from here. I almost feel like I should just do a Factory Reset and start over, but that could really screw things up too.
Man, sure am sorry to hear that..maybe a full RUU would fix you up. Then start over...I'm not sure. Maybe someone with more in depth knowledge needs to chime in here..
bummer.....
mulhiny said:
Man, sure am sorry to hear that..maybe a full RUU would fix you up. Then start over...I'm not sure. Maybe someone with more in depth knowledge needs to chime in here..
bummer.....
Click to expand...
Click to collapse
You know, now that I think about it, I did have full root before, but I wasn't thinking one night and got an OTA update that made me loose root. Maybe that is why I can't use weaksauce. I decided to start in my bootloader. Attached is a screen shot. Tried to go into recovery, but that failed. Just came up with a picture of a battery or something. Had to hold the power button down for 10 seconds just to boot normally.
Does the screen shot tell you anything? It tells me, I think, that the phone is S-off'ed and unlocked. but firewater complained about not being rooted. I am confused.
realsol said:
You know, now that I think about it, I did have full root before, but I wasn't thinking one night and got an OTA update that made me loose root. Maybe that is why I can't use weaksauce. I decided to start in my bootloader. Attached is a screen shot. Tried to go into recovery, but that failed. Just came up with a picture of a battery or something. Had to hold the power button down for 10 seconds just to boot normally.
Does the screen shot tell you anything? It tells me, I think, that the phone is S-off'ed and unlocked. but firewater complained about not being rooted. I am confused.
Click to expand...
Click to collapse
Hey, your phone is already unlocked! So just flash supersu thorough Fastboot to get root.
realsol said:
You know, now that I think about it, I did have full root before, but I wasn't thinking one night and got an OTA update that made me loose root. Maybe that is why I can't use weaksauce. I decided to start in my bootloader. Attached is a screen shot. Tried to go into recovery, but that failed. Just came up with a picture of a battery or something. Had to hold the power button down for 10 seconds just to boot normally.
Does the screen shot tell you anything? It tells me, I think, that the phone is S-off'ed and unlocked. but firewater complained about not being rooted. I am confused.
Click to expand...
Click to collapse
As said right above me....you're all set to go. Use fast boot to push a recovery and then flash super su zip. If you need the zip I can attach it later.
Sent from my living room
mulhiny said:
As said right above me....you're all set to go. Use fast boot to push a recovery and then flash super su zip. If you need the zip I can attach it later.
Sent from my living room
Click to expand...
Click to collapse
Funny. There have been other threads where people are asking how to root DNA 4.4.2. They have been referring them to this thread So I guess I am not SO dumb.
Anyhow, as I remember, there are a couple of ways to flash. 1) from the PC using ADB and from the phone using an IMG file right? What is the easiest way to flash the Recover file? Which version of ClockWorkMod is going to be compatible with 4.4.2 and where would I find the download? Also, one last question, which SuperSU version is going to be compatible and where is the best download?