Database Info

How to ROOT when TowelRoot Fails? **Kitkat Root Method for INTEX AQUA Y2 PRO**

Hey Guyz,
Subhraw here
Today i want share with you a new tutorial by which you can root your MTK kitkat Devices:: Kernel may be after June 3 2k14
Reference phone is INTEX AQUA Y2 PRO 4.4.2
This Include flashing CWM Recovery
WARNING
It is long tutorial
for this you need
MTK droid tools
http://forum.xda-developers.com/showthread.php?t=2160490
SP Flash TOOL
http://forum.xda-developers.com/showthread.php?t=1982587
//(find yourself)
Android ADB drivers
MTK VCOM drivers
//
CTRv2.4
http://forum.xda-developers.com/showthread.php?t=1825722&page=86
;;;
An intelligent and peaceful mind(sorry no download)
First of all backup your Stock ROM using (MTK Droid Tools and SP Flash Tool)
prepare blocks for SP Flash Tools
** we only need your "recovery.img" but to be on safe side a backup is neccesary
Now extract CTRv2.4 to desktop
***
open CTRv2.4.exe "Start for MTK devices....." and select manual mode
***
copy your recovery.img(which you got from stock rom to Stock folder inside CTRv2.4) press OK
////////////////////
It will take some time to unpack
???????????
Now it will AsK for your resolution choose nearest or exact one;
////////////////
for lun file (I personally suggest NO) you can experiment with Yes;;;
//////////
maybe you get some error but dont worry we have new recovery
///
goto CTRv2.4 folder inside CTRv2.4 on desktop
and flash that file using SP FLash Tool (**please check recovery only otherwise you may brick your device**)
/////////
Now reboot your android into recovery
and flash SuperSu.zip (personally recommended)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Voila You will have Root next time you restart:laugh::laugh:
Please be good enough to hit thanks if it helps you
Remember .>. I m not a developer

intex aqua y2 pro
subhraw said:
Hey Guyz,
Subhraw here
Today i want share with you a new tutorial by which you can root your MTK kitkat Devices:: Kernel may be after June 3 2k14
Reference phone is INTEX AQUA Y2 PRO 4.4.2
This Include flashing CWM Recovery
WARNING
It is long tutorial
for this you need
MTK droid tools
http://forum.xda-developers.com/showthread.php?t=2160490
SP Flash TOOL
http://forum.xda-developers.com/showthread.php?t=1982587
//(find yourself)
Android ADB drivers
MTK VCOM drivers
//
CTRv2.4
http://forum.xda-developers.com/showthread.php?t=1825722&page=86
;;;
An intelligent and peaceful mind(sorry no download)
First of all backup your Stock ROM using (MTK Droid Tools and SP Flash Tool)
prepare blocks for SP Flash Tools
** we only need your "recovery.img" but to be on safe side a backup is neccesary
Now extract CTRv2.4 to desktop
***
open CTRv2.4.exe "Start for MTK devices....." and select manual mode
***
copy your recovery.img(which you got from stock rom to Stock folder inside CTRv2.4) press OK
////////////////////
It will take some time to unpack
???????????
Now it will AsK for your resolution choose nearest or exact one;
////////////////
for lun file (I personally suggest NO) you can experiment with Yes;;;
//////////
maybe you get some error but dont worry we have new recovery
///
goto CTRv2.4 folder inside CTRv2.4 on desktop
and flash that file using SP FLash Tool (**please check recovery only otherwise you may brick your device**)
/////////
Now reboot your android into recovery
and flash SuperSu.zip (personally recommended)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Voila You will have Root next time you restart:laugh::laugh:
Please be good enough to hit thanks if it helps you
Remember .>. I m not a developer
Click to expand...
Click to collapse
My mobile got bricked using sp flash tool its not even getting into bootloader ..my device is intex aqua y2 pro ..i tried flshing rom ..i need stock rom for this device ..can anyone here provide it?

