Develop Bugs

[HOWTO] Fix Appbrain fast web installer (using android_id)

Hi, after the update to froyo (in my case JP6) i found out the appbrain fast web installer wasn't working anymore. After some reading, it seems that the android_id (which this app uses) is set to a fixed number during the froyo update. This means the app cannot find a unique android_id to send the 'install instruction' to.
Source: http://forum.xda-developers.com/showthread.php?p=8604909#post86049
1. Make sure and backup your /dbdata/databases /com.android.providers.settings /settings.db file
Then in ADB or connectbot type the following
su
cd /dbdata/databases/com.android.providers.settings sqlite3 settings.db
sqlite> insert into secure (’name’, ‘value’ ) values (’android_id’,'device_id_goes_here’);
sqlite> .exit
Reboot
note 'device_id_goes_here’is your 16 digit HEX device ID
Click to expand...
Click to collapse
This fix seems to do the job, but i can't get it to work. Probably because i made a mistake with the usage of su and shell etc.
So i tried to fix it another way and this is how i did it (similar to the other fix):
1) With RootExplorer (or similar) navigate to: /dbdata/databases/com.android.providers.settings/
2) Make a backup of the file (by copying it)
3) Change the permissions of the file (using RootExplorer) ,so that it can be moved/sent to your pc using Dropbox,Gmail,Bluetooth etc. In this example i have moved it to my c:/ folder on windows.
4) When the file is on your pc. Run windows command (cmd) and navigate (using cd) to your /android/tools folder.
5) Execute: 'sqlite3 c:/settings.db
6) Now type in (after sqlite>): insert into secure (’name’, ‘value’ ) values (’android_id’,'device_id_goes_here’);
Note: 'device_id_goes_here' is a random (so you can choose whatever you want) 16 digit number.
7) Type: .exit and close the cmd box.
8) copy the settings.db file back to your phone and move it back to /dbdata/databases/com.android.providers.settings/
Choose yes when overwrite prompt pops up.
9) Reboot your device
10) Register your device using the 'Fast web installer' app on your phone.
11) DONE! You're ok again to install apps OTA using the appbrain market!
Click to expand...
Click to collapse
Note, if you don't know how to do step 4-7, read some articles about how to set up and use adb (since that also contains the sqlite3 tool)
I hope this helps for people having problems with this.

Hanness said:
Hi, after the update to froyo (in my case JP6) i found out the appbrain fast web installer wasn't working anymore. After some reading, it seems that the android_id (which this app uses) is set to a fixed number during the froyo update. This means the app cannot find a unique android_id to send the 'install instruction' to.
Source: http://forum.xda-developers.com/showthread.php?p=8604909#post86049
This fix seems to do the job, but i can't get it to work. Probably because i made a mistake with the usage of su and shell etc.
So i tried to fix it another way and this is how i did it (similar to the other fix):
Note, if you don't know how to do step 4-7, read some articles about how to set up and use adb (since that also contains the sqlite3 tool)
I hope this helps for people having problems with this.
Click to expand...
Click to collapse
Looks good. One question, how do you find out what your original device ID is? I have a UK unbranded GT-I9000... what's the ANDROID ID for that?

Ah, you just make one up. I used SQLite Editor to just edit the file, made up my own number and rebooted. Works fine now. A bit simpler than your suggestion above.

tokyogtr said:
Ah, you just make one up. I used SQLite Editor to just edit the file, made up my own number and rebooted. Works fine now. A bit simpler than your suggestion above.
Click to expand...
Click to collapse
That should indeed be easier
In the post I refer to in the captivate forum, there is mentioned an app to find out your android_id. But to know your original id, you would first have to reflash to an older firmware where the id is not touched. But it is true, you can just make up your own 16digit number. Only some games with online highscores fixed to the id instead of an account could benefit to know your old id, I think.

Worked for me!
Sent from my GT-I9000 using Tapatalk

hum
shud be easier to just download "Android ID Changer" from market after installing sqlite3. does the same trick.. but more user-friendly for people not so comfortable to use adb shell.

trasig said:
shud be easier to just download "Android ID Changer" from market after installing sqlite3. does the same trick.. but more user-friendly for people not so comfortable to use adb shell.
Click to expand...
Click to collapse
Hmm maybe Iḿ retarded, but how do I install sqlite3 to my phone?

No clue what he meant with installing sqlite3, I just downloaded the said Android ID Changer, made up and applied an ID and now Fast Web Installer works just fine.
I don't know if it is just coincidence or due to this, but before that I had tons of "download unsuccessfull" errors with the Market. Downloads failed nine out of ten times. Now, with changed ID, it works flawlessly again! My phone runs on JP6 Voodoo Doctor Edition 2.1.
Thanks for this advice!

