Database Info

[Q] How to pull boot.img, recovery.img and other stuff from an Android device...

Hey guys... I did a system dump of my HCL Me Connect V3 a while ago, and I posted it on XDA.
Today I tried to pull the .img files from my device...
I have installed Android SDK and platform-tools.
The device is rooted, and I have installed the proper drivers and enabled USB Debugging...
I use these commands:
Code:
cd C:\Android\platform-tools\
adb devices
adb shell
su
The device is detected successfully, and root access is granted successfully.
and this is where the problem occurs...
Normally I'd just enter
Code:
cat /proc/mtd
and the boot.img, recovery.img and other stuff should be displayed, but that's not the case...
Instead of proper results, I get
dev: size erazesise name
and that's it as seen in this image:
{
"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"
}
Since
Code:
cat /proc/mtd
does not work I tried with this one:
Code:
cat /proc/emmc
and now I get totally different results, as shown in the image below:
I really don't know what to do. I desperately need the recovery.img and boot.img...
The device has MT8317 chip if it's of any help... Please help...

bestnugnification said:
Hey guys... I did a system dump of my HCL Me Connect V3 a while ago, and I posted it on XDA.
Today I tried to pull the .img files from my device...
I have installed Android SDK and platform-tools.
The device is rooted, and I have installed the proper drivers and enabled USB Debugging...
I use these commands:
Code:
cd C:\Android\platform-tools\
adb devices
adb shell
su
The device is detected successfully, and root access is granted successfully.
and this is where the problem occurs...
Normally I'd just enter
Code:
cat /proc/mtd
and the boot.img, recovery.img and other stuff should be displayed, but that's not the case...
Instead of proper results, I get
dev: size erazesise name
and that's it as seen in this image:
Since
Code:
cat /proc/mtd
does not work I tried with this one:
Code:
cat /proc/emmc
and now I get totally different results, as shown in the image below:
I really don't know what to do. I desperately need the recovery.img and boot.img...
The device has MT8317 chip if it's of any help... Please help...
Click to expand...
Click to collapse
type the ff:
adb devices (hit enter)
adb shell (hit enter)
su (hit enter)
cat /proc/mtd (hit enter)
now from your screen look at your files and you see mtd2 has your boot.img
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 04380000 00020000 "system"
mtd4: 04380000 00020000 "cache"
mtd5: 04ac0000 00020000 "userdata"
once u see it's LOCATION in which in this sample is in mtd2
type:
cat /dev/mtd/mtd2 > /sdcard/mtd2.img or
cat /dev/mtd/mtd2 > /sdcard/boot.img
note:
instead of mtd2.img you can directly name it to boot.img
and try these with other imgs too

My device is showing mmcblk. with no name specified.
Hi there, i m facing prblm. my device is showing mmcblk....with no name such as system , boot, cache,data,as described by you.. But in esexplorer i found in partition stats file that some partitions hold system,data,cache,productifo but not able to find boot and recovery partition.
My question is that , can we be able to create our own boot.img and recovery.img file from android currently using or not ....If yes then HOW?

How to root Bluestacks 2 using Linux in VirtualBox (Modify .vdi file)

BlueStacks 2.2.17.6203 is introducing "VirtualBox VMs".
The filesystems have been changed to "vdi format" (VirtualBox).
For linux experts: if you know how to mount and modify .vdi without VirtualBox, skip to step 9.
Well, let's get started!
First of all, to root BlueStacks this way you need VirtualBox and you have a Linux OS installed. If you just got started, I'll recommended Ubuntu, you can follow the guide installing Ubuntu on BirtualBox. http://www.wikihow.com/Install-Ubuntu-on-VirtualBox
Also, you will need some linux knowledge. It's not necessessary, but I won't provide any support about the part dealing with linux commands. Just follow the instructions and probably you will be able to root it, but it might not be that simple.
The second mandatory stuff you will need is the Android App called SuperSU. At this time, you should be able to find the latest SuperSU. The instructions should be the same with other SuperSU versions.
Here is a direct link http://www.supersu.com/download
This tutorial assumes you already have an installed BlueStacks you wish to root, but make sure Bluestacks and Ubuntu isn't running isn't running. So, let's get started.
In this tutorial i'm using Ubuntu.
1. MAKE A BACKUP OF ROOT.VDI FILE FIRST!
2. To modify Root.vdi, you need to mount it in Ubuntu virtual machine. Select Ubuntu and click Settings -> Storage. Select Controller: SATA and click on the HDD with green plus symbol.
{
"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"
}
3. A dialog box will appear. Select Choose existing disk
4. Navigate to Bluestacks directory where you installed. Select Root.vdi and Open
ProTip: You can mount Data.vdi and SDcard.vdi to transfer files between guest and VDI.
5. Root.vdi should be added in Storage. Click OK
6. Start Ubuntu on VirtualBox
7. Ubuntu: On your desktop, you should see the grey Hard Drive icon on the right taskbar. Yep, that's root.vdi image file that has been mounted and the disk name should be named 8,6 GB Volume
8. Extract x86 Folder from .zip (Recovery Flashable.zip) archive file and /common/SuperSU.apk somewhere on Ubuntu. Bluestacks is based on Android x86.
8.1. If you already downloaded it on your host computer, Click Devices -> Drag and Drop, Select Bidirectional and you can transfer the file to guest
If you haven't download it yet, download it from http://www.supersu.com/download and click Recovery Flashable.zip
9. Copy the following SuperSU files into your mounted root.vdi
Add file: /x86/su -> (8,6 GB Volume)/android/system/xbin/su
Rename file: /x86/su ---> (8,6 GB Volume)/x86/daemonsu
Add file: /x86/daemonsu ---> (8,6 GB Volume)/android/system/xbin/daemonsu
Add file: /x86/supolicy ---> (8,6 GB Volume)/android/system/xbin/supolicy
Add file: /x86/libsupol.so ---> (8,6 GB Volume)/android/system/lib/libsupol.so
Add file: /common/Superuser.apk ---> (8,6 GB Volume)/android/system/app/Superuser.apk
10. You need to change file permissions in order for SuperSU to work correctly. Open terminal and type the following commands. Type your password when asked
Note: The disk name might be different. You can check it by right click on 8,6 GB Volume and select Properties
ProTip: Type sudo chmod xxx in terminal and drag a file to get the full path like below. Press UP ARROW on your keyboard to show the last command you used.
sudo chmod 755 '/media/test/<disk udid>/android/system/xbin/su'
sudo chmod 755 '/media/test/<disk udid>/android/system/xbin/daemonsu'
sudo chmod 755 '/media/test/<disk udid>/android/system/xbin/supolicy'
sudo chmod 644 '/media/test/<disk udid>/android/system/lib/libsupol.so'
sudo chmod 644 '/media/test/<disk udid>/android/system/app/Superuser.apk'
Files should be owned by root:root. No need to change it on Ubuntu.
11. Now we need to start "daemonsu" on every reboot. BlueStacks init procedure is quite simple. Seems like there is only android/system/etc/init.sh. So, open android/system/etc/init.sh in your preferred linux text-editor, go at the bottom of the file and search for:
Code:
init|"")
do_init
;;
esac
Add this
Code:
init|"")
do_init
/system/xbin/daemonsu --auto-daemon &
;;
esac
I'd say we're done now! Shutdown your Virtualbox
12. Now you can start your BlueStacks. When it's booted, launch SuperSU via Play Store.
You will be prompted about a SuperSU update. Choose the "normal" way and after the update, restart your BlueStacks.
13. That should be it. Now your BlueStacks is rooted.
To be certain you should open your PlayStore and install your preferred RootChecker.
An additional task you might want to do would be using some apps like "/system/app Mover" and "System App Uninstall" and change the SystemDefaultAppLauncher and SystemDefaultAppBrowser.
I usually install Nova Launcher.
Also, as Root FileExplorer, I install X-Plore.
You might want to install a CatLog too!
Hope you enjoyed this tutorial
Hope you will enjoy you newly rooted BlueStacks.
Tweak your Bluestacks and share your .vdi files to everyone.
Credit goes to rumbla (mybot.run) for the original tutorial how to modify root.fs
And me for this new tutorial

