I made a mistake like https://forum.xda-developers.com/t/...a-sideload-zip-or-openrecoveryscript.3673284/
Edit: Original title
Would someones send me copies of "settings_global.xml" & "settings_secure.xml" in /data/system/users/0
What I have tried:
1; 2 xml files from #4 of this thread were replaced (not official), uselessly.
2; It looks like no dpi or resolution parameters in build.prop. If you know, please tell me the details.
3; I have done sideload official ota.zip and flashed factory.zip but kept data. NOT WORKS.
Questions:
1; As I haven't turn on USB debugging, I can't use some ADB commands or GUI ADB tools, so how can I turn on it?
2; Or some ways like I can flash a zip file in custom recovery?
3; I find there are many differences between Android in Pixel series and other brands' manufactures, so maybe a slove is effective on the others, but ineffective on Pixel phone.
Anyway, to edit some files without ADB authority or flash some modified zip are better ways for me.
please!
Or tell me where are these two files in offical ota .zip
Or a second way to solves this issue better, like flashing some zip package anyway
thank you!
OR，please tell me what code of "display_size_forced" in settings_global.xml, just as numbers in yellow box.
Xml file is opened by Notepad++，I understand a little about ASCII like NUL/ETX/STX,maybe I could edit it by myself.
CDShue said:
OR，please tell me what code of "display_size_forced" in settings_global.xml, just as numbers in yellow box.
Xml file is opened by Notepad++，I understand a little about ASCII like NUL/ETX/STX,maybe I could edit it by myself.
View attachment 5731893
Click to expand...
Click to collapse
Attached. Don't know if it makes a difference, but this is from LineageOS.
dcarvil said:
Attached. Don't know if it makes a difference, but this is from LineageOS.
Click to expand...
Click to collapse
Although I find the files you post are different from mine (especially the 'codes'), I replace these two files. Sadly It does not work. Many thx, anyway.
Why not simply sideload the OTA, or dirty flash the factory image?
CDShue said:
Xml file is opened by Notepad++
Click to expand...
Click to collapse
That's no XML file. It looks to be an SQLite database.
Settings in Android have been in an SQLite DB or in XML files in different Android versions.
V0latyle said:
V0latyle said:
Why not simply sideload the OTA, or dirty flash the factory image?
Click to expand...
Click to collapse
Maybe I have turned off USB debugging on my phone, then I followed this site https://stackoverflow.com/questions...evice-unauthorized-in-android-adb-host-device and got temporary adb authority. Sideload in TWRP failed.
Click to expand...
Click to collapse
Dirty flash the factory image did't work neither, if you mean the steps below:
Delete '-w' in 'flash-all.bat', save it, then open it.
V0latyle said:
Why not simply sideload the OTA, or dirty flash the factory image
Renate said:
That's no XML file. It looks to be an SQLite database.
Settings in Android have been in an SQLite DB or in XML files in different Android versions.
Click to expand...
Click to collapse
Thanks for your correction.
Click to expand...
Click to collapse
Renate said:
That's no XML file. It looks to be an SQLite database.
Settings in Android have been in an SQLite DB or in XML files in different Android versions.
Click to expand...
Click to collapse
Thanks for your correction.
Taps visual feedback, SO BIG!
( I photoshoped my fingers, )
If there's no other way to solve it, I'm considering to backup /data in TWRP, but there is no free space.
How to backup the whole /data to PC directly?
Related
After going through many of the different lock ring tutorials, I have noticed that they all have something in common: They are too user intensive and prone to user-error. Sure, once you have it down, it's easy. But it can be daunting to start out.
All I have done here is make it EXTREMELY user friendly.
No more copying and pasting into ZIPs and APKs!!
No more fishing around the Templates tree in M10 Tools!!!
Simply run the BATCH file, get a cup of coffee, and then flash!
Here are the detailed instructions... (also in the Read-Me)
0. Make sure you have installed Microsoft .net 4 framework on your machine.
http://www.microsoft.com/net
1. Unpack User_Friendly_Lock_Screen_Kit_v1.04.zip (Where you put the file does not matter anymore!!!! For example purposes, I will use C:\Lock_Ring_Kit)
2. Copy your image into C:\Lock_Ring_Kit and name it LockRing.png
Image requirements:
a. Must be a PNG file
b. Image must be 271 x 270 pixels (If it is not the right size, it will come out looking funny (270x271 WILL NOT WORK)
c. The image must be rotated 180 degrees and reflected horizontally.
3. Double-click "LockRingCreator.bat" and let it do its thing.
4. Flashable.zip was just created for you. Rename it whatever you wish.
5. Copy it to the root of your SD card, boot into recovery, and flash
The BATCH file cleans up after itself. You don't have to go through and delete any of the old files. If you want to make another one, just change out the PNG and run it again. My desktop is pretty old, and the BATCH takes about 2 minutes to run.
I have only tested this on Synergy, but I assume that it will work on similar ROMs. I also believe that it will work on the Thunderbolt (can someone confirm that?)
All files are included in the ZIP.
User_Friendly_Lock_Ring_Kit_v1.05.zip
Error Reporting
This is a work in progress. If you have an issue, please post it on the thread. Also, please copy and paste the output from the command prompt so we can get to the bottom of it. (Right click on command prompt, Select All, the then press ENTER. It is now ready to paste.)
Acknowledgments:
jmaher1023 - I used his process as a template. All that my BATCH file does is automate his process
Flemmard and DiamondBack2010- I have no idea what M10 Tools does or how much trouble they had to go through to make it, but I do know that it is the heart and soul of this whole operation.
Confirmed ROMS
Gingeritis3d
Synergy RLS 1
InCompatible ROMS
Kinged Shooter RLS 2.3
I'll try this out, thanks alot dude.
One thing you didn't mention is that the images still need to be 271 X 270 or they won't look right. Other than that this works on Gingeritis3d. (And if I want to say I was the one to create the lock ring I might edit the script) lol. Very good work though man. Very useful tool. Have you been able to find where the images are located for the Amazing sense skin? I haven't found those yet and want to use that semi transparent tool bar at the bottom but dont want to use a different launcher
somehow i cant get it to work ive followed every step but when i run the
"LockRingCreator.bat" it just goes into cmd really fast and nothing happens
TDubKong said:
One thing you didn't mention is that the images still need to be 270 X 270 or they won't look right.
Click to expand...
Click to collapse
Fixed in OP. I put that in the ReadMe, but forgot it on the thread Thanks for the reminder.
TDubKong said:
Other than that this works on Gingeritis3d.
Click to expand...
Click to collapse
Thanks for letting me know. I'll add a lit of confirmed ROMS that this works for.
TDubKong said:
(And if I want to say I was the one to create the lock ring I might edit the script) lol.
Click to expand...
Click to collapse
Navigate to C:\Lock_Ring_KitTemplate\META-INF\com\google\android
There is a file named "updater-script" Rename it updater-script.txt, and open it for editing. Just look for my name and replace it with yours. Make sure you take the .txt off after saving
TDubKong said:
Have you been able to find where the images are located for the Amazing sense skin? I haven't found those yet and want to use that semi transparent tool bar at the bottom but dont want to use a different launcher
Click to expand...
Click to collapse
No Idea
IDRFT95S14 said:
somehow i cant get it to work ive followed every step but when i run the
"LockRingCreator.bat" it just goes into cmd really fast and nothing happens
Click to expand...
Click to collapse
What operating system are you running? Do you have Microsoft .net 4 framework installed on your system?
When it is working properly, after you run the BATCH file you should see a command window running various commands for a little while.
did you
IDRFT95S14 said:
somehow i cant get it to work ive followed every step but when i run the
"LockRingCreator.bat" it just goes into cmd really fast and nothing happens
Click to expand...
Click to collapse
did you make sure the file was named LockRing and was a png format? Something else to consider is that if you named a png image lockring.png then when it looks for the file it will see lockring.png.png so make sure it is a png format image but only name it LockRing.Hope this helps
gamendorf said:
Fixed in OP. I put that in the ReadMe, but forgot it on the thread Thanks for the reminder.
Thanks for letting me know. I'll add a lit of confirmed ROMS that this works for.
Navigate to C:\Lock_Ring_KitTemplate\META-INF\com\google\android
There is a file named "updater-script" Rename it updater-script.txt, and open it for editing. Just look for my name and replace it with yours. Make sure you take the .txt off after saving
No Idea
Click to expand...
Click to collapse
Thanks brudda. I was only kidding about renaming the script. I knew where to find it. I can run a couple other ROMS if you want. I got nothing better to do tonight. Let me know which ones you want to add to your list and i'll do a couple.
just downloaded will test in a minute on mik3d beta1, but in the read me file, no sizes for pic you intend to use (just a heads up).
Forgot to mention I am running Gingeritis 3D Beta VIII. And I do have .net 4 installed. Maybe thats why i didn't have any issues. Also I didn't even read the read me file. oops.
life_420 said:
just downloaded will test in a minute on mik3d beta1, but in the read me file, no sizes for pic you intend to use (just a heads up).
Click to expand...
Click to collapse
You're right. Oops. Zip file has been updated
life_420 said:
just downloaded will test in a minute on mik3d beta1, but in the read me file, no sizes for pic you intend to use (just a heads up).
Click to expand...
Click to collapse
Love my DropBox. Tried a few other apps like Minus and another but they are just not so user friendly and helpful. Although a couple have more GB.
gamendorf said:
What operating system are you running? Do you have Microsoft .net 4 framework installed on your system?
When it is working properly, after you run the BATCH file you should see a command window running various commands for a little while.
Click to expand...
Click to collapse
windows 7 i looked it up and it does have the Microsoft .net 4 framework intalled ,im thinking i just didnt name something right ill try what TDubKong suggested VVV and ill get back
TDubKong said:
did you make sure the file was named LockRing and was a png format? Something else to consider is that if you named a png image lockring.png then when it looks for the file it will see lockring.png.png so make sure it is a png format image but only name it LockRing.Hope this helps
Click to expand...
Click to collapse
TDubKong said:
Love my DropBox. Tried a few other apps like Minus and another but they are just not so user friendly and helpful. Although a couple have more GB.
Click to expand...
Click to collapse
dropbox has been the easiest, havent hit a limit yet, except storage space..... which i upgraded to eliminate that problem, all the others i have tried i cant upload anything because they limit file sizes that you can upload, where as dropbox just syncs with your desktop, takes awhile but works.
just tried it to make a flashable zip and it did the same thing as other guy, flashed the cmd prompt super quick, no zip created.....
edit:
wait i just checked windows update and it has 2 updates for net framework 4 lol
nice i was using the copy paste way. i use one like this for the 3d(that was made by triscuit1983.
still didnt work for me, oh well back to m10 editor... thanx anyways
did you put it on your c drive i had that problem on the one for the 3d
I will try again tomorrow, work in the morning
Sent from my PC36100 using xda premium
life_420 said:
just tried it to make a flashable zip and it did the same thing as other guy, flashed the cmd prompt super quick, no zip created.....
Click to expand...
Click to collapse
dased14 said:
did you put it on your c drive i had that problem on the one for the 3d
Click to expand...
Click to collapse
Make sure that you unzip the files to C:\Lock_Ring_Kit. When I install them somewhere else ("C:\Lock_Ring_Kit______"), I get the same error you do. However, the BATCH file did what it was supposed to do. Since C:\Lock_Ring_Kit did not exist, it created it, and there is a "Working" folder as well as a "Flashable.zip" there. But, since the original files were not in the right place, it is useless.
When the command prompt just flashes, what that means is that M10Tools are not having a chance to run. The only explanation I have for that as of right now is that the files are not in the right location. Also make sure that you named the image LockRing.png.
I'll see about making the batch file spit out an error code, but it might be a few days before I can get around to it. I'll keep yall posted.
So, I've tried the fixes for status 7, installation aborted .I'm trying to install Beanstalk kitkat 4.4.
Attached are the before and after edits of the updater script
After I edit the updater script it just aborts install.
Any help would be appreciated,
(I have a Canadian sgh i727R/Rogers)
punksnotdead83 said:
So, I've tried the fixes for status 7, installation aborted .I'm trying to install Beanstalk kitkat 4.4.
Attached are the before and after edits of the updater script
After I edit the updater script it just aborts install.
Any help would be appreciated,
(I have a Canadian sgh i727R/Rogers)
Click to expand...
Click to collapse
Can you upload the actual updater script you modified to pastebin or something like that? It's hard to tell from the screenshot if there is a syntax error somewhere.
rpr69 said:
Can you upload the actual updater script you modified to pastebin or something like that? It's hard to tell from the screenshot if there is a syntax error somewhere.
Click to expand...
Click to collapse
Thanks for taking a look, file is attached as .txt
punksnotdead83 said:
Thanks for taking a look, file is attached as .txt
Click to expand...
Click to collapse
Wow, I've never really looked at the CM updater script before...complicated...having said that, on what platform, and what editor did you use to modify the script? If it's Windows, and notepad, it probably inserted Windows style EOL characters, which don't make Android happy. I'd re-edit it in Notepad++, and make sure the Edit - EOL Conversion is set to UNIX. If you've already done that, then I'm stumped.
Having said all that, I don't think the assert line is the problem. I have a i727R as well, and I've never had to modify the updater-script for CM, which Beanstalk is based on.
rpr69 said:
Wow, I've never really looked at the CM updater script before...complicated...having said that, on what platform, and what editor did you use to modify the script? If it's Windows, and notepad, it probably inserted Windows style EOL characters, which don't make Android happy. I'd re-edit it in Notepad++, and make sure the Edit - EOL Conversion is set to UNIX. If you've already done that, then I'm stumped.
Click to expand...
Click to collapse
k, I used wordpad, I'll dl notepad++ and try again. Really I was just deleting items not adding so not sure if that matters. Thanks
You can't use wordpad.
Sent from my HTC One using Tapatalk
xcrazydx said:
You can't use wordpad.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Kind of what I said...he is going to do it right with Notepad++
Hi,
Previously, I would edit the build prop to change the DPI on my Nexus however with CM12 nightlies, it is annoying to have to edit it every day. I noticed in CyanDelta that there's an option to flash a zip after updating and I'm wondering whether or not there is (or if I could create) a zip that lowers the DPI.
Thanks!
p3ntyne said:
Hi,
Previously, I would edit the build prop to change the DPI on my Nexus however with CM12 nightlies, it is annoying to have to edit it every day. I noticed in CyanDelta that there's an option to flash a zip after updating and I'm wondering whether or not there is (or if I could create) a zip that lowers the DPI.
Thanks!
Click to expand...
Click to collapse
Extract the zip and edit build_prop.sh to your liking, the one default in this zip changes 480 to 470.
You could probably also use a backuptool/addon.d script instead of flashing a zip if your ROM supports it.
Edit: Reuploaded, forgot to save
Lethargy said:
Extract the zip and edit build_prop.sh to your liking, the one default in this zip changes 480 to 470.
You could probably also use a backuptool/addon.d script instead of flashing a zip if your ROM supports it.
Edit: Reuploaded, forgot to save
Click to expand...
Click to collapse
Thanks! I've just edited it to my preferred DPI and I'll see if it works with tomorrow's nightly! I'm just wondering what a backuptool/addon.d script is? Would it be easier to use even though the zip will automatically be flashed with the ROM update (through CyanDelta)?
EDIT: I just found an addon.d folder in the System directory. Can I just leave the '.sh' file in there?
p3ntyne said:
Thanks! I've just edited it to my preferred DPI and I'll see if it works with tomorrow's nightly! I'm just wondering what a backuptool/addon.d script is? Would it be easier to use even though the zip will automatically be flashed with the ROM update (through CyanDelta)?
EDIT: I just found an addon.d folder in the System directory. Can I just leave the '.sh' file in there?
Click to expand...
Click to collapse
Scripts in addon.d are executed during a ROM flash if your ROM supports it. It might work if you put the .sh in, try it.
Lethargy said:
Scripts in addon.d are executed during a ROM flash if your ROM supports it. It might work if you put the .sh in, try it.
Click to expand...
Click to collapse
I've just put the .sh file in the addon.d folder and I'll see if it works tomorrow.
Thanks for your help!
Lethargy said:
Scripts in addon.d are executed during a ROM flash if your ROM supports it. It might work if you put the .sh in, try it.
Click to expand...
Click to collapse
I just received today's update and unfortunately the addon.d method didn't work. Following that, I tried flashing the zip but TWRP says, 'E:Error executing updater binary in zip '/sdcard/Download/ro.sf.lcd_density.zip'
Do you know what this might be?
p3ntyne said:
I just received today's update and unfortunately the addon.d method didn't work. Following that, I tried flashing the zip but TWRP says, 'E:Error executing updater binary in zip '/sdcard/Download/ro.sf.lcd_density.zip'
Do you know what this might be?
Click to expand...
Click to collapse
Yeah redownloaded and noticed I missed a line.
Lethargy said:
Yeah redownloaded and noticed I missed a line.
Click to expand...
Click to collapse
Thanks! Before I save it, I just want to make sure it is the second number that I should change to my preferred dpi (it says 480 and 470).
p3ntyne said:
Thanks! Before I save it, I just want to make sure it is the second number that I should change to my preferred dpi (it says 480 and 470).
Click to expand...
Click to collapse
Yep
Lethargy said:
Yep
Click to expand...
Click to collapse
Awesome, thanks! Once again, I'll test it out tomorrow.
I made a boot animation, and tried installing it using various methods. First I copied the bootanimation.zip to /system/media. Phone booted fine, but it only showed the Google boot logo (not my animation). I also tried copying it to /data/local, same results. I tried making a flashable zip, but when I tried flashing it in CWM it just said "Installing update… Installation aborted." I have also tried flashing the same animation on the Moto G with same methods, and same results.
What am I doing wrong?
Did you make the zip without compression? It can't be compressed.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Did you make the zip without compression? It can't be compressed.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I used the Keka app for Mac and set it to Store (no compression). I might try some other compression apps.
clavierkid said:
I tried making a flashable zip, but when I tried flashing it in CWM it just said "Installing update… Installation aborted."
Click to expand...
Click to collapse
I guess you didn't sign your zip file.
I always use the same structure for my boot animation so here are the differences with yours. Some of them don't matter though.
1. Into your zip, you have a folder bootanimation => you should directly have your partX folders and desc.txt
2. What is .DS_Store?
3. Naming:
part0 => 000.png / 001.png / 002.png....
part1 => 003.png / 004.png / 005.png....
4. desc.txt:
Code:
1080 1920 15
p 1 5 android
p 0 0 part1
Replace "android" by "part0"
BTW the second number is the delay between loops (in milliseconds) so "5" seems useless.
Primokorn said:
I guess you didn't sign your zip file.
I always use the same structure for my boot animation so here are the differences with yours. Some of them don't matter though.
Click to expand...
Click to collapse
Thanks for the feedback! I tried changing the structure of the zip file as you suggested, same results. DS_Store is an annoying hidden file Mac OS makes, I deleted it. I also changed the desc.txt. Still not working.
Would signing the zip make a difference?
clavierkid said:
Thanks for the feedback! I tried changing the structure of the zip file as you suggested, same results. DS_Store is an annoying hidden file Mac OS makes, I deleted it. I also changed the desc.txt. Still not working.
Would signing the zip make a difference?
Click to expand...
Click to collapse
The bootanimation.zip shouldn't be signed. Upload your new version and I'll have a look on my phone.
Primokorn said:
The bootanimation.zip shouldn't be signed. Upload your new version and I'll have a look on my phone.
Click to expand...
Click to collapse
Here it is
clavierkid said:
Here it is
Click to expand...
Click to collapse
Try this: https://www.dropbox.com/s/df7v0u1niexpvcd/bootanimation.zip?dl=1
It works now on my phone. I removed several png files (for testing purpose) because I resized them to 1080x1920.
I also changed desc.txt and removed DS_store file.
Copy this zip file into /system/media/ with 0644. Reboot.
Primokorn said:
Try this: https://www.dropbox.com/s/df7v0u1niexpvcd/bootanimation.zip?dl=1
It works now on my phone. I removed several png files (for testing purpose) because I resized them to 1080x1920.
I also changed desc.txt and removed DS_store file.
Copy this zip file into /system/media/ with 0644. Reboot.
Click to expand...
Click to collapse
It works! Thank you!
This module patches OPLongshot's code so that it produces PNG screenshots, as it should, instead of JPEG screenshots (ew!). It patches only the VDEX/ODEX files, which have no signature on them — only the APK is signed, which we do not modify, so OPLongshot still retains system signature privileges. The original APK is included to avoid version mismatches (although I don't think there will be much issue even if it isn't includd).
Note that the OPLongshot was taken from the OnePlus 5T's system image. YMMV for other devices on OxygenOS (or even HydrogenOS?).
The current version uses the version of OPLongshot from OnePlus 5T OxygenOS 5.1.0/5.1.1 (same), with version 1.1.0.180328153957.6a699c8.
Remember to clear Dalvik/ART cache after installing this.
GitHub repository (also details of how the patch is done).
Download zip (temporary until the Magisk repo bot refreshes)
Hello, could you make a valid version for Nougat? Try yours but it does not work. You could also add the option of 9999 captured pages instead of 12 (do not do it). I saw several values to modify but it did not work ... if you want I'll give you the latest version of nougat. Thank you! @angelsel
PD: Here the apk (OPLongshot) https://mega.nz/#F!KY1gHR6A!taK5YsqI4pwOpe3ewrdAWg
Youtube_Ll0r3nt3 said:
Hello, could you make a valid version for Nougat? Try yours but it does not work. You could also add the option of 9999 captured pages instead of 12 (do not do it). I saw several values to modify but it did not work ... if you want I'll give you the latest version of nougat. Thank you! @angelsel
PD: Here the apk (OPLongshot) https://mega.nz/#F!KY1gHR6A!taK5YsqI4pwOpe3ewrdAWg
Click to expand...
Click to collapse
Could you run (on your device) `oatdump --oat-file=/system/app/OPLongshot/oat/arm64/OPLongshot.odex --export-dex-to=some/dir` and get the resulting DEX file?
angelsel said:
Could you run (on your device) `oatdump --oat-file=/system/app/OPLongshot/oat/arm64/OPLongshot.odex --export-dex-to=some/dir` and get the resulting DEX file?
Click to expand...
Click to collapse
Bro, the .odex file in the longshot folder that happens to you the mega, also throws me this:
Some output directory not found or symlink
Thanks!
Youtube_Ll0r3nt3 said:
Bro, the .odex file in the longshot folder that happens to you the mega, also throws me this:
Some output directory not found.
Thanks!
Click to expand...
Click to collapse
Eh? What's the exact error?
angelsel said:
Eh? What's the exact error?
Click to expand...
Click to collapse
https://ibb.co/k3UcJc
Youtube_Ll0r3nt3 said:
https://ibb.co/k3UcJc
Click to expand...
Click to collapse
Yeah, err, I didn't mean to type "some/dir" verbatim, but some path on the sdcard perhaps to export the dex to.
I guess just /sdcard will do.
angelsel said:
Yeah, err, I didn't mean to type "some/dir" verbatim, but some path on the sdcard perhaps to export the dex to.
I guess just /sdcard will do.
Click to expand...
Click to collapse
https://mega.nz/#!2U5mFSYL!i-EkFdHd5auzuY0hGUPC_ArW30MDDhQwct8gT-WLOMU
Thanks bro
Hello I tried on 5.0.4 but screenshot app crashes
This module works flawlessly on my OnePlus 5, in case anyone else wanted to try it on theirs.
Who at OnePlus decided JPGs should be used for screenshots? Gross.
Thanks!
does it work on android pie? Testing it on OnePlus 6 and it's not working. can't take screenshot anymore
Can anybody confirm if this Xposed module works on OnePlus 7T using Android 10, thanks.
---Edit---
Can confirm that it doesn't work on OnePlus 7T after attempting to flash w/ Magisk.