For the developer device, what is the recommended way to add new jar files to
/system/frameworks
and .so files to
/system/lib
So far .. tried building the new system img from the source.
did
Code:
fastboot flash system system.img
fastboot reboot
The device hangs .. shows the static android robo icon.
Copying these files to their appropriate directories works well on emulator though.
dan.raaka said:
For the developer device, what is the recommended way to add new jar files to
/system/frameworks
and .so files to
/system/lib
So far .. tried building the new system img from the source.
did
Code:
fastboot flash system system.img
fastboot reboot
The device hangs .. shows the static android robo icon.
Copying these files to their appropriate directories works well on emulator though.
Click to expand...
Click to collapse
Modify an existing update.zip and resign it with a test key. That should work.
I am currently using the ADP Stock image from here. Is there a way to extract the keys from the device ? or Does this use the the keys provided in AndroidMod.Zip.
Also the ADP 1 Stock Image has system.tar !! Does this mean all the included files are signed ?
dan.raaka said:
or Does this use the the keys provided in AndroidMod.Zip.
Click to expand...
Click to collapse
Yes, they are signed with the test keys
nice work
nice work bro keep it up
Thread closed.
I may try to help. I'm afraid I won't be able to provide you a pure stock ROM because I will need at least to root and install Droid2 Bootstrapper to get access to nandroid backups. Also my firmware is based on Brazil Retail SBF (with english language available). Is that good for you? Do you have a place where I can upload it? Also, do you need the whole nandroid backup or just the system.img?
I'm actually painfully uploading system.img from a stock-rom nandroid.
I guess you don't care about data.img and cache.img...
Boot.img is not saved in milestone2/droid2 nandroid, is it mandatory ?
Very nice man !!! ;-)
momus87 said:
I'm actually painfully uploading system.img from a stock-rom nandroid.
I guess you don't care about data.img and cache.img...
Boot.img is not saved in milestone2/droid2 nandroid, is it mandatory ?
Click to expand...
Click to collapse
I don't think so as we won't be able to change it anyway. Even so, if you need boot.img, just open adb shell, get root, and type: cat /dev/block/boot > /sdcard/boot.img
help needed?
do you need more nandroids? i'm not a pro in this field, but i would like to help you.
so, what files do you need? just the *.img, clockwork creates by using the "backup"-option?
r2beta0 said:
I don't think so as we won't be able to change it anyway. Even so, if you need boot.img, just open adb shell, get root, and type: cat /dev/block/boot > /sdcard/boot.img
Click to expand...
Click to collapse
It isn't saved because the phone has a locked /boot partition. I don't need it since I'm not going to modify the /boot partition.
Status update:
Downloading Liberty DX & D2.
Downloading AOSP 2.2 image from Android sdk
Downloading Ubuntu 10.10
next:
Install Ubuntu & Setup SDK & stuff
Comparing which files are different between DX & D2
Comparing which files are different between AOSP & D2 (I'll use D2 as base)
Replacing D2 drivers with M2 ones
Uploading for test.
Here is the link to download system.img from french sbf for milestone2 :
http://www.4shared.com/file/7az7qWj8/system.html
momus87 said:
Here is the link to download system.img from french sbf for milestone2 :
http://www.4shared.com/file/7az7qWj8/system.html
Click to expand...
Click to collapse
Thanks, but I have enough files already, I'll start working rigt away
Status update:
Done downloading, backing up ROM files for access in Ubuntu.
Installing Ubuntu & Setup SDK & stuff
Next:
Comparing which files are different between DX & D2
Comparing which files are different between AOSP & D2 (I'll use D2 as base)
Replacing D2 drivers with M2 ones
Uploading for test.
Could anybody share me a layout of the / partition? In easy words:
1. Power up your phone and connect it.
2. Open up a command prompt.
3. Type in: adb shell ls / > text.txt
4. Upload text.txt to xda-dev's
preinstall
tmp
pds
cdrom
config
cache
sdcard
acct
mnt
d
etc
system
sys
sbin
proc
init_prep_keypad.sh
init.rc
init.mapphone_umts.rc
init.mapphone_cdma.rc
init.goldfish.rc
init
default.prop
data
root
dev
hahaaha weird for some reason there's a CDMA.rc in there.... weird for a GSM handset.
smacky_wolf said:
preinstall
tmp
pds
cdrom
config
cache
sdcard
acct
mnt
d
etc
system
sys
sbin
proc
init_prep_keypad.sh
init.rc
init.mapphone_umts.rc
init.mapphone_cdma.rc
init.goldfish.rc
init
default.prop
data
root
dev
Click to expand...
Click to collapse
Thanks, could you
adb pull /init_prep_keypad.sh
adb pull /init.rc
adb pull /init.mapphone_umts.rc
adb pull /default.prop
and then zip & upload them for me?
Found some way of hijacking init.rc, making CM possible. It's hard though.
that should do it...
man, lucky i know linux mostly. i've been doing this via terminal on handset.
smacky_wolf said:
that should do it...
man, lucky i know linux mostly. i've been doing this via terminal on handset.
Click to expand...
Click to collapse
Thanks, that really helps
Great job man!
Good luck and success in this ROM !!
look forward!
Great news, I'm making awesome progress. It's just that I'm on windows right now and need some deodexed apks
Stk.apk
WeatherWidget.apk
LatinIME.apk
PhoneConfig.apk
maybe this?
actually nevermind, am pulling the proper files from xUltimate atm
here we go, these are properly deodexed.
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??