Database Users

Perfect Recovery 4.0.0.5 by Genokolar

I am posting this recovery on behalf of genokolar. No ads in the recovery for this version
Change log:
1. EXT4 support.
2. Large file system support (e.g. /data > 2G).
3. Updated reboot recovery mode.
To install (you need root):
1. Backup /cust_backup/image/recovery.img
2. Download, extract and place the recovery.img into /cust_backup/image/
3. Done.
To go to recovery:
1. Power off
2. Hold Vol+ and Power buttons to power on (hold both buttons UNTIL you see the recovery)
EDIT: If your phone won't boot with this recovery please try this. Credit to stockwell.

thank you and thank geno

How did it become so fast to 4.x.x?
I mean official is at 3.x.x?

cirnocirno said:
How did it become so fast to 4.x.x?
I mean official is at 3.x.x?
Click to expand...
Click to collapse
Official is 4.0.0.5, See the makefile on github (Line 29):
https://github.com/CyanogenMod/android_bootable_recovery/blob/gingerbread/Android.mk
Thanks for the update Geno. Maintaing the current recovery version will help with RM integration.

Argh... just installed 3.0.2.8 recovery image today, should search for new version here first...
Anyway, thank you and genokolar

Thanks for this will update now

Does this backup the baseband firmware (or what stockwell mentioned that the Perfect Recovery didn't do before)?

andreasha said:
Does this backup the baseband firmware (or what stockwell mentioned that the Perfect Recovery didn't do before)?
Click to expand...
Click to collapse
No, my concern was actually that it DID backup both baseband and emmcboot.mbn, which could potentially brick if these files are corrupted on a bad restore.
This version still does this, though no one seems to have had this happen to them. I think since nandroid hashes the backups and checks them when restoring the problem only really would be if your phone was turned off while restoring, and even then bootloader mode might still work fine if those files are damaged.

Genokolar can you please make a self installer so that we can upgrade through previous perfect recovery.Thanks.

stockwell said:
No, my concern was actually that it DID backup both baseband and emmcboot.mbn, which could potentially brick if these files are corrupted on a bad restore.
This version still does this, though no one seems to have had this happen to them. I think since nandroid hashes the backups and checks them when restoring the problem only really would be if your phone was turned off while restoring, and even then bootloader mode might still work fine if those files are damaged.
Click to expand...
Click to collapse
Oh okay! I read your post about that but must have been confused on what you really meant.

thank you very much!excellent work,i wonder how long would genokolar take in order to bring us the CM7,i want to learn something about compile specifide kernel,so that i could do some help ,can someone offer me some infomation?thanks a lot!guys

hi, i install rom manager but it doesn't recognize clockworkmod why?
thanks!

I don't think ROM manager supports the Ideos X5 (yet). Why would you need it anyway?

sebgus said:
I don't think ROM manager supports the Ideos X5 (yet). Why would you need it anyway?
Click to expand...
Click to collapse
to have the recovery updated, to make back up and for other little things..
anyway thanks for your quick answer!

Hello all,
Maybe here is the right place to expose my problem. My Huawei X5 (and few others bought in Portugal from TMN company) are not running CWM v4.0.0.5. Booting in Recovery mode will be forever in "IDEOS" image.
No problem booting in Recovery mode either with original recovery.img or with CWM v3.0.2.8.
The problem is that with v3 there are problems flashing costum ROMs like FLB and void.
What is odd is that I haven't read a single complaint from any xda user in this forum... so maybe it is some problem with X5 sent to Portugal (!?).
Is there some way to debug the problem of the v4 in my X5?
Thanks.

RoyaL said:
Hello all,
Maybe here is the right place to expose my problem. My Huawei X5 (and few others bought in Portugal from TMN company) are not running CWM v4.0.0.5. Booting in Recovery mode will be forever in "IDEOS" image.
No problem booting in Recovery mode either with original recovery.img or with CWM v3.0.2.8.
The problem is that with v3 there are problems flashing costum ROMs like FLB and void.
What is odd is that I haven't read a single complaint from any xda user in this forum... so maybe it is some problem with X5 sent to Portugal (!?).
Is there some way to debug the problem of the v4 in my X5?
Thanks.
Click to expand...
Click to collapse
This is my problem too.

baratexx said:
This is my problem too.
Click to expand...
Click to collapse
Maybe you have U8800H?

baratexx said:
This is my problem too.
Click to expand...
Click to collapse
This is my problem too.
My U8800 is Chinese UNICOM version.

Thanks for your work, is source code available ?
Thanks for your work !
Is source code of this recovery available ?

andreasha said:
Maybe you have U8800H?
Click to expand...
Click to collapse
Nope, U8800.

Accidently flashed p700 kitkat on p705

I found the development thread, downloaded and flashed the p700 version instead of the p705 like I should have and now clockwork won't let me flash the correct version...
Is there a way to correct my mistake? I wouldn't normally care as it seems to work fine, but it's very annoying that the phone won't get out of Edge mode and I have perfect 3G nearby.
Thanks in advance!
-Dave

2BNDatte said:
I found the development thread, downloaded and flashed the p700 version instead of the p705 like I should have and now clockwork won't let me flash the correct version...
Is there a way to correct my mistake? I wouldn't normally care as it seems to work fine, but it's very annoying that the phone won't get out of Edge mode and I have perfect 3G nearby.
Thanks in advance!
-Dave
Click to expand...
Click to collapse
Why won't it let you flash the correct version? Just put the ROM on your external SD, boot into CWM and flash the correct ROM. If that's not possible, I suggest you flash your country's firmware via KDZ and then root your phone, unlock your boot loader again and flash the correct ROM (this is the long way).

You should flash again CWM with CWM app. It'll probably overwrite your current recovery which probably kept in memory your device as a P705 or an other thing.
Sent from my Nexus 7

TahaX said:
Why won't it let you flash the correct version?
Click to expand...
Click to collapse
I don't know, that's the question I was asking you.
TahaX said:
Just put the ROM on your external SD, boot into CWM and flash the correct ROM.
Click to expand...
Click to collapse
Yes, I am aware of how to flash a ROM, that's how I got into this situation. CWM keeps telling me the correct ROM is for a p705 and it says I have a p700, which is not true. It is clearly a p705!
TahaX said:
If that's not possible, I suggest you flash your country's firmware via KDZ and then root your phone, unlock your boot loader again and flash the correct ROM (this is the long way).
Click to expand...
Click to collapse
I really don't want to do that if I don't have to.
azvlean said:
You should flash again CWM with CWM app.
Click to expand...
Click to collapse
Are you are saying that I should re-flash CWM? How would that change things?

You flashed a ROM that changed your phone to a P700, theoretically speaking. There is no way to revert, unless, and this is a theory and not a possible solution, if you find a different P705 ROM and try to flash that. Maybe CWM will let you flash that P705 ROM even though it thinks that your phone is a P700. If this doesn't work, I don't think there's a different way to change your phone back to a P705 rather than flashing the original firmware through KDZ.

TahaX said:
You flashed a ROM that changed your phone to a P700, theoretically speaking. There is no way to revert, unless, and this is a theory and not a possible solution, if you find a different P705 ROM and try to flash that. Maybe CWM will let you flash that P705 ROM even though it thinks that your phone is a P700. If this doesn't work, I don't think there's a different way to change your phone back to a P705 rather than flashing the original firmware through KDZ.
Click to expand...
Click to collapse
Okay, I suppose I didn't make it clear. I already tried to flash the p705 ROM and CWM won't let me.
I am confused as to why CWM won't let me change ROMs considering that I haven't changed the recovery, only the ROM. Why would a ROM not let me change to another ROM? Maybe I have the incorrect CWM version?

2BNDatte said:
Okay, I suppose I didn't make it clear. I already tried to flash the p705 ROM and CWM won't let me.
I am confused as to why CWM won't let me change ROMs considering that I haven't changed the recovery, only the ROM. Why would a ROM not let me change to another ROM? Maybe I have the incorrect CWM version?
Click to expand...
Click to collapse
Yeah, I guess it's just CWM trying to protect P700 users from flashing the wrong version, but not the other way around. Weird. Anyways, I suggest you give it a go with TWRP Recovery. They might allow you to flash a P705 ROM.

2BNDatte said:
Okay, I suppose I didn't make it clear. I already tried to flash the p705 ROM and CWM won't let me.
I am confused as to why CWM won't let me change ROMs considering that I haven't changed the recovery, only the ROM. Why would a ROM not let me change to another ROM? Maybe I have the incorrect CWM version?
Click to expand...
Click to collapse
Actually, CWM considers your phone is a P700. But, if you flash a second time CWM with CWM app available on the Play Store, your recovery will be overwrited with a new recovery who " knows " you own a LG P-705. So, your problem will probably be solved. Or you can also flash TWRP.
Sent from my Nexus 7

Okay... I'm doing the whole thing over again, this really sucks because I spent hours getting it the way I like it, too. UGH.

2BNDatte said:
Okay... I'm doing the whole thing over again, this really sucks because I spent hours getting it the way I like it, too. UGH.
Click to expand...
Click to collapse
That's the beauty of being able to develop your phone to your own liking my friend!

Now KDZ says it can't find the phone... what gives?

2BNDatte said:
Now KDZ says it can't find the phone... what gives?
Click to expand...
Click to collapse
Did you install your drivers? Did you install LG PC Suite? Was your phone in emergency mode? Did you select "EMERGENCY" from the drop down list? Try to double check all of these things.

TahaX said:
Did you install your drivers? Did you install LG PC Suite? Was your phone in emergency mode? Did you select "EMERGENCY" from the drop down list? Try to double check all of these things.
Click to expand...
Click to collapse
I don't know how to get into emergency mode... But yes, I have all the drivers. The PC suite won't connect for some reason, it won't me to download a driver, but the device isn't listed through any of the carriers it lists.

2BNDatte said:
I don't know how to get into emergency mode... But yes, I have all the drivers. The PC suite won't connect for some reason, it won't me to download a driver, but the device isn't listed through any of the carriers it lists.
Click to expand...
Click to collapse
Connect your phone to your computer via an USB cable, remove your battery, wait until the LG logo goes away and then hold the power button and volume up button until you see the yellow emergency screen and immediately release all buttons.

The emergency mode only stays on for a second then the phone goes into regular boot...

2BNDatte said:
The emergency mode only stays on for a second then the phone goes into regular boot...
Click to expand...
Click to collapse
Hold the buttons a bit shorter. It's all about timing.

Okay, i wasn't releasing the buttons fast enough, nevermind, its doing it's thing now, will update...

The problem looks to be the original firmware I had, I still get the same issue now. I need p705 specific firmware to start with...
A little history on the phone, my friend gave it to me because she couldn't remember the pin to open the phone, so I had to flash it to use it. My bad, I guess i didn't know where to get the v20 file to start with. Do you know where I can get a p705 specific version?

Bad post, sorry!

For the record, our phone is the same as the 700. Only they had nfc while we don't. So it's ok to flashed it but the downside is you don't have deepsleep. The battery will drained because of nfc. So relax, you don't need to go over the kdz flashing as long as you can go to cwm. So questions:
1. what Rom did you flashed?
2. If you hate the kdz flashing, then just go to cwm and flashed the correct one. But before that, you need to delete the first line of the updater script in order for it to continue.
3. Or you just stay with the Rom, and delete all nfc related files and flash 705 kernel. For nfc remover, just go to apps and themes section and look for nfc remover by caliban as reference.
sent from my p705g - v20f jellybean extreme w/ stock kernel

Stuck on logo after installing custom rom.

Hello.
I have a problem with my S4 i9500. I've successfully rooted it and flashed custom recovery. But I'd also like to install custom rom on it, and there is where problem begins. Every time I flash rom and reboot it stucks at boot logo. I've tried it with Philz and TWRP recoveries and three different kitkat AOSP based roms. But the situation looks the same every time, despite waiting over 15-30 minutes the system doesn't boot properly, it stucks at boot logo. Creating backups and restoring stock rooted rom works flawlessly however with both recoveries.
I've also tired twice to install rom without doing factory reset before and then it goes trough boot logo, however stucks at "android is being actualised" window or something like that.
I hoped to get rid of ugly and slow touchwiz from my phone as fast as possible, but with no succes so far. What am I doing wrong?
Sorry for possible mistakes, english is not my first language.

mintor said:
Hello.
I have a problem with my S4 i9500. I've successfully rooted it and flashed custom recovery. But I'd also like to install custom rom on it, and there is where problem begins. Every time I flash rom and reboot it stucks at boot logo. I've tried it with Philz and TWRP recoveries and three different kitkat AOSP based roms. But the situation looks the same every time, despite waiting over 15-30 minutes the system doesn't boot properly, it stucks at boot logo. Creating backups and restoring stock rooted rom works flawlessly however with both recoveries.
I've also tired twice to install rom without doing factory reset before and then it goes trough boot logo, however stucks at "android is being actualised" window or something like that.
I hoped to get rid of ugly and slow touchwiz from my phone as fast as possible, but with no succes so far. What am I doing wrong?
Sorry for possible mistakes, english is not my first language.
Click to expand...
Click to collapse
It should just work.
- Is your bootloader up to date?
- Running latest modem?
- Try not to flash it from your external sd but from your internal.
- Use something like Airdroid to transer the files from your laptop to your phone. I find it more reliable then cabled.
- Redownload the rom again.
- Use TWRP recovery. The rest is outdated.
- Make sure to properly wipe in the recovery. Maybe even wipe your internal storage (/data).
That's what comes to mind.

Lennyz1988 said:
It should just work.
- Is your bootloader up to date?
- Running latest modem?
- Try not to flash it from your external sd but from your internal.
- Use something like Airdroid to transer the files from your laptop to your phone. I find it more reliable then cabled.
- Redownload the rom again.
- Use TWRP recovery. The rest is outdated.
- Make sure to properly wipe in the recovery. Maybe even wipe your internal storage (/data).
That's what comes to mind.
Click to expand...
Click to collapse
How do I check bootloader version and update it if necesarry?
I tried flashing both from internal and external memory, with te same result (no success).
Also, I didn't transfer roms form PC, I downloaded them directly to my phone. I did it the same way with my older phones and never had an issue like this.

mintor said:
How do I check bootloader version and update it if necesarry?
I tried flashing both from internal and external memory, with te same result (no success).
Also, I didn't transfer roms form PC, I downloaded them directly to my phone. I did it the same way with my older phones and never had an issue like this.
Click to expand...
Click to collapse
As silly as it sounds, try to download them on your pc and then transfer them.

Lennyz1988 said:
As silly as it sounds, try to download them on your pc and then transfer them.
Click to expand...
Click to collapse
I was unable to get airdroid working correctly. I'm not sure if it wasn't because of SD restrictions on Kitkat. Maybe this causes my problem as well? I also realized that many file related operations like renaming a folder, deleting files and even downloading it is unsuccessful unless I use stock samsung app. I've transferred the rom later via USB cable and flashed, but the problem still occurs.

mintor said:
I was unable to get airdroid working correctly. I'm not sure if it wasn't because of SD restrictions on Kitkat. Maybe this causes my problem as well? I also realized that many file related operations like renaming a folder, deleting files and even downloading it is unsuccessful unless I use stock samsung app. I've transferred the rom later via USB cable and flashed, but the problem still occurs.
Click to expand...
Click to collapse
What roms are you trying to flash?

Lennyz1988 said:
What roms are you trying to flash?
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s4/i9500-develop/rom-t2913193
http://forum.xda-developers.com/showthread.php?t=2688387
and CM11 found outside XDA, I cannot find link.
I also tried to flash CM10.2 and 10.1, but both recoveries refused to even flash it.

I found out that the problem is I cannot flash kernel. I tried to flash few of them, but nothing changed in About device/Kernel Version. I also have SE for Android status "Enforcing".

mintor said:
I found out that the problem is I cannot flash kernel. I tried to flash few of them, but nothing changed in About device/Kernel Version. I also have SE for Android status "Enforcing".
Click to expand...
Click to collapse
What does it say your model is when you are in download mode?

Lennyz1988 said:
What does it say your model is when you are in download mode?
Click to expand...
Click to collapse
Do you mean "Product name"? It's SHV-E300K

It's Korean model. I'm not sure if GT-I9500 ROMs will work correctly on SHV-E300K (if it's booting), due to too many differences between International and Korean version.
Sent from my ASUS_Z00AD

mintor said:
Do you mean "Product name"? It's SHV-E300K
Click to expand...
Click to collapse
Then why did you say you have an i9500? You have a SHV-E300K which is a completely different model.

Lennyz1988 said:
Then why did you say you have an i9500? You have a SHV-E300K which is a completely different model.
Click to expand...
Click to collapse
Because in About device/Model number it shows I9500. Sorry, I didn't know the info from download mode is more important. Why would it show different things anyway?

mintor said:
Because in About device/Model number it shows I9500. Sorry, I didn't know the info from download mode is more important. Why would it show different things anyway?
Click to expand...
Click to collapse
Because you can change it manually, but you cannot change the model in in download mode.
forum.xda-developers.com/showthread.php?t=2284543&page=101
Use that thread for reference.

HardBrick By Flashing Recovery Only !!! Showed QHSUSB_Bulk Help Please

hi
i just flash the Android N Preview it worked normaly then i flash TWRP through Temporary Recovery then i reboot and BAM . Nothing there.
Black display , no bootloader,nothing
just when pluging the device it showed qhsusb_Bulk Driver on Windows
Any Help ?
and if i send it back to google does it cover the Warranty?

Google probably won't do anything for you as you installed it at your own risk

mustafa alzubaidy said:
hi
i just flash the Android N Preview it worked normaly then i flash TWRP through Temporary Recovery then i reboot and BAM . Nothing there.
Black display , no bootloader,nothing
just when pluging the device it showed qhsusb_Bulk Driver on Windows
Any Help ?
and if i send it back to google does it cover the Warranty?
Click to expand...
Click to collapse
No it won't be covered by warranty. What do you mean you flashed TWRP through temporary recovery? Exactly what TWRP did you flash? The filename please.

Good news: your phone is not dead. I've had this issue once with my OnePlus One and I was able to get if fixed.
Bad news: process was a little bit harder than standard flashing, unlocking, etc. stuffs.

Heisenberg said:
No it won't be covered by warranty. What do you mean you flashed TWRP through temporary recovery? Exactly what TWRP did you flash? The filename please.
Click to expand...
Click to collapse
i use the NRT toolKit to flash TWRP (it provide temporary Recovery to flash any zip then it goes back to stock , i did this earlier its not the cause) it boot the recovery and i flashed this file :
twrp-3.0.0.0-s2vep-20160208 (then i realized it is the wrong file in the wrong folder)
after that i reboot the device and got bricked.

anmar21 said:
Good news: your phone is not dead. I've had this issue once with my OnePlus One and I was able to get if fixed.
Bad news: process was a little bit harder than standard flashing, unlocking, etc. stuffs.
Click to expand...
Click to collapse
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)

mustafa alzubaidy said:
i use the NRT toolKit to flash TWRP (it provide temporary Recovery to flash any zip then it goes back to stock , i did this earlier its not the cause) it boot the recovery and i flashed this file :
twrp-3.0.0.0-s2vep-20160208 (then i realized it is the wrong file in the wrong folder)
after that i reboot the device and got bricked.
Click to expand...
Click to collapse
Yeah, wrong recovery, big mistake.
mustafa alzubaidy said:
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
Click to expand...
Click to collapse
You need special Qualcomm tools to recover, I haven't seen such a tool for this device yet though.

Heisenberg said:
Yeah, wrong recovery, big mistake.
You need special Qualcomm tools to recover, I haven't seen such a tool for this device yet though.
Click to expand...
Click to collapse
i search the net i found that for lG G2 , LG G3
any idea
how much time should i wait if such a tool appears?
thanks for you help

mustafa alzubaidy said:
i search the net i found that for lG G2 , LG G3
any idea
how much time should i wait if such a tool appears?
thanks for you help
Click to expand...
Click to collapse
It's impossible to say if or when it might become available.

@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )

sjandroiddeveloper said:
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
Click to expand...
Click to collapse
It corrupts the partition table which affects the other partitions.

mustafa alzubaidy said:
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
Click to expand...
Click to collapse
For my OPO I used a tool and as @Heinsenberg mentioned I've never seen such a tool for the 6P yet. RMA would be the best solution, just say your not able to turn your phone on (which is true) .

sjandroiddeveloper said:
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
Click to expand...
Click to collapse
me too!
i have flashed many rom with many devices , i even flashed a rom by enterning a download rom on a black screen and it worked!
but flashing wrong recovery i dont think it will cause such brick
FYI when i connect it to the PC it is recognized and when i contiously press the power buttuon it re-connected to the pc

If he really sends the device in and Google finds out HOW exactly the phone died, he might face severe consequences. It´s dishonest after all.
If you flash the wrong recovery for a different device, it´s your own bad luck. Now here´s the deal, you can still repair the device if a) Huawei would fix it or b) find a phone shop which could replace the motherboard. Once the Bootloader is bricked, there´s barely anything a regular user could do except for some complicated methods which require the knowledge and the special tools which most people don´t have.
anmar21 said:
For my OPO I used a tool and as @Heinsenberg mentioned I've never seen such a tool for the 6P yet. RMA would be the best solution, just say your not able to turn your phone on (which is true) .
Click to expand...
Click to collapse