Here are the links that helped me a lot to copy/paste text and also files between guest operating system (Ubuntu) and host computer (Windows 10)
"How do I tell if virtualbox guest additions is installed and working correctly" on Ubuntu Forums
"Virtualbox and shared folders - permissions problem" also on Ubuntu Forums
Also I had to chown root:root "files"
Working ................. so far, so good
Thanks a lot

I comfirmed that it still working on bluestack 4 (mac os) thanks a lot! <3
Note that if BS is "x86_64" then you need using files in "x64" folder!

evildog1 said:
BlueStacks 2.2.17.6203 is introducing "VirtualBox VMs".
The filesystems have been changed to "vdi format" (VirtualBox).
For linux experts: if you know how to mount and modify .vdi without VirtualBox, skip to step 9.
Well, let's get started!
First of all, to root BlueStacks this way you need VirtualBox and you have a Linux OS installed. If you just got started, I'll recommended Ubuntu, you can follow the guide installing Ubuntu on BirtualBox. http://www.wikihow.com/Install-Ubuntu-on-VirtualBox
Also, you will need some linux knowledge. It's not necessessary, but I won't provide any support about the part dealing with linux commands. Just follow the instructions and probably you will be able to root it, but it might not be that simple.
The second mandatory stuff you will need is the Android App called SuperSU. At this time, you should be able to find the latest SuperSU. The instructions should be the same with other SuperSU versions.
Here is a direct link http://www.supersu.com/download
This tutorial assumes you already have an installed BlueStacks you wish to root, but make sure Bluestacks and Ubuntu isn't running isn't running. So, let's get started.
In this tutorial i'm using Ubuntu.
1. MAKE A BACKUP OF ROOT.VDI FILE FIRST!
2. To modify Root.vdi, you need to mount it in Ubuntu virtual machine. Select Ubuntu and click Settings -> Storage. Select Controller: SATA and click on the HDD with green plus symbol.
3. A dialog box will appear. Select Choose existing disk
4. Navigate to Bluestacks directory where you installed. Select Root.vdi and Open
ProTip: você pode montar Data.vdi e SDcard.vdi para transferir arquivos entre o convidado e o VDI.
5. Root.vdi deve ser adicionado ao Storage. Clique OK
6. Inicie o Ubuntu no VirtualBox
7. Ubuntu: em sua área de trabalho, você deve ver o ícone cinza do disco rígido na barra de tarefas direita. Sim, esse é o arquivo de imagem root.vdi que foi montado e o nome do disco deve se chamar Volume de 8,6 GB
8. Extraia a pasta x86 do arquivo .zip (Recovery Flashable.zip) e /common/SuperSU.apk em algum lugar do Ubuntu. Bluestacks é baseado no Android x86.
8,1 Se você já fez o download em seu computador host, clique em Dispositivos -> Arrastar e soltar, selecione bidirecional e você pode transferir o arquivo para o convidado
Se você ainda não fez o download, faça o download em http://www.supersu.com/download e clique em Recovery Flashable.zip
9. Copie os seguintes arquivos SuperSU para o root.vdi montado
Adicionar arquivo: / x86 / su -> (Volume de 8,6 GB) / android / system / xbin / su
Renomear arquivo: / x86 / su ---> (Volume de 8,6 GB) / x86 / daemonsu
Adicionar arquivo: / x86 / daemonsu ---> (Volume de 8,6 GB) / android / system / xbin / daemonsu
Adicionar arquivo: / x86 / supolicy ---> (Volume de 8,6 GB) / android / system / xbin / supolicy
Adicionar arquivo: /x86/libsupol.so ---> (Volume de 8,6 GB) /android/system/lib/libsupol.so
Adicionar arquivo: /common/Superuser.apk ---> (Volume de 8,6 GB) /android/system/app/Superuser.apk
10. Você precisa alterar as permissões do arquivo para que o SuperSU funcione corretamente. Abra o terminal e digite os seguintes comandos. Digite sua senha quando solicitado
Nota: o nome do disco pode ser diferente. Você pode verificar clicando com o botão direito em Volume de 8,6 GB e selecione Propriedades
ProTip: Digite sudo chmod xxx no terminal e arraste um arquivo para obter o caminho completo como abaixo. Pressione a SETA PARA CIMA no teclado para mostrar o último comando usado.
sudo chmod 755 '/ media / test / <disk udid> / android / system / xbin / su'
sudo chmod 755 '/ media / test / <disk udid> / android / system / xbin / daemonsu'
sudo chmod 755 '/ media / test / <disk udid> / android / system / xbin / supolicy'
sudo chmod 644 '/ media / test / <disk udid> /android/system/lib/libsupol.so'
sudo chmod 644 '/ media / test / <disk udid> /android/system/app/Superuser.apk'
Os arquivos devem pertencer a root: root. Não há necessidade de alterá-lo no Ubuntu.
11. Agora precisamos iniciar o "daemonsu" a cada reinicialização. O procedimento de inicialização do BlueStacks é bastante simples. Parece que só existe android / system /etc/init.sh. Portanto, abra android / system / etc / init.sh em seu editor de texto Linux preferido, vá até o final do arquivo e pesquise por:
[CÓDIGO] init | "")
fazendo
;;
esac [/ CODE]
Adicione isso
[CÓDIGO] init | "")
fazendo
/ system / xbin / daemonsu --auto-daemon &
;;
esac [/ CODE]
Eu diria que terminamos agora! Desligue seu Virtualbox
12. Agora você pode iniciar seus BlueStacks. Quando ele for inicializado, inicie o SuperSU via Play Store.
Você será avisado sobre uma atualização do SuperSU. Escolha o caminho "normal" e após a atualização reinicie seus BlueStacks.
13. Deve ser isso. Agora seu BlueStacks está enraizado.
Para ter certeza, você deve abrir sua PlayStore e instalar o RootChecker de sua preferência.
Uma tarefa adicional que você pode querer fazer seria usar alguns aplicativos como "/ system / app Mover" e "System App Uninstall" e alterar SystemDefaultAppLauncher e SystemDefaultAppBrowser.
Eu geralmente instalo o Nova Launcher.
Além disso, como Root FileExplorer, eu instalo o X-Plore.
Você pode querer instalar um CatLog também!
Espero que tenha gostado desse tutorial
Espero que você goste de seu BlueStacks recém-enraizado.
Ajuste seus Bluestacks e compartilhe seus arquivos .vdi com todos.
O crédito vai para rumbla (mybot.run) pelo tutorial original sobre como modificar root.fs
E eu para este novo tutorial
Click to expand...
Click to collapse
Não dá

