{Tutorials} Increase Apps Storage In Mtk devices - Miscellaneous Android Development

Increase Apps Storage Partition In Mediatek Devices​
FAQ :​
* Is It Safe To Increase Apps Storage Partition
- Yes
* From Where Storage Increasing In Apps Storage
- This Process Will Merge Internal Sd Card Storage To Apps Storage Partition
* How i can revert it If i neeeded Internal Storage
- Flash ur Stock Rom
* This is permanent No need to do again and again
DOWNLOAD :
1. Hex editor :http://d-h.st/idJ
2. Sp flash tool : http://d-h.st/ol7
Requirements :
1. Hex editor (Download from the above link)
2. Stock Rom (only needed ebr1 and ebr2 files)
3. Sp Flash Tool (Download from above link)
4 Little Knowledge about flashing Rom through Sp Flash tool
Notes :
1. After Doing This process your data will be formatted ,Make sure u backup Your Rom Or Data
2. Backup your Internal Sd before doing this process
Procedure :​
1. Install Hex Editor In your Pc
2. Extract your Stock Rom and Grab ebr1 and ebr2 file and copy to ur desktop
3. Open Both ebr1 and ebr2 Files In Hex editor
4. Now go to ebr1 File tab Scroll Down And There you will notice 4 blocks these are Partition Line (see ss which partition going to edit in nxt step)
5. Now See In screenshots the one Is highlighted In Red you Need to increase +1 (This +1 increase 500Mb in your apps storage and decrease 500Mb from Internal Storage)
Notes: use table which is given below to calculate it then do +1 and -1 (sum and addition like A=10 and 1=1 which will become after adding 11)
This is table you have to use to add +1 and -1
Dec-Hex
0 = 0
1 = 1
2 = 2
3 = 3
4 = 4
5 = 5
6 = 6
7 = 7
8 = 8
9 = 9
10 = A
11 = B
12 = C
13 = D
14 = E
15 = F
Click to expand...
Click to collapse
{
"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"
}
6. Now Go to Ebr2 file Tab scroll down and there you will get 2 partition line (see ss which partition needed to edit in next step)
7.Now See ss There u will need to edit 2 blocks first need to increase +1 and in second block decreases to -1 (see in ss)
8. Again use table which is in steps 5.
9. save it both files.
10. Now load scatter file of your stock rom in sp flash tool, After loaded all files untick all except ebr1 and ebr2 file ,Double click on the ebr1 file and browse and select new saved ebr1 file and do same as ebr2
11. Click on Download and connect your cell (Make sure u installed driver properly)
12. After green window shown, Disconnect your cell and go to cwm recovery or stock recovery
13. Click on format data/cache factory reset and also do cache wipe
14. Restore your Rom or Data
15. After reboot ur phone from cwm or stock recovery and If Internal SD storage showing format do format
16. enjoy with increased apps storage..
Here Is the Final SS (Note: Am using Color Rom By me with swaped sd card in c2+, phone storage showing sd card )
List Of Device Successfully Increased There Apps Storage​
1. Micromax A117 (Magnus)...............By Johnny199314
2. Starmobile Diamond V7..................By chleoj

