Database Users

I think I have bricked it :(

Hello guys,
I think I bricked my nexus 10 while trying to factory restock.
Here's what I did/tried:
Downloaded mantaray-jop40c-factory-0d641789.tgz and ran ./flash-all.sh
Code:
erasing 'boot'...
OKAY [ 0.028s]
finished. total time: 0.028s
erasing 'cache'...
OKAY [ 0.040s]
finished. total time: 0.040s
erasing 'recovery'...
OKAY [ 0.028s]
finished. total time: 0.028s
erasing 'system'...
OKAY [ 0.041s]
finished. total time: 0.041s
erasing 'userdata'...
OKAY [ 0.224s]
finished. total time: 0.224s
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.119s]
finished. total time: 0.281s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB02ZYQT
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
sending 'boot' (4606 KB)...
OKAY [ 0.579s]
writing 'boot'...
OKAY [ 0.128s]
sending 'recovery' (5106 KB)...
OKAY [ 0.641s]
writing 'recovery'...
OKAY [ 0.136s]
sending 'system' (528847 KB)...
OKAY [ 59.771s]
writing 'system'...
OKAY [ 14.660s]
erasing 'userdata'...
OKAY [ 0.231s]
erasing 'cache'...
OKAY [ 0.036s]
rebooting...
finished. total time: 76.192s
Nexus rebooted into the google X, stuck there for 30 minutes ....
I read some posts, decided I needed to wipe data/factory reset, so booted in fastboot mode and launched recovery ... got the droid with the triangle but no amount of volume up + power would boot me into the stock recovery.
Then I flashed CWM recovery
Code:
fastboot flash recovery ../recovery-clockwork-touch-6.0.2.3-manta.img
and could boot into recovery .. tried to do a factory reset and got:
Code:
Error mounting /cache!
Done.
--Wiping data ...
Formatting /data
Error mounting /data!
Skipping format...
Formatting /cache
Formatting /sd-ext
Formatting /sdcard/.android_secure
Error mounting /sdcard/.android_secure
Skipping format...
Data wipe complete
and needless to say I got the same result ..... I have tried this procedure multiple times .. verified the md5 of the factory image, tried re-locking and unlocking the bootloader to no avail ... so I am stumped.
Did I in some way manage to wreck the partition table ? is it even possible ? or am I missing something much simpler?

madmatt71 said:
Hello guys,
I think I bricked my nexus 10 while trying to factory restock.
Here's what I did/tried:
Downloaded mantaray-jop40c-factory-0d641789.tgz and ran ./flash-all.sh
Code:
erasing 'boot'...
OKAY [ 0.028s]
finished. total time: 0.028s
erasing 'cache'...
OKAY [ 0.040s]
finished. total time: 0.040s
erasing 'recovery'...
OKAY [ 0.028s]
finished. total time: 0.028s
erasing 'system'...
OKAY [ 0.041s]
finished. total time: 0.041s
erasing 'userdata'...
OKAY [ 0.224s]
finished. total time: 0.224s
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.119s]
finished. total time: 0.281s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB02ZYQT
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
sending 'boot' (4606 KB)...
OKAY [ 0.579s]
writing 'boot'...
OKAY [ 0.128s]
sending 'recovery' (5106 KB)...
OKAY [ 0.641s]
writing 'recovery'...
OKAY [ 0.136s]
sending 'system' (528847 KB)...
OKAY [ 59.771s]
writing 'system'...
OKAY [ 14.660s]
erasing 'userdata'...
OKAY [ 0.231s]
erasing 'cache'...
OKAY [ 0.036s]
rebooting...
finished. total time: 76.192s
Nexus rebooted into the google X, stuck there for 30 minutes ....
I read some posts, decided I needed to wipe data/factory reset, so booted in fastboot mode and launched recovery ... got the droid with the triangle but no amount of volume up + power would boot me into the stock recovery.
Then I flashed CWM recovery
Code:
fastboot flash recovery ../recovery-clockwork-touch-6.0.2.3-manta.img
and could boot into recovery .. tried to do a factory reset and got:
Code:
Error mounting /cache!
Done.
--Wiping data ...
Formatting /data
Error mounting /data!
Skipping format...
Formatting /cache
Formatting /sd-ext
Formatting /sdcard/.android_secure
Error mounting /sdcard/.android_secure
Skipping format...
Data wipe complete
and needless to say I got the same result ..... I have tried this procedure multiple times .. verified the md5 of the factory image, tried re-locking and unlocking the bootloader to no avail ... so I am stumped.
Did I in some way manage to wreck the partition table ? is it even possible ? or am I missing something much simpler?
Click to expand...
Click to collapse
.. and after half a day banging my head I realized I was using an old version of adb and fastboot ... downloaded the latest version from google and .... restored withouth any problem .....
sorry for the waste of bandwidth

