Database Info

Oem locked, frp block, and drk help

Hey guys. I'm in a hell of a bind and could use some help.
My Galaxy Note 5 (N920T, rooted) was running fine on this ROM: https://forum.xda-developers.com/tm...m-qc6-lite-rom-bloated-knoxed-odexed-t3598686 ; however, I had disabled OEM unlock at one point to try and fix a random app I was playing with. The battery died not long after, causing the phone to reboot. On power, it failed to boot due to custom binary block from FRP, so I decided to try and run the usual troubleshooting of flashing a stock ROM via Odin. Stock images will flash (tried 5.1.1, 6.1, and 7); however, when they try to install I get the error for no DRK. Sometimes I'll also get a dm-verity error as well... So I then tried to flash TWRP or any recovery via Odin to let me fix this issue; however, any custom recoveries I try to flash are being blocked by FRP.
So, I'm in a loop. I can't use my initial ROM because FRP, however I also can't install a stock ROM because of missing DRK, AND I can't fix the DRK or verity errors because I can't install a recovery capable of doing so because of FRP.
IMEI is intact when I look into Download mode, but I can't seem to get anything to work. I've tried the FRP Tool and crack, but that gives me FRP blocks as well (USERDATA).
Am I boned?

B U M P
Anyone?

same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*

You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.

Metabolic12 said:
You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.
Click to expand...
Click to collapse
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.

x24veggie said:
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.
Click to expand...
Click to collapse
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.

craig198 said:
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.
Click to expand...
Click to collapse
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP

craig198 said:
same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*
Click to expand...
Click to collapse
No. It started because you didn't back up your phone properly with twrp before going flash crazy
---------- Post added at 08:52 AM ---------- Previous post was at 08:47 AM ----------
x24veggie said:
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP
Click to expand...
Click to collapse
https://www.google.ca/amp/s/forum.x...to-solve-dm-verity-verification-t3293306/amp/ have you tried this? If we can figure this out please don't ever play with oem or have a stock recovery ? that's your security blanket

[Bricked] One of the harder ones =|

I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Whole story:
This whole episode began when I wanted to install Magisk to use MagiskManager's HideMe feature. This required me to install TWRP recovery which inturn lead me to unlock my bootloader in the process, straightforward and went off nicely. Now it was time to gain superuser which I already had done before on another device, installing SuperSU through TWRP recovery was painless but after booting found out MagiskManager needs Magisk Root to work. I then followed Android Exlpained's article to do so. Running unSU through recovery went smoothly but running Magisk didn't, on the initial run I was prompted to use Adrian DC's BootBridge which after removing a few Assert lines ran nicely. However there was no root install, SuperSU was removed though.
At the time I wasn't sure what exactly I was doing and ended up soft-bricking by flash boot through TWRP, at this time FRP was unlocked. After many many hours I restored to stock firmware by using YMNDLZ's guide. I used BLN-L24C567B370(OTA-MF-FULL) for the img files then proceed to flash the vendor.img using TWRP and the rest (boot.img, recovery.img, system.img) using fastboot in that order as instructed. The only part which didn't work was the forced update, it always failed at 5% however after more hours going recovery mode (now stock) wiping the cache and data/factory reset did the trick (Note: my model showed BLN-L24C567B369). I proceeded to reinstall TWRP, installed MagiskManager, tried to install Magisk 16.0 which ran but didn't root me but was fine because MagiskManager's download worked. I then thought since I went through all this trouble might as well install a custom rom, EliteRom was my ROM of choice. At this point I had logged in with my gmail credentials FRP was now locked.
*Before further action was taken I took the precaution to backup my current stable stock ROM after installing EliteROM but before booting*
The steps to install EliteROM went by flawlessly, installed EliteTWRP reboot into it, ran EliteROM
went through the setup without any hiccups. However up system restart I the ROM wouldn't boot leading me to boot into my recovery only to be prompted for an encryption password (???). Since I didn't recall setting one, couldn't boot into the OS, and FRP was locked I couldn't read my own internal storage. So I reformatted the internal storage and tried what had worked before, flashing the img files using TWRP then booting into stock recovery wiping cache and data/hard reset. . . this did not work. And here I am FRP locked so fastboot isn't useful (I think?), stock recovery doesn't work, eRecovery fails connection, and force update still fails at 5% with "Software install failed!".
Click to expand...
Click to collapse
Lemme know if there is any insight anyone can provide and thanks in advance.

This problem has been solved?

MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
you have to follow only xda methods to root or change to custom rom. i have never heard about flashing stock images from twrp. i think u didn't followed elite rom instructions clearly. you need to formate data then reboot to recovery then wipe everything then flash the os in this way you won't get encription error. anyway now your frp is locked so there is no way to flash twrp so download all the available firmwares for your phone oeminfo then do flashing via dload you will get it worked.
even i was also once stuck with elite rom. i didn't liked it because missing apps icon and forgetting permission. i tried to go back to stock but stuck at 5% error. then went to google searched stock rom for honor 6x india and downloaded nearly 3 roms last one worked helped me to get back to stock.
never flash system images boot,vendor etc from fastboot and twrp unless you are on emui8 and going to try gsi roms.