[email protected] said:
Increase Apps Storage Partition In Mediatek Devices​
FAQ :​​​
* Is It Safe To Increase Apps Storage Partition
- Yes
* From Where Storage Increasing In Apps Storage
- This Process Will Merge Internal Sd Card Storage To Apps Storage Partition
* How i can revert it If i neeeded Internal Storage
- Flash ur Stock Rom
* This is permanent No need to do again and again
DOWNLOAD :
[1. Hex editior :http://d-h.st/idJ
2. Sp flash tool : http://d-h.st/ol7
Requirements :
1. Hex editor (Download from the above link)
2. Stock Rom (only needed ebr1 and ebr2 files)
3. Sp Flash Tool (Download from above link)
4 Little Knowledge about flashing Rom through Sp Flash tool
Notes :
1. After Doing This process your data will be formatted ,Make sure u backup Your Rom Or Data
2. Backup your Internal Sd before doing this process
Procedure :​
1. Install Hex Editor In your Pc
2. Extract your Stock Rom and Grab ebr1 and ebr2 file and copy to ur desktop
3. Open Both ebr1 and ebr2 Files In Hex editor
4. Now go to ebr1 File tab Scroll Down And There you will notice 4 blocks these are Partition Line (see ss which partition going to edit)
5. Now See In screenshots the one Is highlighted In Red you Need to increase +1 (This +1 increase 500Mb in your apps storage and decrease 500Mb from Internal Storage)
Notes: use table which is given below to calculate it then do +1 and -1 (sum and addition like A=10 and 1=1 which will become after adding 11)
6. Now Go to Ebr2 file Tab scroll down and there you will get 2 partition line (see ss which partition needed to edit)
7.Now See ss There u will need to edit 2 blocks first need to increase +1 and in second block decreases to -1 (see in ss)
8. Again use table which is in steps 5.
9. save it both files.
10. Now load scatter file of your stock rom in sp flash tool
11. After loaded all files untick all except ebr1 and ebr2 file ,Double click on the ebr1 file and browse and select new saved ebr1 file and do same as ebr2
12. Click on Download and connect your cell (Make sure u installed driver properly)
13. After green window shown, Disconnect your cell and go to cwm recovery or stock recovery
14. Click on format data/cache factory reset and also do cache wipe
15. Backup your Rom or Data
16. After reboot ur phone from cwm or stock recovery and inrernal storage showing format do format
17. enjoy with increased apps storage..
Click to expand...
Click to collapse
Bro screen shots image corrupted pls upload new one
Sent from my Micromax A117 using XDA Premium 4 mobile app

[email protected] said:
Increase Apps Storage Partition In Mediatek Devices​
FAQ :​​​
* Is It Safe To Increase Apps Storage Partition
- Yes
* From Where Storage Increasing In Apps Storage
- This Process Will Merge Internal Sd Card Storage To Apps Storage Partition
* How i can revert it If i neeeded Internal Storage
- Flash ur Stock Rom
* This is permanent No need to do again and again
DOWNLOAD :
[1. Hex editior :http://d-h.st/idJ
2. Sp flash tool : http://d-h.st/ol7
Requirements :
1. Hex editor (Download from the above link)
2. Stock Rom (only needed ebr1 and ebr2 files)
3. Sp Flash Tool (Download from above link)
4 Little Knowledge about flashing Rom through Sp Flash tool
Notes :
1. After Doing This process your data will be formatted ,Make sure u backup Your Rom Or Data
2. Backup your Internal Sd before doing this process
Procedure :​
1. Install Hex Editor In your Pc
2. Extract your Stock Rom and Grab ebr1 and ebr2 file and copy to ur desktop
3. Open Both ebr1 and ebr2 Files In Hex editor
4. Now go to ebr1 File tab Scroll Down And There you will notice 4 blocks these are Partition Line (see ss which partition going to edit)
5. Now See In screenshots the one Is highlighted In Red you Need to increase +1 (This +1 increase 500Mb in your apps storage and decrease 500Mb from Internal Storage)
Notes: use table which is given below to calculate it then do +1 and -1 (sum and addition like A=10 and 1=1 which will become after adding 11)
6. Now Go to Ebr2 file Tab scroll down and there you will get 2 partition line (see ss which partition needed to edit)
7.Now See ss There u will need to edit 2 blocks first need to increase +1 and in second block decreases to -1 (see in ss)
8. Again use table which is in steps 5.
9. save it both files.
10. Now load scatter file of your stock rom in sp flash tool
11. After loaded all files untick all except ebr1 and ebr2 file ,Double click on the ebr1 file and browse and select new saved ebr1 file and do same as ebr2
12. Click on Download and connect your cell (Make sure u installed driver properly)
13. After green window shown, Disconnect your cell and go to cwm recovery or stock recovery
14. Click on format data/cache factory reset and also do cache wipe
15. Backup your Rom or Data
16. After reboot ur phone from cwm or stock recovery and inrernal storage showing format do format
17. enjoy with increased apps storage..
Click to expand...
Click to collapse
Dude - screen shots are not working. Kindly reupload them.

Guys I was able to find a very easy way of extending the phone storage. Kindly go to the following link and that will help anyone with MTK processor 6589 version.
http://forum.xda-developers.com/showpost.php?p=49094782&postcount=287

kailashnj said:
Guys I was able to find a very easy way of extending the phone storage. Kindly go to the following link and that will help anyone with MTK processor 6589 version.
http://forum.xda-developers.com/showpost.php?p=49094782&postcount=287
Click to expand...
Click to collapse
The meteos tool does not work on the OPPO R819, it bricks the phone requiring flashing of the stock ROM with the flash tool. Just a warning to the R819 users, as this has been already tried 2 months ago.

@ccav2000 u can use my post to do am adding ss
Sent from my Nexus 4 using XDA Premium 4 mobile app

[email protected] said:
@ccav2000 u can use my post to do am adding ss
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm, I may try it, I do have the complete recovery package for the OPPO R819 if it bricks but not sure when.

Ss added

ccav2000 said:
The meteos tool does not work on the OPPO R819, it bricks the phone requiring flashing of the stock ROM with the flash tool. Just a warning to the R819 users, as this has been already tried 2 months ago.
Click to expand...
Click to collapse
Hi,
Are you sure you used the 6589 meteos tool. Probably you would have used the 657X tool and that will brick your phone. I did that myself too and did not realise it. Try it with the 6589 meteos tool and check if its sucessful and let me know the outcome.

-deleted-

kailashnj said:
Hi,
Are you sure you used the 6589 meteos tool. Probably you would have used the 657X tool and that will brick your phone. I did that myself too and did not realise it. Try it with the 6589 meteos tool and check if its sucessful and let me know the outcome.
Click to expand...
Click to collapse
I cannot confirm because it was not me that tried it. A forum member in the OPPO forums did it and he told me, also he gave me the recovery tools he got from their support, including the necessary drivers, OPPO specially modified SP-Flash tool and the ROM.
Also, the OPPO R819 only has TWRP, in the Meteos thread CMW is refered as required, not sure if that plays a role.

If I want to follow your tutorial, should I root first my phone or not?
Thanks.

max_82 said:
If I want to follow your tutorial, should I root first my phone or not?
Thanks.
Click to expand...
Click to collapse
Rooting is irrelevant for this guide, possesion of the SP-Flash tools and the necessary ROM package is all you really need.

ccav2000 said:
I cannot confirm because it was not me that tried it. A forum member in the OPPO forums did it and he told me, also he gave me the recovery tools he got from their support, including the necessary drivers, OPPO specially modified SP-Flash tool and the ROM.
Also, the OPPO R819 only has TWRP, in the Meteos thread CMW is refered as required, not sure if that plays a role.
Click to expand...
Click to collapse
In that case try it out using this trick. It might help.
max_82 said:
If I want to follow your tutorial, should I root first my phone or not?
Thanks.
Click to expand...
Click to collapse
You will need rooted phone.

kailashnj said:
In that case try it out using this trick. It might help.
You will need rooted phone.
Click to expand...
Click to collapse
I was looking at the EBR files of another guide here in XDA for the A116 and there seems to be a difference there, the changed value in EBR2 at the 01cc offeset, they changed the first digit, while on this tutorial here the second diggit is changed. Could this indicate different parition schemes? If OPPO also has different partitions, perhaps that is why the Meteos app killed the R819. The R819 has 16GB of ROM, most other MTK6589 have up to 8GB.
---------- Post added at 01:00 PM ---------- Previous post was at 12:47 PM ----------
To be sure: These are the mount points of the OPPO R819:
Code:
lrwxrwxrwx root root 1970-01-01 00:00 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 00:00 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 00:00 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 00:00 [email protected] -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 00:00 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 00:00 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 00:00 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 00:00 [email protected] -> /dev/block/mmcblk0p7
And the mount points:
Code:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p6 on /cache type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk0p8 on /sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p8 on /and-sec type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p5 on /system type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk0p7 on /data type ext4 (rw,relatime,data=ordered)

ccav2000 said:
I was looking at the EBR files of another guide here in XDA for the A116 and there seems to be a difference there, the changed value in EBR2 at the 01cc offeset, they changed the first digit, while on this tutorial here the second diggit is changed. Could this indicate different parition schemes? If OPPO also has different partitions, perhaps that is why the Meteos app killed the R819. The R819 has 16GB of ROM, most other MTK6589 have up to 8GB.
---------- Post added at 01:00 PM ---------- Previous post was at 12:47 PM ----------
To be sure: These are the mount points of the OPPO R819:
Code:
lrwxrwxrwx root root 1970-01-01 00:00 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 00:00 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 00:00 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 00:00 [email protected] -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 00:00 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 00:00 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 00:00 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 00:00 [email protected] -> /dev/block/mmcblk0p7
And the mount points:
Code:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p6 on /cache type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk0p8 on /sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p8 on /and-sec type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p5 on /system type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk0p7 on /data type ext4 (rw,relatime,data=ordered)
Click to expand...
Click to collapse
This mount point is same as in Micromax C2+ which i used to increase the apps storage ,Hence it will work on OPPO R819

Bro in ebr 2 there is c0 how should I decrease pls help
Sent from my Micromax A117 using XDA Premium 4 mobile app
---------- Post added at 07:27 PM ---------- Previous post was at 07:25 PM ----------
Will this method work in Magnus mtk turbo processor
Sent from my Micromax A117 using XDA Premium 4 mobile app

@ johnny199314 c0 = 12 mean u add there B0=11
Sent from my Nexus 4 using XDA Premium 4 mobile app

[email protected] said:
@ johnny199314 c0 = 12 mean u add there B0=11
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Bro there was 3d I increase it to 4d there is c0 how should I decrease that
Sent from my Micromax A117 using XDA Premium 4 mobile app

@Johnny199314 read the table and see the ss u need to +1 in 1 block and -1 in second block in ebr2
remove c and add here b0
Sent from my Nexus 4 using XDA Premium 4 mobile app

Related

[Guide] [Port] TWRP recovery in 5 minute's easy and Simple way...

Hi guys...
Here is my Xtreme and Simple guide for porting TWTRP Recovery from mobile in 5 minutes... Maybe not works in snapdragon devices...
Though there are a lot of guides in XDA But i didn't find any Simple guide...
So i write this Specially for Noobs Friendly...
I hope you will enjoy it...
Wants to port CTR or CWM recovery?!!
Follow my Another Guide Here ->
http://forum.xda-developers.com/showthread.php?t=2862806
_____________________________________
Post ->
1.Post 1 -> Setting up invaiourments...
2.Post 2 -> Finding EMMC BLK no...
3.Post 3 -> Unpacking...
4.Post 4 -> Porting...
5.Post 5 -> Repacking...
6.Post 6 -> Simple bug fixing...
_____________________________________
Post 1
_____________________________________
Post -> 1
-----------
Setting up Envaiourments
--------------------------
For Mobile Users
------------------
First Download Letast Apktools From Here-> ( http://code.google.com/p/android-apktool/downloads/list )
Now Extract the zip in your sdcard not in any folder...
Then you will see apktool folder in your Sdcard...go to apktools folder and install Apktool4.4.1.apk...But Don't open it...
Now Download Letast Busybox pro.apk from here -> http://forum.xda-developers.com/attachment.php?attachmentid=433705&d=1288878272
Then install it and open it...wait there untill the loading finished...After 100% loading Click on install botton in left Corner...Done!
Now download Root Explorer From play store...
install it and open...go to /data folder then you will need Root permission.Click in grant... Done!
Then install Notepad++..this for mobile user ->
http://goo.gl/mbwgkr
Now you Can open your Apktools...
_____________________________________
Post 2
_____________________________________
Post->2
---------
Finding Emmc BLK no
---------------------
To port any Recovery you must need to know about this BKL no...
1.System BLK no...
2.Cache BLK no...
3.Data BLK no...
4.Vfat BLK no...
If you don't know then follow this post...
-------------------------------------
Open Root Explorer...Go to Root Tab..(/)...Find these files in Root Tab...
[email protected](This is your system blk no)
[email protected](this is your cache blk no)
[email protected](this is data blk no)
[email protected](and this is vfat blk no)
After finding these just see Down of this files Name...you will see all BLK no...
like in my device ->
[email protected]
01 jan 70 06.00.00 ->mmcblk0p4 rwxrwxrwx...
[email protected]
01 jan 70 06.00.00 ->mmcblk0p5 rwxrwxrwx...
[email protected]
01 jan 70 06.00.00 ->mmcblk0p7 rwxrwxrwx...
[email protected]
01 jan 70 06.00.00 ->mmcblk0p6 rwxrwxrwx...
_____________________________
just copy these mmcblk on with there name...in a notepad like ->
[email protected] -> mmcblk0p4,
[email protected]>mmcblk0p5,
[email protected]>mmcblk0p7,
[email protected]>mmcblk0p6,
...Done!
N.B -> These blk no's are not same in all device...So,Don't copies another devices blk no...
_____________________________________
Post 3
_____________________________________
Post -> 3
-----------
Unpacking
-----------
First make a new folder name (Porting Recovery) in your sdcard.Then open it and create two new folders like ->
1.Stock
2.TWRP
Now take your stock recovery...(If you don't have then ask another users...)
Then copy the Stock Recovery in Stock folder...
Now download TWRP Recovery...(If you download twrp of another device,then your device.But one thing if your device has 6 mb recovery pertitions,your downloaded TWRP recovery must be under 6 mb...and you can port you recovery from (mtk <-> mtk)....
Now copy your downloaded TWRP recovery in TWRP folder...
Now open Apktools and Go to Stock folder click on Stock recovery.img and click on (Expack->65xx needs root)...and Wait some minutes...
Done!!
Now unpack your TWRP recovery.img in the same way...
Done!!!
_____________________________________
Post 4
_____________________________________
Post -> 4
-----------
Porting
---------
After unpacking go to Stock folder...then you will see these folder and files there...
1.Ramdisk (Folder)...
2.Karnel...
3.ramdisk.cpio.gz...
______________________
Copy (Karnel) in a new folder...
Then go to Ramdisk folder again and copy these files to new folder ->
1.ueventd.goldfish.rc...
2 ueventd.rc...
______________________
Now open your New folder and copy the (karnel).go to TWRP Folder and paste it there and click on Replaced...
Now again go to new folder and Copy
1.ueventd.goldfish.rc...
2 ueventd.rc...
Then go to TWRP folder...Open Ramdisk Folder and Paste them there...And Replaced...Done!
______________________
Now again go to TWRP Folder...Then in Ramdisk folder...Then go to etc folder and open (recovery.fastab) in notepad...
You will see sometings like this ->
______________________
(# mount point fstype device [device2]
/boot emmc /dev/bootimg flags=display="Boot";backup=1
/recovery emmc /dev/recovery flags=display="Recovery";backup=1
/misc emmc /dev/misc flags=display="Misc";backup=1
/nvram emmc /dev/nvram flags=display="Nvram";backup=1
/uboot emmc /dev/uboot flags=display="Uboot/LK";backup=1
/logo emmc /dev/logo flags=display="Boot Logo";backup=1
/system ext4 /dev/block/mmcblk0p5 flags=display="System";backup=1
/cache ext4 /dev/block/mmcblk06 flags=display="Cache";backup=1
/data ext4 /dev/block/mmcblk0p7 flags=display="Data";backup=1
/emmc vfat /dev/block/mmcblk0p8 flags=display="Phone Storage";storage;wipeingui
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="SDcard";storage;wipeingui
/sd-ext vfat /dev/block/mmcblk1p2 /dev/block/mmcblk2 flags=display="SD-ext";storage;wipeingui
/usb-otg auto /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable)
__________________________
First find this line ->
system ext4 /dev/block/mmcblk0p5 flags=display="System";backup=1
Here paste the mmcblk no of -> [email protected] you copied in notepad..
Like my [email protected] blk no is -> mmcblk0p4...
So just replaced mmcblk0p4 with mmcblk0p5 and the line will look like. ->
system ext4 /dev/block/mmcblk0p4 flags=display="System";backup=1
Do same with this lines ->
/cache ext4 /dev/block/mmcblk06 flags=display="Cache";backup=1
In this line just replaced your [email protected] blk no...like myone is -> mmcblk0p5...
So the line will look like this ->
cache ext4 /dev/block/mmcblk05 flags=display="Cache";backup=1
Now search this line ->
/data ext4 /dev/block/mmcblk0p7 flags=display="Data";backup=1
Here just replaced your [email protected] blk no...like myone is -> mmcblk0p6
So the line must look like this ->
/data ext4 /dev/block/mmcblk0p6 flags=display="Data";backup=1
Now search this line ->
/emmc vfat /dev/block/mmcblk0p8 flags=display="Phone
and Replaced your [email protected] blk no...like myone is -> mmcblk0p7
so the line must be look like this ->
/emmc vfat /dev/block/mmcblk0p7 flags=display="Phone
all done now save it...
Now go to TWRP folder again...and open Default.prop...this file are same like your build.prop...So change this as your edit your build.prop...but don't change all line...just product names,etc,etc...
N.B -> Sometimes you may not find this file (ueventd.goldfish.rc)...If you don't find it in your unpacked TWRP,then don't copy it from Stock Recovery and just ignore this file...I hope you understand...
____________________________________
Post 5
____________________________________
Final Post -> 5
-----------------
Repacking
-----------
Go to TWRP and click on Ramdisk and You will repack option... just click on (repack-mt65xx(need root))...and after repacking you will see (new.img)...Done!You did it man...now just flash it via Recovery tools.apk or Rashr.apk...and go to recovery and see magics...
_____________________________________
Post 6
_____________________________________
Post -> 6
-----------
Simple bug fixing
-------------------
Sometimes ported TWRP may be showed a large Icons which is so disgusting...Now to fixing it see my.simple tips ...
___________________
First download a new themes for twrp...like -> your device regulations is 480*800...So go to google and search some themes ..like -> (TWRP V2.7.0.0 Themes 480*800 XDA )...This and you will find a batter results... Now download some themes and copy them in a folder name Themes...then Extract one theme...then you will see somethings like these ->
1.images
2.fonts
3.ui.xml....
Now Unpack your ported TWRP in a new folder...then go to themes folder (Where you extracted these themes) And copy ->
1.images
2.fonts
3.ui.xml....this files
Now go to New folder (Where you unpacked your ported recovery)...then go to res folder and paste thats there...and Replaced...Done! Now repack your recovery again And flash it via Recovery tools or Rashr.apk...and See Magics again
Sometimes you may fall in this problems like ->
1.Can't take backup...
2.System wasn't mounted...
3.Can't find Recovery and boot pertition...
4.bla..bla...
if you fall in thats problems then unpack your recovery and go to Ramdisk/etc and open recovery.fastab and see that you made any mistake in Replacing thats mmcblk no...Or if you can't understand then post in here..may i can help you...
_____________________________________
Done Everything guys...now you are a developer... ...lol... B|
Facing problems?!!Comments here...i try my best to help you...Thanks for reading... and Sorry for my bad English
_____________________________________
Happy Porting and never stop customizations...
All post written by: MD.S...
____________________________________
Nice Guide Man...
Now trying it...
Nice job bro...
Hi, @Md.Shafikul.islam
First thanks for this guide...But I have some problems...
I can't take backup from my Recovery...Can you help me Please
Nice job!
Good work!
But not working on my Wiko Cink Peax 2 (mtk 6589).
I followed step by step your guide. But.....
Thank you.
Now Working
MD Thanks ...
Now running good in my mtk6572...
Thumbs up for help...
Bad luck bro...
Bouziane_Dr said:
Good work!
But not working on my Wiko Cink Peax 2 (mtk 6589).
I followed step by step your guide. But.....
Thank you.
Click to expand...
Click to collapse
Bad Luck bro... but I think it works o
in every mtk...ok let me try in mtk6589...
Thread closed so that you don't keep chatting to yourself and thanking yourself with your multiple XDA accounts...

[SCRIPT][DUAL-BOOT][I9305] db

(Sorry for english !!)
!! Some problems with Android 5.1.x installed on External.
[Dual-Boot] I9305 [SCRIPT]
Hi. Because i dont find any kernel/script for I9305 with Dual-Boot, i try to make this script for test roms (but can be use day by day without problem).
This script help to patch .zip rom/kernel/gapps (and other i think) for install him on SDCARD. (without touch your internal rom).
How can you do this? Need to repartition your sdcard in 3 parts
1. With your sdcard data (files/music..etc)
2. external System (for system rom)
3. external Data (for data rom)
What you need to know !!!!
- Thanks on @Nicene Nerd for this App. I'm inspired from him.
- I'm not a developer.
- I don't now so much about linux (so, script not have a best optimization)
- This script is better good for people who test roms (like Lollipop).
- If you dont try this script, don't say anything. (only if you have some problem/stucks)
- Install on Internal roms like: Amcha / N4 / ..etc (big roms)..because i try to install on external rom and dosen't work
- Rom like Nameless / RR / ..etc can be install on external
- Anyone who want help me to make this script better, say here where need to edit (with what) and who can code help
- Say here what rom/kernel/script work or dosen't work to install on external. For modify script
What you need.
MiniTool Partition Wizard (or other program to repartition sdcard)
USB Cable (for repartition)
A phone (i9305 of course)
SDCARD 16gb (or more) Class 10 (if you have class 4 or other..your external rom run slow)
Backup your sdcard data (for safe)
Backup your phone (for safe)
ROM with root permision.
Water (because is good for your health)
First time you need to repartition sdcard
First partition: FAT32 (split memory from this..is good option)
Second: 1600 mb (1,6 gb) for system
Third: 2500 mb (2,5 gb) minimum memory for data
How can do this:
On MiniTool show your sdcard (like this)
{
"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"
}
1. Right click on him > Split
2. On New Partition Size you need to have minimum (system + data) 1600 + 2500 = 3600 mb (3,6 gb)..If you want more memory on data, you can type more than 3600 mb (i need more so i split 7000 mb)
After write your value, press ok
Now look like this
3. Right click on new partition (H on me) > Delete
Now you have unallocated partition
4. Right click on unallocated partiton > Create > Ok (on warning)
5. On box you need to edit:
Create As: Primary
File System: Ext4
Partition Size: 1600 (because is system partition)
After this. Press Ok
6. Right click on unallocated partition > Create > Ok (on warning)
Create As: Primary
File System: Ext4
Partition Size: dont modify
After this. Press Ok
7. Before press Apply, check if look like this
Now you can press Apply and wait
Good
After sdcard was partitioned, go to next step
Put my script on your SDCARD
(Why in sdcard? because internal/external rom view the sdcard everytime)
(internal/external rom have separated 'internal memory')
1. Unrar on desktop (right click on archive > extract here)
2. Copy 'db' folder to your sdcard
3. Check if 'db' folder is on your sdcard
4. With file explorer (i use Root Browser), go to db folder and install 'terminal.apk'
5. After install run him
On terminal:
Type: su (for superuser permision)
Type: cd /mnt/extSdCard/db (or anywhere is db folder location..on LolliPop is: cd extSdCard/db)
Type: sh db.sh
Now you are in script menu
Option: 1 -> Save Internal BOOT.IMG
Option: 2 -> Flash Internal BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 3 -> Mount Internal partitions on root direcotry (/.dbSystem & /.dbData)
Option: 4 -> Clean Internal partitions (use this if you are in External rom)
Option: 5 -> Save External BOOT.IMG
Option: 6 -> Flash External BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 7 -> Mount External partitions on root direcotry (/.dbSystem & /.dbData)
Option: 8 -> Clean External partitions (use this if you are in Internal rom)
Option: 9 -> Patch file for External rom (file like rom/gapps/pa-gapps/kernel..etc)
Option: 0 -> uMount /.dbSystem & /.dbData
Option: fb -> Flash manualy BOOT.IMG file
Option: ie/ei (hidden command) -> I'm work on this.. Is a experimental function. Don't use it
Patch files for external rom:
1. Copy on 'db' folder rom who want to patch, gapps archive and kernel your need
2. Run script on terminal
3. Need to save your Internal boot.img (Option 1 on menu)
4. Option 8 to clean your external partitions (if was used before with other rom).
5. Option 9 to patch
6. Type rom/gapps/kernel..etc archive name like: my_rom.zip > And press enter
7. Wait to patch (all patched files have pre name ext-
NOTE: If you patch rom/kernel (with boot files), you need to watch if script modify any fstab file. If no, external rom not work!
8. After you patch all you archive need..go to recovery (i use TWRP 2.8.5.0) and flash him but need to kep order:
- First ROM zip
- Second GAPPS (or PA-GAPPS) (or without this)
- Third KERNEL (if is need)
- .. other patched scripts
9. After flashing, reboot and wait to new external rom start up
(if you have any error (boot loop/other) you can flash internal boot stored in "sdcard/db/.db/.imgs/boot-int.zip")
10. After your external rom is ON, install 'terminal.apk' from sdcard
11. Run script on terminal
12. Save your External BOOT.IMG (Option 5)
13. Enjoy with your external rom.
(To switch rom you have option 2 and 6 or flash manualy .zip stored in "sdcard/db/.db/.imgs/boot-*.zip")
I forgot something?
Another explain: http://forum.xda-developers.com/showpost.php?p=59570171&postcount=11
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
Version 1.0:
+ It's alive !
thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?
LeoDeos said:
thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?
Click to expand...
Click to collapse
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion
il3gal said:
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion
Click to expand...
Click to collapse
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?
LeoDeos said:
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?
Click to expand...
Click to collapse
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?
il3gal said:
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?
Click to expand...
Click to collapse
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?
LeoDeos said:
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?
Click to expand...
Click to collapse
aaaaaa...no..
il3gal said:
aaaaaa...no..
Click to expand...
Click to collapse
ok thanks
LeoDeos said:
ok thanks
Click to expand...
Click to collapse
I make now how i use this script ..with images..
Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.
Explain 2
I made a tutorial how i use this script. Skip the repartition step because is easy (repartition need to make one time..not everytime want you install external rom)
On my rom (N4 Elite Lite v5).
1. Copy what files need to patch in db directory (where is script). In my case (pa_gapps-modular-pico-5.0.1-20150221-signed.zip & nameless-5.0.2-20150318-i9305.zip)
2. Run script.
3. First time need to save your internal boot.img (kernel). (for swich roms)
(because script modify kernel (mount point on kernel) and when you swich rom, all who make script is to flash kernel for internal/external rom)
4. After you save internal kernel, go back to menu and type option 9 to patch zip rom/gapps/kernel..etc
(if rom have a included kernel, watch if script find a fstab.* file and if can be edited. If not edited, external rom not work)
(all rom/kernel/gapps..other script need to modify updater-script or update-binary (pa-gapps use this)..if not edited, you cannot install rom on external partitions
5. After i patch rom file, i need and gapps because i use Google Play Store, so, i patch and gapps (go in menu, option 9 and type gapps file name)
(Now my db directory look like this)
6. All good. Now i want to be sure about my external partitions is clean, and i go to option 8 to clean him
7. After clean, reboot in recovery and flash ROM (ext-nameless-5.0.2-20150318-i9305.zip) and after GAPPS (ext-pa_gapps-modular-pico-5.0.1-20150221-signed.zip)
8. Reboot phone and wait to rom boot complete..(first boot may during a time)
(At Total Memory, is total memory allocated on 'data' partition (from repartition) (third partition))
9. After boot is complete..install 'terminal.apk' from db folder (script folder)
10. Run script from terminal.
11. Option 5 (for save this external boot.img)
12. Voila..now i have 2 separated roms..installed in 2 separate partitions (internal system/data and external system/data)
To swich i have 2 option. From terminal (script). (example) If i'm in internal rom and i want to swich, open script an type option 6..For flash external kernel and reboot phone to boot in external rom.
From recovery: flash manualy .zip files stored in sdcard/db/.db/.imgs/boot-*.zip
Now is good explication?
djb77 said:
Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.
Click to expand...
Click to collapse
Is not same. Do you know dual windows on pc?
Partiton C have Windows 7 (example)
and partition D have Windows 8.1 (for example)
If you boot pc, have a question "Who windows want to boot" 7 or 8.1..and you choose.
My script is same, but for 'choose', need to flash a kernel (external/internal..depend what you want to boot)
hmm.
This script is same with http://forum.xda-developers.com/showthread.php?t=2639112 ...but is not app..and dont have some options like "backup"..
Tested with:
ROM
- AICP 8.0
- Resurrection Remix® LP
- NamelessROM
- Cyanogenmod 12
- SlimLP
KERNEL
- Boeffla 3.0-alpha9
Changelog
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
I see some people was download script. Can give me feedback? (db_1.0.rar - [Click for QR Code] (1.11 MB, 32 views))
What rom is work and what not? (i dont have time to test all roms)
Abandoned.
il3gal said:
Abandoned.
Click to expand...
Click to collapse
why?
LeoDeos said:
why?
Click to expand...
Click to collapse
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this
il3gal said:
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this
Click to expand...
Click to collapse
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method
LeoDeos said:
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method
Click to expand...
Click to collapse
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.
il3gal said:
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.
Click to expand...
Click to collapse
thanks
+Tested with:
ROM
- AICP 9.0 (test version)
Changelog
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)
+Tested with:
ROM
- N4 Elite Lite v7 (but i don't now how much fast is) (when i have time, i will tested)
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Who know a universal reboot command for any rom? Because reboot not work on N4 Elite Lite rom

[GUIDE] How To Root Micromax Canvas Xpress 4G Q413-CWM/TWRP

How to root Micromax Canvas Xpress 4G?​
Micromax Canvas Xpress 4G Q413 is running on Android LOLLIPOP and using Mediatek chipset MT6735P
How to ROOT Micromax Canvas Xpress 4G (Q413)?
1.One-Click-Root apps - FAILED
2.Porting ClockWorkMod using MTK droid tools - FAILED
(Because that does not support MT6735P chipset)
Click to expand...
Click to collapse
So What is NeXt?
Porting ClockWorkMod(CWM) recovery to this mobile i.e Compiling recovery from source
So we can flash superSU flashable zip through CWM to get ROOT access.
What I did exactly is ported ClockWorkMod(CWM) recovery to Micromax Canvas Xpress 4G
Now focus on What should you do to ROOT
1.Flash CWM using SP flash tool (Also TWRP is available)
2.Flash "UPDATE-SuperSU-v2.46.zip" ZIP package through ClockWorkMod (CWM).
Very EASY...
What do you need?
1.A PC/Laptop with windows 7/8/8.1/10
2.Drivers for Micromax Canvas Xpress 4G (Use link in STEP 6)
3.SP Flash Tool
4.UPDATE-SuperSU-v2.46.zip
5.Micromax Canvas Xpress 4G mobile
6.All Files From This Link
7.ADB and FASTBOOT drivers (Use link in STEP 6)
8.USB VCOM drivers (open READ_ME.txt from the link in STEP 6)
Preparation...
1.Goto Settings >> About phone and tap continuously Build Number until you see "You are now a developer" message.
2.Now get back to settings and click Developer Options
3.Now turn on "Allow OEM Unlocking" and "USB Debugging"
1.Flashing CWM
i).Open SP flash tool and load scatter file (from the link)
ii).Locate recovery-cwm.IMG(from link) in recovery,uncheck all and check only recovery
iii).Pull out your battery and insert it,DON'T TURN ON YOUR PHONE
iv).Click "Download" in SP Flash Tool and connect your phone to PC using USB cable
v).You will promoted with a big green tick.Done
2.Flash "UPDATE-SuperSU-v2.46.zip" ZIP package
i).Place "UPDATE-SuperSU-v2.46.zip" in your sd card
ii).Turn off your device
You may also use the following code while your phone is turned on
Code:
adb reboot recovery
and skip to STEP (v)
iii).Press "Power" & "Volume Down" until you see some options
(Here "Volume Down" = DOWN and "Volume Up" = OK )
iv).Choose Recovery by pressing "Volume Up"
v).In ClockWorkMod recovery choose "Install ZIP from sdcard"
(Here "Volume Down" = DOWN "Volume Up" = UP and "Power" = OK )
You may also choose Install From Sideload
Code:
adb sideload path/to/UPDATE-SuperSU-v2.46.zip
vi).Now locate "UPDATE-SuperSU-v2.46.zip" in your sd card and press POWER KEY
vii).After installition choose REBOOT.........Done!
All done..,you have rooted your device.:highfive::good:
If u have any problem post here.
EDIT: TWRP Added.
It is RECOMMENDED To Use it...
Check link #3 below"
Click to expand...
Click to collapse
Credits
[+]Mr.ChainFire for SuperSU
[+]Mr.Koushik Dutta for original ClockWorkMod
[+]TWRP Team
[+]All developers on XDA for wonderful guides and support
Thanks and salute to them
Click to expand...
Click to collapse
Download Links
1.SP Flash Tool
2.UPDATE-SuperSU-v2.46.zip
3.All Files From This Link
Take a note....
Don't use scatter file from the stock rom posted on androidmtk.com
This ClockWorkMod can be easily ported to other devices running on MT6735P/M chipset by replacing kernel.
Awesome JOB...Love it
aravazhi_mdr said:
Don't use scatter file from the stock rom posted on androidmtk.com
This ClockWorkMod can be easily ported to other devices running on MT6735P/M chipset by replacing kernel.
Click to expand...
Click to collapse
Awesome job...didn't know someone would get a recovery for this phone...actually most of mtk built phones are neglected as mtk doesn't release Sources or some other issue...But Thank You....any hopes of having cyanogenmod ROM for this device?
pbababab said:
Awesome job...didn't know someone would get a recovery for this phone...actually most of mtk built phones are neglected as mtk doesn't release Sources or some other issue...But Thank You....any hopes of having cyanogenmod ROM for this device?
Click to expand...
Click to collapse
I don't hope anyone will post cyanogenmod ROM for this device (As of now)
We have to port it ourself.
I think Xposed installer will help our phone to rock...
Will the device have otg support after the root?????
---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------
Will the device have otg support after the root???
May be
Nangshi said:
Will the device have otg support after the root?????
---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------
Will the device have otg support after the root???
Click to expand...
Click to collapse
if the kernel supports OTG,there is a way HERE
But I don't know if the kernel supports OTG
If u have a otg cable,
U can root and try this
don't fear to root your device
because I have posted a untouched stock recovery here....
So don't worry u are safe...
Im glad, I found this post! Please help me with CWM for Q412. Can I use the recovery posted here? Or can I use the Scatter file to grab recovery from the phone?
Thanks!
glasseffects said:
Im glad, I found this post! Please help me with CWM for Q412. Can I use the recovery posted here? Or can I use the Scatter file to grab recovery from the phone?
Thanks!
Click to expand...
Click to collapse
You should not use this scatter and recovery
1.Create scatter based on my scatter....
Connect your phone with pc Your device
Make sure you have configured adb (Android Debugging Bridge)
Now use following command
adb shell cat /proc/partinfo
Click to expand...
Click to collapse
you will get "start address" and "size" of every partitions
compare these results with my scatter and replace the values.
Try to grab recovery using MTK Droid Tools or use 2nd step
2.Unpack my "recovery.img" using "Carlive image kitchen"
now repack it with your own kernel
flash it using sp-flash tool
aravazhi_mdr,
Thank you for the little tutorial! I followed it but ended up with the same error whereby SP Flash Tool tells me that the flashing has failed, perhaps I missed something crucial. So I tried to revert to the stock firmware again but even that ends with error. But this isn't the real problem. This phone has a non-removable battery. Once something has been flashed, the phone remains in some mode and can not be rebooted. I wish the battery could be removed. I have to wait for the battery to drain untill the phone becomes operable.
This is the error I recieve if I flash anything with SPFT in any mode but 'Format All + Download':
{
"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"
}
Please suggest a solution.
PS: I have stock firmware which inclides recovery.img and boot.img. If I flash this firmware, the phone boots fine, but if I unpack and repack any of these with CarlivImageKitchen, results in the same error as above!
glasseffects said:
aravazhi_mdr,
Thank you for the little tutorial! I followed it but ended up with the same error whereby SP Flash Tool tells me that the flashing has failed, perhaps I missed something crucial. So I tried to revert to the stock firmware again but even that ends with error. But this isn't the real problem. This phone has a non-removable battery. Once something has been flashed, the phone remains in some mode and can not be rebooted. I wish the battery could be removed. I have to wait for the battery to drain untill the phone becomes operable.
This is the error I recieve if I flash anything with SPFT in any mode but 'Format All + Download':
Please suggest a solution.
Click to expand...
Click to collapse
while flashing maintain your charge below 15%....
so you don't need to wait 4 long to drain battery
I think you are using an old version of SPFT.
Grab the new one from androidmtk.com
don't touch boot loader...
coz many people stuck here...
gud luck
next time attach log file...
unpacking with carliv image kitchen
use normal android unpack option
if u have error choose mtk unpack option
aravazhi_mdr said:
while flashing maintain your charge below 15%....
so you don't need to wait 4 long to drain battery
I think you are using an old version of SPFT.
Grab the new one from androidmtk.com
don't touch boot loader...
coz many people stuck here...
gud luck
next time attach log file...
Click to expand...
Click to collapse
Thanks aravazhi_mdr,
I downloaded the recent version of SPFT but consistently reporduced the same error . CarlivImageKitchen, on the other hand does not unpack the recovery citing that "it has been packed with an unknown compression menthod". While the same can be unpacked through the regular Android option. Repacking is possible but reproduces the same error upon flashing.
I have attached the log with this post. Error 4008 suggests that SPFT wasn't able to download the flash file but I can't say beyond that.
For now, I have been flashing with almost no battery backup so I won't have to wait. Do you think this is also a design flaw when they overlooked the obvious?
Please guide me further.
Thanks.
OK.
You don't have problem with stock ROM.
But the repacked recovery failed to flash..
am I right?
Unpack your stock recovery (from stock ROM) and my recovery-CWM.IMG (link on 1st post) using regular android unpack.....
copy the following files from your stock recovery to recovery-cwm
1.recovery.img-base
2.recovery.img-board
3.recovery. img-cmdline
4.recovery.img-kernel
5.recovery.img-kernel_offset
6.recovery.img-pagesize
7.recovery.img-ramdisk_offset
8.recovery.img-ramdisk-compress
9.recovery.img-tags_offset
Now repack recovery-cwm using REGULAR ANDROID REPACK option and flash it....
Compare /proc/partinfo and your scatter from androidmtk.com
aravazhi_mdr
Glad, with your help the recovery now works, although I have to disconnect the phone before SPFT could give an error (it still does give the same 4008 error). I would be thankful if you could help me with the following two issues:
1. The recovery works but somehow it can't mount internal storage. I can flash zips like supersu.
2. The second issue relates to the Format + Download option in SPFT which I just came to know also wipes IMEI. So I'm without any network now . I tried the AT+ command method but it didn't work even if I deleted nvram. Elsewhere there's a tutorial about NV Tools but that requires me to have a file which isn't there in the Zip folder of the stock firmware.
Im trying to resolve these but I seek your help once again!
The command is "AT +" not "AT+"
unpack your stock recovery and goto ramdisk/etc/recovery.fstab
compare this with your modified recovery's recovery. fstab file......
this recovery.fstab file has details about where to Mount which block.....
AT + Command will work...
The command is "AT +" not "AT+"
AT +EGMR=1,7,”"
Click to expand...
Click to collapse
aravazhi_mdr,
Thank you for your continued support. I hope I'm not bothering you much here. As far as the progress is concerned. I tried to compare and replace certain parameters but the diversity of these two files has kept me thinking. So each time the results were the same, the internal SDCARD still remains inaccessible. I've attached the contents of these files here: Please take a look.
Q412 recovery.fstab
Code:
boot /boot emmc defaults defaults
/dev/block/mmcblk0p2 /cache ext4 defaults defaults
/dev/block/mmcblk0p3 /data ext4 defaults defaults
misc /misc emmc defaults defaults
recovery /recovery emmc defaults defaults
/dev/block/mmcblk0p4 /sdcard vfat defaults defaults
/dev/block/mmcblk0p6 /system ext4 defaults defaults
Q413 recovery.fstab
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/mmcblk0p3 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/nvdata /nvdata ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,autoformat
#please add cip or persist on project fstab
#/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 ro wait
/storage/sdcard0 auto vfat defaults voldmanaged=sdcard0:auto
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
/devices/platform/mt_usb auto vfat defaults voldmanaged=usbotg:auto
Please help me wich code requires editing. This would complete the task of complete!
On the other hand I went ahead with SN Writer tool and successfully restored the IMEI codes.
Thanks again for your help!
Goto /dev/block and know something about your blocks,which is your internal storage.........
however you can use adb commands to push flashable zips.......
Please also share for canvas xpress a99
Sent from my Moto G using Tapatalk
aravazhi_mdr said:
You should not use this scatter and recovery
1.Create scatter based on my scatter....
Connect your phone with pc Your device
Make sure you have configured adb (Android Debugging Bridge)
Now use following command
you will get "start address" and "size" of every partitions
compare these results with my scatter and replace the values.
Try to grab recovery using MTK Droid Tools or use 2nd step
2.Unpack my "recovery.img" using "Carlive image kitchen"
now repack it with your own kernel
flash it using sp-flash tool
Click to expand...
Click to collapse
Please create CWM recovery or any other recovery .img file for q412 users. pls provide us a simple link to download recovery file, so that we can flash it using sp tool or rashr, like u done for q413 users
pls do the needful,
thanks