madmatt71 said:
.. and after half a day banging my head I realized I was using an old version of adb and fastboot ... downloaded the latest version from google and .... restored withouth any problem .....
sorry for the waste of bandwidth
Click to expand...
Click to collapse
nonesense. Someone else who is having similar issues might find your answer of updating adb and fastboot incredibly useful.

EniGmA1987 said:
nonesense. Someone else who is having similar issues might find your answer of updating adb and fastboot incredibly useful.
Click to expand...
Click to collapse
Err, yes, it could be useful.
What tipped me off was an apparently unrelated post on google groups from a google developer who stated that in the latest versions of fastboot they added some features to query the devices with respect to partition types/layout in order to be able to decide whether to format or erase a partition depending on what was needed, and since it looked like my partition table was wasted I finally got on about checking which version of fastboot I was using ....

madmatt71,
Please add "[SOLVED]" to the beginning of this threads title so as to alert people to your solution. It really helps when viewing search results. Only the orginal poster can make this change. Just edit your original post.

Help p9 lite, black screen how to fix it

Good afternoon to all, I need a lot of help. I have a p9 lite VNS-L23 C605B120, try to install the rom revolution nougat, unlock the bootloader, install the recovery and from there an update file, when I finish, I reset and the phone left with the black screen, I connect it, the PC and I recognize it: Android bootloader interface, do not enter with the 3 buttons: vol + vol - and button on.
I need help on how I can flash it, with some program or how I can fix it, and what are the necessary files ... Thank you very much already.
Pd: the HiSuit of hawei is opened every time I connect the phone to the PC, but it does not allow me to recover the system, at the beginning it leaves: it is acceded to the system recovery mode, I click to recover system and then leaves, the device Does not support system recovery.

Same here unfortunately

Can you to enter to fastboot? If yes is the bootloader locked or unlocked?

Potato997 said:
Can you to enter to fastboot? If yes is the bootloader locked or unlocked?
Click to expand...
Click to collapse
This is in flashboot mode, and yes unlock bootloader, but black screen, allows to restart with commands, but unfortunately I do not have much knowledge about this, I hope help, what steps can I take to be able to turn it on.

Try to flash again TWRP and boot to recovery.

By fastboot I can reset, install twrp, reboot, but still black screen, there is no vibration, but when connecting the phone, appears in android bootloader interface. What else can I do with commands

As I said, can you boot to TWRP?

Potato997 said:
As I said, can you boot to TWRP?
Click to expand...
Click to collapse
See

hanzox5 said:
See
Click to expand...
Click to collapse
....
But no reboot in recovery

