Related
How to Make a full backup ROM for MT6592,MT6589, MT6582, MT6577, MT6575, MT6572, MT6516 phones. This is basically for all MTK phones from MediaTek.
This is also a great way to share your firmware with someone who may need the stock ROM for their bricked phone. Or if you're the bricked one, you can direct someone with the same phone as you to this tutorial so they can prepare their ROM for you.
Important: Make sure to accept any SuperSU or SuperUser permission requests your phone may ask for while you're doing these steps. Any firewall requests your PC may have installed, also allow.
The tutorial will show you how to:
- make a full backup of your ROM (firmware)
- make the ROM firmware ready for SP Flash Tools
Click to expand...
Click to collapse
What you need:
- A rooted MTK phone
- BusyBox (can be downloaded from Google Play)
- MTK Droid Tools v2.5.0 Download Here
- ADB drivers Download Here or Here(so your computer can communicate with your rooted phone)
Click to expand...
Click to collapse
A) Prepare your phone and get the utilities we'll need
1. Enable debugging mode on your phone. From your homescreen, tap the Menu button > Settings > Development. Tap 'Debug Mode' and make sure it's checked.
2. Install BusyBox. Go to Google Play and search 'BusyBox' and install.
3. Install PDANet ADB Drivers. Download from here. Run the download and follow the instructions. A USB cable is required to connect your phone to your PC. After installing the drivers, keep your phone connected.
4. Download MTK Droid Tools 2.5.0 and extract to a known location on your PC.
Click to expand...
Click to collapse
B) Open ADB prompt to begin communication with the phone
1. Go into the extracted MTK Droid Tools folder from step 4 and right-click on 'MTKdroidTools.exe'. Select 'Run as administrator'.
2. Wait several seconds while MTK Droid Tools communicates with your phone. You'll eventually see the main screen come up with all of your phone's information. Look in the bottom left hand corner of the main window, you should see a green square. If it's yellow, you can try to click the 'root' button in MTK Droid Tools to get temporary root shell. If this doesn't work, and you've already got CWM, alternatively you can boot into CWM and then the little square should be green.
Click to expand...
Click to collapse
C) Read back the ROM with MTK Droid Tools
1. Go back to the main menu of MTK Droid Tools and select the 'Root, Backup, Recovery' tab.
2. Click the 'Backup' button. You will see MTK Droid Tools start to read all the data from your phone Smile. This can take awhile. So let it do it's thing. Have a coffee, whatever.
3. After it's finished reading back the ROM, another window will pop up asking you if you'd like to compress the image. Better to select 'Yes'. This will save space and make it into one tight package. MTK Droid Tools will then pack it up into a zip and then let you know it's finished.
İmage
{
"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"
}
Click to expand...
Click to collapse
D) Prepare the data from MTK Droid Tools for SP Flash Tools
1. In the MTK Droid Tools 'root, backup, recovery', you will a button that says 'To prepare blocks for Flash Tool'. Click it.
2. A new explorer window will open directly to the backups folder that MTK Droid Tools made. Select your phone's backup folder. It will look something like *your phone*-backup-YYMMDD. Open this folder.
3. Inside your phone's backup folder, you will see a file called 'files.md5'. Select this and the process will start Smile
4. This will take a while. Go have another coffee or shot of whiskey, smoke a joint. Whatever your like.
5. After it's finished, open the folder where you extracted MTK Droid Tools. There you will see a folder called 'backup'. Open this folder, then open the folder for your phone (*your phone*-backup-YYMMDD). There will be a folder called '!Files_to_FlashTool'. That's the folder to use for flashing with SP Flash Tools! Smile
Click to expand...
Click to collapse
This Guide can be Found on Chianaforums, but i poste specialy becuse of many Q700/Q700i users still unkown from this
Credit:-
@yuweng , @rua1 still don't know who is the developer of this app, if anything missing PM me :highfive:
Click to expand...
Click to collapse
Please rate the thread 5stars For support And Press thanks Too
Rather not thank you for a guide that's been done a hundred times already.
Sent from my A1-810 using XDA Premium HD app
KieranFoot said:
Rather not thank you for a guide that's been done a hundred times already.
Sent from my A1-810 using XDA Premium HD app
Click to expand...
Click to collapse
i know here and there lots of,,
but i think you woun't read the the last few lines
Ok, I'm going to avoid flaming, but shouldn't you have just posted a link to the original with a statement saying you had found it helpfull...
I'm all for information dispersal, but just copying annoys me.
Also, on a rooted device, I wouldnt use MTKDroidTools/SPFlashTool, I'd just use dumchar, dd and gzip to do it on the command line.
Also, it's bad advice to use the root function of MTKDroidTools as it will soft brick S-On devices.
Sent from my A1-810 using XDA Premium HD app
KieranFoot said:
Ok, I'm going to avoid flaming, but shouldn't you have just posted a link to the original with a statement saying you had found it helpfull...
I'm all for information dispersal, but just copying annoys me.
Also, on a rooted device, I wouldnt use MTKDroidTools/SPFlashTool, I'd just use dumchar, dd and gzip to do it on the command line.
Also, it's bad advice to use the root function of MTKDroidTools as it will soft brick S-On devices.
Sent from my A1-810 using XDA Premium HD app
Click to expand...
Click to collapse
i don't have any regret that what i am doing ,, if you don't think its helpful or coped then use the Report button and END this conversion
Here is how to backup your device for those more interested in how it works.
Now, let me say before we begin that this won't be as simple as using MTKDroidTools to create the backup, but as we will read and compress as we go using a gzip stream, it should be faster.
Before the backup can be made you need to find out a bit of information about your device, you will need to find the partition table layout from either dumchar_info or the scatter file distributed inside android update/rom packages.
Here is my dumchar_info (/proc/dumchar_info) from my Acer Iconia A1-810 (MTK6589i) device.
Code:
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0
recovery 0x0000000000a00000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000003180000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003780000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003800000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003b00000 2 /dev/block/mmcblk0
android 0x0000000040000000 0x0000000004500000 2 /dev/block/mmcblk0p5
cache 0x000000002bc00000 0x0000000044500000 2 /dev/block/mmcblk0p6
usrdata 0x000000033a220000 0x0000000070100000 2 /dev/block/mmcblk0p7
bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0
As you can see it gives you the block device used for the partition and the size and start of the position on that device.
Sent from my A1-810 using XDA Premium HD app
KieranFoot said:
Here is how to backup your device for those more interested in how it works.
Now, let me say before we begin that this won't be as simple as using MTKDroidTools to create the backup, but as we will read and compress as we go using a gzip stream, it should be faster.
Before the backup can be made you need to find out a bit of information about your device, you will need to find the partition table layout from either dumchar_info or the scatter file distributed inside android update/rom packages.
Here is my dumchar_info (/proc/dumchar_info) from my Acer Iconia A1-810 (MTK6589i) device.
Code:
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0
recovery 0x0000000000a00000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000003180000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003780000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003800000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003b00000 2 /dev/block/mmcblk0
android 0x0000000040000000 0x0000000004500000 2 /dev/block/mmcblk0p5
cache 0x000000002bc00000 0x0000000044500000 2 /dev/block/mmcblk0p6
usrdata 0x000000033a220000 0x0000000070100000 2 /dev/block/mmcblk0p7
bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0
As you can see it gives you the block device used for the partition and the size and start of the position on that device.
Sent from my A1-810 using XDA Premium HD app
Click to expand...
Click to collapse
dude.. Why to follow an odd and complicated backup method like yours when an easy tool like mtkdroidtool is available which can easily backup whole firmware and it is tested by several users which means it is reliable tool.
KieranFoot said:
Here is how to backup your device for those more interested in how it works.
Now, let me say before we begin that this won't be as simple as using MTKDroidTools to create the backup, but as we will read and compress as we go using a gzip stream, it should be faster.
Before the backup can be made you need to find out a bit of information about your device, you will need to find the partition table layout from either dumchar_info or the scatter file distributed inside android update/rom packages.
Here is my dumchar_info (/proc/dumchar_info) from my Acer Iconia A1-810 (MTK6589i) device.
Code:
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0
recovery 0x0000000000a00000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000003180000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003780000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003800000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003b00000 2 /dev/block/mmcblk0
android 0x0000000040000000 0x0000000004500000 2 /dev/block/mmcblk0p5
cache 0x000000002bc00000 0x0000000044500000 2 /dev/block/mmcblk0p6
usrdata 0x000000033a220000 0x0000000070100000 2 /dev/block/mmcblk0p7
bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0
As you can see it gives you the block device used for the partition and the size and start of the position on that device.
Sent from my A1-810 using XDA Premium HD app
Click to expand...
Click to collapse
Do you have a complete tutorial on how to do this? plus commands to restore? This would be great for us Linux users, I have two of these phones coming in from china and have zero desire to use windows to back up and restore a android device.
I think I got it figured out, wont know for sure until I get my phones to test.
Anyway basically I just
cat /proc/dumchar_info
this gives me partition info, from there I dd partition contents to sdcard, example below is to pull your recovery.img from the info you posted.
to pull eg backup
dd if=/dev/block/mmcblk0 of=/sdcard/recovery.img bs=4096 count=2560 skip=10112
to restore
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0 bs=4096 seek=10112
vampirefo said:
Do you have a complete tutorial on how to do this? plus commands to restore? This would be great for us Linux users, I have two of these phones coming in from china and have zero desire to use windows to back up and restore a android device.
I think I got it figured out, wont know for sure until I get my phones to test.
Anyway basically I just
cat /proc/dumchar_info
this gives me partition info, from there I dd partition contents to sdcard, example below is to pull your recovery.img from the info you posted.
to pull eg backup
dd if=/dev/block/mmcblk0 of=/sdcard/recovery.img bs=4096 count=2560 skip=10112
to restore
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0 bs=4096 seek=10112
Click to expand...
Click to collapse
Yup, that's right
hello, i tried this with my MT6572 Device [Firefly S120 - Rebranded Cubot C11] i followed exactly as said, well not the coffee ones
and here is my log, notice the bolded and underlined letters, i need help thanks in advance
Code:
In system already available: Android Debug Bridge version 1.0.31
--->>> Connect to device <<<---
--- The preservation folder on the computer: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\
--- In phone files will remain in the folder: /storage/sdcard0/clockworkmod/backup/140520-075724/
--- scatter is write to the file:
C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\MT6572_Android_scatter.txt
--- We keep blocks:
- preloader_and_dsp
- MBR
- EBR1
- nodl_pro_info
- nvram.bin
- userdata_nvram_only.tar
- nodl_protect_f.ext4.img
- nodl_protect_f.ext4.tar
- nodl_protect_s.ext4.img
- nodl_protect_s.ext4.tar
- nodl_seccfg
- lk.bin
- boot.img
- recovery.img
- secro.img
- nodl_misc
- logo.bin
- nodl_expdb
- system.ext4.img
[U][B] - system.ext4.tar - ERROR - tar: write error: No space left on device[/B][/U]
--- We keep folders contents copying on PC
- /data/nvram
- /system
--- We pack everything kept in archive: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724.zip
[U][B] --- task end with ERROR ---[/B][/U]
--- Check and copying of files in the folder: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\!Files_to_FlashTool\
-- preloader_and_dsp: md5 OK; ... it is copied ... cut OK
-- MBR: md5 OK; ... it is copied
-- EBR1: md5 OK; ... it is copied
-- nodl_pro_info: md5 OK;
-- nvram.bin: md5 OK;
-- userdata_nvram_only.tar: md5 OK;
-- nodl_protect_f.ext4.img: md5 OK;
-- nodl_protect_f.ext4.tar: md5 OK;
-- nodl_protect_s.ext4.img: md5 OK;
-- nodl_protect_s.ext4.tar: md5 OK;
-- nodl_seccfg: md5 OK;
-- lk.bin: md5 OK; ... it is copied
-- boot.img: md5 OK; ... it is copied
-- recovery.img: md5 OK; ... it is copied
-- secro.img: md5 OK; ... it is copied
-- nodl_misc: md5 OK;
-- logo.bin: md5 OK; ... it is copied
-- nodl_expdb: md5 OK;
-- system.ext4.img: md5 OK; ... it is copied
--- copying is complete ---
--->>> Connect to device <<<---
xlSKYFiRElx said:
hello, i tried this with my MT6572 Device [Firefly S120 - Rebranded Cubot C11] i followed exactly as said, well not the coffee ones
and here is my log, notice the bolded and underlined letters, i need help thanks in advance
Code:
In system already available: Android Debug Bridge version 1.0.31
--->>> Connect to device <<<---
--- The preservation folder on the computer: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\
--- In phone files will remain in the folder: /storage/sdcard0/clockworkmod/backup/140520-075724/
--- scatter is write to the file:
C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\MT6572_Android_scatter.txt
--- We keep blocks:
- preloader_and_dsp
- MBR
- EBR1
- nodl_pro_info
- nvram.bin
- userdata_nvram_only.tar
- nodl_protect_f.ext4.img
- nodl_protect_f.ext4.tar
- nodl_protect_s.ext4.img
- nodl_protect_s.ext4.tar
- nodl_seccfg
- lk.bin
- boot.img
- recovery.img
- secro.img
- nodl_misc
- logo.bin
- nodl_expdb
- system.ext4.img
[U][B] - system.ext4.tar - ERROR - tar: write error: No space left on device[/B][/U]
--- We keep folders contents copying on PC
- /data/nvram
- /system
--- We pack everything kept in archive: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724.zip
[U][B] --- task end with ERROR ---[/B][/U]
--- Check and copying of files in the folder: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\!Files_to_FlashTool\
-- preloader_and_dsp: md5 OK; ... it is copied ... cut OK
-- MBR: md5 OK; ... it is copied
-- EBR1: md5 OK; ... it is copied
-- nodl_pro_info: md5 OK;
-- nvram.bin: md5 OK;
-- userdata_nvram_only.tar: md5 OK;
-- nodl_protect_f.ext4.img: md5 OK;
-- nodl_protect_f.ext4.tar: md5 OK;
-- nodl_protect_s.ext4.img: md5 OK;
-- nodl_protect_s.ext4.tar: md5 OK;
-- nodl_seccfg: md5 OK;
-- lk.bin: md5 OK; ... it is copied
-- boot.img: md5 OK; ... it is copied
-- recovery.img: md5 OK; ... it is copied
-- secro.img: md5 OK; ... it is copied
-- nodl_misc: md5 OK;
-- logo.bin: md5 OK; ... it is copied
-- nodl_expdb: md5 OK;
-- system.ext4.img: md5 OK; ... it is copied
--- copying is complete ---
--->>> Connect to device <<<---
Click to expand...
Click to collapse
i think in your case you should use latest mtk tools as mtk6572 is new
rajit said:
i think in your case you should use latest mtk tools as mtk6572 is new
Click to expand...
Click to collapse
thanks sir, but i already fixed that. my problem now is, mtk droid tools did not generate a backup image of ANDROID, USRDATA, and CACHE .. which is all needed in SPFT .. how can i fix it ? please ? thanks
xlSKYFiRElx said:
thanks sir, but i already fixed that. my problem now is, mtk droid tools did not generate a backup image of ANDROID, USRDATA, and CACHE .. which is all needed in SPFT .. how can i fix it ? please ? thanks
Click to expand...
Click to collapse
I hink you did not read ... mtk6572 has different base.. so the old mtkdroid tools cant generate backup as i am told that the path are diff. so if you are not using latest one no one could help you out
rajit said:
I hink you did not read ... mtk6572 has different base.. so the old mtkdroid tools cant generate backup as i am told that the path are diff. so if you are not using latest one no one could help you out
Click to expand...
Click to collapse
well, i tried the latest version sir. and even dared to test with the old versions too just to be sure lol .. still, no usrdata, android, and cache backups generated
xlSKYFiRElx said:
hello, i tried this with my MT6572 Device [Firefly S120 - Rebranded Cubot C11] i followed exactly as said, well not the coffee ones
and here is my log, notice the bolded and underlined letters, i need help thanks in advance
Code:
In system already available: Android Debug Bridge version 1.0.31
--->>> Connect to device <<<---
--- The preservation folder on the computer: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\
--- In phone files will remain in the folder: /storage/sdcard0/clockworkmod/backup/140520-075724/
--- scatter is write to the file:
C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\MT6572_Android_scatter.txt
.........
- nodl_expdb
- system.ext4.img
[U][B] - system.ext4.tar - ERROR - tar: write error: No space left on device[/B][/U]
--- We keep folders contents copying on PC
- /data/nvram
- /system
--- We pack everything kept in archive: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724.zip
[U][B] --- task end with ERROR ---[/B][/U]
--- Check and copying of files in the folder: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\!Files_to_FlashTool\
.................
--->>> Connect to device <<<---
Click to expand...
Click to collapse
I am not an expert but did you check the available free space on C: partition of your PC? It seems to me that "system.ext4.tar - ERROR - tar: write error: No space left on device" it referring to such an issue. This backup operations can require quite a space sometimes.
How Much time Does it Usually takes !
Hey Guyz i have starting backing up my Mtk Device And it took for abt 10 mins and yet its not finished ?
futurebreeze2014 said:
I am not an expert but did you check the available free space on C: partition of your PC? It seems to me that "system.ext4.tar - ERROR - tar: write error: No space left on device" it referring to such an issue. This backup operations can require quite a space sometimes.
Click to expand...
Click to collapse
... Also check your internal SD for free space as some of the backups can end up in cwm folder.
Sent from my NOA H42 using Tapatalk
---------- Post added at 07:13 PM ---------- Previous post was at 07:12 PM ----------
Vicky khan said:
Hey Guyz i have starting backing up my Mtk Device And it took for abt 10 mins and yet its not finished ?
Click to expand...
Click to collapse
It can last up to an hour depending of PC, used data and system space, etc.
xlSKYFiRElx said:
well, i tried the latest version sir. and even dared to test with the old versions too just to be sure lol .. still, no usrdata, android, and cache backups generated
Click to expand...
Click to collapse
I backup apps, userdata and cache with Titanium Backup. After a nandroid restore (e.g., CWM) Titanium Backup does the rest. Hope this helps.
Btw, Looking forward to your Firefly S120 (aka Cubot C11) custom ROMs
Hello,
This way doesn't work.
It needs to backup every data on the phone from root !
This way backup only the system folder... Then, every apps data are not saved.
EDIT: 2
Root Color OS by flashing the zip using TWRP Recovery ...
http://d-h.st/zJ8
===========
If the ROM Zip shows errors during flash use the following steps...
Open the color os rom zip file with 7zip and just extract the file
META-INF/com/google/android/updater-script
then edit it with notepad ++ ,
Remove the 1st line .....
assert(getprop("ro.product.device") == "A0001" getprop("ro.build.product") == "A0001");
or
Edit the 1st line as ...
assert(getprop("ro.product.device") == "A0001" || getprop("ro.product.device") == "bacon" || getprop("ro.build.product") == "bacon" || getprop("ro.build.product") == "A0001");
Then put back the edited file in the opened ROM Zip file (by 7zip)
Save.
Then try flashing the zip from TWRP again,
===========
EDIT 1:
Official Download Color OS Link for A Plus Phone
===========
Use Chrome / Google Translator
http://bbs.coloros.com/forum.php?mod=phones&code=rom&pid=34
===========
{
"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 use Google translate to see this page...
I found this on oneplusbbs.com
http://www.oneplusbbs.com/forum.php?...2&fromuid=3497
All versions of Color OS can be found here...
Latest Version is : 2.0.18
Here is the translated Web Page ...
======================================
ColorOS 1.2 Update 14/7/1
http://pan.baidu.com/s/1hqzeMUg
ColorOS 1.2 Update 14/7/7
OTA incremental upgrade package
http://pan.baidu.com/s/1jG9Q39W
the full amount of the full package
http://pan.baidu.com/s/1c0pJRBM
=====
ColorOS 2.0 Beta 2014/6/13
http://pan.baidu.com/s/1mgskWje
ColorOS 2.0.1 Beta 2014/6/20
upgrade by OTA the amount of the package
http://pan.baidu.com/s/1o6CzOCE
full amount complete package
http://pan.baidu.com/s/1bnxniG3
ColorOS 2.0.2 Beta 2014/6/20
OTA incremental upgrade package
http: // pan.baidu.com/s/1pJG1C9P
full amount of the full package
http://pan.baidu.com/s/1i3mRDnJ
ColorOS 2.0.3 Beta 2014/7/4
OTA incremental upgrade package
http://pan.baidu.com/s/1dDeS3S1
full amount complete package
http://pan.baidu.com/s/1sjFbO8P
ColorOS 2.0.4 Beta 2014/7/11
OTA incremental upgrade package
http://pan.baidu.com/s/14HmyE
full amount complete package
http://pan.baidu.com/s/1pJNT33H
ColorOS 2.0.5 Beta 2014/7/19
OTA incremental upgrade package
http://pan.baidu.com/s/1mggGx5Y
full amount complete package
http: // pan. baidu.com/s/1sjlpTSx
Color OS 2.0.6_beta 2014/7/25
OTA incremental upgrade package:
http://pan.baidu.com/s/1gdDuOsr
full amount complete package:
http://pan.baidu.com/s/1pJsLHz1
Color OS 2.0.7_beta 2014/8/1
http://pan.baidu.com/s/1qWkCsgO
Color OS 2.0.7_beta 2014/8/1
OTA incremental upgrade package:
http://pan.baidu.com/s/1hqEEPfQ
full amount complete package:
http://pan.baidu.com/s/1s6vuA
Color OS 2.0.8_beta 2014/8/8
full amount complete package:
http://pan.baidu.com/s/1917xc
Mirror
Full Rom A0001ROM_12_OTA_009_all_R0010.zip
MD5: C13BC7F8B1DEDB765A1EF3A528C72B9A
SHA1: 2CC6899298B48A7753C8B06426C5EEFDBD4D82B8
http://pan.baidu.com/s/1ntDOMc5
incremental package A0001ROM_12_OTA_009_patch_R0010.zip
MD5: 9797E592BE573CA400E8DC1780F1B0AA
SHA1: 582143429E5825F6BDB7B9C54F71393146198D54
http://pan.baidu.com/s/1ntmK1Gd
Color OS 2.0.9_beta 2014/8/15
Full Rom A0001ROM_12_OTA_010_all_R0011_wipe.zip
MD5：A91FA3F3EB2492F33B66CB7975CA0560
http://pan.baidu.com/s/1mg5d6Da
Mirror:
Full ROM 2.0.9
Size: 728,920,488 bytes
Modified: August 15, 2014, 1:33:58
MD5: A91FA3F3EB2492F33B66CB7975CA0560
Link: http: //pan.baidu.com/s/1gdkUYEB
Incremental package
Size: 21,753,839 bytes
Modified: August 15, 2014, 1:33:59
MD5: CA91338650314CAFCBA7A5DD72F0821D
Link: http: //pan.baidu.com/s/1o6siqi2
Color OS 2.0.11 Beta
A0001 full - package
Size: 718263346 bytes
Revised time: August 29, 2014, 14:03:59
MD5: BB5CAAD598C8303712B8A28FB40B5162
Http://pan.baidu.com/s/1dDkZtlv
A0001 increment.
Size: 24767359 bytes
Revised time: August 29, 2014, 14:03:59
MD5: F6044E7A4D81AD2A5DD11D675A1BED65
Http://pan.baidu.com/s/1mg0ujPY
Oneplus Color OS 2.0.18 Beta 141024
A0001 full package
size: 715,286,783 bytes
modified: October 23, 2014, 18:29:29
MD5: 7C9177F6C4C8964E1B9949BF0F3707B1
link: http://pan.baidu.com/s/1mg3duB2
A0001 incremental package
size: 7018936 bytes
modified: October 23, 2014, 18:29:58
MD5: D5E23B65C1507E5A93FAA06290EB47C9
link: http://pan.baidu.com/s/1sj5AXT7
=====================================
Downloading now...
Questions:
-What version of Android is the latest 2.0.2?
-Is this for the 64GB?
-Is this a flashable zip for custom recoveries?
-Have you tried it? Anything to report from the process or rom itself?
synergeticink said:
Downloading now...
Questions:
-What version of Android is the latest 2.0.2?
-Is this for the 64GB?
-Is this a flashable zip for custom recoveries?
-Have you tried it? Anything to report from the process or rom itself?
Click to expand...
Click to collapse
Android 4.3
I tried on my 64 GB works fine.... before that I took partition backup by adb dd command ....
it replaces the following...
===================================
1) logo.bin --- boot logo will be RED
2) NON-HLOS.bin -- modem
3) static_nvbk.bin
4) boot.img
5) reserve4.img
6) emmc_appsboot.mbn -- bootloader
7) rpm.mbn
8) sbl1.mbn
9) tz.mbn
and system partition
The 2 partition images in RED are not present in the CM11S stock rom (cm-11.0-XNPH22R-bacon-signed-fastboot.zip) ...
====================================
Not replacing userdata partition... So I guess 64 Gb work fine..
Yes .. It is flashable from TWRP...I tried it...
Note:
If you need the partition backup dd script that I wrote... I can give you that..
You can use it from ADB Shell as root...
:good:
Partition Details of OnePlus One 64GB ...
========================================
lrwxrwxrwx root root 1970-02-05 13:00 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-02-05 13:00 DRIVER -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-02-05 13:00 LOGO -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-02-05 13:00 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-02-05 13:00 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-02-05 13:00 cache -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-02-05 13:00 dbi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-02-05 13:00 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-02-05 13:00 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-02-05 13:00 grow -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-02-05 13:00 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-02-05 13:00 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-02-05 13:00 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-02-05 13:00 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-02-05 13:00 oppodycnvbk -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-02-05 13:00 oppostanvbk -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-02-05 13:00 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-02-05 13:00 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-02-05 13:00 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-02-05 13:00 reserve1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-02-05 13:00 reserve2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-02-05 13:00 reserve3 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-02-05 13:00 reserve4 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-02-05 13:00 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-02-05 13:00 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-02-05 13:00 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-02-05 13:00 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-02-05 13:00 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-02-05 13:00 userdata -> /dev/block/mmcblk0p28
Click to expand...
Click to collapse
So its best to flash stock CM11S if I want to go back rather then restoring from NAND backup? If you can give me the partition backup dd script that would be awesome, thank you
synergeticink said:
So its best to flash stock CM11S if I want to go back rather then restoring from NAND backup? If you can give me the partition backup dd script that would be awesome, thank you
Click to expand...
Click to collapse
Here is my script ... Run from ADB Shell as root...
*** No need to take backup of system & userdata **** because it will either be in CM11S or NAND (take more space)
======================================================================================
HTML:
mkdir /sdcard/PARTITION_BKP
dd if=/dev/block/mmcblk0p4 of=/sdcard/PARTITION_BKP/DDR
dd if=/dev/block/mmcblk0p23 of=/sdcard/PARTITION_BKP/DRIVER
dd if=/dev/block/mmcblk0p22 of=/sdcard/PARTITION_BKP/LOGO
dd if=/dev/block/mmcblk0p5 of=/sdcard/PARTITION_BKP/aboot
dd if=/dev/block/mmcblk0p7 of=/sdcard/PARTITION_BKP/boot
dd if=/dev/block/mmcblk0p16 of=/sdcard/PARTITION_BKP/cache
dd if=/dev/block/mmcblk0p3 of=/sdcard/PARTITION_BKP/dbi
dd if=/dev/block/mmcblk0p19 of=/sdcard/PARTITION_BKP/fsc
dd if=/dev/block/mmcblk0p18 of=/sdcard/PARTITION_BKP/fsg
dd if=/dev/block/mmcblk0p29 of=/sdcard/PARTITION_BKP/grow
dd if=/dev/block/mmcblk0p21 of=/sdcard/PARTITION_BKP/misc
dd if=/dev/block/mmcblk0p1 of=/sdcard/PARTITION_BKP/modem
dd if=/dev/block/mmcblk0p10 of=/sdcard/PARTITION_BKP/modemst1
dd if=/dev/block/mmcblk0p11 of=/sdcard/PARTITION_BKP/modemst2
dd if=/dev/block/mmcblk0p12 of=/sdcard/PARTITION_BKP/oppodycnvbk
dd if=/dev/block/mmcblk0p13 of=/sdcard/PARTITION_BKP/oppostanvbk
dd if=/dev/block/mmcblk0p9 of=/sdcard/PARTITION_BKP/pad
dd if=/dev/block/mmcblk0p15 of=/sdcard/PARTITION_BKP/persist
dd if=/dev/block/mmcblk0p17 of=/sdcard/PARTITION_BKP/recovery
dd if=/dev/block/mmcblk0p24 of=/sdcard/PARTITION_BKP/reserve1
dd if=/dev/block/mmcblk0p25 of=/sdcard/PARTITION_BKP/reserve2
dd if=/dev/block/mmcblk0p26 of=/sdcard/PARTITION_BKP/reserve3
dd if=/dev/block/mmcblk0p27 of=/sdcard/PARTITION_BKP/reserve4
dd if=/dev/block/mmcblk0p6 of=/sdcard/PARTITION_BKP/rpm
dd if=/dev/block/mmcblk0p2 of=/sdcard/PARTITION_BKP/sbl1
dd if=/dev/block/mmcblk0p20 of=/sdcard/PARTITION_BKP/ssd
dd if=/dev/block/mmcblk0p8 of=/sdcard/PARTITION_BKP/tz
dd if=/dev/block/mmcblk0p14 of=/sdcard/PARTITION_BKP/system
dd if=/dev/block/mmcblk0p28 of=/sdcard/PARTITION_BKP/userdata
Note: I don't know purpose of each partition ..
Warning: Use at your own risk... etc .. etc...as we all know ..
:fingers-crossed:
Awesome, will try it out tomorrow and will report back. Off to bed, Thank you.
Mnt-XDA said:
Here is my script ... Run from ADB Shell as root...
*** No need to take backup of system & userdata **** because it will either be in CM11S or NAND (take more space)
======================================================================================
HTML:
mkdir /sdcard/PARTITION_BKP
dd if=/dev/block/mmcblk0p4 of=/sdcard/PARTITION_BKP/DDR
dd if=/dev/block/mmcblk0p23 of=/sdcard/PARTITION_BKP/DRIVER
dd if=/dev/block/mmcblk0p22 of=/sdcard/PARTITION_BKP/LOGO
dd if=/dev/block/mmcblk0p5 of=/sdcard/PARTITION_BKP/aboot
dd if=/dev/block/mmcblk0p7 of=/sdcard/PARTITION_BKP/boot
dd if=/dev/block/mmcblk0p16 of=/sdcard/PARTITION_BKP/cache
dd if=/dev/block/mmcblk0p3 of=/sdcard/PARTITION_BKP/dbi
dd if=/dev/block/mmcblk0p19 of=/sdcard/PARTITION_BKP/fsc
dd if=/dev/block/mmcblk0p18 of=/sdcard/PARTITION_BKP/fsg
dd if=/dev/block/mmcblk0p29 of=/sdcard/PARTITION_BKP/grow
dd if=/dev/block/mmcblk0p21 of=/sdcard/PARTITION_BKP/misc
dd if=/dev/block/mmcblk0p1 of=/sdcard/PARTITION_BKP/modem
dd if=/dev/block/mmcblk0p10 of=/sdcard/PARTITION_BKP/modemst1
dd if=/dev/block/mmcblk0p11 of=/sdcard/PARTITION_BKP/modemst2
dd if=/dev/block/mmcblk0p12 of=/sdcard/PARTITION_BKP/oppodycnvbk
dd if=/dev/block/mmcblk0p13 of=/sdcard/PARTITION_BKP/oppostanvbk
dd if=/dev/block/mmcblk0p9 of=/sdcard/PARTITION_BKP/pad
dd if=/dev/block/mmcblk0p15 of=/sdcard/PARTITION_BKP/persist
dd if=/dev/block/mmcblk0p17 of=/sdcard/PARTITION_BKP/recovery
dd if=/dev/block/mmcblk0p24 of=/sdcard/PARTITION_BKP/reserve1
dd if=/dev/block/mmcblk0p25 of=/sdcard/PARTITION_BKP/reserve2
dd if=/dev/block/mmcblk0p26 of=/sdcard/PARTITION_BKP/reserve3
dd if=/dev/block/mmcblk0p27 of=/sdcard/PARTITION_BKP/reserve4
dd if=/dev/block/mmcblk0p6 of=/sdcard/PARTITION_BKP/rpm
dd if=/dev/block/mmcblk0p2 of=/sdcard/PARTITION_BKP/sbl1
dd if=/dev/block/mmcblk0p20 of=/sdcard/PARTITION_BKP/ssd
dd if=/dev/block/mmcblk0p8 of=/sdcard/PARTITION_BKP/tz
dd if=/dev/block/mmcblk0p14 of=/sdcard/PARTITION_BKP/system
dd if=/dev/block/mmcblk0p28 of=/sdcard/PARTITION_BKP/userdata
Note: I don't know purpose of each partition ..
Warning: Use at your own risk... etc .. etc...as we all know ..
:fingers-crossed:
Click to expand...
Click to collapse
1st Post updated
Latest is 2.0.5 beta...
If I wanted to install this rom, how I do?? I make a backup of all partitions?? And to return to CM11S, I flash the stock rom and nothing more??
shadow25 said:
If I wanted to install this rom, how I do?? I make a backup of all partitions?? And to return to CM11S, I flash the stock rom and nothing more??
Click to expand...
Click to collapse
Color os zip is flashable from CWM or TWRP recovery .. nothing more
Mnt-XDA said:
Color os zip is flashable from CWM or TWRP recovery .. nothing more
Click to expand...
Click to collapse
And for these files that it replaces?? Especially the number 3 and 5
===================================
1) logo.bin --- boot logo will be RED
2) NON-HLOS.bin -- modem
3) static_nvbk.bin
4) boot.img
5) reserve4.img
6) emmc_appsboot.mbn -- bootloader
7) rpm.mbn
8) sbl1.mbn
9) tz.mbn
shadow25 said:
And for these files that it replaces?? Especially the number 3 and 5
===================================
1) logo.bin --- boot logo will be RED
2) NON-HLOS.bin -- modem
3) static_nvbk.bin
4) boot.img
5) reserve4.img
6) emmc_appsboot.mbn -- bootloader
7) rpm.mbn
8) sbl1.mbn
9) tz.mbn
Click to expand...
Click to collapse
Right... not files, replaces partitions.
3 & 5 are not in cm11s zip ...
So if you like to back to stock cm11s again ...3 & 5 will not.
Others can be restored.
OP Updated and Official Link added...
@Mnt-XDA, just one question... Did you try to just flash system and boot partition? Will it boot then or will something be unstable then?
Also, did any of you get the 2.06 version to root? I tried the latest SuperSU 2.02, but it didn't work... SU binary wasn't detected, but it was there...
dansou901 said:
Also, did any of you get the 2.06 version to root? I tried the latest SuperSU 2.02, but it didn't work... SU binary wasn't detected, but it was there...
Click to expand...
Click to collapse
Yes , I installed 2.0.6 and rooted also....
more to test....
May i help you for any issue ?
Mnt-XDA said:
Yes , I installed 2.0.6 and rooted also....
more to test....
May i help you for any issue ?
Click to expand...
Click to collapse
How did you root? I already wrote, was installing SuperSu latest and su binary wasn't detected. I must mention, though, that I modified the zip to only install boot and system partition. I removed all the other partitions from the zip and updater script, also I'm running the international version so I had to disable the check against the model (first line in updater script).
Sent from my One using XDA Premium 4 mobile app
dansou901 said:
How did you root? I already wrote, was installing SuperSu latest and su binary wasn't detected. I must mention, though, that I modified the zip to only install boot and system partition. I removed all the other partitions from the zip and updater script, also I'm running the international version so I had to disable the check against the model (first line in updater script).
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
try this from TWRP
http://d-h.st/zJ8
and let me know
Mnt-XDA said:
try this from TWRP
http://d-h.st/zJ8
and let me know
Click to expand...
Click to collapse
That zip won't install for me. Gives me an error. Will get you a log now...
dansou901 said:
That zip won't install for me. Gives me an error. Will get you a log now...
Click to expand...
Click to collapse
Whats the error ?
which rom and recovery are you in ?
Mnt-XDA said:
Whats the error ?
which rom and recovery are you in ?
Click to expand...
Click to collapse
I flashed latest ColorOS and have TWRP 2.7.1.1 installed. Error is just
E:Unable to open zip file.
Error flashing zip '/sdcard/Download/Find7_ROOT4.3_bbs.oppo.cn.zip'
Nothing more about that in recovery.log. I try now to repackage the zip and flash again, will report later...
1. how to root kitkat rom 4.4.2 on alcatel 6040d? tried almost all apps and tutorials but i failed to root.
2. how to install custom recovery? flashed the twrp recovery in the attachment but still i have the stock recovery.
3. tried to install cwm via mtk tools and sp flash tools but i always got factory_NONmodified_recovery.img as result. no modified recovery created.
--->>> Connect to device <<<---
--- The preservation folder on the computer: C:\Users\bryanjay420\Desktop\Alcatel\MtkDroidTools\backups\TCL-S950_140926_ForFlashtoolFromReadBack_141012-005842\
--- scatter is write to the file:
C:\Users\bryanjay420\Desktop\Alcatel\MtkDroidTools\backups\TCL-S950_140926_ForFlashtoolFromReadBack_141012-005842\MT6589_Android_scatter_emmc.txtcopying is complete
-- preloader.bin ...it is copied ... cut OK
-- MBR ...it is copied
-- EBR1 ...it is copied
-- pmt ...it is copied
- PMT tables found
- PMT tables OK, 23 blocks found
--- Kernel Block Map to PMT mismatch!
-------------------------------------------
BlockName Offset
-------------------------------------------
Kernel: __NODL_BMTPOOL 0x00000000FFFF00A8
PMT: Not present! ??????????
-------------------------------------------
--- scatter from PMTis write to the file:
C:\Users\bryanjay420\Desktop\Alcatel\MtkDroidTools\backups\TCL-S950_140926_ForFlashtoolFromReadBack_141012-005842\MT6589_Android_scatter_emmc_PMT.txt
- Use it if SP FlashTool errors of 8038 or 4050 occurs
-- pro_info ...it is copied
-- nvram.bin ...it is copied
-- protect_f ...it is copied
-- protect_s ...it is copied
-- seccfg ...it is copied
-- uboot.bin ...it is copied
-- boot.img ...it is copied
--- ERROR :No find KernelGZ
--- ERROR :No Split Boot Image
-- recovery.img ...it is copied
-- secro.img ...it is copied
-- misc ...it is copied
-- logo.bin ...it is copied
-- EBR2 ...it is copied
-- custpack2.img ...it is copied
-- mobile_info.img ...it is copied
-- expdb ...it is copied
-- system.img ...it is copied
--- task is complete ---
Click to expand...
Click to collapse
After upgrading from MIUIv4 to v6, I've discovered that the new version comes with a bootloader that
reflashes the recovery partition each time it's run with the stock recovery, which makes it impossible to use a custom recovery in order to install unsigned .zip patches,
doesn't support download mode, which makes it impossible to connect the phone to a computer as a block device and repartition it.
Since resolving this wasn't completely trivial (to me) and required a bit of research, I took some notes for future reference. I later decided to publish these notes, since someone might find them useful. Keep in mind that, while I do have technical background, I'm not intimately acquainted with the inner workings of Android and there was some trial and error involved. As a result, certain steps may be too heavy-handed or even unnecessary and I encourage comments on that.
Prerequisites
The guide presumes one has the adb, fastboot and parted binaries installed on an OS that enables access to connected block devices via the filesystem. For most users, that means a linux box.
Download mode
Booting into download mode appears to be disabled in MIUI6 v5.8.6. You will therefore need to boot into a custom recovery (see Booting into a custom recovery mode) and flash an alternative ROM (it would likely suffice to flash only certain partitions?):
Code:
$ adb push cm-11-20150802-NIGHTLY-aries.zip /storage/sdcard0
To boot into the download mode with an alternative ROM, consult [3] or run adb reboot dload against the phone in the system or in the recovery mode.
Repartitioning the internal flash memory
In my experience, the default size of the /system partition is insufficient to accommodate all the system applications along with the ever-growing Google Apps. The original inspiration came from [4]. To adjust the partition sizes, I used the parted command-line tool, since it comes with full support for GPT partitions and labels. Gparted used, but (as of v0.19.0-2) appeared to be much slower compared to parted and didn't seem to fully support GPT partition labels. Keep in mind that, unlike gparted, parted applies the changes to the block device immediately. Proceed with caution.
Before starting, it's best to backup the current partition table for a reference:
Code:
# gparted /dev/sdc
GNU Parted 3.2
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) unit MiB
(parted) print
Number Start End Size File system Name Flags
1 0,02MiB 85,0MiB 85,0MiB fat16 modem msftdata
2 85,0MiB 170MiB 85,0MiB fat16 modem1 msftdata
3 170MiB 171MiB 0,50MiB sbl1
4 171MiB 171MiB 0,50MiB sbl2
5 171MiB 172MiB 1,00MiB sbl3
6 172MiB 173MiB 1,00MiB rpm
7 173MiB 174MiB 1,00MiB tz
8 174MiB 175MiB 0,50MiB DDR
9 175MiB 179MiB 4,00MiB aboot
10 179MiB 180MiB 1,00MiB misc
11 180MiB 182MiB 2,85MiB logo
12 182MiB 183MiB 0,76MiB m9kefs1
13 183MiB 184MiB 0,76MiB m9kefs2
14 184MiB 184MiB 0,00MiB m9kefsc
15 184MiB 192MiB 8,11MiB bk1
16 192MiB 193MiB 0,76MiB m9kefs3
17 193MiB 256MiB 63,2MiB bk2
18 256MiB 271MiB 15,0MiB boot
19 271MiB 286MiB 15,0MiB boot1
20 286MiB 301MiB 15,0MiB recovery
21 301MiB 312MiB 11,0MiB bk3
22 312MiB 320MiB 8,00MiB ext4 persist
23 320MiB 832MiB 512MiB ext4 system
24 832MiB 1344MiB 512MiB ext2 system1
25 1344MiB 1728MiB 384MiB ext4 cache
26 1728MiB 5312MiB 3584MiB ext4 userdata
27 5312MiB 29820MiB 24509MiB ext4 storage
Mind that /dev/sdc refers to the block device of my phone and will differ on your system depending on the amount of other block devices connected and the type of your system. It's also best to backup either the entire block device (/dev/sdc) or at last the specific partitions you are going to be messing with (/dev/sdcXY) – this is doubly important for partitions <= 22, the correct content of which may be difficult to retrieve when damaged. Labels (most likely) aren't important, the partition numbers are, so make sure you keep the order of the partitions when fiddling with them.
After finishing, reconnect the phone to make the kernel recognize the new partition structure and create the filesystem (mkfs.ext4) for any partitions you have created. The following example makes the system and system1 partitions 1GiB each and the userdata partition 4GiB at the expense of the storage partition:
Code:
# parted /dev/sdc
GNU Parted 3.2
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) rm 23
(parted) rm 24
(parted) rm 25
(parted) rm 26
(parted) rm 27
(parted) mkpart physical ext4 320MiB 1344MiB
(parted) mkpart physical ext4 1344MiB 2368MiB
(parted) mkpart physical ext4 2368MiB 2752MiB
(parted) mkpart physical ext4 2752MiB 6848MiB
(parted) mkpart physical ext4 6848MiB 29819MiB
(parted) name 23 system
(parted) name 24 system1
(parted) name 25 cache
(parted) name 26 userdata
(parted) name 27 storage
(parted) quit
# sync
And then, after reattaching the phone to the computer:
Code:
# for i in /dev/sdc2[34567]; do mkfs.ext4 $i; done
# sync
Recovery mode
For booting into recovery, consult [3].
Booting into a custom recovery
Use the process described at [2], with steps 7-8 interchanged with 9-10. I used the emms_appsboot.mbm and recovery-clockwork-6.0.5.0-aries-20140718.img files (see List of files) from the fastboot mode as follows:
Code:
$ fastboot flash recovery recovery-clockwork-6.0.5.0-aries-20140718.img
$ fastboot flash aboot emmc_appsboot.mbn
$ fastboot boot recovery-clockwork-6.0.5.0-aries-20140718.img
If the phone gets stuck at booting during the last step, restart the phone and try again.
You should now be in the custom recovery. For me, this only lasted until a reboot. Then, the recovery was replaced with the stock one and it became impossible to boot into the system, effectively softbricking the phone. To fix this, flash the stock emmc_appsboot.mbm bootloader image extracted from the .zip of the MIUI ROM you are using and flash it from the fastboot mode:
Code:
$ fastboot flash aboot ./the/original/emmc_appsboot.mbn
$ fastboot continue
Fastboot mode
To boot into the fastboot mode, either:
Reboot the phone while holding the volume down button.
Run adb reboot bootloader against the phone in the system or in the recovery mode.
List of files
You don't need these files, it's only what I used, which should enable the reproducibility of my results.
xiaomi.eu_multi_aries_5.8.6_v6-5.0.zip – The MIUI6 v5.8.6 Czech ROM. Downloaded from [5].
emms_appsboot.mbm – A fixed bootloader for MIUI6 v5.8.6, which allows for the installation of recoveries other than the
built-in one (see Reinstalling the recovery). Downloaded from [2].
recovery-clockwork-6.0.5.0-aries-20140718.img – A recovery image of a custom version of the clockworkmod. Extracted from the archive downloaded from [1].
cm-11-20150802-NIGHTLY-aries.zip – An alternative ROM (Cyanogenmod 11). downloaded from [6].
Links
[2014-07-08] ClockworkMod Recovery 6.0.5.0
[Tools, Tips & Tutorials] [Device Team] How to get Custom Recoveries working again on Mi 2/2S with MIUI 6
[Tips & Tutorials] [Mods' Insight] Understanding Recovery mode & Download Mode
[SCRIPT] Fix partition table for Android 4.4
MIUIV6 OFFICIAL RELEASE
Browse Files for Samsung Galaxy S - aries
Hi, I updated partitioning tutorial to install Android 10: https://forum.xda-developers.com/t/guide-tutorial-howto-xiaomi-mi-2-2s-stock-to-android-10.4391775/
So I finaly soft bricked my p9 lite trying to dual sim it.
I think the situation is not that bad.
Quick recap :
- My phone is VNS-L31 (europe)
- I have access to twrp (venus version)
- My phone is unlocked and FRP unlock
- I have access to Fastboot rescue mode (and fasboot devices -l show it)
So what the best way ? I'm a bit lost with terminology.
I suppose I have to download a full stock firmware (but from where and what version ??)
I suppose I also have to complety wipe my old system ? (twrp make error on this ?)
Should I try an update.app with erecovery or flash directly partition by partition ?
ut0mt8 said:
So I finaly soft bricked my p9 lite trying to dual sim it.
I think the situation is not that bad.
Quick recap :
- My phone is VNS-L31 (europe)
- I have access to twrp (venus version)
- My phone is unlocked and FRP unlock
- I have access to Fastboot rescue mode (and fasboot devices -l show it)
So what the best way ? I'm a bit lost with terminology.
I suppose I have to download a full stock firmware (but from where and what version ??)
I suppose I also have to complety wipe my old system ? (twrp make error on this ?)
Should I try an update.app with erecovery or flash directly partition by partition ?
Click to expand...
Click to collapse
Heyho,
if u have a system which can boot into the TWRP recovery:
1) make sure which Android version u currently run (MM / N)
2) get u a oeminfo matching to the version u want end in (for example: L31C432B130_DS)
3) flash the oeminfo via TWRP u can use my toolkit to do so
4) boot into the bootloader (fastboot mode)
5) flash the stock recovery matching to ur current kernel (MM / N)
(the recovery is included in my toolkit packages, otherwise u need to get u the "Huawei Update Extractor" here on XDA and extract the recovery from the update.app)
6) copy the FULL-L31C432Bxxx update.app on ur sdcard/internal storage (dload folder)
(!IMPORTANT! - The oeminfo must match to the update! This means, u can flash a B130 oeminfo and a B160 rom. But, u can't flash a B130 rom over an B160 oeminfo!)
7) turn the device off and disconnect it from any USB connection
8) turn the device on with the following combination:
Press and hold [Vol+ Vol- Power] until u see the huawei recovery
9) wait until the update is done
If u can't boot into TWRP:
1) turn ur device off - plug the USB cable in
2) press and hold [Vol- Power]
3) unlock ur device with my toolkit, the code can be requested by huawei (a link is in my toolkit)
4) flash the TWRP recovery matching to ur current kernel (MM / N)
5) follow the previous steps above from (1)
Hope i could help u
Regards,
Sebastian
k1ll3r8e said:
Heyho,
if u have a system which can boot into the TWRP recovery:
1) make sure which Android version u currently run (MM / N)
Click to expand...
Click to collapse
Thanks for your patience. Note that I am currently on a MacBook and I cannot use directly your toolkit (my Windows is doing weird thing with usb, as constantly disconnect/reconnect my phone, not very usable)
Yes I can boot on TWRP recovery (I ve installed this one TWRP 3.1.0 Data and Restore Fixed by HassanMirza01).
The good news is I can connect on my phone via adb shell.
1) I try flashing different roms (the last one was Elite by Hassan, but didn't work); the last working was stock Emui 5 Nougat.
I don't understand how I have an android version again as I wipe almost everything ? How to be sure ? (kernel in /boot ? )
k1ll3r8e said:
2) get u a oeminfo matching to the version u want end in (for example: L31C432B130_DS)
3) flash the oeminfo via TWRP u can use my toolkit to do so
Click to expand...
Click to collapse
2) OK
3) Something like this ?
Code:
adb shell su -c "dd bs=32768 if=/sdcard/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
k1ll3r8e said:
4) boot into the bootloader (fastboot mode)
5) flash the stock recovery matching to ur current kernel (MM / N)
(the recovery is included in my toolkit packages, otherwise u need to get u the "Huawei Update Extractor" here on XDA and extract the recovery from the update.app)
Click to expand...
Click to collapse
4) OK
5) You mean only replace twrp with the stock recovery ? What are the command line ? adb+dd or just flashboot recovery ?
I notice in your toolkit we can flash boot/recovery/system/cust partition. Helpful or not ?
(Another question : did you known a tool like huawai update extractor for mac/linux ?
OK just find it in php perfect. => https://github.com/scue/unpacker_huawei. )
k1ll3r8e said:
6) copy the FULL-L31C432Bxxx update.app on ur sdcard/internal storage (dload folder)
(!IMPORTANT! - The oeminfo must match to the update! This means, u can flash a B130 oeminfo and a B160 rom. But, u can't flash a B130 rom over an B160 oeminfo!)
7) turn the device off and disconnect it from any USB connection
8) turn the device on with the following combination:
Press and hold [Vol+ Vol- Power] until u see the huawei recovery
9) wait until the update is done
Click to expand...
Click to collapse
6) Ok so let's use a B130 oeminfo.
OK this part at the end is to let the official huawei recovery do his job.
Another side question : on adb shell , if I try to mount vendor and product the partition didn't exist.
Confirmed by doing a ls on /dev/ or fdisk.
Code:
~ # mount -a
mount: mounting /vendor on ext4 failed: No such file or directory
mount: mounting /product on ext4 failed: No such file or directory
Command (m for help): p
Disk /dev/block/mmcblk0: 30777344 sectors, 2740M
Logical sector size: 512
Disk identifier (GUID): f9f21fff-a8d4-5f0e-9746-594869aec34e
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30777343
Number Start (sector) End (sector) Size Code Name
1 1024 1535 256K 0700 vrl
2 1536 2047 256K 0700 vrl_backup
3 2048 2559 256K 0700 fw_lpm3
4 2560 4095 768K 0700 frp
5 4096 12287 4096K 0700 fastboot
6 12288 20479 4096K 0700 modemnvm_factory
7 20480 32767 6144K 0700 nvme
8 32768 163839 64.0M 0700 oeminfo
9 163840 172031 4096K 0700 reserved3
10 172032 180223 4096K 0700 modemnvm_backup
11 180224 196607 8192K 0700 modemnvm_img
12 196608 204799 4096K 0700 modemnvm_system
13 204800 270335 32.0M 0700 secure_storage
14 270336 274431 2048K 0700 reserved4
15 274432 278527 2048K 0700 reserved5
16 278528 282623 2048K 0700 persist
17 282624 311295 14.0M 0700 reserved1
18 311296 376831 32.0M 0700 modem_om
19 376832 507903 64.0M 0700 splash2
20 507904 511999 2048K 0700 misc
21 512000 561151 24.0M 0700 modemnvm_update
22 561152 692223 64.0M 0700 recovery2
23 692224 815103 60.0M 0700 reserved2
24 815104 823295 4096K 0700 teeos
25 823296 827391 2048K 0700 trustfirmware
26 827392 860159 16.0M 0700 sensorhub
27 860160 884735 12.0M 0700 fw_hifi
28 884736 950271 32.0M 0700 boot
29 950272 1081343 64.0M 0700 recovery
30 1081344 1146879 32.0M 0700 dts
31 1146880 1343487 96.0M 0700 modem_fw
32 1343488 1347583 2048K 0700 reserved7
33 1347584 1351679 2048K 0700 reserved8
34 1351680 1384447 16.0M 0700 dfx
35 1384448 1392639 4096K 0700 reserved6
36 1392640 1916927 256M 0700 cache
37 1916928 1921023 2048K 0700 hisitest0
38 1921024 1925119 2048K 0700 hisitest1
39 1925120 1933311 4096K 0700 hisitest2
40 1933312 7176191 2560M 0700 system
41 7176192 8224767 512M 0700 cust
42 8224768 30777343 10.7G 0700 userdata
Normal ? or very wrong ? if someone can check on a working device
Again thanks for your patience and flooding you with questions ; I slowly learn, but I will definitively try to make a post with my note.
Best,
So I flash the oeminfo with dd found on your google drive.
It seems it relock my phone. So I suppose I have to unlock it again with ./fastboot oem unlock xxxxx ?
I put a stock B160 on root on the sdcard (/sdcard/dload/UPDATE.APP). VNS-L31C432B160.zip.
In fact I cannot go to huawei recovery (hold power +UP+Down) nor Twrp ; I always finish on erecovey (which it not very helpful)
Heyho,
ut0mt8 said:
Thanks for your patience. Note that I am currently on a MacBook and I cannot use directly your toolkit (my Windows is doing weird thing with usb, as constantly disconnect/reconnect my phone, not very usable)
Yes I can boot on TWRP recovery (I ve installed this one TWRP 3.1.0 Data and Restore Fixed by HassanMirza01).
The good news is I can connect on my phone via adb shell.
Click to expand...
Click to collapse
Np
-
About the recovery, u should use the TWRP from @OldDroid from my signature, i can confirm that this recovery will work as it should.
ut0mt8 said:
1) I try flashing different roms (the last one was Elite by Hassan, but didn't work); the last working was stock Emui 5 Nougat.
I don't understand how I have an android version again as I wipe almost everything ? How to be sure ? (kernel in /boot ? )
Click to expand...
Click to collapse
Hehe, u "only" wiped the system, data not the boot partition, the boot.img contains the kernel and ram-disk. But, an N kernel can't boot an MM recovery, also the MM kernel can't boot an N recovery.
ut0mt8 said:
3) Something like this ?
Code:
adb shell su -c "dd bs=32768 if=/sdcard/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
Click to expand...
Click to collapse
Yes and no, the oeminfo is 64 mb not 32 mb!
Just use:
Code:
adb shell su -c "dd if=/sdcard/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
Because, each oeminfo dump will be exactly 64 mb so there is no need to set the size.
ut0mt8 said:
5) You mean only replace twrp with the stock recovery ? What are the command line ? adb+dd or just flashboot recovery ?
Click to expand...
Click to collapse
To flash the recovery u should use fastboot...
Code:
fastboot flash recovery /path/to/the/recovery/image
ut0mt8 said:
I notice in your toolkit we can flash boot/recovery/system/cust partition. Helpful or not ?
Click to expand...
Click to collapse
As described in the preparation, this is only to get the device back to work, that u can boot into the TWRP and do all the stuff i just tell u...
ut0mt8 said:
Another side question : on adb shell , if I try to mount vendor and product the partition didn't exist.
Confirmed by doing a ls on /dev/ or fdisk.
Code:
~ # mount -a
mount: mounting /vendor on ext4 failed: No such file or directory
mount: mounting /product on ext4 failed: No such file or directory
Command (m for help): p
Disk /dev/block/mmcblk0: 30777344 sectors, 2740M
Logical sector size: 512
Disk identifier (GUID): f9f21fff-a8d4-5f0e-9746-594869aec34e
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30777343
Number Start (sector) End (sector) Size Code Name
1 1024 1535 256K 0700 vrl
2 1536 2047 256K 0700 vrl_backup
3 2048 2559 256K 0700 fw_lpm3
4 2560 4095 768K 0700 frp
5 4096 12287 4096K 0700 fastboot
6 12288 20479 4096K 0700 modemnvm_factory
7 20480 32767 6144K 0700 nvme
8 32768 163839 64.0M 0700 oeminfo
9 163840 172031 4096K 0700 reserved3
10 172032 180223 4096K 0700 modemnvm_backup
11 180224 196607 8192K 0700 modemnvm_img
12 196608 204799 4096K 0700 modemnvm_system
13 204800 270335 32.0M 0700 secure_storage
14 270336 274431 2048K 0700 reserved4
15 274432 278527 2048K 0700 reserved5
16 278528 282623 2048K 0700 persist
17 282624 311295 14.0M 0700 reserved1
18 311296 376831 32.0M 0700 modem_om
19 376832 507903 64.0M 0700 splash2
20 507904 511999 2048K 0700 misc
21 512000 561151 24.0M 0700 modemnvm_update
22 561152 692223 64.0M 0700 recovery2
23 692224 815103 60.0M 0700 reserved2
24 815104 823295 4096K 0700 teeos
25 823296 827391 2048K 0700 trustfirmware
26 827392 860159 16.0M 0700 sensorhub
27 860160 884735 12.0M 0700 fw_hifi
28 884736 950271 32.0M 0700 boot
29 950272 1081343 64.0M 0700 recovery
30 1081344 1146879 32.0M 0700 dts
31 1146880 1343487 96.0M 0700 modem_fw
32 1343488 1347583 2048K 0700 reserved7
33 1347584 1351679 2048K 0700 reserved8
34 1351680 1384447 16.0M 0700 dfx
35 1384448 1392639 4096K 0700 reserved6
36 1392640 1916927 256M 0700 cache
37 1916928 1921023 2048K 0700 hisitest0
38 1921024 1925119 2048K 0700 hisitest1
39 1925120 1933311 4096K 0700 hisitest2
40 1933312 7176191 2560M 0700 system
41 7176192 8224767 512M 0700 cust
42 8224768 30777343 10.7G 0700 userdata
Normal ? or very wrong ? if someone can check on a working device
Click to expand...
Click to collapse
I don't use the TWRP u mentioned, maybe there is an issue... I had a look on my device with the TWRP from OldDroid, there are those block-devices... But i had a look under "/dev/block/platform/hi_mci.0/by-name". I think, if u have a look at this path, u'll find the block-devices also on ur device.
ut0mt8 said:
So I flash the oeminfo with dd found on your google drive.
It seems it relock my phone. So I suppose I have to unlock it again with ./fastboot oem unlock xxxxx ?
I put a stock B160 on root on the sdcard (/sdcard/dload/UPDATE.APP). VNS-L31C432B160.zip.
In fact I cannot go to huawei recovery (hold power +UP+Down) nor Twrp ; I always finish on erecovey (which it not very helpful)
Click to expand...
Click to collapse
Yup, if u saw a PW-prompt where u entered a random or ur last known PW, the device will normally do a factory-reset.
As u mentioned, u can unlock it with
Code:
fastboot oem unlock UR_UNLOCK_CODE
again.
About the recovery, which recovery u flashed? (The L31C432B130? it's MM and can't boot with an N kernel...)
Just download the "pkg.L31C432B380.zip" from my g-drive and flash the stock recovery from this package, it's an N recovery.
Hope everything is now working for u
Regards,
Sebastian
k1ll3r8e said:
Heyho,
Np
-
About the recovery, u should use the TWRP from @OldDroid from my signature, i can confirm that this recovery will work as it should.
Hehe, u "only" wiped the system, data not the boot partition, the boot.img contains the kernel and ram-disk. But, an N kernel can't boot an MM recovery, also the MM kernel can't boot an N recovery.
Yes and no, the oeminfo is 64 mb not 32 mb!
Just use:
Code:
adb shell su -c "dd if=/sdcard/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
Because, each oeminfo dump will be exactly 64 mb so there is no need to set the size.
To flash the recovery u should use fastboot...
Code:
fastboot flash recovery /path/to/the/recovery/image
As described in the preparation, this is only to get the device back to work, that u can boot into the TWRP and do all the stuff i just tell u...
I don't use the TWRP u mentioned, maybe there is an issue... I had a look on my device with the TWRP from OldDroid, there are those block-devices... But i had a look under "/dev/block/platform/hi_mci.0/by-name". I think, if u have a look at this path, u'll find the block-devices also on ur device.
Yup, if u saw a PW-prompt where u entered a random or ur last known PW, the device will normally do a factory-reset.
As u mentioned, u can unlock it with
Code:
fastboot oem unlock UR_UNLOCK_CODE
again.
About the recovery, which recovery u flashed? (The L31C432B130? it's MM and can't boot with an N kernel...)
Just download the "pkg.L31C432B380.zip" from my g-drive and flash the stock recovery from this package, it's an N recovery.
Hope everything is now working for u
Regards,
Sebastian
Click to expand...
Click to collapse
OK so I ve re unlock my phone, and flash the recovery with your twrp version. Still have the problem with
Code:
mount: mounting /vendor on ext4 failed: No such file or directory
mount: mounting /product on ext4 failed: No such file or directory
mount: mounting /usbotg on auto failed: No such file or directory
but let's move on.
If I understand correctly I have now a good oeminfo, a boot with nougat kernel and initramfs/initrd.
I have to flash the recovery with stock recovery nougat in order to flash an old B130 update.app.
Let's try.
PS : bs paramater in dd mean how much data your write at each pass (it's an optimisation parameter don't needed here)
ut0mt8 said:
OK so I ve re unlock my phone, and flash the recovery with your twrp version. Still have the problem with
Code:
mount: mounting /vendor on ext4 failed: No such file or directory
mount: mounting /product on ext4 failed: No such file or directory
mount: mounting /usbotg on auto failed: No such file or directory
but let's move on.
If I understand correctly I have now a good oeminfo, a boot with nougat kernel and initramfs/initrd.
I have to flash the recovery with stock recovery nougat in order to flash an old B130 update.app.
Let's try.
PS : bs paramater in dd mean how much data your write at each pass (it's an optimisation parameter don't needed here)
Click to expand...
Click to collapse
Heyho,
hmm, maybe the partitions are not formatted... - Just proceed with the update, normally it will flash those partitions. I had a similar issue a while ago.
About the "bs", it's meant as "block-size"? If so, the normal block-size for the oeminfo will be "4096"
Regards,
Sebastian
k1ll3r8e said:
Heyho,
hmm, maybe the partitions are not formatted... - Just proceed with the update, normally it will flash those partitions. I had a similar issue a while ago.
About the "bs", it's meant as "block-size"? If so, the normal block-size for the oeminfo will be "4096"
Regards,
Sebastian
Click to expand...
Click to collapse
Yep It means blocksize but in fact it is just pass to the read/write system call ; so you can virtually pass every value (even a size greater than the image file; in that case dd/system will try to read it in one pass). This is no alignement related.
Another quick question : did you know a method to break the boot loop and enter fastboot mode ?
Normally you have to shutdown your device but in that configuration I have no option (unless draining the battery).
I think I succeed one time with a precise timing but not sure.
ut0mt8 said:
Yep It means blocksize but in fact it is just pass to the read/write system call ; so you can virtually pass every value (even a size greater than the image file; in that case dd/system will try to read it in one pass). This is no alignement related.
Another quick question : did you know a method to break the boot loop and enter fastboot mode ?
Normally you have to shutdown your device but in that configuration I have no option (unless draining the battery).
I think I succeed one time with a precise timing but not sure.
Click to expand...
Click to collapse
Heyho,
thx for the info
-
About the boot-loop, u can try to long press Power until it turn off and on again.
Just hold the device connected to USB, that's important to enter fastboot!
Just try to:
1) power off
2) and when it's off, hold Vol-
that should be enough to enter fastboot.
Regards,
Sebastian
k1ll3r8e said:
Heyho,
thx for the info
-
About the boot-loop, u can try to long press Power until it turn off and on again.
Just hold the device connected to USB, that's important to enter fastboot!
Just try to:
1) power off
2) and when it's off, hold Vol-
that should be enough to enter fastboot.
Regards,
Sebastian
Click to expand...
Click to collapse
Effectively with phone connected to usb it work much better
So I correctly install the stock recovery , and push an UPDATE.APP, the recovery launch and found the package but it hold at 5% and does nothing more.
I think I had to flash all partition more violently. Let's try.
What really help was if something can look at a correct partition scheme for /vendor an /product; coz I think my problem came from here.
Thks.
ut0mt8 said:
Effectively with phone connected to usb it work much better
So I correctly install the stock recovery , and push an UPDATE.APP, the recovery launch and found the package but it hold at 5% and does nothing more.
I think I had to flash all partition more violently. Let's try.
What really help was if something can look at a correct partition scheme for /vendor an /product; coz I think my problem came from here.
Thks.
Click to expand...
Click to collapse
Heyho,
just disconnect the device while the update... This is normal and mentioned a lot of times... That when the device is connected to USB the update will fail at 5%, why ever.^^
-
I wiped my device yesterday ~20++ times and flashed all the time back to B130 so i can promise u that this will work...
oeminfo + stock recovery + update = 100% B130
Regards,
Sebastian
k1ll3r8e said:
Heyho,
just disconnect the device while the update... This is normal and mentioned a lot of times... That when the device is connected to USB the update will fail at 5%, why ever.^^
-
I wiped my device yesterday ~20++ times and flashed all the time back to B130 so i can promise u that this will work...
oeminfo + stock recovery + update = 100% B130
Regards,
Sebastian
Click to expand...
Click to collapse
OMG it's finally working ! and dual simed !!
Big thks for your patiente with noob like me.
There still a lot of things I had to dig/understand (I will try to flash twrp again and check for my partition issue)
I will now try to make a quick howto with my notes.