Related
I asked this in the Jellybean Jellybomb thread, but that's far too fast moving and not necessarily a question about the ROM anyway (tied to root):
I've used the TeamEpic 'Root from Recovery' method to root my phone in the past, to enable wifi tethering as an emergency fallback only for a company-supplied MiFi that I carry on work trips.
This method results in Settings--> About Device showing "modified" status.
I believe this is directly tied to the following undesirable effects:
Google Wallet throwing 'unsupported' warnings and some transactions appear in 'unconfirmed' status, although technically "it works", this isn't good.
'Wifi Tether' app doesn't work more often than it does work (even following configuration suggestions on GS3-specific troubleshooting threads)
Because of these, I unrooted my device [also following the TeamEpic Root from Recovery thread, restore option].
However, since restoring, I've twice been prompted for an OTA update, and both have failed.
And since I'm now interested in installing a custom JB ROM (or manually apply an update, if I don't), I'll need to root again at any rate.
Simple questions:
Is there a root method that doesn't result in the phone showing a 'modified' status in Settings --> About Device?
If not, is there a mod that can be applied to stop Wallet from showing warnings and 'unconfirmed' transaction statuses that don't appear when the device is not rooted?
Note: Triangle Away disclaimers it does not change 'modified' status - and did not on ICS.
Note: I follow the precautions on the Wallet sticky for both rooting and unrooting. This thread does not discuss a solution.
Any help is appreciated, even if the answer is "no, you can't work around either of those".
Thanks in advance!
geolemon said:
I asked this in the Jellybean Jellybomb thread, but that's far too fast moving and not necessarily a question about the ROM anyway (tied to root):
I've used the TeamEpic 'Root from Recovery' method to root my phone in the past, to enable wifi tethering as an emergency fallback only for a company-supplied MiFi that I carry on work trips.
This method results in Settings--> About Device showing "modified" status.
I believe this is directly tied to the following undesirable effects:
Google Wallet throwing 'unsupported' warnings and some transactions appear in 'unconfirmed' status, although technically "it works", this isn't good.
'Wifi Tether' app doesn't work more often than it does work (even following configuration suggestions on GS3-specific troubleshooting threads)
Because of these, I unrooted my device [also following the TeamEpic Root from Recovery thread, restore option].
However, since restoring, I've twice been prompted for an OTA update, and both have failed.
And since I'm now interested in installing a custom JB ROM (or manually apply an update, if I don't), I'll need to root again at any rate.
Simple questions:
Is there a root method that doesn't result in the phone showing a 'modified' status in Settings --> About Device?
If not, is there a mod that can be applied to stop Wallet from showing warnings and 'unconfirmed' transaction statuses that don't appear when the device is not rooted?
Note: Triangle Away disclaimers it does not change 'modified' status - and did not on ICS.
Note: I follow the precautions on the Wallet sticky for both rooting and unrooting. This thread does not discuss a solution.
Any help is appreciated, even if the answer is "no, you can't work around either of those".
Thanks in advance!
Click to expand...
Click to collapse
If you still have a custom recovery (twrp,cwm) ota update will fail and I believe that's tied to the modified status.
Because your modified Google wallet will always say UN supported device.
Since you want to flash a custom rom , your device will say modified and Google wallet will have that message.
Only way around it is to go completely stock including recovery and stay that way.
This is afaik, I could be completely wrong I'm my assuming.
Sent from Pluto.
Speedin07si said:
If you still have a custom recovery (twrp,cwm) ota update will fail and I believe that's tied to the modified status.
Because your modified Google wallet will always say UN supported device.
Since you want to flash a custom rom , your device will say modified and Google wallet will have that message.
Only way around it is to go completely stock including recovery and stay that way.
This is afaik, I could be completely wrong I'm my assuming.
Sent from Pluto.
Click to expand...
Click to collapse
I don't have custom recovery. That's removed in the the "stock restore" process in the Team Epic 'root from recovery' (link is in the OP). Recovery is stock.
Also, If you look at the error issue thread link in the OP, I included screen captures of the error - they are captured in the stock recovery.
Ultimately, OTA updates are a non-issue if I'm re-rooting.
But if I am going to root again, I'd like to work around the 'modified' status and Wallet 'unconfirmed' status if at all possible.
Anyone have any information on those issues? I'm finding little discussion on it, other than a few comments that it's inherent with rooting - I'd like to determine if that's an absolute, or just inherent in the rooting method that I (and many others) have used.
Thanks in advance.
No, once u become "Modified" the only wsy to return is to use an Odin installable. It does not matter if u install a custom recovery, root, unroot and reinstall stock recovery. Once u are modified u stay that way until u reinstall everything through Odin which you will then see Normal.
Sent from my SPH-L710 using Tapatalk 2
billard412 said:
No because being rooted makes it say that. A system check is done on every startup. It will say that if it finds superuser, su or busybox present anywhere in the system
Click to expand...
Click to collapse
I asked your question in the Android Development forum. This is the answer I got.
Sent from my SPH-L710 using XDA Premium HD app
EPayne123 said:
No, once u become "Modified" the only wsy to return is to use an Odin installable. It does not matter if u install a custom recovery, root, unroot and reinstall stock recovery. Once u are modified u stay that way until u reinstall everything through Odin which you will then see Normal.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
After I restored using the reversal procedure for the TeamEpic 'root from recovery' process (here, for reference - third "Link"). I did use Odin, both for rooting and restoring back.
My phone no longer shows Modified,and Google Wallet has no issues or messages.
I'm simply looking to avoid it if at all possible, if I root my phone again. I'm tempted to try a JB ROM.
If it is avoidable, I'll use that particular method of rooting.
If it is not avoidable (as so far seems to be the consensus, unfortunately), then no harm in using this process again - particularly being the majority method.
why? no effect on wallet's usability
EPayne123 said:
No, once u become "Modified" the only wsy to return is to use an Odin installable. It does not matter if u install a custom recovery, root, unroot and reinstall stock recovery. Once u are modified u stay that way until u reinstall everything through Odin which you will then see Normal.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Not true. For it to be normal you must be stock with a stock kernel, recovery doesn't matter. Cannot have superuser su or busybox present and your flash count must be 0. Then it will say normal. No Odin required
nicholaaaas said:
why? no effect on wallet's usability
Click to expand...
Click to collapse
Two reasons:
1) It's a bit like saying, having one burgundy interior door panel and a random blue glovebox door in your otherwise grey car interior doesn't impact driveability.
And it doesn't... but it does create a nagging "something isn't right" feeling that leaves you less comfortable and enjoying the drive less, and making needless excuses when you host passengers, than if your car was 100% correct.
2) While technically "it works", some transactions remain in an 'unconfirmed' status, where I'm not experiencing that at all with a stock device. One benefit of Wallet is the ability to track transactions, and while I haven't tried yet, could use an export of this to track spending. I'd like it to work as designed.
billard412 said:
Not true. For it to be normal you must be stock with a stock kernel, recovery doesn't matter. Cannot have superuser su or busybox present and your flash count must be 0. Then it will say normal. No Odin required
Click to expand...
Click to collapse
This is good info that sounds pretty close to a definition...
Is there a workaround for this?
I'd think someone would have possibly created a patch of sorts to change that specific logic to something else by now, if for no other reason than to avoid these sorts of issues - I'm speculating (but can't know) that this is also tied to why Wifi Tether app worked so sporadically (even with settings found in GS3-specific Wifi Tether troubleshooting threads) as well.
If rooted, obviously you need superuser...
Possibly you need busybox...
I believe there are methods of rooting that at least don't involve incrementing the Odin flash counter (I haven't used them).
Resolving one or two of the three won't be very useful however, from what you are saying.
Any thoughts on working around it? Does anyone know where this code specifically is?
Thanks-
I used Triangle away and reset the counter and then used the JB update from this thread:
http://forum.xda-developers.com/showthread.php?t=1941546
afterwards, I ended up with rooted JB, a count of zero, and triangle away states:
Current status
Counter: 0
Binary Official
Device: SPH-L710
I should try Triangle Away. I stopped at the disclaimer on the thread that it changing Modified status was "out of scope". So I didn't even try it.
Does your google Wallet show "unsupported device", out of curiosity?
Even if Triangle away fixes the modified system status(which it wont if you're rooted) Google wallet will definitely still say unsupported. It means just that,
It'll still work but dont try callin them for help because they dont support rooted devices as its a security risk. If its that big a deal try unrooting and running the phone stock with no modifications. Then youll have exactly what your lookin for
geolemon said:
Does your google Wallet show "unsupported device", out of curiosity?
Click to expand...
Click to collapse
Yes, it does.
billard412 said:
Even if Triangle away fixes the modified system status(which it wont if you're rooted) Google wallet will definitely still say unsupported.
Click to expand...
Click to collapse
What do you mean triangle away wont fix the modified status?
My SGS3 is rooted, with JB, with a flash count of zero, and a status of "official" like I stated before.
DCRocks said:
Yes, it does.
What do you mean triangle away wont fix the modified status?
My SGS3 is rooted, with JB, with a flash count of zero, and a status of "official" like I stated before.
Click to expand...
Click to collapse
Perfect information, thanks.
My main concern is with Wallet, less so the warning message, more so the 'unconfirmed' status I was seeing on transactions after rooting. May turn out not to be an issue - at least once I'm on a JB build, per my coworker:
I have other reasons for wanting to update as well -
I'm unimpressed with the battery life that I've been getting, and it's not due to a rogue app. For example, today so far my "Cell Standby" is 55% of my battery stats. A coworker of mine is also on Sprint, has installed one of the official Jellybean leaks, and his Cell Standby percentage is always single-digit.
He's also been using Wallet, and all of his transactions have been completing, none are showing the 'unconfirmed' status I was seeing with my stock, rooted, ICS experience.
I may root and try the Sonic ROM - I especially like the sounds of "killer battery life" in the OP.
Thanks for the help here, that really does help me a lot - obviously Wallet uses something deeper than the device's "modified" status to display that warning message.
I am stock rooted running JB and use Voodoo OTA Rootkeeper to "unroot" my phone as needed for certain apps. The Google Wallet app does not display the unsupported warning when I temporarily unroot using the app. If the unsupported message bothers you, you can always go this route.
Of course there is a way
freeza said:
Of course there is a way
Click to expand...
Click to collapse
Are you actually rooted, or also using Voodoo to temporarily unroot when you don't need it?
If that's not it, please share your method. I was just about to root using the root-from-recovery method, but I'll hold off for now pending learning your method.
Thanks.
freeza said:
Of course there is a way
Click to expand...
Click to collapse
But no reply of how?
That would be helpful.
Sent from my Nexus 7 using xda app-developers app
freeza said:
Of course there is a way
Click to expand...
Click to collapse
would like to know. my wife is enjoying your JB rom and just tried Wallet yesterday and came to me with that message. so i'd like to find a solution for her.
okay so I followed this link true-android.blogspot. com/2014/03/root-t999uvuenc2-t-mobile-galaxy-s3. html to root my s3. I did not get the yellow bar that I was supposed to but I decided to follow through anyway. At the end of it I received the PASS message. I had superuser installed. The problem is that it seems like knox is keeping superuser from granting anything root privileges. Every time I launch superSU, it leaves me with a message of "unfortunately SuperU has stopped. On my notification bar it shows security information and the message "an application attempted to acces system on your device without authorization. This attempt has been blocked...." i also can't seem to log into it to uninstall it because it gives me an error. root checker tells me I don't have proper root access but I am assuming it's because superuser is being blocked. I am unable to uninstall superuser and my flash counter went up to one so I am "assuming" that I am rooted. Does anyone know how to disable knox? or if it is not knox and it turns out that my device is not really rooted, do you guys know how I can root it? this is all really confusing. Any help would be greatly appreciated.
Thanks in advance.
First thing, you will have much better luck just sticking to the forums here. Not many are willing to assist with other sites posted processes because for the most part, everything you could possibly need is right here.
Before you do much else, look over the sticky threads in each of our sections. You will find lots of very important info and ill bet a better way to accomplish what you want to do.
Check my firmware thread for root66 firmware. Flash it and your rooted and knox free. Click on the root66 heading to go to the thread.
By reading the sticky threads you will also find alternative methods. The only one I warn against is something called the toolkit.
If you have specific questions about anything feel free to ask.
Sent from my SGH-T999 using Tapatalk
Moved to Q&A.
What I did to root my s3 was I used odin. Put http://forum.xda-developers.com/showthread.php?t=2370981device on download mode. Download a recovery tar click on pda and flash it. After device reboot put su zip on sd card and flash on recovery and you will be rooted. You can you root explorer apk to delete knox from /system/app.
I'll post the files you need.
You can find everything on that website if different s3
Where it says xdadevelopers recognized contributor: click to show content...you will find all recoveries, odin, drivers, su
MODERATOR EDIT - Attachment Removed
Thread cleaned
Hello everybody. So, let me tell you my story.
Back a few months ago, I rooted my phone. At start I liked it a lot, then I decided there might be a lot of problems with it, so decided to unroot it. Searched all over XDA, found a way to unroot, unrooted. Now more details. I rooted it with cfm-autoroot-whatever, then in SuperSU checked that I don't want root, and was naive I got rid of root. I was wrong, so searched XDA, found that the only way out was to flash the original OS(/recovery?) of the phone. So, thanks to guys here on XDA, they provided me with a link to the original recovery. I tried updating a rooted phone OTA, first time it failed, same story was with the 2nd try. 3rd try, however, was successful. Well, almost. It started, as I thought, to update, but then the phone wouldn't turn on - all it could do is to go into Download mode. Thankfully enough, I had Odin (thanks to XDA guys for whicever time). I launched Odin and flashed the phone with stock recovery.
Now I have SPH-L900, L900VPUCNE2, Device status is Official, but...
That's why I'm here, finally.
Recently I downloaded CPU-Z for my phone, and when I opened "System" tab, the first thing I see is this:
Model SPH-L900 (t0ltespr)
What? Really? I thought it's for rooted phones, or at least for some not stock recovery. So, does that mean I don't have a stock recovery? Does that mean my phone is rooted even though I didn't root it after flashing with "stock" recovery?
I can find the threads, I think I bookmarked them if you need.
I'll try to explain
Look in cpu-z under system if at the bottom "Root Access: No" then your phone is not rooted.
now if your wondering about "t0ltespr" it is the code name for the SPH-L900 but every dev uses "l900" from what i can see.
NeoGman said:
Look in cpu-z under system if at the bottom "Root Access: No" then your phone is not rooted.
now if your wondering about "t0ltespr" it is the code name for the SPH-L900 but every dev uses "l900" from what i can see.
Click to expand...
Click to collapse
CPU-Z says the phone is not rooted. Really, my question has been answered: why the app says my phone is t0ltespr. Thanks.
[Q&A] [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.
Q&A for [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.5/8.4 ]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.5/8.4 ]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can this method be used Straight out of the box?
Hey guys, just wanna make sure that this method can be used straight out of the box? only ever rooted LGs so just want to check that I'm doing the right thing here?
Thanks
As long as you have the Samsung usb drivers installed on your pc you're good.
ashyx said:
As long as you have the Samsung usb drivers installed on your pc you're good.
Click to expand...
Click to collapse
Great stuff Thanks, got a bit confused with the CFAutoRoot page saying I needed to unlock the bootloader first, then I stumbled on your Method.
Thanks
AgentCP said:
Great stuff Thanks, got a bit confused with the CFAutoRoot page saying I needed to unlock the bootloader first, then I stumbled on your Method.
Thanks
Click to expand...
Click to collapse
Only Verizon and AT&T models have locked bootloaders. If you don't have one of these you should be fine.
Why root wifi only device?
I have rooted a couple of devices. I get it's purpose of unlocking hotspot, modifying cpu clock, adblocking, etc. I have the Tab S 10.5 and I am trying to find the benefit to rooting this device. Looks simple enough. But What will I gain? I think I have already answered my question though, maybe. I am rooting my note 3 so I can use that for a hotspot for this. But it seems the only real benefit is adblocking? Am I missing something. It has been a while since I have done this so maybe I have...
Anyways, thanks for the input.
Bdozier said:
I have rooted a couple of devices. I get it's purpose of unlocking hotspot, modifying cpu clock, adblocking, etc. I have the Tab S 10.5 and I am trying to find the benefit to rooting this device. Looks simple enough. But What will I gain? I think I have already answered my question though, maybe. I am rooting my note 3 so I can use that for a hotspot for this. But it seems the only real benefit is adblocking? Am manufacturers I missing something. It has been a while since I have done this so maybe I have...
Anyways, thanks for the input.
Click to expand...
Click to collapse
The way to look at is that rooting gives YOU control over your device not the manufacturer. Think of it as like administration rights on a PC.
Would you like it if pc manufacturers told you what you could and couldn't install on your pc?
Rooting allows you to install custom recoveries so you can back up your device, fix problems, try new custom or stock software, install root only apps such as titanium backup. You can modify system files and add back functionality that the manufacturer has decided to remove or disable. Add new functionality, maybe something that is found on another device. Speed up your device by overclocking to make it run smoother.
Change how things look and install apps such as xposed which reveals a ton of hidden features allowing you to customize your device to your liking.
Once you realise what root can do you'll never want a another device that isn't.
Confused
Hi, I have downloaded the file for the T800. However, when I unzip it there are only two files :cache.img & recovery.img. Am I missing something? Please excuse my ignorance, newbie!!
Blythlad said:
Hi, I have downloaded the file for the T800. However, when I unzip it there are only two files :cache.img & recovery.img. Am I missing something? Please excuse my ignorance, newbie!!
Click to expand...
Click to collapse
Yep you certainly are a nooby as you made the rookie mistake of not actually reading the first post.
Go back to the original thread and read the bit under the smiley face.
ashyx said:
Yep you certainly are a nooby as you made the rookie mistake of not actually reading the first post.
Go back to the original thread and read the bit under the smiley face.
Click to expand...
Click to collapse
Sorry, I read that bit,downloaded odin as well, however, I recall reading something somewhere about needing a .tar file? Maybe some full instructions would be nice for us new to rooting a device. Thanks for the reply
Blythlad said:
Sorry, I read that bit,downloaded odin as well, however, I recall reading something somewhere about needing a .tar file? Maybe some full instructions would be nice for us new to rooting a device. Thanks for the reply
Click to expand...
Click to collapse
The tar file is the file you have downloaded.
Just leave it as it is and flash with Odin.
I shouldn't have to provide step by step instructions, this is what XDA search and Google is for. This info is everywhere.
Basically:
Install Samsung usb drivers.
Disable Samsung kies if installed.
Boot your device into download mode - Hold POWER + VOL DOWN + HOME.
Run ODIN , connect USB cable, look for 'added' message.
Load the tar file into the AP slot, click START.
Wait for flash to complete, device will reboot and root.
Enjoy your rooted device with custom recovery.
New build posted: http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488
I tried on my t800 running latest BRI firmware and worked fine. Thanks a lot.
Cannot complete root on T-800 (Lollipop 5.0.2)
I've tried rooting twice on my T-800 running 5.0.2. In both cases ODIN says passed. However, I do not see either supersu or TWRP. When I ran root validator I got the following:
Root Unavailable
su/id/echo did not execute
I had installed the supersu app manually, but even that says the binaries are not installed.
However, Knox says it has been tripped. (using Knox Status app). So looks like I have the worst of both worlds here (well, other than bricking). Is there anything I can do different? Thanks,
chanukya said:
I've tried rooting twice on my T-800 running 5.0.2. In both cases ODIN says passed. However, I do not see either supersu or TWRP. When I ran root validator I got the following:
Root Unavailable
su/id/echo did not execute
I had installed the supersu app manually, but even that says the binaries are not installed.
However, Knox says it has been tripped. (using Knox Status app). So looks like I have the worst of both worlds here (well, other than bricking). Is there anything I can do different? Thanks,
Click to expand...
Click to collapse
Have you actually read the original thread? The answer is in that thread.
http://forum.xda-developers.com/showpost.php?p=60324046&postcount=33
Works now!
Thank you for the reply. I had read that, but did not understand how it applied to me, root works now.
For anyone else in my shoes, here's what I did:
1) unchecked auto reboot
2) Once I got the Pass! message in Odin rebooted using Power+VDOWN+HOME
3) Kept pressing Power+VUP+HOME till it rebooted, at which point it says installing TWRP
4) Kept pressing Power+VUP+Home till it restarted again, and this time it goes to TWRP
5) In TWRP, I said reboot to recovery, it then asked to install SuperSU and root.
chanukya said:
Thank you for the reply. I had read that, but did not understand how it applied to me, root works now.
For anyone else in my shoes, here's what I did:
1) unchecked auto reboot
2) Once I got the Pass! message in Odin rebooted using Power+VDOWN+HOME
3) Kept pressing Power+VUP+HOME till it rebooted, at which point it says installing TWRP
4) Kept pressing Power+VUP+Home till it restarted again, and this time it goes to TWRP
5) In TWRP, I said reboot to recovery, it then asked to install SuperSU and root.
Click to expand...
Click to collapse
That did it! Thanks bro, made my night!
Sent from my Galaxy S5
chanukya said:
Thank you for the reply. I had read that, but did not understand how it applied to me, root works now.
For anyone else in my shoes, here's what I did:
1) unchecked auto reboot
2) Once I got the Pass! message in Odin rebooted using Power+VDOWN+HOME
3) Kept pressing Power+VUP+HOME till it rebooted, at which point it says installing TWRP
4) Kept pressing Power+VUP+Home till it restarted again, and this time it goes to TWRP
5) In TWRP, I said reboot to recovery, it then asked to install SuperSU and root.
Click to expand...
Click to collapse
Did you see the red android after rebooting?
Supersu should have already been installed before booting into twrp.
chanukya said:
I've tried rooting twice on my T-800 running 5.0.2. In both cases ODIN says passed. However, I do not see either supersu or TWRP. When I ran root validator I got the following:
Root Unavailable
su/id/echo did not execute
I had installed the supersu app manually, but even that says the binaries are not installed.
However, Knox says it has been tripped. (using Knox Status app). So looks like I have the worst of both worlds here (well, other than bricking). Is there anything I can do different? Thanks,
Click to expand...
Click to collapse
I have an apology to make. Your troubles seemed to have been due to the SuperSu script not running because it had become corrupt. I realised something was wrong when you said you had to install SuperSu with TWRP.
All fixed now.
Sent from my SM-T805 using XDA Free mobile app
No clue... any help?
Sorry for the questions....
I have SM-T805 with 4.4.2 and build KOT49H.T805XXU1ANH1...
1 - Can i root without tripping knox? (i've done it on GS3 and GS4, no issues on knox, counter remains 0x0);
2 - The cf.auto root files are locked at specific builds? Or can i use the sm-t805 on chainfire page?;
3 - Can i update to lollipop or any other official firmware? And without tripping knox?
Thanks, in advance.
---------- Post added at 08:23 PM ---------- Previous post was at 08:18 PM ----------
Sorry for the questions....
I have SM-T805 with 4.4.2 and build KOT49H.T805XXU1ANH1...
1 - Can i root without tripping knox? (i've done it on GS3 and GS4, no issues on knox, counter remains 0x0);
2 - The cf.auto root files are locked at specific builds? Or can i use the sm-t805 on chainfire page?;
3 - Can i update to lollipop or any other official firmware? And without tripping knox?
Thanks, in advance.
I tried to root my LG G3 5.0.1 using this method lg-phones.org/guide-to-root-lg-g3-with-android-5-0-1-lollipop.htm
Root checker is telling me that root is not properly installed.
Before I try anything else, I wanted to check with you guys to make sure I do not screw anything up.
ikarihiokami said:
I tried to root my LG G3 5.0.1 using this method lg-phones.org/guide-to-root-lg-g3-with-android-5-0-1-lollipop.htm
Root checker is telling me that root is not properly installed.
Before I try anything else, I wanted to check with you guys to make sure I do not screw anything up.
Click to expand...
Click to collapse
*update*
On a side note, I ran an app called "root check" and it is stating I am rooted.
Anything I should do?
ikarihiokami said:
*update*
On a side note, I ran an app called "root check" and it is stating I am rooted.
Anything I should do?
Click to expand...
Click to collapse
Well what do you wanna do ?
If the root is done, this thread is done ?
But if you ask what next, it's installing a recovery so you can change ROM ..., I can let you search in the general topic there are a few methods to install recovery, I did it last week, only one worked for me, the app Autorec on GooglePlayStore.
Good luck
Liell said:
Well what do you wanna do ?
If the root is done, this thread is done ?
But if you ask what next, it's installing a recovery so you can change ROM ..., I can let you search in the general topic there are a few methods to install recovery, I did it last week, only one worked for me, the app Autorec on GooglePlayStore.
Good luck
Click to expand...
Click to collapse
I'm a computer savvy person, but this was my first experience with rooting. I just wanted to be sure I did it right. Turning my LG G3 from T-mobile and debranding it. I did get a belly up icon of the little green android, with the word error under him when I tried to remove some bloatware, but a battery pull seems to have fixed that.