Updater Script Fails... Bootloop... Help!? - Nexus 6 Q&A, Help & Troubleshooting

Hey Folks!
I'm working on my newest Project called "Fluence HD Patch".
Basicly it will just add the content from my Fluence HD ROM to any excisting/flashed ROM, but now the Problem...
The Content which i add always to my ROMs forces a Bootloop after flashing as Stand alone. Included in a ROM there is no Problem. Changed the Updater Script a lot of times, but no success yet...
Hope anyone can help me!? This **** brakes my Neck!
Thanks in advance!

Did you edit it with something other than Notepad++

Miustone said:
Hey Folks!
I'm working on my newest Project called "Fluence HD Patch".
Basicly it will just add the content from my Fluence HD ROM to any excisting/flashed ROM, but now the Problem...
The Content which i add always to my ROMs forces a Bootloop after flashing as Stand alone. Included in a ROM there is no Problem. Changed the Updater Script a lot of times, but no success yet...
Hope anyone can help me!? This **** brakes my Neck!
Thanks in advance!
Click to expand...
Click to collapse
If experiencing a bootloop, does restoring the original build.prop and setting 0644 permissions through TWRP's File Manager allow the device to fully boot? If yes, then it must be an entry or a permissions issue. My next step in that case would be to flash the Fluence Patch to force the bootloop, boot to TWRP, mount System, set permissions to 0644 for the patched build.prop, and reboot. If the bootloop persists then there is certainly something inside causing it. Is there a single entry added that you didn't incorporate in one of your previous roms?
Also, the only other changes from flashing the patch is a build.prop backup and a tweak.prop on /sdcard, right? The next step in this scenario I would do after experiencing that second bootloop after ensuring the patched build.prop had 0644 permissions would be deleting both of those files that were added to /sdcard through TWRP's File Manager, assuming I had made my own copy of the original build.prop on /sdcard before the very first flash of the patch. If that doesn't allow the device to boot then there is something in the patched build.prop.
Edit*
After reading your Fluence Patch thread it is clear you are talking about the Full Patch causing the bootloop issue and not the one in the thread at the moment. I'll take a look if you want to send me a copy. The META-INF folder and any script(s) used during installation might be enough but not positive. :good:

ronaldheld said:
Did you edit it with something other than Notepad++
Click to expand...
Click to collapse
Nope, I'm using only Notepad++ ? The Zip flashs also successful...
guitardedhero said:
If experiencing a bootloop, does restoring the original build.prop and setting 0644 permissions through TWRP's File Manager allow the device to fully boot? If yes, then it must be an entry or a permissions issue. My next step in that case would be to flash the Fluence Patch to force the bootloop, boot to TWRP, mount System, set permissions to 0644 for the patched build.prop, and reboot. If the bootloop persists then there is certainly something inside causing it. Is there a single entry added that you didn't incorporate in one of your previous roms?
Also, the only other changes from flashing the patch is a build.prop backup and a tweak.prop on /sdcard, right? The next step in this scenario I would do after experiencing that second bootloop after ensuring the patched build.prop had 0644 permissions would be deleting both of those files that were added to /sdcard through TWRP's File Manager, assuming I had made my own copy of the original build.prop on /sdcard before the very first flash of the patch. If that doesn't allow the device to boot then there is something in the patched build.prop.
Edit*
After reading your Fluence Patch thread it is clear you are talking about the Full Patch causing the bootloop issue and not the one in the thread at the moment. I'll take a look if you want to send me a copy. The META-INF folder and any script(s) used during installation might be enough but not positive. :good:
Click to expand...
Click to collapse
Thanks for the Reply Man! As you suggested right in Your edit, the build.prop is just fine for now... I will upload the patch content after waking up completely... Was a hard night ?
Your help is much appreciated! Thanks again! :angel:

Related

problem with replacing gps.conf

Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..
aerosmike said:
Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..
Click to expand...
Click to collapse
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.
alray said:
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.
Click to expand...
Click to collapse
Thank you very much

[HOW TO] Full Root EMUI 3.0