How To Guide [GUIDE] How to unlock the bootloader for Nokia 2.2

To content farms: DO NOT COPY AND PASTE THE ENTIRE GUIDE!
Click to expand...
Click to collapse
Now the last piece of puzzle of Nokia x.2 series bootloader unlock line has been completed, thanks to the help of a member called Woke_World.
After I read his procedure, I decided to optimize the entire procedure and use my own firmware file to achieve it.
Step 1: Do full backup
(For this case please use SP Flash Tool 5.1924 or newer that can be found on spflashtool.com )
The firmware for this procedure can be downloaded here: https://sourceforge.net/projects/fi...uaqin_ZAL1670.full.lzma2.d056631a.7z/download
SHA256: D056631A8A795A06795B3A4E5F334DBF9B55C3C71269831F8E7926FA3ABA5637
Please follow the procedure in this topic to do readback: https://forum.xda-developers.com/t/...-global-nokia-5-1-plus-unbrick-guide.3858253/
For this case, you need to keep Download Agent file as the same came with SP Flash Tool, and altunlock-MT6761_Android_scatter.txt
Once readback done, please extract these images inside your backup for later use:
Code:
nvcfg.img
nvram.img
proinfo.img
protect1.img
protect2.img
DO NOT SKIP STEP 1, OR YOUR PHONE WILL NOT HAVE IMEI AND SN!
Click to expand...
Click to collapse
Step 2: Format all + Download to flash the firmware with altunlock scatter file
Switch to Download tab, and choose format all + download to flash the entire phone with this scatter file: "altunlock-MT6761_Android_scatter.txt"
Once flash complete, disconnect the phone.
Step 3: Bootloader unlock
Press and hold volume down key and connect to PC - keep that condition for around 12 seconds then the phone will boot to Fastboot mode.
Execute these 2 commands to perform bootloader unlock:
Code:
fastboot flashing lock_critical
fastboot oem unlock
Look at your phone and press volume up to confirm unlock. Once done, disconnect the phone and remove the battery, wait 5 seconds and place the battery back.
Step 4: Do readback again
Once readback done, please extract these images inside your backup for later use:
Code:
sec1.img
seccfg.img
Step 5: Format all + Download to flash the firmware with original scatter file
Switch to Download tab, and choose format all + download to flash the entire phone with the original scatter file named as "MT6761_Android_scatter.txt" - note there's no altunlock at the beginning of filename.
Once flash complete, disconnect the phone.
Step 6: Power on the phone and enable USB debugging, root the phone with MTK Easy SU
[NOTE: DO NOT INSERT ANY SIM CARDS AND YOU MUST SKIP INTERNET CONNECTION]
You can download the MTK Easy SU apk from here : https://github.com/JunioJsv/mtk-easy-su/releases/latest
And Magisk APK from here : https://github.com/topjohnwu/magisk/releases/latest
When you have both MTK Easy Su and Magisk APK installed, please enable the "Run as 64 Bits" option, and tap the hash (#) button to enable root.
Once root complete, we can now re-enable bootloader unlock and restore IMEI.
Step 7: Re-enable bootloader unlock and restore IMEI
Please copy the 7 img files to your phone's internal storage:
Code:
nvcfg.img
nvram.img
proinfo.img
protect1.img
protect2.img
sec1.img
seccfg.img
We assume you copied them to root directory of internal storage (a.k.a. /storage/emulated/0/ )
Then execute these commands on your PC:
Code:
adb shell
su
dd if=/storage/emulated/0/nvcfg.img of=/dev/block/bootdevice/by-name/nvcfg
dd if=/storage/emulated/0/nvram.img of=/dev/block/bootdevice/by-name/nvram
dd if=/storage/emulated/0/proinfo.img of=/dev/block/bootdevice/by-name/proinfo
dd if=/storage/emulated/0/protect1.img of=/dev/block/bootdevice/by-name/protect1
dd if=/storage/emulated/0/protect2.img of=/dev/block/bootdevice/by-name/protect2
dd if=/storage/emulated/0/sec1.img of=/dev/block/bootdevice/by-name/sec1
dd if=/storage/emulated/0/seccfg.img of=/dev/block/bootdevice/by-name/seccfg
When it's done, please perform factory reset to apply the NVRAM restoration.
Please watch this video for entire procedure demonstration:
That wraps up the entire procedure of bootloader unlock, and have fun for modding this device!
Credits:
Woke_World from triple-color company product community
diplomatic for his MTK-SU Exploit and simplified utility called JunioJsv
topjohnwu for MagiskSU

Reserved #1

Reserved #2

How to install custom recovery on this device? How to port TWRP?

Vlenten said:
How to install custom recovery on this device? How to port TWRP?
Click to expand...
Click to collapse
It's unavailable - instead we can only root via patching boot images with Magisk.

hikari_calyx said:
It's unavailable - instead we can only root via patching boot images with Magisk.
Click to expand...
Click to collapse
So It is impossible to install custom firmware?

Vlenten said:
So It is impossible to install custom firmware?
Click to expand...
Click to collapse
Right now GSI can be installed under Android 9 firmware base (WSP-1680 build given), but unable to boot under Android 10 firmware base (WSP-2400).

hikari_calyx said:
Right now GSI can be installed under Android 9 firmware base
Click to expand...
Click to collapse
But how to install this without custom recovery? (sorry, I don't really understand these things)

Vlenten said:
But how to install this without custom recovery? (sorry, I don't really understand these things)
Click to expand...
Click to collapse
Flash under fastboot mode.
Code:
fastboot flash system system-arm64-ab-gapps.img
fastboot --disable-verity flash vbmeta vbmeta_a.img
fastboot -w reboot

How to extract *.img files from ROM_0 backup?

hikari_calyx said:
Now the last piece of puzzle of Nokia x.2 series bootloader unlock line has been completed, thanks to the help of a member called Woke_World.
After I read his procedure, I decided to optimize the entire procedure and use my own firmware file to achieve it.
Step 1: Do full backup
(For this case please use SP Flash Tool 5.1924 or newer that can be found on spflashtool.com )
The firmware for this procedure can be downloaded here: https://www.androidfilehost.com/?fid=2188818919693749336
SHA256: D056631A8A795A06795B3A4E5F334DBF9B55C3C71269831F8E7926FA3ABA5637
Please follow the procedure in this topic to do readback: https://forum.xda-developers.com/t/...-global-nokia-5-1-plus-unbrick-guide.3858253/
For this case, you need to keep Download Agent file as the same came with SP Flash Tool, and altunlock-MT6761_Android_scatter.txt
Once readback done, please extract these images inside your backup for later use:
Code:
nvcfg.img
nvram.img
proinfo.img
protect1.img
protect2.img
Step 2: Format all + Download to flash the firmware with altunlock scatter file
Switch to Download tab, and choose format all + download to flash the entire phone with this scatter file: "altunlock-MT6761_Android_scatter.txt"
Once flash complete, disconnect the phone.
Step 3: Bootloader unlock
Press and hold volume down key and connect to PC - keep that condition for around 12 seconds then the phone will boot to Fastboot mode.
Execute these 2 commands to perform bootloader unlock:
Code:
fastboot flashing lock_critical
fastboot oem unlock
Look at your phone and press volume up to confirm unlock. Once done, disconnect the phone and remove the battery, wait 5 seconds and place the battery back.
Step 4: Do readback again
Once readback done, please extract these images inside your backup for later use:
Code:
sec1.img
seccfg.img
Step 5: Format all + Download to flash the firmware with original scatter file
Switch to Download tab, and choose format all + download to flash the entire phone with the original scatter file named as "MT6761_Android_scatter.txt" - note there's no altunlock at the beginning of filename.
Once flash complete, disconnect the phone.
Step 6: Power on the phone and enable USB debugging, root the phone with MTK Easy SU
[NOTE: DO NOT INSERT ANY SIM CARDS AND YOU MUST SKIP INTERNET CONNECTION]
Puede descargar la aplicación MTK Easy SU desde aquí: https://github.com/JunioJsv/mtk-easy-su/releases/latest
Y Magisk APK desde aquí: https://github.com/topjohnwu/magisk/releases/latest
Cuando tenga instalados MTK Easy Su y Magisk APK, habilite la opción "Ejecutar como 64 Bits" y toque el botón hash (#) para habilitar la raíz.
Una vez que se haya completado la raíz, ahora podemos volver a habilitar el desbloqueo del cargador de arranque y restaurar el IMEI.
Paso 7: vuelva a habilitar el desbloqueo del cargador de arranque y restaure el IMEI
Copie los 7 archivos img en el almacenamiento interno de su teléfono:
[CÓDIGO] nvcfg.img
nvram.img
proinfo.img
protect1.img
protect2.img
sec1.img
seccfg.img [/ CODE]
Suponemos que los copió en el directorio raíz del almacenamiento interno (también conocido como / almacenamiento / emulado / 0 /)
Luego ejecute estos comandos en su PC:
[CÓDIGO]
shell adb
su
dd if = / storage / emulated / 0 / nvcfg.img of = / dev / block / bootdevice / by-name / nvcfg
dd if = / almacenamiento / emulado / 0 / nvram.img de = / dev / block / bootdevice / by-name / nvram
dd if = / almacenamiento / emulado / 0 / proinfo.img de = / dev / block / bootdevice / by-name / proinfo
dd if = / storage / emulated / 0 / protect1.img of = / dev / block / bootdevice / by-name / protect1
dd if = / storage / emulated / 0 / protect2.img of = / dev / block / bootdevice / by-name / protect2
dd if = / storage / emulated / 0 / sec1.img of = / dev / block / bootdevice / by-name / sec1
dd if = / storage / emulated / 0 / seccfg.img of = / dev / block / bootdevice / by-name / seccfg
[/CÓDIGO]
Cuando haya terminado, realice un restablecimiento de fábrica para aplicar la restauración de NVRAM.
Mire este video para ver una demostración completa del procedimiento:
[MEDIA = youtube] OgGfv65wT7U [/ MEDIA]
Eso concluye todo el procedimiento de desbloqueo del cargador de arranque, ¡y diviértete modificando este dispositivo!
Créditos:
Woke_World de la comunidad de productos de la empresa de triple color
diplomático por su MTK-SU Exploit y utilidad simplificada llamada JunioJsv
topjohnwu para MagiskSU
Click to expand...
Click to collapse
¿Es funcional con Android 10 con parche de seguridad 05/01/2021?

nico2781993 said:
¿Es funcional con Android 10 con parche de seguridad 05/01/2021?
Click to expand...
Click to collapse
No matter which OS version is your Nokia 2.2 running, you can always follow this guide. The possibility of MTK flashing cannot be blocked with any OS update.

nico2781993 said:
¿Es funcional con Android 10 con parche de seguridad 05/01/2021?
Click to expand...
Click to collapse
hikari_calyx said:
No matter which OS version is your Nokia 2.2 running, you can always follow this guide. The possibility of MTK flashing cannot be blocked with any OS update.
Click to expand...
Click to collapse
ok thank you very much, excellent thread very well explained

hikari_calyx said:
Now the last piece of puzzle of Nokia x.2 series bootloader unlock line has been completed, thanks to the help of a member called Woke_World.
After I read his procedure, I decided to optimize the entire procedure and use my own firmware file to achieve it.
Step 1: Do full backup
(For this case please use SP Flash Tool 5.1924 or newer that can be found on spflashtool.com )
The firmware for this procedure can be downloaded here: https://www.androidfilehost.com/?fid=2188818919693749336
SHA256: D056631A8A795A06795B3A4E5F334DBF9B55C3C71269831F8E7926FA3ABA5637
Please follow the procedure in this topic to do readback: https://forum.xda-developers.com/t/...-global-nokia-5-1-plus-unbrick-guide.3858253/
For this case, you need to keep Download Agent file as the same came with SP Flash Tool, and altunlock-MT6761_Android_scatter.txt
Once readback done, please extract these images inside your backup for later use:
Code:
nvcfg.img
nvram.img
proinfo.img
protect1.img
protect2.img
Step 2: Format all + Download to flash the firmware with altunlock scatter file
Switch to Download tab, and choose format all + download to flash the entire phone with this scatter file: "altunlock-MT6761_Android_scatter.txt"
Once flash complete, disconnect the phone.
Step 3: Bootloader unlock
Press and hold volume down key and connect to PC - keep that condition for around 12 seconds then the phone will boot to Fastboot mode.
Execute these 2 commands to perform bootloader unlock:
Code:
fastboot flashing lock_critical
fastboot oem unlock
Look at your phone and press volume up to confirm unlock. Once done, disconnect the phone and remove the battery, wait 5 seconds and place the battery back.
Step 4: Do readback again
Once readback done, please extract these images inside your backup for later use:
Code:
sec1.img
seccfg.img
Step 5: Format all + Download to flash the firmware with original scatter file
Switch to Download tab, and choose format all + download to flash the entire phone with the original scatter file named as "MT6761_Android_scatter.txt" - note there's no altunlock at the beginning of filename.
Once flash complete, disconnect the phone.
Step 6: Power on the phone and enable USB debugging, root the phone with MTK Easy SU
[NOTE: DO NOT INSERT ANY SIM CARDS AND YOU MUST SKIP INTERNET CONNECTION]
You can download the MTK Easy SU apk from here : https://github.com/JunioJsv/mtk-easy-su/releases/latest
And Magisk APK from here : https://github.com/topjohnwu/magisk/releases/latest
When you have both MTK Easy Su and Magisk APK installed, please enable the "Run as 64 Bits" option, and tap the hash (#) button to enable root.
Once root complete, we can now re-enable bootloader unlock and restore IMEI.
Step 7: Re-enable bootloader unlock and restore IMEI
Please copy the 7 img files to your phone's internal storage:
Code:
nvcfg.img
nvram.img
proinfo.img
protect1.img
protect2.img
sec1.img
seccfg.img
We assume you copied them to root directory of internal storage (a.k.a. /storage/emulated/0/ )
Then execute these commands on your PC:
Code:
adb shell
su
dd if = / storage / emulated / 0 / nvcfg.img of = / dev / block / bootdevice / by-name / nvcfg
dd if = / almacenamiento / emulado / 0 / nvram.img de = / dev / block / bootdevice / by-name / nvram
dd if = / almacenamiento / emulado / 0 / proinfo.img de = / dev / block / bootdevice / by-name / proinfo
dd if = / storage / emulated / 0 / protect1.img of = / dev / block / bootdevice / by-name / protect1
dd if = / storage / emulated / 0 / protect2.img of = / dev / block / bootdevice / by-name / protect2
dd if = / storage / emulated / 0 / sec1.img of = / dev / block / bootdevice / by-name / sec1
dd if = / storage / emulated / 0 / seccfg.img of = / dev / block / bootdevice / by-name / seccfg
[/CÓDIGO]
Cuando haya terminado, realice un restablecimiento de fábrica para aplicar la restauración de NVRAM.
Mire este video para ver una demostración completa del procedimiento:
[MEDIA = youtube] OgGfv65wT7U [/ MEDIA]
Eso concluye todo el procedimiento de desbloqueo del cargador de arranque, ¡y diviértete modificando este dispositivo!
Créditos:
Woke_World from triple-color company product community
diplomatic for his MTK-SU Exploit and simplified utility called JunioJsv
topjohnwu for MagiskSU
[/QUOTE]
I have read that the security patch 05/01/2021 in android 10 does not allow the use of MTK easy SU (Step 6).
Carrying out the steps prior to that step, (step 6), is it possible to use the application even with the latest security patch installed?
Click to expand...
Click to collapse

after Step 5 your phone is downgraded to android 9

hikari_calyx said:
after Step 5 your phone is downgraded to android 9
Click to expand...
Click to collapse
ok thank you very much, sorry for the ignorance, I am new to these topics and I want to learn without bricking my phone,

Awesome !. i used tis procedure to restore my lost imei numbers and s/n. and it worked !

@hikari_calyx
Question any chance we could get this to work on nokia 2.3?
They both use Mediatek MT6761 Helio A22

Just managed to unlock the bootloader on my phone
Is it safe to connect to the Internet and insert a sim after completing the tutorial, and/or is there any way I can get about permanently rooting the phone?

Please make a tutorial on how to unlock the bootloader of Nokia 2.1 with Android 10 update.

Install GERDA OS on nokia 8110 4g

Hello xdas,
I'm an android user that started customization with my old (and beloved) galaxy s2, and then I installed custom rom on every smartphone I get.
My girlfriend gave me a present last april, a nokia 8110 because she knows that I love to custom devices.
But I have a problem (and I can't find solution on banana hackers's guides)
I want to install gerda on this feature phone and so I'm following this guide:
https://gerda.tech/#h1.4_install
I installed wallace lite, I dowloaded on my pc (win 10 home 20H2) the adb pckg. From this directory (the adb) I start the PowerShell and I give this command
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery-backup.img bs=2048
.
I have the debug mode activated, the phone rooted (and obviuosly connected the pc) but I get this error message:
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery-backup.img bs=2048
dd : Termine 'dd' non riconosciuto come nome di cmdlet, funzione, programma eseguibile o file script. Controllare
l'ortografia del nome o verificare che il percorso sia incluso e corretto, quindi riprovare.
In riga:1 car:1
+ dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery-back ...
+ ~~
+ CategoryInfo : ObjectNotFound: (dd:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Did anyone get the same problem?
Could you help me to find a way to go on?

ops, I'm sorry...
this sentence
Termine 'dd' non riconosciuto come nome di cmdlet, funzione, programma eseguibile o file script. Controllare
l'ortografia del nome o verificare che il percorso sia incluso e corretto, quindi riprovare.
In riga:1 car:1
means...
The term 'dd' is not recognized as a cmdlet, function, executable program or script file name. to check spelling the name or verify that the path is included and correct, then try again. Per row: 1 car: 1

You have to run any of Androd's Linux commands in a Linux shell started by ADB
Code:
adb shell "dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery-backup.img bs=2048"

yes, now it works!
thank you... now I'm from xubuntu.

[GUIDE] Dual-Boot for any Android Device

Code:
disclaimer
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
*/
Hello
This Guide to make Dual-Boot for any android device that can be useful. It allows two Android os installed at the same time and switch between them almost as easily as a simple reboot.
Spoiler: General information
This done by creating a new system partition using Parted (shrink userdata partition and creat the new system partition)
To Boot from the new system partition: change the name of the new system partition to "system" and the name of old system partition to any name e.g. "system-b"
To Boot from the old system partition: change the name of the old system partition to "system" and the name of new system partition to any name e.g. "system-b"
Dual boot for P20 lite - demonstration video (I am using SHRP RECOVERY (like TWRP) with tweaks to change boot partition easily, instead of writing terminal commands. This a video shows the dual boot process)
Requirements​
TWRP
Parted (attached arm and arm64, unzip the file)
Latest fastboot and ADB commands installed
Backup all your data because you will make a factory reset and format data partition
Steps:​
Boot to TWRP
Run the following commands
Code:
adb push /path/to/parted /sbin/parted
adb shell
chmod 777 /sbin/parted
parted /dev/block/mmcblk0
p free
note: parted /dev/block/xxxxx according do your device
3- it will show the list of partition "save this you may use it later". remember the number of old system partition which is in my case "52"
{
"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"
}
4- remove "userdata" partition which in my case number 59 using the following command
Code:
rm 59
5- create the new system partition (partition number 59 in my case ) using the following command
Code:
mkpart name fs_type start end
name: name of new partition e.g "system-b"
fs_type: file system type e.g "ex4"
start: the end value in MB of the previous partition, in my case "7153MB"
end: equal to start + size where size will be the size of the target partition. in my case in need 4GB partition so end=7153MB + 4GB =11153MB
In my case I'll type:
Code:
mkpart system-b ext4 7153MB 11153MB
set 59 msftdata on
6- create the "userdata" partition (partition number 60 in my case, start= 11153MB )
In my case I'll type:
Code:
mkpart userdata ext4 11153MB 31.3GB
set 60 msftdata on
7- get the new partition list
Code:
p free
8- exit
Code:
quit
9- format userdata and the new system partition using "mkfs.type /dev/block/mmcblk0pxx" (in my case partition number 59 and 60). you may need to reboot before doing that or make factory reset using your recovery
Code:
adb push /path/to/mkfs.ext4 /sbin/mkfs.ext4
adb shell
chmod 777 /sbin/mkfs.ext4
mkfs.ext4 /dev/block/mmcblk0p59
mkfs.f2fs /dev/block/mmcblk0p60
10- To Boot from your new system partition > boot to twrp and run the following command
Code:
adb push /path/to/parted /sbin/parted
adb shell
chmod 777 /sbin/parted
parted /dev/block/mmcblk0
name 52 system-b
name 59 system
or from TWRP terminal write the following
Code:
parted -s /dev/block/mmcblk0 name 52 system-b
parted -s /dev/block/mmcblk0 name 59 system
change the number 52 and 59 according to your partition list (in my case 59: new system partion, 52 old system partition ). Then reboot TWRP and flash your new android os
11- To Boot from your old system partition > boot to twrp and run the following command
Code:
adb push /path/to/parted /sbin/parted
adb shell
chmod 777 /sbin/parted
parted /dev/block/mmcblk0
name 59 system-b
name 52 system
or from TWRP terminal write the following
Code:
parted -s /dev/block/mmcblk0 name 59 system-b
parted -s /dev/block/mmcblk0 name 52 system
change the number 52 and 59 according to your partition list (in my case 59: new system partion, 52 old system partition ). Then reboot
-------------------------------------------------------
You may create flashable zip or modify TWRP file to switch between the two android os easily[/CODE]

You can also create two userdata profiles such as here
https://forum.xda-developers.com/t/a-simple-way-to-kind-of-dual-boot-an-android.4176415/

Did you get what you described on your phone and would you like to show it in a video?

ze7zez said:
Did you get what you described on your phone and would you like to show it in a video?
Click to expand...
Click to collapse
Yes. It is worked on my phone Huawei P20 lite ... I am using SHRP RECOVERY (like TWRP) with tweaks to change boot partition easily, instead of writing terminal commands. This a video shows the dual boot process

Flashable zip Files to switch easily between the two android os (you must have "System" and "System-b" partitions, other names not accepted)
Flash "Active-New-System-partition-arm64-v2" to active the new system partition
Flash "Active-Default-System-partition-arm64-v2" to active the default system partition

Anyone else tried this? I'm courious how safe this is... Someone warned me it's very easy to brick device

Abdelhay.ali said:
Code:
disclaimer
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
*/
Hello
This Guide to make Dual-Boot for any android device that can be useful. It allows two Android os installed at the same time and switch between them almost as easily as a simple reboot.
Spoiler: General information
This done by creating a new system partition using Parted (shrink userdata partition and creat the new system partition)
To Boot from the new system partition: change the name of the new system partition to "system" and the name of old system partition to any name e.g. "system-b"
To Boot from the old system partition: change the name of the old system partition to "system" and the name of new system partition to any name e.g. "system-b"
Dual boot for P20 lite - demonstration video (I am using SHRP RECOVERY (like TWRP) with tweaks to change boot partition easily, instead of writing terminal commands. This a video shows the dual boot process)
Requirements​
TWRP
Parted (attached arm and arm64, unzip the file)
Latest fastboot and ADB commands installed
Backup all your data because you will make a factory reset and format data partition
Steps:​
Boot to TWRP
Run the following commands
Code:
adb push /path/to/parted /sbin/parted
adb shell
chmod 777 /sbin/parted
parted /dev/block/mmcblk0
p free
note: parted /dev/block/xxxxx according do your device
3- it will show the list of partition "save this you may use it later". remember the number of old system partition which is in my case "52"
View attachment 5772225
4- remove "userdata" partition which in my case number 59 using the following command
Code:
rm 59
5- create the new system partition (partition number 59 in my case ) using the following command
Code:
mkpart name fs_type start end
name: name of new partition e.g "system-b"
fs_type: file system type e.g "ex4"
start: the end value in MB of the previous partition, in my case "7153MB"
end: equal to start + size where size will be the size of the target partition. in my case in need 4GB partition so end=7153MB + 4GB =11153MB
In my case I'll type:
Code:
mkpart system-b ext4 7153MB 11153MB
set 59 msftdata on
6- create the "userdata" partition (partition number 60 in my case, start= 11153MB )
In my case I'll type:
Code:
mkpart userdata ext4 11153MB 31.3GB
set 60 msftdata on
7- get the new partition list
Code:
p free
View attachment 5775221
8- exit
Code:
quit
9- format userdata and the new system partition using "mkfs.type /dev/block/mmcblk0pxx" (in my case partition number 59 and 60). you may need to reboot before doing that or make factory reset using your recovery
Code:
adb push /path/to/mkfs.ext4 /sbin/mkfs.ext4
adb shell
chmod 777 /sbin/mkfs.ext4
mkfs.ext4 /dev/block/mmcblk0p59
mkfs.f2fs /dev/block/mmcblk0p60
10- To Boot from your new system partition > boot to twrp and run the following command
Code:
adb push /path/to/parted /sbin/parted
adb shell
chmod 777 /sbin/parted
parted /dev/block/mmcblk0
name 52 system-b
name 59 system
or from TWRP terminal write the following
Code:
parted -s /dev/block/mmcblk0 name 52 system-b
parted -s /dev/block/mmcblk0 name 59 system
change the number 52 and 59 according to your partition list (in my case 59: new system partion, 52 old system partition ). Then reboot TWRP and flash your new android os
11- To Boot from your old system partition > boot to twrp and run the following command
Code:
adb push /path/to/parted /sbin/parted
adb shell
chmod 777 /sbin/parted
parted /dev/block/mmcblk0
name 59 system-b
name 52 system
or from TWRP terminal write the following
Code:
parted -s /dev/block/mmcblk0 name 59 system-b
parted -s /dev/block/mmcblk0 name 52 system
change the number 52 and 59 according to your partition list (in my case 59: new system partion, 52 old system partition ). Then reboot
-------------------------------------------------------
You may create flashable zip or modify TWRP file to switch between the two android os easily[/CODE]
Click to expand...
Click to collapse
Is only GSI flashing possible with this method or any custom ROM?

It should work with any GSI/ROM..... It just change the name of the system partition.
Lord Sithek said:
Is only GSI flashing possible with this method or any custom ROM?
Click to expand...
Click to collapse

Abdelhay.ali said:
It should work with any GSI/ROM..... It just change the name of the system partition.
Click to expand...
Click to collapse
Well, I've tried that procedure on my secondary device but something got screwed and I ended up with the need of EDL flash. Maybe I made a mistake, idk, but it's definitely dangerous

Lord Sithek said:
Anyone else tried this? I'm courious how safe this is... Someone warned me it's very easy to brick device
Click to expand...
Click to collapse
Lord Sithek said:
Well, I've tried that procedure on my secondary device but something got screwed and I ended up with the need of EDL flash. Maybe I made a mistake, idk, but it's definitely dangerous
Click to expand...
Click to collapse
This can happen

Abdelhay.ali said:
Code:
disclaimer
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
*/
Hello
This Guide to make Dual-Boot for any android device that can be useful. It allows two Android os installed at the same time and switch between them almost as easily as a simple reboot.
Spoiler: General information
This done by creating a new system partition using Parted (shrink userdata partition and creat the new system partition)
To Boot from the new system partition: change the name of the new system partition to "system" and the name of old system partition to any name e.g. "system-b"
To Boot from the old system partition: change the name of the old system partition to "system" and the name of new system partition to any name e.g. "system-b"
Dual boot for P20 lite - demonstration video (I am using SHRP RECOVERY (like TWRP) with tweaks to change boot partition easily, instead of writing terminal commands. This a video shows the dual boot process)
Requirements​
TWRP
Parted (attached arm and arm64, unzip the file)
Latest fastboot and ADB commands installed
Backup all your data because you will make a factory reset and format data partition
Steps:​
Boot to TWRP
Run the following commands
Code:
adb push /path/to/parted /sbin/parted
adb shell
chmod 777 /sbin/parted
parted /dev/block/mmcblk0
p free
note: parted /dev/block/xxxxx according do your device
3- it will show the list of partition "save this you may use it later". remember the number of old system partition which is in my case "52"
View attachment 5772225
4- remove "userdata" partition which in my case number 59 using the following command
Code:
rm 59
5- create the new system partition (partition number 59 in my case ) using the following command
Code:
mkpart name fs_type start end
name: name of new partition e.g "system-b"
fs_type: file system type e.g "ex4"
start: the end value in MB of the previous partition, in my case "7153MB"
end: equal to start + size where size will be the size of the target partition. in my case in need 4GB partition so end=7153MB + 4GB =11153MB
In my case I'll type:
Code:
mkpart system-b ext4 7153MB 11153MB
set 59 msftdata on
6- create the "userdata" partition (partition number 60 in my case, start= 11153MB )
In my case I'll type:
Code:
mkpart userdata ext4 11153MB 31.3GB
set 60 msftdata on
7- get the new partition list
Code:
p free
View attachment 5775221
8- exit
Code:
quit
9- format userdata and the new system partition using "mkfs.type /dev/block/mmcblk0pxx" (in my case partition number 59 and 60). you may need to reboot before doing that or make factory reset using your recovery
Code:
adb push /path/to/mkfs.ext4 /sbin/mkfs.ext4
adb shell
chmod 777 /sbin/mkfs.ext4
mkfs.ext4 /dev/block/mmcblk0p59
mkfs.f2fs /dev/block/mmcblk0p60
10- To Boot from your new system partition > boot to twrp and run the following command
Code:
adb push /path/to/parted /sbin/parted
adb shell
chmod 777 /sbin/parted
parted /dev/block/mmcblk0
name 52 system-b
name 59 system
or from TWRP terminal write the following
Code:
parted -s /dev/block/mmcblk0 name 52 system-b
parted -s /dev/block/mmcblk0 name 59 system
change the number 52 and 59 according to your partition list (in my case 59: new system partion, 52 old system partition ). Then reboot TWRP and flash your new android os
11- To Boot from your old system partition > boot to twrp and run the following command
Code:
adb push /path/to/parted /sbin/parted
adb shell
chmod 777 /sbin/parted
parted /dev/block/mmcblk0
name 59 system-b
name 52 system
or from TWRP terminal write the following
Code:
parted -s /dev/block/mmcblk0 name 59 system-b
parted -s /dev/block/mmcblk0 name 52 system
change the number 52 and 59 according to your partition list (in my case 59: new system partion, 52 old system partition ). Then reboot
-------------------------------------------------------
You may create flashable zip or modify TWRP file to switch between the two android os easily[/CODE]
Click to expand...
Click to collapse
look what i got
edit: appearently any name u put when u use the command mkpart doesn't register or smtg idk what's wrong tbh
edit2: i found a solution just do "name 38(in my case) userdata" and it'll name the partition

i accidentally hardbricked my xiaomi pad 5 by deleting the dbg partition (could not find any information about it online), can anybody help?

Does not the new system-b alias requires its own data partition? The new system image may not be compatible with data partition.
New Android OS requires its own data. Above approach will share the /data among different system images which is something not useful.

dual boot is nonsense because one can't share same userdata partition between ROMs

alecxs said:
dual boot is nonsense because one can't share same userdata partition between ROMs
Click to expand...
Click to collapse
Yes you can but it does not work with all apps.
I got an app in the Dualboot I made for Oneplus 6/7 series and had an app where you can choose which apps should be shared on both roms.