Razer phone 2 MR3 build posted on dev site

Search This thread
By:
Advanced…
O

omega552003

Senior Member
Aug 20, 2010
111
57
Melbourne, FL
T-Mobile Samsung Galaxy S III
Asus Eee Pad Transformer
These instructions assumes that you have platform tools and the Google ADB drivers installed. If you need instructions for that, look here:

To do an upgrade/dirty flash do the following:

  1. Extract the Zip, If you dont want root, skip to step 8
  2. Copy boot.img to you phone
  3. Open Magisk Manager app and Install > Patch Image
  4. Copy "magisk_patch.img" from your phone's Downloads to the folder you extracted the ROM to.
  5. Edit/Copy the flash_all.bat (or .sh on Linux/Mac)
  6. Find the lines 54 & 55 with:
    Code: 
    %fastboot_cmd% flash boot_a boot.img
%fastboot_cmd% flash boot_b boot.img
  7. Change them to:
    Code: 
    rem %fastboot_cmd% flash boot_a boot.img
rem %fastboot_cmd% flash boot_b boot.img
%fastboot_cmd% flash boot_a magisk_patched.img
%fastboot_cmd% flash boot_b magisk_patched.img
  8. Find line 71(73 if you did the steps above) with:
    Code: 
    %fastboot_cmd% erase userdata
  9. Change it to:
    Code: 
    rem %fastboot_cmd% erase userdata
  10. Save the batch script file
  11. Reboot your phone and hold the 'Volume Down' button until your phone boots into "Fastboot Mode"
  12. Run flash_all.bat or what ever you named it, It will reboot your phone twice, the second is when it is done and booting into android.
 
Last edited:
  • Like
Reactions: edison, w2830 and AllGamer
finixs

finixs

Member
Mar 7, 2020
27
3
They finally did it LOL.
Hope Android 10 or even 11 on their update roadmap.
 
AllGamer

AllGamer

Retired Forum Moderator
May 24, 2008
11,917
1,657
SGH-T989
AT&T Samsung Galaxy Note I717
I see a bunch of errors like:

"Flashing is not allowed for Critical Partitions"
or
"Erase is not allowed for Critical Partitions"

are those normal errors?

Code: 
D:\aura-p-release-3141>fastboot flash xbl_b xbl.img
Sending 'xbl_b' (3279 KB)                          OKAY [  0.094s]
Writing 'xbl_b'                                    FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash xbl_config_a xbl_config.img
Sending 'xbl_config_a' (95 KB)                     OKAY [  0.013s]
Writing 'xbl_config_a'                             FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash xbl_config_b xbl_config.img
Sending 'xbl_config_b' (95 KB)                     OKAY [  0.005s]
Writing 'xbl_config_b'                             FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash tz_a tz.img
Sending 'tz_a' (2008 KB)                           OKAY [  0.065s]
Writing 'tz_a'                                     FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash tz_b tz.img
Sending 'tz_b' (2008 KB)                           OKAY [  0.060s]
Writing 'tz_b'                                     FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash hyp_a hyp.img
Sending 'hyp_a' (376 KB)                           OKAY [  0.012s]
Writing 'hyp_a'                                    FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash hyp_b hyp.img
Sending 'hyp_b' (376 KB)                           OKAY [  0.019s]
Writing 'hyp_b'                                    FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash aop_a aop.img
Sending 'aop_a' (180 KB)                           OKAY [  0.015s]
Writing 'aop_a'                                    OKAY [  0.003s]
Finished. Total time: 0.028s

D:\aura-p-release-3141>fastboot flash aop_b aop.img
Sending 'aop_b' (180 KB)                           OKAY [  0.009s]
Writing 'aop_b'                                    OKAY [  0.002s]
Finished. Total time: 0.022s