[Resolved] Resize recovery partition on Lenovo K30W

I want to increase size of recovery partition on Lenovo K30W so I can flash larger recovery image created for Lenovo A6000. I have devised a way, but I would be grateful if someone could look it over and spot possible flaws.
Here is the current partition table.
Code:
Model: MMC Q8XSAB (sd/mmc)
Disk /dev/block/mmcblk0: 15634268160B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67108864B 134217727B 67108864B fat16 modem
2 134217728B 134742015B 524288B sbl1
3 134742016B 135266303B 524288B sbl1bak
4 135266304B 136314879B 1048576B aboot
5 136314880B 137363455B 1048576B abootbak
6 137363456B 137887743B 524288B rpm
7 137887744B 138412031B 524288B rpmbak
8 138412032B 138936319B 524288B tz
9 138936320B 139460607B 524288B tzbak
10 139460608B 139984895B 524288B hyp
11 139984896B 140509183B 524288B hypbak
12 140509184B 141557759B 1048576B pad
13 141557760B 143130623B 1572864B modemst1
14 143130624B 144703487B 1572864B modemst2
15 144703488B 145752063B 1048576B misc
16 145752064B 145753087B 1024B fsc
17 145753088B 145761279B 8192B ssd
18 145761280B 156247039B 10485760B splash
19 201326592B 201359359B 32768B DDR
20 201359360B 202932223B 1572864B fsg
21 202932224B 202948607B 16384B sec
22 202948608B 219725823B 16777216B boot
23 219725824B 1830338559B 1610612736B ext4 system
24 1830338560B 1863892991B 33554432B ext4 persist
25 1863892992B 1998110719B 134217728B ext4 cache
26 1998110720B 2014887935B 16777216B recovery
27 2014887936B 15634251263B 13619363328B ext4 userdata
Luckily, recovery and data partition are next to each other. Here is the procedure, please tell me if it is viable.
1. Boot into recovery
2. Create nandroid backup of data partition
3. Make sure that data partition is unmounted in recovery
4. Using parted, delete recovery and data partitions, and then recreate them with new sizes
5. Format data partition
6. Make sure that "use rm -rf instead of formatting" is enabled in recovery settings
7. Restore nandroid backup
8. Flash new recovery
9. Reboot
These are the commands I would use:
Code:
adb shell
parted /dev/block/mmcblk0
unit b
rm 27
rm 26
mkpart primary 1998110720 2031665151
mkpart primary 2031665152 15634251263
name 26 recovery
name 27 userdata
quit
mke2fs -t ext4 /dev/block/mmcblk0p27
As there were no replies, I took a risk and went ahead with resizing the partitions. The described procedure worked without problems.
Could you make a guide on how you did this exactly for noobs?
I understand that you posted the steps you used, but i'm not familiar with what you did.
Also, what rom are you using currently?
I got a rom working for this phone, It works well, but is not ideal.
https://forum.xda-developers.com/general/help/k3-note-question-k30w-t3531158
addict1337 said:
Could you make a guide on how you did this exactly for noobs?
I understand that you posted the steps you used, but i'm not familiar with what you did.
Also, what rom are you using currently?
I got a rom working for this phone, It works well, but is not ideal.
https://forum.xda-developers.com/general/help/k3-note-question-k30w-t3531158
Click to expand...
Click to collapse
Well, making an even more detailed guide will take some effort. I'll do it when I find the time.
I am using this ROM: https://forum.xda-developers.com/lenovo-a6000/development/rom-resurrectionremix-5-8-1-t3555184
It's great, but I do have problems with updating it. Hopefully it'll be resolved soon.
Here is a more detailed procedure. However, if you are not familiar with Linux command line and the Android partition layout, I strongly recommend that you stay away from this.
First, you need Android platform tools from here. Download for your platform (I am going to assume Windows) and extract to a folder of your choosing (for example C:\Android).
You also need parted utility, download from here. It's best to extract it to the same folder as Android platform tools.
Next, open Windows command prompt and go to the platform tools folder. The easiest way to do it is to open the folder in Windows Explorer, right click in the empty space while holding shift and choose "Open command window here". Reboot your device in recovery mode and connect it to the computer USB port.
While in recovery, make a backup of your data partition.
Copy the new recovery image to external SD if you have one, or else to internal memory. You can do it using Windows Explorer.
Copy parted utility to the device.
Code:
adb push parted /.
Next, enter device shell.
Code:
adb shell
Make parted executable.
Code:
chmod a+x parted
Start parted utility.
Code:
./parted /dev/block/mmcblk0
Be extremely careful from now on. Every parted command is executed immediately, so if you type something wrong, you could brick your device.
Change size unit to byte.
Code:
unit b
Print your current partition layout. If it's not the same as in my original post, abort now as you'll mess things up.
Code:
p
Remove recovery and data partitions.
Code:
rm 27
rm 26
Recreate partitions with new sizes (recovery is now 32MB instead of previous 16MB).
Code:
mkpart primary 1998110720 2031665151
mkpart primary 2031665152 15634251263
Give partitions the same names as before.
Code:
name 26 recovery
name 27 userdata
Exit parted utility.
Code:
quit
Format the data partition.
Code:
mke2fs -t ext4 /dev/block/mmcblk0p27
Make sure that "use rm -rf instead of formatting" is enabled in recovery settings. This may not be necessary, but I've seen it in some tutorial, and it can't hurt.
Restore data partition from backup.
Flash new recovery using current recovery (go to install and choose "install image").
Reboot and hope for the best.
Thank you very much
I will give it a try.
All worked well, however I am never able to boot into recovery from my phone itself (before i attempted this, and after).
I always need to use my pc/usb to boot into recovery via a batch file.
Even if I install recovery from the recovery I just booted.
Getting into recovery is holding volume up and the power button right?
I installed the software you mentioned, however it is stuck at the bootscreen
addict1337 said:
All worked well, however I am never able to boot into recovery from my phone itself (before i attempted this, and after).
I always need to use my pc/usb to boot into recovery via a batch file.
Even if I install recovery from the recovery I just booted.
Getting into recovery is holding volume up and the power button right?
I installed the software you mentioned, however it is stuck at the bootscreen
Click to expand...
Click to collapse
To get into recovery, you need to keep BOTH up and down volume keys, and then power on. After a few seconds, you can release volume keys.
As far as the ROM is concerned, make sure you wipe data and cache before installing it. That's all I can think of.
CrazyNik said:
To get into recovery, you need to keep BOTH up and down volume keys, and then power on. After a few seconds, you can release volume keys.
As far as the ROM is concerned, make sure you wipe data and cache before installing it. That's all I can think of.
Click to expand...
Click to collapse
Thanks.
I managed to install a CWM recovery for A6000, witch is working fine now (32MB)
I had problems with GPS on my Cyanongenmod Rom modified for K30-W, but after installing gapps all is working fine now.
Thank you for your help!
I hate to bother you any more, but I would like to use the same rom you are using, however I can't get it to flash.
I got TWRP 2.8.6.1 working (any other version I tried will not work)
I wipe DATA DALVIK and CACHE
When I try to install: 20170403-a6000-Official it gets stuck on:
Patching system image unconditionally....
I am able to flash Cyanogenmod, but that's a much older version.
If you could help me with what I am doing wrong, that would be much appriciated.
There are not many people running this phone.
I am also interested in the recovery you are using.
addict1337 said:
I hate to bother you any more, but I would like to use the same rom you are using, however I can't get it to flash.
I got TWRP 2.8.6.1 working (any other version I tried will not work)
I wipe DATA DALVIK and CACHE
When I try to install: 20170403-a6000-Official it gets stuck on:
Patching system image unconditionally....
I am able to flash Cyanogenmod, but that's a much older version.
If you could help me with what I am doing wrong, that would be much appriciated.
There are not many people running this phone.
I am also interested in the recovery you are using.
Click to expand...
Click to collapse
You must use TWRP 3.1.0, but even with it, RR 20170403 will not install on K30W firmware, I don't know why. I managed to install it by flashing A6000 firmware first. I will post the tutorial on RR thread when I find the time.
addict1337 said:
I hate to bother you any more, but I would like to use the same rom you are using, however I can't get it to flash.
I got TWRP 2.8.6.1 working (any other version I tried will not work)
I wipe DATA DALVIK and CACHE
When I try to install: 20170403-a6000-Official it gets stuck on:
Patching system image unconditionally....
I am able to flash Cyanogenmod, but that's a much older version.
If you could help me with what I am doing wrong, that would be much appriciated.
There are not many people running this phone.
I am also interested in the recovery you are using.
Click to expand...
Click to collapse
I've posted the tutorial here.
CrazyNik said:
I've posted the tutorial here.
Click to expand...
Click to collapse
Awesome, I was waiting for it
Thank you very much.

