Database Info

Soft bricked my Mate 8 - can't flash anything anymore

Hey guys,
I've backed myself into a corner here a little and I hope you can guide me to get a working phone again.
I was on Ephemeral Mate 8 for a while now and decided it was time to upgrade. The new ROM I wanted to try mentioned I should have at least firmware version B3XX to flash it, so I thought the easiest way to get there would be to flash a stock ROM again and let the system update function do it's work. I updated from NXT-L29C432B180 to B192 to B560 to B581 (no B3XX offered in between) and somehow managed to get the phone rooted again. Yet I noticed some things (like Bluetooth) not working quite properly anymore (for whatever reason) and so wanted to downgrade again.
Tried to restore one of my old backups from Ephemeral Mate 8: it failed. The backup from stock B581 I made before: no idea where it was stored, but I can't find it anymore and may have accidentally deleted it by now. Currently it seems I don't have any OS installed anymore.
I still have an unlocked bootloader and can access it by pressing power + volume down and can flash a custom recovery via Fastboot (the one I'm currently trying with is this one). However, no ROM I try to flash or backup I want to restore will work anymore, they just fail with varying errors like error 7 or invalid zip file. At some point I tried to wipe almost anything I could before every new try to flash anything (probably a very bad idea), because I thought a clean start would somehow resolve some of the various errors TWRP was throwing at me - obviously it hasn't. I also tried installing the same stock ROM like the first time via dload method, but it always says there is an incompatibility with my current version (probably that I don't have one anymore by now) and fails.
Sadly, I can't remember anymore what everything I tried to flash in between to try and get it working again or where I found it, because it simply is too much. But I'm willing to provide any information I'm able to achieve and try any steps you tell me to get it working again. I'd be very grateful for any help on this and already thank you in advance for any advice.

Sooo... in the meantime I followed this guide and got my phone working again. However, I'm facing another problem now:
When I try to flash TWRP I always get this error and can't find out what it means and how to fix it:
Code:
target reported max download size of 471859200 bytes
sending 'recovery' (17280 KB)...
OKAY [ 0.437s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.454s
Maybe it's related to that somehow the Serial Number of my device has changed in the process? It's now just '0123456789ABCDEF'. I read about fixing it with HCU Client tool, but when trying to repair the Serial Number it just gives me this error:
Code:
2017-06-23 13:11:36.503 Autodetect COM port and phone type start!
2017-06-23 13:11:36.509 Compatible COM ports not found!
2017-06-23 13:11:36.513 ERROR!
Phone not found !
I don't know how to proceed, but don't want to be stuck with stock rom. Any suggestions?

Okay, image verification error obviously had something to do with the B320 rom I flashed. Tried B192 now and recovery flash with fastboot goes through with OKAY... Just that the phone doesn't boot into recovery - it just sits there stuck on boot screen.
Would still be thankful for any hints.

Patneu said:
Okay, image verification error obviously had something to do with the B320 rom I flashed. Tried B192 now and recovery flash with fastboot goes through with OKAY... Just that the phone doesn't boot into recovery - it just sits there stuck on boot screen.
Would still be thankful for any hints.
Click to expand...
Click to collapse
I read somewhere that once you are on EMUI 5 you can't go back to 4. The rollback works to 4.1 which is where I am now with C636B330 but that's it. No further. I was advised to use the DC Phoenix tool and go to 330 which thankfully worked! Do the same and you should be ok I guess.. 4.1 or 5.
I think I'm just going to have to wait for someone like kang to do a Rom based on one of those before I try custom. Unless there already is one? Next time I flash a phone I should really research the pitfalls. That would avoid a week of using a different device!

Bearded_1 said:
I read somewhere that once you are on EMUI 5 you can't go back to 4. The rollback works to 4.1 which is where I am now with C636B330 but that's it. No further. I was advised to use the DC Phoenix tool and go to 330 which thankfully worked! Do the same and you should be ok I guess.. 4.1 or 5.
Click to expand...
Click to collapse
Thanks for the reply! I'm now back on C432B180 with EMUI 4.0 flashed with DC Phoenix and finally managed to flash a TWRP using SRK Tool.
Anything with B3XX or B5XX still just gives me the 'image verification error' mentioned above for any custom recovery and I doubt it would be any different with SRK Tool since it also just makes use of fastboot as it seems to me. So I'm staying with B180 for the moment unless someone has a suggestion on how to get rid of this error.
I'll now try to flash Ephemeral Mate 8 again, since it was the first (and last) custom ROM that worked for me before. I know it's discontinued, but it's the only one I can currently find that doesn't mention to go to B3XX first - which wouldn't work for me.
What worked and didn't work so far:
Tried flashing EM8_41816_SIGNED.zip, which failed without warning and rebooted to fastboot mode mid-process which showed some error involving the word 'panic'.
Managed to root the stock B180 again with SRK Tool, but will continue to try earlier versions of Ephemeral 'cause I really need the Kang Tools. Will update on how that worked out.
Suggestions still welcome on:
How to get rid of 'image verification error' on B3XX and B5XX' so I can try flashing a non-outdated ROM.
Other still available pre-B3XX ROMs I could try.
Any root apps to achieve navbar and status bar modifications similar to Kang Tools, so I could do without a custom ROM and stay with currently achieved rooted stock ROM.
One little edit concerning the 'image verification error': My phone mentions the FRP to be unlocked in fastboot mode, when on B3XX or B5XX which it doesn't on B1XX, so maybe that's related to it? But I don't know exactly what an FRP is or what it means to unlock it.

YEEESSS!!! :victory:
Tried flashing EM8_40416_SIGNED.zip now and went through without errors. Took a few seconds to reboot and it works! Just B170 now it seems, but hey...
My quest to upgrade may have failed graciously, but at least I got a working rooted phone again with Kang Tools - what more can I ask for? And unless someone, somehow, somewhen has a hint for me about this damned 'image verification error' (at least I now know a foolproof way to fix it if I mess anything up again) I'm taking this cautionary tail to heart and won't touch this damned phone's firmware again 'til it turns to dust under my fingers.
And now, as common courtesy commands, my exact steps - from having completely messed up with nothing save stock recovery and fastboot mode working anymore to functioning phone again with root, cutom ROM and Kang Tools - for the sake of the poor souls of the future who may (hopefully not) follow in my footsteps facing the same problems (no guarantees or responsibility whatsoever on my part, just what worked for me):
1. Reboot your phone into fastboot mode (bootloader) by pressing and holding power + volume down together (don't forget to connect the phone to a PC before!). As always, make sure you have enough battery power left before each step! If you don't at this point, try booting into stock recovery by holding power + volume up and charge your phone, then continue.
2. Download:
2.1: DC Phoenix from here. Found here via here.
2.2: File with partition rework and factory firmware from here. Found here.
2.3: NXT-L29C432B180 stock ROM from here (you may need a different version depending on your device!). Found here. (Stock ROMs B3XX or higher may work too, but didn't for me - see above).
3. Buy 15 credits here to use DC Phoenix (it's worth it!), unpack and start DC Phoenix and login with your DC-unlocker credentials. (Edit: If you want to try the new guide mentioned below from step 5 onward, you should consider buying the 'DC-Phoenix + HCU timed license' option for 19 bucks instead.)
4. Follow this guide. You find the mentioned 'UPDATE.APP' file in the stock ROM ('update.zip') file you downloaded before.
5. You should have unbricked your phone and have a working stock ROM again by now. :fingers-crossed: Now on to getting a custom ROM again:
(Edit: I fiddled around with my phone a bit more in the meantime, so if you prefer flashing a TWRP on a B5XX-based stock ROM and finding your way from there, you may want to follow this new guide instead.)
6. In the settings of your phone enable 'Developer options' -> 'USB debugging' if you haven't already (and 'Enable OEM unlock' too just to be sure, don't know if it's necessary, but I did it). If you don't see 'Developer options', tap on 'About phone' -> 'Build number' a few times. Connect phone to your PC.
7. Downloads:
7.1: SRK Tool from here. Found here via here.
7.2: Ephemeral Mate 8 from here. Found here via here. (Later version or other ROMs may work for you, but didn't for me.)
8. Move 'EM8_40416_SIGNED.zip' file (or the one you want to flash) to the external sdcard of your phone.
9. Unpack and start SRK Tool.
10. Select '3. Install Recovery 6.0' -> '2. Huawei Mate 8' -> '2. Install Mate 8 TWRP for Marshmallow (EMUI 4.0)' (may depend on the stock ROM version you flashed before). Confirm requests and follow the instructions.
11. Your phone now reboots. Remove the USB cable connecting it to the PC and press and hold power + volume up to boot into the newly flashed custom recovery.
12. Select your language (it was chinese later on for me, when I didn't!) and press 'Cancel' if asked for a password. When asked to allow changes to system, do it (don't know if necessary, but I did).
13. Select 'Wipe' -> Swipe to Factory Reset'.
14. Go back and 'Format Data' -> type 'yes' and confirm. Reboot the phone and enter custom recovery like before. Factory Reset again. (Don't know if this step is necessary, but I did it.)
15. Go back and select 'Install' -> select and flash the zip file you moved to sdcard before. If no errors occured, reboot your phone. Let it reboot, it may take a few seconds. If you get errors, try starting with step 1 or 11 again (depending on how badly you messed up...) and try a different custom ROM (Follow the instructions there and be aware of prequisites and warnings!). If that doesn't work either, note your errors and ask for help - good luck!
16. Congratulations, you should have a working phone again with Ephemeral Mate 8 custom ROM with Kang Tools, it should be rooted already. :good:
17. Maybe buy the guys, who developed and wrote the mentioned tools and guides to help you on your way, a coffee - they surely deserve it.
Hint: If you only want a rooted stock ROM, reboot your phone after step 12, start SRK Tool again, select option '4. Root' and follow instructions.

Patneu said:
Thanks for the reply! I'm now back on C432B180 with EMUI 4.0 flashed with DC Phoenix and finally managed to flash a TWRP using SRK Tool.
Anything with B3XX or B5XX still just gives me the 'image verification error' mentioned above for any custom recovery and I doubt it would be any different with SRK Tool since it also just makes use of fastboot as it seems to me. So I'm staying with B180 for the moment unless someone has a suggestion on how to get rid of this error.
I'll now try to flash Ephemeral Mate 8 again, since it was the first (and last) custom ROM that worked for me before. I know it's discontinued, but it's the only one I can currently find that doesn't mention to go to B3XX first - which wouldn't work for me.
What worked and didn't work so far:
Tried flashing EM8_41816_SIGNED.zip, which failed without warning and rebooted to fastboot mode mid-process which showed some error involving the word 'panic'.
How to get rid of 'image verification error' on B3XX and B5XX' so I can try flashing a non-outdated ROM.
Any root apps to achieve navbar and status bar modifications similar to Kang Tools, so I could do without a custom ROM and stay with currently achieved rooted stock ROM.
One little edit concerning the 'image verification error': My phone mentions the FRP to be unlocked in fastboot mode, when on B3XX or B5XX which it doesn't on B1XX, so maybe that's related to it? But I don't know exactly what an FRP is or what it means to unlock it.
Click to expand...
Click to collapse
Isn't the FRP related to the 'enable oem lock' option? Glad it's sorted! I might follow this thread in the future to go back to pre EMUI 4.1, but I like the camera options so willing to stick with it for a while!

Hey, I didn't realized, I have the 0123456789ABCDEF serial number too, I'm on B330, after unbricking it with DC phoenix (flashed directly from the "Factory_firmware.." for unbrick it, to B330). Did you solve that?
I think I cannot do much now because I'm waiting for the 14 days using my HW account to request de bootloader unlock code. Altough, my phone says I have the bootloader unlocked (that's because the DC phoenix tool did something). But I've never formerly unlocked my phone.

Don Kronos said:
Did you solve that?
Click to expand...
Click to collapse
Well, sort of... I'm still on this fake ABC... Serial Number, but as you can read above, I at least managed to flash a TWRP again and also to install a custom ROM, if only a B1XX based. Better than nothing, though. Didn't encounter any other downsides of the changed Serial Number 'til now.
If you have a hint concerning the 'image verification error' I'd still be glad to hear, but otherwise I'm fine now.

Patneu said:
If you have a hint concerning the 'image verification error' I'd still be glad to hear, but otherwise I'm fine now.
Click to expand...
Click to collapse
Patneu said:
One little edit concerning the 'image verification error': My phone mentions the FRP to be unlocked in fastboot mode, when on B3XX or B5XX which it doesn't on B1XX, so maybe that's related to it? But I don't know exactly what an FRP is or what it means to unlock it.
Click to expand...
Click to collapse
The FRP (Factory Reset Protection) prevents some "writing" commands of ADB to be executed, thats the reason of the "image verification error". It is the homologue to an iCloud protection of iPhone, but using Google Account. I don't know why it gets locked.. but the DC phoenix can crack that protection.

Don Kronos said:
The FRP (Factory Reset Protection) prevents some "writing" commands of ADB to be executed, thats the reason of the "image verification error".
Click to expand...
Click to collapse
Sounds right, aside from the fact that my FRP doesn't seem to be locked. When I flashed B320 via DC Phoenix or flashed B1XX and updated to B560 via OTA and booted into fastboot mode, it said there "Phone unlocked" and "FRP unlocked". I shouldn't get the 'image verification error' then, right? But I do. If I flash B1XX via DC Phoenix, it says nothing about FRP, whether locked or unlocked, just "Phone unlocked" and I don't get 'image verification error'.
I remember getting a TWRP to flash when I updated from B180 (flashed with the TWRP I had before) to B581 OTA before I used DC Phoenix (even if it threw errors like nothing good), but I don't remember if it said anything about FRP then.
Don Kronos said:
I don't know why it gets locked.. but the DC phoenix can crack that protection.
Click to expand...
Click to collapse
Yeah, it seems so, but it can't flash a custom ROM, can it? Only 'UPDATE.APP' of stock ROMS as far as I can see.

Patneu said:
YEEESSS!!! :victory:
And now, as common courtesy commands, my exact steps - from having completely messed up with nothing save stock recovery and fastboot mode working anymore to functioning phone again with root, cutom ROM and Kang Tools - for the sake of the poor souls of the future who may (hopefully not) follow in my footsteps facing the same problems (no guarantees or responsibility whatsoever on my part, just what worked for me):
Click to expand...
Click to collapse
You just saved my fuc**ing ass bro. Thanks a lot for such detailed steps. I was another prick who got his device bricked. I also fhashed a buch of things and lost track on the number of solutions tried until I came across your post:fingers-crossed: Now i feel solid again and want to continue flashing and messing up with my device. That´s the beauty of android, you can recover your device from almost any state. Thanks a lot. You made my day!
The process really work and it's really easy. Those 15 bucks are worth every penny!

juanq214 said:
The process really work and it's really easy. Those 15 bucks are worth every penny!
Click to expand...
Click to collapse
Glad, I could help you and yeah, they surely are.
Just a few remarks I discovered in the meantime:
- If you want to further mess with your phone after that, be sure to not mess up so badly as to having to use DC Phoenix again, unless within the next 72 hours or you'll have to pay the 15 bucks again (as mentioned here). Other claims made there about "lifetime" are not legit.
- Tried EM8_41816_SIGNED version of Ephemeral Mate 8 (based on B180) again and it works, too. The failure and mid-process 'panic' reboot at first try was caused by unrelated battery (hardware) problems of my device (which I think already started before messing with the firmware), which caused me to think I had more power left than I actually did. :silly:
I solved the battery problems by replacing the battery using this guide, ruining some cheap repair kit, made of too much plastic, in the process and paying altogether around 40 bucks for it and for now, everything runs fine again. :good:

Patneu said:
Glad, I could help you and yeah, they surely are.
Just a few remarks I discovered in the meantime:
- If you want to further mess with your phone after that, be sure to not mess up so badly as to having to use DC Phoenix again, unless within the next 72 hours or you'll have to pay the 15 bucks again (as mentioned here). Other claims made there about "lifetime" are not legit.
- Tried EM8_41816_SIGNED version of Ephemeral Mate 8 (based on B180) again and it works, too. The failure and mid-process 'panic' reboot at first try was caused by unrelated battery (hardware) problems of my device (which I think already started before messing with the firmware), which caused me to think I had more power left than I actually did. :silly:
I solved the battery problems by replacing the battery using this guide, ruining some cheap repair kit, made of too much plastic, in the process and paying altogether around 40 bucks for it and for now, everything runs fine again. :good:
Click to expand...
Click to collapse
I successfully got OTA for L29C432B581. I don't really care much about xposed or magic, all I needed was Nougat update. The only downside is that fast charging is gone, but that is not because of the brick but rather a bug related to the update.

Everything fixed.
Ok, so I'm a little late on this, but because some recent circumstances forced me to mess with my phones firmware again - despite my former new-found resolutions :angel: - I dug into this mess again and finally found the solution for the last unsolved problem I encountered: the dreaded 'image verification error'. So I thought, I'd share it with anyone else out there, who may still be struggling:
If you followed my original instuctions, maybe you got stuck at the same point I did: I originally wanted to install a more recent custom ROM based on Android Nougat, but couldn't for the hell of it flash a working TWRP, because of 'image verification error', when I was on a stock Nougat ROM (B5XX-based) and finally settled for my old B1XX-based Ephemeral Mate 8 ROM once more.
So here's what I did to get a working TWRP flashed with a B5XX-based stock ROM (again, no guarantees, just what worked for me):
1. Depending on how badly you messed up before or at what point you currently are, first you may want to follow some of my original instructions 'til step 5. (All links are still working, as far as I can see.) You then should be good to go with a working B1XX-based stock ROM as a basis for what where going to do now. :fingers-crossed: If you already are, great. :good:
1.1: Attention! If you don't already have a working B1XX-based stock ROM, you may want to slightly differ from my original instructions: instead of buying the 15 credits for DC Phoenix in step 3, you could directly choose the "DC-Phoenix + HCU timed license" option for 19 bucks, so you're already set for everything we're doing later and can mess with your phone as much as you want for the next 72 hours - it may come cheaper in the end and it's easier in any case.
1.2: You may notice afterwards, that if you start adb and type 'adb devices', that the serial number of your device changed to something generic like '0123456789ABCDEF'. We'll fix that later on, along with the 'image verification error', but be sure to note your devices original S/N! You can find it on a sticker at the side of the box your phone came in or in the phones 'Settings' -> 'About phone' -> 'Status' -> 'Serial number'. I don't know where else to recover it, if you lost it.
2. Once you have a working B1XX-based stock ROM as a basis, update it to the latest B5XX-based one (was B582 for me) via 'Settings' -> 'System update'.
2.1: Attention again! You may want to check 'Developer options' -> 'Enable OEM unlock' first, since it was greyed out (while still checked) for me once I updated to B5XX. Don't know if it's necessary to have it enabled, but better safe than sorry so you don't have to start over. (If you don't see 'Developer options', tap 'About phone' -> 'Build number' a few times.)
3. Download:
3.1: HCU Client from here. (Thanks Petr S. for putting me on the right track!)
3.2: Unofficial TWRP for EMUI 5.X from here. Found here. (Official TWRP versions may work for you, but didn't for me.)
4. If you didn't already, buy a sufficient number of credits (don't know how much it will be) to use HCU Client from here or directly choose the "DC-Phoenix + HCU timed license" option for 19 bucks to get the all-round carefree package.
5. Unpack and start HCU Client and login with your DC-Unlocker credentials.
6. Connect your phone to your PC and enable 'Developer options' -> 'USB debugging' (don't know if necessary, but I did).
7. As instructed by HCU Client, type '*#*#2846579#*#*' (minus the quotes) into your phones dialer and select '1. Background Settings' -> '2. USB Port Settings' -> 'Manufacture Mode'. If your phone should be rebooting somewhere in the process, you may need to do this again.
8. Now click 'Read phone info' in HCU Client ('Autodetect' should be checked already) and wait for it to complete. (If you didn't buy a sufficient number of credits or the mentioned license before, HCU Client will simply get stuck instead of just telling you - which I found a little odd. )
9. Click 'Repair UMTS' (acknowledge the warning) and type the original serial number of your device (not the '0123456789ABCDEF' one!) into the 'SN' textfield, check it and hit 'Repair'. (I also retyped the 'IMEI' and 'IMEI 2' numbers, but I guess that was unnecessary.)
10. If now you hit 'Read phone info' again, all the textfields under 'Repair UMTS' (except 'WiFi MAC' and 'Bluetooth MAC') should be filled with the right values. Then click 'Unlock' -> 'Read Bootloader code', note the bootloader code. Your phone will shutdown.
11. Power up your phone again, make sure 'Settings' -> 'Developer options' -> 'USB Debugging' and 'Enable OEM unlock' are still checked and bring it into fastboot mode, then open a command prompt and cd to where your 'Minimal ADB and Fastboot' (or whatever you're using) is installed, if you didn't already, and type 'fastboot devices'. You should see your device with the original serial number again.
12. Unlock your device again with the command 'fastboot oem unlock ' followed by the bootloader code you noted before. Now you should be able to flash the unofficial TWRP you downloaded with 'fastboot flash recovery twrp-3.1.1-1-next.img' (assuming you copied the TWRP image file to your 'Minimal ADB and Fastboot' directory for convenience and didn't rename it).
13. Type 'fastboot reboot' and immediately bring your phone into recovery mode. You should now have a working TWRP with a B5XX-based stock ROM and should be able to flash anything you'd like. :fingers-crossed::good:
You should also be able to flash a Nougat-based custom ROM now, though I didn't try that and settled for the stock ROM rooted with Magisk for personal reasons.
A last word of warning: Be sure to frequently make backups in TWRP before you flash or change anything important like installing or updating Magisk or Xposed modules, because I noticed my system to be a little... wonky at this point.
Don't know if that's related to the way I unbricked my phone with all these DC-unlocker tools or just using Magisk or whatever, but several times after changing something important and rebooting, my phone kind of crashed into fastboot mode with some warning about 'native_boot_fail' and wouldn't boot again until I made a factory reset in recovery and started all over (the first time while writing this guide :silly. Not so bad, as it doesn't happen randomly as long as I don't make any major changes to the system, but you wouldn't want to retype your Google password and setup your system again everytime like I had to do, would you? So, yeah, just make a backup in TWRP before you change anything root-related - and tread a little lightly, as in: don't make to many changes at once - and you should be fine.

[ROM] Stock Oreo 8.1 With July Security Patch (OPM1.171019.026.V9.6.4.0.ODHMIFE)

Xiaomi released July security patch a couple of days back. However, as always, a lot of people didn't receive it yet. But the wait is over. Now everyone can update their device to the latest security patch.
Disclaimer:
If you are planning to flash the ROM on your device, you are on your own. I can not be held responsible if anything happens to your device. Your warranty will be void after unlocking the bootloader. You need to lock the bootloader for any warranty.
Requirements:
1. Xiaomi Mi A1 (Ofcourse)
2. A PC (I am using Windows 7 here)
3. The ROM file (Available on the link below)
4. MiFlash Tool ( Link: http://en.miui.com/thread-345974-1-1.html ) (A big thanks to Miui forum for making the tool available on miui forum)
5. ADB Platform tool (Search on google)
6. Patience
Installation Process:
1. Download the ROM file from the given link and extract it.
2. You will see a folder with name as tissot_images_V9.6.4.0.ODHMIFE_20180712.0000.00_8.0_735823083f
3. Double click on the folder and open it. You will see another folder with name as tissot_images_V9.6.4.0.ODHMIFE_8.0
3. Copy the folder into the C drive. Remember, you need to copy tissot_images_V9.6.4.0.ODHMIFE_8.0 and not the main folder.
4. Install MiFlash Tool on your PC from the given link
5. Set up ADB driver properly on your PC (It's very important)
6. Now go to your device and enable Developers option by tapping on Build Number 7 times.
6. Open Developers Option and enable "OEM Unlocking" and "USB Debugging" option.
7. Now press and hold the power button and Volume down button for about 10 seconds until you see a small bunny on the screen.
Now connect your device to your PC and open a command box and type fastboot oem unlock
8. Once the bootloader is unlocked, put your device in fastboot mode again and connect it to PC. (BE WARNED!!! if anyone is on May security patch, unlocking bootloader will erase everything from the device and device will restart again. You will need to unlock developers option again and enable "USB debugging" option once more)
9. Now open MiFlash Tool and see if it reads your device serial number by clicking on "Refresh". Now, select tissot_images_V9.6.4.0.ODHMIFE_8.0 and click on "Flash". Make sure you are doing it in a proper way.
10. It may take around 10-15 minutes (for me it took around 11 minutes) to get the process completed. Once done, your device will boot into system and Congrats! Now you have Oreo 8.1 on your device with July security patch.
N.B. It is best that you select "Clean all and lock" option on MiFlash tool.
Flashing Guide For TWRP & Custom Kernel:
1. Grab the latest twrp recovery image (Oreo) and twrp installer zip file.
2. Put the recovery image in ADB folder and the installer zip in your device.
2. Boot your device into fastboot mode and connect it to the PC.
3. Make sure the bootloader is unlocker.
4. Open a command box and type fastboot boot xxx.img (xxx= recovery image name)
5. Once your device is boot into twrp, flash TWRP installer zip file and reboot back to recovery.
6. Now flash the custom kernel of your choice and Magisk (optional).
7. Reboot back to system.
Important Note:
If anyone has any problem understanding the steps, I would recommend that you google or search on Youtube. There are lots of Videos showing on how to flash stock ROM on MiFlash tool. Please don't blame me if you skip any step or do it wrong. I have shared the standard steps that remain the same for flashing both stable and beta rom. It is advised that you STAY AWAY if you don't know what you are doing. I am certainly not going to take any blame for improper flashing. As you have decided to flash the ROM, I expect you to have a little knowledge about how to use MiFlash tool. All newbies have a problem at first, especially when flashing ROM on MiFlash tool. That's because of selecting and flashing the ROM file in an improper way. You need to first learn exactly which folder to flash or else you will always end up on a bootloop. Please don't blame me for not spoon feeding you.
Bugs Encountered:
LED notification stays still when a notification comes in. It doesn't blink.
ROM Download Link:
https://www.androidfilehost.com/?fid=5862345805528051162
Credit:
Xiaomi
Special Note:
I apologize to all for breaking any possible XDA rule and hurting anyone here!! Please note that I am not getting paid for sharing this post here. If anyone still feels something bad, you can either let me know or you can report it to the admin. But again, I am extremely sorry for breaking any rule here.

Occupied

Reerved

There is already a thread for stock roms which is alot nicer because everything is compiled by version. Why bother creating another?

barrack1 said:
There is already a thread for stock roms which is alot nicer because everything is compiled by version. Why bother creating another?
Click to expand...
Click to collapse
Basically, looking for attention and thanks.
He has been doing this for every update even though there are other threads that are much better and more organized
He even claimed that he was in the beta program when 8.1 beta was leaked even though he was asking around on where to get beta update.
Rowdy, you should honestly stop making pointless threads that already exist and start being more respectful to other members

In his defense. This link is AFH, while still not wonderful, it is usually SOOOO much faster than the damn MIUI links. (at least in my experience)

berezker said:
Basically, looking for attention and thanks.
He has been doing this for every update even though there are other threads that are much better and more organized
He even claimed that he was in the beta program when 8.1 beta was leaked even though he was asking around on where to get beta update.
Rowdy, you should honestly stop making pointless threads that already exist and start being more respectful to other members
Click to expand...
Click to collapse
Listen, this is the second time I am telling you not to be personal. If you don't like something, report it to the mods. XDA is not your personal property. So, you don't get to judge people here. I checked all the post for July OTA and then I posted it here. The particular post you are talking about, I checked it prior to creatingmine. He didn't have the ROM uploaded when I created my post. It's not my fault that he uploaded the July fastboot ROM without checking mine. I have already asked the mod to check both his and my post to see who uploaded the July fastboot ROM.

barrack1 said:
There is already a thread for stock roms which is alot nicer because everything is compiled by version. Why bother creating another?
Click to expand...
Click to collapse
Are you sure that post has the July fastboot ROM? I checked his post prior to creating one. He didn't have the ROM uploaded. If you see both my and his post, you can see who edited the post later. It was he who posted the July fastboot ROM later. I have already asked the mod to check both his and mine post to see who uploded the post first. Till then, you may wanna stop being sarcastic.

berezker said:
Basically, looking for attention and thanks.
He has been doing this for every update even though there are other threads that are much better and more organized
He even claimed that he was in the beta program when 8.1 beta was leaked even though he was asking around on where to get beta update.
Rowdy, you should honestly stop making pointless threads that already exist and start being more respectful to other members
Click to expand...
Click to collapse
And talking about attention and thanks, I am not going to be rich by getting a few thanks. You might have joined XDA for thanks, but I don't find any pleasure or point of getting thanks and attention on a software development community. You should think first before attacking someone. You might have forgotten about the "Report" option, but I didn't.

jareddlikewhoaa said:
In his defense. This link is AFH, while still not wonderful, it is usually SOOOO much faster than the damn MIUI links. (at least in my experience)
Click to expand...
Click to collapse
I checked all XDA post prior to posting mine. XDA gives you an option to check all similar posts while you are creating your post. I went to each post and checked if anyone had uploaded the July security patch.
https://forum.xda-developers.com/mi...-ota-links-t3718542/post74828108#post74828108 (I checked his post at first and when I created my post, he didn't have July fastboot ROM uploaded).
https://forum.xda-developers.com/mi-a1/how-to/download-opr1-170623-026-9-5-4-february-t3758090 (This guy gave a headline of July fastboot ROM. But I didn't find V9.6.4.0.ODHMIFE anywhere on his post)
Now, it's not my fault if someone uploaded the July fastboot ROM after I posted it here. I don't know why some people act violently (not you) towards others.

Rowdyy Ronnie said:
Disclaimer:
Your warranty will be void after unlocking the bootloader. You need to lock the bootloader for any warranty.
Click to expand...
Click to collapse
I dont think thats the case with xiaomi.
Thanks for uploading fastboot image.

.:Addicted:. said:
I dont think thats the case with xiaomi.
Thanks for uploading fastboot image.
Click to expand...
Click to collapse
Well, the warranty remains intact only if you use a miui based handset. But since Mi A1 runs on pure AOSP, Xiaomi doesn't provide any warranty after unlocking bootloader (confirmed with Xiaomi customer service).

Rowdyy Ronnie said:
Well, the warranty remains intact only if you use a miui based handset. But since Mi A1 runs on pure AOSP, Xiaomi doesn't provide any warranty after unlocking bootloader (confirmed with Xiaomi customer service).
Click to expand...
Click to collapse
ahh ok. good to know that

i am already rooted on custom rom but i want to flash stock 8.1, do i use mifalsh tool? and does it wipe all the internal data? or use the userdata (like apps etc)

faddys123 said:
i am already rooted on custom rom but i want to flash stock 8.1, do i use mifalsh tool? and does it wipe all the internal data? or use the userdata (like apps etc)
Click to expand...
Click to collapse
Hi, yes you need the MiFlash tool as this is a fastboot ROM. And it is not necessary (but suggested) to wipe the internal storage. You can select your desired option on the MiFlash tool. If you want to keep your apps and data, you can select "Save user data" on MiFlash tool and flash the ROM.

we only need one thread about stock roms. Let's make it easier on everyone and keep all the info in the same thread.
https://forum.xda-developers.com/mi-a1/how-to/mi-a1-monthly-updates-t3750419
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542/

Qualcomm Crashdump

Hi all
I have just bought a new Oneplus 6 and wanted to install Lineage Os.
I had initially set up the OP6 with my google account and installed some minimum apps over a couple of days. The phone updated a couple of times. I think I started on Android 8, it definitely updated to Android 9 and I think it updated to Android 10. But I am not completely sure of this because I did not take notice at that stage because I didn't realise that this might have significance..
I followed the guide from the lineaoge os wiki here
wiki.lineageos.org/devices/enchilada[
I got as far as using adb to Fastboot boot twrp-3.3.1-2-enchilada.img (which was the latest image in the dl.twrp.me/enchilada/
It then got stuck in the qualcomm crashdump line on screen.
I spent a day checking posts, including here on XDA. There are a lot of posts dealing with this issue and I did try to follow some of them with less or more success but no resolve. I downloaded Android 9.02 and used the following instructions
techtrickz.com/how-to/recover-oneplus-6-and-6t-from-qualcomm-crashdump-mode/
The routine started to run and then posted a series of error messages and exited. ( I have a screenshot of the terminal window but cannot see a way to post it here)
I have tried to research this further and there are plenty of posts and lots of suggestions. But to be honest I have become confused as some of the posts give significantly different solutions to each other.
I wondered whether it would be possible to give me some help or point me in the right direction to a post which is current and has the steps that I am likely to need succeed..
Thanks in advance for any help you can give.

grego34 said:
Hi all
I have just bought a new Oneplus 6 and wanted to install Lineage Os.
I had initially set up the OP6 with my google account and installed some minimum apps over a couple of days. The phone updated a couple of times. I think I started on Android 8, it definitely updated to Android 9 and I think it updated to Android 10. But I am not completely sure of this because I did not take notice at that stage because I didn't realise that this might have significance..
I followed the guide from the lineaoge os wiki here
wiki.lineageos.org/devices/enchilada[
I got as far as using adb to Fastboot boot twrp-3.3.1-2-enchilada.img (which was the latest image in the dl.twrp.me/enchilada/
It then got stuck in the qualcomm crashdump line on screen.
I spent a day checking posts, including here on XDA. There are a lot of posts dealing with this issue and I did try to follow some of them with less or more success but no resolve. I downloaded Android 9.02 and used the following instructions
techtrickz.com/how-to/recover-oneplus-6-and-6t-from-qualcomm-crashdump-mode/
The routine started to run and then posted a series of error messages and exited. ( I have a screenshot of the terminal window but cannot see a way to post it here)
I have tried to research this further and there are plenty of posts and lots of suggestions. But to be honest I have become confused as some of the posts give significantly different solutions to each other.
I wondered whether it would be possible to give me some help or point me in the right direction to a post which is current and has the steps that I am likely to need succeed..
Thanks in advance for any help you can give.
Click to expand...
Click to collapse
I would recommend using fastboot flashable stock rom from here. People also like to use msmtool, but I feel like it is an overkill.
Please note this warning:
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
So grab the latest oxygen os 10, and follow the instructions to flash it. After that, if you are feeling a bit paranoid maybe download a zip from oneplus and do a local update. You now should have your phone back.
Official TWRP does not support android 10 yet, as far as I understand, so that is probably the issue. If you want lineageos 16, you should downgrade to android 9 using a downgrade package provided by oneplus and then update to Oxygen OS 9.0.9.
There is unofficial twrp by mauronofrio that supports android 10. If you want to go from OOS 10 to some other android 10 rom

[email protected] said:
I would recommend using fastboot flashable stock rom from here. People also like to use msmtool, but I feel like it is an overkill.
Please note this warning:
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
So grab the latest oxygen os 10, and follow the instructions to flash it. After that, if you are feeling a bit paranoid maybe download a zip from oneplus and do a local update. You now should have your phone back.
Official TWRP does not support android 10 yet, as far as I understand, so that is probably the issue. If you want lineageos 16, you should downgrade to android 9 using a downgrade package provided by oneplus and then update to Oxygen OS 9.0.9.
There is unofficial twrp by mauronofrio that supports android 10. If you want to go from OOS 10 to some other android 10 rom
Click to expand...
Click to collapse
Thanks very much for your helpful reply. I am now back to a working phone with Oxygen os10. And you have also explained what was wrong when I tried to fix it, I was trying to load an Oxygen Os 9 on a phone that had already been upgraded to 10 and you have explained what went wrong in the first place, I was trying to flash an incompatible TWRP image onto Android 10. So your short post has explained a lot. Thank you.
I am not feeling paranoid unless you advise that I should be and I do want to install lineage os. So I need to revert to Oxygen Os9. I have looked on the Oneplus site and that have found the option to Upgrade to 10.3 but no option to downgrade. In the Oneplus community there is a link to downloadable ROMs, these are divided into a number of folders some of which look not applicable. There are three folders that look of interest
1. Signed flashable zips
2. OTA incremental update zips
3. Stock boot-recovery images
Here is the link /forums.oneplus.com/threads/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.835607/
I can see it is not the OTA Incremental that I need but am unsure if it is signed flashable zips or Stock boot recovery images. or whether it is neither.
Do I flash as normal or would it be a local update?
I would be grateful for any further advice.
Thanks again and for any help provided now.

grego34 said:
Thanks very much for your helpful reply. I am now back to a working phone with Oxygen os10. And you have also explained what was wrong when I tried to fix it, I was trying to load an Oxygen Os 9 on a phone that had already been upgraded to 10 and you have explained what went wrong in the first place, I was trying to flash an incompatible TWRP image onto Android 10. So your short post has explained a lot. Thank you.
I am not feeling paranoid unless you advise that I should be and I do want to install lineage os. So I need to revert to Oxygen Os9. I have looked on the Oneplus site and that have found the option to Upgrade to 10.3 but no option to downgrade. In the Oneplus community there is a link to downloadable ROMs, these are divided into a number of folders some of which look not applicable. There are three folders that look of interest
1. Signed flashable zips
2. OTA incremental update zips
3. Stock boot-recovery images
Here is the link /forums.oneplus.com/threads/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.835607/
I can see it is not the OTA Incremental that I need but am unsure if it is signed flashable zips or Stock boot recovery images. or whether it is neither.
Do I flash as normal or would it be a local update?
I would be grateful for any further advice.
Thanks again and for any help provided now.
Click to expand...
Click to collapse
I have had luck with this downgrade package. I basically googled it, the package is hosted on a legitimate website, so that's what I used. Just download it, put it on your phone and do a local upgrade through updater app.
Once you have done that I would recommend upgrading to the latest Android 9, which is OOS version 9.0.9 I believe. Then go ahead and follow instructions to install lineageos.
I am actually on LineageOS 16 + MicroG right now, so I ran into the same problems you did Glad I could help!

TexnoViking said:
I have had luck with //oxygenos.oneplus.net/fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" downgrade package. I basically googled it, the package is hosted on a legitimate website, so that's what I used. Just download it, put it on your phone and do a local upgrade through updater app.
Once you have done that I would recommend upgrading to the latest Android 9, which is OOS version 9.0.9 I believe. Then go ahead and follow instructions to install lineageos.
I am actually on LineageOS 16 + MicroG right now, so I ran into the same problems you did Glad I could help!
Click to expand...
Click to collapse
Thanks so much for your reply again.
I used your downgrade link and that all worked well and then let it upgrade to OOS 9.0.9. Again all very positive.
I then tried to flash TWRP to the device using this image "twrp-3.3.1-2-enchilada.img" It appeared to flash okay. Then I issued the command
"fastboot boot twrp-3.3.1-2-enchilada.img" over my adb connection and it returned to the Qualcomm Crashdump error.
I presume I have to start again with the exception that this time I can use a flashable stock rom that is OOS 9.09? Is that correct?
Then do you have any suggestions for getting round the TWRP problem? Did you use a different version?
Thanks in advance for any help.

grego34 said:
Thanks so much for your reply again.
I used your downgrade link and that all worked well and then let it upgrade to OOS 9.0.9. Again all very positive.
I then tried to flash TWRP to the device using this image "twrp-3.3.1-2-enchilada.img" It appeared to flash okay. Then I issued the command
"fastboot boot twrp-3.3.1-2-enchilada.img" over my adb connection and it returned to the Qualcomm Crashdump error.
I presume I have to start again with the exception that this time I can use a flashable stock rom that is OOS 9.09? Is that correct?
Then do you have any suggestions for getting round the TWRP problem? Did you use a different version?
Thanks in advance for any help.
Click to expand...
Click to collapse
Hm. Yes, unfortunately the safest thing to do is to start again. But you can start with 9.0.9 right away.
People have been discussing a similar issue here. It seems like using unofficial twrp by blu_spark helps. Maybe twrp-3.2.3-x_blu_spark_v9.91_op6.img or maybe try the latest one.
Also, make sure you read the instructions on lineageos website. Make sure you have oem unlocked, usb debugging enabled and you clicked "always give access to this" device or something, do the fastboot set_active a. I have also used fastboot flash boot_a <recovery_filename>.img. However, I do recall using fastboot boot <recovery_filename>.img some other time and I think it worked....
Anyway, yeah, maybe try this modified recovery by blu spark and follow the instructions carefully.

TexnoViking said:
Hm. Yes, unfortunately the safest thing to do is to start again. But you can start with 9.0.9 right away.
People have been discussing a similar issue here. It seems like using unofficial twrp by blu_spark helps. Maybe twrp-3.2.3-x_blu_spark_v9.91_op6.img or maybe try the latest one.
Also, make sure you read the instructions on lineageos website. Make sure you have oem unlocked, usb debugging enabled and you clicked "always give access to this" device or something, do the fastboot set_active a. I have also used fastboot flash boot_a <recovery_filename>.img. However, I do recall using fastboot boot <recovery_filename>.img some other time and I think it worked....
Anyway, yeah, maybe try this modified recovery by blu spark and follow the instructions carefully.
Click to expand...
Click to collapse
Thanks very much for your helpful reply and apologies for the delay in my reply to this post, I have been tied up with work the last couple of days.
I did re-install OOS 9 and then followed the instructions on the Team Win site to install TWRP in the Oneplus6. I had success after I used the latest TWRP image and zip from that site . I was then able to install Lineage OS and Microg as I wished.
So thanks for the help all. Really appreciated.

grego34 said:
Thanks very much for your helpful reply and apologies for the delay in my reply to this post, I have been tied up with work the last couple of days.
I did re-install OOS 9 and then followed the instructions on the Team Win site to install TWRP in the Oneplus6. I had success after I used the latest TWRP image and zip from that site . I was then able to install Lineage OS and Microg as I wished.
So thanks for the help all. Really appreciated.
Click to expand...
Click to collapse
Great! I am glad you managed to fix your phone! Enjoy

Question Rog Phone 5s Pro RAW Files

Hello all,
I am in need of some help please.
I have 18.1220.2109.126 installed presently. I have the EU version/WW version of this phone.
I want to upgrade to the latest firmware but I have an unlocked boot loader and root.
Can someone please provide me with the links for the firmware and an upgrade path from this firmware if i cant go direct?
Thanks
Valen.

as I've wrote a couple times before....
you could've just googled how to manually ota update asus phones. they works more less the same:
1. download the update pkg to the phone.
2. move it to the root of the storage (i.e. the first page you open when you tap internal storage in fm.
3. charge your device to at least 60% and up.
4. reboot the phone.
5. after a while it should give a popup saying update found, tap on it and start local ota.
some notes:
if you want to keep magisk then DONT reboot after ota finished. go to magisk manager and select install to inactive slot. then you can reboot.
This only works for updates not downgrade. if you flashed 31.xxxxx (A12) then you cant go back to 18.xxxx (A11), it won't give you the prompt.
Click to expand...
Click to collapse

yurishouse said:
as I've wrote a couple times before....
Click to expand...
Click to collapse
I am having some trouble navigating this thread. its a mess of stuff.... Other phones have sectioned areas for exactly what i need.
THank you for replying to me. I have begun doing this and am updating as we speak. Sorry i made you repeat yourself.

np

Hi,
It would be awesome if getting to one build.prop from pro
And is Armoury Crate version in pro 5.50.0.49_220124 ? 124MB ?
In: system / priv-app / ROGGameCenter
Plz
Thank you

good afternoon i also have this version 18.1220.2109.126 is there a latest version other than this? because i have an warning saying my installed firmware does not match the device origin

Hi guys please seriously help me about Android 12

How are you everyone I am new here I need your serious help please all of great expert kindly focus to my problem it would be easy for you so my problem is actually recently a couple of days ago I just root my Samsung A7 2018 SM-A750F mobile and its Android version was and are now Android 10 okay now I have successfully rooted my this Samsung A7 2018 Android 10 version mobile after hard and painful time I successfully rooted but now I want I like and I really Desire to install latest Android release version Android 12 ok but I want to install custom rom Android 12 with rooted capability so what should I do now I have already my mobile rooted with Android 10 how could I root my mobile with Android 12 version with this model please is someone give a video guide it would be greatful thank you.

hloooooo :;/

I heard about this TreeUI. It works perfectly for me.
https://forum.xda-developers.com/t/...eeui-0-9-5-beta-for-a8-a8-a7-m20-m30.4252235/
Download the file from there, and in TWRP, flash it as a system image. It should automatically redirect you to the setup. Keep in mind that the resolution and DPI will be incorrect. I fixed it using Easy DPI Changer.
There are some known bugs though. For example, Samsung Camera doesn't work (third party apps will work), and the face unlock. I'd recommend you read the page carefully. If you need anything else, let me know.
EDIT: Just noticed you want Android 12, not 11. My bad. You can try flashing Pixel Experience on your phone. Check this video. Look at the youtuber of this video too, I'm sure you'll find much more help there.

Zanci19 said:
I heard about this TreeUI. It works perfectly for me.
https://forum.xda-developers.com/t/...eeui-0-9-5-beta-for-a8-a8-a7-m20-m30.4252235/
Download the file from there, and in TWRP, flash it as a system image. It should automatically redirect you to the setup. Keep in mind that the resolution and DPI will be incorrect. I fixed it using Easy DPI Changer.
There are some known bugs though. For example, Samsung Camera doesn't work (third party apps will work), and the face unlock. I'd recommend you read the page carefully. If you need anything else, let me know.
EDIT: Just noticed you want Android 12, not 11. My bad. You can try flashing Pixel Experience on your phone. Check this video. Look at the youtuber of this video too, I'm sure you'll find much more help there.
Click to expand...
Click to collapse
I tried flashing Android 12 GSI (Arrow and Corvus) but both GSI have lockscreen bug and I can't access my TWRP when flashed. I was wondering if you have any workarounds or fix for these issues. I also tried following the steps shown in the attached link to a YouTube video but there are no fix as well.

Just asked that yesterday, still waiting for reply. I really hope someone will finally make a custom rom designed for this device! GSI images have that bug, and some apps don't open. I'm so sick of staying on Samsung firmware.

Futazaki said:
I tried flashing Android 12 GSI (Arrow and Corvus) but both GSI have lockscreen bug and I can't access my TWRP when flashed. I was wondering if you have any workarounds or fix for these issues. I also tried following the steps shown in the attached link to a YouTube video but there are no fix as well.
Click to expand...
Click to collapse
Get Odin, and flash the stock firmware on your phone. However, this will erase all data on your device, so make a backup first. If you have any questions, feel free to ask me.

Zanci19 said:
Get Odin, and flash the stock firmware on your phone. However, this will erase all data on your device, so make a backup first. If you have any questions, feel free to ask me.
Click to expand...
Click to collapse
I tried doing this, reverting to the 2020 version to bypass the Knox Security and Encrypted Data sh*t but still, Android 12 has its bugs.

Futazaki said:
I tried doing this, reverting to the 2020 version to bypass the Knox Security and Encrypted Data sh*t but still, Android 12 has its bugs.
Click to expand...
Click to collapse
Just before installing android 12, you would want to go to TWRP > Advanced > Terminal and type this command:
Code:
mount /vendor;rm /vendor/lib64/hw/keystore*&&echo "persist.sys.binary_xml=false" >> /vendor/build.prop
Hope this helps

AaliShine said:
How are you everyone I am new here I need your serious help please all of great expert kindly focus to my problem it would be easy for you so my problem is actually recently a couple of days ago I just root my Samsung A7 2018 SM-A750F mobile and its Android version was and are now Android 10 okay now I have successfully rooted my this Samsung A7 2018 Android 10 version mobile after hard and painful time I successfully rooted but now I want I like and I really Desire to install latest Android release version Android 12 ok but I want to install custom rom Android 12 with rooted capability so what should I do now I have already my mobile rooted with Android 10 how could I root my mobile with Android 12 version with this model please is someone give a video guide it would be greatful thank you.
Click to expand...
Click to collapse
Sorry for being a little late, ForkLineage-19.1 GSI seems to be working fine on stock kernel, except MTP. Link : https://xiaomemeindex.com/treble/?dir=ForkLineage

random.tek said:
Just before installing android 12, you would want to go to TWRP > Advanced > Terminal and type this command:
Code:
mount /vendor;rm /vendor/lib64/hw/keystore*&&echo "persist.sys.binary_xml=false" >> /vendor/build.prop
Hope this helps
Click to expand...
Click to collapse
Thanks, I'll try this later today. I kinda settled on stock rom since GSI has bad battery backup. Does this get rid of the lockscreen bug?
EDIT: it returns an error saying
Code:
rm: can't remove '/vendor/lib64/hw/keystore*': No such file or directory
any help?

Futazaki said:
EDIT: it returns an error saying
Code:
rm: can't remove '/vendor/lib64/hw/keystore*': No such file or directory
any help?
Click to expand...
Click to collapse
Sorry for the late reply. The directory is already removed, so you should be good to go