Hello,,,
anybody knows how to fully root emui 3.0. i've been trying to use 3.0 since it was released by Oxalis for L10 but i have a problem in rooting. I did root the phone, but i can say it is only 99% rooted, bcoz everytime i tried to delete file or app under /system/app directory files will be reverted after rebooting. i've deleted the files or app under the mentioned directory and i successfully deleted, but again, if i will reboot the phone, the apps deleted will be installed again.
Use custom E3.0 rom,unpack zip on pc,delete unwanted apps and everything you want,pack in zip again and than flash rom.This is only way (in my case) to delete unwanted apps.In any other way deleted apps return back after reboot.
Sent from my HUAWEI P7-L10 using Tapatalk
gregysk said:
Use custom E3.0 rom,unpack zip on pc,delete unwanted apps and everything you want,pack in zip again and than flash rom.This is only way (in my case) to delete unwanted apps.In any other way deleted apps return back after reboot.
Sent from my HUAWEI P7-L10 using Tapatalk
Click to expand...
Click to collapse
i'll better make updater.zip than unpacking system...
Just flash a different kernel, the 3.0 version from this thread: http://forum.xda-developers.com/asc...ds-tweaks-kernels-recoverys-emui-2-3-t2966670
The stock kernel contains a ramdisk which restores files deleted from the system partition. The custom kernel does not.
witteswa said:
Just flash a different kernel, the 3.0 version from this thread: http://forum.xda-developers.com/asc...ds-tweaks-kernels-recoverys-emui-2-3-t2966670
The stock kernel contains a ramdisk which restores files deleted from the system partition. The custom kernel does not.
Click to expand...
Click to collapse
Thanks a lot... I hope this will work. coz i tried everything except this. I will install 3.0 again later. Thank you so much.
witteswa said:
Just flash a different kernel, the 3.0 version from this thread: http://forum.xda-developers.com/asc...ds-tweaks-kernels-recoverys-emui-2-3-t2966670
The stock kernel contains a ramdisk which restores files deleted from the system partition. The custom kernel does not.
Click to expand...
Click to collapse
thanks for this idea. i am 100% rooted now. thanks a lot.
Did you delete file set_immutable.list ?
majcomtech said:
thanks for this idea. i am 100% rooted now. thanks a lot.
Click to expand...
Click to collapse
hi, i am also trying to fully root Emui 3.0. i am currently running Emui 3.0 b602 on L10 and after rooting (CWM+Update SuperSU) same issue (with files being reverted)
now I am relying on updates.zip through CWM for downgrades,etc using sideload update through usb and sometimes feels awkward
I followed the link mentioned above and found a custom E3.0 rom named boot_HRT_emui3.0.img.
@majcomtech, is this the one file that made you 100% root? I did not see references to L05, L07 or L10 nor B602, B604 or B609. Does it mean that this HRT boot.img is valid for all P7 models, say for the whole family of p7s?
will it fully root my 99% P7 L10 B620 EMUI3.0 BETA to 100% P7 L10 B620 EMUI3.0 BETA even though is not specific to a L10 nor b602?
@Kostyan_nsk, can not find set_immutable.list file inside /system folder as I used to have, a config text file with a list of immutable folders and files.
If I flash that hrt boot image I would not need to delete that file? is that the following step, flash new boot.img then delete set_immutable.list?
thanks in advance for your advice, those seam like a lot of questions :silly:
p.d: sorry english not my native language
Printusrzero said:
@Kostyan_nsk, can not find set_immutable.list file inside /system folder as I used to have, a config text file with a list of immutable folders and files.
If I flash that hrt boot image I would not need to delete that file? is that the following step, flash new boot.img then delete set_immutable.list?
Click to expand...
Click to collapse
The principle of locking system files and folders is next: there is set_immutable binary in ramdisk of boot image that executes in boot up. This binary reads list of files and folders in /system/set_immutable.list and locks them.
So there's several ways to avoid it: delete or comment line in init.rc file in ramdisk that executes set_immutable. As I remember, it looks like "exec set_immutable 1". Or change parameter from "1" to "0". Or completely delete set_immutable binary from ramdisk. So if set_immutable won't execute, existense of /system/set_immutable.list won't affect at anything.
Or you can just delete set_immutable.list and set_immutable binary will not lock anything because it will not be able to get list of files and folders to lock.
If you don't have set_immutable.list file already, I think custom boot image with disabled set_immutable binary will not solve your issue. But you have to try anyway. If system won't boot, just revert back your boot.img via fastboot or TWRP and you won't loose anything.
I think problem is in su binary. Something with security context or permissions or something else. But it's just my humble opinion, probably I'm wrong.
Thanks Kostyan_nsk for your last post!
I unpacked ramdisk and set 'exec set_immutable 1' to 0. flashed and recovery still active.
then unpacked again and renamed immutable binary inside initrc/sbin, flashed and recovery still on
I also checked supersu binaries and updated supersu both through CWM and Google... so far all my efforts were to not avail
solved! flashing custom 3.0 kernel fixed it. Kostyan_nsk you directed me to the right direction init.rc, thanks a lot .