J7 PRIME (sm-g610y) EFS FILE

I JUST CREATED THIS ACCOUNT IN XDA FOR HELP!
My Phone IMEI, BASEBAND, SN has Unknown value in settings after random reboot and I think it random Reboot because of Full Storage. LINK > SCREENSHOT LINK OR SEE ATTACH FILE
so Does anyone have J7PRIME (SMG610Y) EFS Backup File ?
MY PHONE:::::::::::::::::::::::::::::::::::::::::::
-J7 PRIME - (SM-G610Y)
-CUSTOM ROM (RESSURECTION REMIX LATEST)
-MAGISK ROOTED
-CUSTOM RECOVERY (TWRP)
MY PHONE:::::::::::::::::::::::::::::::::::::::::::
PLEASE UPLOAD AND SEND LINK TO ME FOR THOSE WHO HAVE THE FILE ❤
What I Tried::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
FLASH STOCK ROM 4FILES USING ODIN (DOES_NOT_RESTORE_EFS)
FLASH STOCK ROM 4FILES USING SAMSUNG TOOL PRO CRACK (DOES_NOT_RESTORE_EFS)
FORMAT & MOUNT EFS USING
Code:
adb shell
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
(MAKES IMEI AND SN e.g.000000000000000)
WHOLE DAY OF RESEARCH OF J7PRIME (SM-G610Y) EFS FILE FOR 3 DAYS
AND MORE(ICANTREMEMBER).
What I Tried::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
IF I FIX MY PHONE I WILL REPLAY TO THIS THREAD FOR PROCEDURE
edit:
DATE_UPLOADED: February 14, 2021 12:50PM
J7 PRIME_0914 said:
I JUST CREATED THIS ACCOUNT IN XDA FOR HELP!
My Phone IMEI, BASEBAND, SN has Unknown value in settings after random reboot and I think it random Reboot because of Full Storage. LINK > SCREENSHOT LINK OR SEE ATTACH FILE
so Does anyone have J7PRIME (SMG610Y) EFS Backup File ?
MY PHONE:::::::::::::::::::::::::::::::::::::::::::
-J7 PRIME - (SM-G610Y)
-CUSTOM ROM (RESSURECTION REMIX LATEST)
-MAGISK ROOTED
-CUSTOM RECOVERY (TWRP)
MY PHONE:::::::::::::::::::::::::::::::::::::::::::
PLEASE UPLOAD AND SEND LINK TO ME FOR THOSE WHO HAVE THE FILE ❤
What I Tried::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
FLASH STOCK ROM 4FILES USING ODIN (DOES_NOT_RESTORE_EFS)
FLASH STOCK ROM 4FILES USING SAMSUNG TOOL PRO CRACK (DOES_NOT_RESTORE_EFS)
FORMAT & MOUNT EFS USING
Code:
adb shell
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
(MAKES IMEI AND SN e.g.000000000000000)
WHOLE DAY OF RESEARCH OF J7PRIME (SM-G610Y) EFS FILE FOR 3 DAYS
AND MORE(ICANTREMEMBER).
What I Tried::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
IF I FIX MY PHONE I WILL REPLAY TO THIS THREAD FOR PROCEDURE
edit:
DATE_UPLOADED: February 14, 2021 12:50PM
Click to expand...
Click to collapse
Without a backup it's hard to restore your efs/imei.
Have s look at this guide:
[GUIDE] Recover phone from a formated /efs partition
I'm just writting this because i've recently had this problem. I managed to sort it out by my own but didn't really find it written anywhere, just bits and pieces scavenged from so many pages that might point to a solution (granted, part of my...
forum.xda-developers.com
If you use Repartition Tool then revert it back to its original (pls find its thread) before flashing its stock firmware (you may use other country firmware). I restore my own when flashing stock rom from samfirm (pls. flash updated firmwares using odin).
After 4Months of no mobile data I Successfully legit Restore my EFS Files/SerialNumber/Baseband.
So Here's the step it's very very simple
1). Download Custom ROM name Arrow OS.
Link https://sourceforge.net/projects/ar...x/GSI/27_Jan_2020/system_arm64_a.zip/download
2). Download Project Treblue.
Link https://forum.xda-developers.com/t/treble-arm64-vendor-project-treblue-for-g610x.4098877/
3). Download CreateVendor.zip.
Link https://drive.google.com/drive/mobile/folders/1aX0WBy9juWZpIlFWTw9L6P_PR46JCj0H?usp=sharing
4). Download UniversalRepatitioner
Link https://forum.xda-developers.com/t/...epartition-script-for-vendor-support.4143541/
After you download all the files above follow this steps
1). Reboot to Recovery
2). Flash CreateVendor_2.0.zip
3). Wipe All Include/Exclude Vendor and Internal Storage
Note before step 4 : Flash Universal Repartitioner if System Partition is less than 4GB see recovery log for the size
Edit: BTW wipe all partition as universalrepartitioner sad in the log.
4). Flash Arrow OS 10 that you've downloaded earlier after flashing Rom
5). Flash Project Treblue
Optional: Resize System Partition in Wipe>AdvanceWipe>RepairOrChangeFS
6). Reboot
Edit: I'm the one who created this thread but different account!
And As I promised I reply to this if I fix or restore the problem.

Categories

Resources