Database Users

Problem - lost my data connection after rooting

I just rooted and S-OFFed my Z using Visionary r14 and the method here: http://forum.xda-developers.com/showthread.php?t=835777
Now I have no data connection, either through wifi or the phone network. It was perfectly fine before I rooted :-(
Any ideas, you clever people? I did search, but turned nothing up.
Baseband version
12.28b.60.140eU_26.03.02.26_M
Kernel version
2.6.32.21-gd2764ed
[email protected] #1
Tue Oct 26 16:04:03 CST 2010
Build number
1.34.405.5 CL273326 release-keys
Software number
1.34.405.5

You're the first person to mention this sort of problem, as far as I'm aware. What about if you unroot, does the data connection come back ? It sounds very odd. You may need to do a factory reset if it doesn't magically start working on its own, because I wonder if something's got corrupted.
I used the rage version of rooting myself, very simple, and it seems a more reliable method than Visionary.

Sorry to state the obvious, ... But you have checked the APNs in settings haven't you?
EDIT.... Everything was working fine before rooting, but you haven't changed ROM. Hmmmmm, strange indeed? Try Stevie's suggestion of a reset. This is very, very odd though.

According to the thread on rooting using the "rage" method :
Visionary has caused filesystem corruption for some users during the rooting process
Click to expand...
Click to collapse
Now I don't know what the basis of that is, but I just wonder if that's what has happened in this case ?

Is it safe to reset without unrooting, and while I am still S-OFF?
Or should I unroot first (using Visionary)?

It should be safe, yes. No idea if you lose root or not when you factory reset, I presume you do ? I recommend the rage method of rooting if you need to do it again, there are only a few steps to do and it seems to be pretty reliable.

OK, I've reset my phone, and it appears my network connection is working again.
I've lost root, but I'm still S-OFF
You reckon I should try the rage method of rooting? Problem is, I'm no good with ADB :-(
Can it all be done by transferring files to the phone with file manager, then terminal emulator? I may be a bit thick but I'm just not sure with the whole "pushiing" files to my phone...

setspeed said:
OK, I've reset my phone, and it appears my network connection is working again.
I've lost root, but I'm still S-OFF
You reckon I should try the rage method of rooting? Problem is, I'm no good with ADB :-(
Can it all be done by transferring files to the phone with file manager, then terminal emulator? I may be a bit thick but I'm just not sure with the whole "pushiing" files to my phone...
Click to expand...
Click to collapse
Good that you've got the data connection back. That makes sense that it would keep S-OFF, because that's in your HBOOT, and I wouldn't expect factory reset to touch that.
adb is easy, what is your concern there ? Those commands to push files to your phone are simply copying them via adb. I guess there's no reason you can't copy the files some other way though and then run the stuff through terminal emulator (e.g doing the chmod via the terminal emulator) ?

steviewevie said:
Good that you've got the data connection back. That makes sense that it would keep S-OFF, because that's in your HBOOT, and I wouldn't expect factory reset to touch that.
adb is easy, what is your concern there ? Those commands to push files to your phone are simply copying them via adb. I guess there's no reason you can't copy the files some other way though and then run the stuff through terminal emulator (e.g doing the chmod via the terminal emulator) ?
Click to expand...
Click to collapse
I dunno, I'm just not confident with adb - I don't understand it. I might have a look and give it a bash...

Weirdness. I thought I'd give Visionary one more shot since it's so easy, and it appears that I now have root again, plus my network connection is working.
I don't know what the difference is this time round, as I followed the exact same steps I did the first time.
Anyway, I'm happy! Thanks for your help guys

setspeed said:
Weirdness. I thought I'd give Visionary one more shot since it's so easy, and it appears that I now have root again, plus my network connection is working.
I don't know what the difference is this time round, as I followed the exact same steps I did the first time.
Anyway, I'm happy! Thanks for your help guys
Click to expand...
Click to collapse
Great news !

setspeed said:
I don't know what the difference is this time round, as I followed the exact same steps I did the first time.
Anyway, I'm happy! Thanks for your help guys
Click to expand...
Click to collapse
.... so what Stevie said about corruption issues may well be true, Visionary doesn't seem consistent does it? I might restore to stock and give Rage a try now.
Sent from my T-Mobile G2 using XDA App

Uh oh - trouble in paradise... My network connection has gone again :-(
Goddamn phone!!!

I'm thinking maybe it's a problem with one of my apps, because it was fine immediately after rooting this time round. Then I installed all my apps, and noticed I then had a problem. I'm going to uninstall everything and see if I can isolate the problem that way.

I am officially a "ri-tard". My problem was that I had installed DroidWall without applying any whitelist.

setspeed said:
I am officially a "ri-tard". My problem was that I had installed DroidWall without applying any whitelist.
Click to expand...
Click to collapse
Ha,... too funny man!

do I need s=off for cyanogenmod 7?

I have ROM manager premium, and I just downloaded CM7 through it, and was about to flash it, but remembered I dont have s=off.
Also, I cannot get past this screen no matter what. htt p://img145.imageshack.us/i/20110222142411.jpg/
Any help will be appreaciated I really want to be able to run CM7

You need to be rooted, use the ultimate gfree method that's stickie in the development section after you root make sure to back up your stock OS.
Sent from my HTC Glacier using XDA App

epsix said:
You need to be rooted, use the ultimate gfree method that's stickie in the development section after you root make sure to back up your stock OS.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Thanks for answering, but I am rooted, I used the visionary perm-root method. I have terminal emulator and typed "su" and it prompted for super user access. I also have a few apps that use root, which work.

Root access alone is not enough. You need S-Off as well.

jggimi said:
Root access alone is not enough. You need S-Off as well.
Click to expand...
Click to collapse
Is that why I always get this screen when I try to make a back up or boot into recovery.

jggimi said:
Root access alone is not enough. You need S-Off as well.
Click to expand...
Click to collapse
This Statement is correct.
jessek17 said:
Thanks for answering, but I am rooted, I used the visionary perm-root method. I have terminal emulator and typed "su" and it prompted for super user access. I also have a few apps that use root, which work.
Click to expand...
Click to collapse
for short terms "s" Means security protocol. If your S=ON that means the phone will do a search each time you boot the phone on to see if anything as been tampered with. and if it has it will revert back to a factory status. Just like you first bought the phone. Which includes rooting, recovery images, boot images, engineering screens. What ever you do to your phone that isn't factory will be undone.
It is impossible to do. Because you need to flash the ROM from the recovery image. And since one you boot your phone it will replace Clockwork ROM manager with the factory style recovery image, you cannot not even get to the place you need to flash it from.

jessek17 said:
Is that why I always get this screen when I try to make a back up or boot into recovery.
Click to expand...
Click to collapse
Correct because you flashing the Clockwork Recovery image will not STICK unless you have s=off.
They system will replace the aftermarket image with the original EVERYTIME you turn off the phone.

That is the Stock Recovery. You need S-Off and ClockworkMod Recovery. And the right release of CWM Recovery, also. Use CWM Recovery 2.x to back up, restore, and install Android 2.2 (Froyo) based ROMs, including stock, and CWM Recovery 3.x to back up, restore, and install Android 2.3 (Gingerbread) based ROMs, such as CM7.
There is a special version of CWM Recovery that can manage both Froyo and Gingerbread ROMs: 3.0.0.6. Search for it in the Development subforum.

Thanks for all the information, I am slowly learning, and trying to understand all of this.
I am currently trying to get s=off. I found this link via google : ht tp://forum.xda-developers.com/showthread.php?t=858996
I am already "rooted" I believe, because I have superuser access. Should I unroot first?
Also, in order to back up my current(stock) rom, do I need to use clockwork recovery 2.x?

jessek17 said:
Thanks for all the information, I am slowly learning, and trying to understand all of this.
I am currently trying to get s=off. I found this link via google : ht tp://forum.xda-developers.com/showthread.php?t=858996
I am already "rooted" I believe, because I have superuser access. Should I unroot first?
Also, in order to back up my current(stock) rom, do I need to use clockwork recovery 2.x?
Click to expand...
Click to collapse
Yes that method will work.
no do not unroot prior to starting that method
yes you need to use 2.x to back up froyo (2.2) ROMs.

neidlinger said:
Yes that method will work.
no do not unroot prior to starting that method
yes you need to use 2.x to back up froyo (2.2) ROMs.
Click to expand...
Click to collapse
Okay, is there a simpler way to get s=off? That looks a little complex for my first time doing this, and it seems as if one typo will brick my phone.

jessek17 said:
Okay, is there a simpler way to get s=off? That looks a little complex for my first time doing this, and it seems as if one typo will brick my phone.
Click to expand...
Click to collapse
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/
you can use the link i posted ^^^ there.
I will state this though. That link that you posted is the simplest way of truly rooting your phone. If that seem complex i would advice against you doing it at this point in time.
Rooting your phone basically turns your phone into a computer that can make and receive phone calls. And doing the wrong thing at the wrong time will seriously FUBAR your phone.
If you take a look in the Q&A section and the General Section you will see TONS of post with people in your shoes that didn't know what they were getting into and didn't take the warning laid out there.
READ READ READ about the android ADB before you decide to root your phone. And learn what everything is and what it does.
not trying to sound like a "Richard" but i don't want to see you mess up your phone either.

neidlinger said:
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/
you can use the link i posted ^^^ there.
I will state this though. That link that you posted is the simplest way of truly rooting your phone. If that seem complex i would advice against you doing it at this point in time.
Rooting your phone basically turns your phone into a computer that can make and receive phone calls. And doing the wrong thing at the wrong time will seriously FUBAR your phone.
If you take a look in the Q&A section and the General Section you will see TONS of post with people in your shoes that didn't know what they were getting into and didn't take the warning laid out there.
READ READ READ about the android ADB before you decide to root your phone. And learn what everything is and what it does.
not trying to sound like a "Richard" but i don't want to see you mess up your phone either.
Click to expand...
Click to collapse
Isnt that just a video of temprooting and then confirming the root with terminal emulator?
I have seen many people with problems and they think they bricked their phone. I dont want to be one of them, and I've had a few close calls, and I'll tell you it wasnt fun.
From what I see ADB is just a remote terminal?
I appreciate that, and have taken the warnings very seriously.

jessek17 said:
Isnt that just a video of temprooting and then confirming the root with terminal emulator?
I have seen many people with problems and they think they bricked their phone. I dont want to be one of them, and I've had a few close calls, and I'll tell you it wasnt fun.
From what I see ADB is just a remote terminal?
I appreciate that, and have taken the warnings very seriously.
Click to expand...
Click to collapse
That's kind of my point. People don't read.
If you take your time and read and do the entire process you won't have a problem. but you need to read all the way through something prior to jumping in the ring. There is a very strict set a rules that need to be followed.

I downgraded from the Official AT&T 2.2 update back to 2.1

I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb

I have done this and can confirm that this works
Thanks mate!

I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.

khaytsus said:
I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.
Click to expand...
Click to collapse
I went back to 2.1 because the 2.2.2 version that AT&T released was extremely slow, and my touchscreen would become unresponsive.

andrewishcool95 said:
I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb
Click to expand...
Click to collapse
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?

Gene Poole said:
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?
Click to expand...
Click to collapse
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.

andrewishcool95 said:
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.
Click to expand...
Click to collapse
I'm also very curious about this.

Sounds like the first steps to rooting and downgrading. I'm curious to see if any developers catch this
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.

Gene Poole said:
I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.
Click to expand...
Click to collapse
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?

FroztIkon said:
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?
Click to expand...
Click to collapse
There may be. When I first got my Aria, the rooting procedure involved an HTC signed update that you fooled the hboot into partially loading, then swapped the sdcard with the root package. It involved some complex timing issues where you had to run adb in a loop and plug/unplug the usb cable at appropriate times.
I've been searching the net for that procedure and I can't seem to find the right search terms, or I'm just not looking in the right places or something, but I know that's how I did my Aria before there was an unrevoked plug-n-root.

I have the procedure u are looking for i think...let me know if this is what u were after because i have an archive of saved documents I have copied from forums in the past...GOOD LUCK!
well apparently i haven't posted enough to put the links up in the post

PM me if you want the process...

xerotix said:
PM me if you want the process...
Click to expand...
Click to collapse
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.

econcep said:
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.
Click to expand...
Click to collapse
That process does not work with the new HBOOT. That's why unrevoked doesn't work. Having root access does not unlock NAND.
Currently, the only way known is via hardware tools.

It works. I managed a work around for 2.2.2 update
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.

econcep said:
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.
Click to expand...
Click to collapse
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272

Gene Poole said:
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272
Click to expand...
Click to collapse
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.

econcep said:
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.
Click to expand...
Click to collapse
Perhaps I misread (or we're talking past each other). You do have, in fact, HBOOT 1.02.0000 on your Aria, and managed to write to the system partition?

Yes & No. I'm stuck on couple of things. First the will temporary give me root access but then it locks up saying I don't have busybox. I'm rooted but no s-off. I also noticed when I reboot into recovery I go into CWM 2.5.0.1 but other times it boots into CWM 2.5.0.7. When that happens I loose my unknown source in settings>application. Again, if this is the wrong thread, I really am sorry.
I googled alpharev and some others who have worked on rooting. Found some cached pages from Jan when they were testing to root/s-off the Aria. Basing my work on that and couple of other devices that are similar to the Aria.

Help a noob install a rom on Epic 4g so I can tether with my over priced phone?

So I got the Froyo update and it killed my ability to tether and root.
Seriously, Im even having trouble with WIRED tethering. Its not working and wont root.
Please point me in the direction of some noob friendly step by step instructions for installing a custom rom that is tethering friendly, along with any info for simply getting wired or wireless tethering to work after the Froyo update?

You shouldn't have installed the update.
Sent from my HTC Glacier using XDA Premium App

Yeah I know. Is there nothing I can do now?
They say they can bring you back to 2.1 if you take it to the shop. Does the update do anything that prevents installing ROMs? When they bring you back to 2.1, will that fix whatever they did or is it in that version now too?

Why can't you root?

Because I accepted the update and the update killed root and tethering for me? I guess there was a way to upgrade without accepting that update.
z4root wont work, and also it says that the OS no longer has the drivers to support the free wireless tethering apps.
......Did you read the OP?
So how am I supposed to root if I cant even use clockwork to install new roms without root access? Am I totally ****ed? Should I just return this phone and get one from Verizon?

Yes I read the OP but the 2.2.1 update doesn't prevent rooting again. If it did, I wouldn't be rooted right now.
I'm not sure what you did or didn't do, but the one click method works.

hes never been one clicked. he only used z4root.

Nick_Djinn said:
z4root wont work, and also it says that the OS no longer has the drivers to support the free wireless tethering apps.
......Did you read the OP?
So how am I supposed to root if I cant even use clockwork to install new roms without root access??
Click to expand...
Click to collapse
z4root is hokey. you need to use the oneclick root. its really simple.
http://forum.xda-developers.com/showthread.php?t=770388
use this thred. it is for real root, not z4. also, the drivers are installed on your computer, not your phone.

austin420 said:
z4root is hokey. you need to use the oneclick root. its really simple.
http://forum.xda-developers.com/showthread.php?t=770388
use this thred. it is for real root, not z4. also, the drivers are installed on your computer, not your phone.
Click to expand...
Click to collapse
Thank you for something helpful finally.
That makes sense. I tried installing it on my phone. Thank you for noticing that.
You know, if you wrote these instructions for noobs it would really help....For example, when we are dealing with not 1 but 2 devices, it might be helpful to describe which device is doing what. One minute I am doing something with the phone and the next its just "install this"....Dumb it down a bit, like you are talking to people who dont know anything about anything.
Anyway, thanks. Im going to try this now.

Nick_Djinn said:
Thank you for something helpful finally.
That makes sense. I tried installing it on my phone. Thank you for noticing that.
You know, if you wrote these instructions for noobs it would really help....For example, when we are dealing with not 1 but 2 devices, it might be helpful to describe which device is doing what. One minute I am doing something with the phone and the next its just "install this"....Dumb it down a bit, like you are talking to people who dont know anything about anything.
Anyway, thanks. Im going to try this now.
Click to expand...
Click to collapse
Don't feel too bad. I had to read that stuff several times before even deciding whether I should try it.

It keeps saying phone is not connected, even though it says USB-storage is enabled and I can access the files on my phone.

Don't click on mass storage.....and turn on usb debugging
Sent from my SPH-D700 using XDA App

The NON-One click solution seems doable but complicated, and I dont really know what I am doing.
Im thinking about paying somebody to root the phone properly. One person advertised in the SF Bay Area that I know of.

wytecaztle said:
Don't click on mass storage.....and turn on usb debugging
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Cool.
Thanks for the support. Im going to try this at least for another day or so before giving up.

OK. Now it says rage against the cage is missing.
The file is clearly there, but VLC media player wants to open it instead of anything useful.

do you use any sort of anti virus? it will remove things from the ragagainstthecage exploit. disable you antivirus for a few minutes and redownload the the rootpackage. im not saying thats what the problem is, im just saying antivirus clashes with the root method.

A little effort goes a long way. Getting root is easy for the epic. Install the samsung drivers, turn on usb debuging on phone, extract the oneclick folder and run the "run.bat" file and let it do its thing.
Sent from my SPH-D700 using XDA App

Nick_Djinn said:
OK. Now it says rage against the cage is missing.
The file is clearly there, but VLC media player wants to open it instead of anything useful.
Click to expand...
Click to collapse
I had that problem also and it turned out that I was trying to run it from a networked drive. I had to unzip the file to my computer desktop then run the program from there before it worked properly.

If you check out this thread there is a how to video i made to root and flash a rom. Check it out, I think it will help you out.
http://forum.xda-developers.com/showthread.php?t=1009997

make sure correct samsung drivers are installed on your computer (32 or 64)
download and extract once click root to your computer
Enable usb debugging on your phone (settings - applications - development - usb debugging)
Plug phone into computer
Run run.bat, wait, and enjoy.

OneClickRoot Sprint, anyone?

Curious as to whether anyone has tried this. Suspicious as I haven't seen it here lol. Thoughts?

Good luck lol

yeah i saw that site this morning.. anyone have luck?

Jaws4God said:
yeah i saw that site this morning.. anyone have luck?
Click to expand...
Click to collapse
OCR is non attainable on this device.
Too much stuff to do manually.

elijah420 said:
OCR is non attainable on this device.
Too much stuff to do manually.
Click to expand...
Click to collapse
has anyone tried and it fail?

Jaws4God said:
has anyone tried and it fail?
Click to expand...
Click to collapse
OCR is not attainable on this device.
Too much to do manually.

I always recommend manual methods over one click methods you never know what kind of crap these programs will put on your phone.
Its not the first situation where spyware has ended up on phones from these sites. King Root is a good example.
Sent from my LG-H918 using XDA-Developers Legacy app

evo4g63t said:
I always recommend manual methods over one click methods you never know what kind of crap these programs will put on your phone.
Its not the first situation where spyware has ended up on phones from these sites. King Root is a good example.
Sent from my LG-H918 using XDA-Developers Legacy app
Click to expand...
Click to collapse
oh thank you for the heads up.. I was just hoping to find a way to just get simple root on my phone to have access to Gravity Box ... but i do not want to unlock my bootloader and have a custom recovery..
Thanks!

Jaws4God said:
oh thank you for the heads up.. I was just hoping to find a way to just get simple root on my phone to have access to Gravity Box ... but i do not want to unlock my bootloader and have a custom recovery..
Thanks!
Click to expand...
Click to collapse
It's a scam. My dad (without consulting me) tried it on a moto g4. Not only did it not work, he ended up with spyware and spam that I had to get rid of.
There is no simple root. Any phone going forward that is rootable will have to be connected to a pc and adb or odin used to exploit a vulnerability manually.

One click Root Worked For Me (H91810J) T-MO
sjr19 said:
Curious as to whether anyone has tried this. Suspicious as I haven't seen it here lol. Thoughts?
Click to expand...
Click to collapse
OneClickRoot worked on my T-Mobile H91810J. I've rooted a lot of phones and tried the recowvery and numerous other methods. I couldn't get TWRP to flash because I was missing a few commands not listed. They connect through the program (Oneclickroot) and use a program called Vysor. It has to be manually done by one of their techs. I was able to see and copy their commands and files but again I have a T-mobile not Sprint. To be sure, open a chat session and they will 100 percent verify if they can do it. They ask for everything from the model number, to the build number, security patch info...etc . It has to be done manually by the tech not by the program which will tell you after trying to root that you need to have it done manually by them.
They are legit but not cheap. The up side is they can do it right from your pc or most any pc . It's a 24/7 operation also. Pay the extra for the protection. It isn't cheap but it sure is easy and now I am 99 percent sure I can follow their steps if needed. I see where I messed up in the shell commands. I hate my bootloader locked When I boot though. I still have to access it through ADB unless I am missing something. I also still have the annoying orange oem warning screen. Otherwise full root access. I just don't know what I am going to do if something happens and it has to be reset...etc. I love lux and color changer pro. Completely transforms the device in my opinion. Hopefully we have a solution by then to bypass the entire thing. If I could get a hold of chainfire I'd send the code and files right to him or anyone capable of making this easier on everyone.
I plan on posting the code in the near future I just haven't had time. More to follow. OneClickRoot is legit but not cheap. You also have to have some trust to allow a remote connection. If they say they can do it they can. I tried doing the recowvery step by step and it kept locking up on me do to FRP. I messed up some additional shell commands which I didn't know I needed to actually flash twrp.
I am almost positive they can do the sprint version. Just check with them first via chat which is free.

Unless they have found another exploitable security hole, or your phone has NOT taken the zv6 update, your phone is NOT rootable.
The exploit that allowed dirty cow/Santa/elf, copy on write, has been plugged.
Legitimacy of their operation aside, the exploit was plugged with the zv6 update.