[MOD][TEMPLATE] Magisk Module Template with EvilTheme Patcher

Hello everyone.
This is a little mod to the Magisk Module Template that allows you to patch APK files on-the-fly and have them created as a Magisk Module.
For example, you could have a modified camera module for your ROM, where this patcher would replace the classes.dex file with mods, then pack that as a Magisk Module, using the original file found in the /system (ROM)
For some of the devs that have been around for a while, you would be aware of the old VRTheme modding system, which would allow you to patch files on-the-fly. EvilTheme is basically a newer version of that, so combined with Magisk can be very useful
Here's what this module CAN do:
Replace resources.arsc, classes.dex, AndroidManifest.xml, and META-INF folder
Replace compiled res folders / files
Here's what this module CAN'T do:
Replace files in res/values or smali folders
How to use EVilTheme
(Example using /system/priv-app/SecSettings2.apk)
In the eviltheme folder, go to system and make a folder called priv-app. Inside it, make another folder called SecSettings2.apk
Now make folders as necessary, according to the location of the files you want to theme. For example, battery_icon_50.png is located in res/drawable-hdpi, so make a folder named res inside SecSettings2.apk.
Inside it, create a folder named drawable-hdpi, then paste your new battery_icon_50.png inside.
Repeat step 2 until you've placed your theme files in their appropriate locations.
When you're done, go back to the root folder of the theme (the one that contains eviltheme, engine, etc.) and put all the objects in a ZIP file.
You should use Deflate compression with compression level on Normal, but if your theme is huge, you can safely try compressing using Deflate and the level set to Ultra or whatever high level is available.
Test your mod.
For information regarding the Magisk Module subbmision etc, please read the information HERE
Link to Github Repository: HERE
Enjoy
Nice! Sounds interesting!
I've been using vrtheme for years and even contacted spanna aabout adapting the script to achieve modding of live system files this eliminating the need for recovery zips and even Aroma!
So I have a question about the use and locations of the asset files.
Would it be possible to change, at least the location from which the files get pulled from and placed into the execute folders?
So basically could it be set to pull the image/resource, whatever file from either a data folder or my preference, sd storage?
I've used an asset folder built into my system for similar commands, but with enough options and large files the system partition can get extremely crowded.
Does my question make sense?
Basically i would like to eliminate a big section of my packed 2gb Aroma zip. About 700mb is all vrtheme injected compiled files.
Either way I will definitely be looking into this!
Thanks
stangdriver44 said:
Nice! Sounds interesting!
I've been using vrtheme for years and even contacted spanna aabout adapting the script to achieve modding of live system files this eliminating the need for recovery zips and even Aroma!
So I have a question about the use and locations of the asset files.
Would it be possible to change, at least the location from which the files get pulled from and placed into the execute folders?
So basically could it be set to pull the image/resource, whatever file from either a data folder or my preference, sd storage?
I've used an asset folder built into my system for similar commands, but with enough options and large files the system partition can get extremely crowded.
Does my question make sense?
Basically i would like to eliminate a big section of my packed 2gb Aroma zip. About 700mb is all vrtheme injected compiled files.
Either way I will definitely be looking into this!
Thanks
Click to expand...
Click to collapse
You could, but you would have to look at update-binary and installtheme.sh, then modify it for your needs. So instead of copying the modded files from the flashable zip, you would just have to remove the unzip function and change the path of where they are unzipped to to the location of where the files are on your data partition.
Give it a try
so with this I can technically change the rotation of an app without ever messing with the apk? I've tried editing the AndroidManifest.xml, but after editing I've never been successful putting it back into the apk
dimm0k said:
so with this I can technically change the rotation of an app without ever messing with the apk? I've tried editing the AndroidManifest.xml, but after editing I've never been successful putting it back into the apk
Click to expand...
Click to collapse
If you plan to change androidmanifest.xml you will have to include the newly created META-INF folder for it too.
Could this be used to convert substratum themes to work systemlessly with magisk?
Sent from my Pixel using XDA Labs
qwer777 said:
Could this be used to convert substratum themes to work systemlessly with magisk?
Sent from my Pixel using XDA Labs
Click to expand...
Click to collapse
If you're talking about pre-packaged APK theme files, no it probably won't work, as they still need to be installed.
This is more for files that are already installed that require patching.
Nice work
Got one question - is it possible to modify classes.dex if .apk file is not in system folder? I mean for example, if system app gets updated, it creates new folder in data/app/ with the name of the package and with either -1, -2 or whetever number at the end (ex. data/app/com.google.android.youtube-2).
Do I need to just integrate update into system and then modify it? Or just create new folder in eviltheme one with data/... instead of system/...?
Thanks
I tried to modify system/framework/framework-res.apk/res/drawable-xxhdpi-v4/default_wallpaper.jpg, but unfortunately it did not work. Neither on InFocus M808/mod stock 6.0(mt6753) nor on SamsungS5Neo/mod stock 6.0.1(exynos7580)
Both tried with official Magisk 12.0 and newest beta.
nevermind i didn't read all the way
drei.liter.milch said:
I tried to modify system/framework/framework-res.apk/res/drawable-xxhdpi-v4/default_wallpaper.jpg, but unfortunately it did not work. Neither on InFocus M808/mod stock 6.0(mt6753) nor on SamsungS5Neo/mod stock 6.0.1(exynos7580)
Both tried with official Magisk 12.0 and newest beta.
Click to expand...
Click to collapse
Started another try to replace some icons. did not work. am I missing something or is this template just faulty?
anybody who got this working?
drei.liter.milch said:
Started another try to replace some icons. did not work. am I missing something or is this template just crap?
anybody who got this working?
Click to expand...
Click to collapse
That was a bit rude.
Edit: better to give some details on what you've actually done, maybe even upload your files. Easier to find any faults on your side or possible bugs that way.
I want to add the clock onto my lockscreen statusbar. Would this help me achieve that?
Didgeridoohan said:
That was a bit rude.
Edit: better to give some details on what you've actually done, maybe even upload your files. Easier to find any faults on your side or possible bugs that way.
Click to expand...
Click to collapse
yes ok, the word "crap" maybe was a little bit over the top. i'm sorry for that. I just would like to know, if anybody can report this module/template as working. If so, I would go on looking for the error on my side.
I've actually followed exactly the guide given in OP. (It seems not that tricky to me)
-placed folder tree system/framework/framework-res.apk/res/drawable-xxhdpi-v4/ in the eviltheme-folder and put my default_wallpaper.jpg file in drawable-xxhdpi-v4 folder
-edited module.prop und config.sh
-zipped the whole template folder
-installed via magisk manager
-rebooted
tried with to different phones, beta and official magisk (see my first post)
I'll reproduce my logs and attach them later.
anyway thanks for the hint
drei.liter.milch said:
yes ok, the word "crap" maybe was a little bit over the top. i'm sorry for that. I just would like to know, if anybody can report this module/template as working. If so, I would go on looking for the error on my side.
I've actually followed exactly the guide given in OP. (It seems not that tricky to me)
-placed folder tree system/framework/framework-res.apk/res/drawable-xxhdpi-v4/ in the eviltheme-folder and put my default_wallpaper.jpg file in drawable-xxhdpi-v4 folder
-edited module.prop und config.sh
-zipped the whole template folder
-installed via magisk manager
-rebooted
tried with to different phones, beta and official magisk (see my first post)
I'll reproduce my logs and attach them later.
anyway thanks for the hint
Click to expand...
Click to collapse
Flash Via Recovery, it may work. didnt work for me when i installed from magisk manager.
btw i have a question, is there any way to remove a file from the apk?
shekhawat2 said:
Flash Via Recovery, it may work. didnt work for me when i installed from magisk manager.
btw i have a question, is there any way to remove a file from the apk?
Click to expand...
Click to collapse
thx, i'll try that. which magisk-version do you use? and i guess maybe you can remove a file by placing a dummy.
drei.liter.milch said:
thx, i'll try that. which magisk-version do you use? and i guess maybe you can remove a file by placing a dummy.
Click to expand...
Click to collapse
No brother, I want to delete the file, not to replace it with dummy file. Replacing with dummy file will give system ui FCs.
I saw something delete.list in the installtheme.sh, but I don't know how to use it. If anyone can help, pls help me.
BTW I am using Magisk v12.
shekhawat2 said:
No brother, I want to delete the file, not to replace it with dummy file. Replacing with dummy file will give system ui FCs.
I saw something delete.list in the installtheme.sh, but I don't know how to use it. If anyone can help, pls help me.
BTW I am using Magisk v12.
Click to expand...
Click to collapse
Ok, I see. Perhaps you find sth about it in the vrtheme-topic. Btw. flashing in recovery doesn't work either. I'm not messing around with this anymore and continue using flipster :good:
Where can we download? I want to change Viber's background to pure black so I will change the AndroidManifest. Will this theoretically work?
I was wondering what, if anything, I would need to change for this to work on a pixel. On Pixel's, the install path is system/system. I couldn't tell whether or not this could detect the correct path on its own.
Edit: Never mind. I got it to work.

