Guide flash rom Nokia X6 to Global Rom Nokia X6.1
All file dowload for guide
Link dowload aplication this guides:
Link dowload patched boot:
Link dowload rom Cook nokia X6:
Link dowload Rom stock global DRG-229D-0-00WW-B01.nb0 edited .MLF file:
Link dowload rom stock global DRG-229D-0-00WW-B01.nb0
Link dowload rom stock china OSTLA_DRG-TA-1099-nokia-X6-221F-0-00CN-B03_001.zip:
Update security (2018.6)
DRG-229D-boot_patched.img
Update security (2018.7)
C1N-238A-0-00CN-B01-patched_boot.img
Update security (2018.8)
B2N-2420-0-00CN-B01-patched_boot.img
or
B2N-242C-0-00CN-B02-patched_boot.img
B2N-242F-00CN-B01_patched_boot.img for 09/2018
Video tut https://www.youtube.com/watch?v=5T0GXo5FOrc&t=13s
1. Unlock bootloader
Get unlock key IsignatureI:
Bootloader unlock key is an encrypted file containing the signatures which are required to unlock the bootloader. You can use our bootloader key service to buy the unlock key. Price for the unlock key is $5 per request. You will need to send the following information:
• Your IMEI number IDial *#06# to get itI
• Your phone serial IFind it in Settings - About phone - StatusI
• https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
Boot into bootloader mode:
Now boot your Nokia smartphone to the bootloader Ior downloadI mode. Follow these steps for bootloader mode:
1. Turn off your phone.
2. Connect the USB cable to the device
3. Press and hold Volume Down + Power key together till you reach the screen reads that reads “Download mode”.
Alternatively, you can also use the command adb reboot bootloader in the adb interface to reboot the phone to bootloader mode.
Unlock the bootloader:
The final step is to connect the Nokia phone to the PC and send the bootloader unlock command along with the unlock key which you acquired earlier. Here are the details:
1. Ensure that your Nokia smartphone is detected by fastboot by running:
fastboot devices
2. If your device is detected, then send the following command:
Note: Replace UnlockFile.bin with the name or full path of your unlock file.
fastboot flash unlock UnlockFile.bin
3. Now send the command to unlock the bootloader.
fastboot oem unlock-go
4. On some Nokia devices, you will receive a bootloader unlock confirmation prompt. It looks like the following. Use the volume keys to select “Unlock the bootloader” and then press the power key to confirm.
5. Fastboot flash unlock unlockfile.bin
6. Fastboot flashing unlock_critical
2. Root Nokia 2018
Reboot your phone and download Magisk Manager
Copy Magisk Manager and Magisk-v17.1 to folder download on phone.
Install Magisk Manager
Make boot file from Magisk Manager
• Press Install - Install - Patch Boot Image File, and select your stock boot image fileMagisk Manager will now patch your boot image, and store it in /Internal Storage//Download/patched_boot.img
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
• adb pull /sdcard/Download/patched_boot.img
• Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
• And download file boot img for your phone.
• Now start
• OK
•
Then add the Magisk zip as module. The phone will patch the boot image with Magisk.
Reboot your phone when finished.
3. Change skuid to worldwire Nokia
Dowload terminal emulator to your phone
Dowload HxD Hex Editor to PC
Use a terminal emulator
$ su
IAccept root permission on your phoneI
# dd if=/dev/block/bootdevice/by-name/deviceinfo of=/storage/emulated/0/deviceinfo.img
Use a Hex Editor to open deviceinfo.img placed at root directory of internal storage.
Save it as deviceinfo_mod.img.
Copy it to internal storage if you modify it on a PC, then execute these commands with a terminal emulator or adb shell:
$ su
# dd if=/storage/emulated/0/deviceinfo_mod.img of=/dev/block/bootdevice/by-name/deviceinfo
Reboot your phone, reflash global firmware
4. Flash firmware by ost la.
Dowload OST LA 6.04
And Dowload nb0_tools_FIH_Mobile_v3.4, ROM global 6.1 for nokia X6.
Unpack file DRG-229D-0-00WW-B01.nb0
Search file XXXX. Mlf opent it is note
Edit 0x60000 -- 0x20000
x160 --x60
0x0004 - - 0x0001
Save it.
Opent OST LA 6.04 and flash rom
My phone is not detected in fastboot mode in pc. How can I fix it? Can you guide me properly? Thanks.
iamshojib said:
My phone is not detected in fastboot mode in pc. How can I fix it? Can you guide me properly? Thanks.
Click to expand...
Click to collapse
you try start cmd is Windows+X > windows powershell (admin) and install OST LA 6.04 make sure your pc have enough driver your phone
My phone is not rooted properly. I tried but when I check the root. it showed your phone is not rooted properly. I can not use the terminal editor. I need to root it again. How can I unroot it again? and then again root it?
Hi. Im stuck at flashing global rom.
OST LA is getting stuck at system_a flashing partition.
Please advice.
{
"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"
}
Sent from my G8142 using Tapatalk
Hi.
OST LA stops flashing midway @ system
Please help
Sent from my G8142 using Tapatalk
techdroidsg said:
Hi. Im stuck at flashing global rom.
OST LA is getting stuck at system_a flashing partition.
Please advice.View attachment 4594887
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
you can correct all step for instruction ? your device rooted? and now phone can go to bootload mode?
iamshojib said:
My phone is not rooted properly. I tried but when I check the root. it showed your phone is not rooted properly. I can not use the terminal editor. I need to root it again. How can I unroot it again? and then again root it?
Click to expand...
Click to collapse
You can reset all data on obout phone. then you can try again. Or you can uninstall magicks manager.apk
cuongga311 said:
you can correct all step for instruction ? your device rooted? and now phone can go to bootload mode?
Click to expand...
Click to collapse
Hi.
Yes followed all instructions.
It can go bootloader mode.
Ost la will start flashing and then it stops half way while flashing system
Error message adb_cmd
Just an update.
I can flash the china version fully on OST.
It became a downgrade as i was having a higher version.
But i tried flashing WW firmware again. Same issue.
Stuck when flashing system.
Do you have any other WW firmware i can try?
Out of all your firmwares, there is only one which can recover back my phone from no firmware.
Recap :
Original Firmware version : 00CN_2_37e
Rooted it and changed skuid to WW
Flashed WW firmware and failed as stuck at flashing system.
Flashed CN firmware
Current Version : 00CN_2_29E
Rooted phone again.
Checked the skuid. Its the same (WW)
Flashed WW firmware again
Same issue.
Flashed back CN firmware
Its ok.
Solved it myself by patching the global firmware.
Now the phone is in 6.1 global firmware instead of 6x CN.
Finally successful.
Thanks anyway.
You provided great help by posting this guide.
techdroidsg said:
Its ok.
Solved it myself by patching the global firmware.
Now the phone is in 6.1 global firmware instead of 6x CN.
Finally successful.
Thanks anyway.
You provided great help by posting this guide.
Click to expand...
Click to collapse
You can test some rom cook for Nokia X6
https://www.youtube.com/watch?v=TdTOWKhB8lQ&t=1s
hi
my phone is nokia x6 chinese stuck at nokia logo screen after flashing boot already opened bootloader , not rooted and i can not access to recovery , have any way to solve this?
thanks
azama02 said:
hi
my phone is nokia x6 chinese stuck at nokia logo screen after flashing boot already opened bootloader , not rooted and i can not access to recovery , have any way to solve this?
thanks
Click to expand...
Click to collapse
You dont worry, you go to download mode -> run command on cmd (OST LA) fastboot-android boot B2N-2420-0-00CN-B01-patched_boot.img
After your phone will correct boot.
B2N-2420-0-00CN-B01-patched_boot.img is your stock img file boot your phone.
techdroidsg said:
Hi. Im stuck at flashing global rom.
OST LA is getting stuck at system_a flashing partition.
Please advice.View attachment 4594887
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
This error, you go to download mode, on PC opent cmd on folder OST LA: Fastboot-android flash unlock unlockfile.bin
next command: Fastboot-android flashing unlock_critical
after reboot and go again dowload mode:
Try command: fastboot-android oem device-info
If unlock_critical have value is true You can go OST LA flash again. Good luck
techdroidsg said:
Its ok.
Solved it myself by patching the global firmware.
Now the phone is in 6.1 global firmware instead of 6x CN.
Finally successful.
Thanks anyway.
You provided great help by posting this guide.
Click to expand...
Click to collapse
could you explain to me how patching the global firmware?
azama02 said:
could you explain to me how patching the global firmware?
Click to expand...
Click to collapse
If fatboot patched boot.img then you stuck boot logo nokia.
You dont worry, you go to download mode -> run command on cmd (OST LA) fastboot-android boot B2N-2420-0-00CN-B01-patched_boot.img
After your phone will correct boot.
B2N-2420-0-00CN-B01-patched_boot.img is your stock img file boot your phone.
Hey guys , i have the same phone bought online, if i flash global firmware , the other lte bands with be active?
florijak2013 said:
Hey guys , i have the same phone bought online, if i flash global firmware , the other lte bands with be active?
Click to expand...
Click to collapse
All version nokia x6 can used 4G lte after flash rom Nokia X6.1 (because Nokia X6.1 global)
I live in europe, italy, and i bought the phone from honk kong in some i have 4g in other nope, and i writed to nokia and they tell me your phobe is designed for the chinese market how to unlock band 20 lte, it is enough to only flash the global rom?
Related
How to Install TWRP:
Note: that version is UNOFFICIAL TWRP-3.3.0-0524
.Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here https://devsjournal.com/usb-drivers-...d-devices.html
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here https://devsjournal.com/download-min...boot-tool.html
Pre-Requisite 3
Your device needs this with unlocked bootloader
if it is not unlocked do the tutorial to unlock HERE
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
------------------------------------------------
1) Download TWRP: recovery-TWRP-3.3.0-0524-LENOVO_Z5PRO_GT-CN-wzsx150.img
2) After getting the TWRP file put it in the same ADB folder
3) Now start the phone in bootlader by doing this:
Connect the phone to the PC
Start the Minimal ADB & Fastboot program from the PC
On the PC screen, type:
adb reboot bootloader
(A request may appear on the phone screen with permission of USB debugging, accept it)
The phone will now restart in Bootloader mode.
4) Now that you are in bootloader mode, from the PC, from the screen
Minimal ADB and Fastboot type:
fastboot flash recovery recovery-TWRP-3.3.0-0524-LENOVO_Z5PRO_GT-CN-wzsx150.img
Sending 'recovery' (98304 KB) OKAY [ 5.970s]
Writing 'recovery' OKAY [ 0.539s]
Done !
---------
.How to Install Root Magisk:
{
"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"
}
Done !
Credits:
Maker: wzsx150
Developer Team: LR.Team
Is there any issues related to this recovery?
firemax13 said:
Is there any issues related to this recovery?
Click to expand...
Click to collapse
I had no problem with this recovery
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
BlueIce84 said:
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
Click to expand...
Click to collapse
Have the same scenario as you but I haven't done the tutorial yet as I read your post and I got concerned. Have you fix you issue? Is it safe to do this tutorial?
No solution so far. No twrp and no root
Now I have flashed the original rom with ZUI 10. Works well and updated to ZUI 11.
luigi0824 said:
Have the same scenario as you but I haven't done the tutorial yet as I read your post and I got concerned. Have you fix you issue? Is it safe to do this tutorial?
Click to expand...
Click to collapse
I've read somewhere that you need to flash vbmeta.img if verified boot is enabled, however I couldn't find the correct img to flash anywhere. Maybe if we ask someone that has the phone already rooted.
Can anyone post wzsx150's newest TWRP 3.3.1 from October 4? It's in this thread but the download link is for registered users only. I can't sign up for a Club Lenovo account.
BlueIce84 said:
No solution so far. No twrp and no root
Now I have flashed the original rom with ZUI 10. Works well and updated to ZUI 11.
Click to expand...
Click to collapse
What method would you follow to install the stock rom, like you, it comes with the bootloader unlocked by the seller and I don't know how to flash stock rom
Use this guide:
https://forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945
carlshark said:
Can anyone post wzsx150's newest TWRP 3.3.1 from October 4? It's in this thread but the download link is for registered users only. I can't sign up for a Club Lenovo account.
Click to expand...
Click to collapse
I gave up on clublenovo. They require SMS authentication to post so even when you log in you can't post and download. TWRP 3.3.1 is also available from 4PDA. That's what I used.
I was able to flash the TWRP 3.3.1 but i cant root nor i cant flash anything as the folders inside the sdcard directory is showing in weird names
luigi0824 said:
I was able to flash the TWRP 3.3.1 but i cant root nor i cant flash anything as the folders inside the sdcard directory is showing in weird names
Click to expand...
Click to collapse
You need to decrypt the internal storage.
normally this is done by entering to ping code to unlock the phone in TWRP on start up.
thorvall said:
You need to decrypt the internal storage.
normally this is done by entering to ping code to unlock the phone in TWRP on start up.
Click to expand...
Click to collapse
Will I lose any data if I decrypt my phone? And where do I find that pin code?
luigi0824 said:
Will I lose any data if I decrypt my phone? And where do I find that pin code?
Click to expand...
Click to collapse
Its the pin code you use to open the phone.
And enabling does not remove data, but it does give twrp read/write permission
Is it possible to implement support for OTA updates through TWRP?
BlueIce84 said:
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
Click to expand...
Click to collapse
i had the same issue and discover a solution
1) you have to manually go to your phone after you finish the flash below. DO NOT cmd fastboot reboot as it will flash stock
recovery
a) fastboot flash recovery twrp.img ( i rename the tweak recovery file to twrp.img)
b) http://4pda.ru/forum/index.php?showtopic=973179&st=0
(tweak recovery version 3.31)
2) after flash quickly go to your phone fastboot mode ( reminder again: do not tyoe fastboot reboot after flash successful appear in cmd)
3) manually select recovery , select english then select reboot and TWRP will appear
issues
1) i cannot manually tweak recovery via phone ( power +volume down ) as stock recovery will appear again.
A) so you need to go your PC to redo flash recovery again
B) i did a back up and redo PC flassh recovery again and mine files are stored successful
c) there is no install root in TWRP
D) about backup...
.best to back up via OTA-USB. pixel GCI crash ( QUALCOMM CRASH DUMP MODE ) my phone and my restore
file was missing as TWRP rename the restore file. spent one hour it so decide to do stock rom
current
a) I have not flash any rom yet and my original ANTUTU benchmark hovers around 300000 to 350000 based on vendor custom global rom
b) my phone model is 8gb 128gb android version 9 and lenovo version 11.0.084
c) updatess and NFC not supported
d) i opt not too root
e) bootloader still unlock
REQUEST...
would appreciate a ROM recommendation
a) have anyone flash a rom (not china stock rom) wirh an antutu beachmark abve 400000 ?
from a novice... after 2 weeks i can finally flash tweak recovery from the phonE.
about flashing stock rom..
i opt for stock rom and my antutu hovers around 409000 to 418000. from LENOVO app centre you can install play store
butterx2341 said:
i had the same issue and discover a solution
1) you have to manually go to your phone after you finish the flash below. DO NOT cmd fastboot reboot as it will flash stock
recovery
a) fastboot flash recovery twrp.img ( i rename the tweak recovery file to twrp.img)
b) http://4pda.ru/forum/index.php?showtopic=973179&st=0
(tweak recovery version 3.31)
2) after flash quickly go to your phone fastboot mode ( reminder again: do not tyoe fastboot reboot after flash successful appear in cmd)
3) manually select recovery , select english then select reboot and TWRP will appear
issues
1) i cannot manually tweak recovery via phone ( power +volume down ) as stock recovery will appear again.
A) so you need to go your PC to redo flash recovery again
B) i did a back up and redo PC flassh recovery again and mine files are stored successful
c) there is no install root in TWRP
D) about backup...
.best to back up via OTA-USB. pixel GCI crash ( QUALCOMM CRASH DUMP MODE ) my phone and my restore
file was missing as TWRP rename the restore file. spent one hour it so decide to do stock rom
current
a) I have not flash any rom yet and my original ANTUTU benchmark hovers around 300000 to 350000 based on vendor custom global rom
b) my phone model is 8gb 128gb android version 9 and lenovo version 11.0.084
c) updatess and NFC not supported
d) i opt not too root
e) bootloader still unlock
REQUEST...
would appreciate a ROM recommendation
a) have anyone flash a rom (not china stock rom) wirh an antutu beachmark abve 400000 ?
from a novice... after 2 weeks i can finally flash tweak recovery from the phonE.
about flashing stock rom..
i opt for stock rom and my antutu hovers around 409000 to 418000. from LENOVO app centre you can install play store
Click to expand...
Click to collapse
If you boot your ZUI system, your twrp will be overwritten by a stock recovery.
However if you flash magisk, your twrp won't be overwritten anymore. If you want to preserve your twrp after rebooting on ZUI, you need to flash magisk.
whatever I do.. the twrp wont be installed (let alone the root/magisk). ADB does say the twrp is flashed... but it will always boot to or the bootloader.. or the system (not the lenovo recovery or twrp recovery). Quiet frustrating... what can I do? Want this boy rooted!
Edit: done. The twrp linked in the tutorial is not correct use this one: https://drive.google.com/file/d/13mt0RLmT83BHSUBpH-J7EhaeZQ-MPYUu/view
That worked!
I want to unlock my bootloader but the site where you request the image file for unlocking it wont accept my IMEI1.. any idea guys?
Avoid and pass by a fool and a madman
How to root Black Shark 2 Global (short way)
Avoid and pass by a fool and a madman
Avoid and pass by a fool and a madman
A few guide to fix your bricked or bad-conditioned phone
Avoid and pass by a fool and a madman
Avoid and pass by a fool and a madman
Thank you for this great guide, I'm sure it will help a lot of people.
The update file I used in my post was from this link, I just rename to make it easier to update.
KM7 said:
Thank you for this great guide, I'm sure it will help a lot of people.
The update file I used in my post was from this link, I just rename to make it easier to update.
Click to expand...
Click to collapse
Wow, thank you very much for the full name link. I think I found something great. I think, now, you can try to root directly on latest firmware, and save lots of time. I will test it... and post it soon.
How to download the latest update as full-sized, factory stock roms
Under Construction....
Sorry for deleting this post.
BS team never open the stock rom download site. I think we can build one, but I couldn't gather enough information.
I was able to find all my own factory stock rom OTAs including the latest, but not others due to lack of information. Further problem is that after I share how to find & download your own latest factory stock rom directly, that site is really slowed down now. Maybe lots read it, download, never share, or due to other reason... The region and ota link is enough to build the stock rom download site, but now the server is slowed down, no one shares... so I stop here.
I will re-open this if I could gather enough information.
wga0 said:
Hey guys, I realized that I neither need to provide a detailed explain nor can.
I can't attach any files, pictures, links... even I can write now. There are too much restriction.
(I must delete all links I included here You can search it in xda-dev forum)
So, here's the shortest and fastest way to root your black shark 2 global.
If anybody want a long detail, more safe way, let me know. I will add later if possible.
If something goes wrong, end to brick your phone, you can always revive that with safe way.
As you know, though safety is increased greatly (Thanks very much to a/b slot system),
but accident can happen anytime. It's on your own responsibility, at your own risk.
Pre-Requirements:
adb/fastboot drivers, Magisk Manager latest version, global OTA1 update
(I skip all the details of 3 firmware regions, payload_dumper, twrp, all others)
(Backup your data. It requires several factory reset)
Steps (also skip all detail. I wish you familiar with adb, fastboot, a/b slot)
1. Unlock the bootloader
1) fastboot oem bs2_unlock (Thanks greatly to Bave Lee)
2) fastboot oem bs2_unlock_critical (I'm not certain this is mandatory, I just do it at first)
2. flash the global OTA1 update and reboot
1) find and set active your not using slot
fastboot getvar all
fastboot set_active x
2) flash the global OTA1 images to that slot
fastboot flash partition_x partition.img (flash all of it, not partially)
fastboot reboot (It will be reboot again to do factory reset, than will boot successfully)
3. Patch the boot.img with Magisk Manager and flash it
Now, you have a working old version boot image. Patch it, flash it and reboot
4. Backup the latest, your own boot.img
Now, your phone is rooted with old version. Backup your original latest boot image
1) adb shell
su
dd if=/dev/block/bootdevice/by-name/boot_x(your using_latest slot) of=...(any folder you prefer)/boot.img
2) copy the boot.img to your PC (with adb pull or mtp)
5. patch your own latest boot.img
1) Set back the active slot to your original slot, reboot
2) do factory reset (because of using OTA1, OTA2 update request will be remained to your current slot)
3) push the magisk manager, boot.img again and repeat the job (patch, pull out, reboot, flash and reboot again)
6. Now, you have the latest updated, rooted phone with stock & modified boot image
7. Don't forget to backup all your stock ROM before doing anything!!
{
"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"
}
If you done well, you can check the root status. It's rooted with magisk systemless root, all function's normal.
And be careful. Don't share the patched or stock boot image directly. There's multiple global version.
This is the latest version from my own black shark 2 global. It definitely different from yours.
If you flash different region version, your phone will be bricked. That's why I didn't share it and write this long method.
(If anyone want, I will explain details later with more safe way, what I did. But It's quite long way, takes long time)
Click to expand...
Click to collapse
Here is my region skyw1991010Os00mp5,can u help me with this?
Avoid and pass by a fool and a madman
Flauros7 said:
Here is my region skyw1991010Os00mp5,can u help me with this?
Click to expand...
Click to collapse
you have same region with me,
do you still need the files ? i have magisk rooted boot.img if you want.
Need help
I am successful root my BS2
it run Magsik perfect
but the Build number is SKYW1908301CN00MP6 and wifi does not work, also i cant update build number to Build SKYW1910291CN00MP7
use *#*#1027#*#* to locall update with the
SKYW1907040OS01MP3 Stock Factory Image not work too, it said Error the package unauthorized
can u help me solve this problem,
does the Global OTA 1 boot can fix it?
Can u send me your boot file i cant find it
thank you very much!!!
Avoid and pass by a fool and a madman
The MP7 China OTA update...
IT'S WORKED!!!
thank you very much!
now i'm trying to root new version
exynos 540 said:
you have same region with me,
do you still need the files ? i have magisk rooted boot.img if you want.
Click to expand...
Click to collapse
Hi can you sent me the stock boot image for skw1991010Os00mp5? I really need it.
Hello , Please I need Stock boot.img for this region SKYW1902180OS00MP2 android version 9.
Mustafa9698 said:
Hello , Please I need Stock boot.img for this region SKYW1902180OS00MP2 android version 9.
Click to expand...
Click to collapse
Are you sure your revision SKYW1902180OS00MP2? Isn't it SKYW1904180OS00MP2?
exynos 540 said:
you have same region with me,
do you still need the files ? i have magisk rooted boot.img if you want.
Click to expand...
Click to collapse
Yes bro can u send me the file?
wga0 said:
You mean your revision is SKYW1911010OS00MP5. Right? If you didn't try anything to your roms, you'll have previous revision SKY1909192OS00MP4 at the inactive slot. Here is the factory boot image of it. How to root is similar as above.
Before doing, backup all your data and unlock the bootloader. In this time, unlock_critical is not needed.
1. adb reboot bootloader
2. fastboot getvar current-slot (let's assume it returns b)
fastboot set_active a <- set the opposite slot as active
3. fastboot reboot
After factory reset, this will bring you to previous revision SKYW1909192OS00MP4. Install Magisk Manager and patch the boot image.
4. adb pull /sdcard/Download/patch_boot.img (let's assume you save the image to Download directory)
5. fastboot flash boot_a patch_boot.img <- flash that patched image to same slot (you just set active)
Your phone is now rooted with previous revision. You can backup all of your latest stock rom.
6. adb shell
7. su
8. dd if=/dev/block/bootdevice/by-name/boot_b of=/sdcard/Download/boot.img <- example of boot image. For insurance, just backup all your stock roms.
Now back to your original latest slot, root your own image.
9. fastboot set_active b
and repeat the rooting again with your own roms.
As you know, adb command can be used with USB Debugging, fastboot can be used in bootloader mode.
Or... if you need all of those images, let me know. I will upload full MP4 OTA factory images for your region. You can flash this to your inactive slot and it will fix all problems during updating to MP5 to your active slot.
Click to expand...
Click to collapse
Can u give me the file again because the link is dead?
Boot images, Factory(Full) OTA images for known regions/revisions
Avoid and pass by a fool and a madman
I am not responsible for your actions, but I will try to help.
I'm going to assume you have unlocked bootloader and ADB/Fastboot tools installed.
1. Download latest Magisk and make 2 copies of it. Install one of them on your phone. Change the extension of 2nd from .apk to .zip, then move it to your phone`s storage
2. Download Pitch Black recovery for Redmi 9C
3. Move recovery.img to both your ADB folder (can be found at C:\adb) and phone`s storage
5. Download DM-VERITY, FORCED ENCRYPTION
6. Rename it to enfec.zip and place in phone`s storage
4. Download attached vbmeta.img and place it in your ADB folder
5. Go into fastboot mode
5. On your PC, open cmd-here.exe in adb folder
6. fastboot flash recovery recovery.img
7. fastboot flash vbmeta vbmeta.img
8. fastboot reboot recovery
9. Sometimes recoveries don't work with touchscreen. In this case, flash other region's ROM. To do this, find and download fastboot version of ROM. Unzip it, run flash_all.bat while being in a fastboot mode (this will erase all data). WARNING: DO NOT RUN flash_all_and_lock.bat. THIS WILL LOCK THE BOOTLOADER AND YOU WILL HAVE TO WAIT ANOTHER WEEK!
Next retry again the whole tutorial. You can also use USB-OTG mouse.
10. Navigate to 'Install' section. Check every option except 'Reboot after installation is complete', 'Zip signature verification' and 'Advanced remove of Forced Encryption'. Select recovery image that you previously moved to your storage and install it 'as Recovery'.
11. In recovery, move to 'backup' and make a backup to your SD card (optional, but highly recommended). Usually, it doesn`t work out of the box. Try searching for guides.
12. In the same section install enfec.zip and then Magisk.zip. If you get errors like 'Failed to mount /nv_data', ignore them.
13. Reboot to system, copy external_sd/PBRB/tools -> storage/0/emulated/PBRB/
Done!
How to pass SafetyNet (tested on 05.05.21 dd/mm):
Simply enable MagiskHide. This will only work if you haven`t modified the /system with modules that don`t hide themselves.
If you did heavy modifications, install UniversalSafetyNetFix (USNF) (repo) or install both MagiskHide Props Config (can be found in Magisk`s modules) and USNF. Instructions to installation of Props Config can be found in the README or on the web. Experiment with it, this is device specific.
{
"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"
}
It seems like you are using redmi 9C NFC
I am using redmi 9C Global
Did you tested this recovery on your phone?
I downloaded a recovery from GitHub for redmi 9c flashed it after flashing I flashed vbmeta too but can't boot into recovery
I am currently on global EU ROM 12.0.3 which I flashed yesterday
Before that I was on miui global 12.0.10
I tried to root it with magisk and after flashing magisk patched boot.img flashed vbmeta too
But can't get root access
Before I was on miui global 12.0.8
I rooted with magisk and got root access
In order to get root access I downgraded back to miui 12.0.8 but can't get root access
What should I do now?
It seems like you are using redmi 9C NFC
Click to expand...
Click to collapse
True
I am using redmi 9C Global
Click to expand...
Click to collapse
That doesn`t really matter
Did you tested this recovery on your phone?
Click to expand...
Click to collapse
Yes
I downloaded a recovery from GitHub for redmi 9c
Click to expand...
Click to collapse
Which recovery have you flashed? I provided link to SouceForge, not GitHub
I downloaded a recovery [...] flashed it after flashing I flashed vbmeta too but can't boot into recovery
Click to expand...
Click to collapse
Try fastboot reboot recovery.img
If that doesn`t work, try updating your ADB/Fastboot tools. Just download needed files from any site and place them in your ADB folder.
Also, since this recovery is unofficial port, it is a bit different from original. To boot into recovery, you don`t have to hold power+volume_up untill you see recovery menu. Instead, hold it untill screen goes black.
I tried to root it with magisk and after flashing magisk patched boot.img flashed vbmeta too
But can't get root access
Click to expand...
Click to collapse
From my guide:
No users report bootloops, but in some cases root isn't granted. In this case follow next steps.
Click to expand...
Click to collapse
Before I was on miui global 12.0.8
I rooted with magisk and got root access
In order to get root access I downgraded back to miui 12.0.8 but can't get root access
Click to expand...
Click to collapse
I don`t really get what you say, but there is no need to downgrade/upgrade. If I were you, I would flash latest MIUI, though
What should I do now?
Click to expand...
Click to collapse
Try flashing latest eu MIUI (I can help with that, if you want) and then follow method B) step by step, without making any changes and reading everything that I wrote
Hope this helps!
Can't make a backup as your tutorial because i got an error, and what i need to backup just the 'one' selected from the recobery ? can i skip this step and just install the enfec.zip and then Magisk.zip ?
I am stuck from the step 8 and 9 because i got that error and i have no idea what select from the list of the backup...
Backup is an optional step. I get an error too and I have no idea why.
Seems like it worked very well. but the safetynet failed, should download Magisk v21.4 zip because the newest one failed at the moment to flash it, and if you get an error at the end of flashing the DM-VERITY, FORCED ENCRYPTION it's ok still working anyway. thanks for sharing the post
@0purple
Btw personally skip the step 8 and 9, if you failed to get into recovery with the bottons just try again the step 5,6,7
Knox6 said:
but the safetynet failed, should download Magisk v21.4 zip because the newest one failed at the moment to flash it,
Click to expand...
Click to collapse
Updated the post, try it
I have the European version 12.06 of the redmi 9c. I tried to boot into recovery, but the touch doesn't work in any way, so I can't do anything... help me
i just enabled magisk hide option in magisk manager setting it fixed it
MHaseebpk said:
View attachment 5278627View attachment 5278627i just enabled magisk hide option in magisk manager setting it fixed it
Click to expand...
Click to collapse
does the root work for you? I have the EUropera version 12.0.6 and it doesn't work
sephirot91 said:
does the root work for you? I have the EUropera version 12.0.6 and it doesn't work
Click to expand...
Click to collapse
Yes
MHaseebpk said:
Yes
Click to expand...
Click to collapse
See this
MHaseebpk said:
See this View attachment 5278773
Click to expand...
Click to collapse
how did you do it? I followed the guide perfectly and it doesn't work. On the other hand, with the second method, the pitch recovery touch does not respond to commands
sephirot91 said:
how did you do it? I followed the guide perfectly and it doesn't work. On the other hand, with the second method, the pitch recovery touch does not respond to commands
Click to expand...
Click to collapse
I just followed seconds method and I am on global rom
You should flash global rom and should try again
MHaseebpk said:
I just followed seconds method and I am on global rom
You should flash global rom and should try again
Click to expand...
Click to collapse
Ok thanks, I could try. Do you have a guide to flash the global version? thank you very much
https://c.mi.com/oc/miuidownload/detail?guide=2
is it okay? for flashing rom global
sephirot91 said:
Ok thanks, I could try. Do you have a guide to flash the global version? thank you very much
Click to expand...
Click to collapse
First you need to download angelica global latest (12.0.10) fastboot rom from Here
Download miflash pro english from Here
Extract mi flash pro zip file install mi flash pro and extract angelica global image too in your PC
Now power off you phone
Hold volume down and power button simultaneously for 5 seconds
Your phone will boot into fastboot mode
Now open miflash pro login with your mi account connect your phone
When you will connect your phone your phone will be automatically detected
And miflash pro will recommend you to flash in recovery click on it
Next select package (fastboot rom) which you downloaded and extracted before and select script flash all.bat
Wait for 5 to 6 minutes
Your phone will be flashed
After that setup your phone
Boot again into fastboot mode
Setup adb in your PC
Install mediatek USB vcom drivers
And next follow second method
MHaseebpk said:
First you need to download angelica global latest (12.0.10) fastboot rom from Here
Download miflash pro english from Here
Extract mi flash pro zip file install mi flash pro and extract angelica global image too in your PC
Now power off you phone
Hold volume down and power button simultaneously for 5 seconds
Your phone will boot into fastboot mode
Now open miflash pro login with your mi account connect your phone
When you will connect your phone your phone will be automatically detected
And miflash pro will recommend you to flash in recovery click on it
Next select package (fastboot rom) which you downloaded and extracted before and select script flash all.bat
Wait for 5 to 6 minutes
Your phone will be flashed
After that setup your phone
Boot again into fastboot mode
Setup adb in your PC
Install mediatek USB vcom drivers
And next follow second method
Click to expand...
Click to collapse
I don't lose the unlocked bootloader, right?
sephirot91 said:
I don't lose the unlocked bootloader, right?
Click to expand...
Click to collapse
Yes select flash all.bat your bootloader will remain unlock and your phone will be flashed
Don't select flash all and lock script otherwise bootloader of your phone will be locked and you will have to wait for 7 days to unlock bootloader
Unlocking your mi mix 4 :
lets start by enabling developer options on our mix 4, to do that go to device settings,then tap on My device > All specs > keep tapping on miui version till u enable developer options.
{
"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"
}
this will enable developer options under additional settings,
go to developer settings and enable OEM unlocking, and
select mi unlock status, put in a sim card, disconnect from wifi, enable cellular data, and tap on add account and device
wait for a week, only then u are allowed to unlock.
on your windows pc download and install adb, fastboot and drivers using the 15 seconds adb install tool link
this should install device drivers,
boot your phone into fastboot mode,
to boot your phone into fastboot, power off your device, and while poweing on hold volume down button.
this will put your phone into fastboot mode, connect it to your windows pc, check if the drivers are installed properly by going into
device manager and see if android device is shown without any errors,
open power shell and see if the device is recognised by the system by typing in
Code:
fastboot devices
this should display your device id.
Warning : unlocking your phone will format the whole phone please take a bakcup of your daata.
now download mi unlock tool from this link
open the mi unlock tool select your device and tap on unlock, it will prompt for your credentials,
type in your mi account details that are binded to your device, and once your are logged in,
click on unlock again, this will start the unlock process
on your mix 4, you will be prompted with this,
tap on the first option and log in using your mi account credentials,
your phone is now unlocked.
Replacing the chinese rom with an EU rom:now that the phone is unlocked, lets download the latest available EU fastboot flashable build from the following link
extract the downloaded rom, before we flash the rom, we need to reboot our phone to fastboot mode, to do that
as i told earlier, power off your device, and while powering the phone on, hold volume down, this will boot your mix 4 into fastboot mode.
lets reverify if your phone is unlocked by opening powershell and type in this command
Code:
fastboot oem device-info
Warning : the next step will format your device to factory settings, please backup the needed files.
now that we verified that the device is unlocked, lets flash the rom by clicking on
windows_fastboot_first_install_with_data_format.bat
this will start the flashing process. once the flash process is done, you can setup the mix 4 device.
Rooting mix 4 with magisk manager:warning : to root the phone your phone should be having an unlocked bootloader, please dont try to root your phone without unlocking the bootloader.and also banking apps, and payment apps might not work, so do accordingly.
copy imgages/boot.img file from extracted eu rom folder to mix 4 device,
install magisk manager from magisk github link.
once the magisk manager is installed,
open magisk manager, tap on install button next to Magisk,
then tap on select and patch file,
from the file manager, select the copied boot.img, and tap on next.
this will patch the boot.img image file and generate a magisk_patched.img in the downloads folder.
copy the magisk_patched.img file from downloads folder on android to the desktop on windows,
reboot your mix 4 to fastboot mode, and connect it to pc.
now open power shell window in the desktop folder by howering your mouse in the empty space,
and while holding the shift key on your keyboard, right click on the mouse, this will show an option
of open power shell window. click on it, and see if the device is recognised in fastboot mode by typing in
Code:
fastboot devices
this should show your device code.
now that the device is in fastboot mode, type in the following command
Code:
fastboot flash boot magisk_patched*.img
this will flash the magisk patched boot image, you can reboot your phone by typing in
Code:
fastboot reboot
once the phones booted up, open magisk manager, it should say installed : yes under magisk
and also a hovering menu at the bottom which will give access to super su functionality, and magisk modules too.
so if you guys want a detailed video for the same, check out ,
Great tutorial, i did all this but did not use magisk or root the phone, is there any reason to ?
jrvenge said:
Great tutorial, i did all this but did not use magisk or root the phone, is there any reason to ?
Click to expand...
Click to collapse
If you want to use Google Pay or any other app that uses SafeNet API to detect root, you might want to use Magisk to add hide module to trick SafetyNet and hide. SafetyNet unfortunately detects even unlocked bootloader and/or flashed custom ROM.
inao said:
If you want to use Google Pay or any other app that uses SafeNet API to detect root, you might want to use Magisk to add hide module to trick SafetyNet and hide. SafetyNet unfortunately detects even unlocked bootloader and/or flashed custom ROM.
Click to expand...
Click to collapse
so most of the banking apps or payment apps only stop working if u have rooted your rom. so i am on eu rom and most of the banking apps work if i dont root it
I guess it depends. On my MIX 3 Google Pay wasn't working because I had bootloader unlocked even when nothing was flashed. I'm planning to experiment a bit when official TWRP comes out because I really hate CN XiaoAI and a lot of features missing.
vamsi209 said:
so most of the banking apps or payment apps only stop working if u have rooted your rom. so i am on eu rom and most of the banking apps work if i dont root it
Click to expand...
Click to collapse
It does? Maybe try this one...
wipe cache of google play services
then perform safetynet-check...
I use google Pay on a daily basis and my phone is rooted.
SanHelios said:
It does? Maybe try this one...
wipe cache of google play services
then perform safetynet-check...
I use google Pay on a daily basis and my phone is rooted.
Click to expand...
Click to collapse
ok but rooted phones how is ur safetynet check passing mate ?
vamsi209 said:
ok but rooted phones how is ur safetynet check passing mate ?
Click to expand...
Click to collapse
Yes, everytime...
I should mention, that i use magisk hide for all my playstore and banking apps too.
Will the wait time to unlock bootloader reset if the phone is turned off for 7 days?
Aleksanderbjorn said:
Will the wait time to unlock bootloader reset if the phone is turned off for 7 days?
Click to expand...
Click to collapse
No. I turned off my device too. Unlocking proceeded without any problems.
Can anybody give instruction on root and magisk without installing eu? If i wanna use ch?
flozzz said:
Can anybody give instruction on root and magisk without installing eu? If i wanna use ch?
Click to expand...
Click to collapse
so inorder to root, you have to have your bootloader unlocked for sure,
so unlock your device as shown in my post above,
then extract your boot.img from the rom( find the version of your rom, download that specific rom from https://mifirm.net/model/odin.ttt )
and follow the above instructions for root as shown in my post(basically install magisk manager on your phone, use magisk to patch the boot.img, and the finally flash the boot.img using the command in fastboot mode.
Code:
fastboot flash boot magisk_patched*.img
and your phone should be rooted.
What if I want to return a phone to stock?
Bootloader is unlocked and it is running MIUI 12.6 by xiaomi.eu.
So I want to lock the bootloader and install the official rom so I can get OTA updates.
I downloaded MiFlash2020-3-14-0 and China Fastboot ROM: odin_images_V12.5.12.0.RKMCNXM_20211021.0000.00_11.0_cn_0d71adc934.
In MiFlash I selected clean all and lock. When trying to flash I am getting an Antirollback check error.
Short update: it seems you can't have spaces in the file path. After fixing this it flashed with no errors
ferid said:
Short update: it seems you can't have spaces in the file path. After fixing this it flashed with no errors
Click to expand...
Click to collapse
thaanks for the update
By switching to the EU rom, does that mean I will not have to change any permission settings to get the gaps to work or will I still have to change permissions settings even after the ROM comes preinstalled with Google apps?
It might be common sense for some, but I didn't see this as a separate post and it might help people get around this.
Once you unlock the bootloader and root with Magisk, you can't have OTA updates from the phone itself.
But what you can do to get these updates is to use the Xperia Companion tool.
You have to go to Magisk first and click on Uninstall and choose Restore images. This will bring back your original boot image from a backup Magisk does when patching the image.
Once this is done, reboot and connect the phone with Xperia Companion. Allow file transfers through USB. No need for USB debugging.
If there's an update available, it will download and transfer it to your phone. You'll see the install process in the status bar.
Once this is done, you can reboot and verify the update was installed. Now it's time to use Magisk to patch the new boot image.
There's a good guide already made - here.
In short use XperiFirm to download the latest FW, get the boot-x... sin file, put it in the folder where you have unsin executable file and just drag it over unsin. This will produce an image file, which you copy to your phone. Start Magisk, Magisk -> Install, it will ask you where the image file is, so point to the location where you saved it.
The result file will be put in Downloads on your phone. Copy it over to your PC.
Reboot the phone to Fastboot (Volume Up and Power buttons, or turn off the phone and press Volume Up, then connect the USB cable), you'll see you're in Fastboot if the LED is blue.
Open CMD, point to the location where you have ADB files copied and type in:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Where magisk_patched.img is your image file, so just put in the name and location to that file.
For example: fastboot flash boot_a c:\temp\boot_X-FLASH-ALL-4BA8.img
If the command fails, type in fastboot devices and that should list one device - the phone you connected.
If no devices are listed, check if you have the drivers for your phone. The article link above lists all driver and utilities downloads.
I've used newflasher and it soft bricked my phone. Maybe it's something I did wrong, but using the above is way easier and safer, in my opinion.
Hope it helps you too!
i tried your guide, and magisk don`t have backup of boot,
Was there any sort of an error message from Magisk?
It worked straight out for me.
Can't find Magisk's backup folder though, so I can see what I have inside.
unicastbg said:
Was there any sort of an error message from Magisk?
It worked straight out for me.
Can't find Magisk's backup folder though, so I can see what I have inside.
Click to expand...
Click to collapse
yes
Sakuma_Eitarou said:
yes
Click to expand...
Click to collapse
Emm, ok, what was the error message? I can guess one or two, but better ask than assume the wrong thing.
unicastbg said:
Emm, ok, what was the error message? I can guess one or two, but better ask than assume the wrong thing.
Click to expand...
Click to collapse
I did't deal with blocking the bootloader, but I expressed my thoughts
Let's see if someone else has the same issue.
I found Magisk uses root/data/magisk_backup_xxxxxxxxx folders, where xxxx is a combination of numbers and letters. There's a boot image copy in there.
When I flashed my magsik patched boot file, I had to factory reset my phone, otherwise on boot android would tell me my file system is currupt.
Any ideas why that might be?
cheesepuff said:
When I flashed my magsik patched boot file, I had to factory reset my phone, otherwise on boot android would tell me my file system is currupt.
Any ideas why that might be?
Click to expand...
Click to collapse
reflash with newflasher and use 2.4,3 of magisk ad\nd upgrade from that point
bountyman334 said:
reflash with newflasher and use 2.4,3 of magisk ad\nd upgrade from that point
Click to expand...
Click to collapse
I'm not 100% sure what all that means.
What's ad/nd?
And I'm not sure what 2.4,3 means in regards to magisk
Pretty sure that was a typo and they meant "and". Plus the magisk Number is the variant for example I'm on 25.2 which should be the latest one...
unicastbg said:
It might be common sense for some, but I didn't see this as a separate post and it might help people get around this.
Once you unlock the bootloader and root with Magisk, you can't have OTA updates from the phone itself.
But what you can do to get these updates is to use the Xperia Companion tool.
You have to go to Magisk first and click on Uninstall and choose Restore images. This will bring back your original boot image from a backup Magisk does when patching the image.
Once this is done, reboot and connect the phone with Xperia Companion. Allow file transfers through USB. No need for USB debugging.
If there's an update available, it will download and transfer it to your phone. You'll see the install process in the status bar.
Once this is done, you can reboot and verify the update was installed. Now it's time to use Magisk to patch the new boot image.
There's a good guide already made - here.
In short use XperiFirm to download the latest FW, get the boot-x... sin file, put it in the folder where you have unsin executable file and just drag it over unsin. This will produce an image file, which you copy to your phone. Start Magisk, Magisk -> Install, it will ask you where the image file is, so point to the location where you saved it.
The result file will be put in Downloads on your phone. Copy it over to your PC.
Reboot the phone to Fastboot (Volume Up and Power buttons, or turn off the phone and press Volume Up, then connect the USB cable), you'll see you're in Fastboot if the LED is blue.
Open CMD, point to the location where you have ADB files copied and type in:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Where magisk_patched.img is your image file, so just put in the name and location to that file.
For example: fastboot flash boot_a c:\temp\boot_X-FLASH-ALL-4BA8.img
If the command fails, type in fastboot devices and that should list one device - the phone you connected.
If no devices are listed, check if you have the drivers for your phone. The article link above lists all driver and utilities downloads.
I've used newflasher and it soft bricked my phone. Maybe it's something I did wrong, but using the above is way easier and safer, in my opinion.
Hope it helps you too!
Click to expand...
Click to collapse
Going through relock and using xperia companion to update is way too slow, inefficient and you loose your data in the mean time.
Just download latest fw from xperifirm, get the new bootimage (unsin ), magisk it, flash the whole fw with new flasher in flash mode (usb + vol down), goto fastboot, flash magisk boot image, reboot, done !
You've lost 0 data, didn't lost root, and you have the new fw
That's nice, but bootlocker remains unlocked during the procedure I wrote about. Therefore no data is lost in the process.
I used newflasher before and softbricked my phone.
And it's always good to have an alternative.
All of the options are way too complicated, compared to using TWRP. But we sadly don't have custom recovery.
unicastbg said:
That's nice, but bootlocker remains unlocked during the procedure I wrote about. Therefore no data is lost in the process.
I used newflasher before and softbricked my phone.
And it's always good to have an alternative.
All of the options are way too complicated, compared to using TWRP. But we sadly don't have custom recovery.
Click to expand...
Click to collapse
I don't get how you soft bricked with newflasher, bad firmware maybe ? model crossflashing ?
I've always used newflasher since it's out, before I was using flashtool by androixyde and didn't had issues too
It stopped on the very last step. To be honest the first time I used FW for another region. When I realized that, I tried flashing the proper one, but newflasher always stopped on the very last step. Can't recall what it was checking or verifying for.
Today LSposed was updated and I ended up in bootloop. As @fastbooking was saying why not use newflasher. So I did. And I ended up exactly where I was before.
{
"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"
}
unicastbg said:
Today LSposed was updated and I ended up in bootloop. As @fastbooking was saying why not use newflasher. So I did. And I ended up exactly where I was before.
View attachment 5758521
Click to expand...
Click to collapse
Try an usb 2.0 port maybe
I tried everything the guys proposed on the newflasher xda thread. Sadly it made no difference. I tried different USB ports, cables, Windows, Linux... I'm giving up on an otherwise app with a great potential.
unicastbg said:
It might be common sense for some, but I didn't see this as a separate post and it might help people get around this.
Once you unlock the bootloader and root with Magisk, you can't have OTA updates from the phone itself.
But what you can do to get these updates is to use the Xperia Companion tool.
You have to go to Magisk first and click on Uninstall and choose Restore images. This will bring back your original boot image from a backup Magisk does when patching the image.
Once this is done, reboot and connect the phone with Xperia Companion. Allow file transfers through USB. No need for USB debugging.
If there's an update available, it will download and transfer it to your phone. You'll see the install process in the status bar.
Once this is done, you can reboot and verify the update was installed. Now it's time to use Magisk to patch the new boot image.
There's a good guide already made - here.
In short use XperiFirm to download the latest FW, get the boot-x... sin file, put it in the folder where you have unsin executable file and just drag it over unsin. This will produce an image file, which you copy to your phone. Start Magisk, Magisk -> Install, it will ask you where the image file is, so point to the location where you saved it.
The result file will be put in Downloads on your phone. Copy it over to your PC.
Reboot the phone to Fastboot (Volume Up and Power buttons, or turn off the phone and press Volume Up, then connect the USB cable), you'll see you're in Fastboot if the LED is blue.
Open CMD, point to the location where you have ADB files copied and type in:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Where magisk_patched.img is your image file, so just put in the name and location to that file.
For example: fastboot flash boot_a c:\temp\boot_X-FLASH-ALL-4BA8.img
If the command fails, type in fastboot devices and that should list one device - the phone you connected.
If no devices are listed, check if you have the drivers for your phone. The article link above lists all driver and utilities downloads.
I've used newflasher and it soft bricked my phone. Maybe it's something I did wrong, but using the above is way easier and safer, in my opinion.
Hope it helps you too!
Click to expand...
Click to collapse
hi, I have some questions, could you please help me explain:
1. Uninstalling magisk and rebooting backup boot image will wipe device data?
2. If I can't find back up of boot image, can I use the one downloaded from Xperifirm with the same build number of my device?
3. Is there any other way to update ota without haveing to reset device. Thanks
dieuluucanh said:
hi, I have some questions, could you please help me explain:
1. Uninstalling magisk and rebooting backup boot image will wipe device data?
2. If I can't find back up of boot image, can I use the one downloaded from Xperifirm with the same build number of my device?
3. Is there any other way to update ota without haveing to reset device. Thanks
Click to expand...
Click to collapse
Hi,
1. This won't wipe the device data nor change any system or user apps.
2. Yes, you can use a boot image of the same FW version as the one installed on the phone.
I even did it with a different version, by a mistake, and the phone booted OK. But I don't know what might go wrong so I can't recommend this.
3. OTA doesn't work with the patched by Magisk boot image. So you need to replace the image with the original one, restart, apply the OTA (via Xperia Companion), restart, replace with the patched file of the new FW boot image.
This process doesn't reset your data as it's on another partition. If you have a custom boot animation (the first one), it might be lost.
If we had a full TWRP support, the whole process would have been way easier. Developers are trying to get it to work, for which I'm grateful even if it doesn't work at the end.