Database Info

How I cook a ROM

My Guide to cooking requested by a few of my ROM users.
- IMPORTANT -
Make sure you have Visual C++ 2008 and M$ .Net Framework and it's Service Pack.
- NOTE TO COOK -
These Sys and Xip files are for 96 dpi devices only or commonly known as QVGA. So Please if you want to cook for your device using my guide, please make sure your device is as such.
- THE PREP _ Gathering Your Ingredients-
You can download my kitchen.
(Extract my kitchen to the C:\ directory (the root of your harddrive))
-OR-
Download the kitchen files below and create your own kitchen.
Create a directory C:\kitchens\
(Go into the C: drive and right click in an open area. Hover over 'New' and the select 'New Folder' and name it kitchens.)
Then download these kitchen files:
Link 1
Link 2
Link 3
Link 4
Link 5
Link 6
Link 7
(These links were brought to you by JustKitchen.info)
These links are archived with 7-zip.
When you have all these files downloaded, and you have 7-zip installed, Select all of the files you've downloaded. Then right click on one of the highlighted files and hover over 7zip in your dropdown menu and then click on 'Extract Here.'
{
"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"
}
This will create a directory that looks similar to this:
As you also see in that picture (The 'Working_Folder' archive) you'll need my Sys & Xip files. And as you know me, I will always try to keep this folder updated so that when a new build comes out you guys can cook with it too, Which you guys can find HERE or any of my ROM threads. Right now I have all the newest builds. So you guys are set
_If you downloaded my kitchen instead, then it will have come with build 23545 & build 23563 only (Which are Windows Mobile 6.5.5 - the latest Windows Mobile Builds)._
After you download my Working_Folder.7z then just extract the files as shown (Just right click on the file and hover over 7zip and you can click on 'Extract Here.'
And yes, lol, my computer is names Muff - PC because me and my wife's pet names are Muffin, lol.
Now, click 'Yes' when it prompts you asking if you want to Merge the folders and then also click 'Yes' to Overwrite the files there if necessary.
Once you have the kitchen setup the way you want it, (you'll also notice the PagePool Changer I have in there) then go up one level in the folder to where you see Working_Folder and send a shortcut to the desktop as you see below:
Here is where you'll need to make changes to your files (Because my files have my background image and watermarks and all of my GUI changes..etc..).
Navigate to C:\kitchens\SuperJustKitchen\Working_Folder\SYS\23563\dpi_96\COMMON\Base_DPI_96
You can download this Base_DPI_96 folder here if you want the original files..
Just drag and drop over the Base_DPI_96 folder in the C:\kitchens\SuperJustKitchen\Working_Folder\SYS\23563\dpi_96\COMMON directory.
After you're all set in making your GUI changes then navigate to
C:\kitchens\SuperJustKitchen1\Working_Folder\EXT\SHARED\THEMES_QVGA
This is where you are going to change your background images. The most important part about making these images is the fact you need to keep them perfectly proportioned to your device. If you have a qvga, like my Wing/Herald, then its going to be 240 x 320 (portrait) and 320 x 240 (landscape).
When you're done making your images make sure to rename them respectively.
Now navigate to C:\kitchens\SuperJustKitchen1\Working_Folder\EXT\SHARED\Control Panel\HTCAnimation_1_3_5_0\files
This is where you'll change the splash screens. And Please do ^>^ because we each should have our own unique style of cooking, lol.
Just find an animated .gif image - Also 320 (tall) x 240 (width) - and just rename it Animation2.gif
Then Find a still image of whatever you'd like and rename it welcomehead.96.png
Just take mine out and dispose of them..
- End of Prep -
Part two below.​

- PART TWO _ More Prep -
Okay. First thing is navigate to your Working_Folder, which should be on your desktop continuing from the last post. Open the ErviusKitchen.exe
Let it load, then click on the drop down menu in the picture and land it on Herald. It will go crazy for a second, but, that is normal.
Next, click on the dropdown menu for the XIP and SYS and land them on the build you're using. I am using, the included, 28223 build.
Next, you're going to add your ROM version number. In the picture is how I normally label mine.
Should look like this:
Using LZX Compression is useful when you notice your ROM is too big. The Max size a ROM can be is about 80MB or so. If you plan on not flashing by SDCard then the minimum size of the ROM should be 50.1MB. When you are ready to cook, you'll see the size in bytes. So, in bytes, 50.1MB is 52,567,531
- - -
Next, click on Show Editor.
This will bring up all the .rgu files that are located in the kitchen. Scroll down to where you see the .rgu file located in the Shell.
Double click on it and it will open up the editor. Locate line 419. This is where you can 'brand' your ROM. All my ROMs I create usually have the branding '- Trib.' Put anything you want after the '- ' (and you also have to leave space right after the '- '). Then make sure to save. Then close out of the editor. Then go back to the main kitchen window.
- - -
Next, click on Extra Buttons.
This will bring up a menu with large buttons. Click on the CABtoEXT button.
That will bring up a command prompt window as shown:
Minimize all the other windows. Then hit the Enter key. This will open up a large window.
Then navigate to any of the cab files that you might want that are not listed in the kitchen. Select and Right-Click on the cab files that you want then click on Copy.
Then Right-Click and Paste the cab files into the window that popped up.
When all the cab files have been placed go back to the other command prompt window and then press Enter where you see Press any key to continue . . .(and make sure to only put up to four at a time.. for some reason it doesn't work right).
A prompt will follow asking if it will be used for 96dpi devices. Make sure you select the respective digit for 96dpi then hit enter. Another message will prompt you to select what devices can use the programs. Make sure to select All devices.
Your cabs you import into the kitchen will be located in the 0096 Category in the list
- - -
Now head back to the kitchen's main window. Next we are going to Save the ROM so far. Make sure you save with a version number (sometimes if I save before I put a version number I'll forget to put one all together. Basically a ROM won't flash without one.
Now Close out of the kitchen all together then re-open it. Reason being is because the cab files you've just installed won't show up until you do. Then Load your previously saved ROM.
Now it's time to make your selections of what is going to go into your ROM. Double click on each file/module to toggle the enabling/disabling of packages.
These are my selections:
Once you've made your selections make sure to save once more.
- End of Part Two_ More Prep-
Cheers,
Trib
​

- PART THREE _ Cooking -
Now you are ready to cook. Press the Create ROM button.​
You will see more craziness:
This process can take up to an hour depending on how many cores your computer has - it's a logical based kitchen ^>^
Once the process is complete, navigate to C:\kitchens\SuperJustKitchen\Working_Folder\RELEASE_HERALD and click on the ROM Update Utility. Or you can use the PagePool Changer to change the pagepool to something other than the default, which is 6MB. Changing it to 3MB will give you about 5MB more Ram. But it also has a trade-off of slowing your ROM down a bit.
Put your device into the bootloader by soft-reseting it (by pressing in, with your stylus, the little hole on the left side of your device) and also holding down the camera button. You will then be in a, what we call a tri-colored, screen.
Then check off the check box and press next. Do this again. Then it will pause. Then the utility will pop up again and click on next twice and then UPDATE.
Once you flash the ROM to your device, upload it with RGhost.Net
Then post the link in this thread. I would like nothing more than to see the fruits of yours and my own labour.
Cheers,
Trib.
-End Part Three _ Cooking -
​

An excellent and to the point start!
Let me be the first to congratulate you! This tutorial is going to help people like me tremendously!

Hm. i just realized I forgot to mention that these Sys and Xip files are for 96 dpi devices only or commonly known as QVGA. So Please if you want to cook for your device using my guide, please make sure your device is as such.

Long time viewer, first time poster.
I am also looking very forward to this tutorial. I've been messing around in the "kitchen", just getting the feel of it.
Looking forward to a better understanding.
Thanx for all the hard work.

Thank you for this!! I will try to.

Your welcome. I can't wait to see what your ROMs will be like.

WOW! Nice tutorial!!
If I mess it up now, it could only be due to my own un-geekness.
Just one question: Would it be too much trouble to outline just the files needed to create a "bare-bones" rom; i.e. a rom that will work (duh), but have as little "fluff" as possible?
Excellent work!! Donation is on the way!

Thank you for your kindness.
And that is exactly what I did - If you select the selections i've made you'll come out with a barebones system with all the necessary files.

nothing
not appear
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]...
img: http://cwmobile.webcindario.com/nothing.PNG
what is the error?
thanks in advance..

Hm. Didn't realize that it wasn't in there. You can manually enter it in there. But I'll include it for you... Just redownload

Tribulattifather said:
Thank you for your kindness.
And that is exactly what I did - If you select the selections i've made you'll come out with a barebones system with all the necessary files.
Click to expand...
Click to collapse
Ah, OK, excellent.
Please pardon my noobness.
I'm at work right now. I'll hit that PayPal button when I get home (I don't want to be typing logins/passwords on this PC, for obvious reasons).
It can't be said often enough: Thank you for your work.

I surrender, thanks for try help me...

Don't surrender, lol. I'm uploading the files you'll need right now.
I'll post back here when its uploaded.
UPDATE: Added the correct files to the SYS folder; you will now be able to 'brand' your ROM now.

Tribulattifather said:
Thank you for your kindness.
And that is exactly what I did - If you select the selections i've made you'll come out with a barebones system with all the necessary files.
Click to expand...
Click to collapse
i have to disagree with you there. You have included many unneeded things for the average user.
To name a few unneeded:
ADC, Adobeflash/codecs, DRM, Entertanment, ipsecvpn, SQLCEMobile, Transcriber, Voicecommand, HTC animation, SIM_Tkit, Net CF.
Just my 2 cents
Granted your roms are more geared towards everyone. Many know mine were not

Oh yeah, I know what you mean. I only meant that this was a barebones ROM that I would make. I guess one could construe that I meant barebones for an average user. My apologies :1
But best thing one can do is cook , cook , cook and cook some more until you get the ROM you want, lol.

thanks, but if I yield to truth, and you can not download the files because they are heavy and my internet is 256 and download speed is + / - 30 kbs.
thanks... thanks... and thanks...

What build would you like me to upload separately for you? I think you said you needed 28223.
This file is only 30MB and contains only 28223 with the updated Shell folder:
http://rghost.net/download/980604/6a9cbd59a9d861179da20ac3f06349b222d8cfda/Working_Folder.7z

Cellomancer said:
Ah, OK, excellent.
Please pardon my noobness.
I'm at work right now. I'll hit that PayPal button when I get home (I don't want to be typing logins/passwords on this PC, for obvious reasons).
It can't be said often enough: Thank you for your work.
Click to expand...
Click to collapse
Thank you so much Cell for your kindness. I will prioritize your needs if you do need anything.

[How To] Flash Splash1 on EVO on Windows 7

[HOW TO] Changing the starting Splash Image EVO
Tools Used:
GIMP http://www.gimp.org/downloads/
fastboot http://okean.ath.cx/splash_editing/fastboot.exe
rgb2565.exe http://okean.ath.cx/splash_editing/rgb2565.exe
cygwin1.dll http://okean.ath.cx/splash_editing/cygwin1.dll
ImageMagic http://okean.ath.cx/splash_editing/ImageMagic.exe
Note: Mirrors to most of those can be found in the threads bellow section.
Help With Tutorial:
Thread I Started http://forum.xda-developers.com/showthread.php?p=6820690#post6820690
G1 Thread That I got most of this from. http://forum.xda-developers.com/showthread.php?t=456071
Thanks a lot to everyone.
----------------------------------------------------------------
Disclaimer.
My first tutorial, I am not responsible for any damages. I did this
by trial and error on my Evo Running Damage Control 3.0 by damageless with Radio Evo-1.39.00.05.31 (06/06/2010) by toastcfh. Fully rooted with engineering SPL via toastcfh method for fast boot access.
--------------------------------------------------------------------------
Step 1:
NAND Backup, Just in case always do this. YOu never know when this will save your phone.
Step 2:
Put the phone aside, and find a picture with a aspect ratio close to 800 height by 480 width, will work best. Open up GIMP with your image. Modify the photo to be 800 height by 480 height or scale it via Image Scale Image, You may hit the chain link on the right if the aspect ratio is not equal. Once the image is scaled, Go to Image -> Mode -> Indexed. Leave it at Generate optimum palette Maximun number of colors 256. Then in the layers, merge all all the layers if required and remove all alpha channels, if there are any. Save as a png, prefferable as splash.png as I will refer to it from this point.
Step 3:
Let us check to make sure we are on the right track, in Windows right click and go to properties than details and make sure width is 480 amd height is 800 and that Bit depth is 8.
Step 4:
Next we will use the ImageMagick software, if installed on windows correctly when you type in convert into cmd (Command Prompt) it will display tons of options. Well will go into the
directory where we saved splash.png and run this command in that folder
Code:
convert -depth [COLOR="SeaGreen"]8[/COLOR] [COLOR="Magenta"]splash.png[/COLOR] rgb:[COLOR="Orange"]splash.raw[/COLOR]
It should make a file called splash.raw right next to it.
Step 5:
Make sure that in the same area as splash.raw is, that you have cygwin1.dll and rgb2565 also and we will execute the following command
Code:
rgb2565.exe < [COLOR="Orange"]splash.raw[/COLOR] > [COLOR="Teal"]splash.raw565[/COLOR]
It should make a file called splash.raw565
WARNING: I know these files are size sensitive and I have had it come out to
exactly 750 KB (768,000 bytes) for size and 752 KB (770,048 bytes) size on disk each time. If someone who knows more about this can explain a significanse or what the size should be exactly i and everyone will appreceate it but for me it works with that size.
Step 6:
Get into fast-boot on your phone via turning it off, than turning on while holding power button, untill you get into the white screen with androids. Select fastboot, it should show fastboot usb. If you type the command
Code:
fastboot devices
it should show you your phone. Next type the following command
Code:
fastboot flash splash1 [COLOR="Teal"]splash.raw565[/COLOR]
It should print out some stuff about sending it and the speed it sent it at. Then finish up with fastboot reboot And you should see your new splash image. YAAAY.
I will include an attachment of a file from Digital Blasphemy that i used and all the files it made in the process.
Questions, Comments, Need Help Post Below.

Xyber3364 said:
Code:
fastboot flash splash1 [COLOR="Teal"]splash.raw565[/COLOR]
Click to expand...
Click to collapse
nice! thanks for putting this together! this should be the beginning of plenty sweet boot images!
new to the HTC fastboot methods ... any idea if there are any other methods of flashing splash1 from inside recovery or normal android? can the flash_image binary flash to splash1?

Ahh ive been looking for something like this for awhile now. Any chance you saved the original splash image? I was hoping to use it in the second bootanimation to make it a smooth switch.
Thanks!

Original
Mast3rpyr0 said:
Ahh ive been looking for something like this for awhile now. Any chance you saved the original splash image? I was hoping to use it in the second bootanimation to make it a smooth switch.
Thanks!
Click to expand...
Click to collapse
Forgot to include this, it is important
Original Hosted here http://okean.ath.cx/splash_editing/splash.nb0
right click and save as if it opens the file in your browser.
Code:
fastboot flash splash1 splash.nb0

Xyber3364 said:
Forgot to include this, it is important
Original Hosted here http://okean.ath.cx/splash_editing/splash.nb0
right click and save as if it opens the file in your browser.
Code:
fastboot flash splash1 splash.nb0
Click to expand...
Click to collapse
Aww its not an image? Is there any way to change it back into an image?

Best I know
joeykrim said:
nice! thanks for putting this together! this should be the beginning of plenty sweet boot images!
new to the HTC fastboot methods ... any idea if there are any other methods of flashing splash1 from inside recovery or normal android? can the flash_image binary flash to splash1?
Click to expand...
Click to collapse
Not sure is my answer.
If you are handy with linux and android,
http://elinux.org/Android_Fastboot
From the recovery you can find these partitions, what to do with them, at the moment I have no clue

Not Perfect BUT
Mast3rpyr0 said:
Aww its not an image? Is there any way to change it back into an image?
Click to expand...
Click to collapse
This is from the HTC BootAnimation, since i have no clue how to convert .n0 back to png, but this is close.
{
"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"
}

Not close enough for what I was hoping to do :/ Oh well, ill keep looking.

Mast3rpyr0 said:
Not close enough for what I was hoping to do :/ Oh well, ill keep looking.
Click to expand...
Click to collapse
Here you go, in BMP format.

ortizdupri said:
Here you go, in BMP format.
Click to expand...
Click to collapse
Ahh yess i love you! haha. Il have a bootanimation out later utilizing it
Might I ask how you were able to acquire it?

Xyber3364 said:
Not sure is my answer.
If you are handy with linux and android,
http://elinux.org/Android_Fastboot
From the recovery you can find these partitions, what to do with them, at the moment I have no clue
Click to expand...
Click to collapse
this is perfect! the information is not for our phone specifically but it helps to understand the fastboot and phone interaction plus basic partition structure! of course, it raises more questions for me, but they're at least advanced a step which is definitely progress! thanks!!

Mast3rpyr0 said:
Ahh yess i love you! haha. Il have a bootanimation out later utilizing it
Might I ask how you were able to acquire it?
Click to expand...
Click to collapse
Through a pain in the ass. And lots of Google. And what not.
Basically grabbed the splash1.nb0 file from toast's RUU file, renamed it to splash1.nb, and used this tool: http://forum.xda-developers.com/showthread.php?t=405118 to convert the splash1.nb to splash1.bmp. My goal is the same as yours - utilize a bootanimation with that as the starting image to jump off from. Luckily, I hope I have helped people out.
(Interesting note from the splash screen, the background isn't pure white, but is a shade of gray, one that continues on to the Sprint bootanimation background.)

ortizdupri said:
Through a pain in the ass. And lots of Google. And what not.
Basically grabbed the splash1.nb0 file from toast's RUU file, renamed it to splash1.nb, and used this tool: http://forum.xda-developers.com/showthread.php?t=405118 to convert the splash1.nb to splash1.bmp. My goal is the same as yours - utilize a bootanimation with that as the starting image to jump off from. Luckily, I hope I have helped people out.
(Interesting note from the splash screen, the background isn't pure white, but is a shade of gray, one that continues on to the Sprint bootanimation background.)
Click to expand...
Click to collapse
So you are telling me, that that program easily turns and bmp to a nb also.... that one can than flash? that makes life easier

Xyber3364 said:
So you are telling me, that that program easily turns and bmp to a nb also.... that one can than flash? that makes life easier
Click to expand...
Click to collapse
Yeah, not sure how well it works on the conversion back to NB, but it might be easier than some of the other methods I've read.

I will let someone else test that out .

Here's a clean and simple one I threw together today for those of us who are rooted.

I like it. What I would like to see is some combo's splash1 -> bootanimation -> background to make it look as smooth as possible.

here is a quick visual program i made.
I used the code for the G1 splash made by Koush.
open up image
preview how it will look
convert to raw file with correct filesize.
it auto resizes to dimension on the longest side.
then just fastboot flash to phone.
I might add a nb0 to bmp/jpg/png
--Included
Executable
Orginal Splash Screen
fastboot

Xyber3364 said:
I like it. What I would like to see is some combo's splash1 -> bootanimation -> background to make it look as smooth as possible.
Click to expand...
Click to collapse
I tried doing that on a bootanimation (as far as splash1 connecting in terms of design), unfortunately, splash1 cuts to a black screen before booting into the animation. I believe it's something like a quarter or half a second of black screen before the animation starts, nothing dramatic, but enough to be noticeable so it is not a smooth transition.

Little something I threw together.
And a link to the file if you want to use it. Feel free to ask questions and use freely.
http://www.wikiupload.com/c8Kn5mTz

Update.zip 2.0 Modifier/Creator [Script] Drag/Drop Support [Windows]

This script has 2 main uses:
1. Modify an update.zip
2. Create an update.zip
For #1 - You just extract the contents of an update.zip into the placehere folder, modify its contents, and run the script stating to create an update.zip
For #2 - So far these are the options i have in there for create the update-script
1. Copy directories
2. Copy files
3. Create Symlinks
4. Delete file
5. Delete directory
6. Flash boot image
7. Set permissions for file
8. Set permissions for directory
New Features in 2.0 :
- Set java heap size / compression level for zip
- New drag/drop mode.
>>> - If you drag a folder onto the script's icon (as in Script.bat) it will compress the contents of the folder into a zip and sign it.
>>> - If u drag a zip onto the script's icon (as in Script.bat) it will sign the zip for you.
So this script guides u as u select each option, and adds the appropriate command to the update-script file. Then u exit that sub-menu and create update.zip
Heres a video for a better explanation:
This script is a result of me constantly wanting to modify roms before i flash them & users who are unaware/lost as to creating/modifying update.zips.
Download : [Windows]

Awesome Gotta try it out.

I tried using this to just push a single app into /system/app just to see if it would work, but when I try to flash from recovery I get E:Syntax error in update script
when I open my update script it reads thus:
Code:
package_extract_file("LearnPython_1.1.1.apk", "/system/app/Python.apk")
Do you know what the issue might be?

marsevern said:
I tried using this to just push a single app into /system/app just to see if it would work, but when I try to flash from recovery I get E:Syntax error in update script
when I open my update script it reads thus:
Code:
package_extract_file("LearnPython_1.1.1.apk", "/system/app/Python.apk")
Do you know what the issue might be?
Click to expand...
Click to collapse
Hmm thats wierd. Can u try placing the file inside a folder withing the placehere folder? N then try it. Tell me if tht works, in meantime ill try a example, perhaps the new changes i made broke something
K i figured it out, i forgot to place a ; after the line. Try placing it and then flashing. Ill fix it.

update-script is now
Code:
package_extract_file("LearnPython_1.1.1.apk", "/system/app/Python.apk");
but I still get a syntax error
Edit: I had also tried putting it in a placeholder file, but that didn't help either, even with the added semicolon

Hmm so something seems wrong with my package_extract_file syntax
Even though ive compared it to online update-script samples. Regardless, for now use the copy directories option instead.

marsevern said:
update-script is now
Code:
package_extract_file("LearnPython_1.1.1.apk", "/system/app/Python.apk");
but I still get a syntax error
Edit: I had also tried putting it in a placeholder file, but that didn't help either, even with the added semicolon
Click to expand...
Click to collapse
Retry, cuz i just did it and it works fine.
Created a folder app inside placehere folder
placed my apk inside it
Ran the script, chose option 1
Then chose option 1
Then typed DATA
Then typed app
Then typed app
Then typed 9
Then typed 2
Then flashed the update.zip
Letter Casing matters, if it says SYSTEM or DATA , do that dont do data or system.
Btw, first clear out using the script. So when u run it. type y to clear ur previous work.

marsevern said:
update-script is now
Code:
package_extract_file("LearnPython_1.1.1.apk", "/system/app/Python.apk");
but I still get a syntax error
Edit: I had also tried putting it in a placeholder file, but that didn't help either, even with the added semicolon
Click to expand...
Click to collapse
K i uploaded a fixed one. No file option for now just directory. And added a push to sdcard option. I think wht u were doing was putting it inside a folder and still using the file option.

Yay, it works now. Thank you for creating this and for helping me.

marsevern said:
Yay, it works now. Thank you for creating this and for helping me.
Click to expand...
Click to collapse
Cool, glad to help. Let me know if i can make it more user-friendly

Daneshm90 said:
This script has 2 main uses:
1. Modify an update.zip
2. Create an update.zip
For #1 - You just extract the contents of an update.zip into the placehere folder, modify its contents, and run the script stating to create an update.zip
For #2 - So far these are the options i have in there for create the update-script
1. Copy directories
2. Copy files
3. Create Symlinks
4. Delete file
5. Delete directory
6. Flash boot image
7. Set permissions for file
8. Set permissions for directory
So this script guides u as u select each option, and adds the appropriate command to the update-script file. Then u exit that sub-menu and create update.zip
Heres a video for a better explanation:
This script is a result of me constantly wanting to modify roms before i flash them & users who are unaware/lost as to creating/modifying update.zips.
Download : [Windows]
Click to expand...
Click to collapse
It would be nice if the download link worked and didn't take me to some wierd web sites everytime I click on the download button!

sparksco said:
It would be nice if the download link worked and didn't take me to some wierd web sites everytime I click on the download button!
Click to expand...
Click to collapse
the link works. it's hosted on mediafire and sometime ad page pops up.

sparksco said:
It would be nice if the download link worked and didn't take me to some wierd web sites everytime I click on the download button!
Click to expand...
Click to collapse
sunzoje said:
the link works. it's hosted on mediafire and sometime ad page pops up.
Click to expand...
Click to collapse
Well the reason i do it on something like mediafire is cuz its not xda dependant and that its one of the few sites with no waiting time for downloads. Plus i get to monitor # of downloads, in order to know if something is in demand, hence ill work on improving that.

Daneshm90 said:
Well the reason i do it on something like mediafire is cuz its not xda dependant and that its one of the few sites with no waiting time for downloads. Plus i get to monitor # of downloads, in order to know if something is in demand, hence ill work on improving that.
Click to expand...
Click to collapse
Ok, well I've tried both firefox and IE and they both do the same thing. Can you post a mirror because I've never had any problems with mediafire downloads before? I even logged into mediafire and it still gives me this error:
The website declined to show this webpage
HTTP 403
Most likely causes:
•This website requires you to log in.
What you can try:
Go back to the previous page.
This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.
For more information about HTTP errors, see Help.

sparksco said:
Ok, well I've tried both firefox and IE and they both do the same thing. Can you post a mirror because I've never had any problems with mediafire downloads before? Do I have to log in to mediafire? It gives me this error:
The website declined to show this webpage
HTTP 403
Most likely causes:
•This website requires you to log in.
What you can try:
Go back to the previous page.
This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.
For more information about HTTP errors, see Help.
Click to expand...
Click to collapse
Hmm k sure. Heres an xda attachment.

Did you know you are awesome?
You are awesome

Daneshm90 said:
Retry, cuz i just did it and it works fine.
Created a folder app inside placehere folder
placed my apk inside it
Ran the script, chose option 1
Then chose option 1
Then typed DATA
Then typed app
Then typed app
Then typed 9
Then typed 2
Then flashed the update.zip
Letter Casing matters, if it says SYSTEM or DATA , do that dont do data or system.
Btw, first clear out using the script. So when u run it. type y to clear ur previous work.
Click to expand...
Click to collapse
It works just fine for me too. I just combined Chromatic3.7 rom with httclay's theme by changing the framework.apk and the services.jar files. I also deleted some system apps as well as added a couple of my own. I also put my own bootanimation.zip on there and it works fine.

My first successfull update.zip
Ok so I have messed around with this a lot and I have successfully created a update.zip rom that runs stable. I decided to go with the Chromatic 3.7 rom based off of cm-5.0.8-DS Stable. Feel free to download this and give me your feedback. I take no credit for this rom what so ever. All of the credit goes to Chromersmith and the other devs that made this, not me! This rom is only 1mb larger than the original, about 59mb. What this rom includes:
-reverse nexus style bootanimation (added by me)
-Stock ADWLauncher.apk from cm-5.0.8-DS Stable (has the nexus style launcher, but isn't all themed up. It runs smoother because it isn't as much of a system hog. Added by me)
-apps: Mytouch Music (came with rom not added), 3D Gallery (removed Gallery for same reason), cachecleaner (great for freeing up internal memory), Wireless Tether v2.0.2 for eclair, and of course all the regular stock system apps like YouTube, etc.
And of course you can modify this and re-post your own results as well the same way I did. Isn't that the whole point of this thread?
IMPORTANT! Make sure you read the Chromatic 3.7 thread to get all of the requirements and settings correct after flashing:
http://forum.xda-developers.com/showthread.php?t=679135
I take no responsibility for anyone that breaks their phone because they don't know what their doing!
And of course enjoy:
http://www.mediafire.com/?1zzhoj32oqw

I just finished my second update.zip
Ok so I put a lot more work into this one than I did the first one. This is based off of the CM-5.0.8-DS Stable rom+gapps. I got sick of having to flash the gapps seperatly after flashing the rom, so I just added them in.
-Added the Multitasking OC Kernel and a lot of other things like a black status bar mod, and a custom ADWLauncher icon.
{
"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"
}
-Added other icons to stock apps like music and a few others that I can't remember right now lol.
-Removed the stock Cyanogenmod boot animation and replaced it with the reverse nexus style one (takes up less memory and boots faster, really fast!). Once you get it flashed and get everything set up, reboot your phone and watch how fast it boots up. Mine boots in about a 30 seconds once the boot animation comes on.
Apps included:
-3DGallery (Default Gallery, removed Gallery to save on internal space)
-CacheCleaner (Good system cache cleaner to free up that internal memory!)
-New Phone.apk added from Chromatic3.7 rom (looks very nice btw)
-Wireless Tether v2.0.2 for Eclair roms.
Requirements:
-Danger SPL or Engineering SPL:
If you do not have these or know what they are then do not flash!
-I highly recommend that you have a swap partition of at least 32mb:
If you want this rom to run smoothly, or enable compcache under spare parts app.
Instructions:
-Do Nandroid backup!!!
-I recommend a wipe if your coming from anything other than cm5.0.8-DS based rom, otherwise, just flash it, and then run fix permissions!
-Download and flash as normal:
It will say welcome to cyanogenmod 5.0.8 DS! Do not be alarmed, this is not a stock version of his rom! I did not want to take the credit away from Cyanogenmod and his team for this rom, since I am using so much of it!
-SetCpu:
Install SetCpu. Run app and select auto detect speeds. The kernel on this rom will allow you to overclock way faster than you should. I can run this stably at 614MHz max, and 245MHz min on ondemand. If you go more than this, your phone will probably lock up, and you will have to pull the battery out just to reboot.
-SpareParts:
After Flashing you must change the clock and date color under spare parts found in the settings menu. I changed everything to white because it's a black status bar, but change to whatever color you wish. Also change the Carrier PLMN label color, and the Carrier SPN label color. The only color I change under the notification settings is the Notifications ticker color. Set window animations and transition animations to fast! Check fancy input animations and launcher in memory.
-ADW settings:
Under sreen preferences set Desktop scrolling speed to 0, it's silly fast! Set Desktop overshoot to 50. Select orientation sensor and auto stretch.
Under UI settings check Hide AllApps Bg and Hide AB Bg, and this will make your launcher look much better. Uncheck scrollable widgets unless you use them. Select whatever else you want, I like to select Hide icon labels and closing dockbar as well. The only one I don't check is the tint ab.
Run Firerats Patch:
Download and run Firerats Patch. This will patch things like facebook sync, enable swap partition, and a lot of other things. Dowload and place the fr-patch133.txt file on the root of your sd card. Go to terminal emulator and type "su" and press enter. Type "sh /sdcard/fr-patch133.txt" and press enter. This will bring up a list of commands for the script, along with an example of how the script works. Everything should install correctly unless your don't have a swap partition on your sdcard then it will not install swap. Everything else should install just fine. Once it finishes type "reboot" and your all done! It will take a long time to boot as it is finishing up all of the installations. Be patient and do not interrupt it by rebooting or powering off your phone!
http://forum.xda-developers.com/attachment.php?attachmentid=348484&d=1277328643
Make sure swap or compache is working in terminal emulator. Type "su" and press enter. Type "free" and enter.
I have put a lot of work into this, so that I can use this as a daily driver rom, until a stable froyo release comes out. This rom is really fast once you get it set up correctly. I mean let's face it, we have no idea how long it will take for froyo 2.2 to be realeased. So until then, let's keep on modding!
Disclaimer: I am not responsible if you break you phone because you did not read the requirements or follow the instructions correctly!
Download Link:
http://www.filefactory.com/file/b27a6g7/n/CM-5.0.8-DS-Black-OC-Mod.zip

if we have a lot of files, do we have to write them manually into cmd one by one?

[GUIDE] The Noobs Guide to Android ROM'ing

Work in progress..
Now the purpose of this guide is only one, to guide you through “cooking” your own stock flashable ROM from a shipped ROM… That’s it. It’s not hard but it does help you start the journey of the real dev work. There are to many "Devs" around that just do something like this guide and copy files from other ROMs to theres, And this DOES NOT make you a Developer so please dont go posting stock deodexed ROMs everywhere and call yourself a Developer
Before starting I’m going to assume you have setup the correct ADB Drivers for your device although not really needed to make a ROM, it does make it easier in the long run.
Once you run through this guide you will have a stock ROM with ROOT permissions, DeoDexed, Zipaligned, Busybox and init.d support. From there you can modify your ROM to your hearts content, all this is doing is making your base. The real Dev work is .smali editing, modifying .xmls making your own apps, etc... This guide will just help you to not rely on other members to release "Stock deodexed ROMs"​
Wording:
ROM = An Android Operating system
Cooking = Making your own ROM
Shipped ROM = A Stock ROM for your device, e.g. a RUU.exe etc…
Kitchen = The Dsixda’s ROM Kitchen
ADB = Android De-Bugging
CWM = Clockwork Mod Custom Recovery
zImage = Kernel controls CPU, Battery etc.
Modem/Radio = Controls cell signal, internet etc.
ROOT = ROOT Permissions, access to the ROOT or / of your device, kind of like the Windows folder on your computer.
DeoDexed = Removing the .odex files from a ROM to allow for .apk customizing e.g. Theming etc..
.apk = Android application file
Init.d = Allows the running of scripts such as Memory tweaks and SD-Card tweaks etc.
SU = Superuser
CMD = Windows Command Prompt
MOD = Modification
Click to expand...
Click to collapse
ADB Short codes that may be helpful later:
Type these directly into your CMD window with your device plugged in.
adb reboot recovery = Reboots your phone straight into recovery mode
adb reboot = Reboots your phone
adb push = use this to push files to your phone, make sure you are in the folder with the file you want to push in CMD (Example, adb push c:\android\SystemUI.apk /system/app)
adb logcat = Tells you what your phone is doing.
adb remount = Remounts the partition specified (Example, adb remount /system)
Note 1:
When making a ROM the overall concept is the same for every device that runs CWM or any other custom recovery. The only main difference is extracting the files you need from the Shipped ROM​
Note 2:
It makes it easier to have a shortcut to your kitchen folder and any others you need in your favourites or dektop​
Part 1. Setting up the “Kitchen”
Go to THIS FAQ and choose the method you prefer to install on. If you are running Windows I recommend the Cygwin way. It’s easier and you don’t need to keep booting between Linux and Windows, You don’t even need Linux if you do it the Cygwin way. And please do get the pictorial guide HERE, it helps A LOT for “noobs” and don’t forget to install the Java JDK if you do Windows Option 1. Keep in mind that doing it on Ubuntu IS much faster.
NOW IF Cygwin is to difficult for you, just download Ubuntu and install it next to windows.
Part 2. Extracting the files you need.
There are a few different ways you can do this, the main ones are:
For HTC Devices
Get a RUU.exe from the internet for HTC Devices and extract the system.img and boot.img
Download the RUU and run it on Windows, proceed until you get to the screen with the picture of the phone, see bellow. – (No you don’t need to plug your phone in)
{
"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"
}
Open your Start Menu on Windows
In the Windows 7 search bar type %temp% and hit enter
In the folder that opens click in the search box in the top right corner and search ROM.zip
Drag ROM.zip to your desktop, open and extract system.img and boot.img to your desktop.
________________________________________________
For ANY Android Device (Or if you cant get them any other way)
Using a backup of a stock ROM, This way gives you the ability to make a ROM from pretty much any device that has CWM installed.
Taking the system.img and boot.img from the backup folder
________________________________________________
For Samsung Devices:
Extracting the following from a Samsung Shipped ROM
factoryfs.img (and optionally: cache.img, zImage, modem.bin)
TAR file containing factoryfs.img (optional: cache.img, zImage, modem.bin)
ZIP file containing factoryfs.img (optional: cache.img, zImage, modem.bin)
Any of these above methods can be used and the extracted files placed in the ORIGINAL_UPDATE folder of the kitchen in the next step. If your device is not compatible with these methods check the device list in this THREAD for more guides.
Part 3. Setting up the working folder.
Now we have the files needed to make our ROM let’s get to it!
Go to your kitchen folder then the original_update folder and place your files in It
Start the kitchen by starting Cygwin and typing cd kitchen then ./menu
Hit option “1. Setup working folder from ROM” press enter again
Select the option you want from the list e.g. “(1) system.img and boot.img”
Rename the folder if you wish but it doesn’t matter, hit enter
If you are working from system.img and boot.img you need to run through the extraction process in next step. Most new ROMs use an EXT4 file system so if you are unsure just hit option “2 – Run Ext2Explore (EXT3/EXT4)” and follow the instructions in the Cygwin window (If you are just using a .zip or .tar etc. you don’t need to do this step.)
When that’s finished hit “3 – I’m finished unpacking / abort”
Finally hit Y to see you working folder details once its run through the process.
Part 4. Add the options you want to add
A good thing to do now is, keep it simple. The kitchen is best to use only for making your ROM base, once you have the .zip file most customizing can be done from there unless you need to edit the boot.img etc. but we are not going to get into that in this guide.
Now, we are going to make a simple ROM base optimized for speed and functionality. Follow the next steps and by the end you will be ready to build the ROM.
The most obvious of all, we will add “ROOT Permissions”. So choose option 2.
Always stick with Chains method so hit option F, this won’t take long at all, wait for it to finish the press enter to continue.
Next add Busybox with option 3, hit Y to continue and enter when finished.
Most people disable boot sounds (option 4), I usually just do it later if I choose to.
Don’t worry about Zipaligning because we will do it when we build the ROM.
Next choose option 0 for advanced options.
If you ROM isn’t already DeoDexed choose option 11
If you wish you can backup both folders but I usually don’t bother.
Then select option B to Deodex BOTH folders, this one will take some time, on an HP Laptop core2duo with 4gig of RAM takes about 15 minutes.
Now add /data/app functionality so choose option 13 and select Y to continue, This allows you to move apps from the system folder to your /data/app folder before the install, which in turn allows the end user to uninstall the apps if they wish. This can ONLY be done with certain apps, like apps you get from the market.. YouTube, Google Maps, Twitter etc. DO NOT put dependent apps like SystemUI.apk etc in the /data/app folder.
Next add the Nano text editor on option 14
Next add Command Shell or “Bash” with option 15
Next add init.d support with option 17 to allow the running of init.d scripts, sometimes you may have to manually add the init.d folder to your ROM at the end or before build, either way it doesn’t matter.
Now we are ready to build the ROM and flash it. Understand that all these are optional, if you want to you can just deodex the ROM and go straight to option 99 and build the .zip file. This is just what I recommend you do
Next go to option 99 when you’re ready to build your ROM.
For now you will choose option 1 “Interactive Mode”
When it asks you to Zipalign your .apk’s you can now choose Y and it will quickly run through and Zipalign all the .apk’s in your build.
Once finished, it will start building you ROM.zip file this may take about 5-10 mins on a slow computer or if your CPU is busy already.
When that’s finished it will ask you to either continue with the updater-script or not, this is always a YES for you guys, so hit Y and move on.
Now we need to Sign our ROM, this is always a YES also
The final step is to either rename your ROM or not, it doesn’t matter if you do it now or just rename the .zip file later, so do what you wish and hit enter.
Congratulations you have made your first ROM! You can now backup your current setup in CWM and flash it from your SD-Card, be sure to do a full wipe if it’s the first time and install it.
Note 1:
Sometimes you may get an error and CWM wont flash it, USUALLY this is because the kitchen has screwed up the updater-script but this doesn’t often happen. If it does take one from another ROM on the SAME DEVICE (<< IMPORTANT) and add it to your ROM.​

Part 5. Further Mods and tweaks:

Resources:

Last one..

Well be the first one to reply this is amazing for a person like me who is in the learning process.

Mr.Oug said:
Well be the first one to reply this is amazing for a person like me who is in the learning process.
Click to expand...
Click to collapse
That's the idea
Sent from my Nexus S using xda premium

Awesome work! I'll be following this interesting thread. Thanks bro!
Sent from my GT-S5660 using XDA Premium App

Thank you very much. I've tried and passed from your guide and do I expect further intermediate and advance guide ?

Can't wait to start on this tonight.
I changed my ics lockscreen on my one with help from someone.
Now i finaly can learn to mod a rom on my own.
THX for the tutorial.
Time to learn more from my android

This tutorial worked like a charm.
Nice to see that everything worked and that i learned a lot from it.
Can wait to see how to mod it all.
Keep updating and i will follow the threats.

730000229 said:
Thank you very much. I've tried and passed from your guide and do I expect further intermediate and advance guide ?
Click to expand...
Click to collapse
Coming soon guys
Sent from my Nexus S using xda premium

A good tutorial for those with HTC devices, the tablets such as those from Samsung do not follow the file structure as before and will require a correct Edify definition file to create an update script that will work.

lorinkundert said:
A good tutorial for those with HTC devices, the tablets such as those from Samsung do not follow the file structure as before and will require a correct Edify definition file to create an update script that will work.
Click to expand...
Click to collapse
The kitchen should still sort it out. I've not had a Samsung tablet but its not going to be that different and if the updater isn't formatted properly compare it to a pre made ROM and see what's different
Sent from my Nexus S using xda premium

hi i have i9100G and i used the guide as written from top to bottm but for my i9100g it ask to change the framework.i tried the guide twice and both times i get stuck at the boot...

manishdev said:
hi i have i9100G and i used the guide as written from top to bottm but for my i9100g it ask to change the framework.i tried the guide twice and both times i get stuck at the boot...
Click to expand...
Click to collapse
What do you mean it asked to change the framework. More details mate. Make sure you have the right base ROM for your device
Sent from my Nexus S using xda premium

I'm definitely gonna try this out. Thanks for the instruction!

I want to follow this but i see no specifics on how to set up the kitchen on an Ubuntu machine, i purposely took one of my older dell latitude d420 and completely removed windows and installed the latest version of ubuntu, which is 11.10. would you please if possible, post some specifics on how to go about setting up the kitchen for an ubuntu machine, the faq links are pretty much windows specific. you said that using ubuntu would be much easier to go about this adventure, and i am dying to try it out, but im stuck, I know i have the java files and i have the android sdk all installed and stuff (or so i think). Any kind of enlightenment would be much appreciated,,,,,,,im refreshing this thread like every 2 minutes.....i really wanna dive into this

kevace1 said:
I want to follow this but i see no specifics on how to set up the kitchen on an Ubuntu machine, i purposely took one of my older dell latitude d420 and completely removed windows and installed the latest version of ubuntu, which is 11.10. would you please if possible, post some specifics on how to go about setting up the kitchen for an ubuntu machine, the faq links are pretty much windows specific. you said that using ubuntu would be much easier to go about this adventure, and i am dying to try it out, but im stuck, I know i have the java files and i have the android sdk all installed and stuff (or so i think). Any kind of enlightenment would be much appreciated,,,,,,,im refreshing this thread like every 2 minutes.....i really wanna dive into this
Click to expand...
Click to collapse
Just skip everything cywgin. Cywgin basically runs Linux commands on Windows
Sent from my ARCHOS 80G9 using xda premium

Everything will be heaps faster if you run it on ubuntu
Sent from my Nexus S using xda premium

so basically just do all comands written and just omit any refeernce to cywgin? when i extract the zip from the kitchen file, i get 3 folders and a "menu" file, and a readme text. what command do i have to use on terminal to start the kitchen?

[GUIDE] Rooting the Moann inkPalm 5

Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
EDIT: You can find an extended guide at https://github.com/qwerty12/inkPalm-5-EPD105-root with steps for installing microG.

qwerty12 said:
Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
Click to expand...
Click to collapse
As far as I could gather, with both USB connection and developper mode on, ADB conncection is explicitely rejected. Besides, there is, on InkPalm, below the usuals USB checks, one that reads "...ADB/ADT..." which cannot be checked. The connetion request by wireless ADB, supplying the correct address, is also rejected.... As though the device needed be rooted first !

I haven't tested using ADB over Wi-Fi, but I can honestly say I have had no issues using ADB over USB on the inkPalm. ADB was enabled by default on mine, and not to mention the security of it has been weakened - you don't even need to approve ADB connections for the first time...

So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ? I cannot find any reference to the manufacturer that would eventually grant me permissions-- step ?
So long,
Sixto Quesada

Bis -- I forget to mention that my primary goal is merely to be able to change the language to English, as I think that there are already many possibilities in-built as to the configuration, including the shell !

squsqu6 said:
So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ?
Click to expand...
Click to collapse
Is debugging mode actually on? Open the settings, go to the highlighted page and
{
"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"
}
turn the highlighted setting on (make sure the setting above it is on too - it will let you install external APKs)
You can follow these steps to show the Developer Settings, that's up to you: https://github.com/epodegrid/epd106-ADB#step-1-install-adb
squsqu6 said:
Bis -- I forget to mention that my primary goal is merely to be able to change the language to English
Click to expand...
Click to collapse
If you really can't get ADB to work, then there might be another way. Install the APK of my launcher fork (how you do that is up to you - you can try using the built-in browser or transferring the APK over MTP and using the file manager [which I've never opened] to install it).
In the new launcher, tap-and-hold the Settings icon (the one with a dark background),
choose Additional Settings and tap Locale. Then follow the instructions here: https://github.com/philips/inkpalm-5-adb-english#change-the-language

ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.

This worked great for me thanks a lot. I have a quick question if you know it. Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)? The stuff you can do with the home button/logo button in settings is pretty limited.

Thanks.
reaverclan said:
Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)?
Click to expand...
Click to collapse
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button

qwerty12 said:
Thanks.
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button
Click to expand...
Click to collapse
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible. So I guess it's for another xiaomi device or base android version. I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.

reaverclan said:
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible.
Click to expand...
Click to collapse
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.
Click to expand...
Click to collapse
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).

qwerty12 said:
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).
Click to expand...
Click to collapse
Ah I see that's clever. It's not the end of the world and yeah I think it's cause root explorer does what you said about invoking the thing directly. I just use the stock app to only install and that's it. My journey so far is shown here and regardless of the jank it has been a great device. https://www.mobileread.com/forums/showpost.php?p=4140508&postcount=155
Thanks again for the time to make it even greater. Only thing that sucks is no stock img to un brick if something goes to far. Hopefully someone leaks that at some point. This device seems pretty new to the market still.

squsqu6 said:
ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.
Click to expand...
Click to collapse
I now have a new, but old !, trouble : battery life. I have enforced all saving possibilities available --from standard menu, from E-Ink Launcher, and, from RomToolBox, processors speed slowing--, and, yet, after 8 hours of use, InkPalm battery is totally empty, even though being totally user-idle --not a single user application being active according to linux 'top' request. Conversely, Kobo reader battery lasts for days in reading mode.
My question : would it be thinkable any possible trick of triggering the sleeping function without pushing the red button, so as to keep the screen as it is --allowing the reading of actual page until next (not a book, a musical partion, which takes longer !)--. Bypassing by script the red button action, or other ? --Note : the screensaver option allows for user-image, like a screenshot, but it requires to move it to the proper place and to renew it at every page...
Sorry for being so long, I am far from being familiar wich Linux (Android).
Greetings,
S. Quesada