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.
Related
hey im not sure if i am the right section but i tried to search but none of the solutions i have found worked please help..
I apologize if i am in the wrong section
dr690n said:
hey im not sure if i am the right section but i tried to search but none of the solutions i have found worked please help..
I apologize if i am in the wrong section
Click to expand...
Click to collapse
1) Download the following file: http://xeno.bemaniso.ws/Launcher2.apk
2) Place file on the root of your SD Card.
3) Reboot into recovery, same method that you use to flash roms.
4) Under Clockwork, select Partitions.
5) Mount System through Clockwork
6) Unplug and Re-Plug in USB Cord to device or else you won't be able to continue.
7) Open a command prompt or whatever you use to use ADB, type adb shell
8) cd /system/app
9) rm ADWLauncher.apk
10) cp /sdcard/Launcher2.apk /system/app/
11) exit
12) Reboot phone normally.
Next time you flash a rom use winrar or 7zip to open the zip (do not unzip or extract it!!!). Go to system/app/adwlauncher.apk and delete it. Then drag and drop whatever launcher you want to use. Flash the new rom and you're done.
KCRic said:
Next time you flash a rom use winrar or 7zip to open the zip (do not unzip or extract it!!!). Go to system/app/adwlauncher.apk and delete it. Then drag and drop whatever launcher you want to use. Flash the new rom and you're done.
Click to expand...
Click to collapse
I thought stuff like that never works. ROM's and any other files such as apk's are usually signed. Therefore any modifications won't work and the package is corrupt unless you re-sign it. At least in my experience.
Hayzie said:
I thought stuff like that never works. ROM's and any other files such as apk's are usually signed. Therefore any modifications won't work and the package is corrupt unless you re-sign it. At least in my experience.
Click to expand...
Click to collapse
Clockwork let us flash unsingned .zip files, there is an option and you choose if you want clockwork to check if the files are singed or not, and as long as you dont screw and move stuff where is not supposed to be your not gonna get an "installaion aborted" message.... i always do that to remove apps i dont use from system/app before i flash the rom and i've never had a problem
but back on topic... yeah you can do what the second post says, or if you dont want launcher2 just install the launcher you want to use from the market or sdcard if you have the apk, set it to deafult home app then go to recovery and do steps 4 to 9 and reboot, adw should be gone.
Once you get everything set up, resigning is simple. Since you don't have to resign with this method though, that task it pointless.
Hayzie said:
I thought stuff like that never works. ROM's and any other files such as apk's are usually signed. Therefore any modifications won't work and the package is corrupt unless you re-sign it. At least in my experience.
Click to expand...
Click to collapse
I've never signed any of my rooms, ever. If you modify everything without unzipping it, using 7zip or the default package manager in ubuntu, there's no need to, regardless of what it is that you're replacing/modifying.
Hayzie said:
I thought stuff like that never works. ROM's and any other files such as apk's are usually signed. Therefore any modifications won't work and the package is corrupt unless you re-sign it. At least in my experience.
Click to expand...
Click to collapse
I just rename whatever I'm replacing it with to ADWLauncher and switch it out before I flash lol.
Noob rooter question: I was extracting the Oneclickroot file from Qbking and FSecure warned me about a virus (which it removed ) called "Exploit:Android/DroidRooter:B". I noticed then that the folder was missing this file: "rageagainstthecageare5.bin". I can turn off real time scanning and get that file to extract, but my question is, is this a valid file that is needed in OneclickRoot? Or is it really a virus?
rando991 said:
Noob rooter question: I was extracting the Oneclickroot file from Qbking and FSecure warned me about a virus (which it removed ) called "Exploit:Android/DroidRooter:B". I noticed then that the folder was missing this file: "rageagainstthecageare5.bin". I can turn off real time scanning and get that file to extract, but my question is, is this a valid file that is needed in OneclickRoot? Or is it really a virus?
Click to expand...
Click to collapse
in OP of the one-click root thread where you downloaded it.
Rodderik said:
Notes:
1. Button mappings are slightly different from older versions of CWM. Volume buttons = Up and Down, Power or Camera = Enter, Capacitive Back = Back. Capacitive Home also works as enter but not correctly from the main menu so if you hit it and the screen disappears hit Capacitive Home again or Capacitive Back to bring it back.
NOTE: As of 3.1.0.1 the buttons have been sorted out.
2. KNOWN ISSUE: When invoked, reboot recovery requires a re-plug of the usb cable for adb to work again. Simply unplug the usb cable and plug it back in.
3. If the script does not reboot your phone at the end please run the script again. If it still doesn't work reboot the phone and run the script again.
4. USB Mass Storage can be mounted from inside of recovery. 'adb shell' into the phone and type 'mountums' MAKE SURE YOU SAFELY REMOVE/EJECT BEFORE RUNNING 'umountums' to safely unmount sdcard.
NOTE: As of 3.1.0.1 mounting from the menu works again!
5. There is a Go Back menu option but it must be enabled. See the post here.
6. VIRUS ALERT!!! rageagainstthecage may be detected by your antivirus program but it is NOT harmful to your computer. See this post for an explanation.
Click to expand...
Click to collapse
The video tutorials are just tools to assist you. That doesn't mean you should not do your research.
It is not a virus.
From the developer Rodderick
http://forum.xda-developers.com/showpost.php?p=13868587&postcount=36
Thanks to all, I had gone thru a lot of the links, getting the files, looking at the videos, and reading the instructions, as well as gathering data on how to restore in case something went wrong, but somehow missed that line about the false positive. I even searched the forum afterwards about virus issues and though I didn't see that info in the link where i got the file I felt that this was a safe file. I think I was in information overload...Just wanted to be sure. Thanks for the answers anyway.
Hi Guys,
Firstly, thanks so much for the info on this community. I've followed loads of the threads and almost all of what I need to know is here.
I have a KF2 @ v10.3.1. I've rooted it and applied the 2nd bootloader using a homemade lead (thanks to the thread on that!). I started in Windows but switched to Kubuntu after getting driver issues etc.. To compound the problem, the KF2 is blocked by Amazon, which didn't help as I couldn't load apps whist it was stock. (It's not stolen or otherwise illegally obtained. Amazon sent it in error, and despite me contacting them to ask how to return it, they've never replied)
Anyhow, After following THIS thread, which appeared to go OK, after rebooting I'm unable to boot into Recovery. The blue screen just stays there. I can still boot normally, but I would like to load CM10 which is loaded as per the thread, along with gapps, both in zip format. I have read many threads about being stuck on the blue screen, but these are always locked and need to be restored, but I have no problem booting normally and the KF2 is not locked. I've searched this site and googled plenty.
I don't expect an exact answer, but if someone could just point me at what to look at, I'm sure I can find the rest of the info I need on here. :good:
Oh, also. Another quick question. I see that the CM10 images are constantly being updated, if (when I get mine working) I want to use one of these, is it simply a case of copying the zip file over? Or is there more to do than that.
Many thanks in advance.
You can boot normally? Into stock, I assume.
Run the apk tool from here:
http://forum.xda-developers.com/showthread.php?t=2106463
Should get you fixed right up
The zip file will have to be flashed from recovery. So, its a matter of copying the zip file (and gapps) over. Boot into recovery. Wipe data, cache, dalvik and system. Then flash rom first, the gapps.
Also, be VERY CAREFUL and make sure you have a GOOD DOWNLOAD by checking the md5 on the file. If you wipe the system (which deletes the stack file) you will not be able to boot into recovery or anything.
I still recommend that you purchase a fastboot cable.
Edit: also, when booting into recovery you might have to hit the power button a couple of times.
--
Sent from my mind to your screen.
Cheers mindmajick. I've tried to do this but still having a few problems.
If I use the wired version, the runme.bat does not have permissions to the data/app folder. I can't seem to run it in Kubuntu as it says I can't run a binary file if I make it executable, but says I don't have permission if I remove execute. (I'm looking into this - but I'm not very good with Linux, so lots of Googling!!...lol....) Also I see that there are some issues with this version with the wireless version being favored. Unfortunately as I'm unable to log onto my Amazon account, I can't use this method.
I will continue to try, I'm almost there now, thanks for you help so far.
SportyPorty said:
Cheers mindmajick. I've tried to do this but still having a few problems.
If I use the wired version, the runme.bat does not have permissions to the data/app folder. I can't seem to run it in Kubuntu as it says I can't run a binary file if I make it executable, but says I don't have permission if I remove execute. (I'm looking into this - but I'm not very good with Linux, so lots of Googling!!...lol....) Also I see that there are some issues with this version with the wireless version being favored. Unfortunately as I'm unable to log onto my Amazon account, I can't use this method.
I will continue to try, I'm almost there now, thanks for you help so far.
Click to expand...
Click to collapse
Really confused. Pm me with your gmail account and I'll chat you through it
--
Sent from my mind to your screen.
Cheers, PM'd you.
Sorry if I've not explained it very well.
I tried to use the KF2CM10.zip via the Desktop method. I downloaded and ran the runme.bat file. This is what I get -
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
C:\Users\Steve\Desktop\Kindle Fire Root\KF2CM10>ECHO off
Press any key to continue . . .
.
Removing install-recovery.sh to ensure that stock rom does not overwrite TWRP
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Usage: mount [-r] [-w] [-o options] [-t type] device directory
rm failed for systemetcinstall-recovery.sh, No such file or directory
rm failed for systemRECOVERY-AMZN-4430-OTTER2-PROD, No such file or directory
.
Pushing stack
failed to copy 'stuff\stack' to '\sdcard\': Read-only file system
sdcardstack: cannot open for read: No such file or directory
.
Inserting stack override to \system
datalocaltmpstack: cannot open for read: No such file or directory
.
Pushing freedom-boot
failed to copy 'stuff\boot.img' to '\sdcard\': Read-only file system
.
Pushing TeamWinRecoveryProject
failed to copy 'stuff\recovery.img' to '\sdcard\': Read-only file system
.
Writing freedom-boot to \boot via dd
sdcardboot.img: cannot open for read: No such file or directory
.
Writing TWRP to recovery via dd
sdcardrecovery.img: cannot open for read: No such file or directory
.
Rebooting
.
Make sure to press the power button during the secondary bootloader to reboot in
to recovery.
.
Give credit where credit is due: Script written by [email protected]
Press any key to continue . . .
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I'm still unsure how to run the runme.sh from Kubuntu command line.
I tried - ./runme.sh
but error is - unable to run a binary file - or something like that.
I'm unable to use the cordless version com.powerpoint45.FMKilo-2.apk due to the fact that as the KF2 is blocked by Amazon, I'm unable to log in and download or install .apk files.
Is there is an alternative way to install .apk files without needing to log in?
Hopefully that makes a little more sense. Cheers
Yes. Download the fmkilo apk from his thread, (use the browser if you have to) then once downloaded pull down the notification bar and tap on the apk link. Also, make sure that the option to install from unknown sources is set in the settings before doing the download
You could alternatively push the file via adb to the system Directory.
Is USB debugging enabled? Are you rooted?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Yes. Download the fmkilo apk from his thread, (use the browser if you have to) then once downloaded pull down the notification bar and tap on the apk link. Also, make sure that the option to install from unknown sources is set in the settings before doing the download
Click to expand...
Click to collapse
Yup, that did it. I had overlooked the fact that I was still able to use the browser on the KF2 and didn't really know you could install .apk's using that method anyway. So now I have carried on and installed Jellybean 4.2.2 on there and it works a treat.
Thank you ever so much Mindmajick for taking an interest in my problem, I really do appreciate yours and the rest of the developers time on here. :good:
Cheers
Sporty
fmkilo apk link shows as removed
mindmajick said:
Yes. Download the fmkilo apk from his thread, (use the browser if you have to) then once downloaded pull down the notification bar and tap on the apk link. Also, make sure that the option to install from unknown sources is set in the settings before doing the download
You could alternatively push the file via adb to the system Directory.
Is USB debugging enabled? Are you rooted?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Went to link for fmkilo apk and, link shows link removed?
galearned said:
Went to link for fmkilo apk and, link shows link removed?
Click to expand...
Click to collapse
Correct. Tried to talk them out of removing but it was removed. Only removed so no one uses it stupidly...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
fmkilo apk removed from link
mindmajick said:
Correct. Tried to talk them out of removing but it was removed. Only removed so no one uses it stupidly...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Not a problem: Thanks
I think this is a method of pushing the flash and image files to the tablet and then installing using ADB by the way it is described.
I think I have that method copied down some place else.
I have never used this method but, sounds like it would work.
I also presume you need root to do the install via ADB.
Regards Jerry
I have used all drivers and two different tot files, and it works to reboot, then it fails when I try to get past the first welcome screen... Does it make a difference if the sim card is in or out???
It makes it to preactivation and set phone name, then a second or two later goes back into the reboot stage.
I made it to the settings screen and phone info, and all areas were UNKNOWN
pitbull8265 said:
I have used all drivers and two different tot files, and it works to reboot, then it fails when I try to get past the first welcome screen... Does it make a difference if the sim card is in or out???
It makes it to preactivation and set phone name, then a second or two later goes back into the reboot stage.
I made it to the settings screen and phone info, and all areas were UNKNOWN
Click to expand...
Click to collapse
I don't know what went wrong but since you don't have a reply I'll say this... I would start from scratch. Download the tot file AND dll again to a new place on your PC (like desktop). Run LG flash tool again and browse to those 2 files (flash tools likes to remember previous settings). Flash again and let us know the result. Sim card doesn't make a difference.
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware if you need it, always flashed reliably for me.
...
scottdanpor said:
I don't know what went wrong but since you don't have a reply I'll say this... I would start from scratch. Download the tot file AND dll again to a new place on your PC (like desktop). Run LG flash tool again and browse to those 2 files (flash tools likes to remember previous settings). Flash again and let us know the result. Sim card doesn't make a difference.
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware if you need it, always flashed reliably for me.
Click to expand...
Click to collapse
Ive done this.. no luck
pitbull8265 said:
Ive done this.. no luck
Click to expand...
Click to collapse
Did you get anywhere with this? Under status, is your IMEI listed as unknown? This seems like your efs partition might be messed up. Did you make a backup of it?
scottdanpor said:
Did you get anywhere with this? Under status, is your IMEI listed as unknown? This seems like your efs partition might be messed up. Did you make a backup of it?
Click to expand...
Click to collapse
I just read elsewhere that if you used ioroot you may have a backup anyways. On the computer in ioroot. You may find a couple files called, modem st1, and modem st2.
Hopefully they will speak of it. Watch this thread..,.
http://forum.xda-developers.com/showthread.php?p=51932057
@scottdanpor for the info and hopefully how to use it.
pitbull8265 said:
Ive done this.. no luck
Click to expand...
Click to collapse
Sent from my Nexus 7 using Tapatalk
secret.animal said:
I just read elsewhere that if you used ioroot you may have a backup anyways. On the computer in ioroot. You may find a couple files called, modem st1, and modem st2.
Hopefully they will speak of it. Watch this thread..,.
http://forum.xda-developers.com/showthread.php?p=51932057
@scottdanpor for the info and hopefully how to use it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yeah but he has basically access to download mode and fastboot it seems. I haven't found a way to push files without at least recovery
Well, if he has access to stock recovery should be able to push files that way through ADB
NOPE
scottdanpor said:
Yeah but he has basically access to download mode and fastboot it seems. I haven't found a way to push files without at least recovery
Well, if he has access to stock recovery should be able to push files that way through ADB
Click to expand...
Click to collapse
it just hangs and reboots still... cant access fastboot.. tried every file available nothing is working
rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr
scottdanpor said:
Yeah but he has basically access to download mode and fastboot it seems. I haven't found a way to push files without at least recovery
Well, if he has access to stock recovery should be able to push files that way through ADB
Click to expand...
Click to collapse
I have a recovery I made using twrp saved to my pc, and I chose the option to backup my efs, so all of my info is on my pc in the backup file.
HOW can I use adb sideload or ADB to push it to my phone???
HAS TO BE DONE FROM STOCK RECOVERY ADB, as i cant even get into the ui long enough to activate usb debugging
pitbull8265 said:
I have a recovery I made using twrp saved to my pc, and I chose the option to backup my efs, so all of my info is on my pc in the backup file.
HOW can I use adb sideload or ADB to push it to my phone???
HAS TO BE DONE FROM STOCK RECOVERY ADB, as i cant even get into the ui long enough to activate usb debugging
Click to expand...
Click to collapse
It will take a bit of reading but you will learn a lot!
Here's a guide with some commands, you just need to tailor it to your needs/paths, it says Samsung but all you need are the commands.
http://forum.xda-developers.com/showthread.php?t=2141817
If you have ioroot on your computer you have ADB. Plug in your phone in recovery mode and check device manager. It's probably under "unknown" as LG-LS980. You need to right-click and select "update driver", then manually select driver. From the list, you should be able to find something like Android composite ADB device. Select that one and it should then be recognized as ADB.
Hold Shift and right click on the ioroot folder and select "Open command window here", then in cmd type "adb devices". If all is good you will get a serial number as it detects your device. Once you got this you are ready to enter commands, check that guide for the right command to push the file to: /dev/block/platform/msm_sdcc.1/by-name/
as stated by Autoprime here: http://forum.xda-developers.com/showthread.php?t=2451390
I hope that's enough info to get you going. You should type "adb shell" first in ADB so you have access to root.
---------- Post added at 09:12 AM ---------- Previous post was at 09:03 AM ----------
Oh crap... I just re-read that. I don't think this will work if your backup is from TWRP. That needs to be restored from TWRP. Do you not have a backup from ioroot? That contains the img files you need.
---------- Post added at 09:18 AM ---------- Previous post was at 09:12 AM ----------
Ok, I found this...
"Even though all TWRP backup files carry the extension .win, they are either tar archives or filesystem images. System, data, cache and .android_secure are backed up as tar archives or gnu-zipped tar archives if compression is enabled. You can rename those .win files to .tar (.tar.gz if compressed) and extract them like a regular archive. Boot and recovery partitions are backed up as .img files using dd"
from: http://forum.xda-developers.com/showthread.php?t=1694617
I couldn't find out if TWRP backs up EFS to .tar or .img. Once you figure that out you should be able to rename them to modemst1.img and modemst1.img. I just verified on mine that the files are the same size, so I would guess they are actually img files and not compressed. They should be 3MB in size.
There's a lot more info in that thread by Autoprime that should help.
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.