Related
Hello guys im trying for awhile to make a run some boot animation sound over the stock CM6 blue android that is comming as stock but i never get succes can somebody help me with this please
juancaperez2000 said:
Hello guys im trying for awhile to make a run some boot animation sound over the stock CM6 blue android that is comming as stock but i never get succes can somebody help me with this please
Click to expand...
Click to collapse
The solution is not for the faint of heart and will have to be reapplied with each nightly.
Add this to init.local.rc
Code:
###Bootsound - Safe to Delete: Start ###
service bootsound /system/bin/bootsound
user media
group audio
disabled
oneshot
on property:init.svc.bootanim=running # to correct timing
start bootsound
on property:dev.bootcomplete=1
stop bootsound
### Bootsound - Safe to Delete: End ###
Then make a new file called "bootsound" and push it to /system/bin
i.e. "adb push c:\path\to\bootsound /system/bin/bootsound"
Code:
#!/system/bin/sh
bprop=/system/build.prop
grepprop() { x=`grep "^$1=" $bprop | head -n 1`; echo $x | cut -d = -f 2; }
play=`grepprop "ro.config.play.bootsound"`
if [ "$play" = "1" ]; then
stagefright -a -o /data/local/android_audio.mp3
fi
exit 0
Issue the following commands:
Code:
adb remount
adb shell chmod 777 /system/bin/bootsound
adb shell chown root:shell /system/bin/bootsound
adb shell echo ro.config.play.bootsound=1 | cat >> /system/build.prop
Now put your startup sound, whatever MP3 it is, in /data/local with name android_audio.mp3 and it will be played at startup. You test it with an adb reboot. I flash nightlies on a regular basis so I stopped doing this as it's a PITA to constantly have to push changes each night. I like to flash + go.
'tuna
Wow...only question is would this work for for stable 6? And can I do it thru term emu
cubanjinx said:
Wow...only question is would this work for for stable 6? And can I do it thru term emu
Click to expand...
Click to collapse
As long as you have a way to edit the init file + create/edit the new bootsound file then yes it can be done via term emu. Should work with any/all versions of cm6. Obviously you'd omit the "adb shell" portion of the shell commands.
'tuna
spiicytuna said:
The solution is not for the faint of heart and will have to be reapplied with each nightly.
......
'tuna
Click to expand...
Click to collapse
Wow. One of the best answers I have ever seen around here.
spiicytuna said:
The solution is not for the faint of heart and will have to be reapplied with each nightly.
---------
Now put your startup sound, whatever MP3 it is, in /data/local with name android_audio.mp3 and it will be played at startup. You test it with an adb reboot. I flash nightlies on a regular basis so I stopped doing this as it's a PITA to constantly have to push changes each night. I like to flash + go.
'tuna
Click to expand...
Click to collapse
Wow. Not kidding with the "not for the faint of heart" part. I think I will live with no sound. Unless, I knew how the hell to use that code. Meh....
Will donate
Tuna or anyone else willing to walk me through this for a donation? Haha... I set up a whole mp3 for the boot to come to this road block. Also, for anyone reading, how can I change just the lock screen wallpaper on froyo. (Using plain black background right now and it makes the lockscreen a little too boring) Thanks.
has this been confirmed working on CM6 final? read some comments over at the cyanogenmod forum that this script was droid x phones, not the evo?
i'm going to give it a try tonight or tomorrow night, some questions
1)where is the init.local.rc file?
2)what kind of file should the bootsound file be? .txt file? no extension? ??
3) the code you put after saying to make the bootsound, does that mean that code is to be entered into adb or as the content of the bootsound file?
spiicytuna said:
The solution is not for the faint of heart and will have to be reapplied with each nightly.
'tuna
Click to expand...
Click to collapse
EDIT: tried it. edited the init.local.rc file using Notepad++. made the bootsound file using Notepad++ and in it put the code you have up there. no file extension. pushed it to the right directory, followed the adb commands. got an error in the last one (echo) saying it couldn't find the path (it's there though?).
put the android_audio.mp3 in /data/local....rebooted and no sound. no errors either, but no sound.
EDIT 2: thanks for your work spiciituna. apparently there was some mistake on my part. i ran a script that your code in it and now the boot sound works.
http://forum.cyanogenmod.com/topic/7433-bootanimations-audio/
I am still having no luck. :-( Can anyone enlighten me?
Sent from my PC36100 using XDA App
austinjay said:
I am still having no luck. :-( Can anyone enlighten me?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I was finally about to get it to work.
Here is the post with the flashable zip
http://forum.xda-developers.com/showthread.php?t=844414
juancaperez2000 said:
Hello guys im trying for awhile to make a run some boot animation sound over the stock CM6 blue android that is comming as stock but i never get succes can somebody help me with this please
Click to expand...
Click to collapse
if it's FroYo, then the directory has been moved to /system/customize/resource/. You reboot to clockworkmod -> mount system (partitions menu) -> reboot recovery (advanced menu) -> open cmd prompt in windows, cd to sdk\tools\ and run: "adb remount" -> then have the .wav file in the tools folder and run "adb push ATT_bootup.wav /system/customize/resource/" if it's an AT&T phone. Verizon phones use VZW_bootup.wav I am pretty sure & I'm not sure about the other ones.
Hello all,
i would like to buy a new (cheap) tablet which i can modify to auto boot / start on charge. I need this for an project. I plan to use this tablet as a mediaplayer in my new bathroom and the buttons of this tablet will not be reachable. Is it possible to modify every device to auto boot on charge or has someone experience with devices not working?
Thx and greetings
gigi
Sorry OP
i want to hijack this thread to to compile all successful method for different devices to autoboot when plug in /charging
any one to do this must root their device and use AIK to decompile/recompile boot.image, modify certain file depending on the device
---------- Post added at 05:35 PM ---------- Previous post was at 05:23 PM ----------
]REDMI 6A MTK Device
need to modify kopc_charger file
here
https://forum.xda-developers.com/showpost.php?p=81874791&postcount=158
https://forum.xda-developers.com/showpost.php?p=81880927&postcount=159
---------- Post added at 05:45 PM ---------- Previous post was at 05:35 PM ----------
On I9500 runing linage OS 16
modify the init.rc
on charger
setprop ro.bootmode "normal"
setprop sys.powerctl "reboot"
---------- Post added at 06:03 PM ---------- Previous post was at 05:45 PM ----------
Redmi 4x
modify init.rc
on charger
class_start charger
class_stop charger
on property:sys.boot_from_charger_mode=1
trigger late-init
Samsung S5 (klte)
Working Roms: lineage-15.1
stock 6
modify init.rc:
on charger
setprop ro.bootmode "normal"
setprop sys.powerctl "reboot"
tried the same with samsung s3 mini (kminilte) but not working
HI there, i have installed this Rom to my samsung s8, it is pretty cool, and i am trying to set auto boot on USB power pluggin, but until now, no luck.
Since Android 10, seems the init.rc is regenerated every time when it boots, so unpack/repack of the .img solution seems not working any more. what i am trying next is via magisk module, still in process but no progress.
Is there any other way to do this? any light would be appreciated.
tonyniu2008 said:
HI there, i have installed this Rom to my samsung s8, it is pretty cool, and i am trying to set auto boot on USB power pluggin, but until now, no luck.
Since Android 10, seems the init.rc is regenerated every time when it boots, so unpack/repack of the .img solution seems not working any more. what i am trying next is via magisk module, still in process but no progress.
Is there any other way to do this? any light would be appreciated.
Click to expand...
Click to collapse
The init.rc is unpacked from the boot partition, you see in / only a copy of init.rc
What other solutions did you try to make it boot instantly?
hisoka_simp said:
The init.rc is unpacked from the boot partition, you see in / only a copy of init.rc
What other solutions did you try to make it boot instantly?
Click to expand...
Click to collapse
I tried to unpack the boot image, and actually the init.rc is missing from the root path, i googled it, as i think it caused by the system version, starting from Android 10, init.rc will be only generated when booting, my system is LineageOS 17.1
when the system finishing booting, i can adb shell to the file, init.rc is there then, i tried to unpack the recovery image, the init.rc is there, i tried to change that and flash to boot, and recovery, no luck, after booting the init.rc still keep the same as before.
I am currently trying the magisk module, but not yet a solution.
As you said the init.rc is copyed from somewhere, do you know where?
tonyniu2008 said:
I tried to unpack the boot image, and actually the init.rc is missing from the root path, i googled it, as i think it caused by the system version, starting from Android 10, init.rc will be only generated when booting, my system is LineageOS 17.1
when the system finishing booting, i can adb shell to the file, init.rc is there then, i tried to unpack the recovery image, the init.rc is there, i tried to change that and flash to boot, and recovery, no luck, after booting the init.rc still keep the same as before.
I am currently trying the magisk module, but not yet a solution.
As you said the init.rc is copyed from somewhere, do you know where?
Click to expand...
Click to collapse
Can you send me a link (google drive would be nice) to an unmodified version of your boot.img? I'll modify it correctly and send back to you
hisoka_simp said:
Can you send me a link (google drive would be nice) to an unmodified version of your boot.img? I'll modify it correctly and send back to you
Click to expand...
Click to collapse
It is so kind of you, you can find my TWRP backup image here: https://drive.google.com/file/d/1dtdovnRIZY58SYqFBNEgT4TafktmAycd/view?usp=sharing
just have a clean backup there. but as i unpacked, there is no init.rc under root, hope you know a way for this.
Let me know if you found something, thx
hisoka_simp said:
Can you send me a link (google drive would be nice) to an unmodified version of your boot.img? I'll modify it correctly and send back to you
Click to expand...
Click to collapse
The content of ramdisk is extracted from the boot partition every time it starts, so modifying init.rc does not work.
I extracted my boot partition to boot.img, then unpacked it, modified the init.rc inside, repackaged it as boot.img, and finally flashed into the boot partition
After the system started, I saw that the init.rc was modified
But it’s not pungent and has no effect
on charger
class_start charger
setprop sys.powerctl reboot
My device is huawei MediaPad3，maybe your device can work。Try it
tonyniu2008 said:
I tried to unpack the boot image, and actually the init.rc is missing from the root path, i googled it, as i think it caused by the system version, starting from Android 10, init.rc will be only generated when booting, my system is LineageOS 17.1
when the system finishing booting, i can adb shell to the file, init.rc is there then, i tried to unpack the recovery image, the init.rc is there, i tried to change that and flash to boot, and recovery, no luck, after booting the init.rc still keep the same as before.
I am currently trying the magisk module, but not yet a solution.
As you said the init.rc is copyed from somewhere, do you know where?
Click to expand...
Click to collapse
The content of ramdisk is extracted from the boot partition every time it starts, so modifying init.rc does not work.
I extracted boot partition to boot.img, then unpacked it, modified the init.rc , repackaged it as boot.img, and finally flashed into the boot partition
After the system started, I saw that the init.rc was modified
But it’s no effect
on charger
class_start charger
setprop sys.powerctl reboot
My device is huawei MediaPad3，maybe your device can work。Try it
bearllm said:
The content of ramdisk is extracted from the boot partition every time it starts, so modifying init.rc does not work.
I extracted boot partition to boot.img, then unpacked it, modified the init.rc , repackaged it as boot.img, and finally flashed into the boot partition
After the system started, I saw that the init.rc was modified
But it’s no effect
on charger
class_start charger
setprop sys.powerctl reboot
My device is huawei MediaPad3，maybe your device can work。Try it
Click to expand...
Click to collapse
Hey I recommend you to also try this code which worked for another device I had, hope it works
on charger
setprop ro.bootmode "normal"
setprop sys.powerctl "reboot"
hisoka_simp said:
Hey I recommend you to also try this code which worked for another device I had, hope it works
on charger
setprop ro.bootmode "normal"
setprop sys.powerctl "reboot"
Click to expand...
Click to collapse
Thanks，I tried it last night，It does not work : (
I think Huawei’s program entry is not here
BTW，i use the APP "Tasker"，my device can automatically shut down when the usb line is unplugged
hisoka_simp said:
Hey I recommend you to also try this code which worked for another device I had, hope it works
on charger
setprop ro.bootmode "normal"
setprop sys.powerctl "reboot"
Click to expand...
Click to collapse
I think i did it
in the "init.charger.rc"
on charger
chmod 0440 /sys/class/hw_power/battery/isc
chown system system /sys/class/hw_power/battery/isc
trigger cust_parse_action
class_start charger
wait /dev/block/bootdevice/by-name/oeminfo
start oeminfo_nvm
start teecd
change to
on charger
chmod 0440 /sys/class/hw_power/battery/isc
chown system system /sys/class/hw_power/battery/isc
trigger cust_parse_action
class_start charger
setprop ro.bootmode "normal"
setprop sys.powerctl "reboot"
wait /dev/block/bootdevice/by-name/oeminfo
start oeminfo_nvm
start teecd
the new problem is coming
when i flash the repacked into my device，i can't enter developer options
I tried not to make any changes, just package boot.img with the unpacked file, the same situation
but i flash the boot.img from my boot partition，everything is ok
You
bearllm said:
I think i did it
in the "init.charger.rc"
on charger
chmod 0440 /sys/class/hw_power/battery/isc
chown system system /sys/class/hw_power/battery/isc
trigger cust_parse_action
class_start charger
wait /dev/block/bootdevice/by-name/oeminfo
start oeminfo_nvm
start teecd
change to
on charger
chmod 0440 /sys/class/hw_power/battery/isc
chown system system /sys/class/hw_power/battery/isc
trigger cust_parse_action
class_start charger
setprop ro.bootmode "normal"
setprop sys.powerctl "reboot"
wait /dev/block/bootdevice/by-name/oeminfo
start oeminfo_nvm
start teecd
the new problem is coming
when i flash the repacked into my device，i can't enter developer options
I tried not to make any changes, just package boot.img with the unpacked file, the same situation
but i flash the boot.img from my boot partition，everything is ok
Click to expand...
Click to collapse
I removed the whole code in the on charger block and pasted just mine so in the block is ONLY those 2 commands.
This maybe results in an error bc charger class is started but not properly shutdown.
Another error could be the file, idk if there is a global init.rc in your boot.img if yes then search in there for on charger bc the global init.rc is called at first and only after that the others so maybe look if there is an on charger block in the unpacked boot img in the init.rc
But I don't know why you can't access the developer options anymore, it would help me to do if you explain a bit more detailed what's going on when you try to open them
hisoka_simp said:
You
I removed the whole code in the on charger block and pasted just mine so in the block is ONLY those 2 commands.
This maybe results in an error bc charger class is started but not properly shutdown.
Another error could be the file, idk if there is a global init.rc in your boot.img if yes then search in there for on charger bc the global init.rc is called at first and only after that the others so maybe look if there is an on charger block in the unpacked boot img in the init.rc
But I don't know why you can't access the developer options anymore, it would help me to do if you explain a bit more detailed what's going on when you try to open them
Click to expand...
Click to collapse
ok
this is my test
step1
I extracted boot.img from the boot partition.
step2
unpack boot.img to the folder “unpacked_img”
step3
repacked the folder “unpacked_img” to the RepackBoot.img (Did not change any files in the folder, just repacked)
step4
flah the RepackBoot.img to the boot partition
i can't access the developer options anymore
but i flash the boot.img(step1) to the boot partition
i can access the developer options again
think you so much
bearllm said:
ok
this is my test
step1
I extracted boot.img from the boot partition.
step2
unpack boot.img to the folder “unpacked_img”
step3
repacked the folder “unpacked_img” to the RepackBoot.img (Did not change any files in the folder, just repacked)
step4
flah the RepackBoot.img to the boot partition
i can't access the developer options anymore
but i flash the boot.img(step1) to the boot partition
i can access the developer options again
think you so much
Click to expand...
Click to collapse
bearllm said:
ok
this is my test
step1
I extracted boot.img from the boot partition.
step2
unpack boot.img to the folder “unpacked_img”
step3
repacked the folder “unpacked_img” to the RepackBoot.img (Did not change any files in the folder, just repacked)
step4
flah the RepackBoot.img to the boot partition
i can't access the developer options anymore
but i flash the boot.img(step1) to the boot partition
i can access the developer options again
think you so much
Click to expand...
Click to collapse
Did you try to unlock developer options again? (Tapping build number 10x)
hisoka_simp said:
Did you try to unlock developer options again? (Tapping build number 10x)
Click to expand...
Click to collapse
I have tried, failed~~~~~~~
and i reset pad to factory settings, do not open the developer options first，flash the RepackBoot.img
unlock developer options after reboot
the situation is still the samet,can't access the developer options
my heart is broken，hahaha
bearllm said:
I have tried, failed~~~~~~~
and i reset pad to factory settings, do not open the developer options first，flash the RepackBoot.img
unlock developer options after reboot
the situation is still the samet,can't access the developer options
my heart is broken，hahaha
Click to expand...
Click to collapse
What do you mean exactly you can't access? Is the toast not showing which says you unlocked developer options or do you try to open them and settings crash then?
hisoka_simp said:
What do you mean exactly you can't access? Is the toast not showing which says you unlocked developer options or do you try to open them and settings crash then?
Click to expand...
Click to collapse
i can unlocked developer options ,but when i click the "developer options ",the program crashes
hello.
one year ago, i can modify my xiaomi mix2s with xiaomi.eu rom. and the phone boots when the charger is connected. The modification i make power the phone, apears the chargin animation and after a second, the phone reboots and launch android.
The problem is, i must factory reset the phone and now, this not works, and i must do the trick again. but i dont remember what i did!!!!
somebody know how to modify the phone to boot when charger is connected??
i am in no way responsible if you brick, break or just plain blow up your device. it's your device and your responsibility. if you blame me i am gonna die laughing!
Disclaimer! the exploits in the rar may be flagged as a virus by your virus software. just add an exception for them! they are not a virus
T-Mobile/MetroPCS Root, TWRP and Deodexed Stock Roms
Cannot Stress this Enuff but Read this Entire Post, when done read it again, and finally read it once more for good measure
ok all. this is dirtycow exploit for the t-mobile k428 - works on the 10g firmware(works for the metropcs ms428 as well - Must have 10c kdz flashed first). the exploit method is almost the same as the v20
i have personally done this multiple times on my t-mobile k10 without issues to make sure it is 100% working
all the needed files you need are in this rar. just extract it to the root of your C drive Download Me
this requires an unlocked bootloader and on the t-mo variant it's very easy to do. check this forum. you'll find instructions on how to do it
Now lets get started!!
copy the supersu file to your sdcard
open a command prompt window.
now copy and paste each line except the lines surrounded by "< >"
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process32 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb push twrp-3.1.0-0.img /sdcard/twrp.img
adb shell
cd /data/local/tmp
chmod 0777 *
./dirtycow /system/bin/applypatch recowvery-applypatch
"<Note! wait for to finish>"
./dirtycow /system/bin/app_process32 recowvery-app_process32
"<Note! wait for to finish, it should appear to crash, however
the crash will not happen, you have to force the crash.
to do this wait for the exploit to finish. now press and hold
the power button until you see the t-mo logo screen and hear
the jingle. now it's crashed and you can continue onto the next
step>"
exit
adb logcat -s recowvery
"<wait for it to tell you it was successful - Then Press>"
"[CTRL+C]"
adb shell reboot recovery
"<wait for phone to boot up again, your recovery will be reflashed to stock>"
adb shell
getenforce
"<it should say Permissive>"
cd /data/local/tmp
./dirtycow /system/bin/run-as recowvery-run-as
run-as exec ./recowvery-applypatch boot
"<wait for it to flash your boot image this time>"
run-as su
run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
"<wait for it to complete>"
reboot recovery
"<once in twrp do the following>"
click install
select supersu 2.79-sr3.zip
reboot
setup your phone and enjoy
thats it. enjoy root!
Stock Deodexed Roms
Features:
Deodexed
Debloated(if thats what you want to call it) i've removed what i don't want so
Magisk v12.0 with magisk manager 4.3.0
Note! (make sure to enable hide magisk in magisk manager settings) - pass's safetynet check - android pay will work along with pokemon go and any other apps that look for root
Busybox 1.26.2 installed by default
dolby atmos 6.5
Viper4Android 2.5.0.5
Includes a custom app for a reboot menu that ties into the actual power button
As always to install either rom you'll want to wipe system, data, dalvik and cache(this is normal for any rom)
T-Mobile Rom
T-Mobile K10 K428sg 10h rom - Weather Widget has been removed due to deodexing issues. PLZ use an Alternate Weather Widget
K428sg10h Removed Files
MetroPCS Rom
MetroPCS K10 ms428 10h rom - Weather Widget has been removed due to deodexing issues. PLZ use an Alternate Weather Widget
MetroPCS Removed Files
for anyone interested you can freely use these rom as a starting point base for a custom rom.
Thanks to @pvineeth97 - for working twrp, @Chainfire - for supersu, @topjohnwu - for magisk, and everyone else i forgot to mention. sorry guys i'm tired!
reserved 1
OvrDriVE said:
reserved 1
Click to expand...
Click to collapse
I just didn't remember that dirtycow could be used to root MetroPCS 428! Thanks for the guide
actually the metropcs twrp you did works like a charm on the t-mo 428. ty for that btw.
i wasn't sure if this worked for metropcs or not but since you say it does i'll mention it as well
OvrDriVE said:
actually the metropcs twrp you did works like a charm on the t-mo 428. ty for that btw.
i wasn't sure if this worked for metropcs or not but since you say it does i'll mention it as well
Click to expand...
Click to collapse
I don't have a MetroPCS 428 phone but I compiled TWRP for it. I happy it works for you guys
---------- Post added at 03:14 PM ---------- Previous post was at 02:47 PM ----------
@OvrDriVE
Edit the guide properly whenever you are free.
Can you contact me on hangouts: [email protected].
On the very first command I'm already facing issues:
Code:
adb push dirtycow /data/local/tmp
adb: error: cannot stat 'dirtycow': No such file or directory
GuyInDogSuit said:
On the very first command I'm already facing issues:
Code:
adb push dirtycow /data/local/tmp
adb: error: cannot stat 'dirtycow': No such file or directory
Click to expand...
Click to collapse
make sure your running cmd from the adb dir. also you need to make sure usb debugging is enabled in dev options along with oem unlock
OvrDriVE said:
make sure your running cmd from the adb dir. also you need to make sure usb debugging is enabled in dev options along with oem unlock
Click to expand...
Click to collapse
I am running it from the adb directory. And USB debugging and OEM unlock are enabled.
GuyInDogSuit said:
I am running it from the adb directory. And USB debugging and OEM unlock are enabled.
Click to expand...
Click to collapse
then it should work as the file is in that folder if you grabbed my zip at the top of OP
OvrDriVE said:
then it should work as the file is in that folder if you grabbed my zip at the top of OP
Click to expand...
Click to collapse
I got it! The "dirtycow" file was being removed by ESET. You should add a disclaimer in the OP about it possibly being flagged by antivirus software.
GuyInDogSuit said:
I got it! The "dirtycow" file was being removed by ESET. You should add a disclaimer in the OP about it possibly being flagged by antivirus software.
Click to expand...
Click to collapse
yeah it's a false positive. anyway disclaimer added.
OK, now I'm stuck. The part where I'm supposed to hold the power button? It doesn't reboot. It just brings up the power menu and stays there.
GuyInDogSuit said:
OK, now I'm stuck. The part where I'm supposed to hold the power button? It doesn't reboot. It just brings up the power menu and stays there.
Click to expand...
Click to collapse
redo the exploit line right before your supposed to hold the power button. wait for it to finish then hold the power button to crash the phone
It takes about 2-3 minutes for the "./dirtycow /system/bin/app_process32 recowvery-app_process32" command to finish. It doesn't appear to crash. I'm still waiting for it to happen.
GuyInDogSuit said:
It takes about 2-3 minutes for the "./dirtycow /system/bin/app_process32 recowvery-app_process32" command to finish. It doesn't appear to crash. I'm still waiting for it to happen.
Click to expand...
Click to collapse
ok, make sure your screen is on and doesn't shutoff. that may help. the crash that happens on the v20 doesn't happen on the k10 unless ypou hold the power button to force it
and you'll know you crashed it because the white t-mo logo screen will pop up and you'll hear part of the t-mo jingle and then phone will appear to be froze
OvrDriVE said:
ok, make sure your screen is on and doesn't shutoff. that may help. the crash that happens on the v20 doesn't happen on the k10 unless ypou hold the power button to force it
and you'll know you crashed it because the white t-mo logo screen will pop up and you'll hear part of the t-mo jingle and then phone will appear to be froze
Click to expand...
Click to collapse
I set the screen to stay on. I'm actually using an MS428, the MetroPCS variant. Nothing happening, still. I've run the command four times now.
---------- Post added at 09:53 AM ---------- Previous post was at 09:47 AM ----------
I think I'll need to downgrade. I let the phone update once since I got it. And there's a new 57.1 MB update today.
GuyInDogSuit said:
I set the screen to stay on. I'm actually using an MS428, the MetroPCS variant. Nothing happening, still. I've run the command four times now.
---------- Post added at 09:53 AM ---------- Previous post was at 09:47 AM ----------
I think I'll need to downgrade. I let the phone update once since I got it. And there's a new 57.1 MB update today.
Click to expand...
Click to collapse
you may need to. i did this on a k428 t-mo version with 10g and i havn't tryed on 10h yet but i gaurentee it works on t-mo. was told it works on metropcs however they could have been wrong on that.
Once rooted, will I lose root if I update? I kinda figure I will.
GuyInDogSuit said:
Once rooted, will I lose root if I update? I kinda figure I will.
Click to expand...
Click to collapse
it actually shouldn't update because of the modified recovery. although it may still complain about there being an update you can just ignore it
OvrDriVE said:
it actually shouldn't update because of the modified recovery. although it may still complain about there being an update you can just ignore it
Click to expand...
Click to collapse
Oh, right, the recovery. Yeah. Alright.
---------- Post added at 10:46 AM ---------- Previous post was at 10:10 AM ----------
I'm on 10g already and it's not working. I tried downgrading, which said it completed, but I'm still on the same version. WTF. And this still isn't working.
I'm not responsible for damage, loss, etc cause by this script. This script lacks of situation and error management. Please read the script and understand what it does. Please backup your /system/priv-app/MiuiSystemUI/MiuiSystemUI.apk
Tested on xiaomi.eu 11.0.4.0. Should work on any miui11, maybe even other devices with notch.
This scripts moves the system clock in the notch-enabled status bar to the right side of the notch. It does this by pulling the apk, decompiling it in tmp folder and recompiling it. I made this because I got annoyed by the fact that there is tons of space on the right side of the notch while there is no space for notification icons on the left side.
SafetyNet should pass. Reboot after execution to ensure root is read-only.
Requirements:
MIUI 11
Magisk v20+
apktool < v2.6.0 (-c option is required)
adb
a decent linux install
The patch.patch file on the same directory of where you run it. If you're dev you can edit this file to make your custom patch.
PS: xda doesn't let me upload sh, the script is script.txt, rename it into script.sh, make it executable and execute it
EDIT: Will bootloop on Android 10 MIUI 11!
Thanks, it's very useful.
But can you please explain how to run the script?
---------- Post added at 11:00 AM ---------- Previous post was at 11:00 AM ----------
Thanks, it's very useful.
But can you please explain how to run the script?
he script is script.txt, rename it into script.sh, make it executable and execute it
DP FH said:
he script is script.txt, rename it into script.sh, make it executable and execute it
Click to expand...
Click to collapse
I'd rename it. but how to execute it? dublle click on the file or how?
yamabokra1 said:
I'd rename it. but how to execute it? dublle click on the file or how?
Click to expand...
Click to collapse
Via terminal
DP FH said:
Via terminal
Click to expand...
Click to collapse
It seems that you don't have time to explain. thanks anyway
yamabokra1 said:
It seems that you don't have time to explain. thanks anyway
Click to expand...
Click to collapse
Mate, if you don't know how to execute scripts from terminal you probably shouldn't mess around with them.
JaSomTy said:
Mate, if you don't know how to execute scripts from terminal you probably shouldn't mess around with them.
Click to expand...
Click to collapse
Please, spend 10 second to tell here if it worked, so we know on which systems it works
DP FH said:
Please, spend 10 second to tell here if it worked, so we know on which systems it works
Click to expand...
Click to collapse
I'm not getting it right.
Can you assist?
https://ibb.co/N7GXpcS
https://ibb.co/XDMZSv9
I run it, but it says apktool not found?
Please check the link for the picture. Do i have the correct APK tool there? I see you said < 2.6.0, but the highest i can find is 2.4.1
Dude... Running Windows binaries from Linux ain't gonna work. Just install everything from apt.
V2.6.0 does not yet exist, I wrote it for the time being
Rooted phone?
Maybe an obvious question, but does the phone need to be rooted to allow that manipulation?
duplicate message lol
josephlegrand33 said:
Maybe an obvious question, but does the phone need to be rooted to allow that manipulation?
Click to expand...
Click to collapse
Requirements: Magisk v20+ so yes. You can unroot after a successful installation, but if the mod goes away (ota update) you need root to reinstall it
Hey, I think I set up everything right, but when I run it I get
Input file (MiuiSystemUI.apk) was not found or was not readable.
Script: modding
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- /tmp/miuis/res/layout/drip_status_bar_contents_container.xml 2020-01-04 20:09:39.224390176 +0100
|+++ /tmp/miuis/res/layout/drip_status_bar_contents_container.new 2020-01-04 20:09:56.504390102 +0100
--------------------------
File to patch:
Am I missing something?
I'm attaching the output
Thx for your work
I also think I did it right, but get "MiuiSystemUI.apk was not found or was not readable".
(Redmi Note 8 Pro, MIUI Global 11.0.3)
I've also tried to move that stupid clock with Substratum, but overlays seem not affecting system stuff in statusbar and, sadly, CustoMIUIzer doesn't include this setting.
Hi, sorry if I didn't read it straight away. That means MiuiSystemUI.apk couldn't be read. Do you have correct permissions to write files in /tmp?
Try to execute the commands in the script manually. for example, adb pull /system/priv-app/MiuiSystemUI/MiuiSystemUI.apk /tmp/
Can you manage to read the file? Do you see it in /tmp?
If it is, apktool d -p /tmp -o /tmp/miuis/ -s MiuiSystemUI.apk
should work right away
Tancredus said:
I'm attaching the output
Click to expand...
Click to collapse
I've read the log, the apktool decompilation gets straight away skipped for some reason. I'm using 2.4.1 as well.
What happens when you run apktool d -p /tmp -o /tmp/miuis/ -s MiuiSystemUI.apk
manually?
Oh right! My fault. replace
apktool d -p /tmp -o /tmp/miuis/ -s MiuiSystemUI.apk
with
apktool d -p /tmp -o /tmp/miuis/ -s /tmp/MiuiSystemUI.apk
And try again.
Also, don't try using it on android 10. will bootloop.
Do you know why it will bootlop in android 10 miui 11?
Because it's only a change on one line of xml... Maybe it's a invalid positioning, let me see it...
I tested this on my Dasaita px6 mtce head unit once I installed Android 10
(thanks @Diavol for the tip)
I know that there are other ways to do this, but this is how I accomplished it.
****************DO THIS AT YOUR OWN RISK***********************************
1- On Head Unit: install a terminal emulator and run the three following commands pressing enter each time. (device will reboot). This will open ADB witj root permissions on port 5555
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot
*******************************************************************************
2- Uzip Su-Magisk folder and place the files on the root directory of your PC ( C:/ )
Open command prompt window on your PC with administrative privileges and enter one line at a time,,,,,, if you get stuck at "adb shell /system/bin/su --daemon", repeat the process on a new command prompt
window. When that is finished install Magisk V 20.4 (20400), after it gets installed it will search for updates and will say that the app is not installed, press on install, a window will pop up, choose to install it as a "Direct Install (Recommended)" when finished, press the yellow reboot button.
cd c:/
adb connect (enter here your ip address number, for example 10.0.0.2)
adb root
adb connect (enter here your ip address number, for example 10.0.0.2)
adb remount
adb shell setenforce 0
adb push su /system/xbin/su
adb push su /system/bin/su
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/xbin/su
adb shell /system/bin/su --install
adb shell /system/bin/su --daemon
adb push rooting.rc /system/etc/init/rooting.rc
***************************************************************************
***************************************************************************
Finally, after months of garbage "help me how do I do (the same boring question multiple new members signed up to XDA for - without reading the forums a thoughtful contributing post! Brilliant!
marchnz said:
Finally, after months of garbage "help me how do I do (the same boring question multiple new members signed up to XDA for - without reading the forums a thoughtful contributing post! Brilliant!
Click to expand...
Click to collapse
Yeah, that's how it sometimes goes, I am still testing this stuff.
Для РХ5 тоже подойдет??
Suitable for PX5 too ??
---------- Post added at 09:03 AM ---------- Previous post was at 08:57 AM ----------
I read different forums, and there seems to be a way to make boot.img root (also through Magisk) and flash it into the radio
AndreySanich said:
Для РХ5 тоже подойдет??
Suitable for PX5 too ??
---------- Post added at 09:03 AM ---------- Previous post was at 08:57 AM ----------
I read different forums, and there seems to be a way to make boot.img root (also through Magisk) and flash it into the radio
Click to expand...
Click to collapse
Yes I am aware of that, but why? when I install Magisk it patches directly the stock boot image, or am I wrong? please let me know.
Al Ferro said:
Yeah, that's how it sometimes goes, I am still testing this stuff.
Click to expand...
Click to collapse
I mean, well done, great post!
I wonder how that's gonna work?
Rockchip boot.img or patches are not supported by Magisk.
There must be more experience reports, someone might get a boot loop.
sorry, maybe for the translation I missed something, how do I connect pc and tablet ?, ip address to put I guess is that of the tablet ?.
thanks for your patience.
Have anyone tried to root with this method ?
jamal2367 said:
Have anyone tried to root with this method ?
Click to expand...
Click to collapse
Yeah, me. I' ve done it many ,many times because I am testing stuff, no boot loops or anything so far.:good::laugh:
marcanpaolo said:
sorry, maybe for the translation I missed something, how do I connect pc and tablet ?, ip address to put I guess is that of the tablet ?.
thanks for your patience.
Click to expand...
Click to collapse
Yes, your radio unit's ip address .
Al Ferro said:
Yeah, me. I' ve done it many ,many times because I am testing stuff, no boot loops or anything so far.:good::laugh:
Click to expand...
Click to collapse
I have a PX5.
The problem is that I do not have a test radio where I can test it all the time.
It takes a long time to set up the radio back the way it was before.
The problem is actually that Magisk does not support rockchip ramdisk.
I have tried it several times in the past and it always resulted in boot loops or black screens.
Show this issue on github:
https://github.com/topjohnwu/Magisk/issues/755
Maybe there are differences from radio to radio.
With you it works and with others it doesn't, that's the question.
jamal2367 said:
I have a PX5.
The problem is that I do not have a test radio where I can test it all the time.
It takes a long time to set up the radio back the way it was before.
The problem is actually that Magisk does not support rockchip ramdisk.
I have tried it several times in the past and it always resulted in boot loops or black screens.
Show this issue on github:
https://github.com/topjohnwu/Magisk/issues/755
Maybe there are differences from radio to radio.
With you it works and with others it doesn't, that's the question.
Click to expand...
Click to collapse
It Works wonderful with my Dasaita head unit.
One cannot expect correct answers here, can one?
Grow up and stop acting like a child
jamal2367 said:
One cannot expect correct answers here, can one?
Grow up and stop acting like a child
Click to expand...
Click to collapse
Hey, I am just saying that I have not problems at all running this stuff on my radio unit, I don't know what brand of radio unit you have, I see on the market a lot of cheap stuff that I personally avoid. This guide is for every one that feels confident to try it out, I am not forcing anyone to do it, I can tell you that I am happy that it works for me, let's keep on learning good stuff.:good:
jamal2367 said:
One cannot expect correct answers here, can one?
Grow up and stop acting like a child
Click to expand...
Click to collapse
without testing, you won't get a result. I already sent you a private message about the build test. Yes, we have different CPUs, but if you want results, you must sacrifice time and settings.
Ok i have test it and it´s working without any problems.
Magisk + Magisk Module!
jamal2367 said:
One cannot expect correct answers here, can one?
Grow up and stop acting like a child
Click to expand...
Click to collapse
jamal2367 said:
Ok i have test it and it´s working without any problems.
Magisk + Magisk Module!
Click to expand...
Click to collapse
which method worked?
Diavol said:
which method worked?
Click to expand...
Click to collapse
From this thread. :good:
jamal2367 said:
From this thread. :good:
Click to expand...
Click to collapse
with the stock boot?