android 11 root problem miui 12.5

hi.I rooted the phone using magisk, it was installed and apparently rooted, but I have a problem with root file programs like root explorer or es file manager. The problem is that the rw mount does not work or I even have trouble installing busybox.
my phone : redmi note 10 pro
miui version : 12.5.8 and 12.5.9
android version : 11
magiak version : 23
I don't know deeply this case, but it was told that mounting r/w is not possible in recent Androids for system partitions.
However this is Magisk benefit that you put your files to it's tree and Magisk overmounts original files, I guess it does it using option "mount --bind".
You put file into /data/adb/modules/<module_name>/system/etc/<exemplary file> and after reboot you see it under /system/etc/.
At least the above path was checked personally by me by changing /system/etc/gps_psds.conf file to my own.
F308 said:
I don't know deeply this case, but it was told that mounting r/w is not possible in recent Androids for system partitions.
However this is Magisk benefit that you put your files to it's tree and Magisk overmounts original files, I guess it does it using option "mount --bind".
You put file into /data/adb/modules/<module_name>/system/etc/<exemplary file> and after reboot you see it under /system/etc/.
At least the above path was checked personally by me by changing /system/etc/gps_psds.conf file to my own.
Click to expand...
Click to collapse
I want to install a program as a system, but it is not possible without rw mount, do you know the solution?
I presume you have at least one Magisk module installed.
Put it into /data/adb/modules/<any_Magisk_module_name>/PATH_WHERE_YOU_WANT_TO_HAVE_IT/.
If wanted directories don't exist - create them.
Reboot.
Check.
Maybe tune permissions to make file executable.
Report result here.
F308 said:
I presume you have at least one Magisk module installed.
Put it into /data/adb/modules/<any_Magisk_module_name>/PATH_WHERE_YOU_WANT_TO_HAVE_IT/.
If wanted directories don't exist - create them.
Reboot.
Check.
Maybe tune permissions to make file executable.
Report result here.
Click to expand...
Click to collapse
I have no problem installing the module. My problem is accessing the system / app folder and making changes.
What changes do you want to perform?
Change one or more of files there, right?
If so - I repeat.
Put your modified file(s) under /data/adb/modules/<any_installed_Magisk_module_name>/system/app/ and reboot.
F308 said:
What changes do you want to perform?
Change one or more of files there, right?
If so - I repeat.
Put your modified file(s) under /data/adb/modules/<any_installed_Magisk_module_name>/system/app/ and reboot.
Click to expand...
Click to collapse
I do not want to install the module, I want to move an apk file to the system/app folder that is installed as a system and can not be deleted
I wasted my time.
Good luck.
I devoted a while to check that I was right suggesting what I suggested.

Can Xposed hook Runtime.loadLibrary for a system call ?

The custom rom I am using on my device for some reason doesn't have logcat. After a bit of digging up in the root folder, I found out that it was missing logd file which should be present under /system/bin and is necessary for logcat to work. Already tried to copy it from the official rom of my device (I extracted it from system.img) but pasting it manually (tried both a root explorer and adb) in /system/bin won't do anything as any changes made to /system/bin get reverted back automtically after reboot.
So I thought of a method about hooking Runtime.loadLibrary with xposed and redirecting it to logd on my internal storage when it's requested. Isn't that possible ?
Otherwise, do you suggest any other solution?
Do you think I should move the file with twrp if this doesn't work ? (I am avoiding the use of it because it's still unstable for my device and bootlooped a few times.).
Or should I edit the custom rom's system.img and repack it (I'm afraid if it's size changes my device won't boot)
I will be very grateful if someone helps me out
if you copy a file you must set right permissions and ownership

Categories

Resources