auzshah said:
My mobile got bricked using sp flash tool its not even getting into bootloader ..my device is intex aqua y2 pro ..i tried flshing rom ..i need stock rom for this device ..can anyone here provide it?
Click to expand...
Click to collapse
Just Google you will find it like me

Need a cwm recovery for Huawei g6-l11 (LTE)

I can't find any cwm recovery suitable for g6-l11 LTE. Can someone help me develop or find one Pls.
-=-♔♚Need help♚♔-=-

There is twrp recovery u can download it from here
https://drive.google.com/file/d/0B-wMRksKspUMNFY1LWI5X1ltMFU/view?usp=sharing
if u have ubuntu x64 & speed internet connection i can help u to compile cwm

How do you get Ubuntu?? I'm. Using windows 7.
-=-♔♚Need help♚♔-=-

I tried flashing the .img and it worked! Thanks :thumbup::thumbup:
-=-♔♚Need help♚♔-=-

Btw if I accidentally installed a wrong version of cynogenmod will my device soft/hard brick?? And if something else happen what should I do??Should I flash stock boot image? Or what??
-=-♔♚Need help♚♔-=-

Btw on my Huawei G6-L11 Android 4.3 Jellybean. Should I install
CM 10.2/CM 7.2 which??
-=-♔♚Need help♚♔-=-

Need CynogenMod for Huawei G6-L11.
-=-♔♚Need help♚♔-=-

Can anyone help me build one?I have issues with sudo. It kept giving me command not allowed.
-=-♔♚Need help♚♔-=-

i'm building one for u10 i can help u pm me ur fb account or any method to contact with you

I found this guid in other forum. It also have a link for a TWRP recovery.
http://www.htcmania.com/showthread.php?t=969144
Direct Link for the TWRP recovery>
https://yadi.sk/d/SSDNtX5xeMeDB
Note - I did not tried it!
This tutorial is what I have done on my device, I hope can use them my help
Emui installed in your device 3.0 beta we need to install this ROM but does not work...
We will need to download the ROM b370 here I leave the linck: https://yadi.sk/d/gqWACWBleVQAG
And we will do the following for installation, after downloaded extractor must install the Huawei on our computer here the link: http://forum.xda-developers.com/show...php?t=2433454
Then with the Huawei exhaust unzip the following
-Boot.img
-Cust.img
-Recovery.img
-System.img
Now you will have to download the android adb and the SDK tools, adb link here: http://www12.zippyshare.com/v/67744317/file.html
And put the adb on the local disk c and in the folder adb, place the custom recovery.
And we will do the following, execute the cmd in windows
And write the following: chdir c:\adb
And execute the following
-fastboot flash cust cust.img
-fastboot flash recovery recovery.img
-fastboot flash boot boot.img
-fastboot flash system system.img
-fastboot reboot
And ready we already have the system installed with the b370 and the system will tell us that it is Huawei p7 mini not the g6-l11
Now we go to the root of this phone
For that the tutorials need recovery twrp here:
http://www.htcmania.com/showthread.php?t=967406
This is a compilation of the user pepe0000 and there was where remove information in 4pda so stay us more clear tutorial
Agradeciemientos to pepe0000 for bringing us this recovery
He clarified that to install this recovery is mandatory to have the unlocked bootloader, but I know here in this link to go back: http://www.htcmania.com/showthread.php?t=939960
This tutorial was made by D.ceres which I also thank you for this tutorial
1.*descargar and unzip the contents of the ADB at the root of the C: drive * http://www12.zippyshare.com/v/67744317/file.html
TWRP G6-L11 2.*Descargue *: https://yadi.sk/d/SSDNtX5xeMeDB
3.*Copy the downloaded content to the folder file root ADB *
4.*Conect the phone to the computer in Fastboot (bootloader). *(Vol-+ botón de encendido)
5.* Holding down the SHIFT key, right-click on the ADB folder and select the option "Open command window" *
6.* In the command prompt, type without quotes "fastboot flash recovery TWRP_G6-L11.img" or if you want to rename to write the name that been placed
Enter 7.*Pulse now and execute the following code "fastboot reboot"
If you want to return to the original recovery you have to download this file: https://yadi.sk/d/cAphF5smcwmUX
And perform the same procedure.
Again I thank Pepe0000 also for your tutorial because of remove the info there and I couldn't do it on my phone
Click to expand...
Click to collapse
After you install the recovery, downloaded the super su, link its here: https://yadi.sk/d/a92MoztteJAKe
We installed it and ready we will have root on our phone...
That's it, this is what I did and I thank 4pda also because of pull out there is rom
Click to expand...
Click to collapse