mustafa alzubaidy said:
me too!
i have flashed many rom with many devices , i even flashed a rom by enterning a download rom on a black screen and it worked!
but flashing wrong recovery i dont think it will cause such brick
FYI when i connect it to the PC it is recognized and when i contiously press the power buttuon it re-connected to the pc
Click to expand...
Click to collapse
Flashing the wrong recovery can and does cause such a brick, this is what you're experiencing. I've seen it happen on many devices, it borks the partition table.

mustafa alzubaidy said:
but flashing wrong recovery i dont think it will cause such brick
Click to expand...
Click to collapse
You can tell yourself this all day long, but the phone that is in your hands that is now a doorstop, is proof otherwise.
Very crappy situation, but this is why toolkits stink, and why you need to be VERY careful when you mess w the device.

Hard bricked,only vibrates

Hello guys,i was trying to flash LOS and after many tries i hard bricked my phone.At start,screen wasnt turning on and phone vibrated sholtly every 1 sec.I did EDL and then flashed different roms but still phone just vibrates but for a bit longer.When i do EDL it gets recognised by pc.Also when i flash a rom before i try to boot,if i connect it to power the led is blinking.
I dont want to be this guy who opens a thread that has opened many times,but i couldnt figure out a solution whatsoever.Thanks in advance.

