Unable to mount /Persist - OnePlus 3 Questions & Answers

Hey folks,
I need help.
I am getting "failed to mount '/persist' (invalid argument)"
So far i tried
1. Mega unbrick for oneplus 3t.
2. Placed persist.img in internal storage and through terminal ran this dd if=/sdcard/persist.img of=/dev/block/by-name/persist
I am still getting mount error and my sensors e.g. ambient, magnetic, proximity are not working
Please help

try putting the persist image into the adb/ fastboot folder the reboot the phone into fastboot mode the flash the persist image in fastboot mode

have you solved your issue yet

kallum7 said:
try putting the persist image into the adb/ fastboot folder the reboot the phone into fastboot mode the flash the persist image in fastboot mode
Click to expand...
Click to collapse
That didn't help.
Faced, FAILED (remote: Partition flashing is not allowed)
kallum7 said:
have you solved your issue yet
Click to expand...
Click to collapse
Yeap, Thanks to @ppajdek.
He recommended to flash Marshmallow via MSM.

Related

/sdcard not mounting

dear all
i am using GN 4.2.2 stock
at the moment i can go to fastboot and i flash clockwordmod recovery v6.0.1.9
i did this because my phone startted to reboot
at the GB logo
.
now problem is i cant flash ROM to sdcard.
here is the output
=================
sending 'bootloader' (2308 KB)...
OKAY [ 0.260s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.435s
==========================
sending 'radio' (12288 KB)...
OKAY [ 1.353s]
writing 'radio'...
FAILED (status read failed (Too many links))
finished. total time: 2.060s
===================================
in recovery when i am trying to mount sdcard.
===============
Error mounting sdcard
Are u trying to flash the rom immediately after unlocking the bootloader?? When the bootloader unlock is performed, the data is wiped completely.. Now u have to restart the device to mount the sd card again in recovery..
Sent from my Galaxy Nexus using xda app-developers app
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Zepius said:
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Click to expand...
Click to collapse
fastboot commands i tried are
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
i cant flash any thing
i am stuck
is my sdcard gone
????
amith007 said:
Are u trying to flash the rom immediately after unlocking the bootloader?? When the bootloader unlock is performed, the data is wiped completely.. Now u have to restart the device to mount the sd card again in recovery..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
yes i unlocked bootloader, and yes all data must have been wiped out.
i restarted into recovery but with recovery i cant mount the sdcard
!!!!!
zakisays said:
fastboot commands i tried are
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
i cant flash any thing
i am stuck
is my sdcard gone
????
Click to expand...
Click to collapse
do you have the files in the same directory with your fastboot.exe?
you could also boot into your custom recovery and use adb to push a rom to your phone.
zakisays said:
yes i unlocked bootloader, and yes all data must have been wiped out.
i restarted into recovery but with recovery i cant mount the sdcard
!!!!!
Click to expand...
Click to collapse
Perhaps you didnt read the post, so I will quote it here:
Zepius said:
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Click to expand...
Click to collapse
Zepius said:
do you have the files in the same directory with your fastboot.exe?
you could also boot into your custom recovery and use adb to push a rom to your phone.
Click to expand...
Click to collapse
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
can you sent me the link to the steps for custom recovery & adb push
let me try it
thanks in advance
zakisays said:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
can you sent me the link to the steps for custom recovery & adb push
let me try it
thanks in advance
Click to expand...
Click to collapse
first, flash cwm 6.0.2.3.
look in problem can happen section in my thread
samersh72 said:
first, flash cwm 6.0.2.3.
look in problem can happen section in my thread
Click to expand...
Click to collapse
i gave the following command
H:\Galaxy Nexus (yakju)>adb -d push "H:\Galaxy Nexus (yakju)\Stock-Unroot Jelly
Bean GNex GSM.zip" /sdcard/
its almost 2 hours now the command hasnt finished executing, hope all is going ok
ok i cancelled the previous command .
rebooted to recovery , mounted /data and /system
then reran push command.
got the zip file into sdcard
then tried installing , error generated
finding update package
opening update package
installing update
Installation aborted
!!!!!
please help
thanks
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Zepius said:
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
well i followed the steps.
i got error as below
===================
H:\brick\xda-24-3-2013\yakju-jdq39>fastboot.exe flash bootloader bootloader-magu
ro-primelc03.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.260s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.507s
================================
i hope now its clear what i am facing.
i can boot to fastboot and to recovery , but cant do anything else
if i flash something then the "Too many links error" comes
thanks for the help , is there anything else i can try
========================
ok i found something interesting
when i flash something i get the error " Too many links"
then when i run fastboot.exe devices , i get
???????????? fastboot
and after reboot i get
H:\brick\xda-24-3-2013\yakju-jdq39>fastboot.exe devices
My IEMI number fastboot
y is this happening
*sigh* ...
Op, uninstall all drivers, reboot your system;
Connect device in fastboot to PC, manually update drivers, disconnect device, reboot PC
Connect device again, flash recovery, after it finishes, disconnect USB, use volume keys to "reboot recovery", reconnect USB, manually update drivers again
'adb devices' should return your SN
'adb push ROM.zip /sdcard/' or if that doesn't do it, 'adb push ROM.zip /data/media/'
Sent from my Nexus

Probleems, bootloop and recovery/system issue (BRICKED!)

Hi help,
I did something wrong with firmware flash.
So phone is bricked.
I followed on XDA the OP3 Unbrick forum, now my phone can turn on.
but I have an older bootloader. Also I het failed, when I press recovery, I can also only connect with fastboot and not ADB.
Help.
HELP ME
YourTheBest said:
HELP ME
Click to expand...
Click to collapse
flash this TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21835&task=get
First go into fastboot then flash by typing fastboot flash recovery <name of the twrp you downloaded above><a
You can now flash latest OOS from TWRP
strumaticjoker2 said:
flash this TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21835&task=get
First go into fastboot then flash by typing fastboot flash recovery <name of the twrp you downloaded above><a
You can now flash latest OOS from TWRP
Click to expand...
Click to collapse
I did that, thanks.
Doesn't work. I can do fastboot boot twrp.img
but when I install OOS or other ROM i get this error: ERROR 7 *unknow command and
failed to mount /cache (invalid argument)
failed to mount /system (invalid argument)
[email protected]#$%^&*()_
I get stupid error: when phones start/reboot.
md5 checkum failed
boot failed
recovery failed
My whole #!#$$#@ life failed.
Had the same few nights ago. Check the forum for the unbrick guide - method 2.
orlexx said:
Had the same few nights ago. Check the forum for the unbrick guide - method 2.
Click to expand...
Click to collapse
Then I lost al my WhatsApp messages... Right?
I can see the data files.
I still have issues!
Help

Stuck after trying to upgrade to Pie.. worried I bricked it.

Having an issue with my XL. I've been on LOS 15.1 for a while and wanted to try out the new Pie image. I made a backup and fired up fastboot as usual. I left the -w tag on as I wanted a complete wipe. Fastboot failed while wiping userdata and now bootloops twice before dumping me in stock recovery. I am completely unable to format data while in stock recovery. Same when I boot TWRP through the PC. Stock recovery says it can't write a new EXT4 partition and TWRP says I have no internal storage, then throws a ton of errors. Flashing OEM images from Google (Oreo or Pie) results in the same thing.
Any ideas? For the first time in years I am stumped.
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
caain said:
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
Click to expand...
Click to collapse
Is your platform tools updated to the newest one?.
Edit I thought I was on the pixel 2 forum.
Could try to repartition the storage using a method similar to this one for the nexus 7? https://forum.xda-developers.com/nexus-7-2013/general/guide-repartition-nexus72013-to-t3599907
You would need to figure out the proper partition table for the Pixel though.
If you're 100% sure your platform-tools are fresh, you've got me stumped as well. I ran into tons of errors and such due to out of date tools when flashing Pie - obviously updating the tools fixed the issue.
Well I'd try external Type-C USB drive it enables external storage even if internal isn't working and fastboot flash your backup.
caain said:
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
Click to expand...
Click to collapse
i got the same problem, i just downloaded the Platform-Tools and opened it in PowerShell and executed flash-all script and it worked
Flash all script is good but I'd rather use external storage .. it's nice to know that there's more than one way to fix the problem outside of platform tools
I had issues with Pixel before and the multi partition thing screwed me up, but the Unified_Android_ToolKit was able to fix it for me. Worth a try for sure. Download Google Factory Image and use the tool.
Thanks for all the help everyone. Lots of good ideas here that I'll save for next time. Ten years tinkering with phones and I've never gotten this stuck.
In the end I flashed back to the factory Pixel XL image (October 2016). Like the previous attempts, it failed on accessing userdata. I used fastboot to flash a userdata.img file again, which similarly failed but somehow the phone still booted after about 20 minutes.
I found similar threads for other phones where people were in the same situation, but nothing they tried did the trick.
Back up and running now.
Sent from my Pixel XL using Tapatalk
Very odd. Based off your last post I'm going to assume you are not sure what triggered the issue?

device unable to boot Error - mdtp image is corrupted

Hi there,
I have a problem i was try to root my phone.
Now i dont have access to ADB but only fastboot works.
If i start my phone it goes on fastboot mode, and if i try "fast boot twrp-3.3.0-0-daisy.img" i get the error "device unable to boot Error - mdtp image is corrupted"
Can some one help me out, if tried to download the image again but without success..
You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.
a1291762 said:
You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.
Click to expand...
Click to collapse
Sorry im a little bit noob, but how it works:
flastboot flash a?
fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.
Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
a1291762 said:
fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.
Click to expand...
Click to collapse
mj2o said:
Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
Click to expand...
Click to collapse
No OS installed is maybe cause the last rom that you flashed was not flashed in the right slot or correctly flashed.
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.
SubwayChamp said:
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.
Click to expand...
Click to collapse
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.
mj2o said:
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.
Click to expand...
Click to collapse
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.
I have the same problem, what you have did to fix? please
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
hi
same issue here @mj2o: Can you please provide a link to the site in English; it all in Chinese and I cannot read it
Thanks
mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
SubwayChamp said:
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.
Click to expand...
Click to collapse
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.
BenG7 said:
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.
Click to expand...
Click to collapse
Why do you want to flash the bootloader, what is the issue?
Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Device unable to boot. Error - mdtp is corrupted
BenG7 said:
Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Click to expand...
Click to collapse
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread
Thanks SubwayChamp,
Will try as advised and keep you updated.
I m going to look for the fastboot rom for my daisy.
SubwayChamp said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread
Click to expand...
Click to collapse
@SubwayChamp
dit it and when I
Code:
fastboot reboot
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
[EDIT]
realised I can
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
and I can flash the twrp-installer-daisy-3.3.1-0-offain.zip
but if I want to reboot; it says
Code:
No OS installed! Are you sure you wish to reboot?
so I went on with flashing lineageos 16
but at the end of the flash, I get
Code:
Failed to mount '/system' (permission denied)
please advise
BenG7 said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use and
@SubwayChamp
dit it and when I
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
Click to expand...
Click to collapse
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.
SubwayChamp said:
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.
Click to expand...
Click to collapse
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!
BenG7 said:
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!
Click to expand...
Click to collapse
This is exactly what I tried to tell you: your issue concerning to this thread was solved.
Now you have an issue regarding how to flash and boot to system attempting to install LOS. TWRP is perfectly capable to mount/remount or unmount partitions if needed, no need an action from the user, this is not the reason why you are not booting but the method and steps is discussed more properly in the same thread.
From here you can take one of hese three routes:
- To insist with trying to flash LOS.
- Flash other rom or a previous known working rom.
- Return completely to stock by flashing a full global rom.
Just I could recommend that for the future when you flash a stock rom take a backup of the most important partitions (without userdata) this could avoid that you need to use EDL anymore.

[GUIDE][UNBRICK] How unbrick your bootloop in MERLIN after flashing TWRP (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)

If you try to flash the file misc.bin your device can be in bootloop forever, please follow this guide to fix it.
It works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Method 1:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
If you can see your device in adb recovery mode, you have to erase misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Method 2:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
And then reboot to bootloader:
Code:
adb reboot bootloader
And then check if it is detected in fastboot mode:
Code:
fastboot devices
If you can see your device in fastboot mode, you have to erase misc partition:
Code:
fastboot erase misc
Keep attention, if you try to format misc partition, you will get this error: Formatting is not supported for file system with type 'raw data'.
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Good luck !
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
VD171 said:
If you boot your device and it keeps in a black screen because outdated TWRP, please follow this guide.
It works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected:
Code:
adb devices
If you can see your device in adb recovery mode, you have to format misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will FORMAT any other partition and it can brick your device forever and cause more damages.
Good luck !
Click to expand...
Click to collapse
OR they can just use
adb reboot bootloader
boot to fastboot and flash the stock image of the partition which is corrupted.
Communos said:
OR they can just use
adb reboot bootloader
boot to fastboot and flash the stock image of the partition which is corrupted.
Click to expand...
Click to collapse
Please, read the guide. This guide is for people who flashed misc.bin partition from the outdated TWRP.
This misc.bin partition from the outdated TWRP, will bootloop the device forever in recovery mode.
There is NO misc partition on stock image. So, you have to erase misc partition for stops with bootloop in recovery.
Thanks! If I knew this a few weeks ago it would have been helpful, But I fixed it with MiTool V2
VD171 said:
Please, read the guide. This guide is for people who flashed misc.bin partition from the outdated TWRP.
This misc.bin partition from the outdated TWRP, will bootloop the device forever in recovery mode.
There is NO misc partition on stock image. So, you have to erase or format misc partition for stops with bootloop in recovery.
Click to expand...
Click to collapse
Well, I've been in this situation twice or thrice, first I fixed by flashing full stock rom, rest of the times flashing stock recovery and stock boot fixed it for me.
Communos said:
Well, I've been in this situation twice or thrice, first I fixed by flashing full stock rom, rest of the times flashing stock recovery and stock boot fixed it for me.
Click to expand...
Click to collapse
As I've said, if you've flashed misc.bin from the outdated TWRP, just flashing stock recovery or stock boot will not fix the problem.
For fixing it, you have to erase misc partition. If it doesn't help you, please, go away and let it help who wants help.
Nice job and see you later.
VD171 said:
If you try to boot your device and it keeps in a black screen because outdated TWRP, please follow this guide.
It works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Method 1:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
If you can see your device in adb recovery mode, you have to format misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will FORMAT any other partition and it can brick your device forever and cause more damages.
Method 2:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
And then reboot to bootloader:
Code:
adb reboot bootloader
And then check if it is detected in fastboot mode:
Code:
fastboot devices
If you can see your device in fastboot mode, you have to format misc partition:
Code:
fastboot format misc
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will FORMAT any other partition and it can brick your device forever and cause more damages.
Good luck !
Click to expand...
Click to collapse
thanks sooo much
imranbinlatif said:
thanks sooo much
Click to expand...
Click to collapse
Good job, my friend.
You are welcome
VD171 said:
If you try to boot your device and it keeps in a black screen because outdated TWRP, please follow this guide.
It works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Method 1:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
If you can see your device in adb recovery mode, you have to erase misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Method 2:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
And then reboot to bootloader:
Code:
adb reboot bootloader
And then check if it is detected in fastboot mode:
Code:
fastboot devices
If you can see your device in fastboot mode, you have to erase misc partition:
Code:
fastboot erase misc
Keep attention, if you try to format misc partition, you will get this error: Formatting is not supported for file system with type 'raw data'.
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Good luck !
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
Click to expand...
Click to collapse
Hey there, i erased the Misc partition, it's still bootlooping,
I tried to un-brick my device from the Xiaomi Mod Tool,
Yes i did try flashing a outdated TWRP image,
It got hard bricked, and i tried to fix it,
through some good luck, i managed to get into "fastboot"
And, nothing, it just got soft bricked,
I guess that's proggress?
My device: merlinnfc (Redmi Note 9/10X 4G)
TheMagnificent_Y said:
Hey there, i erased the Misc partition, it's still bootlooping,
I tried to un-brick my device from the Xiaomi Mod Tool,
Yes i did try flashing a outdated TWRP image,
It got hard bricked, and i tried to fix it,
through some good luck, i managed to get into "fastboot"
And, nothing, it just got soft bricked,
I guess that's proggress?
My device: merlinnfc (Redmi Note 9/10X 4G)
Click to expand...
Click to collapse
If you have access to fastboot and erasing misc did not work, simply flash the entire stock rom you were on through MiFlash.
TheMagnificent_Y said:
Hey there, i erased the Misc partition, it's still bootlooping,
I tried to un-brick my device from the Xiaomi Mod Tool,
Yes i did try flashing a outdated TWRP image,
It got hard bricked, and i tried to fix it,
through some good luck, i managed to get into "fastboot"
And, nothing, it just got soft bricked,
I guess that's proggress?
My device: merlinnfc (Redmi Note 9/10X 4G)
Click to expand...
Click to collapse
Erasing misc only works if you are frozen in a black screen after flashing misc partition.
Recovery partition can't break boot.
Probably your problem is vbmeta.
Vbmeta can break the boot.
Did you flash it too?
I flashed the entire ROM,
So yes,
Every single partition, except misc since it's gone now,
When i say "Every Single Partition", I mean every single one,
this includes,
Scp1/2
super
..etc.
TheMagnificent_Y said:
I flashed the entire ROM,
So yes,
Every single partition, except misc since it's gone now,
When i say "Every Single Partition", I mean every single one,
this includes,
Scp1/2
super
..etc.
Click to expand...
Click to collapse
Misc partition is not present in original stock rom.
It contains a variable data/parameter for boot.
Did you solve the bootloop after flash full rom?
No,
Here are the full details:
1. I tried flashing the recovery partition, Nothing.
2. I used an unnofficial TWRP ROM that hard bricked my device, this includes the following partitions:
Misc Opt Vbmeta Recovery
3. I managed to get into ADB recovery, i got into fastboot, then flashed the stock rom.
4. Boot loop
TheMagnificent_Y said:
No,
Here are the full details:
1. I tried flashing the recovery partition, Nothing.
2. I used an unnofficial TWRP ROM that hard bricked my device, this includes the following partitions:
Misc Opt Vbmeta Recovery
3. I managed to get into ADB recovery, i got into fastboot, then flashed the stock rom.
4. Boot loop
Click to expand...
Click to collapse
You need to avoid the misc partition.
If you've flashed it, you REALLY need to erase it.
Or, it will make your device to enter in recovery forever.
Vbmeta needs to be flashed with disababled verification.
Here you can find safe and secure vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
Or, it will detect modification on partitions and will reboot the device forever.
I think Opt doesn't change anything.
I'm not sure, but I think it only matter for devices without vbmeta partition. (I'M NOT SURE.)
Because it modifies the system, and obviously you will get in a bootloop.
If you want to modify the system, you need to debloat your system before.
Try to flash the whole system again.
Or just try to flash the whole rom again.
I've done that twice, and i deleted misc afterwards,
What about...:
fastboot flashall -w ?
Shouldn't that help flashing the system?
Also what does Vbmeta verify?
Thanks.
PS: I tried flashing the un-official and official versions, both leave a brick, and nothing really changes, i haven't tried your "Patched" version tho.
TheMagnificent_Y said:
I've done that twice, and i deleted misc afterwards,
What about...:
fastboot flashall -w ?
Shouldn't that help flashing the system?
Also what does Vbmeta verify?
Thanks.
Click to expand...
Click to collapse
I'm not sure.
Just flashing the system should solve it.
Or just flashing the whole rom using the flashing scripts inside the original stock rom.
Vbmeta checks if boot, recovery and dtbo partitions keeps untouched and unmodified.
I flashed the whole rom using the Xiaomi Mod Tool which is coded in java script,
i'll try to flash your "Patched" vbmeta image and see if that helps, if not, i'll re-flash the stock rom.
TheMagnificent_Y said:
I flashed the whole rom using the Xiaomi Mod Tool which is coded in java script,
i'll try to flash your "Patched" vbmeta image and see if that helps, if not, i'll re-flash the stock rom.
Click to expand...
Click to collapse
Flashing the whole stock rom, certainly solves everything.
And then, if you want TWRP again, try this first: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/
Good luck

Categories

Resources