Database Develop

[Q] Problems with enabling sideloading

Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks

goosefraba91 said:
Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
Could you provide a little more information about your phone? Is it stock JF6 with just root? If not provide firmware information and anything else that might be useful
P.S. Questions belong in the Q&A section

I'm not really sure what JF6 is haha...After I used Odin and set it back to stock conditions, the only thing I did was use the One Click Root.

As far as sideloading goes, the One Click De-Cripple method on page 2 of the general forum worked for me. If you want to know what version your phone is, go to the about phone section under your settings menu. If you need or want to upgrade to JH7, which was the last OTA update from ATT, do a search and there are a few options out there for that.

Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that

goosefraba91 said:
Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that
Click to expand...
Click to collapse
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.

miztaken1312 said:
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.
Click to expand...
Click to collapse
Ok, I got that to work. Now I'm just having trouble entering the code for mac. Like I said, I'm not very savvy with this stuff, so pardon my ignorance, haha.
I'm using the method in the "How to: Remove (Almost) Every Trace of AT&T" thread. (I would post a link, but since I'm a new user, it won't let me)
Is there anything different that I need to put into terminal other than the "./adb"?

I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.

Roof King said:
I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.
Click to expand...
Click to collapse
That method worked great. Thank you!

No prob!
Happy Modding!

Glad you got it working. For the record, the next time you guys wanna post links, just replace the http in the front with hxxp. Most people will fix it when they copy/paste it
Sent from my Captivate

NG2 Baseband unlock without downgrading

First this is only a guide not a repost
NG2 Baseband
1. Use ssu.apk to unlock it first
2.use cf auto root to it
3 use adb:
su
am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://27663368378
UMTS -> DEBUG SCREEN -> PHONE CONTROL -> NETWORK CONTROL -> GCF
There the phone is domestic unlock without downgrading the modem

Haven't tested this but if it works, Bravo!
Sent from my SPH-L720 using Tapatalk

@AndroidKing, after doing just pop up domestic sim and go?
how you discovered this? lol
I have not tested yet, but this kill all other methods
thanks,

yea pop the sim and go i found this method when i was nae frimware and baseband and kept updating it went NG2 and lost the unlock for some reason so I tried so this i seen for the note 3/l720t and it worked

So Does this method make my device works on CDMA&GSM carriers (standby),or GSM only carriers?

Thanks for the steps and instruction. Quick question:
- if step 1 (ssu.apk) does the unlock, then why do we need to do steps 2 and on?
Thanks !
Sent from my SPH-L720 using XDA Free mobile app

I'm not a noob by any means, but I haven't been keeping up with all the s4 updates. I recently broke my s4 witch was running mf9(that tells you how long its been) and the replacement i recieved is OF COURSE ng2. My question is .... will this method root my mk2 s4? Tripping knox doesnt bother me one bit(gotta love blacktie coverage)
Thanks in advance
Mario

mario182005 said:
I'm not a noob by any means, but I haven't been keeping up with all the s4 updates. I recently broke my s4 witch was running mf9(that tells you how long its been) and the replacement i recieved is OF COURSE ng2. My question is .... will this method root my mk2 s4? Tripping knox doesnt bother me one bit(gotta love blacktie coverage)
Thanks in advance
Mario
Click to expand...
Click to collapse
No this is NOT for rooting
This is only for unlocking. To root the NG2 build you have to use chainefires method which will trip Knox. But you said you don't mind. So root and flash away!

can any confirm?
and, can we get a cleaner instruction for noobs?
also does it matter which ROM u'r using?

agentcelsius said:
can any confirm?
and, can we get a cleaner instruction for noobs?
also does it matter which ROM u'r using?
Click to expand...
Click to collapse
also, do we have to adb? can u use the terminal emulator?

ssu step didn't work for me. I'm on NG2.
Edit: It didn't work b/c I was on custom NG2 with custom recovery.
Sent from my SPH-L720

