Develop Bugs

[How to] Rom cooking

Original post:
Hello,
I am new to android but not to linux. I used to tweak my winmo phone rom.
I have backed up my device with nandroid. I just need some explanations:
- why isn't the radio extracted?
- how can I "extract" does .img files to modify and then rebuild them?
I found some informations of what the .img files contain here: ROM Partitions it should be the same for Hero
I have found some informations on how to push updates to the rom by looking at modaco updates. It seems quite simple to delete/copy files on the hero rom using an update-sript file. I am however curious about the RSA cert and if some files need to be signed.
Any information welcomed.
Regards
Click to expand...
Click to collapse
How to
Extract NAND image files
To extract .img files, I have found unyaffs from http://code.google.com/p/unyaffs/ I have compiled it under ubuntu 64 (attached). Unyaffs works on system.img but on no other .img file
To extract boot.img use attached extract-kernel.pl and extract-ramdisk.pl
# extract-kernel.pl boot.img
# extract-ramdisk.pl boot.img
Should work for recovery.img but haven't tried as custom recovery images on the forum are great.
Rebuild system.img
Seems you just need "to loopback mount an image on your linux box and format it with YAFFS".
But it is useless as because Hero's SPL does not allow flashing system.img directly. You should use an update.zip package for that. (read below)
Rebuild boot.img
After extracting your boot.img using attached extract-*.pl and tweaking it, in same folder run:
# mkbootfs boot.img-ramdisk | gzip > ramdisk-boot
# mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-boot --cmdline "no_console_suspend=1 console=null" -o newBoot.img --base 0x19200000
Creating an update.zip package
Creating an update.zip package is quite easy in fact. For example, to add a (valid) test.apk package to your rom:
- create an empty folder <workdir>
- create folder structure for test.apk (<workdir>/system/app) and copy the test.apk
- create folder structure for update-script (<workdir>/META-INF/com/google/android)
- edit <workdir>/META-INF/com/google/android/update-script
- put in it:
Code:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.1 10
- compress the <workdir> content to zip (not the <workdir> folder itself)
Now you are going to sign the zip file. Download attached testsign.zip and copy it in your <SDK>/tools folder. Extract it here. It should create a sign subfolder with a testsign.jar file in it.
Then, from <workdir> folder, do:
java -classpath <SDK>/tools/sign/testsign.jar" testsign file.zip file-signed.zip
Ok, now your zip file is ready to be deployed using cyanogen recovery image.
To find more command to use in update-script, look at other's.
Modify .apk package
Seems it is easy to uncompress an .apk package (zip) an to modify files in it and then compress it. But after all: you must sign it like update.zip packages.
ODEX files
- What are those Odex files? Answer.
- How to get rid of them?
Odex files depend on framework they are made for. To deodex an odex file use that how to
Then you may create a classes.dex file by executing the smali program on the "out" folder. You then rename it to classes.dex and add it to the .apk.
- How to create them?
Use dexopt-wrapper on device.
Porting an other device's rom
Well, that part is easy
- extract the system.img
- extract boot.img
- replace boot.img-kernel with the one from your stock Hero rom one.
- rebuild boot.img
- build update.zip package (look someone's hero custom rom to see how to do it)
- sign and flash
It should run place and make calls but probably won't have Wifi, BT, trackball support. If you make those work: tell me, but I think we should wait to be able to compile a 2.6.29 kernel to have those.
Tools
Androsign script (linux)
I wrote that androsign script to quick sign zip files. Just put it in your <SDK>/tools folder, then chmod +x. If you have put the tools folder in your PATH, you can call it directly like this:
androsign /dev/folder1/folder2/update.zip (or any zip/apk file)
It will output an update-signed.zip (or app-signed.apk etc) in the same folder than original file was in.
Notes
Note1: thanks
Thanks to every guy that helped me found all that.
Note1: sharing
I searched for hours, so I am more than happy to share it to save someone's time. I am just disappointed than some people here do not have that spirit: I could have use those hours for development instead of research...
Note3: corrections
So, if you found anything incorrect, would like to supply more informations or want to correct my bad english: just PM me.
To find
- how to dump radio from device
- how to build a custom hero kernel (waiting for HTC sources)
To come
How to prepare your own kitchen and useful scripts (linux)

gecka said:
I am new to android but not to linux.
Click to expand...
Click to collapse
Same here. I do lots of tweeking on my linux machine, so i know quite a lot of linux. If there would be anyone to answer those questions by gecka, I might start tweeking the rom (maybe someday cook one up)
Best regards

Hello,
First post edited, but still some ignorances... Please share if you know anything.
Best regards

unpack and pack boot.img and recovery.img
First you need utilities such as mkbootfs and mkbootimg. maybe you can find them online (i can upload them later compiled for linux x86-64) but i suggest you download android source (http://source.android.com) and do a generic make. In this way you have these and other utilities(tools to pack system.img too, but if you haven't an engineering bootloader you can't flash it directly) in /out/host/... (it's better if you add this in your PATH)
To unpack and pack boot and recovery, read here:
http://forum.xda-developers.com/showthread.php?t=443994
or here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
...or...
(I have attached extract-kernel and extract-ramdisk scripts from JF build environment) :
to unpack (boot.img or recovery.img, i'm writing the commands with boot.img):
Code:
extract-kernel boot.img
extract-ramdisk boot.img
at this point you have
boot.img-kernel
boot.img-ramdisk
to repack (boot.img or recovery.img):
For hero you need to specify the base address because it's different (0x19200000). For more information: http://forum.xda-developers.com/showthread.php?t=541522.
Code:
mkbootfs boot.img-ramdisk | gzip > ramdisk-boot
mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-boot --cmdline "no_console_suspend=1 console=null" -o newBoot.img --base 0x19200000
Useful resources for android modding are the dream forums (most of the concepts/hacks works for hero too):
http://forum.xda-developers.com/forumdisplay.php?f=448
(informative thread here: http://forum.xda-developers.com/showthread.php?t=519523)
note: mkbootimg with --base support is in donut and master (or find the patch on gerrit and apply it to cupcake)

First of all, the reason you cant unyaffs anything other than system.img is because they aren't YAFFS images. boot/recovery is kernel+initrd like in any normal linux bootimage scenario (see more below).
Tofind
- how to dump radio from device
Click to expand...
Click to collapse
Haven't gotten into that myself yet, but I know modaco posted an update.zip with radio image included on this very forum. Look for it.
- how to extract NAND images other than system.img
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=443994
- rebuild NAND images such as system.img
Click to expand...
Click to collapse
This isn't hard, just loopback mount an image on your linux box and format it with YAFFS.

Building a custom kernel and recovery binary
HTC hasn't yet released the changes they have made to the hero/dream/magic kernels, 32A board, so you can't just compile a kernel from the AOSP. I haven't tried it yet but this patch might work on hero too:
http://forum.xda-developers.com/showthread.php?t=548061
EDIT: HTC Sources for dream and magic at http://developer.htc.com
For building a custom recovery, it's better if you use cyanogen's recovery code, found in his git : github.com/cyanogen, because it already has menus for nandroid and other tools, but you can use the recovery code from AOSP too (cyanogen's one is a patched version with a lot more features, http://forum.xda-developers.com/showthread.php?t=523558). To make a custom recovery you need to change the recovery binary (because the press event of the hero trackball has a different keycode, 191), the kernel and the init scripts. Actually i don't remember what else I've changed to make cm's recovery working with hero (the recovery that we are actually using here), I'm at work now, but i'll check later and post more details, or you can just unpack the recovery and see the changes .

First post updated.

Nandroid only backs up the partitions in the main storage nand, but radio and spl are flashed to the radio's own nand flash. Whether it's possible to dump it or not I don't know, but honestly, I don't see why you'd want to. Radio images are available through RUU's and I don't think editing would be an easy task

jubeh said:
Nandroid only backs up the partitions in the main storage nand, but radio and spl are flashed to the radio's own nand flash. Whether it's possible to dump it or not I don't know, but honestly, I don't see why you'd want to. Radio images are available through RUU's and I don't think editing would be an easy task
Click to expand...
Click to collapse
Sometimes, new radio images appear on new phones. That is why I am looking on a way to extract it.

very useful thread.

Very nice tutorial, thank you!

could you please specify a bit more on how to clone from android's git and then build the mkbootimg and mkbootfs (just make, right)? I tried and I keep getting a "fatal:server dumped connection" error

Are we able to modify an official ROM (also for hero). Which shows up in RUU as INFOsignature checking... failed. Am I able to change the kernel and make it work?

jubeh said:
could you please specify a bit more on how to clone from android's git and then build the mkbootimg and mkbootfs (just make, right)? I tried and I keep getting a "fatal:server dumped connection" error
Click to expand...
Click to collapse
What command do you use?
In fact i won't be able to explain you better than that page: http://source.android.com/download
Following that how to, you'll be able to sync an android branch You can learn more about git, branches and more here (Repo and Git resources)
The sync is long (2.9Go). Then, to build mkbootimg and mkbootfs, you should do a generic build of android going to source folder and issuing the 'make' command.
All that will be part of my upcoming "How to prepare your own kitchen and useful scripts".
awsy44 said:
Are we able to modify an official ROM (also for hero). Which shows up in RUU as INFOsignature checking... failed. Am I able to change the kernel and make it work?
Click to expand...
Click to collapse
Well, to grep the system from a windows RUU exe file you should launch it and then look in your user temporary folder for a rom.zip file in a {uid} subfolder. It contains the system and boot img files.
You then need to make an update.zip package from them. Have a look to someone's hero custom rom and to it's update-script to see how it is achieved. My 'How to' gives you all you need to understand update.zip packages and to extract system.img.
If you are porting a Hero rom, no need to change the kernel.
Regards

Well, to grep the system from a windows RUU exe file you should launch it and then look in your user temporary folder for a rom.zip file in a {uid} subfolder. It contains the system and boot img files.
You then need to make an update.zip package from them. Have a look to someone's hero custom rom and to it's update-script to see how it is achieved. My 'How to' gives you all you need to understand update.zip packages and to extract system.img.
If you are porting a Hero rom, no need to change the kernel.
Regards
Click to expand...
Click to collapse
Thanks so much for this amazing information, however how do i stop getting hit with the infosignature failed error? is that the kernel or the hboot? it says 12 signature verify error.

Oh, I do have the source and I am running my own donut build on my dream with some of my spice, but the problem I was having was cloning that exact project (mkbootimg) from android.git.kernel.org using git, but when I read what you said, I remembered that when you make the build, it also compiles several tools and i overlooked checking the out folder for it, kind of dumb on my part since I had already pulled the fastboot tool from that build and added it to my own bin, i guess mkbootimg and mkbootfs should be there too, right?

i tried running androsign and got this error
Code:
[email protected]:~/android/dev/sdk/tools$ ./androsign META-INF.zip
Exception in thread "main" java.lang.NoClassDefFoundError: testsign
Failed!
[email protected]:~/android/dev/sdk/tools$

if i use a ROM of one device on an other different device, I think I must build a kernel on my own, is that correct?
but what config should I use? a config from my current running ROM? then I think I must make it suitable for new ROM, what options should I care about?
for example, if I want to run a AOSP 2.01 ROM ( system.img) on a Magic 32A device with SPL 1.76, and now I am running a SenseUI ROM which kernel is 2.6.27, I think I should build a 2.6.29 kernel from the git tree, and ensure it will work with camera/bt/wifi/trackball of my device properly first .
how can I make this step successful?
other hand, the dynamic lib files(.so) with the system.img can be incorrect. so, I may need to build them too for pairing with the kernel I built in previous step. I think applications will work properly because they only care about if the interfaces of kernel and lib is correct. for that, also there some config job (like build.prop, etc) to do, is there a list of all of these jobs? and what values can I refer to? the original ROM (Magic 32A SPL 1.76 working ROM here) ?
am I right? what should i do and what are in those steps? are there some doucments I can read from?

Thanks for the good summary. Just one question, where did testsign.jar come from? I'd like to get the source. Thanks!

JackZero said:
Thanks for the good summary. Just one question, where did testsign.jar come from? I'd like to get the source. Thanks!
Click to expand...
Click to collapse
Read this !
http://www.androiddevelopment.org/tag/apk/
;-)

[Guide] Android Cooking Guide for HD2 [Guide]

heartsurfer008 said:
Well I am desparetly trying to cook a NAND build for my HD2 but there is pretty much less info available for me [a big NOOB in cooking] to try out my luck at cooking..!!!
So I'll appreciate if someone would put some light on it..!!!
PS: - I would appreciate if somebody can provide a detailed info..!!!
Click to expand...
Click to collapse
Finally the tutorial
Make your own Android Build for the HD2 by domineus ​I have always lived by these words- if you give a man a fish, he can eat for a day; but if you teach a man to fish you can eat for a lifetime. Android on the HD2 has always been an interesting thing for me and I know a lot of people that want to create their own builds, but have no idea how. If you ask a build creator or maybe someone in the htc-linux-chat how to get started, there may not be an answer. In fact, some of the perplexing behavior has left me puzzled in several ways - as if how to get an android build is a vaulted secret of knowledge like the holy grail. To be honest, it's not. It's a bit of hard work, a few nods in the right direction, and ultimately it's a community involved project. Just like miui development is a community project spanning actual continents to get this thing on our device every single week! It has led to a lot of questions, in my inbox, of how to begin. For a long time, the answer to the question was not answered until Cass helped me out. I want to do the same and contribute how to get a build of miui (or any android build) to the HTC HD2.
Things you will need
In order to properly start android development, it would be a good idea to make sure you have the following (a lot of it is no duh when you think about it)
A computer running linux
I can't stress that enough. While there is a lot of things you can do in windows, you will need some sort of linux distro in order to get android properly running on your HD2. There are a lot of linux distros you can use; with many using ubuntu as it is the most user friendly. I use Fedora and I am quite happy with the results. It's simple and effective. It gets the job done. Get a distro that you feel can get the job done.
Android SDK - either windows or linux
Android SDK is something that can be freely accessed and downloaded from the following location:
http://developer.android.com/sdk/index.html
It is a developer environment, but probably the most important thing you can use here (for the time being) is logcat. Logcat provides you to visually see the libraries and files working together to get android to work as well as if you run into an issue, it is the first thing you should resort to. For instance, boot reloop? Take a look at your logcat and try again.
A kernel
There are quite a few kernels available for android previously and they are divided into evo kernel or nexus one kernel. Many builders have transitioned to an evo kernel for PPP and a few other nice details but it is totally up to you. I highly recommend hastarin's kernel. For most of the time, it works well. But as you have noted, on MIUI, it hasn't been working as fantastic on other builds.
Donor Files
This is a bit difficult to find because it appears that the files that work best are nexus one builds without CM6.1 modification. So far, only one chef has that and it is tytung's nexus one build. Regardless of whose files you're using (e.g. tytung or darkstone's system which is the preferred choice) you will need a well working android build. You will be pulling several files in order to port.
MIUI itself (well any build honestly just miui is a good example)
This is a given. However, if you download from miui.com you will probably have an untranslated rom with odex files. That's bad. And in Chinese! It would be a good idea to browse the English forum for a deodexed rom with appropriate english translation (apps and frameworks)
-If pulling files from windows, you will need this
system extractor
http://uranus.chrysocome.net/linux/explore2fs-old.htm
I use that if I download in windows. It's relatively straight forward and it allows you to pull the files you need from the system.ext2 you're using and copying them to folders necessary.
build.prop
This you will need. You can find one here:
http://www.multiupload.com/B59IU3S6XY
Patience
Probably the most important thing. One thing I have noticed is you need patience to make it through. Sometimes, your build works, sometimes it doesn't. And it is difficult to still keep going. But gotta pull it all in and keep trying...it does pay off.
Okay so you have your files, a nice linux distribution, your build you want to port (MIUI preferrably) and you're ready to go. Now it's time to begin the process!
Step One - The Setup
I usually grab my files in windows before transitioning to my linux distro to finish the process. If you using windows 7 and you are using explore2fs, you will definitely have to right click on the exe and make it compatible by selecting compatible with windows vista. The file should also need to be run by administrator. If you don't know how to do that you can google compatibility in windows 7.
First thing is first. Create a new folder, you can call it donor_files if you want because name is arbitrary. The most important thing is to just name it. Within that folder, create a new folder called system. Enter the system directory and create a new folder called etc. Within etc, select Once that is done, create a new folder within etc called firmware. Once completed, return back to the system folder, create the folder called lib. In the lib folder, create a new folder called hw. So your folder should look like this:
Folder Name
-system
--etc
---firmware
--lib
---hw
So far so good? Excellent. Now, if you're in windows you will need to do a few things. Extract the system.ext2 of your donor build and place it somewhere you will remember (like your desktop). Now open up explore2fs, select file, and open image file. Under files of type (drop down), select all files and navigate to your system.ext2 file. You should now see the ext loaded on the left side of the program's workspace. Located is a very small + that allows you to view all directories in your ext2 file. Click that.
You will see several system folders on the left and files on the root. Since you haven't selected a specific folder, in the right hand view, you should see the file build.prop. If you did select a folder (like app) you will see some files. And that's okay too. Get a feel of the program.
Now you will do a test file pull. On the left hand side, select the folder etc. On the right window, you will see several files. We want AudioBTID.csv. Once you see the file, right click on AudioBTID.csv and select export file. Navigate to the donor file folder (or whatever you named it) and place the file in system/etc of that folder. Congratulations you just pulled your first file! But you will need a lot more files. Within the same directory, pull gps.conf, hosts, media_profiles.xml and the ppp folder. Now, navigate to firmware and pull the following files:
BCM4329B1_002.002.023.0360.0362.hcd default_france.acdb htcleo.acdb
BCM4329B1_002.002.023.0436.0439.hcd default_nel.acdb yamato_pfp.fw
bcm4329.hcd fw_bcm4329_apsta.bin yamato_pm4.fw
default.acdb fw_bcm4329.bin
Ideally you should not be able to find htcleo.acdb. You can find it here
http://gitorious.org/xdandroid_leo/q...eo/htcleo.acdb
Now in explore2fs, go to the lib directory and pull these files and place them in your lib directory:
libcamera.so
libcamera_client.so
libcameraservice.so
libhtc_ril_wrapper.so
libmm-omxcore.so
liboemcamera.so
libomx_aacdec_sharedlibrary.so
libomx_amrdec_sharedlibrary.so
libomx_amrenc_sharedlibrary.so
libomx_avcdec_sharedlibrary.so
libomx_m4vdec_sharedlibrary.so
libomx_mp3dec_sharedlibrary.so
libomx_sharedlibrary.so
libomx_wmadec_sharedlibrary.so
libomx_wmvdec_sharedlibrary.so
libOmxCore.so
libOmxVdec.so
libOmxVidEnc.so
libqcomm_omx.so
libstagefright_omx.so
Once those files are pulled, navigate to the hw folder of the system and pull the following files:
sensors.htcleo.so
lights.htcleo.so
Once those files are pulled, you can save your donor files to a flash drive and then boot into your linux distro. Login to superuser in terminal. For fedora, the proper method involves typing in su --login and entering your password you set up. Minimize your terminal window.
Extract the miui (or any other build) to your desktop (the focus is the system folder). Ensure the rom is deodexed and in your own language (if its miui, you will have to apply the proper language translations). Now copy the files you pulled from your donor build and apply it to the appropriate folders (usually a copy and a paste-literally). In this instance there will be duplicate files, overwrite them. That's the point! Do not forget the build.prop file I linked to earlier. You should add that to system folder.
So the files are copied, the next step is to restore the minimized terminal window (the one that is logged in as root). cd to where your system is located (not to the system folder itself). Now you will have to enter the following commands in terminal
chmod -R 777 system/etc
chmod 755 system/bin/*
chmod 755 system/xbin/*
rm system/etc/firmware/default*acdb (if you have sound in call issues)
touch system/etc/ppp/active (If you have latest wrapper and need ppp)
chown root:2000 system/bin/pppd
chmod 4755 system/bin/pppd
chown root:root system/xbin/su
chmod 4755 system/xbin/su
chown root:root system/xbin/hci*
chmod 4755 system/xbin/hci*
dd if=/dev/zero of=system.ext2 bs=1048576 count=256
mke2fs -F system.ext2
sudo mount -o loop system.ext2 /mnt2
cp -rp system/* /mnt2
sudo umount /mnt2
A few words on this that I must bold. the /mnt2 directory may not exist. If not, try mnt, that usually works
Once this is done, you will have a nice system.ext2. The only thing you'd need now is a rootfs, a kernel, clrcad.exe and a startup.txt file. Once that is done, you can test your build out.
Any questions
Special thanks to Cass and the htc-linux-chat for the few pointers they gave me.
The guide is by "domineus - http://www.miui-dev.com/" & I take no credit what so ever​
Thanks to "white-energy" for giving us the link..!!!
Hope to have many more Chief's for our HD2, so that we [especially me] can satisfy our hunger to try different builds/ROM's..!!!
Happy Cooking..!!!​
PLEASE PRESS THANKS IF YOU FOUND THIS THREAD USEFUL..!!!​​

+ 1... nobody wants to share information?

I don't know if this help but you can try
http://forum.xda-developers.com/showthread.php?t=897940
These kind of thread pop up once in awhile, but it's going no where, I've never seen well known chef show up in this kind of thread.
knowledge is power, maybe they dont want to share the power

Can anybody out there give us a step by step guide for cooking a NAND ROM for HD2..???

http://www.miui-dev.com/forums/showthread.php?481-Howto-Make-your-own-Android-Build-for-the-HD2
Instead of making a ext image, you should make a yaffs image.. so it can work on Nand

white-energy said:
http://www.miui-dev.com/forums/showthread.php?481-Howto-Make-your-own-Android-Build-for-the-HD2
Instead of making a ext image, you should make a yaffs image.. so it can work on Nand
Click to expand...
Click to collapse
Thank you, please check post 1..!!!

I've been looking for something like this. I want to create my own build for the recovery flasher. I guess the only thing needed would be how to convert from regular nand to recovery.
Thanks bro.

velayo said:
I've been looking for something like this. I want to create my own build for the recovery flasher. I guess the only thing needed would be how to convert from regular nand to recovery.
Thanks bro.
Click to expand...
Click to collapse
I was lookin for the same & credit goes to domineus & white-energy

& "white-energy" comes up with a NAND ROM..!!!
Congrats..!!!

white-energy said:
http://www.miui-dev.com/forums/showthread.php?481-Howto-Make-your-own-Android-Build-for-the-HD2
Instead of making a ext image, you should make a yaffs image.. so it can work on Nand
Click to expand...
Click to collapse
Are you sure its the only difference? Are the nand drivers stored only in the bootimg/initrd and not somewhere in the system.img?
yes or no will do for me thx

Is there a way to edit system.bin files, that comes with the NAND builds. I suppose that is where the ROM is. I want to unpack, edit the included apps and repack. How it is done? How the bin file is done. Google does not give any satisfiable links, did a quick search, though...

i am confused
Which explore 2fs do I download? There are 3 different ones one for binary one for code and optional update source code. I am a noob and tired of not having roms I am happy with. I have windows 7 and xp. I realize this will take time and I am good with it everything thats worth anything takes time.

deckoff said:
Is there a way to edit system.bin files, that comes with the NAND builds. I suppose that is where the ROM is. I want to unpack, edit the included apps and repack. How it is done? How the bin file is done. Google does not give any satisfiable links, did a quick search, though...
Click to expand...
Click to collapse
I think you mean system.img not system.bin
You can extract them with the unyaffs.exe or with the unyaffs command under linux. I have written a guide with attatched utilities here
Additionally birksoffsjunk (seasoned WM guru & chef of ChuckyDroid, ChuckyROM, & Dexter) has made a batch program to make this process easier. It's a work in progress & somethings are still buggy so follow the thread
Between the utility birkoffsjunk made & the tutorial I wrote you should be able to successfully edit & run your own build. Hope this helps.

deckoff said:
Is there a way to edit system.bin files, that comes with the NAND builds. I suppose that is where the ROM is. I want to unpack, edit the included apps and repack. How it is done? How the bin file is done. Google does not give any satisfiable links, did a quick search, though...
Click to expand...
Click to collapse
I think you mean system.img not system.bin
You can extract them with the unyaffs.exe or with the unyaffs command under linux. I have written a guide with attatched utilities here
Additionally birksoffsjunk (seasoned WM guru & chef of ChuckyDroid, ChuckyROM, & Dexter) has made a batch program to make this process easier. It's a work in progress & somethings are still buggy so follow the thread
Between the utility birkoffsjunk made & the tutorial I wrote you should be able to successfully edit & run your own build. Hope this helps.

anyone know how to edit or anything about initrd.gz?

hnamanh said:
anyone know how to edit or anything about initrd.gz?
Click to expand...
Click to collapse
It's an archive that can be decompressed and edited thru linux.

White-Energy use system.bin in his rom
Regarding initr and zimage, there is a guide that you can point me on ?
Thank you
KillaHurtz said:
I think you mean system.img not system.bin
You can extract them with the unyaffs.exe or with the unyaffs command under linux. I have written a guide with attatched utilities here
Additionally birksoffsjunk (seasoned WM guru & chef of ChuckyDroid, ChuckyROM, & Dexter) has made a batch program to make this process easier. It's a work in progress & somethings are still buggy so follow the thread
Between the utility birkoffsjunk made & the tutorial I wrote you should be able to successfully edit & run your own build. Hope this helps.
Click to expand...
Click to collapse

I have only green HTC
Hello
I would like to use Android on my HD2. I was searching and testing many ROMS but I didn´t find any rom which is usable for me. I would like to have a ROM that is without Sense, has Multilanguage support and is on Android 2.2 version.
So I decided that I would make my own.
0) I was reading
HTML:
http://forum.xda-developers.com/showpost.php?p=10291851&postcount=1
and made this procedure.
1)downloaded some ROM from here
2)unpacked this rom in linux with :
Code:
unyaffs system.img
then I got this directories:
Code:
app bin build.prop etc fonts framework lib media usr xbin
3)I downloaded update-cm-6.1.1-N1-signed.zip from CyanogenMod Forum > Downloads > Stable Mod > Nexus One and unpacked. I got : META-INF system boot.img.
4)I copied everything what was described step 0 from directories from step 2 to directory system from step 3
5)I downloaded and copied build.prop from step 0 to system
6) I updated permition like it is described in step 0
7) I created system.img with command : mkyaffs2image . ../system.img
Then I copied this system.img from linux to my windows and put this file in directory in which was different NAND rom. (replaced system.img). After that I flashed my phone and it did not work. Screen was frozen after booting and only green HTC was on display.
Can somebody please help me and give me some advice or some small howto. Does anybody know what can be wrong?
Thank you
Michal Fichtner

I appreciate the guide but damn that is hard to read. It really needs some sort of structure to it, titling proper paragraphs etc.

Hi,
it is possible to combi the dropdown energy widget froom miui and the gingerbread lockscreen into Desire HD Build?
Thats was awesome !
Sorry for my bad english

[MOD] OLD VERSION HULU MOD Automatic Hex Editing Script

OLD VERSION
NEW VERSION FOLLOW LINK BELOW
CLICK HERE for Updated Post and Application
==========OLD INFO BELOW THIS LINE===========================
Im leaving the old info here for reference and in case anyone still wishes to continue to use this version. The new version is beter in every way IMO. But the choice is yours.
===============================
FLASHEX and FLASHMOD script INFO 0.98beta
===============================
This is a new set of scripts I created, Flashex.sh and Flashmod.sh. They take advantage of the same old AND to WIN hex edit. The big difference is Flashex.sh will hex edit the file right on any android device that has busybox installed. I have only been able to test it on my 1 Android device the A100 works perfectly on it. I'm curious if anyone can run it on current rooted ICS since it only requires WRITE to /data, I'm fairly sure it will work just fine, and/or on other devices with flash and a decent enough CPU and memory to watch hulu.
What they do
==========
Flashex.sh will look at /data/data/com.adobe.flashplayer/lib/libflashplayer.so, find its version string, then make a copy of the file and hex edit the copy. It DOESNT require root since it only needs READ access. Flashex.sh only needs to be run once unless you delete the WIN_libflashplayer.so or your Flash Player gets an update.
Flashmod.sh will look for the WIN_libflashplayer.so(hex edited file), check for write access, then copy the file to /data/data/com.adobe.flashplayer/lib/libflashplayer.so.
They can both be run from Terminal, Script Manager, etc. I suggest Setting Flashmod.sh up with a Desktop Icon via Script Manager for an easy way to apply the fix before watching Hulu.
How To Install and Use
======================
1) Create a directory you want to run the script from. I suggest
/mnt/external_sd/FLASHEX but it can be anyplace as long as you
can find, and run the scripts.
2) Download FLASHEX_098b.tar.gz and place it inside the folder
3) cd into the directory
cd /pathtofolder/foldername (note: typically /mnt/external_sd/FLASHEX or /mnt/sdcard/FLASHEX)
4) run the following commands to extract Flashex.sh and Flashmod.sh
gzip -d FLASHEX_098b.tar.gz
tar -xvf FLASHEX_098b.tar.gz
5) Now "sh Flashex.sh" this will READ the original flash file, and hex edit the file.
it will place the edited file inside the default(same folder as script) directory.
The Edited file is named "WIN_libflashplayer.so"
6) Now "su" because Flashmod.sh will need root access to overwrite
/data/data/com.adobe.flashplayer/lib/libflashplayer.so with the edited version
7) Now "sh Flashmod.sh" This script will find WIN_libflashplayer.so and copy it to
/data/data/com.adobe.flashplayer/lib/libflashplayer.so
Note: You will also see "ORIG_libflashplayer.so" that is a backup of the original
that is made before the change. It can be used to restore in the even someone
edits and decides they want to go back, or in case of an unforseen event.
8) Now just make sure your web browser is set to view as "Desktop" and enjoy watching hulu.
That's about it. IF you have run Flashex.sh once you
DON'T need to run it again UNLESS you get a Flash
update, or you delete the WIN_libflashplayer.so.
If your Adobe Flash updates on you just rerun Flashex.sh
to edit the new file. Once edited it will store a copy of
the modded file the scripts home dir.
Then use as Flashmod.sh as normal.
THANKS TO:
===========
All the other people who make GNU open source
programs, the people who figured out how to get hulu to work
by hex editing the libflashplayer.so, and all the great folks
at XDA Developers for providing so much good information,
and for all the hard work to figure out root methods,
and all the other amazing stuff that goes on.
=========================================================
TESTING INFO FOR OTHER DEVICES
This should work on most any android flash in theory but that's UN-tested.
I wrote it to try and look for the same expected pattern for 10.x 11.x and even
12.x(taking a guess). It HAS been tested with Flash 11.x and works
great. It's written in such a way it should be safe to test. Either the Flashex.sh script will give you a properly edited libflashplayer.so or it should be able to tell you it couldnt edit the file. If you end up with an edited file it should be safe to copy over and should work. If you find it DOESN'T work with your version of flash you may contact me and make the .so file available and I will see if I can add support. Eventually I would like this to be universal and easy to use.
ALSO PLEASE!
If it does work for you, especially on other devices or other flash versions please post and let me know. It will help me improve the set of scripts.

Got it working on ICS took me abit of reading on google on how to cd to the directory but alls well that ends well!

/system/bin/sh: cd: /FLASHEX - No such file or directory
1|[email protected]:/mnt/sdcard $ tar -xvf FLASHEX_098b.tar.gz
tar: can't open 'FLASHEX_098b.tar.gz': No such file or directory
1|[email protected]:/mnt/sdcard $ tar -xvf FLASHEX_098b.tar.gz
Flashex.sh
Flashmod.sh
README.txt
[email protected]:/mnt/sdcard $ sh Flashex.sh
======================================================================
Cannot locate /mnt/external_sd/FLASHEX(configured path for Flashex.sh)
The script will attempt to adapt...
Flashex.sh is running from /mnt/sdcard
Flashex.sh has write access to /mnt/sdcard
attempting to use /mnt/sdcard instead...
To avoid this message in the future read the directions better
======================================================================
Detected READ access for /data/data/com.adobe.flashplayer/lib/libflashplayer.so
USING: /data/data/com.adobe.flashplayer/lib/libflashplayer.so
Created /mnt/sdcard/cache Sucessfully...
Found /data/data/com.adobe.flashplayer/lib/libflashplayer.so...Checking
grep: 1[0-2],[0-9]*: No such file or directory
grep: 1[0-2],[0-9]*: No such file or directory
ERROR: Can't figure out what version of Flash this is so it cant be edited.
Currently only tested with v11.1.111.x. It should work with about any version.
I can't test what I dont have. If you send a copy of the libflashplayer.so I will
add it to the Flash versions that are 100% tested and supported.
Contact me(NoSudo) and/or look for updates at forum.xda-developers.com
1|[email protected]:/mnt/sdcard $ su Flashmod.sh
[email protected]:/mnt/sdcard # sh Flashmod.sh
======================================================================
Cannot locate /mnt/external_sd/FLASHEX(configured path for Flashmod.sh)
The script will attempt to adapt...
Flashmod.sh is running from /mnt/sdcard
Flashmod.sh has write access to /mnt/sdcard
attempting to use /mnt/sdcard instead...
To avoid this message in the future read the directions better
======================================================================
ERROR: /mnt/sdcard/WIN_libflashplayer.so NOT FOUND
1|[email protected]:/mnt/sdcard #
Here is my outcome from the script. Searched files and could not find flash hex version.
Running Acer a100 ICS rooted

igwtapc said:
[email protected]:/mnt/sdcard $ sh Flashex.sh
===============================================
Cannot locate /mnt/external_sd/FLASHEX(configured path for Flashex.sh)
The script will attempt to adapt...
Flashex.sh is running from /mnt/sdcard
Flashex.sh has write access to /mnt/sdcard
attempting to use /mnt/sdcard instead...
To avoid this message in the future read the directions better
===============================================
Click to expand...
Click to collapse
You need to create a folder for the script still. It looks like you currently have the scripts located in /mnt/sdcard. You would need to make a folder called FLASHEX still inside /mnt/sdcard/ or /mnt/external_sd/ so the full path would be /mnt/external_sd/FLASHEX or /mnt/sdcard/FLASHEX. If you change the folder name you "may" have to edit the script. I will be releaseing an update soon and I will include a little more testing of that. It was an afterthought and was just added to help make it easier for people. Anyway try this...
First make a folder.
"mkdir /mnt/external_sd/FLASHEX"
Now move the 2 scripts into that folder from the current location
"mv /mnt/sdcard/Flashex.sh /mnt/external_sd/FLASHEX/Flashex.sh"
"mv /mnt/sdcard/Flashex.sh /mnt/external_sd/FLASHEX/Flashmod.sh"
Now you can run them
This will run the script once moved
"sh /mnt/external_sd/FLASHEX/Flashex.sh"
Now you should have WIN_libflashplayer.so inside the FLASHEX folder.
Next run
"su"
"sh /mnt/external_sd/FLASHEX/Flashmod.sh"
I suggest running this via script manager once you decide you like using it. I have mine setup to run at boot. Just be sure and turn off auto update for adobe flashplayer if you run Flashmod.sh at boot. The next version Im thinking about adding the ability to have it run the hex edit each time it detects an updated version. We will see. My main concern with that would be the amount of time the hex edit takes.
Anyway that should get you going on the Hulu. Remember to set your browser to "Desktop" too or it still wont work. I suggest Dolphin HD for a browser.
Let me know if you have any more issues and check back for an updated version in the next few days.

by igwtapc
Created /mnt/sdcard/cache Sucessfully...
Found /data/data/com.adobe.flashplayer/lib/libflashplayer.so...Checking
grep: 1[0-2],[0-9]*: No such file or directory
grep: 1[0-2],[0-9]*: No such file or directory
ERROR: Can't figure out what version of Flash this is so it cant be edited.
Currently only tested with v11.1.111.x. It should work with about any version.
I can't test what I dont have. If you send a copy of the libflashplayer.so I will
add it to the Flash versions that are 100% tested and supported.
Click to expand...
Click to collapse
After looking at your output a little closer. I noticed it did seem to create a cache folder inside your /mnt/sdcard. Can you confirm the existence of a cache folder at /mnt/sdcard/cache? Also did you edit the script or did you change the type of quotes around the strings used by grep? I'm going to do some testing and it would speed things up if I knew those two things.
The above(previous post) directions still apply and should work. However if the script has been edited even just a change from " to ' could break it so be careful.
If your not used to scripting I would not advise you change anything other then the HEXHOME="/mnt/external_sd/FLASHEX" inside the script, and don't change anything left of the = or change the " type. Only edit the directory path/name.

I just tried this and got the same error as above. I did notice that it created the cache folder in the same directory though. It just can't determined what the library file is.
Current flash player version is: 11.1.115.7 March 5, 2012
Edit: Here is the libflashplayer.so file:
http://dl.dropbox.com/u/24495685/libflashplayer.so
Sent from my A500 using XDA Premium HD app

does this works in ICS?
Update:
Yes it does.
But,,, the script gave me an error about "uncommon string' on line 228,, any ways what I did was just to open adb and run all commands in the script one by one. I copy the edited lib.so to the flash folder , restarted, watching hulu now.
Thanks for this.

Cool. Not sure what the error was(without a way to recreate it) but, I have a new version coming out in a few days that will work better. I will post it over in the app section so I can get more feedback posts and just link it back to here.
It's a single script solution that will do the hex edit when it detects an upgrade or downgrade of Flash to update the edited copy and write it over each boot. That way people don't have to worry about updates and such.
If I can find the time I'm going to upgrade to ICS this weekend. I haven't had time to do much the last few weeks and need my tablet so I have been waiting. I need to read up on the latest. It looks like we even have CWM now OMG! Nice work!
Once I'm running ICS I can test on it and make sure it's working on both.

Joecascio2000 said:
I just tried this and got the same error as above. I did notice that it created the cache folder in the same directory though. It just can't determined what the library file is.
Current flash player version is: 11.1.115.7 March 5, 2012
Edit: Here is the libflashplayer.so file:
http://dl.dropbox.com/u/24495685/libflashplayer.so
Sent from my A500 using XDA Premium HD app
Click to expand...
Click to collapse
That's very odd. My current version is 11.1.111.7. I will take a look at it in a few. For me so far I have seen 11.1.111.5-11.1.111.7 and all worked fine on my acer. I'm posting a new version that may already address the issue you are having. I will do some tests with the file you attached to see this evening.
Also might not be a bad idea to confirm the path for the libflashplayer.so is the same as the script is expecting. I havnt added anything in to search the system for alternate flash locations yet. It can be configured at the top of the script though.
I have also found some people are using an older BusyBox that seems to be mission a feature. Im using busybox v1.19.3 latest is 1.19.4 the installer I use is the one from JRummy. It's not a bad idea to confirm which Busybox you have if you run into issues with odd errors.

Looking at this right now. I will need to modify the pattern a little to make it work on this lib version. Thanks for bringing it to my attention. I'll PM you when I update with support for that version.
EDIT: New improved version here
Joecascio2000 said:
I just tried this and got the same error as above. I did notice that it created the cache folder in the same directory though. It just can't determined what the library file is.
Current flash player version is: 11.1.115.7 March 5, 2012
Edit: Here is the libflashplayer.so file:
http://dl.dropbox.com/u/24495685/libflashplayer.so
Sent from my A500 using XDA Premium HD app
Click to expand...
Click to collapse

[BOOT-ON-CHARGE] LG Pro Lite D680 - Developer help needed.

LG Pro Lite D680
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boot On Charge
Non-generic feature for commercial purposes
URGENT NEED! - WILL DONATE​
What we need:
I am looking for an urgent solution to boot-on-charge LG D680 cell phone, I am asking for help to developers who have experience on this area. The subject is related to unlock the bootlaoder, fastboot and custom rom. I understand the task is not simple, I am looking forward to donate whoever hacks the non generic feature.
What we do:
We provide video service through LG D680 cell phone (Also known as LG Pro Lite D680), the phone has 3G connection and is plugged to the power supply when is working.
Problem:
Most of the day the phone is plugged and working properly, however when the weekend comes the cell phone is unplugged and the energy is completely consumed. Currently, when the power is back to the cell phone we need to start the cell phone MANUALLY by pressing the power on button.
Goal:
We need the phone to be booted into the OS automatically when is plugged into the power USB cable (the phone initial status is powered off).
Possible Solutions / Alternatives:
Unlock the bootloader and run fastboot command fastboot oem off-mode-charge 0.
Continue our research, based on the steps described below (see LG D680 experience)
Replace charge animation with boot file command /system/bin/reboot (see Huawei experience below replacing ipod file).
Finding a custom ROM that already contains a Boot on Charge behaviour.
Finding a custom ROM that at least has “Power On Schedule” feature (AOSP certificate permissions level).
Finding a generic Android vestion with “Power On Schedule”.
Cellphone specifications:
PLATFORM
OS - Android OS, v4.1.2 (Jelly Bean), upgradаble to v4.4.2 (KitKat)
Chipset - Mediatek MT6577
CPU - Dual-core 1 GHz Cortex-A9
GPU - PowerVR SGX531
Previous work and research:
We did this "boot on charge" research in two types of cell phones. One is HUAWEI G730 and the other is LG D680. Fortunately, it worked fine in G730, but we haven’t the same results up to now on LG D680.
In Huawei G730, we replaced charging animation located at /system/bin/ipod with an ipod file containing “/system/bin/reboot” and worked like charm!
LG D680, we could not find the animation file, but we found that it might be inside the boot image. We did some research in order to modify it, but we got blocked (someone might continue our steps if useful).
HUAWEI G730 Extended Procedure:
Since this phone has a Mediatek chipset, the “battery animation” app is running on /system/bin folder. Is running with the filename ipod. The main task is to exchange ipod content (which is originally binary) to an ipod file with this content: /system/bin/reboot.
So, create a brand new file called ipod, and wrote the line in there. We transferred the file to the phone via adb push, as shown in next steps below.
Copy procedure: So, we set our phone to USB Debugging Mode, then we connected it to the PC, and run the following script:
adb shell mkdir /storage/sdcard0/carga/ (We created a folder to store files being pushed from the PC to the phone)
adb push ipod /storage/sdcard0/carga/ (We are pushing the file to the storage folder within the phone)
adb shell "su -c 'mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system'" (This step is very important, here we remount the /system folder with read-write permissions. Only doing this we will be able to copy programmatically the “hacked” file ipod to /system/app. Look out that we used mmcblk0p5 because the system folder is mapped there in this phone. You can check this running cat /proc/dumchar_info)
adb shell "su -c 'chattr -i /system/bin/ipod'" (doing this we took out immutability to the original file ipod)
adb shell "su -c 'cp /system/bin/ipod /storage/sdcard0/carga/ipod.old'" (just creating a backup file from the original ipod)
adb shell "su -c 'rm /system/bin/ipod'" (here we are removing original ipod file)
adb shell "su -c 'cp /storage/sdcard0/carga/ipod /system/bin/'" (now we copy the new file ipod to the destination folder)
adb shell "su -c 'chmod 755 /system/bin/ipod'" (change the permission ro rwx-rx-rx)
adb shell "su -c 'mount -o ro,remount -t ext4 /dev/block/mmcblk0p5 /system'" (we remount the /system folder with read-only permissions)
adb shell "su -c 'reboot'" (Finally we reboot the phone)
RESULT: Whenever you plug in the phone to the charger when it is off, it will try to boot on the battery animation, but instead, it will be redirected to a “reboot” command, which in turn will be redirecting execution to the O.S.
LG D680 Procedure:
We found that this phone also has a Mediatek chipset. Moreover, it also has a file called ipod within /system/bin. But in this case, the bootloader image doesn’t call ipod whenever it displays the battery animation. So we had to check where is mapped the boot image on the phone by executing adb shell "cat /proc/dumchar_info". As the picture shows, the boot image (bootimg) is mapped in /dev/block/mmcblk0, from offset 0x1200000, and with size 0x900000.
We tried the following steps, in order to test if we were able to download / upload booting without bricking the phone:
We copy bootimg partition to boot.img by doing adb shell "su -c dd if=/dev/block/mmcblk0 of=/storage/sdcard0/boot.img bs=1024 skip=18432 count=9216’. (Skip and Count are measured on KBytes, and those values are offset and size translated from hexa to dec).
Then we did the inverse operation by executing: adb shell "su -c dd if=/storage/sdcard0/boot.img of=/dev/block/mmcblk0 bs=1024 seek=18432”
RESULT: The phone WASN’T bricked, and reboot normally (obviously without any change on bootimg).
Because these steps worked, we went even further, this time by unpacking and repacking boot.img file. The steps done were:
Same as (b)
We pulled boot.img file from the phone to a folder within the PC, and then we unpacked the image with bootimg.exe as the picture shows below. One interesting fact is that the pulled file sized almost 9MB.
Then we repacked it without any change inside the image, as the picture shows below. The “repacked” image is now on file “boot-new.img”, but its size is almost 7.4MB. We don’t know why we have this difference.
Same as step (ii) on (b).
RESULT: The phone resulted in a SECURITY_ERROR. It is weird because we didn’t change anything. We didn’t tried further since we are not able to unpack-repack the same image, and loading it successfully.
Edited: The security error can be avoided please follow the just below instructions.
Avoid Security Error:
In order to avoid the security error above mentioned, you need to edit the default.prop file (located at /bootimg/initrd)
Change the value from 1 to 0.
FastBoot Note LG:
Fastboot is a solution performing these commands, the problem is that the bootloader is locked for these operations on the generic vesion:
fastboot oem unlock
fastboot oem off-mode-charge 0
fastboot oem lock
fastboot reboot
The command "adb reboot bootloader" does not enter on fastboot upon reboot. There seems to be an opened option while booting on "Download Mode". What I did find out is that when you go into "Download Mode" a new ADB Device is detected on my computer however no driver matched the device. I assume fastboot could be avilable on Download Mode. I have been suggested by romulocarlos to Install the drivers on LG's website however did not work out.
Files:
For making the tests your will need the system.img, boot.img images files. If you brick your phone and want to un-brick the phone please follow this guide [Guide] LG G PRO LITE- Unroot/Unbrick - flash official factory firmware. Currently we are using this kdz image.
Forum:
G Pro Lite D680 Android Development at Android General.
XDA considered the case and opened a new forum for the phone. Thanks very much laufersteppenwolf (aka Wolf), MikeChannon (forum moderator) and svetius.
Conclusion:
We have reached this spot and need help from more advanced hackers. As you guys can see, we have been working hard to trying to hack the boot-on-charge feature on the D680 however has not been yet possible. There is no precedent on this phone on custom CWM & TWRP and custom roms yet therefore the is no out of the box solution as on many other phones (i.e. cyanogen list). We have also tried XDA University practices with no results.
I am ready to donate whoever would help us in solving this problem, its an urgent matter that needs to be solved as soon as possible. I will reward a developer by making a donation.
Appreciate very much the help in advance and reading.
Best,
Jose

Well, it's not that easy without having the actual device, but it'd help quite a bit if you could upload a system dump as well as the boot.img

laufersteppenwolf said:
Well, it's not that easy without having the actual device, but it'd help quite a bit if you could upload a system dump as well as the boot.img
Click to expand...
Click to collapse
Hi laufersteppenwolf,
Congratulations for your achievements and career, amazing.
I am hereby sharing two link resoruces to download what you have asked for, system.html containing the system.img and boot.html containing boot.img. Please let me know if you have problems downloading.
I understand the side effects of not having the cellphone by your side, hope we can mitigate it with the image files you are asking. As extended solution I can open a vnc session or whatever remote tool you can consider.
Thanks so much for the answer and support.
Best,
Jose

JoseVigil said:
Hi laufersteppenwolf,
Congratulations for your achievements and career, amazing.
I am hereby sharing two link resoruces to download what you have asked for, system.html containing the system.img and boot.html containing boot.img. Please let me know if you have problems downloading.
I understand the side effects of not having the cellphone by your side, hope we can mitigate it with the image files you are asking. As extended solution I can open a vnc session or whatever remote tool you can consider.
Thanks so much for the answer and support.
Best,
Jose
Click to expand...
Click to collapse
I am DL'ing the files now, but please use another hoster, as 4shared is not allowed on XDA

laufersteppenwolf said:
I am DL'ing the files now, but please use another hoster, as 4shared is not allowed on XDA
Click to expand...
Click to collapse
Hi laufersteppenwolf,
Thanks for clarifying, I was not aware 4shared was not allowed. I am changing the hosting and updating the link.
Cheers,
Jose

Alright, what I have done so far is I have unpacked the boot image and the ramdisk, edited the ramdisk so it shoud execute /system/bin/reboot when the phone boots because of the charger. Then I repacked both and signed the boot.img again so the bootloader would accept it.
The result, however, is a bootloop. I am just not yet sure whether it is caused by a "false alarm" (the ramdisk always thinking the phone is being booted because of a plugged in charger) or caused by either the bootloader or other low-level security checks. But I also doubt that, as the bootloader seems to accept the repacked image (doesn't show the security error screen).
But I currently do not have any logs, which is why all this is wild guessing. So the highest priority now is to get some proper logs so I know what's going on

laufersteppenwolf said:
Alright, what I have done so far is I have unpacked the boot image and the ramdisk, edited the ramdisk so it shoud execute /system/bin/reboot when the phone boots because of the charger. Then I repacked both and signed the boot.img again so the bootloader would accept it.
The result, however, is a bootloop. I am just not yet sure whether it is caused by a "false alarm" (the ramdisk always thinking the phone is being booted because of a plugged in charger) or caused by either the bootloader or other low-level security checks. But I also doubt that, as the bootloader seems to accept the repacked image (doesn't show the security error screen).
But I currently do not have any logs, which is why all this is wild guessing. So the highest priority now is to get some proper logs so I know what's going on
Click to expand...
Click to collapse
Hi Wolf,
Great advance! Keep the great work up .
I have made some modifications on the original post. Yes you are right, the bootloader friendly accepts the original image and we have figured out the security error. We have found on our end that you need to edit the default.prop file (located at /bootimg/initrd) and set ro.secure to value 0. I also added the files to the post (yet to change the server origin on the boot.image though), added the kdz image to unbrick. Also appended the new forum for the phone.
I appreciate that you have favored to create the forum for the G Pro Lite D680 Android Development. Its great that we can help the community with our achievements.
Best,
Jose

JoseVigil said:
Hi Wolf,
Great advance! Keep the great work up .
I have made some modifications on the original post. Yes you are right, the bootloader friendly accepts the original image and we have figured out the security error. We have found on our end that you need to edit the default.prop file (located at /bootimg/initrd) and set ro.secure to value 0. I also added the files to the post (yet to change the server origin on the boot.image though), added the kdz image to unbrick. Also appended the new forum for the phone.
I appreciate that you have favored to create the forum for the G Pro Lite D680 Android Development. Its great that we can help the community with our achievements.
Best,
Jose
Click to expand...
Click to collapse
ro.secure doesn't trigger the security checks, this prop is only for other things like adb on early boot, enabling adb remount, adb as root by default,...
I also set ro.secure to 0 in the builds I sent you, so that's not the cause of the issue

@JoseVigil
I have some pretty good news The phone now does exactly what you want it to do, as soon as you plug in the charger, the phone boots into offline charging mode, but then directly reboots again into the normal system.
The reboot is not that nice, but it's by far the easiest, as well as safest, way to do it.
Turns out, LG did a pretty sloppy job, giving me adb access to the device when in offline charging mode, giving me the chance to read which process is running and patching the binary to run my hack before actually executing the binary. And that's it. A few lines of bash code and you're good to go
Now my question, do you want me to write a tiny script to do all the work patching the system, or shall I just explain what to do?

laufersteppenwolf said:
@JoseVigil
I have some pretty good news The phone now does exactly what you want it to do, as soon as you plug in the charger, the phone boots into offline charging mode, but then directly reboots again into the normal system.
The reboot is not that nice, but it's by far the easiest, as well as safest, way to do it.
Turns out, LG did a pretty sloppy job, giving me adb access to the device when in offline charging mode, giving me the chance to read which process is running and patching the binary to run my hack before actually executing the binary. And that's it. A few lines of bash code and you're good to go
Now my question, do you want me to write a tiny script to do all the work patching the system, or shall I just explain what to do?
Click to expand...
Click to collapse
You are the man Wolf!
Its great that you have been able to find a workaround.
Yes, ideally both. I would appreciate if you can write the script so we can run it on our rooted phones pragmatically and a brief description of what it does (comprehensive from reading the script too) with implementation steps to reproduce too.
With the script I will do the proper test on my end and provide you feedback in case we have an issue. I will place the donation the coming week early on right after the test, I will be pleased that you get your reaward .
Once that, I think It would be pertinent though that we can expose how far we have reached with our research. If you agree, we can set the ground for someone (either me or you or anyone) to get a bootable customized boot image and unlock the door for CM.
I would love to see this running on CM. But I also know we have to be realistic, as you mentioned, this could be a hell of a work to have a working custom recovery, the device tree and blobs with kernel (almost XDA University I have not been able to deal with too).
It has been a lot of fun and a pleasure to know you and interact with you. I hope this is our first experience.
Thanks very much for the great work.
Best,
Jose

JoseVigil said:
You are the man Wolf!
Its great that you have been able to find a workaround.
Yes, ideally both. I would appreciate if you can write the script so we can run it on our rooted phones pragmatically and a brief description of what it does (comprehensive from reading the script too) with implementation steps to reproduce too.
With the script I will do the proper test on my end and provide you feedback in case we have an issue. I will place the donation the coming week early on right after the test, I will be pleased that you get your reaward .
Once that, I think It would be pertinent though that we can expose how far we have reached with our research. If you agree, we can set the ground for someone (either me or you or anyone) to get a bootable customized boot image and unlock the door for CM.
I would love to see this running on CM. But I also know we have to be realistic, as you mentioned, this could be a hell of a work to have a working custom recovery, the device tree and blobs with kernel (almost XDA University I have not been able to deal with too).
It has been a lot of fun and a pleasure to know you and interact with you. I hope this is our first experience.
Thanks very much for the great work.
Best,
Jose
Click to expand...
Click to collapse
Alright, in the attachment I have uploaded the script, including all needed files in order to execute it. The script will also tell you what it's about to do before doing it, so in case you run into issues, you know where to look into
So, what the installer script is going to do:
It will first of all push a script temporarily to the internal sdcard, then it will back up /system/bin/rtcd to /system/bin/rtcd_original, as we need to execute it later again. Next it will copy the script over from the sdcard to /system/bin/rtcd, replacing the original binary (and setting the correct permissions to both modified files). As the last step it will delete the temp file from the sdcard again.
That's all the installer script does.
The actual "magic" is inside the script being pushed to /system. It gets executed before starting chargemon and reads out the devices boot mode. If the boot mode is charger, it executes /system/bin/reboot. Otherwise it executes the original binary in /system/bin/rtcd_original.
And that's about it As simple as it could only be
Regarding further development, up until now, every device I own received a werewolf kernel, and I'm not planning on making an exception for this phone
I will definitely keep on looking into it, though it will not be as high on my priorities list as this workaround was
I will most likely open a new thread in the next couple of days, stating my findings regarding the phone/boot image/bootloader.

@JoseVigil @laufersteppenwolf
I'm New In Rom Developing . But I Think This Can Help You To Find Security Checks

I need lg g pro lite dual d686 custom twrp recovery i cant find anywhere plz provide working recovery link for d686 as iam new it seems custom recovery for specific d686 dosnt exits so share tested link for d686
Sent from my LG-D686 using xda Forums PRO

Hello I need boot on charge on my LG E460 with MTK. I done ipod change, rctd replace from laufersteppenwolf file without results. I can't went into fastboot mode of course to set oem mode charge for 0
Phone have root, bootloader unlock, busybox and supersu. Any suggestions?

Maxjimme said:
I need lg g pro lite dual d686 custom twrp recovery i cant find anywhere plz provide working recovery link for d686 as iam new it seems custom recovery for specific d686 dosnt exits so share tested link for d686
Sent from my LG-D686 using xda Forums PRO
Click to expand...
Click to collapse
TWRP RECOVERY
http://forum.xda-developers.com/optimus-g-pro/d680-development/d686-unsecured-boot-img-twrp-2-8-7-x-t3163144

Same Problem here with LG E460. Is there a solution for fastboot mode with this device?

hi, do you think this script could work on a LG G Pro 2 ?

hi guys, any chance i could get this working on a chinese mediatek device running kitkat 4.4.2 ??

[Q] How to root SM-T113 ?

Hello, i have one question.
I have a Samsung Galaxy Tab 3 7.0 ( SM-T113 ) i can't find any rom and root package for my pad.
Maybe someone can help me?

I support this request. The T113 is a new device. I was thinking of getting me a cheap t110, but the t113 is also cheap. If it would be possible to root this I would take it.

Rooting SM-T113
Hello everybody
I struggled to root my Samsung Galaxy Tab 3 Lite
(SM-T113). So I decided to shared my experience and writing this tuto.
Of course, this is "a non standart" device, and elements for rooting
SM-T110 or SM-T210 didn't work. Android version of this device is 4.4.4
Methodology and tries :
I have proccured myself the Samsung official firmware (here). This image
allow me to get back during beetwen the experimentations. I tried several
experimentation and restore the device after each fail.
Installing with Odin the Clockworkmod (CWM) for SM-T110 , for SM-T210, and
SM-T211. (Has preconnised here) Each time, when loading the CWM, I got a little
(1 ascii character) exclamation mark at the top-left of the screen. The device
didn't boot on recovery
Installing with Odin the (TWRP) for SM-T110. Same symptom
Installing philz_touch : against the message with only the red exclamation
mark.
I conclude of checked of some signature before executing recovery.
Using Kingo root application : software try to root during 20 minutes and
finaly fail.
Using Towel root application : The device isn't reconized
Conclusion: Security breach for rooting have been fixed in this version of android
I have downloaded UPDATE-SuperSU-v2.46 for android. The idea is to push this
application by the standart android update way. (native recovery).
Sending the zip archive 'as is' => failure to check the whole archive
Re-sign the archive with the autosign tools => failure to check footer of archive
Rewriting the update-script (see here) and (here) and auto-sign the archive
: failure to check footer
I am procured myself some pre-rooted image. Odin fail to import them. (and I
have no succed to use heimdall for linux on my debian)
I have try to improve the official samsung Image by adding root manually , using
simg2img and make_ext4fs. Odin fail at the same point
It's remaining me two way : Or I try to generated a correct update file, or I
try to understood why odin fail to import prerrooted system and my custom
image. I choosed the second option.
The offical update is splited by several blocks, each block having is own
header. A master header provide global information about the image (number of
blocks, size, ...). I have putting some spies in simg2img and
observate the headers of official update and of my custom uptate. Result is
surprising : It is missing 4 bytes by headers. in custom update. According to
samsung orginal update, missing values seem to be constant. I suppose it's a 'magic
number', checked by the device to be sure the 'good' update is applied. So I
modifed this headers in make_ext4fs for adding the missing constants. My custom update is now
accepted by my devices, and I got root (!)
I will now describe how to generate and import this update.
DISCLMAIMER
I or Xda-developers are not responsable of any damage one your device, in particular if you bricked it
You waranty will probably void
Rooting device may lead to some dysfonctionnement, or may open some security breach. You are the only responsable.
1. What do you need :
Your device, and a cable to connect it to your PC
A Windows distribution, with Odin (www (dot) samsungodindownload (dot) com/) and the samsung drivers (www (dot) samsung (dot) com/us/support/owners/product/SM-T110NYKAXAR#")
A Linux distribution, with the appropriate compilation package (build-essential), and with git.
A way to transfers big files beetwen your Linux and your Windows.
The Official samsung update (best-tech-reviews (dot) com/update-sm-t113-t113xxu0aoa4-android-4-4-4-2152 or rapidgator (dot) net/file/7140bfdc421eea86eda5a5cbca00216e)
The UPDATE-SuperSU-v2.46 in zip format (download (dot) chainfire (dot) eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1") (or root program for your android)
Method assume you never installed root on your device
2. Generate the update
Uncompress the Samsung official image.
Code:
unzip image_official.zip
tar -xf image.tar.md5
Uncompress and make_ext4fs and simg2img (here)
Code:
cd ..
git clone https:// github.com/YuLaw/ext4-utils.git
cd ext4_utils
Download and applied the patch (see attachment)
Code:
patch -p1 < ../patch_ext4_utils.diff
Build ext4_utils
Code:
make
Extract the image
Code:
cd ..
unzip DBT-T113XXU0AOA4-20150121104149.zip
tar -xf T113XXU0AOA4_T113OXA0AOA4_HOME.tar.md5
ext4_utils/simg2img system.img system.img.raw
Mount the image
Code:
mkdir mount_point
sudo mount -o loop,rw system.img.raw mount_point
unzip the UPDATE-SuperSU-v2.46
Code:
mkdir UPDATE-SuperSU-v2.46
mv UPDATE-SuperSU-v2.46.zip UPDATE-SuperSU-v2.46/
cd UPDATE-SuperSU-v2.46/
unzip UPDATE-SuperSU-v2.46.zip
cd ..
Now, copy common file and armv7 one the mount_point. If you use an other
device, replace the armv7 repository by the appropriate repository according
to your device processor. You can refer to the
UPDATE-SuperSU-v2.46/com/google/android/update-binary to find them.
Code:
sudo cp UPDATE-SuperSU-v2.46/armv7/{su,supolicy} mount_point/xbin
sudo cp UPDATE-SuperSU-v2.46/armv7/su mount_point/xbin/daemonsu/
sudo cp UPDATE-SuperSU-v2.46/armv7/libsupol.so mount_point/lib
sudo mkdir mount_point/etc/init.d
sudo cp UPDATE-SuperSU-v2.46/common/99SuperSUDaemon mount_point/etc/init.d
sudo cp UPDATE-SuperSU-v2.46/common/Superuser.apk mount_point/app
sudo mv mount_point_app/etc/install-recovery.sh mount_point/etc/install-recovery.bak
sudo cp UPDATE-SuperSU-v2.46/common/install-recovery.sh mount_point/etc
sudo chmod 0755 mount_point/xbin/daemonsu
sudo chmod 06755 mount_point/xbin/su
sudo chmod 0755 mount_point/xbin/supolicy
sudo chmod 0644 mount_point/lib/libsupol.so
sudo chmod 0755 mount_point/etc/install-recovery.sh
sudo chmod 0744 mount_point/etc/init.d/99SuperSUDaemon
sudo chmod 0644 mount_point/app/Superuser.apk
We will regenerate the file system. Do not umount them. If patch on
ext4_utils is not applied, you shall applied it now.
Code:
mkdir output
sudo ext4_utils/make_ext4fs -s -a system -l 1500M output/system.img mount_point
cd output
tar -cf system.img system.img.tar
md5sum -t system.img.tar >> system.img.tar
mv system.img.tar system.img.tar.md5
You can now transfert this file to your windows operating system.
3. Android prepartion
You must ensure your device is allowed to install apk from untrusted source. See
in option/application or in developper menu option
Connect the android to you pc.
Boot your android device into downloading mode. On SM-T113 Samsung galaxy Tab3 lite,
press power, volume down and pad when booting.
Run odin, ensure Repartion is NOT checked, and select the AP (PDA) button. (The
only checked case is autoreboot and F.Reset time) Load the previously generated
file and click start.
Your android device may now reboot and install the root application.
Congratulation, you have now rooted your device. You can clean up the downloaded files.
4. One of these step fail, what I can do to come back. :crying:
You may import with odin the official samsung firmware or proceed to a factory return from the recovery.
5. May I eat my devices if I can't root it ?
Samsung user manual say to not do it.

samsung tab 3 sm-t113 root
Thank for the update about for the root. But I don't have Linux and I don't know how to use Linux too. It's there a way without Linux

If you don't have linux, you can try using Cygwin. This is a linux like environment running on Windows.
or if you find my solution is too complicated, I do it for you.
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
https://drive.google.com/file/d/0Bwao3SgtdOPPYm9XNF8wQXEyWjg/view?usp=sharing
unzip file and upload it to you device with Odin
Nb: This file will remain on my google drive until I need space or until I decide to remove it. (in a long time)

grizzlyfute said:
If you don't have linux, you can try using Cygwin. This is a linux like environment running on Windows.
or if you find my solution is too complicated, I do it for you.
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
unzip file and upload it to you device with Odin
Nb: This file will remain on my google drive until I need space or until I decide to remove it. (in a long time)
Click to expand...
Click to collapse
Thank you for your great work!!
Do you think the package will work also with Tab3 lite SM-T116? (Sm-t116 should have only the 3g module more than sm-t113)

Root Worked
Thanks for the your great effort grizzlyfute.
Worked perfectly and finally got my device rooted

beodev said:
Do you think the package will work also with Tab3 lite SM-T116? (Sm-t116 should have only the 3g module more than sm-t113)
Click to expand...
Click to collapse
No. Package will erase the system partition, including configuration file (/system/etc), and probably some drivers. Importing the SM-T113 package will probably put the 3G module out of service.
I suggest you to procure an 'official firmware' for your device (see in Settings/about for the exact version) and follow procedure in post#3.

grizzlyfute said:
No. Package will erase the system partition, including configuration file (/system/etc), and probably some drivers. Importing the SM-T113 package will probably put the 3G module out of service.
I suggest you to procure an 'official firmware' for your device (see in Settings/about for the exact version) and follow procedure in post#3.
Click to expand...
Click to collapse
I tried to follow your linux-instructions (by using cygwin, with an official sm-t116 firmware), but something go wrong (i think cygwin doesn't know batch commands like "sudo", or "su" etc..).
I put your md5 file to my sm-t116: the results is that the device is rooted, but no network connection works (Wi-Fi too) .
I jump back to the original firmware, maybe in the future someone will develop the firmware for the sm-t116 version.
Thank you for the Help

Thanks buddy! It works! :good:
Just got my t113 today and now rooted. Awesome!

Light at end of tunnel
grizzlyfute said:
...
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
https://drive.google.com/file/d/0Bwao3SgtdOPPYm9XNF8wQXEyWjg/view?usp=sharing
unzip file and upload it to you device with Odin
...
Click to expand...
Click to collapse
FABULOUS!!! And thank you! And have i said fabulous? And thank you??? And this, only for giving me rooting hope!
I am a proud user of a gt-i9100 for a few years, rooted/unlocked/custom rom(ehndroix), so, all the 9 miles, but, that´s the phone... And since i am not very proficient when it comes to using odin, and if you don´t write all the steps, i am like a fish out of water (can´t breathe or swim) and i am afraid to do some wrong step.
So, when you say upload it to your device, which will be the parameters in ODIN?
Edit: I confirm, it works, i was afraid of doing something wrong and brick the thingy, but its working fine, thanks to odin and pda and this developpers work!:victory:
!! Thanks !!

I followed these instructions step-by-step on my SM-T113, but for some reason the device would always fail to receive the image I'd built (Odin would just sit there saying NAND Write Start! for a while, then fail. So I tried downloading your precompiled version... and what do you know, it worked straight away.
Thanks a ton, HUGE help!

(q)how to root tab sm-t116nu ?
please help me

cjmac said:
I followed these instructions step-by-step on my SM-T113, but for some reason the device would always fail to receive the image I'd built (Odin would just sit there saying NAND Write Start! for a while, then fail. So I tried downloading your precompiled version... and what do you know, it worked straight away.
Thanks a ton, HUGE help!
Click to expand...
Click to collapse
Sorry for the delay.
I encountered the same problems before I make the patch. Cause of the problem is the file generated by ext4_utils tools is not immediately compatible with the sm-t113 device. I have to add constants in the encapsulation headers for the device to accept the file. You can see details in the patch provided.
To determine theses constants, I put some spies in simg2img and extracts the official firmware. It is not exclude these values change in function of the device.
For the sm-t116, I suggest to open an other thread. I think the works can be picked up and adapted.

wifi issues?
Thanks for your work!
I have successfully rooted my tablet, but its now not connecting to a weak wifi signal it was previuosly connecting to. In fact, it previuosly rratd the same signal as "fair".
Is this connected in any way to the rooting package, and can be resolved somehow?

Hello, thanks for your help! now, i have my Samsung SM-T113 rooted.
but, there any way to put the cmw?
I want to make a backup image and not as .... thanks

Anyone know if this way working in model SM-T113NU ?

Samsung official image ?
grizzlyfute said:
2. Generate the update
Uncompress the Samsung official image.
Click to expand...
Click to collapse
I don't understand what is the "Samsung official image" :
i don't see it neither in the 1. What do you need : list , nor in attached files
I thought it could be "The Official samsung update ", but its name is not "image_official.zip" I see in the first line of code, and moreover I see "unzip DBT-T113XXU0AOA4-20150121104149.zip" in the following lines.

any chance to make more easy the way to get root? btw I have the variant SM-T133NU 4.4.4 KK please!

Minimalistk0 said:
any chance to make more easy the way to get root? btw I have the variant SM-T133NU 4.4.4 KK please!
Click to expand...
Click to collapse
I second that! Rooted custom rom highly appreciated! I'd even pay some bucks