Related
Hey Motorola Fire owners!
Here's ClockWorkMod for our beloved QWERTY phone [With nandroid backup minor issues]
Any damages, you're responsible of it.
The Steps:
1- Download busybox from playstore, i prefer stericson's one, install busybox binary.
2- Download Pimp My Rom from playstore, open it, click > Universal init.d support, then click > activate
3- Download latest zip (bootmenu 3-12-12.7z)
4- Extract it, and run Install-boot-menu.bat
If you want to know what the script does:
5- Download latest bootmenu folder, extract it, copy "bootmenu" folder to /system/ (by using any root browser of your choice)
6- Fix permission of all the files inside "/system/bootmenu/binary/" to: RWXR--R--
7- a- Create a new file with no extention, rename it to 97bootmenu, put it inside "/etc/init.d/" set it's permissions to RWXRWXRWX (full permissions)
7- b- inside this file paste this code and save it:
Code:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
-Then Reboot
Now focus, while you're seeing motorola logo, the capacitive keys' leds will light up at certain timing, quickly press VOL- button before the lights go off, if you later, don't want to boot to bootmenu, just don't press the VOL- button, the phone will boot normally to system
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------To restore backed up nandroid system.yaffs2.img
In terminal emulator or adb shell type:
cd /sdcard/clockworkmod/backup/YYYY-MM-DD.HH.MM.SS/
md5sum *.img > nandroid.md5
Where <YYYY-MM-DD.HH.MM.SS> is the folder of your backup.
Then go to cwm again and restore ( i prefer advanced restore > system )
Or with fastboot: By typing: "fastboot flash system system.yaffs2.img"
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Now the most important part, press thanks button, it motivates me
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I'd like to thank those who made this dream come true: GentryLamp - 7amdoun (Thanks alot bro) - Aweosomeabhijeet - Mr. indigo - Andrewidya - AndYRo - Chen2011521
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Changelog:
3-12-12
-Added automatic installer (abhijeet's idea)
1-12-12
-Booting to bootmenu through volume down button (Thanks alot 7amdoun!)
-Now you don't have to delete 97bootmenu at all
-Unified bootmenu-recovery background
30-11-12: Very old build
-Removed ability to backup data via clockworkmod since it probably is corrupted, causing bootloops when restoring, you can backup the whole rom using onandroid backup instead
-Ability to restore nandroids
28-11-12: Very old build
-Fixed font size of the recovery, (Thanks chen2011521)
-Changed wallpaper because i got bored
25-11-12: Very old build
-Modified Stock.sh so when you select [+boot] > [stock] it boots normally to stock system, Without needing pc. (Thanks aweosomeabhijeet)
-Fixed some mounting issues, may be able to backup .android_secure
24-11-12: Very old build
-First alpha release
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Downloads:
Removed old builds, for the user not to download them and use the new incompatible steps.
Just registered!
---------- Post added at 04:40 PM ---------- Previous post was at 03:43 PM ----------
Only just created a bunch of commands to mount secure.android. After normal backup of system and data, gave me this error:
Backing up .android_secure...
Freeing space...
sh: dedupe: not found
Done freeing space.
sh: dedupe: not found
Already did it!!
Waiting for more to come
:good::good::good::good::good:
No more dedupe error, tar generated correctly! but more mounting problems! The last logs lines:
Backing up .android_secure...
com.joelapenna.foursquared
com.google.android.youtube
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
So fstab is sill umcomplete!
---------- Post added at 05:59 PM ---------- Previous post was at 05:42 PM ----------
Im startint to think that every sbf has diferents mounts...
xt316 chinese 2.3.5
97bootmenu permission 744
and reboot into bootmenu
but not full permission.
Backup stuck at /system
....
Did you port the recovery from source? You can change it font smaller.
Mazen.kh said:
Hey Motorola Fire owners!
Here's CWM for our beloved QWERTY phone [Still have issues with nandroid backup]
Okay so first of all this is not only my work
I only built CWM6 and put it inside the bootmenu, also helped in discovering init.d support, and when you nandroid backup, i fixed the creation of system.img and data.img (with help of dear friends from taringa.net) :angel:
The Steps:
1- Download busybox from playstore, i prefer stericson's one, install busybox binary.
2- Download PimpMyRom.apk from attachments and install it, because the one in the market have some errors causing FCs
3- From Pimp my rom, click > Universal init.d support, then click > activate
4- Download bootmenu.zip, extract it, copy "bootmenu" folder to /system/ (by using any root browser of your choice)
5- Fix permission of all the files inside "/system/bootmenu/binary/" to: RWXR--R--
6- a- Create a new file with no extention, rename it to 97bootmenu, put it inside "/etc/init.d/" set it's permissions to RWXRWXRWX (full permissions)
6- b- inside this file paste this code and save it:
HTML:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
7- Reboot
After reboot, android bootmenu will appear, choose recovery, then select custom recovery
Now you entered CWM 6 :cyclops:
Please don't select the "mounts" section, still needs fixes, might be dangerous
If you take nandroid it will successfully backup system.img and data.img without sd-ext.
You may not be able to restore them through cwm.
But you can restore them through FASTBOOT.
I flashed many zips through this recovery successfully.
PS: to boot again to system, normally connect the device through adb, and type:
adb shell
rm -r /system/etc/init.d/97bootmenu
Then reboot using "adb reboot" or reboot function in bootmenu
Now the most important part, press thanks button, it motivates me to keep up the good work
I'd like to thank those who helped in getting this bootmenu to work:
- Gentry Lamp
- 7amdoun
- Aweosomeabhijeet
- Mr. indigo
- Andrewidya
- AndYRo (from Taringa.net)
probably others that i forgot to mention
I'll keep updating the recovery until it becomes perfect
Click to expand...
Click to collapse
Hey Mazen I would like to suggest you something.
Open bootmenu folder go to script folder and open stock.sh
and add
Code:
rm -r /system/etc/init.d/97bootmenu
reboot
Then if you select boot>Stock your phone will reboot twice and boot normally.
then no need of using adb in PC.
I make everything as u say and restarted it above 6 times but nothing happens and my device starts normally!!!
EDIT: try to change permissions of 97bootmenu to rwxr-r- & restart 2 times but nothing happened!!
chen2011521 said:
xt316 chinese 2.3.5
97bootmenu permission 744
and reboot into bootmenu
but not full permission.
Backup stuck at /system
....
Did you port the recovery from source? You can change it font smaller.
Click to expand...
Click to collapse
I built it online and modded some files, couldn't build from source, the font is not so important right now so i'm working on fixing the nandroid backup
aweosomeabhijeet said:
Hey Mazen I would like to suggest you something.
Open bootmenu folder go to script folder and open stock.sh
and add
Code:
rm -r /system/etc/init.d/97bootmenu
reboot
Then if you select boot>Stock your phone will reboot twice and boot normally.
then no need of using adb in PC.
Click to expand...
Click to collapse
I tried that once and it booted to the bootmenu again but i will retry, thanks :laugh:
wrong :|
I follow ur steps and I fail in problem! just tell me what shoud I do NW?
and nothing wrong in my device!
EDIT: I change some permissions and it's work but I forgot what I do and I reboot without need PC!
I advice u guys to make that suggest by aweosomeabhijeet it's awesome
Ok remember to use reboot after rm command.
Sent from my XT530 using xda app-developers app
european sbf
Hey guys has anyone an european sbf for the xt311, i really need it.
Hey Mazen,
How did you manage to get CWM to make a full backup. I tried everything but it just freezes on system. I edited recovery.fstab to point to /dev/block/mtdblock* for every partition but it keeps complaining that it can't find that volume to mount.
7amdoun said:
Hey Mazen,
How did you manage to get CWM to make a full backup. I tried everything but it just freezes on system. I edited recovery.fstab to point to /dev/block/mtdblock* for every partition but it keeps complaining that it can't find that volume to mount.
Click to expand...
Click to collapse
I added mkyaffs2image
and AndYRo fixed a couple of mounting errors, if you build CWM 6 online you can take our xt311's modded files and only replace "recovery" file in /recovery/sbin/, with the corresponding one in your CWM 6
Mazen.kh said:
I added mkyaffs2image
and AndYRo fixed a couple of mounting errors, if you build CWM 6 online you can take our xt311's modded files and only replace "recovery" file in /recovery/sbin/, with the corresponding one in your CWM 6
Click to expand...
Click to collapse
Edit: I ported CWM6 to my phone manually and it loads and backs up boot and recovery but still gets stuck on /system
Any ideas?
Moderator warning.
Thread has been cleaned. Remember forum rules when posting.
Mazen.kh said:
Hey Motorola Fire owners!
Here's CWM for our beloved QWERTY phone [Still have issues with nandroid backup]
Okay so first of all this is not only my work
I only built CWM6 and put it inside the bootmenu, also helped in discovering init.d support, and when you nandroid backup, i fixed the creation of system.img and data.img (with help of dear friends from taringa.net) :angel:
The Steps:
1- Download busybox from playstore, i prefer stericson's one, install busybox binary.
2- Download PimpMyRom.apk from attachments and install it, because the one in the market have some errors causing FCs
3- From Pimp my rom, click > Universal init.d support, then click > activate
4- Download latest bootmenu.zip, extract it, copy "bootmenu" folder to /system/ (by using any root browser of your choice)
5- Fix permission of all the files inside "/system/bootmenu/binary/" to: RWXR--R--
6- a- Create a new file with no extention, rename it to 97bootmenu, put it inside "/etc/init.d/" set it's permissions to RWXRWXRWX (full permissions)
6- b- inside this file paste this code and save it:
Code:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
7- Reboot
After reboot, android bootmenu will appear, choose recovery, then select custom recovery
Now you entered CWM 6 :cyclops:
Please don't select the "mounts" section, still needs fixes, might be dangerous
If you take nandroid it will successfully backup system.img and data.img without sd-ext.
You may not be able to restore them through cwm.
But you can restore them through FASTBOOT.
I flashed many zips through this recovery successfully.
PS: to boot again to system, normally:
In bootmenu select [boot] > [stock]
OR
Connect the device through adb, and type:
adb shell
rm -r /system/etc/init.d/97bootmenu
Then reboot using "adb reboot" or reboot function in bootmenu
Now the most important part, press thanks button, it motivates me to keep up the good work
I'd like to thank those who helped in getting this bootmenu to work:
- Gentry Lamp
- 7amdoun
- Aweosomeabhijeet
- Mr. indigo
- Andrewidya
- AndYRo (from Taringa.net)
probably others that i forgot to mention
I'll keep updating the recovery until it becomes perfect
Click to expand...
Click to collapse
Thanks for creating a thread!
I'm trying with UAE sbf, unfortanelly I have to reflash it, since there's a problem with my Init.d support.
*Can we able to change the font size in the recovery not in the bootmenu? cuz it's looks bigger
PS. i make oNandroid backup and I delete it to try the backup section in the recovery when I make it it's stuck on
backup system.....
and no progress bar like any CWM recovery!
If build from source,android.mk in bootable/recovery can change font.
smaller font looks well on xt311/6
I have built one, but some problem not solve.
chen2011521 said:
If build from source,android.mk in bootable/recovery can change font.
smaller font looks well on xt311/6
I have built one, but some problem not solve.
Click to expand...
Click to collapse
Upload it so i can mix things and fix the font
MutiTool - Swiss army knife - MUST have for Newbies. 17Menu >300 choices. believe it!
MutiTool Advaced - Swiss army knife - All in One Tool is on post#3
MutiTool Basic- Swiss army knife - MUST have tool for Newbies.
This is for N7100 only, N7105 user look here.
Glad to announce a utility tool - MultiTool.
This is state of the art must have tool for all newcomers. You can manage following things with it.
- Root
- Busybox
- EFS Backup/Restore
- Recovery changer
- Kernel changer
- Modem changer
- Backup/Restore System App & Framework folder
- Bloatware Backup-Remove-Restore
- LockScreen Security bypass
- Clean device to prepare for Triangle Away
- Flash Recovery/Kernel/Modem from SD card (.img .bin)
Details of features under Installation & Features
Installation and Features MUST READ BEFORE USING
So You must have CWM/TWRP Recovery Installed to use this tool. Here is detail guide to get CWM on your device.
Procedure to get CWM : Click to Show Contents if you want to know How to flash CWM. If you have CWM installed then move to next step - MultiTool Intallation and features.
Step 1
Download Philz_touch_*n7100.tar.md5 Also you need to have Kies OR Samsung USB driver installed on PC.
1.Open Odin and select PDA tab (see image below) (Get Odin from here)
2.Point to recovery file you have downloaded philz_touch_* -n7100.tar.md5
3.Now switch off device and reboot in download mode
press Vol down + Home +Power, And then, press Volume UP button in Warning Page to enter the Download Mode
4.Connect device to PC and wait till device successfully added to com port (it will turn light blue) (see image below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5.Hit ‘Start’ to flash
6.Once it flashed successfully, you can see 'PASS' in table above the ID :COM, you can disconnect device from PC (see image below)
[Note : normally, phone should auto-reboot into recovery.
If it reboots into android and your recovery remains stock, repeat above steps and untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm]
On successful flashing your recovery change to CWM, Now Next step How to use Multitool
Installation of Multitool and Detail features
- Download DrKetan_MultiTool-AromaVxx.zip from end of this post and copy to SD card (Internal / Ext)
- Reboot device to Recovery (Vol Up +Power + Home).
- You will have recovery menu like this(see image below), Select Install zip
- Then select Int/Ext SD card depending on you have copied file location.
- Select file you have copies DrKetan_MultiTool-AromaVxx.zip and hit Entre. (See image)
This will Open Aroma Installer and you will have following Option to perform. Read every option in detail before proceeding.
1.Root
Here you will have two option.
A.Root : You can root your device with this option, Also this option cleans leftover of previously installed Superuser/SU of different superuser app.
In case your device is previously rooted and on reboot you can't see SuperSU app in drawer OR if you unable to update binary, simply update from Play store and it should work.
B.BusyBox - Routinely this doesn't needs and most of app needs root works without this too. Still any of your app demand this then you can select this option also you can do it later too.
2.EFS Backup If you are newbies and don't know why you need this then first read this thread. I recommend all user to make EFS backup if you still don't have.
A.EFS Backup : This will make EFS backup in format of raw imahe efs.img to int SD card MyEFS folder
B.EFS Restore : This will restore previously made backup in case you lose IMEI and need it.
3.Recovery - This is recovery changer tool.
You can switch to different recovery like
A.Philz touch CWM based recovery
B.TWRP
C.Stock Recovery- remember if you flash stock recovery, you will have to use odin to flash CWM/TWRP.
Here is Philz Recovery original thread
Here is TWRP official project website
4.Kernel - You can switch between kernel
Available kernels are
A.NEAK kernel B.Perseus Kenel C.Stock Kernel
Here is Neak kernel original thread if you have any queries for NEAK kernel Credit @simone201 for NEAK kernel.
Here is Perseus Kernel original Thread, in case you have any kernel related queries for Perseus Kernel. Credit @AndreiLux for Perseus Kernel
5.Modem
A.Old Modem LK6 : Don't Flash this on New ROM ME6 and later otherwise you will lose IMEI
B.New Modem MG1 :If you downgrade ROM and lose your IMEI, flashing this new modem can restore your IMEI.
6.backup Restore general - Helpful before trying different MODs, if that doesn't work you can restore previous file wuth this.
A.Backup Framework folder - Will make backup of System/framework folder to IntSDcard/DrKetanMod/framework folder -Needs 100MB free space
B.Backup System Folder - will make backup of System/app folder to IntSdcard/DrKetanMod/app folder. it needs appr 700MB space.
C.Backup to ExtSD - will backup System/app + System/framework folder to ExtSDCard/DrKetanMod. Needs 800MB space.
For Restore select option according you have selected backup location.
D.Restore Framework folder from IntSD
E.Restore System/App folder from IntSD
F.Restore System app and framework folder from ExtSD
7.Bloatware
A.Backup Bloatware - Select this to backup bloatware before removing it so you can restore anytime you need it.
B.Remove Bloatware - You can remove batch bloatware with this. To remove selected bloatware use this tool
C.Restore Bloatware
8.LockScreen security bypass
A.Remove Password - If you forget your lockscreen password/Pin/Pattern, you can bypass security with this option. This will remove PIN/Password and you can reset new. In case you bypass Pattern then you may have pattern on reboot but you can unlock with any pattern and you can reset your new pattern.
9.Prepare device to use TriangleAway Newbies are not knowing about their recovery/kernel so this tool will help to reset stock.
A.Clean device - This will remove all left over of Super user app and SU, also remove Busybox and symlink of busybox. As well this will Replace CWM to Stock recovery. But still clean root access will remain present to use triangle away app. That can be unroot with SuperSU settings.
Again if device doesn't have SuperSU app OR fail to update binary then update it from play store.
Remember after selecting this option your recovery will be stock and if you need CWM, you have to use Odin again
B.Select This If you have stock kernel - If your kernel is custom and you want to make device clean you also have to select this option along with A. to use triangle away.
10.Own Flashing
No more Flashable zip OR Tar needed to flash extracted recovery/kernel.img OR modem.bin
You can extract recovery.img or boot.img or modem.bin from stock ROM by simple unzip tool and put file on Int/Ext Sd card root directory then you can follow below mentioned task from aroma to flash that stuff.
A.Flash Kernel from IntSD
B.Flash Kernel from ExtSD
C.Flash modem from IntSD
D.Flash modem from ExtSD
E.Flash recovery from IntSD
F.Flash recovery from ExtSD
Download :
DrKetan_MutiTool_AromaV11 - Basic version
Dr.Ketan_MultiTool_Advanced
Old Version
DrKetan_MutiTool_AromaV10
-------------------------------------------------------------------------------------------------------------------------------------------------------
Hope friends you will find this tool helpful to keep on your SD card so you can use it anytime. If Niewbies can't post here in dev section, use this thread instead.
GoodLuck And Happy Flashing !
ChangeLog :
[15.09.13] DrKetan's MultiTool V10 -Initial release
[17.09.13] DrKetan's MultiTool V11 - two changes. A. Own Flashing - you can flash your recovery.img /boot.img /modem.bin. B.fixed issue on twrp using ExtSD option.
[21.09.13] DrKetan's MultiTool Advance V1 added. A. Aroma File Manager with Terminal. B. Odex remover C. Simplistic backup restore. D. System push
[29.09.13] DrKetan's MultiTool Advance V2 added. A.GPS Glonass fixer B. CSC Features C. build.propTweaks D. Bloat remover customized
Credits : @Phil3759 for his amazing recovery and busybox cleaning tool @Chainfire for his Superuser.apk and SU
I MutiTool Advanced
Ok friends glad to present advanced version of MultiTool. This is not much different from basic version but having some extra features and may not be comfortable to use by newbies. so releasing here as extra version and keeping basic vesion as it is.
Index
- Root
- Busybox
- Recovery changer
- Kernel changer
- Modem changer
- Backup/Restore System App & Framework folder/ EFS /Simplistic and mass bloatware remover
- Restore
- Odex remover
- Customized bloatware remover
- Customized CSC Features
- Tweaks - build.prop
- LockScreen Security bypass
- Push System Apks
- GPS Glonass Fixer
- Clean device to prepare for Triangle Away
This is advanced version and expecting no need to write guide about how to flash CWM and install multitool, still anyone have doubt please refer post #1.
Detail features
- Tool having some welcome screen, introduction, terms and condition, changelog, features list initially.
- After this is MainMenu. You can select either of one menu
A. MultiTool Utilities
B. Aroma File Manager with Terminal Console
C. System Information.
- Starting with Mutitool utilities, you will get following options
1. Root option : Inject root to device.
2. Busybox : Inject Busybox to device.
3. Recovery Flasher
Phillz recovery
TWRP recovery
Stock recovery
Recovery from SD card - You need to put desired recovery.img file on root directory of int SD card
Recovery from ExtSD card - You need to put desired recovery.img file on root directory of Ext SD card
Do Not change - To Keep your existing recovery
4. Modem Flasher
New MG1 flash - you can restore IMEI lost by downgrading ROM. I have removed option to flash old modem as it is not useful. still can flash any modem from SD card
Flash Modem from Ext SD - Put modem.bin file on root directory of ExtSD to flash
Flash Modem from Int SD - Put modem.bin file on root directory of IntSD to flash
Do Not change - To keep your existing modem
5. Kernel Flasher
Perseus Kernel
NEAK Kernel
RedPill Kernel (TW)
Adam Kernel
Stock Kernel (MG1)
Flash Kernel from ExtSD - Put boot.img file on root directory of ExtSD to flash
Flash Kernel from IntSD - Put boot.img file on root directory of IntSD to flash
Do not change - To keep existing kernel
6.Backup and Removel utility - This will be Menu page
There will be option to skip this OR to enter to customize backup/removal
EFS - A.Backup to IntSD B.Backup to ExtSD
Bloatware - A.Backup Bloatware (To bloatware folder in intSD)B.Bloatware Removal
System Backup A.Backup System/app folder to IntSD/DrKetanMod/app B.Backup System/framework folder to IntSD/Dr.KetanMod/framework
Simplistic Backup A.OdexB.Deodex If you want to try Simplictic framework. select according you are flashing version of simplistic. Incase simplistic doesn't work, you can restore your files.
7.Restore Utility - This will be menu page
There will be option to skip OR enter customiztion of restore.
All above option of backup will available here when you needs to restore.
EFS - A.Restore from IntSD B.Restore from ExtSD
Bloatware - Restore bloatware, if you have previously made backup
System Folder - A.Restore from DrKetanMod/app to System/app B. Restore from Dr.KetanMod/framework to System/framework
Simplistic - A.Odex B.Deodexed
8.Odex remover - This is Menu page
select skip OR enter to remove selected odex. This helpful when you flashing mod on odex rom doesn't have odex removal script
There is 19 common odex you can select any of it to remove
9.Customized bloatware remover
Now there is option to remove selected Bloatwares.
10.Customized CSC Features
You can have following CSC features. Thanks to @wesamothman and @MBariya for providing feature list. Just to add
-Backup is highly Recommended -Don't Use TRIGGER option first time -If you know your fetures file name is feature.cml and not others.xml then only select workaround option. - if first time regular flashing doesn't work, select only workaround option and flash. - still fail, select Trigger option + all requred feature and flash. - still fails select only workaround and flash - Still fails, Sorry hard luck, restore your backup.
11.Build Prop Tweaks
Following tweaks you can apply. Credits goes to original founder of tweaks, searched XDA for build.prop tweaked and selected some of it.
12.Lock Screen security bypass
You can use this if you forget PIN/Password/Pattern to remove it.
13.SystemPush - Push application to System folder
place apk and / or odex to sdcard/app folder to push system/app folder
place jar,apk and / or odex to sdcard/framework folder to push
system/framework folder
14.GPS/Glonass Fixer
Read This for more info, no need to download separately as it's included in tool.
15.Clean Device -
Use this to replace recovery with stock one, also remove old leftover of multiple superuser,su and busybox. still you will have root access to use triangle away
If your kernel is custom you have to use second option, as that will do above all plus replace custom kernel with stock one.
Will update screenshot later
Download
Dr.Ketan MultiTool Advance V2 [For 4.1.*]
Dr.Ketan MultiTool Advance V6 [For 4.3]
Older Vx
Dr.Ketan MultiTool Advance V1
Mirror
MultiTool V5 (For 4.3 OS) ---------- Mirror for V5 advance
Reserved one
Last one In case
Thanks a lot Doc for the tool and your entire contribution to the Note II comminity!! We sure will miss u! Just a request here: is it possible to work with another recovery, besides cwm? I'm using TWRP, hence the question. Thanks again!!
From the middle of nowhere to the center of everywhere!!
Yeah you can use CWM/TWRP
even you can change it from this tool only (without downloading).
chandoliasnikos said:
We sure will miss u!
Click to expand...
Click to collapse
How is that,did you bought other device doc???
I will go with Note3 once out.
May be this one last development for Note2 (unless change my mind )
Sad news for this section,where is the follow button????
I will supoort this section too but there will be little possibilities to develop without device. But sure still will be here for all newbies for their question on any of my thread.
I would like to try this out but I can't seem to find the link.
I guess host is still down. Will have to check after a few hours then. Thanks dr ketan.
We will miss dr ketan's apps and presence in note 2 forums.
Sorry for delay
Download link updated to OP
Finally good news for nOObs!
All in one toolbox by Dr.Ketan, waiting for few day for testing this tool.
Great Job Dr.Ketan. No need any extra zip files. only one file will do all things.
Will Miss your mods.
Can you please provide link for guide of Aroma installer. I have searched in xda forum but can't get proper result.
I have referred few, i will send you link tomorrow from office pc. But truly still not single guide there to explain everything. I have read a guide in note1 forum few days ago and I found it better than I referred.
Sent from my GT-N7100 using xda premium
I think one more utility we can add to this tool.
Flash own choice recovery kernel and modem. As many user still unable to manage flashable zip or tar from .img
So here you can put img file on sdcard and aroma can flash it.
Also looking forward to flash stock rom with aroma so no more prerooted rom you needs.
Sent from my GT-N7100 using xda premium
Hi dr ketan. I appreciate your hard work but your tool can't seem to save to my external sd card. The log says it is trying to create a directory in /external_sd but mine is /ExtSdCard. I think a rewrite of the code will solve the problem. I could send you the log file but I do not know how to attach it here.
Which ROM you have installed? and which recovery you have used ?
Next version have extra feature
- Flash your selected Recovery/modem/kernel from SDcard
You have to just keep your desired recovery.img/boot.img/modem.bin to Sd card.
No more need to have flashable zip OR tar.
HOW TO PORT ROMS TO YOUR MTK WITH ANDROID DEVICE
Most of us have always wanted to use custom roms but there just no custom roms for our devices so we just use different app launchers and uninstall some bloatware to make our stock rom feel good.
Rom porting makes it possible to use a custom rom on your mtk device provided in this tutorial they have the same chipset (example: mtk 6582 ported to mtk6582).
THINGS NEEDED :
1. B1 archiver / ES FILE EXPLORER
2. Root Browser.
4. A rooted device is also needed but not much important if you have CWM INSTALLED WITHOUT ROOT.
PROCEDURE :
1. Make a backup of your current rom, preferably CWM backup. You can either use MTK DROID TOOLS or ROM MANAGER...
The location of the backup will be at clockwork/backup/"date and time of the backup ". This is very important since we will need stuff from the back up and we will also use the backup to recover the phone should the ported rom give any problems.
2. At this point I presume you have already downloaded the apps needed and the custom rom you want to use which is in a zip format( this was not important but I had to bring it up cause I know zombies could be reading this.
3. Now extract the custom Rom with Root Browser. if you extracted with Root Browser then the location will be "speedsoftware/extracted/"folder with the name of the custom rom "".
4. Now open Root Browser and open the folders side by side "custom rom which will be ported at one side and other side will be used for searching for the location of the things needed for the custom rom.
5. Delete the following from the Custom rom:
Boot.img
logo.bin (You do this only when you like the Your current logo.bin)
system/vendor
system/usr
system/lib/hw
system/lib/modules
system/lib/libncurses.so
system/etc/firmware
system/etc/vold.fstab
system/etc/vold.fstab.nand
system/etc/bluetooth
6. Now that you have deleted them from the custom rom replace them. You will find the boot.img at clockworkmod/back/"folder with date and time"/boot.img. The rest of the files and folders will br located in the Root /system. Just copy and paste
7. Now at the custom Rom panel go back to where you find the "META-INF" folder,open /google/android will now long press on "updater script" and tap on open with then select text editor.
8. Check The mount & format point check something like this mmcblk0p. A number is always written after the "P" replace the number of your BASE to PORT.
9. Check multi select in B1 archiver Select ( do not archive the folder the files are in but the individual files in the folder containing the extracts)
10. Compress to ZIP file wait till the process finished. Now boot to recovery and flash your ROM
Good luck in porting Your Rom... I have used this method to port 5 roms including AROMA ROMS. and I have never ported a Rom with a pc before
MAYBE U NEED TO EXTRACT THE BOOT IMG TOO IF THIS DIDNT WORKED
DO IT AS FOLLOWS
Requirements:
-- BusyBox (cpio, gunzip and gzip is mandatory)
-- /System Write Permissions (Does not need to be a modified kernel)
-- Terminal Emulator
-- ES File Explorer (or similar)
-- Hex Editor (or use of DD)
-- Open up your android terminal emulator.
-- Now go ahead and pull your boot.img from your device (or use another one if you wish)
-- Open up your boot.img with the Hex Editor and look for: ANDROID!. Remove everything before it so that the ANDROID! header is the first to be read then save it over top of the boot.img. NOTE: This is only required if you are using a stock boot.img.
OR USE THIS IF U DIDNT UNDERSTOOD THIS
Hello Everyone, I’ll show you how to Unpack and Repack your Phone’s Boot.img & Tweak Karnel. Lets start.
Make a new folder named “boot edit” in cache/
image
Pull your boot.img in this folder
image
Now open ApkTool. Long press on “cache“, click on Get Access Permission.
image
Open cache folder and do same with boot edit. Give ApkTool access permission
image
Open boot edit, click on boot.img select Expack(MT65xx), press ok
image
It will unpack your boot.img.
image
Now open file manager & go to cache/boot edit/. You wil find your unpacked boot.
image
Now edit/modify the files or tweak karnel.
Again open ApkTool. Goto cache/boot edit click on ramdisk select repack-mt65xx.
image
It will repack your boot.
image
You will find an img file named new.img
image
This file is your Tweaked/edited/custom boot.img!!
Flash it via Recovery or Flashify & Enjoy..
FOR DETAILED AND STEP WISE GUIDE WITH SCREEN SHOTS SEE HERE
Mod Edit: link removed
XDA:DevDB Information
HOW TO PORT ROMS TO YOUR MTK WITH ANDROID DEVICE, ROM for all devices (see above for details)
Contributors
manhar2108, manhar2108, 2108kick
Source Code: Mod Edit: link removed
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: all
Version Information
Status: Stable
Created 2015-08-16
Last Updated 2015-08-16
HIT THANKS IF I HELPED U
Good guide..
Especially for noobs....
Darshan601 said:
Good guide..
Especially for noobs....
Click to expand...
Click to collapse
i too am a noob so i tried and made this guide
how bout porting 5.1 rom to 4.4.2 stock?
what should I consider?
aside from tweaking kernel
manhar2108 said:
i too am a noob so i tried and made this guide
Click to expand...
Click to collapse
Yeah....Even I am a noob
gunzgunz said:
how bout porting 5.1 rom to 4.4.2 stock?
what should I consider?
aside from tweaking kernel
Click to expand...
Click to collapse
just replace all these files and use stock kernal to port them
good luck
Sir i tried your guide in porting rom. Mt6582 tp mt6582 chipset roms.. But after replacing those files you mentioned and when i flashed it to my phone, it was tuck in boot screen and keep on restarting. How am I going to fix this?
Thread closed. Pay per click links are not allowed on XDA.
Darth
Forum Moderator
*****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?
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.