I can't believe it was this easy. I temp flashed back to stock rooted ng2, used ssu.apk to unlock, then restored my GPE Lollipop 5.0.1 backup, popped in my Metro sim(t-mobile), set it to World mode, and bam, says I'm on T-mobile's network, calls and data seem to work. It even shows up as MetroPCS as the active network under status. Put the Sprint sim back in, and it's back to my Ting account.
So to recap, I went to stock NG2 rom, did step one only, skipped the other steps, then went back to custom rom and it now works great. Thanks dude

Stock or stock rooted NG2
Zhono said:
I can't believe it was this easy. I temp flashed back to stock rooted ng2, used ssu.apk to unlock, then restored my GPE Lollipop 5.0.1 backup, popped in my Metro sim(t-mobile), set it to World mode, and bam, says I'm on T-mobile's network, calls and data seem to work. It even shows up as MetroPCS as the active network under status. Put the Sprint sim back in, and it's back to my Ting account.
So to recap, I went to stock NG2 rom, did step one only, skipped the other steps, then went back to custom rom and it now works great. Thanks dude
Click to expand...
Click to collapse
I'm slightly confused. Did you root NG2? 1. Stock NG2, 2. SSU.apk, 3. Restore rooted Lollipop?

kauboy2 said:
I'm slightly confused. Did you root NG2? 1. Stock NG2, 2. SSU.apk, 3. Restore rooted Lollipop?
Click to expand...
Click to collapse
I responded to your PM. I hope you have time to read a book. lol
For anyone else that's wondering:
1. be on stock NG2. ssu.apk force-closes on aosp/custom roms, at least for me.
2. Run ssu.apk and do the unlock. This does not require root.
3. do the other commands through ADB(step 3 from Androidking's original post), just in case. You may or may not need them. I don't know why it worked for me without them. That step DOES require root.
4. Test your sim card and make sure your phone can read it, and if possible, make a call, try text/data, whatever.
5. Flash to the rom of your choice. I recommend this excellent Lollipop rom by Danvbh: http://forum.xda-developers.com/gal...-5-0google-play-edition-lrx219-12-24-t2982384
It allows easy selection of any band/technology that the phone is capable of(which will not actually mean anything until after this unlock procedure). It also automatically gives you many choices for APN's related to your chosen band(not sure if that is a feature of the rom, or if it is standard Android behavior.) Easily select the correct APN for all sorts of carriers, including many popular prepaid services. No manual entry of info needed(probably).
One thing to note: on the custom rom, when I have my Sprint sim in, it says "Invalid Sim" on the lockscreen. The phone does read the sim though, it just says it doesn't. Not sure why that happens. It may be due to the fact that I deactivated my Ting service and haven't gotten new service elsewhere yet, so it can't actually connect to any 4g lte service. It doesn't do that in the stock rom though, it displays normally. Probably just an odd quirk that will work itself out when I switch services. Nothing to worry about.

agentcelsius said:
also, do we have to adb? can u use the terminal emulator?
Click to expand...
Click to collapse
I tried terminal emulator and it opens up the secret menu that opens when you dial *#0011# everytime. I couldnt get into it dialing that tho. I cant get it to work in adb for some reason. So I just used this to get into the menu and change everything manually. The only problem I have now is when I flash a lollipop rom, the network mode gets stuck on LTE only. Even if I change it to world mode, when I go back it just goes back to LTE only. Any ideas?

Jacob030 said:
I tried terminal emulator and it opens up the secret menu that opens when you dial *#0011# everytime. I couldnt get into it dialing that tho. I cant get it to work in adb for some reason. So I just used this to get into the menu and change everything manually. The only problem I have now is when I flash a lollipop rom, the network mode gets stuck on LTE only. Even if I change it to world mode, when I go back it just goes back to LTE only. Any ideas?
Click to expand...
Click to collapse
so u got it unlocked? and the, data mode might be ROM related

sounds like rom problem as the looks of it

AndroidKing said:
First this is only a guide not a repost
NG2 Baseband
1. Use ssu.apk to unlock it first
2.use cf auto root to it
3 use adb:
su
am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://27663368378
UMTS -> DEBUG SCREEN -> PHONE CONTROL -> NETWORK CONTROL -> GCF
There the phone is domestic unlock without downgrading the modem
Click to expand...
Click to collapse
Hi all, I'm new to this. I have a SPH-L720 that is never being rooted before. Is there any link that show step by step how to unlock domestic for this NG2 baseband like AndroiKing mention ? I can understand step 1 and did the unlock but what I'm going to do in the step 2 after you download cf auto root? What is adb and how you get to the following steps? Thanks in advance for your help.

Can anyone share the ssu.apk file?
Sent from my SM-G925P using Tapatalk

http://forum.xda-developers.com/spr...print-samsung-unlocker-unlock-sprint-t2928250

Rooted nexus 6 will not boot up after I edited build prop

Hey all this is my first post on XDA.
So I was trying to unroot and relock my nexus 6 so i decided to replace the build.prop that i have edited with a copy of the original build.prop i had saved on my phone. I used root browser to do this. after I did this I restarted my phone and all I would get is a black screen with google in white and an unlocked lock. it will not boot back up.
My phone will go into recovery mode and that about all i can tell you.
I would truly appreciate your help.

Yaksh123 said:
Hey all this is my first post on XDA.
So I was trying to unroot and relock my nexus 6 so i decided to replace the build.prop that i have edited with a copy of the original build.prop i had saved on my phone. I used root browser to do this. after I did this I restarted my phone and all I would get is a black screen with google in white and an unlocked lock. it will not boot back up.
My phone will go into recovery mode and that about all i can tell you.
I would truly appreciate your help.
Click to expand...
Click to collapse
If your bootloader is unlocked, you can fastboot flash the stock factory image.
Or, if you have TWRP Recovery (I sure hope so, since you were modifying the build.prop) you can connect to your PC while in recovery, then transfer a custom ROM .zip from your PC to your SDcard. Then flash it in recovery.

I had the same thing happen, all you need to do is flash the system image only. Luckily you don't need to flash userdata. Still looking for a way to enable tethering.
Sent from my Nexus 6 using XDA Forums

you do realize that when you edit your build.prop, if you edit to something that doesnt support the n6 or you make a spelling error somewhere, then most likely it will not boot? anyways, the easy way around this is before you edit your build.prop, make a nandroid backup in recovery. so that when you mess up, it won't be a pain in the butt to get everything back.

simms22 said:
you do realize that when you edit your build.prop, if you edit to something that doesnt support the n6 or you make a spelling error somewhere, then mist likely it will not boot? anyways, the easy way around this is before you edit your build.prop, make a nandroid backup in recovery. so that when you mess up, it won't be a pain in the butt to get everything back.
Click to expand...
Click to collapse
This was a method to enable tethering under 5.1, but they've done something to disable it in 5.1.1.
Sent from my Nexus 6 using XDA Forums

Rogue_Blade said:
This was a method to enable tethering under 5.1, but they've done something to disable it in 5.1.1.
Sent from my Nexus 6 using XDA Forums
Click to expand...
Click to collapse
no, its still the way to enable FREE tethering, as long as it is all entered in correctly, it still works. but for tethering, you dont need to do anything, it works straight out of the box.

simms22 said:
no, its still the way to enable FREE tethering, as long as it is all entered in correctly, it still works. but for tethering, you dont need to do anything, it works straight out of the box.
Click to expand...
Click to collapse
Nope, not for me on LMY48I stock, unrooted. WiFi hotspot won't even turn on with 48I, for me. AT&T family share plan (which includes WiFi hotspot). But USB tethering does still work.

cam30era said:
Nope, not for me on LMY48I stock, unrooted. WiFi hotspot won't even turn on with 48I, for me. AT&T family share plan (which includes WiFi hotspot). But USB tethering does still work.
Click to expand...
Click to collapse
in your apn, try changing the IPv6 to IPv4 instead, that should fix the tethering issue(not free tethering, just wireless tethering).

simms22 said:
in your apn, try changing the IPv6 to IPv4 instead, that should fix the tethering issue(not free tethering, just wireless tethering).
Click to expand...
Click to collapse
Thanks. But it is IPv4. Standard AT&T "nextgenphone" APN.
Doesn't really matter for me, since I rarely use tethering. But other users may benefit.

cam30era said:
Thanks. But it is IPv4. Standard AT&T "nextgenphone" APN.
Doesn't really matter for me, since I rarely use tethering. But other users may benefit.
Click to expand...
Click to collapse
oh, for tmo ipv6 is standard. and sometimes wireless tether doesnt work, until tmobilers change it to ipv4.

simms22 said:
no, its still the way to enable FREE tethering, as long as it is all entered in correctly, it still works. but for tethering, you dont need to do anything, it works straight out of the box.
Click to expand...
Click to collapse
As reported many times in numerous locations it doesn't work. If you have a way it does please share.
Sent from my Nexus 6 using XDA Forums

Rogue_Blade said:
As reported many times in numerous locations it doesn't work. If you have a way it does please share.
Sent from my Nexus 6 using XDA Forums
Click to expand...
Click to collapse
well, i just shared, and he tried, said it didnt work. but, it works for tmobile users. its changing the IPv6 in your apn, to a IPv4.

No Joy No Tether
simms22 said:
you do realize that when you edit your build.prop, if you edit to something that doesnt support the n6 or you make a spelling error somewhere, then most likely it will not boot? anyways, the easy way around this is before you edit your build.prop, make a nandroid backup in recovery. so that when you mess up, it won't be a pain in the butt to get everything back.
Click to expand...
Click to collapse
Thanks. I deleted and changed this back to original before I shut down. Having fits trying to get wireless wifi tether from this new Nexus 6 5.1.1. Rooted with CM 12.1. Have yet to find tether? No joy

ray6279 said:
Thanks. I deleted and changed this back to original before I shut down. Having fits trying to get wireless wifi tether from this new Nexus 6 5.1.1. Rooted with CM 12.1. Have yet to find tether? No joy
Click to expand...
Click to collapse
tether is normally in main settings, more.. is it not in cm?

simms22 said:
tether is normally in main settings, more.. is it not in cm?
Click to expand...
Click to collapse
CM strikes again. LMAO

cam30era said:
Nope, not for me on LMY48I stock, unrooted. WiFi hotspot won't even turn on with 48I, for me. AT&T family share plan (which includes WiFi hotspot). But USB tethering does still work.
Click to expand...
Click to collapse
On LMY48I stock WiFi hotspot works great for me. I also have a AT&T family share plan and I connect my tablet to the WiFi hotspot quite frequently.

alryder said:
On LMY48I stock WiFi hotspot works great for me. I also have a AT&T family share plan and I connect my tablet to the WiFi hotspot quite frequently.
Click to expand...
Click to collapse
Working now, here too.

wifi tether unable to open log-file
simms22 said:
tether is normally in main settings, more.. is it not in cm?
Click to expand...
Click to collapse
Am new at this and in uncharted territory. I rooted my new Google Nexus 6 using the WugFresh, Nexus Root Toolkit 2.0.4, Root program downloaded. Also downloaded Busybox, ES File Explorer, Superuser, TWRP, Root Browser. I fail to understand which one gives me root control. Also loaded Cyanogen Mod 12.1 nightly build as a ROM. Also downloaded Wifi Tether 3.4 Experimental 1-07202013 which has worked in my old rooted Galaxy Nexus since 2013, and previous versions since 2011.
I'm thinking I am in over my head as I attempt to deal with a new system, Lollipop, and now Marshmallow 5.1.1 and new phone Nexus 6 and older tether program? Can you suggest or recommend a ROM with perhaps more compatibility and ease of tethering? Wife and I live deep in country and our phone tether only access we have over Verizon with the repeater.
Ray

[How to]VS980 Confirmed Root and Recovery Installation Method

Hey guys,
Recently, I have been trying to re-root my LG G2 VS980 that was returned to lollipop stock (LG Firmware). However, all the tools I knew that previously worked, (Ioroot, Towelroot, Stumproot, Kingoroot, etc..) did not work. After months of testing, I finally found one app that currently works called KingRoot.
As far as I know, it is the only root method that acutally still works after LG patched most of the exploits so I thought I would share the info with you guys in case some of you are still interested in rooting your G2.
Instructions:
1. Install Kingroot: http://kingroot.net/ (the APK doesn't work for the G2)
2. Go to settings in your phone and click the build number 7-10 times to enable Developer Options
3. Go to Developer Options and enable USB Debugging
4. plug the phone into your computer and launch the program. Make sure you see the USB Debugging card that will pop up on your phone.
Launch the program and allow the program to root your phone.
Sidenote: The only downside to the app is it is all in Korean but it is very easy to tell what it is asking due to excellent pictures
After you receive root, download the app RootChecker just to make sure.
To Install TWRP:
1. Instructions: Go to Play Store and type in the search window, "AUTOREC".
2. Select the correct variant: ex. VS980=Verizon etc...
3. Install the app.
4. Watch TWRP Install on your phone.
5. Reward yourself on your hard work with a pat on the back.
So that's it; A fast easy, and trouble free method on getting root and installing TWRP

Thanks for this. I recently acquired a G2, and will be trying this out tonight.

tribalartgod said:
Thanks for this. I recently acquired a G2, and will be trying this out tonight.
Click to expand...
Click to collapse
No problem. Have fun with your custom ROM of choice.

Can you share the setup files? I also need to re-root my Verizon phone. The kingroot ownload links looks dead
i downlaoded it from here. I have usb dev enabled. now what? http://kingroot-pc.en.uptodown.com/download
Stuck on that step. I know its telling me to enable USB debuggin which I have, it doens' do anythong when I click Go in Korean

I managed to enable debugging mode which was by setting the 'USB Type" on the phone to "Internet -> Ethernet"
But Kingroot isn't managing to root the phone. It goes 100 percent and nothing.
Ioroot managed to get the phone into the reboot phase but the phone no longer processed the splash screen of the recover/bootloader. The splash screen which has the android mascot on its back with abdomen open.
"LG G2 One lick Tool" makes the phone go to "download mode" but its stuck at 0 percent. I disconnect and replug in hope of kickstarting it, doesn't work.
What can I do now?

y300owner said:
I managed to enable debugging mode which was by setting the 'USB Type" on the phone to "Internet -> Ethernet"
But Kingroot isn't managing to root the phone. It goes 100 percent and nothing.
Ioroot managed to get the phone into the reboot phase but the phone no longer processed the splash screen of the recover/bootloader. The splash screen which has the android mascot on its back with abdomen open.
"LG G2 One lick Tool" makes the phone go to "download mode" but its stuck at 0 percent. I disconnect and replug in hope of kickstarting it, doesn't work.
What can I do now?
Click to expand...
Click to collapse
Where you able to get it to work? I am running into the same problems.
Sent from my SM-N920V using Tapatalk

y300owner said:
Can you share the setup files? I also need to re-root my Verizon phone. The kingroot ownload links looks dead
i downlaoded it from here. I have usb dev enabled. now what? http://kingroot-pc.en.uptodown.com/download
Stuck on that step. I know its telling me to enable USB debuggin which I have, it doens' do anythong when I click Go in Korean
Click to expand...
Click to collapse
Hmm... Sorry for the late response. Try this link and see if it works: http://www.kingroot.org/

mach01 said:
Hmm... Sorry for the late response. Try this link and see if it works: http://www.kingroot.org/
Click to expand...
Click to collapse
Thanks I tried almost almost everything.
Stumbled upon Stump root last night and it brute forced it way in.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Jshokamp said:
Where you able to get it to work? I am running into the same problems.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
What problem? Check one of the thread I started. Posted everything on it.

y300owner said:
Thanks I tried almost almost everything.
Stumbled upon Stump root last night and it brute forced it way in.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
What problem? Check one of the thread I started. Posted everything on it.
Click to expand...
Click to collapse
You on 39aa or just 39a?

Lawlrus said:
You on 39aa or just 39a?
Click to expand...
Click to collapse
No idea. I was on a downgraded stock ROM, VS980_27A or was it VS980_24A. Can't remember; 4.4.2
Whatever it was, none of the popular rooting method was working. They were managing to do 'semi root' as in root message was displayed in "hard reset mode" and in 'download mode' but there was no root when the OS fully booted. The 'stock recovery' was also corrupted as in it showed a dead android with red exclamation mark. From the searching I did, people were saying there was no recovery installed so I needed one but I could not install. No stock recovery means no 'adb'.
Stump root gave 'complete' root. I hope you understand what I'm trying to say.

Will this work if I am on the 39aa update from Verizon? I am skeptical about this because this is my only phone and don't need to mess it up.

UserofAndroid1813 said:
Will this work if I am on the 39aa update from Verizon? I am skeptical about this because this is my only phone and don't need to mess it up.
Click to expand...
Click to collapse
I don't think I've seen a way to root 39aa as of yet. One of our developers was asking about it as well, if you do find a way, please @ me so I can hook him up
I'm still looking around for a way.

Lawlrus said:
I don't think I've seen a way to root 39aa as of yet. One of our developers was asking about it as well, if you do find a way, please @ me so I can hook him up
I'm still looking around for a way.
Click to expand...
Click to collapse
I tried and failed at it. I am downgrading to VS98039A_05 and going from there. it seems VS9803AA was meant to patch root and also SF security patches.

This XML file does not appear to have any style information associated with it.
The document tree is shown below.
<Error><Code>AccountProblem</Code><Message>
Your Google account is not currently enabled for this operation. Please check https://code.google.com/apis/console/#:billing to see if you have a past due balance or if the credit card (or other payment mechanism) on your account is expired. You can find additional information at https://developers.google.com/storage/docs/signup</Message></Error>

Thanks for this. For people who don't want to mess with Korean, or if Kingroot doesn't work, LG One Click Root still works on VS9803AA, although you may have to run it 3 or 4 times. Here's the original post: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
And here's a good guide: http://webtrickz.com/how-to-root-lg-g2-running-lollipop-with-lg-one-click-root/

Interesting... I've tried that method four times and it never worked for me. Good to hear it works for other people though. I agree not to many people want to use
Korean deciphering skills just to root their phone but its just an option.

marathonjon said:
Thanks for this. For people who don't want to mess with Korean, or if Kingroot doesn't work, LG One Click Root still works on VS9803AA, although you may have to run it 3 or 4 times. Here's the original post: http://forum.xda-developers.com/lg-g...lipop-t3056951
And here's a good guide: http://webtrickz.com/how-to-root-lg-...ne-click-root/
Click to expand...
Click to collapse
Both of these links are dead.

CruelSun said:
Both of these links are dead.
Click to expand...
Click to collapse
Links are fixed. The whole URLs don't show in the post, but if you click on them, they should work.

those with the issue of kingroot not reading your phone plugged in. put your usb option on phone to PTP camera mode and it will work now.

Even doing all, i m still unable to get my phone recognized. Switched many times befween ptp
Sent from my VS980 4G using Tapatalk
---------- Post added at 05:55 AM ---------- Previous post was at 05:54 AM ----------
Furqan Ullah said:
Even doing all, i m still unable to get my phone recognized. Switched many times befween ptp
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
And other file transfer option. USB picture is displaying sometimes or sometimes circle
Sent from my VS980 4G using Tapatalk

Confusion About Best Root Method For Fire 7 Tablet (9th generation)

Hello,
I recently purchased a Fire 7 tablet and have a question about rooting it. Currently my tablet has the following out of the box:
- Fire 7 (9th generation)
- Build number = 0002517050244
- Fire OS = 6.3.1.2
After reading many of the posts on XDA, I am confused how to do root. Here are the following posts that talk about root for the Fire 7:
- https://forum.xda-developers.com/amazon-fire/general/fireos-6-3-1-0-amazon-fire-7-2019-t3937209
- https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
- https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
- https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
Which is the best recommended method to root? I don't think I need to install a custom ROM, unless it turns out I need to install a de-bloated stock version.
Thanks in advance!

Software method here (good up to 6.3.1.2) and most recent.
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365

Michajin said:
Software method here (good up to 6.3.1.2) and most recent.
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
Click to expand...
Click to collapse
Thank you... that's what I figured. I'll let everyone know my results.

After much tinkering around, I finally got it to root (or at least I think I did). A couple of things:
- How do I confirm whether I actually have root?
- After following the instructions, what should the next steps be? Should I upgrade the software OTA? I remember reading something about possibly disabling OTA, but I can't remember if this applies?

gil_happy said:
After much tinkering around, I finally got it to root (or at least I think I did). A couple of things:
- How do I confirm whether I actually have root?
- After following the instructions, what should the next steps be? Should I upgrade the software OTA? I remember reading something about possibly disabling OTA, but I can't remember if this applies?
Click to expand...
Click to collapse
Hi, any comments on this? Since my Wifi has been disabled the entire time, I don't want to enable it until I know whether I need to disable updates. I don't know if the Fire 7 will automatically try to do an update and break root, etc. Secondly, how do I tell if I have root (keeping in mind that Wifi is still disabled)?
Thanks!

gil_happy said:
Hi, any comments on this? Since my Wifi has been disabled the entire time, I don't want to enable it until I know whether I need to disable updates. I don't know if the Fire 7 will automatically try to do an update and break root, etc. Secondly, how do I tell if I have root (keeping in mind that Wifi is still disabled)?
Thanks!
Click to expand...
Click to collapse
Did you make it through both the bootrom-step and the fastboot-step? Can you boot into TWRP? I would recommend changing to lineage if android is your flavor. You can install a root checker, but if you followed the steps, you should have magisk installed (magisk is a root manager). What exactly are you looking to do with the tablet?

gil_happy said:
After much tinkering around, I finally got it to root (or at least I think I did). A couple of things:
- How do I confirm whether I actually have root?
- After following the instructions, what should the next steps be? Should I upgrade the software OTA? I remember reading something about possibly disabling OTA, but I can't remember if this applies?
Click to expand...
Click to collapse
Michajin said:
Did you make it through both the bootrom-step and the fastboot-step? Can you boot into TWRP? I would recommend changing to lineage if android is your flavor. You can install a root checker, but if you followed the steps, you should have magisk installed (magisk is a root manager). What exactly are you looking to do with the tablet?
Click to expand...
Click to collapse
Thanks so much for getting back to me. As far as making it through the bootrom-step and the fastboot-step, I think I successfully completed both steps as I can boot into TWRP (I assume booting in TWRP means successfully completing both steps?). A couple of things:
- As mentioned, I can boot into TWRP no problem. I can also see that Magisk is also installed (when I click on Magisk, it looks like it is attempting to access the Internet for updates).
- My Fire 7 currently has Fire OS = 6.3.1.2, but after what I think is the completed install, I still have not turned on the Wifi as I'm worried that something (including the OS) might auto-update and break something, e.g. root. That is why I was asking if OTA needs to be disabled?
- As far as my plans for my tablet, here is my original post (https://forum.xda-developers.com/amazon-fire/help/customize-fire-7-tablet-t4112223), but essentially we would like to use these for promotional purposes. To explain, I want to sent out a tablet to a potential client via mail, and when they power up the tablet, our logo will replace the Amazon / Fire logo (root is needed for that), then after it boots up, it boots right to a screen where there is a some type of product messaging (maybe with a graphic), and then a button that basically says 'press here to watch our video'. It really doesn't even need access to the internet.
Hopefully all of this makes sense?

gil_happy said:
Thanks so much for getting back to me. As far as making it through the bootrom-step and the fastboot-step, I think I successfully completed both steps as I can boot into TWRP (I assume booting in TWRP means successfully completing both steps?). A couple of things:
- As mentioned, I can boot into TWRP no problem. I can also see that Magisk is also installed (when I click on Magisk, it looks like it is attempting to access the Internet for updates).
- My Fire 7 currently has Fire OS = 6.3.1.2, but after what I think is the completed install, I still have not turned on the Wifi as I'm worried that something (including the OS) might auto-update and break something, e.g. root. That is why I was asking if OTA needs to be disabled?
- As far as my plans for my tablet, here is my original post (https://forum.xda-developers.com/amazon-fire/help/customize-fire-7-tablet-t4112223), but essentially we would like to use these for promotional purposes. To explain, I want to sent out a tablet to a potential client via mail, and when they power up the tablet, our logo will replace the Amazon / Fire logo (root is needed for that), then after it boots up, it boots right to a screen where there is a some type of product messaging (maybe with a graphic), and then a button that basically says 'press here to watch our video'. It really doesn't even need access to the internet.
Hopefully all of this makes sense?
Click to expand...
Click to collapse
You should be able to disable OTA with renaming this app,
/system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk
Also a package disabler will work.
I have had sucess with
adb shell
$ su
# pm disable com.amazon.device.software.ota
Or
#pm uninstall com.amazon.device.software.ota
There are a few ways...
Easy to check, do one of these OTA disables connect wifi, check for updates. If you see it downloading, turn wifi back off. If it just closes, or says error, then OTA's are disabled. You might lose root, if you take an udpate, but TWRP should be safe. Make a backup in twrp to go back to what you have now.

Michajin said:
You should be able to disable OTA with renaming this app,
/system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk
Also a package disabler will work.
I have had sucess with
adb shell
$ su
# pm disable com.amazon.device.software.ota
Or
#pm uninstall com.amazon.device.software.ota
There are a few ways...
Easy to check, do one of these OTA disables connect wifi, check for updates. If you see it downloading, turn wifi back off. If it just closes, or says error, then OTA's are disabled. You might lose root, if you take an udpate, but TWRP should be safe. Make a backup in twrp to go back to what you have now.
Click to expand...
Click to collapse
Thanks so much for this! I didn't see anything with the name *.software.ota in that directory. The closest thing I saw was com.amazon.device.sync and sync.sdk.internal. Of course now when I try to boot up my Fire after attempting to reboot it using the touch screen, now my tablet doesn't power up :-/ I was doing so many things trying to get into the shell, I don't fully know what I'm doing. However, when this happened last time, I need to open the tablet, disconnect the battery, and then do some of the shell commands.

gil_happy said:
Thanks so much for this! I didn't see anything with the name *.software.ota in that directory. The closest thing I saw was com.amazon.device.sync and sync.sdk.internal. Of course now when I try to boot up my Fire after attempting to reboot it using the touch screen, now my tablet doesn't power up :-/ I was doing so many things trying to get into the shell, I don't fully know what I'm doing. However, when this happened last time, I need to open the tablet, disconnect the battery, and then do some of the shell commands.
Click to expand...
Click to collapse
Well if you cant find the ota the re-rename method, dont rename the other ones. I have always used disable
adb pm disable com.amazon.device.software.ota
Did you make a back up prior to doing anything as i suggested? What kind of things were you doing to try to get in a shell?
"Make a backup in twrp to go back to what you have now."