Database Info

[OBSOLETE] unofficial CyanogenMod 9/ClockworkMod Recovery 5 for Allwinner A10 devices

this was a work-in-progress development project for porting CyanogenMod 9 (ICS/4.0.4) and ClockworkMod Recovery 5 to Allwinner A10 devices.
but my CM9 is obsolete now. if you want to get CM9, please refer other active projects.
currently here is only for my miscellaneous work for Allwinner A10 devices. if you have a question about development work for A10, you may post it on here. but I can't guarantee any answer.
* links to other active CM9/CM10 projects
http://forum.xda-developers.com/showthread.php?t=1821398 CM10 for many A10 tablets by Christian Troy
http://forum.xda-developers.com/showthread.php?t=1760929 CM9 for many A10 tablets by Christian Troy
http://www.slatedroid.com/topic/33820-ics-404-ivi-cm9-firmware-for-novo7-advanced-btgpsusb-audio/ for NOVO7 Advanced(1) by tsynik
* links to other active AOKP projects
http://forum.xda-developers.com/showthread.php?t=1760931 for many A10 tablets by Christian Troy

* How to install ClockworkMod Recovery 5
1. (if you don't have official ROM and flash tool,) make backup of recovery partition
2. download recovery.zip and unzip it
3. put install-recovery.sh and recovery.img(recovery.cpio for GB ROM) on /sdcard/ *1 *2
4. run install-recovery.sh from root shell or any apps which can run a script (terminal, gscript, etc)
e.g.
Code:
> adb shell
$ su
# sh /sdcard/install-recovery.sh
* How to boot recovery
1. put reboot-recovery.sh on /sdcard/ *1 *2
2. run reboot-recovery.sh from root shell or any apps which can run a script (terminal, gscript, etc)
e.g.
Code:
> adb shell
$ su
# sh /sdcard/reboot-recovery.sh
*1 if you are using CM9, install-recovery.sh and reboot-recovery.sh are already installed on /system/bin/. if you are not using CM9, you can put these scripts on your ROM.
*2 /sdcard/ is referred as "SD card" on Android, but it may not be physical/external "SD Card". please make sure files are placed on /sdcard/.
* How to boot recovery (alternative)
for ainol NOVO7 AdvancedII/Aurora/Elf
BACK + POWER
for other tablets, please find the way to boot recovery.
* How to control ClockworkMod Recovery 5
for ainol NOVO7 Advanced
VOL-: down, VOL+: up, POWER/MENU: select, BACK: back
for ainol NOVO7 AdvancedII/Aurora/Elf
VOL-/MENU: down, VOL+/HOME: up, POWER: select, BACK: back
* How to install CyanogenMod 9
1. download update.zip and put it on internal NAND flash or SD card (don't unzip it)
2. install ClockworkMod Recovery 5
3. reboot recovery
4. install update.zip
5. wipe data/factory reset *3
6. reboot
*3 only if you are upgrading from non-CM9 ROM (CM9 1st install)

reserved

reserved

Hi,
I was not shure if I should by the NOVO7 Advanced, but now as I see that there is (or will be) CM avaidable for it , I will buy it.
Thanks for porting
T

saulmrt said:
I was not shure if I should by the NOVO7 Advanced, but now as I see that there is (or will be) CM avaidable for it , I will buy it.
Thanks for porting
Click to expand...
Click to collapse
thank you for your message.
but I don't recommend to buy it because of my CM, unless you like/want to do porting work. my CM is not perfect at all.

I ordered it because I thin it is a good piece of hardware, you don't have to be afraid that it was only because of this port.
Well as soon as I have this tablet I will try to help with porting as good as I can.

Great work so far OP!
I have the Ainol Advanced waiting for me at the post office. There's already a healthy community over on slatedroid but it's always good to see CM getting ported!

thank you for your comments.
I wish I'll re-upload my files in this weekend...(it's not technical reason at all)

FILES! FILES!! My Kingdom for FILES!!!

i have been longing for it and i suggest to launch a new board for it. it's been a popular device in PRC, taiwan & hong kong already! please note that the 2.0.3 & 2.0.4 firmwares are quite buggy, and i would advise all to flash 1.8 modified version which is stable and can score 18XX at quadrant.

I've been trying to do this for my A10-based tablet too. Can you up the download links again? Maybe I can improve some things.
Edit: I'll upload a dump of the stock ROM soon. I also found a tool to (partially) extract the LiveSuite *.img files.
Edit 2: WiFi chipset of the tablet is a Realtek 8192CU, Freescale MMA7660 accelerometer & Goodix touchscreen.

FezzFest said:
I've been trying to do this for my A10-based tablet too. Can you up the download links again? Maybe I can improve some things.
Edit: I'll upload a dump of the stock ROM soon. I also found a tool to (partially) extract the LiveSuite *.img files.
Edit 2: WiFi chipset of the tablet is a Realtek 8192CU, Freescale MMA7660 accelerometer & Goodix touchscreen.
Click to expand...
Click to collapse
sorry, I need some time to prepare my site. it seems I don't have enough time on this weekend but I hope I'll get some time on next week.
I guess you are talking about this tool: http://www.mp4nation.net/forum/viewtopic.php?f=24&t=20476
I'll try it when I get enough time
and thank you for your information. if you want to add your tablet to my support list, I need more detail info (please see post#4). if you can do it yourself, please just wait for some day... I'll uploaded my git repo too.
(nothing is secret, just I need my free time!)

I found it on a different website, but I think it's the same tool.
This is a dump I made of the original partitions with dd:
boot.img: http://dl.dropbox.com/u/28680222/XDA/tablet/boot.img
misc.img: http://dl.dropbox.com/u/28680222/XDA/tablet/misc.img
rootfs.img: http://dl.dropbox.com/u/28680222/XDA/tablet/rootfs.img
recovery.img: http://dl.dropbox.com/u/28680222/XDA/tablet/recovery.img
system.img: http://dl.dropbox.com/u/28680222/XDA/tablet/system.img
I haven't included cache, data and internal sdcard because I don't think they are of any use for ROM development.
Edit: attached required output from commands in post #4. Find /sys doesn't work because adb can't find find

Hi fun thanks for the pm found my way here at last
i have not managed to get into stock recovery on the Excel so far so i have not made any kind of file dump or backup i will see how it goes and keep my eye on this thread i have root and terminal emulator i have installed superuser as an app from market
can i type a command to get into stock recovery or would you think there is no stock recovery
cheers

Recovery is also a mistery to me. I tried 'adb reboot recovery' but I guess that was too simple. There is a recovery partition (I created an image with dd above) but haven't found a way to boot into it. I'd love to know how the topic starter got clockworkmod working

Mitred said:
i have not managed to get into stock recovery on the Excel so far so i have not made any kind of file dump or backup i will see how it goes and keep my eye on this thread i have root and terminal emulator i have installed superuser as an app from market
can i type a command to get into stock recovery or would you think there is no stock recovery
Click to expand...
Click to collapse
hi.
stock recovery should work because it's necessary to run "factory reset" from setting menu on stock rom. (it's done automatically so we can't use it to enter recovery mode. I just explained about functionality)
and recovery is not necessary for now. what I need is not complete dump image. I just want to know hardware related things so tar archive is enough.
permanent root is not necessary too. sometimes rooting app makes brick, so I don't recommend it. I don't recommend to modify stock rom unless you have official rom and flash tool.
if adb shell is root shell, then rooting is not necessary at all. if adb shell is not running, or non-root user shell, temporary root is necessary to get root shell.
then, you already got root shell, right?
then, please check following commands are available in your rom, "tar" and/or "busybox".

FezzFest said:
Recovery is also a mistery to me. I tried 'adb reboot recovery' but I guess that was too simple. There is a recovery partition (I created an image with dd above) but haven't found a way to boot into it. I'd love to know how the topic starter got clockworkmod working
Click to expand...
Click to collapse
"adb recovery" doesn't work. I'll post how to enter recovery. please wait for a moment.
anyway, please tell me name of your tablet, or link to web, or photo.
if busybox is in your rom, "busybox find /sys" will work.

It's a Bmorn V11. The 'busybox find /sys' command indeed works, I have attached the output files to the zip file in this post.

FezzFest said:
It's a Bmorn V11. The 'busybox find /sys' command indeed works, I have attached the output files to the zip file in this post.
Click to expand...
Click to collapse
i'm guessing you are referring to the Bmorn V11 rebranded for Promedia ?
If so, keep in mind that there are 2 versions of this tablet, one with 3600 battery and one with 3200 battery, the 3200 version has the goodix_touch drivers.

[p500][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just long press outside a menu (2 sec and slightly change pressure after the delay)
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
LG Optimus One P500 (p500)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/p500
Click to expand...
Click to collapse
XDA:DevDB Information
[p500][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the LG Optimus One P500
Contributors
Phil3759
Version Information
Status: Testing
Created 2014-04-21
Last Updated 2014-04-21

Cool.
Upon which CWM version is this based? Note fundamental differences between newer 6.0.* after June 16 -- can flash new Kitkat ROMs and older 5.* which flash older ROMs.
Because of space limitations -- whole business must fit < 5 meg, functionality such as partitioning SDcard was removed from the 6.0.* versions.
What do we have in this version?

Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???

ujilraj said:
Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???
Click to expand...
Click to collapse
If you can't read OP and follow links, just do not test
I am fine with this

Unable to flash!
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:

I suggest that the first link needs to highlighted... My mistake, but honestly i didn't notice a link below the title...

sumansur2008 said:
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:
Click to expand...
Click to collapse
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.

Dovidhalevi said:
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.
Click to expand...
Click to collapse
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.

indigobv said:
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image
Click to expand...
Click to collapse
This should be the error. Then flash_image the 6.0.4.6 which fits. Do it immediately or else .... I believe I had that happen once. I posted about that 5meg limit above. Did not try this because of the limit.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.
Click to expand...
Click to collapse
Maybe the op should post a proper flashable zip instead. Problem is that status 7 itself might mean a brick.

Dovidhalevi said:
Problem is that status 7 itself might mean a brick.
Click to expand...
Click to collapse
Thanks for the heads up, I actually didn't try booting in recovery after the status 7 error. Now I can confirm that it tries to flash it even if it shows the error and then forces the phone to go in fastboot mode until the problem is solved.

I built using official p500 armv6 repo
They should fix the device recovery size in that case!!

Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk

eran32 said:
Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk
Click to expand...
Click to collapse
I believe this is simple a nice GUI for flash_image. Aint no such thing as no risk so beware.
The method I suggested should be safe if one flash_image's a valid recovery immediately after any error (but I make no guarantee!).
I advise against flashing this recovery version at this point because it is clearly too big for our device. We can get along just fine without a touch interface if need be. Never had one.
Changing board partition sizes is not a readily done simple matter by any means.

[DEV][RECOVERY] TWRP Recovery 2.7.0.0

TWRP Recovery
For Galaxy Fit
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
BUGS:
If you have found a bug, please consider posting it here.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
@chraso: Hosting & for providing Compatible flags
Me: Compiling

CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.

DOWNLOAD:
http://www.mediafire.com/view/?xum64uit9a43q6s
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!

About the current build:
STABLE.
Reboot to system bug now fixed.

Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2

TpupLpasa said:
One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works.
Click to expand...
Click to collapse
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail

TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
1st - install PhilZ Touch Recovery 6.40.1.
2nd - install twrp.

My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.

Ok, thanks.
update
Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:

Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
I would advise against this. I tried it and it soft bricked my phone.
I will wait for the official release, which I hope will be soon. I really like TWRP.
jemail

TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
iSanechek said:
Ok, thanks.
update
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:
Click to expand...
Click to collapse
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: remooved

belyava said:
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: http://yadi.sk/d/IAr6Z_OvQohqq
Click to expand...
Click to collapse
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail

jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
No success I am afraid.
jemail
Click to expand...
Click to collapse
sorry, I must have made a mistake. I''ll check tomorrow. Sorry for the inconvenience

jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail
Click to expand...
Click to collapse
Ok, try this one

belyava said:
Ok, try this one
Click to expand...
Click to collapse
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail

jemail said:
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail
Click to expand...
Click to collapse
There are a lot of method nowadays for unpack-repack and most of them fails to make a proper repack, so you'll have booting problems like you had when you tried to do it yourself. I just told @belyava to do unpack-repack because he did this with the recovery (TWRP - had same reboot to system issue) of his device successfully. Thanks @belyava for this help.
Everything expected to work. However, you can always report bugs with a proper recovery logfile.
Updated download link with a new mediafire link. The latest build can be now labelled as STABLE build.

hi anyone have got it if possible in rar zip for this recovery.

ahmetakin said:
hi anyone have got it if possible in rar zip for this recovery.
Click to expand...
Click to collapse
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.

swat4samp said:
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.
Click to expand...
Click to collapse
I can't speak for your ROM, but for me back up ( 3 1/2 mins max) and restore (3 1/2 mins max).
jemail

Ok yesterdeay install with terminal emulator thanks.

[Guide] [SC8830/SC7731/SC9830] Custom Recoveries Porting guide for Spreadtrum phones.

Code:
[CENTER][COLOR="Red"]Your warranty is now void.[/COLOR]
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research before asking help and reporting bugs and please read the entire OP.
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.[/CENTER]
All suggestions and helps are welcome here so please help me in improving this thread by suggesting your ideas.
This guide will work for any SPRD phone (any SPRD chip) from Old versions of android to latest Oreo but recoveries that I provided in this thread will work for devices from KitKat to Marshmallow no guarantees for older or newer versions.
Buckup! Backup! Backup!​
Before modifying system it's highly recommended to have full dump of your device. So don't forget to take backup.
It's simple to get custom recovery for rooted users as they can directly backup, modify and flash recovery or boot images on the go with the help of root. But non-rooted users need to do some extra which will be explained later. Follow the below steps:
=>Download and setup AIK (Android Image Kitchen)
=>Grab your stock_recovery.img
For rooted users​Install Flashify, Rashr, Partitions Backup or like apps (available on play store for free) and backup the stock recovery. If you are using Flashify to backup you have to rename the backed up image with .img extention
For non-rooted users​Download your stock firmware which will be in .pac extension extract it using this guide and copy the recovery.img
=>Now download custom recovery (for downloads see 2nd post)
=>Port recovery
For PC version of AIK​
• Extract the AIK on desktop in a folder (extracting inside other folder(s) is not recommended)
• Place stock_recovery.img (use the name recovery.img only I added stock to refer the image) in earlier extracted folder
• Now double click on 'unpacking.bat'
• Now you'll see two folders 'ramdisk (mostly executables)' and 'split-img (kernel to boot recovery) rename those folders like this 'ramdisk.s' and 'split_img.s' (renaming is used to avoid copying/moving needed files)
• Now delete the earlier pasted stock_recovery.img and paste custom_recovery.img (rename it to recovery.img)
• Unpack it just like stock_recovery
• Delete the split-img and rename the 'split_img.s' to split_img
• Open recovery.fstab from /ramdisk.s/etc (stock recovery's fstab) and /ramdisk/etc (custom recovery's fstab) using Notepad++ or with your favorite note editor. In case of TWRP recovery this file will be named as twrp.fstab if there is recovery. fstab you can ignore it.
• Edit the partition names and mount points in custom recovery with your stock recovery's fstab. But in most cases the mount points will be shown like this 'mmclbk0p17 for system partition' in that case you need to change custom recovery.fstab with the mount points of your device, to find out mount points of partitions install Diskinfo from play store and enable all options in it which will show complete information regarding each and every partition on your device
• At last double click on 'repackimg.bat' now you'll see 'image-new.img' which is ported custom_recovery.img for your device
• The final step is flashing the recovery. It's easy for rooted users simply use Flashify app to flash. For non-Root users you need to flash it over fastboot mode for this look at this thread.
For mobile version of AIK​
You can also port the recovery on-the-go using AIK-Mobile unfortunately to use this needs your device must be rooted with BusyBox (Stephen (stericson) is recommended) installed.
It's a flashable zip but you can extract the zip and place the files manually. Follow below steps for setup:
• Extract the AIK-Mobile.zip
• Paste the AIK-Mobile folder under data/local of extracted zip to /data/local
• Paste files under /bin of extracted zip to /data/local/AIK-Mobile/bin
• Make sure all files including folders are having these permissions "-rwrx-xr-x-".
For placing files, changing permissions and executing scripts 'Explorer' by speed software is recommended.
For porting follow above steps (steps in PC version of AIK) the only difference here is .bat files of PC version will be as .sh in mobile version which are to be executed as root for unpacking and repackaging images.
Note:Follow the instructions properly, don't quote entire OP while asking for help. Due to some touch related drivers missing in kernel of recovery in some devices touch recovery won't work in that case please use Non-Touch recovery. In lollipop or later versions don't flash <3.x.x versions which may result in SD card mounting issues and even flashing errors. First test the recovery that you ported by flash a simple mode (I prefer AIK-Mobile since it doesn't modify the system partition hence there is not chance of bootloop. Also see whether wipe options works properly or not in some devices wiping (even cache) takes ~10m in that case goto settings check the option "use rm -rf instead of formatting".
Hit thanks button instead of posting thanks it'll boost me to create more threads like this.
Credits:
Advan S4P [Official] (fb group), SuDroid Tech (fb group), @@ki , @Jitheshwar (it's me), and some aliens from other universe.​
Created: 27-09-2017
Last Updated: 27-09-2017

Custom recovery downloads
1) TWRP recovery images
2.7.0-0
2.8.5-0
2.8.5-0
3.0.0-0
3.0.2-0
3.0.2-0
3.0.2-0
3.1.1-0
2)Cyanogen recovery (for lollipop)
3)Cyanogen recovery (for kikat)
4)MIUI recovery
5)Ultra CWM
6)Temporary CWM (only for KitKat and older
7)Temporary Philz (only for KitKat and older)
Temporary recoveries provided here are not for porting. You can flash those zips directly from you stock recovery these recoveries will have basic functions like flashing ROMs, Wiping (in some devices it'll take too long to wipe so just use factory reset option of stock recovery and then flash this recovery finally the ROM. Back up option of recovery might not be fully functional. Scrolling is glitchy but it'll work when you press button. These are more for users who are unable get working recovery

Reserved for FAQ.

Do you know how to port boot to help twrp recovery mode boot up ? Please guide me.
Boot Secure & twrp

Jitheshwar said:
Click to expand...
Click to collapse
I have fpt x50 , vn phone , which runs android 7.0 with sc7731c
Will this guide work ??

Jitheshwar said:
..
Click to expand...
Click to collapse
Sir...
you wrote that delete only split_img.s.....
but not ramdisk.s.......
Is there any problem will arise when repacking with ramdisk.s with ramdisk and split_img of custom recovery?

HemanthJabalpuri said:
Sir...
you wrote that delete only split_img.s.....
but not ramdisk.s.......
Is there any problem will arise when repacking with ramdisk.s with ramdisk and split_img of custom recovery?
Click to expand...
Click to collapse
Read again carefully you have to pack custom recoveries ramdisk with stock split_img and reversing the process will mess up the recovery and then you have to flash the stock recovery. So read the guide carefully step-by-step and follow the process exactly unless you know different working method.

unknown said:
I have fpt x50 , vn phone , which runs android 7.0 with sc7731c
Will this guide work ??
Click to expand...
Click to collapse
Give it a try it may work. But none of the recoveries that are provided here will work for your device, you need to find Android 7.0 and later recoveries which will be compatible with your chipset model.

kaew158 said:
Do you know how to port boot to help twrp recovery mode boot up ? Please guide me.
Boot Secure & twrp
Click to expand...
Click to collapse
TWRP has nothing to do with boot.img. If you are not able to boot to recovery try different key combination. Is you messed up recovery too then flash it via fastboot and then flash the stock Rom.

Jitheshwar said:
Click to expand...
Click to collapse
Sir finally the process is to pack
⇛split_img of stock recovery ......
⇛ramdisk of custom recovery you listed by replacing recovery.fstab file
Some doubt are ... from where the recoveries are taken sir?
another one is can i port a custom recovery made for similar device to my device by using these steps?
Thanks for supporting spreadtrum devices....

HemanthJabalpuri said:
Sir finally the process is to pack
⇛ramdisk of recovery you listed by replacing recovery.fstab file
⇛spit_img of stock recovery right......
Some doubt are ... from where the recoveries are taken sir?
another one is can i port a custom recovery made for similar device to my device by using these steps?
Thanks for supporting spreadtrum devices....
Click to expand...
Click to collapse
Kindly go through the entire post carefully, I believe I provided sufficient info that even a newbie can port.

Jitheshwar said:
Kindly go through the entire post carefully, I believe I provided sufficient info that even a newbie can port.
Click to expand...
Click to collapse
Sir I read entire post...
But there is no line that states to delete ramdisk of stock recovery....
Check and add that line sir....
Also process of installing AIK for Mobile changed...
We directly install and use the AIK as all other apps on playstore

HemanthJabalpuri said:
Sir I read entire post...
But there is no line that states to delete ramdisk of stock recovery....
Check and add that line sir....
Also process of installing AIK for Mobile changed...
We directly install and use the AIK as all other apps on playstore
Click to expand...
Click to collapse
I clearly stated all the steps in an easy and simple way. My kind request to you to read the post again. And one more thing if you want to use apk version use it I don't have any issues but don't ask me if anything goes wrong.

i ported twrp 3.2.1 to sc8830 sucessfully but touch is not working , can you help?
where can i find non-touch recovery
I'm using android 5.1

What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.

denmasgie said:
What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.
Click to expand...
Click to collapse
This is just some copy&paste guide thath will not work on most bootloader locked spreadtrum OEM phones

Please fix the twrp links!!!

@Vortex said:
This is just some copy&paste guide thath will not work on most bootloader locked spreadtrum OEM phones
Click to expand...
Click to collapse
No custom recovery will work on bootloader locked devices...

denmasgie said:
What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.
Click to expand...
Click to collapse
Kernel architecture is ARM.

[RECOVERY] - TeamWin Recovery Project [REDFIN] [OFFICIAL]

[RECOVERY] TWRP 3.6.0_11-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Device Config: https://github.com/bigbiff/android_device_google_redbull
GitHub - bigbiff/android_device_google_redfin
Contribute to bigbiff/android_device_google_redfin development by creating an account on GitHub.
github.com
If others thing don't work, please report the issue and let me know.
Download here:
Test9: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test9-redfin.img
- fix cpu temperature display
- turn off openaes
- MTP: fix 100% CPU
- fix perms for last_log.gz
- one click flash option to keep twrp when updating boot in recovery - thanks @Nebrassy
You need to install a kernel with built-in touch drivers such as ElementX-P5.
First, install ElementX-P5, the use the install ramdisk recovery option in the Install menu to install the TWRP image.
https://build.twrp.me/test/redfin/twrp-3.5.0-0-test1-redfin.img
Please ignore the -10 in the version string when fastbooted into TWRP. I am hoping to get the a11 TWRP branch working in a10 trees.
Test 2: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test2-redfin.img
Test 3: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test3-redfin.img
Decryption and backup restore working. Tested with April Firmware.
Test 4: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test4-redfin.img
Enable MTP. Fix /sdcard bind mount to /data/media/0
Test 5: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test5-redfin.img
Add partitions: misc, boot and persist. Enable repacking into ramdisk. Tested with ElementX-P5.
Test 6: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test6-redfin.img
Fix repacking twrp into recovery. You need to install a kernel with built-in touch drivers such as ElementX-P5.
First, install ElementX-P5, the use the install ramdisk recovery option in the Install menu to install the TWRP image.
Test 7: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test7-redfin.img
Fix wiping Titan M chip. Fix decryption hanging on lineage-18.1 when booting TWRP.
Test 8: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test8-redfin.img
Fix reboot to recovery from fastbootd.
http://twrp.me

Nice work!
Once the encryption element is fixed I will definitely be rocking this!!

Nice to see this, good job on working TWRP for this Device. Thank you.

Is there only the img build. No zip file? How to stay on twrp without zip?

This boots on a pixel 4a5g, but touch controls and adb do not seem to work. Do you think it would take a lot of code changes to enable it on the 4a 5g? The two phones share kernels for what it's worth.

Its possible to root android 12 with this?

Was able to boot to it on the pixel 5. Look forward to the progress! Thanks!

mistermojorizin said:
This boots on a pixel 4a5g, but touch controls and adb do not seem to work. Do you think it would take a lot of code changes to enable it on the 4a 5g? The two phones share kernels for what it's worth.
Click to expand...
Click to collapse
Can you provide me a copy of dmesg?

gogixx said:
Is there only the img build. No zip file? How to stay on twrp without zip?
Click to expand...
Click to collapse
This is a fastboot image only.

bigbiff said:
Can you provide me a copy of dmesg?
Click to expand...
Click to collapse
To get a dmesg, I need to use ADB (which doesn't work while booted into TWRP). So would this capture the info you'd need - boot into TWRP, reboot by holding power button, get a dmesg when it boots?
EDIT: so I'm trying to get it this way but the dmesg.txt comes out blank for some reason

mistermojorizin said:
To get a dmesg, I need to use ADB (which doesn't work while booted into TWRP). So would this capture the info you'd need - boot into TWRP, reboot by holding power button, get a dmesg when it boots?
EDIT: so I'm trying to get it this way but the dmesg.txt comes out blank for some reason
Click to expand...
Click to collapse
Unfortunately that would be from the android kernel. I didn't realize adb wasn't working for you. Are you using windows?

bigbiff said:
Unfortunately that would be from the android kernel. I didn't realize adb wasn't working for you. Are you using windows?
Click to expand...
Click to collapse
yes, windows 10, latest adb drivers. when it boots to TWRP it doesn't recognize that any adb devices are connected.
when booting to android though, I can access ADB without problems

bigbiff said:
This is a fastboot image only.
Click to expand...
Click to collapse
Thank you.
What's the proper installation process (how-to) to flash TWRP on the P5/redfin ?

unibombz said:
Thank you.
What's the proper installation process (how-to) to flash TWRP on the P5/redfin ?
Click to expand...
Click to collapse
There is no flashing of it. You would just boot in to it via fastboot boot *twrpimgfile.img

VivisClone said:
There is no flashing of it. You would just boot in to it via fastboot boot *twrpimgfile.img
Click to expand...
Click to collapse
Thank you for clarifying that it is not flashed to the recovery partition and only booted to when you need TWRP features via
Code:
fastboot boot twrp-3.5.0-0-test1-redfin.img

I was able to get touch working on the 4a5g using these commands:
fastboot flash boot twrp-3.5.0-0-test1-redfin.img
fastboot boot ProtonKernel-pixel5-v1.1.img
ADB Still didn't work. The log said couldn't mount storage. Under "mount" I could check every box except the last two (storage and external storage or sdcard I think).
the backup menu is very different looking than i'm used to. instead of being able to select which partitions to backup, there's only one option - "super (vendor, system, system ext...etc)" The only partition that's not listed there is the boot partition. Also, storage says 0mb . Not sure if it would have backed up anything.
Is it able to make backups on the Pixel 5? Can I get you any info (using the TWRP terminal or file manager mayber) to help development?

mistermojorizin said:
I was able to get touch working on the 4a5g using these commands:
fastboot flash boot twrp-3.5.0-0-test1-redfin.img
fastboot boot ProtonKernel-pixel5-v1.1.img
ADB Still didn't work. The log said couldn't mount storage. Under "mount" I could check every box except the last two (storage and external storage or sdcard I think).
the backup menu is very different looking than i'm used to. instead of being able to select which partitions to backup, there's only one option - "super (vendor, system, system ext...etc)" The only partition that's not listed there is the boot partition. Also, storage says 0mb . Not sure if it would have backed up anything.
Is it able to make backups on the Pixel 5? Can I get you any info (using the TWRP terminal or file manager mayber) to help development?
Click to expand...
Click to collapse
The super partition and other partitions you can backup as byte images. However most of these can be restored from the stock firmware. I am working on decryption right now. I am not sure what to do about adb unless you can pull logcat and dmesg for clues for the 4a5g.

Thanks for this TWRP image.
Side loading works.
TWRP does not read the internal storage... Any ideas?

vandyman said:
Thanks for this TWRP image.
Side loading works.
TWRP does not read the internal storage... Any ideas?
Click to expand...
Click to collapse
Yeah. Encryption in A11 is Wip like Op specified.

Is there the ability to resize system partition?