I just installed the ID changer, entered a new code and rebooted, but the ID had not changed..
first time i tried it i got an "error editing databases".... do you have to change permissions to the folder/directory for the settings.db?

ukdtweak said:
I just installed the ID changer, entered a new code and rebooted, but the ID had not changed..
first time i tried it i got an "error editing databases".... do you have to change permissions to the folder/directory for the settings.db?
Click to expand...
Click to collapse
same problem here....

The only thing remotely related I could think of is that I had my system folder mounted as R/W with SGS Toolbox. But does that affect dbdata?

Check SGS Toolbox on mine and system was already mounted as RW...
I have tried changing the permissions with Root Explorer, to dbdata etc. but after rebooting, they are back as they were?

Beats me... but I can now confirm that the "download unsuccessfull" errors are back in place. It was just a coincidence after all, and shows that the blame is on Google, not any specific ROM or mod.
Fast Web Installer still worked though, even made it past the "unsuccessfull" barrier.

Wonderful fix!
Hanness, have you considered reporting this to Samsung? I think having the proper Android ID set and retained during firmware updates is quite important.

miki4242 said:
Wonderful fix!
Hanness, have you considered reporting this to Samsung? I think having the proper Android ID set and retained during firmware updates is quite important.
Click to expand...
Click to collapse
According to this, this may be due to ro.serialno not being set in build.prop

trasig said:
shud be easier to just download "Android ID Changer" from market after installing sqlite3. does the same trick.. but more user-friendly for people not so comfortable to use adb shell.
Click to expand...
Click to collapse
Android ID Changer did the trick for me . (I have not done anything with sqlite3.)

I used http://www.dbsoftlab.com/database-editors/database-browser/overview.html to edit settings.db as explained.
Works like a charm. Downloads & Updates are flying in!
Edit: After few downloads it stucks again, I deleted Market data. Works again. Bugs everywhere ...

Hanness said:
Hi, after the update to froyo (in my case JP6) i found out the appbrain fast web installer wasn't working anymore. After some reading, it seems that the android_id (which this app uses) is set to a fixed number during the froyo update. This means the app cannot find a unique android_id to send the 'install instruction' to.
Source: http://forum.xda-developers.com/showthread.php?p=8604909#post86049
This fix seems to do the job, but i can't get it to work. Probably because i made a mistake with the usage of su and shell etc.
So i tried to fix it another way and this is how i did it (similar to the other fix):
Note, if you don't know how to do step 4-7, read some articles about how to set up and use adb (since that also contains the sqlite3 tool)
I hope this helps for people having problems with this.
Click to expand...
Click to collapse
Thank you very much...I followed your instructions exactly and managed to fix it. Android ID changer didn't work for me.

sadly appbrain is blocked in China for whatever reason I don't know... so that won't work for me hehe

stassano said:
sadly appbrain is blocked in China for whatever reason I don't know... so that won't work for me hehe
Click to expand...
Click to collapse
oh well, the great firewall of china at work again.

Lockscreen Rotation Android 4.2.x

Force enable lockscreen rotation
Code:
setprop lockscreen.rot_override true
Force disable lockscreen rotation
Code:
setprop lockscreen.rot_override false
On devices that already can rotate, this does nothing.
Code should work on all AOSP ROMs with lockscreens that don't rotate, unless the code there has been modified.
Resets on reboot though I think

Great find. Thanks!

Thanks man, I have a DIY dock for mine and the fact I had to enter my PIN sideways everytime I unlock my device driving me insane.

Can this code be used on the fly? I'm using a app at the moment (called Rotate) which can enable, disable lockscreen rotation. however this is heavy on memory and I want to simply do this with a script in Tasker.
---------- Post added at 04:58 PM ---------- Previous post was at 04:37 PM ----------
Just ran this from terminal emulator as root and it worked! Awesome - but it is lost on reboot so I need to be able to run this as a script in tasker - scripting looks tricky in Tasker though. Open to ideas!

I have enabled rotation by modifying bools.xml file and now I get to know that JB 4.2 has different rotation texts to enable rotation!
How about Launcher?

privatesam said:
Just ran this from terminal emulator as root and it worked! Awesome - but it is lost on reboot so I need to be able to run this as a script in tasker - scripting looks tricky in Tasker though. Open to ideas!
Click to expand...
Click to collapse
If you run it from a terminal emulator, it's temporary. If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
manumanfred said:
I have enabled rotation by modifying bools.xml file and now I get to know that JB 4.2 has different rotation texts to enable rotation!
How about Launcher?
Click to expand...
Click to collapse
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.