Did you try downgrade from pie to oreo? Can you enter fastboot mode?
I bricked my phone too. Nothing worked for me. I hope you have more luck.

How it got bricked? Did you read the whole tutorial ?

emiljano539 said:
How it got bricked? Did you read the whole tutorial ?
Click to expand...
Click to collapse
I tried to flash from a video in youtube and didnt work.My system was deleted so i tried flashing different roms,it let me flash stock android and when i rebooted it just vibrated.Looks like the first vibration is the same as when the phone boots and the rest are a bit longer.

degen1997 said:
I tried to flash from a video in youtube and didnt work.My system was deleted so i tried flashing different roms,it let me flash stock android and when i rebooted it just vibrated.Looks like the first vibration is the same as when the phone boots and the rest are a bit longer.
Click to expand...
Click to collapse
Does it let you to boot into twrp now? If yes try to flash the stock rom via twrp there is a version which you flash directly with twrp

emiljano539 said:
Does it let you to boot into twrp now? If yes try to flash the stock rom via twrp there is a version which you flash directly with twrp
Click to expand...
Click to collapse
Sadly it doesnt,i can flash roms though with edl mode and miflash,maybe i haven't tried the correct one yet?Do you know which rom i need to flash for stock android 7 with mi flash?I've seen that other people have had the same problem but dont know if anyone managed to get through it.

