Cloning Pre-configured Android 8.1 Device / ROM - Android Software/Hacking General [Developers Only]
Hey guys,
Not sure if this is the correct place to post, but I am at my wits end and think I need a bit of help. I have been cloning devices on Android 7.1 without too much trouble, but something has changed in Android 8.1 which breaks things. Here is my setup:
Device: Xiaomi Redmi Note 4X 16GB, unlocked bootloader
OS: LineageOS 15.1 (Android 8.1)
My setup process is as follows:
Let stock ROM update (for latest firmware), unlock BL, flash TWRP, clean wipe, flash LineageOS + Gapps + Magisk
Skip through setup wizard, apply customisations (apps via APKs, launcher, settings, etc)
Clear Data for following:
com.google.android.gms.setup
Google App
Google Account Manager
Google Backup Transport
Google One Time Init
Google Partner Setup
Google Play Services
Google Play Services for Instant Apps
Google Play Store
Google Services framework
Reboot to TWRP
Connect to PC, run following ADB command: adb pull /data/system/users/0/settings_secure.xml
Open settings_secure.xml and delete "android_id" line
Push settings_secure.xml back to device: adb push settings_secure.xml /data/system/users/0/
Capture system image, flash onto other devices (either via TWRP backup or pushing system images via ADB)
Boot device, log into client Google account, done
Now this process used to work great on LineageOS 14.1 (Android 7.1), but now I get the following issues:
When adding a Google Account, it does not appear in Android device manager, but it appears in the list of devices in the Google Play Store? If I remove the account and then add it again it appears, but the issues below still occur.
Google's messaging / push system is broken. If I send a Hangouts message to my Google account, it won't appear until I open the app.
Any pre-installed apps won't appear in the "installed" list of apps in the play store, and therefore not update automatically until the user manually searches for the app in the Play Store and hits "update" (ugh).
I need to be deploying around 100 units over the next couple of months or so I need something that is scalable. I might be going around this the wrong way completely. I am not a ROM developer or programmer, just found something that has worked well in the past, so if I need to develop a ROM from scratch based on LineageOS I'll probably need to hire someone to do this for me as this is a bit beyond my current capabilities and time constraints. Let me know your thoughts! Thanks.
Android ID is same for many devices if you clone. That is really bad and can cause issues.
Rayman96 said:
Android ID is same for many devices if you clone. That is really bad and can cause issues.
Click to expand...
Click to collapse
I am deleting the Android ID from settings_secure.xml though. Unless it is somewhere else as well?
I'm still struggling with this problem. Is there anything else I can try? I googled this problem and the first result is this thread :/
stephendt0 said:
I'm still struggling with this problem. Is there anything else I can try? I googled this problem and the first result is this thread :/
Click to expand...
Click to collapse
Code:
adb shell settings delete secure android_id
adb shell settings delete secure advertising_id
adb shell settings delete secure bluetooth_address
adb shell settings put secure bluetooth_name 'YOURNAME'
adb shell settings put global device_name 'YOURNAME'
adb shell settings put global wifi_p2p_device_name 'YOURNAME'
The two IDs are then randomly regenerated. YOURNAME is any name of your choice.
rainman74 said:
Code:
adb shell settings delete secure android_id
adb shell settings delete secure advertising_id
adb shell settings delete secure bluetooth_address
adb shell settings put secure bluetooth_name 'YOURNAME'
adb shell settings put global device_name 'YOURNAME'
adb shell settings put global wifi_p2p_device_name 'YOURNAME'
The two IDs are then randomly regenerated. YOURNAME is any name of your choice.
Click to expand...
Click to collapse
Thanks for that. I believe I actually found their respective strings in settings_secure.xml:
<setting id="59" name="config_update_certificate"
<setting id="43" name="bluetooth_address"
And of course the Android ID. Once I deleted these, they auto-generated on the next boot, so I do this using ADB in TWRP.
I tried this and so far I'm not having any problems! Will report back if I experience any issues.
Another update - turn out that this is NOT enough. You will also want to clear data for the following apps (ideally just before shutting down the system and clearing android, bluetooth and config_update_certificate) to ensure that push notifications continue to work:
Com.google.android.gms.setup
Google App (not 100% sure if this is required, but I do it anyway)
Google Play Services
Google Play Store
Google Services framework
Reboot, clear your IDs, and then take your image. It should be OK after that, I think. I generally like to setup Hangouts on the device and then reboot, and let it sit for 5 minutes so its fully dozed before I send a test message.
Edit: STILL not working even after all this. Anyone else able to offer an explanation as to why push notifications is such an issue? This is becoming really difficult
stephendt0 said:
Another update - turn out that this is NOT enough. You will also want to clear data for the following apps (ideally just before shutting down the system and clearing android, bluetooth and config_update_certificate) to ensure that push notifications continue to work:
Com.google.android.gms.setup
Google App (not 100% sure if this is required, but I do it anyway)
Google Play Services
Google Play Store
Google Services framework
Reboot, clear your IDs, and then take your image. It should be OK after that, I think. I generally like to setup Hangouts on the device and then reboot, and let it sit for 5 minutes so its fully dozed before I send a test message.
Edit: STILL not working even after all this. Anyone else able to offer an explanation as to why push notifications is such an issue? This is becoming really difficult
Click to expand...
Click to collapse
ok, if you want to reset everything in a clone, proceed as follows:
Code:
adb shell su -c mount -o remount,rw /system
adb shell su -c rm /data/system/users/0/accounts.db
adb shell su -c rm /data/system/users/0/accounts.db-journal
adb shell su -c rm /data/system/users/0/photo.png
adb shell su -c rm /data/system/sync/accounts.xml
adb shell su -c rm /data/system/sync/pending.xml
adb shell su -c rm /data/system/sync/stats.bin
adb shell su -c rm /data/system/sync/status.bin
adb shell su -c pm clear com.android.packageinstaller
adb shell su -c pm clear com.android.providers.downloads
adb shell su -c pm clear com.android.vending
adb shell su -c pm clear com.google.android.backuptransport
adb shell su -c pm clear com.google.android.gms
adb shell su -c pm clear com.google.android.gsf
adb shell su -c mount -o remount,ro /system
Please also follow my instructions above for resetting the IDs before rebooting.
Google then recognizes a new device! Have fun :fingers-crossed:
rainman74 said:
ok, if you want to reset everything in a clone, proceed as follows:
Code:
adb shell su -c mount -o remount,rw /system
adb shell su -c rm /data/system/users/0/accounts.db
adb shell su -c rm /data/system/users/0/accounts.db-journal
adb shell su -c rm /data/system/users/0/photo.png
adb shell su -c rm /data/system/sync/accounts.xml
adb shell su -c rm /data/system/sync/pending.xml
adb shell su -c rm /data/system/sync/stats.bin
adb shell su -c rm /data/system/sync/status.bin
adb shell su -c pm clear com.android.packageinstaller
adb shell su -c pm clear com.android.providers.downloads
adb shell su -c pm clear com.android.vending
adb shell su -c pm clear com.google.android.backuptransport
adb shell su -c pm clear com.google.android.gms
adb shell su -c pm clear com.google.android.gsf
adb shell su -c mount -o remount,ro /system
Please also follow my instructions above for resetting the IDs before rebooting.
Google then recognizes a new device! Have fun :fingers-crossed:
Click to expand...
Click to collapse
OMG, I think that worked, thank you! I spent 5 hrs and stayed up to 3am trying to work this out with no luck, and this did the trick. To make things easier however, I morphed these commands into a dirty "one-liner" that saves entering each command.
Code:
adb shell settings delete secure android_id && adb shell settings delete secure advertising_id && adb shell settings delete secure bluetooth_address && adb shell settings put secure bluetooth_name 'Redmi Note 4' && adb shell settings put global device_name 'Redmi Note 4' && adb shell settings put global wifi_p2p_device_name 'Redmi Note 4' && adb shell su -c mount -o remount,rw /system && adb shell su -c rm /data/system/users/0/accounts.db && adb shell su -c rm /data/system/users/0/accounts.db-journal && adb shell su -c rm /data/system/users/0/photo.png && adb shell su -c rm /data/system/sync/accounts.xml && adb shell su -c rm /data/system/sync/pending.xml && adb shell su -c rm /data/system/sync/stats.bin && adb shell su -c rm /data/system/sync/status.bin && adb shell su -c pm clear com.android.packageinstaller && adb shell su -c pm clear com.android.providers.downloads && adb shell su -c pm clear com.android.vending && adb shell su -c pm clear com.google.android.backuptransport && adb shell su -c pm clear com.google.android.gms && adb shell su -c pm clear com.google.android.gsf && adb shell su -c mount -o remount,ro /system
I'm sure there is a more efficient way of stacking commands, but this worked. Replace "Redmi Note 4" with your actual device and reboot. I cleared data for any messaging apps and removed my Google account before I began, however.
stephendt0 said:
OMG, I think that worked, thank you! I spent 5 hrs and stayed up to 3am trying to work this out with no luck, and this did the trick. To make things easier however, I morphed these commands into a dirty "one-liner" that saves entering each command.
I'm sure there is a more efficient way of stacking commands, but this worked. Replace "Redmi Note 4" with your actual device and reboot. I cleared data for any messaging apps and removed my Google account before I began, however.
Click to expand...
Click to collapse
Perfect! You don't need to remove your Google account as the commands do this anyway
rainman74 said:
Perfect! You don't need to remove your Google account as the commands do this anyway
Click to expand...
Click to collapse
Quick update.
After a bit more testing, turns out that there were still a few things that needed clearing, particularly on different versions of Android (7.1). Also, I've noticed that a GSF ID can be generated before you get a chance to capture an image if you leave Wi-Fi enabled, so I've included that in the script. I've ended up with a .BAT file with the following:
Code:
echo on
adb shell settings delete secure android_id
adb shell settings delete secure advertising_id
adb shell settings delete secure bluetooth_address
adb shell su -c mount -o remount,rw /system
adb shell su -c svc wifi disable
adb shell su -c rm /data/system/users/0/accounts.db
adb shell su -c rm /data/system/users/0/accounts.db-journal
adb shell su -c rm /data/system/users/0/photo.png
adb shell su -c rm /data/system/users/0/settings_ssaid.xml
adb shell su -c rm /data/system/sync/accounts.xml
adb shell su -c rm /data/system/sync/pending.xml
adb shell su -c rm /data/system/sync/stats.bin
adb shell su -c rm /data/system/sync/status.bin
adb shell su -c pm clear com.google.android.ext.services
adb shell su -c pm clear com.google.android.ext.shared
adb shell su -c pm clear com.google.android.gsf.login
adb shell su -c pm clear com.google.android.onetimeinitializer
adb shell su -c pm clear com.android.packageinstaller
adb shell su -c pm clear com.android.providers.downloads
adb shell su -c pm clear com.android.vending
adb shell su -c pm clear com.google.android.backuptransport
adb shell su -c pm clear com.google.android.gms
adb shell su -c pm clear com.google.android.instantapps.supervisor
adb shell su -c pm clear com.google.android.gsf
adb shell su -c mount -o remount,ro /system
I have found that this works consistently across both LineageOS 14.1 and LineageOS 15.1 devices.
stephendt0 said:
OMG, I think that worked, thank you! I spent 5 hrs and stayed up to 3am trying to work this out with no luck, and this did the trick. To make things easier however, I morphed these commands into a dirty "one-liner" that saves entering each command.
Code:
adb shell settings delete secure android_id && adb shell settings delete secure advertising_id && adb shell settings delete secure bluetooth_address && adb shell settings put secure bluetooth_name 'Redmi Note 4' && adb shell settings put global device_name 'Redmi Note 4' && adb shell settings put global wifi_p2p_device_name 'Redmi Note 4' && adb shell su -c mount -o remount,rw /system && adb shell su -c rm /data/system/users/0/accounts.db && adb shell su -c rm /data/system/users/0/accounts.db-journal && adb shell su -c rm /data/system/users/0/photo.png && adb shell su -c rm /data/system/sync/accounts.xml && adb shell su -c rm /data/system/sync/pending.xml && adb shell su -c rm /data/system/sync/stats.bin && adb shell su -c rm /data/system/sync/status.bin && adb shell su -c pm clear com.android.packageinstaller && adb shell su -c pm clear com.android.providers.downloads && adb shell su -c pm clear com.android.vending && adb shell su -c pm clear com.google.android.backuptransport && adb shell su -c pm clear com.google.android.gms && adb shell su -c pm clear com.google.android.gsf && adb shell su -c mount -o remount,ro /system
I'm sure there is a more efficient way of stacking commands, but this worked. Replace "Redmi Note 4" with your actual device and reboot. I cleared data for any messaging apps and removed my Google account before I began, however.
Click to expand...
Click to collapse
YES, this did it. I cloned a kindle fire hdx using TWRP backup&restore and had to perform the action mentioned above in order to use both devices independetly.
ATTENTION!
Remember to change the values listed in stephendt0's example that were not part of the original code from rainman74:
- device_name: Equals the device type. E.g. adb shell settings put global device_name 'KFHDX'
- bluetooth_name: Hostname of the device seen in bluetooth.
- wifi_p2p_device_name: Hostname used for a p2p wifi network aka "ad hoc network". Not supported on all devices.
Related
[Q] TPSparkyRoot - ICS (Root/UnRoot)
Hi sparkym3, I'm not able to reply your post "[ROOT] TPSparkyRoot - ICS' so I created a new post here. I had successfully rooted my Star N8000 phone using the below script with busybox, Superuser and RootExplorer installed. Root ==== echo off cls adb shell mv /data/local/tmp /data/local/tmp.bak adb shell ln -s /data /data/local/tmp adb reboot echo Rebooting (1/3) - Continue once device finishes rebooting pause adb shell rm /data/local.prop > nul adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop" adb reboot echo Rebooting (2/3) - Continue once device finishes rebooting pause adb shell id echo If the id is 0 / root then continue, otherwise ctrl+c to cancel and start over pause adb remount adb push su /system/bin/su adb shell chown 0.0 /system/bin/su adb shell chmod 06755 /system/bin/su adb push busybox /system/bin/busybox adb shell chown 0.0 /system/bin/busybox adb shell chmod 0755 /system/bin/busybox adb push Superuser.apk /system/app/Superuser.apk adb shell chown 0.0 /system/app/Superuser.apk adb shell chmod 0644 /system/app/Superuser.apk adb push RootExplorer.apk /system/app/RootExplorer.apk adb shell chown 0.0 /system/app/RootExplorer.apk adb shell chmod 0644 /system/app/RootExplorer.apk echo Removing changes except ROOT adb shell rm /data/local.prop adb shell rm /data/local/tmp adb shell mv /data/local/tmp.bak /data/local/tmp adb reboot echo Rebooting (3/3) - You should now be Rooted pause echo on ***My question is if I want to unroot my Star N8000 phone, I will need to remove the su, busybox, Superuser and RootExplorer from my phone system. So, the new script should as below. Please help to verify and let me know whether this is correct. Thanks in advance. UNRoot ====== echo off cls adb shell mv /data/local/tmp /data/local/tmp.bak adb shell ln -s /data /data/local/tmp adb reboot echo Rebooting (1/3) - Continue once device finishes rebooting pause adb shell rm /data/local.prop > nul adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop" adb reboot echo Rebooting (2/3) - Continue once device finishes rebooting pause adb shell id echo If the id is 0 / root then continue, otherwise ctrl+c to cancel and start over pause adb remount adb shell rm /system/xbin/su adb shell rm /system/xbin/busybox adb shell rm /system/xbin/Superuser.apk adb shell rm /system/xbin/RootExplorer.apk echo Removing changes except ROOT adb shell rm /data/local.prop adb shell rm /data/local/tmp adb shell mv /data/local/tmp.bak /data/local/tmp adb reboot echo Rebooting (3/3) - You should now be UNRooted pause echo on
rayxware said: Hi sparkym3, I'm not able to reply your post "[ROOT] TPSparkyRoot - ICS' so I created a new post here. I had successfully rooted my Star N8000 phone using the below script with busybox, Superuser and RootExplorer installed. Root ==== echo off cls adb shell mv /data/local/tmp /data/local/tmp.bak adb shell ln -s /data /data/local/tmp adb reboot echo Rebooting (1/3) - Continue once device finishes rebooting pause adb shell rm /data/local.prop > nul adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop" adb reboot echo Rebooting (2/3) - Continue once device finishes rebooting pause adb shell id echo If the id is 0 / root then continue, otherwise ctrl+c to cancel and start over pause adb remount adb push su /system/bin/su adb shell chown 0.0 /system/bin/su adb shell chmod 06755 /system/bin/su adb push busybox /system/bin/busybox adb shell chown 0.0 /system/bin/busybox adb shell chmod 0755 /system/bin/busybox adb push Superuser.apk /system/app/Superuser.apk adb shell chown 0.0 /system/app/Superuser.apk adb shell chmod 0644 /system/app/Superuser.apk adb push RootExplorer.apk /system/app/RootExplorer.apk adb shell chown 0.0 /system/app/RootExplorer.apk adb shell chmod 0644 /system/app/RootExplorer.apk echo Removing changes except ROOT adb shell rm /data/local.prop adb shell rm /data/local/tmp adb shell mv /data/local/tmp.bak /data/local/tmp adb reboot echo Rebooting (3/3) - You should now be Rooted pause echo on ***My question is if I want to unroot my Star N8000 phone, I will need to remove the su, busybox, Superuser and RootExplorer from my phone system. So, the new script should as below. Please help to verify and let me know whether this is correct. Thanks in advance. UNRoot ====== echo off cls adb shell mv /data/local/tmp /data/local/tmp.bak adb shell ln -s /data /data/local/tmp adb reboot echo Rebooting (1/3) - Continue once device finishes rebooting pause adb shell rm /data/local.prop > nul adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop" adb reboot echo Rebooting (2/3) - Continue once device finishes rebooting pause adb shell id echo If the id is 0 / root then continue, otherwise ctrl+c to cancel and start over pause adb remount adb shell rm /system/xbin/su adb shell rm /system/xbin/busybox adb shell rm /system/xbin/Superuser.apk adb shell rm /system/xbin/RootExplorer.apk echo Removing changes except ROOT adb shell rm /data/local.prop adb shell rm /data/local/tmp adb shell mv /data/local/tmp.bak /data/local/tmp adb reboot echo Rebooting (3/3) - You should now be UNRooted pause echo on Click to expand... Click to collapse This is doing way to much extra while unrooting. Since you would already have root by this point, you can just call su to do all the removes and then remove su last. This can be done from adb or any root file explorer like es file explorer (which will also allow you to mount the file system). Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
[ROOT] LG Intuition & LG Spectrum ICS
Source: http://www.androidpolice.com/2012/0...root-the-lg-intuition-and-lg-spectrum-on-ics/ If you find this useful please follow me (jcase) on twitter ( https://twitter.com/teamandirc/ ). Here you go, root for both the new LG Intuition and the LG Spectrum running ICS. The vulnerability is a simple permission bug allowing us to setup a symlink to local.prop (yes yet again). While the bug is the same, the procedure is slightly different, so I will have the instructions separate. With the LG Intuition, they did seem to attempt to mitigate this attack. Not by setting correct permissions, but by dropping adbD to the shell user if it runs as root, even if ro.kernel.qemu=1 is set. They failed, they give us enough time to run one command before dropping the root privileges, in our case a script to root the phone. LG Spectrum ICS Root (for the leaked ICS rom): Expect this to be patched in the release rom. Leaked ICS rom has locked bootlaoders, ie no recovery at this point. Files needed: su ( http://dl.dropbox.com/u/8699733/lgroot/su ) adb shell $ rm /data/vpnch/vpnc_starter_lock $ ln -s /data/local.prop /data/vpnch/vpnc_starter_lock $ exit adb reboot adb wait-for-device shell $ echo 'ro.kernel.qemu=1' > /data/local.prop $ exit adb reboot adb wait-for-device remount adb push su /system/xbin/su adb shell # chown 0.0 /system/xbin/su # chmod 06755 /system/xbin/su # rm /data/local.prop # rm /data/vpnch/vpnc_starter_lock # reboot Once rebooted, install Superuser from the market and enjoy. LG Intuition Root Files needed: su ( http://dl.dropbox.com/u/8699733/lgroot/su ) lgroot.sh ( http://dl.dropbox.com/u/8699733/lgroot/lgroot.sh ) adb push su /data/local/tmp/su adb push lgroot.sh /data/local/tmp/lgroot.sh adb shell $ chmod 777 /data/local/tmp/lgroot.sh $ rm /data/vpnch/vpnc_starter_lock $ ln -s /data/local.prop /data/vpnch/vpnc_starter_lock $ exit adb reboot You may have to unplug/replug your phone to get some computers to pick it up again after this reboot. adb wait-for-device shell $ echo 'ro.kernel.qemu=1' > /data/local.prop $ exit Here is the important part, you will have to execute the next to commands one after the other. We want the second command to be fired off as soon as adbD comes up, before it drops root privileges. This may take some a few minutes, and after the second command is complete you may have to unplug/replug you phone to get your computer to see it again. adb reboot adb wait-for-device /data/local/tmp/lgroot.sh (Here is where you may have to unplug/replug, but only after the second command has ran). adb wait-for-device shell $ su # rm /data/local.prop # rm /data/vpnch/vpnc_starter_lock # reboot Once rebooted, install Superuser from the market and enjoy.
Thanks! Dude, it has been killing me not having root since I managed to get the leaked ICS installed. But I tried this, and just wasn't having any luck. I tried to make a .bat file for it, no go. So i tried inputting it line by line and i keep getting hung up at the $ echo 'ro.kernel.qemu=1' part. Just wondering if anyone else is having this problem. Also, since yesterday whenever I check for a software update, I'm getting an "error occurred during download". I was wondering if I would even be able to get the final ICS OTA when it finally is available. Thanks again jcase!
LostCauseSPM said: Dude, it has been killing me not having root since I managed to get the leaked ICS installed. But I tried this, and just wasn't having any luck. I tried to make a .bat file for it, no go. So i tried inputting it line by line and i keep getting hung up at the $ echo 'ro.kernel.qemu=1' part. Just wondering if anyone else is having this problem. Also, since yesterday whenever I check for a software update, I'm getting an "error occurred during download". I was wondering if I would even be able to get the final ICS OTA when it finally is available. Thanks again jcase! Click to expand... Click to collapse Which specific ICS version do you have, I had a couple different leaks to work with.
jcase said: Which specific ICS version do you have, I had a couple different leaks to work with. Click to expand... Click to collapse build #: IMM76D Still tweeking on it. Just updated all my drivers, too. I'm not a total newb, but I'm no pro, either.
jcase said: Source: http://www.androidpolice.com/2012/0...root-the-lg-intuition-and-lg-spectrum-on-ics/ LG Intuition Root Files needed: su ( http://dl.dropbox.com/u/8699733/lgroot/su ) lgroot.sh ( http://dl.dropbox.com/u/8699733/lgroot/lgroot.sh ) adb push su /data/local/tmp/su adb push lgroot.sh /data/local/tmp/lgroot.sh adb shell $ chmod 777 /data/local/tmp/lgroot.sh $ rm /data/vpnch/vpnc_starter_lock $ ln -s /data/local.prop /data/vpnch/vpnc_starter_lock $ exit adb reboot You may have to unplug/replug your phone to get some computers to pick it up again after this reboot. adb wait-for-device shell $ echo ‘ro.kernel.qemu=1’ > /data/local.prop $ exit Here is the important part, you will have to execute the next to commands one after the other. We want the second command to be fired off as soon as adbD comes up, before it drops root privileges. This may take some a few minutes, and after the second command is complete you may have to unplug/replug you phone to get your computer to see it again. adb reboot adb wait-for-device /data/local/tmp/lgroot.sh (Here is where you may have to unplug/replug, but only after the second command has ran). adb wait-for-device shell $ su # rm /data/local.prop # rm /data/vpnch/vpnc_starter_lock # reboot :crying: Once rebooted, install Superuser from the market and enjoy. Click to expand... Click to collapse i tried but as soon as i entered adb shell it kick me off and haven't been able to try since
jcase said: Which specific ICS version do you have, I had a couple different leaks to work with. Click to expand... Click to collapse Ive got the spectrum, btw. Still trying to make a nice, clean, automated .bat, but it keeps failing now at the remount command. ---------- Post added at 07:37 PM ---------- Previous post was at 07:24 PM ---------- And now is saying "rm failed for /data/vpnch..." When the remount fails, I get a "remount failed: operation not permitted" message. Hope this is useful to you.
LostCauseSPM said: Ive got the spectrum, btw. Still trying to make a nice, clean, automated .bat, but it keeps failing now at the remount command. ---------- Post added at 07:37 PM ---------- Previous post was at 07:24 PM ---------- And now is saying "rm failed for /data/vpnch..." When the remount fails, I get a "remount failed: operation not permitted" message. Hope this is useful to you. Click to expand... Click to collapse add [email protected] to gltak and hit me up.
lahegry said: i tried but as soon as i entered adb shell it kick me off and haven't been able to try since Click to expand... Click to collapse unplug/replug, The intuition is very touchy. Might need to do it from another system or with another cable.
jcase said: unplug/replug, The intuition is very touchy. Might need to do it from another system or with another cable. Click to expand... Click to collapse i don't think i'm fast enough, i just can't type faster than it kicks me off
lahegry said: i don't think i'm fast enough, i just can't type faster than it kicks me off Click to expand... Click to collapse Place the two commands into a batch file/shell script, or setup teamviewer and msg me on gtalk
so this is just I've come up with tonight, the exploit still fails line by line, so I made a batch file just for that command, and I think I may be misunderstanding that "adb mount - o" command you recomended. Wow, this chrome is NOT liking this txt box, keeps jumping backwards for some reason. C'mon Google...
I've got the intuition and here is what I'm coming up with using cmd prompt in windows: C:\android-sdk\platform-tools>adb push su /data/local/tmp/su 2642 KB/s (380532 bytes in 0.140s) C:\android-sdk\platform-tools>adb push lgroot.sh /data/local/tmp/lgroot.sh 10 KB/s (164 bytes in 0.015s) C:\android-sdk\platform-tools>adb shell [email protected]:/ $ chmod 777 /data/local/tmp/lgroot.sh chmod 777 /data/local/tmp/lgroot.sh [email protected]:/ $ rm /data/vpnch/vpnc_starter_lock rm /data/vpnch/vpnc_starter_lock [email protected]:/ $ ln -s /data/local.prop /data/vpnch/vpnc_starter_lock ln -s /data/local.prop /data/vpnch/vpnc_starter_lock [email protected]:/ $ exit exit C:\android-sdk\platform-tools>adb reboot C:\android-sdk\platform-tools>adb wait-for-device shell [email protected]:/ $ echo `ro.kernel.qemu=1' > /data/local.prop echo `ro.kernel.qemu=1' > /data/local.prop > exit exit > adb reboot adb reboot > adb wait-for-device /data/local/tmp/lgroot.sh adb wait-for-device /data/local/tmp/lgroot.sh > adb wait-for-device shell adb wait-for-device shell > I believe I see where the mistake is, but don't know how to fix it. ---------- Post added 30th September 2012 at 12:02 AM ---------- Previous post was 29th September 2012 at 11:57 PM ---------- actually I don't see my mistake and I should be doing all this in PTP mode correct?
Try now, something was altering my post arnshrty said: I've got the intuition and here is what I'm coming up with using cmd prompt in windows: C:\android-sdk\platform-tools>adb push su /data/local/tmp/su 2642 KB/s (380532 bytes in 0.140s) C:\android-sdk\platform-tools>adb push lgroot.sh /data/local/tmp/lgroot.sh 10 KB/s (164 bytes in 0.015s) C:\android-sdk\platform-tools>adb shell [email protected]:/ $ chmod 777 /data/local/tmp/lgroot.sh chmod 777 /data/local/tmp/lgroot.sh [email protected]:/ $ rm /data/vpnch/vpnc_starter_lock rm /data/vpnch/vpnc_starter_lock [email protected]:/ $ ln -s /data/local.prop /data/vpnch/vpnc_starter_lock ln -s /data/local.prop /data/vpnch/vpnc_starter_lock [email protected]:/ $ exit exit C:\android-sdk\platform-tools>adb reboot C:\android-sdk\platform-tools>adb wait-for-device shell [email protected]:/ $ echo `ro.kernel.qemu=1' > /data/local.prop echo `ro.kernel.qemu=1' > /data/local.prop > exit exit > adb reboot adb reboot > adb wait-for-device /data/local/tmp/lgroot.sh adb wait-for-device /data/local/tmp/lgroot.sh > adb wait-for-device shell adb wait-for-device shell > I believe I see where the mistake is, but don't know how to fix it. ---------- Post added 30th September 2012 at 12:02 AM ---------- Previous post was 29th September 2012 at 11:57 PM ---------- actually I don't see my mistake and I should be doing all this in PTP mode correct? Click to expand... Click to collapse
Correction needed for Intuition First of all, thank you!!! For Intuition, where the 'important part' is, the second command returns an error. I was able to succeed by running adb reboot adb wait-for-device shell then wait for the # to appear, and quickly paste and execute: /data/local/tmp/lgroot.sh took a few tries, but I am rooted! :laugh:
krapman said: First of all, thank you!!! For Intuition, where the 'important part' is, the second command returns an error. I was able to succeed by running adb reboot adb wait-for-device shell then wait for the # to appear, and quickly paste and execute: /data/local/tmp/lgroot.sh took a few tries, but I am rooted! :laugh: Click to expand... Click to collapse Just wondering how you guys like this device? I was just debating on switching to verizon and this device stands out as the most interesting to me... so I had to look here to see if anybody rooted it. Anybody try any different roms? or think there may be a Jelly Bean update for it?
/system/bin/sh su not found any help with this was having an issue with the echo command but got past that but now it's giving me this error
davieslacker said: Just wondering how you guys like this device? I was just debating on switching to verizon and this device stands out as the most interesting to me... so I had to look here to see if anybody rooted it. Anybody try any different roms? or think there may be a Jelly Bean update for it? Click to expand... Click to collapse It's an amazing device I love it and im rooted. used the steps above and it worked. I am sure it will get jelly bean love eventually. No roms yet. But LG added a lot of customization to the device form what developers usually add as mods.
Will there be a single click method for root on the intuition. I can't seem to get this method to work
Exploit still works on the final version of ICS for the LG Spectrum Just updated my phone. Couldn't wait for the OTA rollout, updated via the Verizon Wireless Update Util on my comp. Root worked no problem. Thanks again Jcase!
What did you update your phone to? Sent from my VS950 4G using xda app-developers app
[Q]How to access android FS form fastoot/flashmode
I have copyied a damaged file in /system/app folder and now my phone is in the Bootloop. I wanna acces that file and replace it with the original. Can I do that?
I managed to solve it by deleting the 2 damaged files with this piece of code Code: echo " " echo "Waiting for device..." adb wait-for-device echo " " adb -d shell su -c "mount -o rw,remount /system" adb -d shell su -c "ls /system" adb -d shell su -c "rm /system/app/AudioEffectService.apk" adb -d shell su -c "rm /system/app/SoundEnhancement.apk" (of course the boot-loop forced me to find the right moment in the boot sequence to run the script)
[Completed] [Q] Batch file commands help
So I am trying to make a batch file that automatically flashes a custom bootanimation from my computer and I am having trouble with these commands. adb wait-for-device shell "su -c 'ls /system/media'" adb wait-for-device shell "su -c 'mount -o rw,remount -t yaffs2 /dev/block/mtdblock1 /system'" adb wait-for-device shell "su -c 'rm /data/media/bootanimation.zip1'" Bascially I want to have the adb shell enter superuser mode, remount system in read write mode and delete the existing bootanimation.zip Whenever I try and run this it says permission denied.
Please post your question in Android General so that the right experts may be of help. Thread Closed. Thank you.
Disable system packages [ADB - Android 13]
Hi... I made the very bad mistake of updating my Oppo Reno 6 5G to ColorOS 13... There is no possibility to downgrade and moreover some packages can no longer be uninstalled or disabled via ADB. For example, if I wanted to uninstall/disable com.oplus.ota to avoid further updates, the ADB commands that worked until yesterday would no longer work... Es: shell pm uninstall --user 0 com.oplus.ota Failure [DELETE_FAILED_INTERNAL_ERROR] shell pm disable-user --user 0 com.oplus.ota Package com.oplus.ota new state: default shell pm disable com.oplus.ota [Error]:failed to disable com.oplus.ota Anyone has a solution? Thanks....
Is the mentioned file listed as package? Code: adb devices adb shell "pm list packages -s" If not then you can't use pm cmd to operate on this file.
jwoegerbauer said: Is the mentioned file listed as package? Code: adb devices adb shell "pm list packages -s" If not then you can't use pm cmd to operate on this file. Click to expand... Click to collapse Yes the package is in the list! However both the disable and the uninstall give the error...
If one wants to get completely rid off of a system-package he/she 1. must make /sstem partition RW - what requires Android is got rooted Code: su -c "mount -o rw,remount /system" 2. simply runs Code: su -c "rm -f /system/<package-name>"
jwoegerbauer said: If one wants to get completely rid off of a system-package he/she 1. must make /sstem partition RW - what requires Android is got rooted Code: su -c "mount -o rw,remount /system" 2. simply runs Code: su -c "rm -f /system/<package-name>" Click to expand... Click to collapse Thank you for the info... My phone is not routed unfortunately... I want to downgrade it but i can't... :-(
jwoegerbauer said: If one wants to get completely rid off of a system-package he/she 1. must make /sstem partition RW - what requires Android is got rooted Code: su -c "mount -o rw,remount /system" 2. simply runs Code: su -c "rm -f /system/<package-name>" Click to expand... Click to collapse hallo, i've been using this method from a2.3 to a11 to uninstall system apps, but this method is not useable with a11 in a TWRP shell, so i'm curious, are these steps still works correctly in a13? in a system shell or TWRP shell?
The code excerpt printed above is meant to be run via ADB as Code: adb shell 'su -c "mount -o rw,remount -t auto /system"'