Awesome. This worked for me on 4.1.2 as well. Thanks!
Really useful in the car since I don't have the official car dock. No more unlocking sideways!

Cilraaz said:
If you run it from a terminal emulator, it's temporary. If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Click to expand...
Click to collapse
I know that, that's why I have modified bools.xml file to enable rotation on launcher + lockscreen.
I think JB 4.2.x have also the changed code for launcher rotation...

manumanfred said:
I know that, that's why I have modified bools.xml file to enable rotation on launcher + lockscreen.
I think JB 4.2.x have also the changed code for launcher rotation...
Click to expand...
Click to collapse
Does anyone have an answer to whether they have changed the code in 4.2? I can't find a bools.xml file anywhere - and no one seems to point at it. Also, no one says exactly where the suggested code should sit in the build.prop file - at the end, in the 'build' section, at the front? And it doesn't work on android 4.2.2 as far as I can tell although the terminal emulator temporary method works. And while you're firguring that out - can you tell me a way (without an app) to get the screen to stay awake after rebooting? Why won't that option remain set in Developer Options?

dosent work for me
xaueious said:
Force enable lockscreen rotation
Code:
setprop lockscreen.rot_override true
Force disable lockscreen rotation
Code:
setprop lockscreen.rot_override false
On devices that already can rotate, this does nothing.
Code should work on all AOSP ROMs with lockscreens that don't rotate, unless the code there has been modified.
Resets on reboot though I think
Click to expand...
Click to collapse
I tried this command in the terminal and no error message came.i.e it got executed properly Then when i see the lock-screen it is always in portrait mode.
Cant manage to get it to landscape mode. My auto rotation is on.
I am on 4.2.2 and using NOVA launcher. Xperia S OPENSEMC ROM.
Any idea y i am not able to rotate my lockscreen ??

siddharthisback said:
I tried this command in the terminal and no error message came.i.e it got executed properly Then when i see the lock-screen it is always in portrait mode.
Cant manage to get it to landscape mode. My auto rotation is on.
I am on 4.2.2 and using NOVA launcher. Xperia S OPENSEMC ROM.
Any idea y i am not able to rotate my lockscreen ??
Click to expand...
Click to collapse
Run Terminal as root, type "su" (no quotes), then enter, then the command.

Cilraaz said:
... If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
Click to expand...
Click to collapse
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)

dark0shark said:
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
Click to expand...
Click to collapse
Thank you for this. I wasn't sure if there was a specific spot in build.prop where I had to insert the line. The temporary fix in Terminal Emulator worked for me, but now it sticks after boot! I was sick of having to unlock my device sideways when it was in my car mount. The only weird thing is that it smooshes my wallpaper instead of switching to the landscape orientation, but I can live with that.

laur3n.newm4n said:
... I was sick of having to unlock my device sideways when it was in my car mount.
Click to expand...
Click to collapse
Yes, the car mount in heads up position with the cables (USB-power and 3,5 audio jack) to the bottom were exactly my reason to add this option permanently, too. The position of this environment variable in the configuration file build.prop does not matter, it is just common sense to add additional lines at the end, so you can find them easily.

dark0shark said:
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
Click to expand...
Click to collapse
Thank you for outlining this -- it helped me remember what to do!

and kaferei
Jeffreycat said:
Thank you for outlining this -- it helped me remember what to do!
Click to expand...
Click to collapse
Indeed -- very helpful and worked for me as well!

basic build.prop editing to enable pie on sgh-i747m
Shibang said:
Indeed -- very helpful and worked for me as well!
Click to expand...
Click to collapse
Thanks for providing the info on this basic build prop prop editing !
Ive been reading CyanogenMod 10.1 – A Complete Hands-On Review & Guide
by Haroon Q Raja and really wanted to enable Pie,etc on my rooted Samsung SGH I747m. With your help I was able to edit my build prop as was suggested by a comment I picked up on to:
ro.product.manufacturer=LGE
ro.product.model=Nexus 4
This didnt make any difference. Is there something else that needs to be changed?
Samsung G3 SGH-I747M Rogers

Cilraaz said:
...
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Click to expand...
Click to collapse
Redscorpian said:
Does anyone have an answer to whether they have changed the code in 4.2? I can't find a bools.xml file anywhere - and no one seems to point at it. Also, no one says exactly where the suggested code should sit in the build.prop file - at the end, in the 'build' section, at the front? And it doesn't work on android 4.2.2 as far as I can tell although the terminal emulator temporary method works. And while you're firguring that out - can you tell me a way (without an app) to get the screen to stay awake after rebooting? Why won't that option remain set in Developer Options?
Click to expand...
Click to collapse
No one can tell?