hey i cant revert back to stock rom. it fails to get package from server. does jio voice calling works on this device?? if no then plz guide me how to go back to stock rom..

MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
Register for update using firmware finder and Puts dns address in the router settings and then use erecovery

Need help recovering my phone from bootloop after trying to update custom rom

Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.

Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc

Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now

twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.

Why nobody use orangefox?

is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable

joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.

Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you

Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.

CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?

[Q] [Locked OP6] Bootloop after upgrading to 10.3.0 - how to recover without format

My dad got the OTA update to 10.3.0 on xmas day and installed it. However the phone is now stuck on boot logo. He has a locked phone just as it came out of the box (ie no TWRP, no OEM unlock, no root).
I am quite experienced with installing custom ROMs but with locked phones I am lost. Is there anyway to recover the device without deleting data / factory reset? This is because my dad has quite a lot of pics on the device that are not backed up (yeah I know...).
Things I've tried so far:
- reboot holding power button + volume up
- boot flash twrp from fastboot - no permission due to phone being locked
- in stock recovery I do not get access to device via cable
- installed Tool all in One - it sees phone via fastboot
I always use the Stock Fastboot ROMs for OnePlus 6 myself to recover from soft bricks but this wipes data so no option here. Unless there is a way to install parts of ROM? Any other tips or ideas from the awesome XDA community? :good:
Btw this is the update he installed:
Screenshot of update that was installed