degen1997 said:
Sadly it doesnt,i can flash roms though with edl mode and miflash,maybe i haven't tried the correct one yet?Do you know which rom i need to flash for stock android 7 with mi flash?I've seen that other people have had the same problem but dont know if anyone managed to get through it.
Click to expand...
Click to collapse
Check it :https://forum.xda-developers.com/showpost.php?p=75711835&postcount=2
I hope it helps

degen1997 said:
Sadly it doesnt,i can flash roms though with edl mode and miflash,maybe i haven't tried the correct one yet?Do you know which rom i need to flash for stock android 7 with mi flash?I've seen that other people have had the same problem but dont know if anyone managed to get through it.
Click to expand...
Click to collapse
I was one of them. I was lucky though and got a new phone from the dealer. I followed all the threads with the same issue. Never saw one user who was able to solve it.

XtraWater said:
I was one of them. I was lucky though and got a new phone from the dealer. I followed all the threads with the same issue. Never saw one user who was able to solve it.
Click to expand...
Click to collapse
I was thinking about flashing a Rom because im in stock now only rooted... But you guys scared me

emiljano539 said:
I was thinking about flashing a Rom because im in stock now only rooted... But you guys scared me
Click to expand...
Click to collapse
I recommend you to read a lot about flashing custom ROMs before trying to do it.
LineageOS has a pretty explicit installing tutorial.

If you can get into fastboot mode there is hope.
Remember that you must have the bootloader unlocked.

my thread
emiljano539 said:
How it got bricked? Did you read the whole tutorial ?
Click to expand...
Click to collapse
Hi everyone, I have rooted Mi A1 (pie), I have a hard brick. but fixed, when flashing Rom with TWRP, my phone cannot receive the partition / 'cache', when root receives the message: error: 28, I need help, thank you very much