D:\aura-p-release-3141>fastboot flash keymaster_a keymaster.img
Sending 'keymaster_a' (227 KB)                     OKAY [  0.008s]
Writing 'keymaster_a'                              FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash keymaster_b keymaster.img
Sending 'keymaster_b' (227 KB)                     OKAY [  0.016s]
Writing 'keymaster_b'                              FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash cmnlib_a cmnlib.img
Sending 'cmnlib_a' (367 KB)                        OKAY [  0.019s]
Writing 'cmnlib_a'                                 FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash cmnlib_b cmnlib.img
Sending 'cmnlib_b' (367 KB)                        OKAY [  0.021s]
Writing 'cmnlib_b'                                 FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash cmnlib64_a cmnlib64.img
Sending 'cmnlib64_a' (484 KB)                      OKAY [  0.020s]
Writing 'cmnlib64_a'                               FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash cmnlib64_b cmnlib64.img
Sending 'cmnlib64_b' (484 KB)                      OKAY [  0.015s]
Writing 'cmnlib64_b'                               FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash devcfg_a devcfg.img
Sending 'devcfg_a' (39 KB)                         OKAY [  0.010s]
Writing 'devcfg_a'                                 FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash devcfg_b devcfg.img
Sending 'devcfg_b' (39 KB)                         OKAY [  0.007s]
Writing 'devcfg_b'                                 FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash ImageFv_a ImageFv.img
Sending 'ImageFv_a' (20 KB)                        OKAY [  0.010s]
Writing 'ImageFv_a'                                OKAY [  0.001s]
Finished. Total time: 0.020s

D:\aura-p-release-3141>fastboot flash ImageFv_b ImageFv.img
Sending 'ImageFv_b' (20 KB)                        OKAY [  0.006s]
Writing 'ImageFv_b'                                OKAY [  0.001s]
Finished. Total time: 0.017s

D:\aura-p-release-3141>fastboot flash qupfw_a qupfw.img
Sending 'qupfw_a' (63 KB)                          OKAY [  0.005s]
Writing 'qupfw_a'                                  OKAY [  0.002s]
Finished. Total time: 0.015s

D:\aura-p-release-3141>fastboot flash qupfw_b qupfw.img
Sending 'qupfw_b' (63 KB)                          OKAY [  0.012s]
Writing 'qupfw_b'                                  OKAY [  0.001s]
Finished. Total time: 0.024s

D:\aura-p-release-3141>fastboot flash abl_a abl.img
Sending 'abl_a' (1024 KB)                          OKAY [  0.038s]
Writing 'abl_a'                                    FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot reboot-bootloader
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.002s

D:\aura-p-release-3141>timeout /t 10

Waiting for  0 seconds, press a key to continue ...

D:\aura-p-release-3141>fastboot oem simconfig set SS
                                                   OKAY [  0.001s]
Finished. Total time: 0.001s

D:\aura-p-release-3141>fastboot flash avb_custom_key pkmd.bin
fastboot: error: cannot load 'pkmd.bin': No such file or directory

