How To Port CWM Recovery on Marvell Devices PXA988/PXA1088
This Guide working is only tested on PXA1088 Devices, But Maybe Work on PXA988 and and others Marvell Powered Devices too.
The Guide Provided by Marcone Noise / @marcone093 if you copy give a proper credits.
NOTE:
Code:
Do This At Your Own Risk!
Remember, Am not Responsible for Any bricked devices, Wars and explosions, or because you simply lost your girlfriend's nudes,
be aware that YOU are doing the procedure on your own, if you do not know what you are doing give up now, in case something goes wrong my hands are tied
Requirements:
Android Image Kitchen Tool. -You can download here
Your Stock or Base recovery.img - Which is functional on your device.
The Port recovery.img - CWM or any other recovery you want to port.
Notepad++
A brain and patience.
let's start?
- Extract Your Base/Recovery
- Extract the recovery you want to port - (on different folders obviously)
You will now have two folders: BASE And PORT Folders.
{
"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 split_img on both folders and copy & replace recovery.img-zImage from base to port.
Now go to ramdisk folder and then copy from BASE to PORT:
-ueventd.rc
-ueventd.goldfish.rc
Aand other files you don't have in the PORT / ramdisk folder
Compare The Fstab.PXAxxx
-if your port recovery don´t have like me, copy from base to port
-in your base recovery don´t have, just ignore or checks and set your mount points.
Now You Need To compare default.prop, Just replace these lines From the BASE to the PORT.
ro.product.model=
ro.product.brand=
ro.product.name=cm_ here maintain the cm_ and set with your device codename
ro.product.device=
ro.product.board=
ro.product.manufacturer=
ro.build.product=
ro.board.platform=
ro.cm.device=
And search more codename and replace with your codename on some lines of default.prop like this:
Now go to /randisk/etc folder then compare recovery.fstab, replace your mountpoints from BASE to PORT.
NOW REPACK PORT RECOVERY AND TEST IT
DONE
I successfully ported a CWM to the Galaxy S3 slim using this method
sorry for my bad English
HIT THE THANKS BUTTON IF I HELPED YOU
What about the "libs" folder and "sbin" ?
i need help to understand that, the stock img don't contains too many files on sbin and the port img contain's a lot of files onto sbin folder, my phone is not booting on recovery, kitkat based device
Related
Hi ,
i want to compile kernel with compat-wireless 3.6 compatibility (drivers for monitoring mode / packet injection) , so for start
i compiled kernel from asus source
changed kernel config
then i have make kernel image then blob
and this is where i need to help
after flashing blob to TAB i have bricked it , 2 times already, i have it now from service.
first time i tried to flash blob from .zip
second time i tried dd to /dev/block/mmcblk0p4
i need help with this.
thank you
...........................................................
slider SL101 with revolver 4.2.1
external USB adapter Edimax-EW-7811Un (rlt8188cus chipset)
{
"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"
}
with working monitoring mode / packet injection
Fluffinko said:
Hi ,
i want to compile kernel with compat-wireless 3.6 compatibility (drivers for monitoring mode / packet injection) , so for start
i compiled kernel from asus source
changed kernel config
then i have make kernel image then blob
and this is where i need to help
after flashing blob to TAB i have bricked it , 2 times already, i have it now from service.
first time i tried to flash blob from .zip
second time i tried dd to /dev/block/mmcblk0p4
i need help with this.
thank you
...........................................................
slider SL101 with revolver 4.2.1
external USB adapter Edimax-EW-7811Un (rlt8188cus chipset)
with working monitoring mode / packet injection
Click to expand...
Click to collapse
Did you include an appropriate init ramdisk? A flashable kernel package usually includes the blob, a META-INF folder and a system folder. The blob, when unpacked, includes at least a blob.LNX (which is the same as a boot.img) which when unpacked further contains the init ramdisk file system and the kernel zImage. The META-INF folder has the updater-script and maybe a few other files and the system folder may have an lib/modules folder for the modules built with the kernel and possibly an init.d folder for startup scripts and such. The init ramdisk has the system initialization files for the underlying Linux system that Android runs on top of.
XDA PORTAL
Click to expand...
Click to collapse
Hello everyone
In this tutorial i will show you how to integrate the recovery into a custom rom.
This way users will not have to install it separately
{
"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"
}
REQUIREMENTS:
You must know how to build a custom rom using Android Kitchen.
You must know how to edit an updater-script using Notepad++.
The WORKING folder of your rom (the one you get from the android kitchen when you extract system.img or zip folder or system.tar).
The recovery's flashable zip.
For this tutorial i am gonna use the PhilZ Touch CWM as example but this method is universal for all recoveries.
So, let's start:
1. Create in the kitchen's WORKING folder, a new folder and name it system2 (in your case working folder's name is gonna be different).
2. Extact the recovery's system folder contents into the system2 folder (the one previously created).
3. From the recovery's META-INF folder open, using Notepad++, the updater-script.
In my case looks like this:
4. Before proceeding, let me explain what is going on with the following lines:
package_extract_file("system/bin/recovery.tar", "/system/bin/recovery.tar");
package_extract_file("system/bin/taimport", "/system/bin/taimport");
package_extract_file("system/bin/taimportx", "/system/bin/taimportx");
package_extract_dir("system/btmgr", "/system/btmgr");
----- package_extract_dir(” “, “/”) – This command extracts all the files from the folder mentioned inside first quotation to the directory inside second quotation. -----
So since you created a new folder named system2, the above lines should be edited and look like this:
package_extract_file("system2/bin/recovery.tar", "/system/bin/recovery.tar");
package_extract_file("system2/bin/taimport", "/system/bin/taimport");
package_extract_file("system2/bin/taimportx", "/system/bin/taimportx");
package_extract_dir("system2/btmgr", "/system/btmgr");
5. Now open, using Notepad++, the updater-script for your rom.
6. Now copy the edited lines from the recovery's updater-script into the updater-script of your rom (add them at the bottom). Remove the show_progress lines. Now save the file.
7. Now you can build your rom and enjoy the integrated recovery!
8. Happy rom building
reserved
Too good
So you are back with your pc i guess
Awesome! Definitely looks much, much better than the "ms-dos" clone I see in my device
Bro @DaRk-L0rD
Very nice and very clear explained, specially for new ones :good:
Very clever tutorial my friend!! :good:
keep rocking...
Nice guide..
U are featured on portal. Congrats
Sent from my C5303 using XDA Premium 4 mobile app
Congratz bro.your post is on portal.nice job
Great, its work for me! :highfive:
My Question is about editing kernel's built In Recovery.
the kernel has cwm recovery but i had a new one :victory: so i want make it permanently by editing kernel's recovery
But when i replaced files i fount that the new cwm has folder etc that isn't exist in the kernel so i added it with the files in it and repacked
so the question is
Will That Make Any Thing Wrong In The Kernel?
If yes
What Would Happen If i flashed it?
and if the kernel failed to be flashed what would happen to the phone ?
The Phone Is Galaxy Y Duos
In the worst situation,your phone will get blasted and you'll suffer from Hypothermia.
Make a backup and then flash the kernel.Nothing will happen until or unless your recovery is not integrated properly.You might probably face a black screen though.
I already flashed it and recovery is working but i got strange problem that after phone boot up 3 seconds or 5 then it gave the boot animation and open again then the same give the boot animation and open and still luke that until i flash the original kernel
so where is the problem?
to know that the cwm that i add is the same files that i removed from the original kernel except the etc folder that i add .
Hazem442 said:
I already flashed it and recovery is working but i got strange problem that after phone boot up 3 seconds or 5 then it gave the boot animation and open again then the same give the boot animation and open and still luke that until i flash the original kernel
so where is the problem?
to know that the cwm that i add is the same files that i removed from the original kernel except the etc folder that i add .
Click to expand...
Click to collapse
you should not be adding etc folder... in normal boot /etc is symlinked to /system/etc
{
"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"
}
maybe add recovery folder put your files there and copy to /etc by using recovery.rc :|
(°_o) said:
you should not be adding etc folder... in normal boot /etc is symlinked to /system/etc
View attachment 2813182
maybe add recovery folder put your files there and copy to /etc by using recovery.rc :|
Click to expand...
Click to collapse
thanks for reply
and the kernel worked well after removing etc and add the file inside it in sbin folder
:laugh:
I got the Full Deodex Rom 1.13.
Use the JoelDroid Tool Lollipop Batch Deodexer V 2.5
The problem is that I can not install the Zenfone Selfie ZD551KL.
Does anyone have any solution for this?
Or someone create a Full Deodex to Rom 1:13
I would have to specifically create an image to flash in ZD551KL?
Or was it a ZIP file to install via ADB Sideload ??
Because we have no TWRP Recovery on this unit.
I look..
[Tutorial] JoelDroid Lollipop Batch Deodexer V 2.5
This tool gives us the facility to make a deodex our system for some applications they want serivrá modding them, for those who do not have much knowledge haha and use the mods out there does not help us much. :
Here is a tutorial on how to use this tool.
Download: http://forum.xda-developers.com/attachment.php?attachmentid=3268390&d=1429332195
Characteristics:
* Review the requirements before installing
* Displays a counter of the odex apps. Priv-apps - Framework apps.
* Displays a counter of my deodex Priv-apps - Framework apps.
Prerequisites:
* Windows with .NET Framework4.5
* Java 7 or higher
Use:
* Make sure you have java installed with the path configured correctly.
* Run the application in a directory without spaces for example: C:\JBD
* Unzip the rom odex in a directory without spaces. For example: C:\mirom
- So in the C:\mirom be subfolders "system" and within the System Folder, folders apps, priv-app framework must be present, you must select "system".
* Run the application, then the directory will be asked where is the rom odex
* Deodexar
{
"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"
}
Thanks!
Very good! Thanks!
Well I can not do with these two applications because not Linux but Windows use. And then it would be nice a file ready update-binary and compatible updater-script to instalart then Deodex the device.
Selfie ZD551KL
I've deodexar the Stock rom selfie ZD551KL. I just can not install because of the error in updater-script.
In fact I do not even have the original file to the selfie ZD551KL.
What I was tested in a template JoelDroidLollipopBatchDeodexer the page.
This man did not work ...
I found no script created for Deodexar Rom in selfie ZD551KL.
Here for you ..http://www.mediafire.com/download/84...erTemplate.zip
Can you provide the actual WW deodexar file that works with you? also Can provide how can we install it?
Had once a little boredom and made a MOD for the themeing of Custom Splash Screen. Just like S8(+) and S9(+). You can change now pictures without to modify and flash the bootloader (up_param.bin).
Important: The MOD only works with Exynos-9810-based devices!
Important2: Its untested, but works on my s8+ and on s9(+).
[FONT="]Neither I nor XDA is responsible for any damage to your device. You're flashing at your own risk![/FONT]
[FONT="]Before you start, make a Nandroid (backup) of your system. Safe is safe![/FONT]
Changelog
Changelog v1.0
Release
What you need?
a custom recovery like >>TWRP<<
my exynos9810_N9_logochanger Zip
skills how to modify/repack/drag&drop into zip files
skills how to flash MODs
Pictures to download (only examples)
{
"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"
}
Download
View attachment exynos9810_N9_logochanger.zip
View attachment exynos9810_logochanger_stock-N9.zip
How to Flash
Place the zip on the internal/external memory.
boots into Recovery
then click on "install" in the TWRP
searches for the folder where the zip file was placed
and flashes it by clicking on the zip and dragging the slider to the right at the TWRP
rebooting
How do I change the boot logo in the template?
open the exynos9810_N9_logochanger zip (with WinRar or 7zip) and replace the logo. jpg with another image of your choice
the new image must be renamed to logo. jpg again. Otherwise it won't work!
How to return to the Stock logo?
You don't like the custom logos anymore?
then just flash the zip appropriate for your device:
exynos9810_N9_logochanger_Stock_S9 (for Galaxy Note 9)
Troubleshooting
If your hanging in a bootloop without access to twrp, please reflash the bootloader via odin. TWRP and system boots up again.
Note:
Not all images work, the best results are achieved if you just edit the stock image.
Credits
Samsung
arter97
me
So, that's it, too. Leave a "thanks" here if it was helpful or you even liked it.
Does the guide need to be updated with some additional info?
The Tool doesn't work anymore..
please provide an update to code..
no longer works on note9 with Pie update