Related
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.
Hi I am a new member on this forum, though I had been browsing this forum for long long time, I had not registered. Recently I had the courage to root and install omnirom on my phone (as my phone is getting old, i was ready to take the chances of bricking my device. I verified my device with eMMC brick bug tester and my device is frees from that bug, probably as my motherboard was changed under warranty). After toying with omnirom, I am back on stock rom. I went to Samsung Service Center and got my factory firmware installed for Rs 225/- (I had taken nandroid backup with epsilon 6.0... version of CWM, but it missed preload partition and restored the backup with philz recovery and my preload partition was erasaed and have to go for SSC).
I have few queries regarding the SGR, please help me with them:
1. Is there a temporary recovery for SGR (ie, can be flashed with stock recovery and returns back to stock on reboot. The zip file has to be maintained on SD card)
For SGS2: http://forum.xda-developers.com/galaxy-s2/general/guide-root-unroot-stock-ics-firmware-t1501719
2. In order to restore the partition on my own, I tried and searched net for recovery using testdisk and had taken a file image of the SGR internal flash disk. I opened it with testdisk, but testdisk was not able recognise the partitions I tried EFI GPT as suggested and Intel partiton table type and both did not work. Do you know the partition table type for this?
recovery link: http://www.df.lth.se/~jokke/androidfilerecovery/
3. I was just curious if becoming root (on adb shell) is just running su, thought I would copy su binary from superuser zip ro sdcard and run it with the path, but it just runs and nothing happens (I need this to remove few samsung apps esp, vlingo. I plan to do it from recovery -> adb shell -> su and delete apk & odex files).
This has been a great forum and helped me a lot. Thank you guys for all your effort.
Actually the first working version of custom recovery for Onda v919 Air CH DualOS -> TWRP 2.8.7.0.
This is the port TWRP for Teclast x98Pro provided by user Dani Basabe on this resource, for which many thanks to him, honor and respect.
All basic functions are working: touch, install, wipe, backup and restore, OTG-function (can make a backup on a flash drive) & etc.
Only no vibration feedback. I suppose it's not the worst thing in life...
With the appear of TWRP can install different system mods, for example, audio. After taking a backup copy of the system, of course.
I have to say: xposed on this device doesn't run! After installation bootloop.
Installation:
Place twrp.img in the root of internal /sdcard and run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/android_recovery
(I described the usual and most simple way for me. With devices through adb-interface I'm working with Total Commander with the plugin. We can try to install TWRP through fastboot commands:
adb reboot bootloader
fastboot flash recovery twrp.img)
To enter in TWRP after selecting "Android" in the main boot menu, hold down volume "-" before the advent of the service menu where the volume keys select "Recovery Mode" and press the power button.
Or you can use this method: http://forum.xda-developers.com/android/development/root-how-to-root-access-tablet-onda-t3396299
Download
Work fine!!
I just installed!
Excellent!
Thank you
ViAlexSt said:
Actually the first working version of custom recovery for Onda v919 Air CH DualOS -> TWRP 2.8.7.0.
This is the port TWRP for Teclast x98Pro provided by user Dani Basabe on this resource, for which many thanks to him, honor and respect.
All basic functions are working: touch, install, wipe, backup and restore, OTG-function (can make a backup on a flash drive) & etc.
Only no vibration feedback. I suppose it's not the worst thing in life...
With the appear of TWRP can install different system mods, for example, audio. After taking a backup copy of the system, of course.
I have to say: xposed on this device doesn't run! After installation bootloop.
Installation:
Place twrp.img in the root of internal /sdcard and run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/android_recovery
(I described the usual and most simple way for me. With devices through adb-interface I'm working with Total Commander with the plugin. We can try to install TWRP through fastboot commands:
adb reboot bootloader
fastboot flash recovery twrp.img)
To enter in TWRP after selecting "Android" in the main boot menu, hold down volume "-" before the advent of the service menu where the volume keys select "Recovery Mode" and press the power button.
Download
Click to expand...
Click to collapse
Thank you very much!
Please, try to do the mod to enable audio on latest firmware with old bios.
mismamente said:
Please, try to do the mod to enable audio on latest firmware with old bios.
Click to expand...
Click to collapse
The difficulty is that I have sound. How do I determine whether sound on other devices? I have tried to use Viper-mod, but for some reason it stubbornly refuses to install the driver. You can try different audio mods from this forum, after making the system backup. Mods based on Viper most likely will not start, therefore it's necessary to try with another engine.
I currently run an interesting RemixOS: version 2.0 starts successfully, but no wifi and sound. While thinking about it, what libraries to take from stock firmware.
mismamente said:
Thank you very much!
Please, try to do the mod to enable audio on latest firmware with old bios.
Click to expand...
Click to collapse
Try Remix OS - boot 20160429, but system audio libraries other.
ViAlexSt said:
Try Remix OS - boot 20160429, but system audio libraries other.
Click to expand...
Click to collapse
thank you, I will try.
I have a cube tablet which has the same processor (intel bay trail), how did you port the twrp? I would like to do the same from my stock recovery (if you don't mind). Thanks. All I want is advice/tips... The recovery that I've ported just reboots when entered on recovery from Droidboot.
XDA_h3n said:
I have a cube tablet which has the same processor (intel bay trail) ... The recovery that I've ported just reboots when entered on recovery from Droidboot.
Click to expand...
Click to collapse
I can't say for sure how identical processors in terms of porting TWRP (Cherry Trail <=> Bay Trail). May need more significant changes to the original TWRP. General method for porting one: from stock recovery move to port kernel and recovery.fstab. Further it's necessary to look and compare other files. Unpack/pack images possible using Carliv Image Kitchen for Android. But in your place I would have found TWRP for a more suitable tablet. What is your model? Maybe I will prompt the object of porting.
ViAlexSt said:
I can't say for sure how identical processors in terms of porting TWRP (Cherry Trail <=> Bay Trail). May need more significant changes to the original TWRP. General method for porting one: from stock recovery move to port kernel and recovery.fstab. Further it's necessary to look and compare other files. Unpack/pack images possible using Carliv Image Kitchen for Android. But in your place I would have found TWRP for a more suitable tablet. What is your model? Maybe I will prompt the object of porting.
Click to expand...
Click to collapse
Well, I've tried the method of replacing zimage and dtb images and the recovery.fstab, which was the image I created before. It just doesn't work. I would think it's something to do with an partition layout issue.
I've been using the Teclast X98 twrp, as their rom actually works on our tablet without any modifications needed other than a couple of framework changes with resolution as it causes issue with the system ui being bigger.
Anyhow, thanks for your help, I'll try to see what I can do from the tool you've provided, as I used to unpack and repack the images using another kitchen tool. It quite off-topic from this thread; thanks for you help. Here's my stock recovery if you do have free time.
XDA_h3n said:
Well, I've tried the method of replacing zimage and dtb images and the recovery.fstab, which was the image I created before. It just doesn't work. I would think it's something to do with an partition layout issue.
Click to expand...
Click to collapse
I'm pretty sure that your chances of success will increase significantly if you select TWRP for a more suitable machine. I suggest to try TWRP for Onda v820w, as most similar devices Cube iWork7: Bay Trail+Android 4.4.4 (see attachment; autor kostyamat@4pda). About dt.img: I can't tell you how to do when porting, but if you are compiling TWRP this point is taken into consideration when editing BoardConfig.mk. What concrete advice I can't give, my recovery/TWRP hasn't dt.img.
For example: I to run on Onda TWRP 3.0.2.0 for Cube iWork8 Ultimate did (unpacked Carliv Imagetool):
1. Replaced all: recovery.img-base, recovery.img-cmdline, recovery.img-kernel, recovery.img-kernel_offset, recovery.img-pagesize, recovery.img-ramdisk-compress, recovery.img-ramdisk_offset, recovery.img-tags_offset.
2. In folder 'ramdisk':
- etc/recovery.fstab -> edited blocks like me;
- replaced: file_contexts, selinux_version, service_contexts, default.prop;
- file names init.recovery.***.rc, ueventd.***.rc changed like me, contents are not changed.
It was enough for a successful launch. But there is a little roughness in it work, so don't share.
Successful porting!
ViAlexSt said:
I'm pretty sure that your chances of success will increase significantly if you select TWRP for a more suitable machine. I suggest to try TWRP for Onda v820w, as most similar devices Cube iWork7: Bay Trail+Android 4.4.4 (see attachment; autor kostyamat@4pda). About dt.img: I can't tell you how to do when porting, but if you are compiling TWRP this point is taken into consideration when editing BoardConfig.mk. What concrete advice I can't give, my recovery/TWRP hasn't dt.img.
For example: I to run on Onda TWRP 3.0.2.0 for Cube iWork8 Ultimate did (unpacked Carliv Imagetool):
1. Replaced all: recovery.img-base, recovery.img-cmdline, recovery.img-kernel, recovery.img-kernel_offset, recovery.img-pagesize, recovery.img-ramdisk-compress, recovery.img-ramdisk_offset, recovery.img-tags_offset.
2. In folder 'ramdisk':
- etc/recovery.fstab -> edited blocks like me;
- replaced: file_contexts, selinux_version, service_contexts, default.prop;
- file names init.recovery.***.rc, ueventd.***.rc changed like me, contents are not changed.
It was enough for a successful launch. But there is a little roughness in it work, so don't share.
Successful porting!
Click to expand...
Click to collapse
Thank you a lot for all of your help
I've got it working on my tablet. I am very grateful for your help.
Recovery just doesn't mount the partitions correctly, but I'll be modifying the recovery.fstab until I'll find a way. Intel does the mount points like /dev/block/platform/intel/by-label/boot on stock recovery. I'll need to find the true location of all of the partitions, but it is fixable.
Again, I am very grateful :laugh:
Lol the original recovery.fstab from the port, has the same guid name on the partition blocks. That fixed it. Everything is mounting! Thanks.
Anybody with an Linx 7 or a Cube iWork 7 I'd posted in the linx forums and there is a tool that should do everything for you soon
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 usersInstall 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 usersDownload 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.
hey i want to install a custom rom (gsi) so i hope some people can help me out
main info: i have a ulefone note 9p with mediatek 6762 (runs with mediatek 6765 android scatter) and android 10.
this twrp is a twrp 3.4.0. built for ulefone note 9p i downloaded from here:
unofficial twrp 3.4.0 Root Ulefone Note 9P - unofficial twrp
download unofficial twrp 3.3.1 root Ulefone Note 9P, user who own Ulefone Note 9P can root it by following the below instructions
unofficialtwrp.com
after going to the painful procedure of unlocking bootloader flashing stock and twrp modified rom + rooting the device
i stuck at the procedure to install a gsi image via twrp.
i already know that the device must be unrooted and i have already gained some experiences in flashing the rom
even after a few softbricks, so i will try installing this image with a stock rom and twrp after i received the help i need.
i use a sd card because twrp always disappears when i transfer a file via my phone and i land on stock recovery.
this problem solves when i root my phone via magisk. as i heard flashing gsi's dont work in a heavy modified state (like with magisk),
so a sd card solved this problem to run files on recovery mode without file transfer and rooting.
the problem i have is the following: i followed some instructions saying to wipe some data first in advanced wipe
- also the system partition which is not available. after that tried to install the image directly. as it finds the rom from my sd card i have to select the partition type to flash image
i only have boot recovery and super available but i need the system partition. i looked in the internet further (the painful process) and it gave me some hints going to mount.
there it finds the system partition but when i set a checkmark on it nothing changes, so this hint didn't helped me.
what should i do now? i'm stuck in some dead end and i don't know what to do it seems like this is the only way for me to get it work.
please help.
i think i found something. since my phone is rooted i also tried to delete system apps which also don't work. i tried many system app removers but it always give error. i think the problem lies in permissions that are not given to this phone. how can i get full access to \ system to gain full permission rights? i also have busybox installed btw
You've to mount the /system partition as RW in order to access this storage location.
Example code:
Code:
adb devices
adb shell "su -c 'mount -t auto -o rw,remount /system'"