How abt cyanogenmod for this device?
-=-♔♚Need help♚♔-=-

flightdragonz said:
How abt cyanogenmod for this device?
-=-♔♚Need help♚♔-=-
Click to expand...
Click to collapse
as far as we know no one is working on it,
some people are working on cm12 for G6-U10, maybe later they will port it to the L11

Twrp g6 l11
messi2050 said:
There is twrp recovery u can download it from here
if u have ubuntu x64 & speed internet connection i can help u to compile cwm
Click to expand...
Click to collapse
Maybe you know where can I get new version of TWRP recovery.img for Huawei G6-L11?

[GUIDE][ROOT][MEDIATEK] Systemless root for mediatek

*****Keep in mind that I or XDA or anyone else is not responsible for what happens to your device make sure you have a nandroid backup before proceeding
This is based on my personal experience I'm not a Dev
How to enable systemless root on mediatek !!!!
Step 1:
Get the booting of your phone via readback using spflashtool or dumping the ROM IMG !!
Step 2:
Unpack the boot IMG using mkbootimg or carliv IMG kitchen or Android kitchen !!!
Step 3:
Open the ramdisk folder and open the init.rc using notepad++
Step 4
Goto the line
Code:
export PATH /sbin:/system/bin:/system/xbin:/vendor/bin
**The line may vary but it will look similar !!!
Add the path of your su file at the end
Like I was t to install it at my data partition so
Add
Code:
:/data/bin
At the end of the line and save !!
Then change the permissions of /data/bin to 644 else apps won't be able to read the path due to insuffient permission !!!
Then repack the boot.img
Flash the bootimg via sp flash tool of flashify or any other method
Step 6:
***note use the su binaries of your CPU only
Like I used arm 7 binaries for my device !!
To know your CPU type
Download terminal emulator or use adb shell and type cat /proc/cpuinfo
Now using adb push copy the su file to the /data/bin folder or make a flashable zip to do the same !!
If you can't push via adb try doing it in adb supported recovery !!!
You might need to create the bin folder manually
And don't forget to set the permission to 0755 and reboot !!
Plz let me know if it works !!!
And also let me know if it doesn't !!!!
I can't post the flashable zip because I'm still new !!!

Can you post some more info for this? What mtk chipset is it tested with? What android version? When you repack the kernel image, do you use android headers or mediatek headers?

AlexZap said:
Can you post some more info for this? What mtk chipset is it tested with? What android version? When you repack the kernel image, do you use android headers or mediatek headers?
Click to expand...
Click to collapse
Carliv Image Kitchen will repack the same way it was unpacked so you do not have to worry.
I also want more info for this because I'm not even finding the first link export .....

kirito9 said:
Carliv Image Kitchen will repack the same way it was unpacked so you do not have to worry.
I also want more info for this because I'm not even finding the first link export .....
Click to expand...
Click to collapse
the point is that the systemless installer is supposed to unpack and repack the kernel... and i dont know/dont think it can handle a mediatek header

AlexZap said:
the point is that the systemless installer is supposed to unpack and repack the kernel... and i dont know/dont think it can handle a mediatek header
Click to expand...
Click to collapse
Ohh, it could be that it doesn't support Mediatek because I tried a systemless SuperSU and it didn't boot the MT6580 device. I had to flash the boot.img to fix.