D:\aura-p-release-3141>fastboot flash abl_b abl.img
Sending 'abl_b' (1024 KB)                          OKAY [  0.036s]
Writing 'abl_b'                                    FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot erase ddr
Erasing 'ddr'                                      FAILED (remote: 'Erase is not allowed for Critical Partitions
')
fastboot: error: Command failed

D:\aura-p-release-3141>fastboot flash persist persist.img
Sending 'persist' (32768 KB)                       OKAY [  0.923s]
Writing 'persist'                                  OKAY [  0.411s]
Finished. Total time: 1.345s

D:\aura-p-release-3141>fastboot flash modem_a modem.img
Sending 'modem_a' (116444 KB)                      OKAY [  3.292s]
Writing 'modem_a'                                  OKAY [  0.916s]
Finished. Total time: 4.218s

D:\aura-p-release-3141>fastboot flash modem_b modem.img
Sending 'modem_b' (116444 KB)                      OKAY [  3.296s]
Writing 'modem_b'                                  OKAY [  0.884s]
Finished. Total time: 4.197s

D:\aura-p-release-3141>fastboot flash dsp_a dsp.img
Sending 'dsp_a' (32768 KB)                         OKAY [  0.925s]
Writing 'dsp_a'                                    OKAY [  0.232s]
Finished. Total time: 1.166s

D:\aura-p-release-3141>fastboot flash dsp_b dsp.img
Sending 'dsp_b' (32768 KB)                         OKAY [  0.925s]
Writing 'dsp_b'                                    OKAY [  0.246s]
Finished. Total time: 1.202s

D:\aura-p-release-3141>fastboot flash boot_a magisk_patched.img
Sending 'boot_a' (20772 KB)                        OKAY [  0.594s]
Writing 'boot_a'                                   OKAY [  0.165s]
Finished. Total time: 0.768s

D:\aura-p-release-3141>fastboot flash boot_b magisk_patched.img
Sending 'boot_b' (20772 KB)                        OKAY [  0.592s]
Writing 'boot_b'                                   OKAY [  0.299s]
Finished. Total time: 0.907s

D:\aura-p-release-3141>fastboot flash dtbo_a dtbo.img
Sending 'dtbo_a' (8192 KB)                         OKAY [  0.238s]
Writing 'dtbo_a'                                   OKAY [  0.066s]
Finished. Total time: 0.312s

D:\aura-p-release-3141>fastboot flash dtbo_b dtbo.img
Sending 'dtbo_b' (8192 KB)                         OKAY [  0.239s]
Writing 'dtbo_b'                                   OKAY [  0.066s]
Finished. Total time: 0.333s

D:\aura-p-release-3141>fastboot flash bluetooth_a bluetooth.img
Sending 'bluetooth_a' (748 KB)                     OKAY [  0.026s]
Writing 'bluetooth_a'                              OKAY [  0.005s]
Finished. Total time: 0.042s

D:\aura-p-release-3141>fastboot flash bluetooth_b bluetooth.img
Sending 'bluetooth_b' (748 KB)                     OKAY [  0.028s]
Writing 'bluetooth_b'                              OKAY [  0.008s]
Finished. Total time: 0.054s

D:\aura-p-release-3141>fastboot flash logfs logfs_ufs_8mb.bin
Sending 'logfs' (16 KB)                            OKAY [  0.010s]
Writing 'logfs'                                    OKAY [  0.001s]
Finished. Total time: 0.021s

D:\aura-p-release-3141>fastboot flash system_a system.img
Sending sparse 'system_a' 1/6 (515468 KB)          OKAY [ 15.415s]
Writing 'system_a'                                 OKAY [  0.001s]
Sending sparse 'system_a' 2/6 (514448 KB)          OKAY [ 19.345s]
Writing 'system_a'                                 OKAY [  0.000s]
Sending sparse 'system_a' 3/6 (515328 KB)          OKAY [ 19.086s]
Writing 'system_a'                                 OKAY [  0.001s]
Sending sparse 'system_a' 4/6 (516208 KB)          OKAY [ 19.555s]
Writing 'system_a'                                 OKAY [  0.000s]
Sending sparse 'system_a' 5/6 (516208 KB)          OKAY [ 19.726s]
Writing 'system_a'                                 OKAY [  0.000s]
Sending sparse 'system_a' 6/6 (367560 KB)          OKAY [ 15.416s]
Writing 'system_a'                                 OKAY [  0.000s]
Finished. Total time: 114.098s

D:\aura-p-release-3141>fastboot flash system_b system_other.img
Sending 'system_b' (335964 KB)                     OKAY [  9.455s]
Writing 'system_b'                                 OKAY [  0.001s]
Finished. Total time: 9.615s

D:\aura-p-release-3141>fastboot flash vendor_a vendor.img
Sending 'vendor_a' (493676 KB)                     OKAY [ 13.896s]
Writing 'vendor_a'                                 OKAY [  0.001s]
Finished. Total time: 14.120s

D:\aura-p-release-3141>fastboot flash vendor_b vendor.img
Sending 'vendor_b' (493676 KB)                     OKAY [ 13.900s]
Writing 'vendor_b'                                 OKAY [  0.000s]
Finished. Total time: 14.129s

D:\aura-p-release-3141>fastboot flash vbmeta_a vbmeta.img
Sending 'vbmeta_a' (4 KB)                          OKAY [  0.009s]
Writing 'vbmeta_a'                                 OKAY [  0.001s]
Finished. Total time: 0.019s

D:\aura-p-release-3141>fastboot flash vbmeta_b vbmeta.img
Sending 'vbmeta_b' (4 KB)                          OKAY [  0.008s]
Writing 'vbmeta_b'                                 OKAY [  0.001s]
Finished. Total time: 0.019s

D:\aura-p-release-3141>fastboot flash systeminfo_a systeminfo.img
fastboot: error: cannot load 'systeminfo.img': No such file or directory

D:\aura-p-release-3141>fastboot flash systeminfo_b systeminfo.img
fastboot: error: cannot load 'systeminfo.img': No such file or directory

D:\aura-p-release-3141>fastboot flash nvdef_a nvdef.img
Sending 'nvdef_a' (1380 KB)                        OKAY [  0.046s]
Writing 'nvdef_a'                                  OKAY [  0.021s]
Finished. Total time: 0.077s

D:\aura-p-release-3141>fastboot flash nvdef_b nvdef.img
Sending 'nvdef_b' (1380 KB)                        OKAY [  0.049s]
Writing 'nvdef_b'                                  OKAY [  0.018s]
Finished. Total time: 0.084s

D:\aura-p-release-3141>rem fastboot erase userdata

D:\aura-p-release-3141>fastboot erase box
Erasing 'box'                                      OKAY [  0.086s]
Finished. Total time: 0.092s

D:\aura-p-release-3141>fastboot flash splash splash.img
Sending 'splash' (10816 KB)                        OKAY [  0.312s]
Writing 'splash'                                   OKAY [  0.090s]
Finished. Total time: 0.412s

D:\aura-p-release-3141>fastboot flash storsec storsec.mbn
Sending 'storsec' (20 KB)                          OKAY [  0.006s]
Writing 'storsec'                                  OKAY [  0.002s]
Finished. Total time: 0.017s

D:\aura-p-release-3141>fastboot reboot
Rebooting                                          OKAY [  0.000s]
Finished. Total time: 0.002s


*** waiting for boot... 30 min later... ***

No luck...
seems like it didn't like the replacement for the magisk_patched.img

went back to fastboot mode, flashed MR3 without root, basically skipped to step 8 directly, that worked well.
booted into OS in like 15 sec.
it kept all my data, nice.

Now I need to figure out how to root it again, so i can keep using Titanium Backup and many other Apps that only works with root.

*** after a while ... ***

Alright
flashed latest R14 arter97 (https://xdaforums.com/razer-phone-2/development/arter97-kernel-razer-phone-2-t3914996) kernel img to boot a and boot b
this gives me access to TWRP
picked up latest version of Magisk https://******************/
booted to TWRP
flashed Magisk root.
now I'm back in business with Titanium Backup, etc...
 
Last edited:
xtacb4

xtacb4

Senior Member
Oct 11, 2010
136
31
Hi!

I just wanted to share my experience performing this steps.

I dirty Flashed. In short, everthing worked, with a minor hiccup. After rebooting the first time, it said encryption unsuccessful, so I rebooted to TWRP and flashed f2fs_fstab.zip and vold_mod_arter97.zip that I had copied before to the phone (not being sure if I'd need them), rebooted and everything worked!


AllGamer said:
I see a bunch of errors like:
"Flashing is not allowed for Critical Partitions"
or
"Erase is not allowed for Critical Partitions"

are those normal errors?
Click to expand...
Click to collapse

Yes, it happends when the partitions are locked for flashing, you should be able to unlock them with the following command.

Code: 
fastboot flashing unlock_critical

I didn't had to do this for these steps to work for me though.

Cheers.
 
Last edited:
  • Like
Reactions: w2830
H

hoodred

Senior Member
May 21, 2011
175
86
Link to the patched Global MR3 boot image with Magisk
Patched boot.img


omega552003 said:
These instructions assumes that you have platform tools and the Google ADB drivers installed. If you need instructions for that, look here:

To do an upgrade/dirty flash do the following:

  1. Extract the Zip, If you dont want root, skip to step 8
  2. Copy boot.img to you phone
  3. Open Magisk Manager app and Install > Patch Image
  4. Copy "magisk_patch.img" from your phone's Downloads to the folder you extracted the ROM to.
  5. Edit/Copy the flash_all.bat (or .sh on Linux/Mac)
  6. Find the lines 54 & 55 with:
    Code: 
    %fastboot_cmd% flash boot_a boot.img
%fastboot_cmd% flash boot_b boot.img
  7. Change them to:
    Code: 
    rem %fastboot_cmd% flash boot_a boot.img
rem %fastboot_cmd% flash boot_b boot.img
%fastboot_cmd% flash boot_a magisk_patched.img
%fastboot_cmd% flash boot_b magisk_patched.img
  8. Find line 71(73 if you did the steps above) with:
    Code: 
    %fastboot_cmd% erase userdata
  9. Change it to:
    Code: 
    rem %fastboot_cmd% erase userdata
  10. Save the batch script file
  11. Reboot your phone and hold the 'Volume Down' button until your phone boots into "Fastboot Mode"
  12. Run flash_all.bat or what ever you named it, It will reboot your phone twice, the second is when it is done and booting into android.
Click to expand...
Click to collapse
 
M

Makyura

Member
Jan 5, 2019
7
0
Hello everyone,

I tried to dirty flash it easily through fastboot (flash_all) as per razer instructions and now I seem to be stuck in a quasi-boot loop.

Devices reaches system and after two seconds it pops the window "Power off - shutting down" and it reboots. After rebooting, I get a similar to bootloader interaction saying that boot failed and that i should wipe userdata, which I do, with no effect.

Sometimes, after I tried flashing MSR2 and 1, i get an interaction saying that android.process.acore stopped working and then it powers off.

Safe mode didn't help either. Any suggestion? I need to RMA this one for a screen issue and I wanted to wipe everything installing the system from scratch, I don't think that they will accept it as is.

Thank you for your help!
 
H

hoodred

Senior Member
May 21, 2011
175
86
Makyura said:
Hello everyone,

I tried to dirty flash it easily through fastboot (flash_all) as per razer instructions and now I seem to be stuck in a quasi-boot loop.

Devices reaches system and after two seconds it pops the window "Power off - shutting down" and it reboots. After rebooting, I get a similar to bootloader interaction saying that boot failed and that i should wipe userdata, which I do, with no effect.

Sometimes, after I tried flashing MSR2 and 1, i get an interaction saying that android.process.acore stopped working and then it powers off.

Safe mode didn't help either. Any suggestion? I need to RMA this one for a screen issue and I wanted to wipe everything installing the system from scratch, I don't think that they will accept it as is.

Thank you for your help!
Click to expand...
Click to collapse

Dont dirty flash
Make sure both your bootloader and bootloader critical are unlock

just flash as usual and download the rom from
https://developer.razer.com/razer-phone-dev-tools/factory-images/

general instruction from below
https://developer.razer.com/razer-p...70.285929881.1593019602-1360853609.1593019602
 
M

Makyura

Member
Jan 5, 2019
7
0
hoodred said:
Dont dirty flash
Make sure both your bootloader and bootloader critical are unlock

just flash as usual and download the rom from
https://developer.razer.com/razer-phone-dev-tools/factory-images/

general instruction from below
https://developer.razer.com/razer-p...70.285929881.1593019602-1360853609.1593019602
Click to expand...
Click to collapse

I was flashing those, but none of the recent ones worked. I had to flash the very first release, 8.1 MR0 (litterally tried all of them backwards).
 
R

Ruriseban

New member
Aug 23, 2020
1
0
Unable to get to fast boot

If not in the right location please direct me. I'm at quite aloss I've been extensively reading the forums to root my razer phone 2. I cannot get windows 10 to recognize the phone in fastboot in cmd prompt while in bootloader, it will recognize the phone while it's on and adb works. Once I give the command for adb reboot bootloader it has the phone reboot to boot loader but fastboot won't detect. I've tried updating the drivers and it still shows android with the question mark circle. I know it must be something simple I'm overlooking. Please can anyone assist?
 
You must log in or register to reply here.

Similar threads

Twiggy000b
Flash GSI Roms on Razer Phone 2!
Replies
254
Views
43K
T
TechX1991
chpimentelpr
ROOT with PIE Guide
Replies
156
Views
46K
R
Reznor7
M
[GUIDE] Android 11 GSI With GApps and Root (magisk)
Replies
194
Views
46K
M
Marcos8760
U
[GUIDE] Root and/or install a GSI on razer phone 2 and pass safety net (For Windows)
Replies
166
Views
24K
F
Firedrake1
S
Razer Phone 2 Brick with Locked Bootloader
Replies
19
Views
8K
S
simplegek

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 3
    O
    omega552003
    These instructions assumes that you have platform tools and the Google ADB drivers installed. If you need instructions for that, look here:

    To do an upgrade/dirty flash do the following:

    1. Extract the Zip, If you dont want root, skip to step 8
    2. Copy boot.img to you phone
    3. Open Magisk Manager app and Install > Patch Image
    4. Copy "magisk_patch.img" from your phone's Downloads to the folder you extracted the ROM to.
    5. Edit/Copy the flash_all.bat (or .sh on Linux/Mac)
    6. Find the lines 54 & 55 with:
      Code: 
      %fastboot_cmd% flash boot_a boot.img
%fastboot_cmd% flash boot_b boot.img
    7. Change them to:
      Code: 
      rem %fastboot_cmd% flash boot_a boot.img
rem %fastboot_cmd% flash boot_b boot.img
%fastboot_cmd% flash boot_a magisk_patched.img
%fastboot_cmd% flash boot_b magisk_patched.img
    8. Find line 71(73 if you did the steps above) with:
      Code: 
      %fastboot_cmd% erase userdata
    9. Change it to:
      Code: 
      rem %fastboot_cmd% erase userdata
    10. Save the batch script file
    11. Reboot your phone and hold the 'Volume Down' button until your phone boots into "Fastboot Mode"
    12. Run flash_all.bat or what ever you named it, It will reboot your phone twice, the second is when it is done and booting into android.
    View
    1
    M
    macjunkie
    MR3 build as posted
    https://developer.razer.com/razer-phone-dev-tools/factory-images/
    View
    1
    xtacb4
    xtacb4
    Hi!

    I just wanted to share my experience performing this steps.

    I dirty Flashed. In short, everthing worked, with a minor hiccup. After rebooting the first time, it said encryption unsuccessful, so I rebooted to TWRP and flashed f2fs_fstab.zip and vold_mod_arter97.zip that I had copied before to the phone (not being sure if I'd need them), rebooted and everything worked!


    AllGamer said:
    I see a bunch of errors like:
    "Flashing is not allowed for Critical Partitions"
    or
    "Erase is not allowed for Critical Partitions"

    are those normal errors?
    Click to expand...
    Click to collapse

    Yes, it happends when the partitions are locked for flashing, you should be able to unlock them with the following command.

    Code: 
    fastboot flashing unlock_critical

    I didn't had to do this for these steps to work for me though.

    Cheers.
    View

New posts