C:\Program Files (x86)\HiSuite\hwtools>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (13810 KB)...
OKAY [ 0.297s]
writing 'boot'...
OKAY [ 0.491s]
finished. total time: 0.788s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.704s]
writing 'recovery'...
OKAY [ 1.143s]
finished. total time: 1.862s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (331661 KB)...
OKAY [ 7.077s]
writing 'cust'...
OKAY [ 8.053s]
finished. total time: 15.149s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (452763 KB)...
OKAY [ 10.992s]
writing 'system'...
OKAY [ 11.640s]
sending sparse 'system' (458056 KB)...
OKAY [ 10.877s]
writing 'system'...
OKAY [ 11.137s]
sending sparse 'system' (459104 KB)...
OKAY [ 11.816s]
writing 'system'...
OKAY [ 12.201s]
sending sparse 'system' (457466 KB)...
OKAY [ 11.096s]
writing 'system'...
OKAY [ 11.214s]
sending sparse 'system' (460756 KB)...
OKAY [ 11.049s]
writing 'system'...
OKAY [ 11.190s]
sending sparse 'system' (135249 KB)...
OKAY [ 3.234s]
writing 'system'...
OKAY [ 3.302s]
finished. total time: 119.793s
C:\Program Files (x86)\HiSuite\hwtools>fastboot reboot
rebooting...
finished. total time: 0.016s
C:\Program Files (x86)\HiSuite\hwtools>

Reboot to recovery in this way: shut down the phone, press volume up + power button
Factory reset
Reboot

Do not enter recovery, still on black screen, can tell me which software I can flash it

I already told you like three times.. try both TWRP and stock recovery..

I installed the twrp as the stock recovery and try to enter using press volume up + power button, and nothing
Is there any way to force the phone to enter twrp via fastboot, would help me with commands.

hanzox5 said:
I installed the twrp as the stock recovery and try to enter using press volume up + power button, and nothing
Is there any way to force the phone to enter twrp via fastboot, would help me with commands.
Click to expand...
Click to collapse
fastboot boot recovery.img
Try that.
Also you should try the three buttons method now.