Some users who flashed the leaked JWR66N on their N4's report there is no full app rotation anymore in the Camera app, just the icons. So another change to feel optimistic about 4.3.

madd0g said:
Some users who flashed the leaked JWR66N on their N4's report there is no full app rotation anymore in the Camera app, just the icons. So another change to feel optimistic about 4.3.
Click to expand...
Click to collapse
Speaking of the camera, I played around with a iPad yesterday at the local store, i felt that Apple's shutter button have a better placement as compared to Google's. The shutter button is placed by the right side of the app, falls just nice of my thumb.
Beamed from my Grouper

How to STOP the Sprint update notification [GUIDE & VIDEO]

You can follow this guide to stop the Sprint update notification using the latest version of ES File explorer. This instruction is for the Sprint Samsung Galaxy note II. This is known to work on other Samsung devices as well. This guide will begin from scratch so that anyone can follow it from square one. If you already have root and ES File Explorer set up you can skip to step 7
See a video demonstration here http://www.youtube.com/watch?v=ifG5iPSFuCE
1. First be sure you have superuser access (root access). You can use a root checker like this one to be sure
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
2. Download and install ES File explorer. You can get that here...
https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
3. Open ES File explorer and grant root permission. Go into settings and set your preferences
4. Tap your device menu
5. Tap Tools
6. Tap root explorer.
7. The root explorer menu will pop up and you'll tap Mount R/W
8. Fill in all the bubbles for RW and tap OK
9. Navigate to the root of your device (At the Top you'll see the root directory is listed as "Device" or "/")
10. Tap the File named "etc"
11. Tap the File named "security"
12. Long press on the otacerts.zip until the check box appears and put a check in it.
13. Tap more
14. Tap properties
15. Place check marks in the read and write boxes and Tap ok
16. Tap rename (on the bottom action bar)
17. Rename the otacerts.zip file to otacerts.bak and tap ok
18. Tap refresh (bottom action bar)
19. Pull down the notification curtain and accept the update. *Some devices reboot here. (if the notice isn't in your notification bar just go on to the next step)
20. On your homescreen open your device menu and Tap system settings.
21. Scroll to and select System update.
22. Tap Update firmware.
Your device will say it is up to date and you won't get the notification anymore. If you do then reboot and start over because you skipped something.
If this helped you feel free to click the "thanks" button.

Space reserved

Thankd
Sent from my SPH-L900 using xda app-developers app

There's easier way just freeze updater
Sent from my GT-I9505 using Xparent Skyblue Tapatalk 2

vasiaeva said:
There's easier way just freeze updater
Sent from my GT-I9505 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
About that... I do appreciate your comment but I wanted to make a guide (and video) to help the most people. I felt like giving a free option here would be the best way to go.
I know there are apps that can freeze the updater but I didn't want to get into a comparison of the apps that may do it or provide instruction for every single one of them. Also there have been reports that freezing the updater didn't work or caused other issues. The solution I provided will work on the Sprint SGN2 (and other Samsung devices) and only requires ES File Explorer which I feel very comfortable recommending and is free.
I would like to consider all the options, though. So, going forward if we're going to recommend alternative solutions I think it would be best if a guide (or a link to a guide or video) would also be posted with it...or at least some detailed instructions. This way the most people will get the most out of it.

vasiaeva said:
There's easier way just freeze updater
Sent from my GT-I9505 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Is it called Updater, when looking for it to freeze, incase asked ??

DonB. said:
Is it called Updater, when looking for it to freeze, incase asked ??
Click to expand...
Click to collapse
First backup, in some roms it disabled by default and i'm not sure but it should be some like system updater or updater some like that

This is an excellent guide and a sure and EASY way to get rid of those pesky updates.

vasiaeva said:
First backup, in some roms it disabled by default and i'm not sure but it should be some like system updater or updater some like that
Click to expand...
Click to collapse
No need to do any backup using the method in the OP just follow the instructions or watch the video here
http://www.youtube.com/watch?v=ifG5iPSFuCE

just got my sprint note 2 last night its on 4.12 followed the vid and was ok for about 1 hour now i'm getting a thing for a 28.9 mb system update. how big is the 4.3? is it safe to take this little one? and I am rooted at this point thanks

timezone12 said:
just got my sprint note 2 last night its on 4.12 followed the vid and was ok for about 1 hour now i'm getting a thing for a 28.9 mb system update. how big is the 4.3? is it safe to take this little one? and I am rooted at this point thanks
Click to expand...
Click to collapse
The update notice you're seeing now is minor. It contains a security enhancement and nothing else worth mentioning. You needn't worry about it.
On a side note if you want 4.3 and don't want to wait for the OTA update you can get it here
http://forum.xda-developers.com/showthread.php?t=2541395
Cheers to lorjay589 for doing the heavy lifting.
regards

chzeckmate said:
You can follow this guide to stop the Sprint update notification using the latest version of ES File explorer. This instruction is for the Sprint Samsung Galaxy note II. This is known to work on other Samsung devices as well. This guide will begin from scratch so that anyone can follow it from square one. If you already have root and ES File Explorer set up you can skip to step 7
See a video demonstration here http://www.youtube.com/watch?v=ifG5iPSFuCE
1. First be sure you have superuser access (root access). You can use a root checker like this one to be sure
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
2. Download and install ES File explorer. You can get that here...
https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
3. Open ES File explorer and grant root permission. Go into settings and set your preferences
4. Tap your device menu
5. Tap Tools
6. Tap root explorer.
7. The root explorer menu will pop up and you'll tap Mount R/W
8. Fill in all the bubbles for RW and tap OK
9. Navigate to the root of your device (At the Top you'll see the root directory is listed as "Device" or "/")
10. Tap the File named "etc"
11. Tap the File named "security"
12. Long press on the otacerts.zip until the check box appears and put a check in it.
13. Tap more
14. Tap properties
15. Place check marks in the read and write boxes and Tap ok
16. Tap rename (on the bottom action bar)
17. Rename the otacerts.zip file to otacerts.bak and tap ok
18. Tap refresh (bottom action bar)
19. Pull down the notification curtain and accept the update (if this isn't in your notification bar just go on to the next step)
20. On your homescreen open your device menu and Tap system settings.
21. Scroll to and select System update.
22. Tap Update firmware.
Your device will say it is up to date and you won't get the notification anymore. If you do then reboot and start over because you skipped something.
If this helped you feel free to click the "thanks" button.
Click to expand...
Click to collapse
Did exactly as described following the YouTube Video. Restarted and got the update notification. It did not work.

ArtooDetoo said:
Did exactly as described following the YouTube Video. Restarted and got the update notification. It did not work.
Click to expand...
Click to collapse
I don't want to seem contentious but you must have missed something in the process. This process is tried and true and has worked for tens of thousands of people so you most likely missed some minor thing. At any rate, when done exactly right it works.
I would suggest that you first make sure you're rooted and if so make sure that you've granted root to ES File explorer. Next make sure the otacerts.zip file has retained the name change to otacerts.bak and if it didn't then you've got permissions problems. Next in ES make sure root explorer has RW selected on each item. Make sure the icon for the otacerts file looks like a question mark (if it looks like a zip start over).
The best thing to do is just repeat the process. Take it slow and don't get frustrated. If you'd like to make a video of you going through the process I can look at it and tell you what you're missing.

chzeckmate said:
I don't want to seem contentious but you must have missed something in the process. This process is tried and true and has worked for tens of thousands of people so you most likely missed some minor thing. At any rate, when done exactly right it works.
I would suggest that you first make sure you're rooted and if so make sure that you've granted root to ES File explorer. Next make sure the otacerts.zip file has retained the name change to otacerts.bak and if it didn't then you've got permissions problems. Next in ES make sure root explorer has RW selected on each item. Make sure the icon for the otacerts file looks like a question mark (if it looks like a zip start over).
The best thing to do is just repeat the process. Take it slow and don't get frustrated. If you'd like to make a video of you going through the process I can look at it and tell you what you're missing.
Click to expand...
Click to collapse
All of the things you mentioned I did. I am running a stock rom and am rooted. That being said, I may have posted too quickly before. After performing the tasks that you outlined very clearly, the notification returned upon reboot. I slid it away and it has not returned. So, I humbly withdraw my previous post.

ArtooDetoo said:
All of the things you mentioned I did. I am rooted running a stock rom and am rooted. That being said, I may have posted too quickly before. After performing the tasks that you outlined very clearly, the notification returned upon reboot. I slid it away and it has not returned. So, I humbly withdraw my previous post.
Click to expand...
Click to collapse
If you wanna test to see if it comes back you could reboot again. If it doesn't come back after a reboot then you're all set. Let us know how it goes.
best regards

chzeckmate said:
If you wanna test to see if it comes back you could reboot again. If it doesn't come back after a reboot then you're all set. Let us know how it goes.
best regards
Click to expand...
Click to collapse
All good now. Thank you very much.

Thank you! This worked like a champ.

thisdidn't work on my note that 2 it's pushing the system 4. 3 the update. .. thoughts

treo4life said:
thisdidn't work on my note that 2 it's pushing the system 4. 3 the update. .. thoughts
Click to expand...
Click to collapse
I would suggest going through the process again. It's very easy to miss some small step in the process. Be sure you're rooted, make sure you've granted root to ES File explorer, make sure you have Root Explorer turned ON, make sure you have rw selected for all four selections under the Mount R/W menu, and make sure your name change of the otacerts.zip file sticks, make sure that the otacerts.bak file looks like a question mark and not a zip, and remember to refresh. Those are the most common things people overlook when running through this process.
Watch the video and follow precisely. Take it slow and don't let the video get ahead of you. I go really fast through it in the video so the pause button will be your friend. You'll get it don't worry.

chzeckmate said:
I would suggest going through the process again. It's very easy to miss some small step in the process. Be sure you're rooted, make sure you've granted root to ES File explorer, make sure you have Root Explorer turned ON, make sure you have rw selected for all four selections under the Mount R/W menu, and make sure your name change of the otacerts.zip file sticks, make sure that the otacerts.bak file looks like a question mark and not a zip, and remember to refresh. Those are the most common things people overlook when running through this process.
Watch the video and follow precisely. Take it slow and don't let the video get ahead of you. I go really fast through it in the video so the pause button will be your friend. You'll get it don't worry.
Click to expand...
Click to collapse
I got it figured out, had to click on the update. .

--[FIX]--SkyDragon G3 USB Fix

Like many of you new flashers, I have flashed the SkyDragon ROM and have noticed that there is no connectivity to the computer whatsoever, so I did a little digging. I went back and forth between 2 Nandroid backups and kept flashing parts of them until I could narrow down where this problem was coming from. I found out that it comes from the specific folder - data/property
There is a missing file called persist.sys.usb.config ,13B in size, and I have no idea what it does (maybe some of you could enlighten me) but throwing the old file into that folder, changing the permissions to rw-------- and rebooting worked like a charm.
I apologize for not sticking this into the development thread, however I'm a lurker with no input! :victory:
Without further ado,
I TAKE NO RESPONSIBILITY FOR ANY BORKEN DEVICES. IF YOU DON'T KNOW WHAT YOU'RE DOING, DON'T DO IT!
1. Download Root Browser and RB Text Editor
2. Navigate to /data/property
3. On the bottom bar, tap the "New" button
4. Click on "New file"
5. Enter the file name as follows:
persist.sys.usb.config
6. Click the file you just made and hit "Open as..."
7. Hit "Text file"
8. Click RB Text editor
9. Delete whatever is there and enter as follows:
auto_conf,adb
No spaces or caps!
10. Save the file by clicking the save button on the top right corner.
11. Reboot your phone
12.Profit
----------------------------------------------------------------------------------------------------------------------------------------
Steal this information, spread it around, someone post it to the development thread and make this ROM better!
If you're having any problems, don't hesitate to ask

i could just drop this in the proper location before flashing the rom yes ??

CheesyNutz said:
i could just drop this in the proper location before flashing the rom yes ??
Click to expand...
Click to collapse
Only if you're going to dirty flash it, but at that point, I'd just dirty flash it anyways. The file should already be there if you're on a ROM that can recognize your phone. I also do recommend a clean flash. I'm sorry if I made this difficult. When flashing the rom, it'll format /data which is where the file is held so if you had the file there already, it would just wipe it.

88keys6strings said:
Only if you're going to dirty flash it, but at that point, I'd just dirty flash it anyways. The file should already be there if you're on a ROM that can recognize your phone. I also do recommend a clean flash. I'm sorry if I made this difficult. When flashing the rom, it'll format /data which is where the file is held so if you had the file there already, it would just wipe it.
Click to expand...
Click to collapse
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone

CheesyNutz said:
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone
Click to expand...
Click to collapse
As long as it's after the wipe then yes. If you opened up the zip that contains the ROM, you could head into /data then create a new folder called property and throw the file in there then zip it back up and flash it. But you MUST put the file in /data/property AFTER you flash the ROM. You could drop the file into a downloads or media folder because those don't get touched then flash the rom then move it and change permissions then reboot as well.
So no, you cannot drop the file in it's PROPER location before you wipe, otherwise it'll get deleted. However, you can copy/paste it into say, mnt/sdcard/Download, via your root browser, beforehand then follow my instructions

I'll try when I get home in about six hours.

partylikeaninjastar said:
I'll try when I get home in about six hours.
Click to expand...
Click to collapse
For sure! Will await results

I hope the developers get to see this for the next update

I tried creating my own file as per the instructions (came to 13b size for the file too), but my phone isn't being recognized in android file transfer.
Then again, it wasn't recognized either when I was on stock rom (prior to flashing anything).

On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat. If I delete the file, it is recreated when enabling USB debugging....boot,adb,mtp.
Just a preliminary finding. I'm not well versed enough to explain or troubleshoot it any further. It did nothing to cure my USB problem.

Cablespider said:
On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat.
Just a preliminary finding. I'm not well versed enough to explain it further. It did nothing to cure my USB problem.
Click to expand...
Click to collapse
I may have overlooked something. I deleted some usb portion of the build.prop. Didn't change anything so i didnt think about it. If you make a backup then edit it deleting the usb part, then reboot that might get it to work.If you need specifics, I'll be next to a computer in about an hour and a half

Can someone just post the file here?
Sent from my LG-D851
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
I copied one of the persist.sys files from that folder to my sdcard and edited it with Rom Toolbox Pro. I opened it as a text file and deleted what was there, then added the stuff in the OP and saved. I then renamed the file to persist.sys.usb.config and added it to that folder and changed permissions and rebooted. Worked fine.
Sent from my LG-D851

Skizzy034 said:
Can someone just post the file here?
Sent from my LG-D851
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
I copied one of the persist.sys files from that folder to my sdcard and edited it with Rom Toolbox Pro. I opened it as a text file and deleted what was there, then added the stuff in the OP and saved. I then renamed the file to persist.sys.usb.config and added it to that folder and changed permissions and rebooted. Worked fine.
Sent from my LG-D851
Click to expand...
Click to collapse
Awesome! Glad it worked for you

This is from my stock rom with the modified skydragon kernel. place in root\data\property. let me know if this works. just rename it and drop the .zip part.

Cablespider said:
On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat. If I delete the file, it is recreated when enabling USB debugging....boot,adb,mtp.
Just a preliminary finding. I'm not well versed enough to explain or troubleshoot it any further. It did nothing to cure my USB problem.
Click to expand...
Click to collapse
Jephre said:
I tried creating my own file as per the instructions (came to 13b size for the file too), but my phone isn't being recognized in android file transfer.
Then again, it wasn't recognized either when I was on stock rom (prior to flashing anything).
Click to expand...
Click to collapse
partylikeaninjastar said:
I'll try when I get home in about six hours.
Click to expand...
Click to collapse
CheesyNutz said:
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone
Click to expand...
Click to collapse
UPDATED
Much easier now. Just tested it with a Nand that didn't work at all and followed the instructions and it worked flawlessly. Let me know if you have any more issues

aclegg2011 said:
This is from my stock rom with the modified skydragon kernel. place in root\data\property. let me know if this works. just rename it and drop the .zip part.
Click to expand...
Click to collapse
It should work just fine as long as you didn't actually compress it lol. Thank you for the upload!
ALSO
THIS IS MY 10TH POST!!! DEV SECTION HERE I COME!! :victory:

88keys6strings said:
1. Download Root Browser and RB Text Editor
2. Navigate to /data/property
3. On the bottom bar, tap the "New" button
4. Click on "New file"
5. Enter the file name as follows:
persist.sys.usb.config
6. Click the file you just made and hit "Open as..."
7. Hit "Text file"
8. Click RB Text editor
9. Delete whatever is there and enter as follows:
auto_conf,adb
No spaces or caps!
10. Save the file by clicking the save button on the top right corner.
11. Reboot your phone
12.Profit
Click to expand...
Click to collapse
I can now confirm that this does work. I now have working MTP again.

You guys could try adding "persist.sys.usb.config=mtp,adb" to the build.prop and see if that works.

No Mobile Data on Treble Roms

I've tried over 5+ different treble ROMs and the mobile data will not work. My friend @Spaceminer had helped me try to solve it by finding an apns-conf.xml as well as a flashable zip but no luck.
I'm using the Moto G6 Play XT1922-7 Boost Mobile Variant.
I'm sorry I haven't provided much detail to the issue but this basically sums it up.
Thank you for any help.

Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie

Alphita said:
Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie
Click to expand...
Click to collapse
Did you try to flash the vendor.img on TWRP?

sinkoo1979 said:
Did you try to flash the vendor.img on TWRP?
Click to expand...
Click to collapse
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks

Alphita said:
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks
Click to expand...
Click to collapse
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.

Spaceminer said:
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.
Click to expand...
Click to collapse
How do i set those permissions? Thanks in advance

Alphita said:
How do i set those permissions? Thanks in advance
Click to expand...
Click to collapse
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot

Spaceminer said:
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot
Click to expand...
Click to collapse
Thanks! I will try this the next time i flash a rom

Would someone be so kind enough to share their BOOST apn.config.xml that the replaced the one on with that does NOT work on these GSI's?? If you do I'll follow you and hit thanks all day. ??

Here's (see screenshot) the closest I've ever gotten far as having data on a gsi. I must have the wrong xml file. I am fully aware of the process described above and have even done it multiple ways after I knew the way described and how I was adding the apn xml was correct and I have zero data.
If someone will attach their apn.config.xml, the one that they acquired data from using the boost Mobile network I'll be extremely thrilled and forever greatful to add it to the thread I made over in guides section so that in the future people can solve this issue fast and get her running and have a jolly day. ? I made that thread (I'll change the name later today) initially to consolidate as much info as I could and put it all in the op so we can be a bit more organized. I just haven't figured out anything else so I can't add to it just yet. ? This would be a great addition if someone would be so cool enough to kick me down some knowledge far as what's the correct apn.config.xml to replace the og one in gsi to get data working. I've deleted the current apn xml and replaced it with the one I have, I've overwritten it, I've tried countless times messing with the telephony.db and I obviously can't do it. Please pleeeaasee post the proper apn xml so I can get this phone going and add to op over there. @Starkiller2
I hope everyone is having a good day. It hot as **** where I'm at today. ??

I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight

Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.

Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Vague and unhelpful. Need better directions on that I messed with sqlite editor for days on end swapping out telephony.db things and never did get it going.
Did you swap both of them??
Did you swap other files in telephony.db too?
Details...?
What files exactly did you extract in telephony.db?
Vague comments never help anyone. Better to not post at all then post some two word comment with a link.

I apologise, I'm driving across country and was making an effort to help in the little time I had, but you're right, better to not try at all. Which may be why you aren't getting any answers to your questions. Some info is usually better than none and can sometimes lead you in the right direction, but you won't even get that much snapping at everyone who doesn't immediately solve the problem you have and then rage quitting when you can't do it yourself. It makes people not want to put in any effort. You have 4000 posts I assumed you could figure out how to edit apns with an app from the play store. You're right. I should absolutely stop offering any input at all, but rather I should just start *****ing and whining when I'm not spoon fed like I see so much here.
And as I have posted directions in multiple other threads, I assumed you had done at least a cursory search for your answer(as per forum rules) which would've found those posts but I was apparently wrong there as well.
---------- Post added at 07:00 PM ---------- Previous post was at 06:45 PM ----------
Spaceminer said:
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.
Click to expand...
Click to collapse
Thank you. That's good to know

hi, there is in the web a file apns-conf.xml to download? or sombody take us a backup? Thanks

Hey gang, I too am having issues trying to simply get mobile data working on GSI's. I have a Pixel 3a, and have tried multiple Android 10 GSI's, all of them don't allow me to use mobile data. I have not tried the apns-conf.xml trick yet, as I am unsure if that's the answer if it hasn't worked for others. Android 11 does not use an apns-conf.xml in system/etc/ so I couldn't extract it from my current setup unfortunately. Wish you all luck, post back if you get something working.

not working, moist do you have rooted phone? because only on rooted phones you can do this trick

doid1 said:
not working, moist do you have rooted phone? because only on rooted phones you can do this trick
Click to expand...
Click to collapse
I'll probably flash a ROM this weekend and pull my xml to test this. I have Telus so I unfortunately can't help with the Boost users, but can at least help confirm whether this method works or not.

ok thanks i wait, my phone seems to be dead on 4g.. says: no registration..
I tried everything imaginable and perhaps even the unimaginable .. heheheh .. but the result is always the same: no recording on the 4g, so I'm more and more inclined that it is a hardware failure or even a damage to the eeprom memory because 'I have formatted everything and the mobile phone has recharged everything correctly but it was useless ..
I tried to see that maybe it has a sim locked, but I didn't manage to enter meta mode and try to force it also because only with miracle box there is a guide ... umh ... and I do not stop until I succeed in the objective, and then the next step will be to take a complete image of another mobile phone identical to mine and copy it over it (but it is almost impractical because I cannot find anyone who gives me a full backup of this phone) and then I will brutally try to put another image of another working smartphone on it, leaving only the crucial sectors intact (system, boot, vendor, recovery, preloader, everything else I format it hehehehh) I will know..

Well I have a ROM flashed and found the apns-conf.xml, which is not included on my stock ROMs (10 or 11). Now going to flash a GSI or two and do some tests to see if I can get any data working.
Edit: Couldn't get the apns-conf.xml to work. However, I did find out the some GSI's work right out of the box for my Pixel 3A, those included AOSP 10 / 11 by Phh, and the CAOS R build. Bless, qidroid, havoc booted fine but did not have mobile data working.