kirito9 said:
Ohh, it could be that it doesn't support Mediatek because I tried a systemless SuperSU and it didn't boot the MT6580 device. I had to flash the boot.img to fix.
Click to expand...
Click to collapse
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.

AlexZap said:
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
Click to expand...
Click to collapse
There isn't? Strange, then why when I flashed the SuperSU systemless zip from here it didn't boot but when flashed the SuperSU from here it did but said in SuperSU app, couldn't find the su binary.
Maybe I should push "su" to xbin folder or bin? What are your thoughts?

kirito9 said:
There isn't? Strange, then why when I flashed the SuperSU systemless zip from here it didn't boot but when flashed the SuperSU from here it did but said in SuperSU app, couldn't find the su binary.
Maybe I should push "su" to xbin folder or bin? What are your thoughts?
Click to expand...
Click to collapse
I think you need to read some more on how and why systemless root works and what it is for.
Regular root, the summer you installed, puts a bunch of binaries in the /system partition on your android phone, and while giving you root, it breaks a lot of things because it modifies the stock image, something that android doesn't expect to ever change except for system upgrades.
Systemless root fixes this. It does nothing to the system partition. It creates a mountable image and stores it in the /data partition that contains the su binary and whatever else is needed for root. It then modifies the boot image (the ramdisk that is packed with the kernel) so that on boot, it mounts this su image inside the already mounted system partition. This keeps the system partition stock, but at the same time, gives you root. Things like safetynet are unbroken and you can run things like android pay that check for a modified system image.
In order to do its magic, the systemless root installer has to be able to unpack and repack the boot partition. If you have a mediatek phone, you have about an 80% chance that your boot image is different then the rest of the android world. Mediatek phones have their own header in their images like boot and recovery (except for some very new devices). I am 95% certain that the systemless root installer does not know anything about mediatek headers. So it may unpack something, but clobber the boot image on repack. The author of this thread purports to have it working. I ask how. Is he one of the 20 or so percent without a mediatek header? Or did he do something else

AlexZap said:
.................
Click to expand...
Click to collapse
Yeah lol, first time working with android 6.0 and this systemless root. I know that's what the systemless root does, that's why after flashing the MT6580 device that I have, it didn't boot. Don't think the systemless supports this MT6580 as it uses it's own MTK header and not the standard AOSP.
Seems like OP as disappeared from this thread.

Sorry I took so long to respond
AlexZap said:
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
Click to expand...
Click to collapse
And yes I got the systemless root working on my Panasonic T41 running CM 12
The SuperSU installer doesn't work on mediatek 'coz in cannot unpack the boot.img with mtk headers so i did it manually but SuperSU tried to fix the placement of the binaries !!
So i used another superuser !!

uttarayan21 said:
And yes I got the systemless root working on my Panasonic T41 running CM 12
The SuperSU installer doesn't work on mediatek 'coz in cannot unpack the boot.img with mtk headers so i did it manually but SuperSU tried to fix the placement of the binaries !!
So i used another superuser !!
Click to expand...
Click to collapse
I have found that magisk works flawlessly on my Jiayu s3... it uses hybrid headers in the images... but magical does the unpack/repack just fine.
Sent from my KFTHWI using XDA Premium 4 mobile app

AlexZap said:
I have found that magisk works flawlessly on my Jiayu s3... it uses hybrid headers in the images... but magical does the unpack/repack just fine.
Click to expand...
Click to collapse
Well but in my case when i tried it on CM 12.1 mtk6582
The phone got bricked !!
The SuperSU installer couldn't even get the boot image from my phone !! :crying: so i tried to modify the installer script with other tools but it was waaaay too complex for me so tried to do this instead with another superuser and it worked !!
I also had to modify the init.rc to start the daemonsu service !!! :good:

uttarayan21 said:
Well but in my case when i tried it on CM 12.1 mtk6582
The phone got bricked !!
The SuperSU installer couldn't even get the boot image from my phone !! :crying: so i tried to modify the installer script with other tools but it was waaaay too complex for me so tried to do this instead with another superuser and it worked !!
I also had to modify the init.rc to start the daemonsu service !!! :good:
Click to expand...
Click to collapse
I think magisk is better at handling boot image formats.

AlexZap said:
I think magisk is better at handling boot image formats.
Click to expand...
Click to collapse
I agree with @AlexZap and i am using it and it is working perfectly
Sent from my Z14 using Tapatalk

Does this work for the newer chipsets? I tried on Android 6.0 / MT6750, but I dont see the path export anywhere in the boot image (grep -nrw 'boot.img-ramdisk' -e "PATH")

MalikDrako said:
Does this work for the newer chipsets? I tried on Android 6.0 / MT6750, but I dont see the path export anywhere in the boot image (grep -nrw 'boot.img-ramdisk' -e "PATH")
Click to expand...
Click to collapse
magisk works flawlessly. no need to muck around, just flash it from twrp
Sent from my KFGIWI using XDA Premium 4 mobile app

AlexZap said:
magisk works flawlessly. no need to muck around, just flash it from twrp
Click to expand...
Click to collapse
I've been having trouble getting TWRP to run on this phone (black screen for a few seconds then it reboots into android), although I just discovered an unmodified repacked boot image wont boot, so either the phone is doing some verification that is failing or the tool I used cant repack it right

MalikDrako said:
I've been having trouble getting TWRP to run on this phone (black screen for a few seconds then it reboots into android), although I just discovered an unmodified repacked boot image wont boot, so either the phone is doing some verification that is failing or the tool I used cant repack it right
Click to expand...
Click to collapse
any chance the boot loader is locked? usually flashing a bad image will brick your phone if the boot loader is locked, but you never know.
have you tried unpacking the boot image with carliv's image kitchen? it throws out a bunch of info on how the image is made. as long as it is repacked the same way (Carliv's tool does this automatically), it should work fine. unless whoever your phone manufacturer is somehow included another signature check... which is really really out of the ordinary.

AlexZap said:
any chance the boot loader is locked? usually flashing a bad image will brick your phone if the boot loader is locked, but you never know.
have you tried unpacking the boot image with carliv's image kitchen? it throws out a bunch of info on how the image is made. as long as it is repacked the same way (Carliv's tool does this automatically), it should work fine. unless whoever your phone manufacturer is somehow included another signature check... which is really really out of the ordinary.
Click to expand...
Click to collapse
I just tried Carliv's image kitchen, and both boot and twrp port worked first try

How to change Permissions?
i could not understand it
can u help me Please?

[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.

CAT s48c Stock rom

Helo i brick my cat s48c.
i use this tutorial to run AOSP Androind 10
How to Install AOSP Android 10 for Cat S48c [GSI Treble Q]
If you just bought the Cat S48c and want to install Android 10 Q, then you are in the right place. In this guide, we will share a step by step tutorial to
www.getdroidtips.com
and now phone screens logo cat and reboting
I have enable bootloader
i have TWRP and i can load any system.img but any system not working i try instal (and instal but dont work)
system-roar-arm64-ab-vanilla.img
system-roar-arm64-onlya-vanilla.img
and more.
What i can do?

i have full backup from twrp . restone so ok

Imei lost can help extract QCN file?

I need the QCN file backed up by QPST now, please help me

could u share it please

CAT S48C
Hello XDA Community https://forum.xda-developers.com/t/cat-s48c-stock-rom.4310627/#post-86346157 https://forum.xda-developers.com/t/help-with-root-caterpillar-s48c.3916567/page-3#post-84319021...
forum.xda-developers.com

mrbeanchina85 said:
i have full backup from twrp . restone so ok
Click to expand...
Click to collapse
hello can shared bak up please?