If you boot on twrp, it does not ask for the pin code to access the data?
Maybe try the last twrp for OOS 10.3.0 : ( https://androidfilehost.com/?fid=4349826312261678088 )
Use command : fastboot flash boot twrp-3.3.1-16-enchilada-Q-mauronofrio.img
Try flash a new boot img :
Stock boot 10.3 img
https://drive.google.com/open?id=1w44cUg815g-H1h_6gObUVPLDTc_dtiMX

The phone is not unlocked and therefore has no TWRP recovery. This is my problem, if it was unlocked I would have figured out a way to fix it.
PS it does ask for pincode when accessing stock recovery

I'm not sure if this works on locked bootloaders but try switching boot slots using fastboot.

Couple of weird things:
-you don't need an unlocked bootloader for fastboot to boot back into the system
-the dual partition was designed precisely to prevent things like this from happening. When an update fails, you are supposed to roll back to the old slot you were on previously.
Anyway, since you are able to boot to fastboot, can you try to get to stock recovery again from fastboot and see if you can boot up to system from there?

Hey
You can try to change the boot slot using fastboot mode
It can help uh maybe
Its worth to try

awaiz said:
Hey
You can try to change the boot slot using fastboot mode
It can help uh maybe
Its worth to try
Click to expand...
Click to collapse
When I try to set it to slot A (it's B now) it says device does not support slots which is weird as 'fastboot getvar current-slot' does show it using slot B right now.
When I try to set it to B (ie current slot) it says: FAILED (remote: 'Slot Change is not allowed in Lock State').

awaiz said:
Anyway, since you are able to boot to fastboot, can you try to get to stock recovery again from fastboot and see if you can boot up to system from there?
Click to expand...
Click to collapse
When I reboot to stock recovery it gives two options:
- Wipe Data and Cache
- Advanced
There are two reboot options under Advanced:
1. Reboot to fastboot
2. Reboot to recovery
2nd option just boots it back to this same recovery. Boot to fastboot works as well. So there is no option to reboot the device.
Perhaps I can try to flash the stock ROM (kinda of dirty flash) but again not sure if that works on locked phone.

https://www.androidexplained.com/change-active-partition-slot/

JagDave said:
https://www.androidexplained.com/change-active-partition-slot/
Click to expand...
Click to collapse
This doesn't work unfortunately on a locked device.

I found the fix and it was very simple: in Recovery under Wipe Data and Cache it has the option to delete 1. System Settings 2. Cache 3. Wipe all (incl Data).
I choose option 1 (System Settings) and after that it booted and I had to set up phone again as with a new install but all data on sd card had remained. I did lose all apps but that is a very minor thing.
Thanks for everyone who thought along with me. We got there in the end

help me.. my op6 stuck in bootlogo.. how can i run my phone back. it is still locked never rooted..

Alamin4736 said:
help me.. my op6 stuck in bootlogo.. how can i run my phone back. it is still locked never rooted..
Click to expand...
Click to collapse
Bro..Use the Msm tool to get recover coz you have the locked bootloader

roel1976 said:
I found the fix and it was very simple: in Recovery under Wipe Data and Cache it has the option to delete 1. System Settings 2. Cache 3. Wipe all (incl Data).
I choose option 1 (System Settings) and after that it booted and I had to set up phone again as with a new install but all data on sd card had remained. I did lose all apps but that is a very minor thing.
Thanks for everyone who thought along with me. We got there in the end
Click to expand...
Click to collapse
I am facing similar problem with my OP5. When I boot in recovery, it asks for pattern to unlock. But does not accept any pattern. In the absence of pin, it gives option to Wipe Data. Will I get similar options like you did ? I am hoping to save my data.

Bricked my Note7pro, Need help!

Hello!
I tried installing TWRP which i successfully did (I was planning to install a custom rom) but then I delete everything on wipe section these are:
•Dalvik
•Cache
•Vendor
•Data
After wiping these, I accidentally turned off the phone and now it can't boot to recovery and says "The system has been destroyed". Good thing is I can still go into fastboot mode.
I tried flashing stock MIUI ROM but it keeps getting error on MiFlash. I can confirm the bootloader is unlocked and I also tried other ROMs but I feel like the phone won't accept it.
I keep getting error whenever I flash even if I use original China ROM.
I know messed it up but please.....
Please save my poor phone.

kiyu07 said:
Hello!
I tried installing TWRP which i successfully did (I was planning to install a custom rom) but then I delete everything on wipe section these are:
•Dalvik
•Cache
•Vendor
•Data
After wiping these, I accidentally turned off the phone and now it can't boot to recovery and says "The system has been destroyed". Good thing is I can still go into fastboot mode.
I tried flashing stock MIUI ROM but it keeps getting error on MiFlash. I can confirm the bootloader is unlocked and I also tried other ROMs but I feel like the phone won't accept it.
I keep getting error whenever I flash even if I use original China ROM.
I know messed it up but please.....
Please save my poor phone.
Click to expand...
Click to collapse
which error r u getting

kiyu07 said:
Hello!
I tried installing TWRP which i successfully did (I was planning to install a custom rom) but then I delete everything on wipe section these are:
•Dalvik
•Cache
•Vendor
•Data
...
Click to expand...
Click to collapse
1. The real error is not turning off the phone. The real error is wiping Vendor. Why on earth would you want to do that? You should never wipe vendor manually. If you just wiped data and dalvik/cache (which is all that you should wipe) you could turn off your phone one thousand times, and the ROM would still boot when you turn on the phone again.
2. You say you tried flashing stock MIUI - but you have not indicated which kind of stock MIUI you have tried flashing (ie, are you trying to flash a fastboot ROM or a zip?).
3. What error are you getting from Mi Flash?

DarthJabba9 said:
1. The real error is not turning off the phone. The real error is wiping Vendor. Why on earth would you want to do that? You should never wipe vendor manually. If you just wiped data and dalvik/cache (which is all that you should wipe) you could turn off your phone one thousand times, and the ROM would still boot when you turn on the phone again.
2. You say you tried flashing stock MIUI - but you have not indicated which kind of stock MIUI you have tried flashing (ie, are you trying to flash a fastboot ROM or a zip?).
3. What error are you getting from Mi Flash?
Click to expand...
Click to collapse
How can he flash a custom rom without wiping vendor???

Sourab debnath said:
How can he flash a custom rom without wiping vendor???
Click to expand...
Click to collapse
Easily. Each ROM will flash its own vendor. The process of flashing to the partition involves wiping the partition and then immediately flashing. So, there is absolutely no point in wiping vendor manually. On the contrary, you can already see the pitfalls of doing so (a similar situation will occur if the new ROM that you want to flash doesn't flash its own vendor - lots of tears!!).

you should try flashing again twrp and then flash the miui zip...

thank you for all the help. got it fixed by using miflashpro, the normal one doesn't flash anything on my phone. i got the stock rom flashed then i was able to get twrp and PE10 working!

kiyu07 said:
Hello!
I tried installing TWRP which i successfully did (I was planning to install a custom rom) but then I delete everything on wipe section these are:
•Dalvik
•Cache
•Vendor
•Data
After wiping these, I accidentally turned off the phone and now it can't boot to recovery and says "The system has been destroyed". Good thing is I can still go into fastboot mode.
I tried flashing stock MIUI ROM but it keeps getting error on MiFlash. I can confirm the bootloader is unlocked and I also tried other ROMs but I feel like the phone won't accept it.
I keep getting error whenever I flash even if I use original China ROM.
I know messed it up but please.....
Please save my poor phone.
Click to expand...
Click to collapse
We'll need one tar or fastboot file of miui extract it and place it in c drive under folder name note 7 pro then again go in fastboot mode open mi flash tools search for the same then no error whole process of flashing will take 10 to 15 minutes once done will reboot your phone immediately and will sure work I messed. Up my device 100 times went to Xiaomi service centre many times but due to their errogance I came back did it myself no issues it's easy but you have to try