C:\Program Files (x86)\HiSuite\hwtools>fastboot boot recovery.img
creating boot image...
creating boot image - 33753088 bytes
downloading 'boot.img'...
OKAY [ 0.703s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.719s

hanzox5 said:
C:\Program Files (x86)\HiSuite\hwtools>fastboot boot recovery.img
creating boot image...
creating boot image - 33753088 bytes
downloading 'boot.img'...
OKAY [ 0.703s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.719s
Click to expand...
Click to collapse
ಠ_ಠ
Weird.

479/5000
Several times I installed TWRP and stock recovery, and I can not enter any of the 2 forms and even with the three buttons, I even purchase a micro SD of 32gb class 10, with this saying that the SD was the one that did not work.
Please, let's go again, I recommend doing from 0 to try to solve this blessed problem. That I should be doing, it will be possible to clean the cache and user data from fastboot, and from there to do something more.

Have you tried three button method with update.app in dload folder in SD card?
If yes, did it gave you some error/did the update started/when did it stopped?

If I have the sd, and inside the Dload folder, update.app, but it does nothing.

Nexus 7 (2013 Mobile) fails to boot; can't enter Recovery mode; flash write failure

My Nexus 7 (2013 Mobile) was rooted and updated to stock Android 6.0 a year ago, no 3rd party ROM/recovery is installed. Last week while checking emails, it rebooted suddenly then remained at Google letters and unlock icon, I can enter fastboot mode by pressing power and volume- buttons together, the last line shows status unlocked; then if select "Recovery mode", it reboots then shows a dead robot with an exclamation mark only. I downloaded the latest factory image "razorg-mob30x", connect it to my PC and enter adb command "flash-all.bat" (I modified the bat file by removing -w, so it won't wipe the user data), then it shows: FAILED (remote: flash write failure)
sending 'bootloader' (3915 KB)...
OKAY [ 0.135s]
writing 'bootloader' ...
FAILED (remote: flash write failure)
finished. total time 90.811s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time 0.012s
sending 'radio' (76038 KB)...
OKAY [ 2.393s]
writing 'radio' ...
FAILED (remote: flash write failure)
finished. total time 92.549s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time 0.013s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
----------------------------------------------------
Bootloader Version...: FLO-04.08
Basedband Version...: DEB-Z00_2.44.0_0213
Serial Number................: 0879222a
----------------------------------------------------
checking product...
OKAY [ 0.005s]
checking version-bootloader...
OKAY [ 0.006s]
checking version-baseband...
OKAY [ 0.006s]
sending 'boot' (7422 KB)
OKAY [ 0.243s]
writing 'boot' ...
FAILED (remote: flash write failure)
finished. total time 90.151s
Press any key to exit...
Click to expand...
Click to collapse
What else I can do to resuce my pad? Does this mean the memory is physically damaged?
Please advise. Your help is much appreciated.

OnePlus 6T always boot on Bootloader, cant flash TWRP or Stock Recovery...

What about friends, it happens that I wanted to install TWRP to my OP6T, but it did not go well ... I followed the steps and when I gave "Reboot Recovery", I entered the fastboot mode, and it did not happen there, it did not allow me to flash the rom, the stock recovery, or the TWRP, tells me the following ...
This happens when wanting to boot the twrp.img:
PS C:\Users\vhr07\Desktop> fastboot devices
785694ef fastboot
PS C:\Users\vhr07\Desktop> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.713s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.746s
PS C:\Users\vhr07\Desktop>
--------------------------------------------------------------------------------------------
This happens when you want to install the recovery stock:
PS C:\Users\vhr07\Desktop> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.518s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.536s
PS C:\Users\vhr07\Desktop>
---------------------------------------------------------------------------------------------
I install the recovery by means of "boot" and it says OK, but when wanting to boot I get error:
PS C:\Users\vhr07\Desktop> fastboot flash boot recovery.img
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.518s]
writing 'boot'...
OKAY [ 0.271s]
finished. total time: 1.794s
PS C:\Users\vhr07\Desktop> fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.506s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.547s
PS C:\Users\vhr07\Desktop>
---------------------------------------------------------------------------------------------
These were my last attempts ...:
PS C:\Users\vhr07\Desktop> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (30948 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.734s
PS C:\Users\vhr07\Desktop> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.508s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.525s
PS C:\Users\vhr07\Desktop> fastboot flash recovery twrp.zip
target reported max download size of 536870912 bytes
sending 'recovery' (16849 KB)...
OKAY [ 0.391s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.406s
PS C:\Users\vhr07\Desktop> fastboot flash recovery_b recovery.img
target reported max download size of 536870912 bytes
sending 'recovery_b' (65536 KB)...
OKAY [ 1.523s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 1.538s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b recovery.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.517s]
writing 'boot_b'...
OKAY [ 0.301s]
finished. total time: 1.824s
PS C:\Users\vhr07\Desktop> fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.511s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.549s
PS C:\Users\vhr07\Desktop> fastboot flash boot twrp.img
target reported max download size of 536870912 bytes
sending 'boot' (30948 KB)...
OKAY [ 0.714s]
writing 'boot'...
OKAY [ 0.154s]
finished. total time: 0.874s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (30948 KB)...
OKAY [ 0.717s]
writing 'boot_b'...
OKAY [ 0.181s]
finished. total time: 0.904s
PS C:\Users\vhr07\Desktop> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.716s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.746s
----------------------------------------------------------------------------
Please, I need your help I promise not to ROOT again the hahaha team
I would pay if necessary
PD: already tried with bootloader unlocked and blocked
UPDATE: MSMTools, stuck on "PARAM PREPROCESSING"
https://imgur.com/qiaF8oh

First, flash the original boot.img again:
> fastboot flash boot_a boot.img
> fastboot flash boot_b boot.img
Then follow the instructions in https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482.

foobar66 said:
First, flash the original boot.img again:
> fastboot flash boot_a boot.img
> fastboot flash boot_b boot.img
Then follow the instructions in https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482.
Click to expand...
Click to collapse
Same situation
PS C:\Users\vhr07\Desktop> fastboot devices
785694ef fastboot
PS C:\Users\vhr07\Desktop> fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.500s]
writing 'boot_a'...
OKAY [ 0.308s]
finished. total time: 1.814s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.498s]
writing 'boot_b'...
OKAY [ 0.345s]
finished. total time: 1.849s
PS C:\Users\vhr07\Desktop> fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.505s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.537s
PS C:\Users\vhr07\Desktop>

Seem look like usb debug not authorize pc

i had the same issue, and i was able to resurrect my phone, here's what i did:
Download both files from here
Once u are finished:
1.- Turn off ur phone
2.- Press volume up + volume down (at the same time, DONT PRESS POWER BUTTON) and plug ur phone into ur computer (the phone will go into QDL mode)
3.- Open msmdownloadtools mclaren
4.- Press START
5.- Wait for it to finish
You will have H2OS installed... now install OOS
This should work for you, since i was on the same boat as you. Good Luck!

efebe said:
i had the same issue, and i was able to resurrect my phone, here's what i did:
Download both files from here
Once u are finished:
1.- Turn off ur phone
2.- Press volume up + volume down (at the same time, DONT PRESS POWER BUTTON) and plug ur phone into ur computer (the phone will go into QDL mode)
3.- Open msmdownloadtools mclaren
4.- Press START
5.- Wait for it to finish
You will have H2OS installed... now install OOS
This should work for you, since i was on the same boat as you. Good Luck!
Click to expand...
Click to collapse
MSMTools stuck on this
https://imgur.com/qiaF8oh

Vlodayax said:
MSMTools stuck on this
https://imgur.com/qiaF8oh
Click to expand...
Click to collapse
Click "stop" then "exit" and kill the program and start over. Keep trying. I was down a whole day and a half after trying to flash a Rom. I made it worst after wiping the system and the MSM tool saved my a$$.
Sent from my OnePlus6T using XDA Labs

Razer phone 2 MR3 build posted on dev site

MR3 build as posted
https://developer.razer.com/razer-phone-dev-tools/factory-images/

These instructions assumes that you have platform tools and the Google ADB drivers installed. If you need instructions for that, look here:
Google ADB Drivers & Androind SDK Platform Tools instructions
To do an upgrade/dirty flash do the following:
Extract the Zip, If you dont want root, skip to step 8
Copy boot.img to you phone
Open Magisk Manager app and Install > Patch Image
Copy "magisk_patch.img" from your phone's Downloads to the folder you extracted the ROM to.
Edit/Copy the flash_all.bat (or .sh on Linux/Mac)
Find the lines 54 & 55 with:
Code:
%fastboot_cmd% flash boot_a boot.img
%fastboot_cmd% flash boot_b boot.img
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
Find line 71(73 if you did the steps above) with:
Code:
%fastboot_cmd% erase userdata
Change it to:
Code:
rem %fastboot_cmd% erase userdata
Save the batch script file
Reboot your phone and hold the 'Volume Down' button until your phone boots into "Fastboot Mode"
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.

They finally did it LOL.
Hope Android 10 or even 11 on their update roadmap.

ah! finally I can upgrade without losing all my data.

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://forum.xda-developers.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...

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.

is there a changelog for the new mr3 build?

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:
Google ADB Drivers & Androind SDK Platform Tools instructions
To do an upgrade/dirty flash do the following:
Extract the Zip, If you dont want root, skip to step 8
Copy boot.img to you phone
Open Magisk Manager app and Install > Patch Image
Copy "magisk_patch.img" from your phone's Downloads to the folder you extracted the ROM to.
Edit/Copy the flash_all.bat (or .sh on Linux/Mac)
Find the lines 54 & 55 with:
Code:
%fastboot_cmd% flash boot_a boot.img
%fastboot_cmd% flash boot_b boot.img
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
Find line 71(73 if you did the steps above) with:
Code:
%fastboot_cmd% erase userdata
Change it to:
Code:
rem %fastboot_cmd% erase userdata
Save the batch script file
Reboot your phone and hold the 'Volume Down' button until your phone boots into "Fastboot Mode"
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

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!

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

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).

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?

I've had this same issue. I think it's something with Windows 10 Update 2004. What I ended up doing was getting a usb drive and making a boot disk with FWUL on it. Which makes a live linux disk with all the tools you need.