Database Info

Bootloader Unlocking through Downgrade possible?

Hello Guys,
i had bought an Huawei P20 about an year ago. Now you know with all of this "USA-Huawei" Trouble going on, the thought came to my mind that i better start unlocking bootloader and be prepared to flash custom rom if worst come to worst. so far, so good.
now i started looking around if there is an easy method of getting the bootloader unlocked. but oh my, the huawei company is very friendly to us users and say "no, you wont get any unlock code from us anymore". so screw that.
now i want to try some experimental stuff. it looks like this:
my Smartphone has currently the version EML-L29 8.1.0.168(C432). I bought some Credits (i think it is that thing for $4) from DC-Unlocker. Yeah yeah i know, there they say "no support for Huawei P20!!!". But i still want to try. Well i tried, but it doesnt work - what you should expect.
now i read from some other website that there is another way of unlocking it. i only read it diagonal but the one thing i read was the information "unlocking bootloader is only possible till firmware version june 2018". so i jumped to an maaybe interesting conclusion about unlocking the phone with DC-Unlocker or HCU (whatever, i guess maybe both use the same method anyway).
if i do an rollback to the old firmware version *before* June 2018 on the device, wouldnt it be possible to do the unlock? Because the security patches that preventing it unlocked arent on the device then.
So what i have done so far is loading the old firmware version 8.1.0.128(C432). But the source is saying that it is coming from "Asia" but in the next line it reads "Asia, Europe" etc. - do they mean that this version is universal or do i run in trouble if i install one that is having the wrong area?
the next thing that kinda baffles me... all guides are sayin "copy the extracted dload folder to your sd-card". even the p20 guides do that. but.. well you know, the p20 device doesnt even have sd-card support. so how are you intended to use it then? i wonder about that a bit.
i dont think that without unlocked bootloader, flashing an original OTA full update would be impossible. but im not really sure how. there is this shady menu you can reach if you call this strange numbercode. but im very unsure if that will really work out. the phone (it is still a phone without SD-Card-Support) even has the option "apply update from sd-card". so im wondering how this feature they implemented in the original software is intended to use at all. maybe i should push the dload folder on the internal storage? i dunno.
i read about another possibilty of flashing stock roms. they say you can do it per adb command. so no problems would be here, i have adb and the hisuite and all already set. but i have absolutely no idea if that is possible without unlocked bootloader. so the questions arose from my mind are those:
- does an stock rom image from possibly/maybe asia would do any harm to my device like it is getting unbootable or anything like that?
- is it possible to flash an image older android stock rom with methods like this special menu on the device or the adb load?
- do you all think that my plan of downgrading the phone in order to get the bootloader code would work?
i'm looking very forward to your answers )

no_monday said:
Bootloader Unlocking through Downgrade possible?
Click to expand...
Click to collapse
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.

Jan Philipp said:
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.
Click to expand...
Click to collapse
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.

no_monday said:
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.
Click to expand...
Click to collapse
It seems you have a couple of questions, pal, I answered to the first one (Bootloader Unlocking through Downgrade possible?). All I said is that it's impossible to unlock the bootloader through a downgrade. If you read all the how-to's you should have noticed that FirmwareFinder doesn'st work anymore since EMUI 9.0. This Information simply means Huawei doesn't allow us to flash updates on our own anymore like we did before. For sure there are some guides how to rollback to Android 8 but even this changes nothing to the bootloader.
Sadly I have no answer to the other questions about the strange behavior, it sounds pretty odd. Never heared something like this. But good luck fixing your phone anyway.

well i found out a couple of things now.
first thing: you know the service menu when you try to apply a zip archive from sd card? well you wont be able to use it UNTIL you use an usb-otg cable and an exFat formatted USB-Stick. Next thing to know is, you have to use the right images. there seem to be an kind of rule how this images are supposed to be and the image i found was from an russian firmware download site it was linked here in the forum in a thread. so i did choose "apply zip from sdcard" and .. IT DOES! the device rebooted, the stick flashed and the flashing process occured! and guys, im back to Version EML-L29 8.1.0.128(C432)! it is clearly stated in the build version view in settings. so.. i guess you *can* roll back even without firmware updater.
so far so good. but lets get back to the problem with the Bootloader. sadly Jan Philipp was totally right.. the bootloader cant be unlocked even in this version with the security patch of 5. may 2018. that is kinda sad. even kingoroot is still no different from before. i guess i have to search now for an way to get the system rooted. however, it must be easier on an earlier security update stage like now instead of the future versions of emui 8.1.
edit: another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).

"unlocking bootloader with exploit is only possible till firmware version june/july 2018" does not apply to 2018's devices with kirin970, kirin980 & kirin710.
You are with kirin970.
So to unlock your kirin970, the only way for now is to wait for 3rd party seller to hypotheticaly start back their dervice:
- In the last 6 months there was only 2 'windows' which lasted 3 or 4 days where you could order your bootloader's unlock code by imei (from 5 to 124 us$).

GuestD0711 said:
another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).
Click to expand...
Click to collapse
Google Play services require all permissions, otherwise won't work.
I also been searching on how to unlock the bootloader and found no solution or hope. I guess we are stuck with EMUI forever.

Reply from Huawei:
You can roll back to earlier versions of EMUI software, but you have to roll back one version at a time. However, our earlier phones operate exclusively on Google Mobile Services so removing it would limit the functionality extremely, however, we do have a range of new devices that no longer rely on Google Mobile Services and use Huawei Mobile Services instead - such as our P40 series.
Here are the instructions for rolling back software:
[Rollback Guideline] EMUI 9.1 (Android 9) Rollback to EMUI 9.0 (Android 9) Operation Instruction
EMUI 9.1 (Android 9) can now be rolled back to the official version of EMUI 9.0 (Android 9) using HiSuite, without downloading any intermediate packages. To ensure that the rollback succeeds, read the instructions carefully and perform the steps as instructed.
1. The following are precautions for roll-back.
a. Rolling back to an earlier version will erase all data on your device. Use an SD card, computer, or Cloud storage to back up all important data before rolling back your phone, and make sure all backed up content is complete and effective.
b. Use a computer running a Windows operating system to visit http://consumer.huawei.com/minisite/HiSuite_en/index.html and download the latest version of HiSuite. If HiSuite is installed on your computer, click the version number in the lower left corner of the page to check if it is the latest version. Make sure HiSuite version is 9.1.0.303 _OVE or above.
c. Before rolling back the phone, make sure your phone has not been upgraded using non-official updates. Otherwise, the roll-back may fail and unknown issues may be introduced. If you have used non-official packages to upgrade your phone, it is recommended that you go to an after-sales service center to roll back your phone.
d. Before rolling back your phone, make sure that your phone system has not been unlocked or rooted. If the system has been unlocked or rooted, it is recommended that you go to an after-sales service center to roll back your phone.
e. Before the roll-back, restore the phone to factory settings to make sure there is enough storage space.
f. Make sure the battery level is more than 50%.

Hi All,
I need assistance to update my EML L29 Huawei P20 phone.
The phone is Locked and FRP Lock
Issue the phone is always booting into recovery mode and not into the main screen.
I tired flashing via CMD using twrp.img file but its not writing.
Need help

Proper OS cleanup of new OnePlu7 Pro

Hi Everyone,
Living in Japan, we have no official channel to purchase a OnePlus handset here.
Really wanted to get a OnePlus 7 Pro as I felt it is the best model on the market as of today.
Knowing that, I got mine on Amazon Japan from a HK online shop which had very good reputation.
Now, the problem is these phones always come already opened as they say they need to confirm operation before sending it.
I have been reading news and article about this where we see more third party companies flash their roms with malware/ransomeware already built in...
In these situation, the best way to clean the phone is to do a full re-install of the OS.
I did review a bunch of article on XDA and it seems that now, due to the A/B partition setup, we can't just use official OnePlus image to load from the fastboot easily.
We have to rely on community provided too and stock rom to be able to do so....
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Sorry if I sound paranoid. Ideally, I understand the best thing to do was to buy directly from Oneplus and work a way to have it shipped to Japan but thought it would be interesting for me to learn more about android.
With previous Oneplus, it was easier as they were provided this type of official file for recovery but they stopped...
Thank you again for your time and hopping to learn more about how new android setup works.

Is the bootloader locked? Is Widevine (Netflix HD) certification still there? You can check these things to see if the phone has been tampered with.

brissoukun said:
Hi Everyone,
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Thank you again for your time and hopping to learn more about how new android setup works.
Click to expand...
Click to collapse
Good questions. Before you start, check the model number of your device through Settings > About. I'm assuming it's the international/global/unlocked version (GM1917).
With regard to question 1, a full build downloaded from the link you provided should contain every part of the OS, and flashing it through local update should overwrite anything that was there before. Before flashing, I would perform a full data wipe through recovery like you mentioned.
Q2: There is an MSM tool that will completely flash a system image for the OP7 Pro. I don't think they're generally intended for public use but they always get leaked anyways. They write an image (in the case of OnePlus, a .ops file) to the phone using a PC and USB connection. Here is a link to a thread which contains the MSM tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Download the tool for the model of your phone (probably the international, firmware GM21AA), and extract its contents into a directory. In order for the tool to work, you need the OnePlus USB drivers installed on your PC. Plug the phone into your PC with it on, and enable USB file transfer. Open File Explorer and you should see a drive labeled "OnePlus drivers" or similar. Open it and run the driver setup executable file. You'll also need ADB to make your phone reboot into a mode that will allow the tool to perform its tasks. Here is a guide to installing ADB:
https://www.xda-developers.com/what-is-adb/
Once you've set that up, make sure the phone is plugged into the PC and the MSM tool is open. Make the phone boot into edl mode by typing
Code:
adb reboot edl
and once it says Connected next to a COM port in the tool, press start. Don't interrupt the process until it completes the download and the status message turns green. The phone should automatically reboot. This method is arguably more risky than using the local upgrade option, so do it at your own risk.
Q3: Make sure that OEM unlocking is turned off in developer settings and that the bootloader is locked (if the bootloader is unlocked, you'll see a yellow warning message after you power on the device from a power off state). Without an unlocked bootloader it would be pretty difficult to make any deep modifications to the device.

Hi @Zocker1304 and @TManchu,
Please let me thank you very much first for your kind and detailed reply, this is really welcome.
@Zocker1304:
I checked using the ADB/Fastboot connection that indeed, the Bootloader is locked so, that looks good.
Also installed (using a separate Google account) DRM Info app to confirm that the Widevine is properly installed and at L1 level which indeed again, looks good.
@TManchu
Thank you again for your very detailed reply! This was exactly what I needed as information.
I did already exactly as mentioned for the #1 so, it looks I should be good now with a proper rom from OnePlus (and did a full wipe in the Recovery boot mode)
For #2, I think I will skip that since as you rightly said, with #1, it should be fine so, prefer to keep with the recommended step.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:

brissoukun said:
.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
Click to expand...
Click to collapse
No problem! I’ve just done some reading and from what I understand, re-locking the bootloader on anything other than a completely stock ROM will result in a bricked phone. I believe this is due to the way Android handles data encryption. If what you’ve heard is true, being able to lock your bootloader on a custom ROM would be great for device security. However, should something go wrong with the ROM having a locked bootloader might make it more difficult to fix.

I know that there are ways to sign system and boot images so that you can lock the bootloader with them installed, but I think that would still show a warning though I'm not sure.
Anyways, if all the build dates and numbers in the system info are correct, the firmware should be stock and as long as the bootloader is locked too, I don't believe you can tamper with that.

Hi Gents,
Thank you very much for the answer to the thread and much appreciated.
Apologies for not getting back to you all earlier as yesterday was family day...haha!
Well, since things looked good on the OS and the build, I went ahead and started to use the phone properly setting up my accounts. It did give me some incentive to get all my sensitive accounts setup with 2FA so that in case I get hacked with my passwords in the future...they would still need the 2fa (using Google Authenticator).
I did check also all system apps/running process and didn't see anything shady.
Just for reference, here were the type of articles I was refering too for the OS being plagued with malware even out of the box:
Page_theverge.com/2019/6/6/18655755/google-android-malware-triada-ota-rom-ads-spam-oem (sorry gents, new account, cannot put links yet)
However here, it seems it is due to lax review from the maker to third party tools which were including malware...
To have the same level on the oneplus I bought from the HK shop, they would have needed access to OnePlus Dev team to inject the malware in official image (knowing anyway I have re-installed a new image from the local update).
Otherwise, I was reading on the web about the fact to relock the bootloader with a custom roam and there seems to have a lot of messages but not concrete steps. It seems it depends a lot on phone model and brand.
When you are checking
Page_gizmochina.com/2019/06/10/relock-bootloader-oneplus-7-pro/
This is where you can read at the end:
"The above method only works if OnePlus 7 Pro is running on stock recovery and stock firmware. The ability to relock devices running custom recovery is expected in the next few weeks. "
That was published last month so, not sure if they got this to work on the OnePlus 7 pro yet.
So that's it, I am now using my new device which looks to work great and hopefully, won't get any bugs down the road.
I appreciate you taking the time to get back to me and will continue to learn about android.:good:

Oukitel WP6 General Discussion

As there's no thread on this device I decided to start one
The hardware of this device is really nice, but the stock ROM on it is total garbage. It has some built in power saving that closes all background apps no matter what the settings are, so after an hour so so you won't receive any more notifications from messaging apps such as telegram and outlook.
Since there are not even stock ROMs available anywhere I decided to take the risk of a brick and install phh's AOSP 10 GSI, no need for TWRP as everything can be done using ADB and fastboot. The procedure is the same as with any other phone: Unlock the bootloader, wipe all partitions in fastboot, install system image, restart and hope for the best. Luckily it booted up just fine and everything except VoLTE and VoWIFI works, @lucian.w153 found two little bugs which I didn't notice:
lucian.w153 said:
- In call volume not working, it is stuck at max which is very annoying
- You can't disable the second sim card, you need to take it out if you don't want it to consume battery.
Click to expand...
Click to collapse
It's an arm64 AB device, so any matching GSI should run fine on it.
I have tested phh's vanilla, FLOSS and GAPPS variants, they all work flawlessly barring those two bugs mentioned above.
GAPPS version is my daily driver now, the phone runs blazingly fast and battery lasts forever. All hardware (bluetooth, sensors, cameras etc.) works perfectly, no force closing or other issues.
Hope some more share their experience to help others.
Cheers

Finished. Done!

Joergelmann said:
Please provide complete instructions. I am an absolute beginner. Please a step to step instruction with links.
Click to expand...
Click to collapse
Ok, just the usual disclaimer: You may void your warranty or brick your device in the process, you do everything on your own risk and I'm not responsible if anything goes wrong.
Of course you will also loose any data on your device as it will be formatted in the process.
Prerequisites:
You need ADB and fastboot installed on your computer, follow these instructions for windows or these for MacOS or Linux.
Also you'll need to download the system image from phh's releases, it has to be arm64 AB but you can choose whichever one suits you best, with or without google apps, FLOSS etc. If you don't know what those are, please do some research in the forum first.
For most people system-quack-arm64-ab-gapps.img.xz will be the most suitable one as it's closest to a stock ROM with google apps. After downloading extract the .img to the same folder you installed ADB and fastboot to. Also rename it to something simpler like system.img for later.
Make sure you have sufficient battery in your phone before you start, at least 50%.
Once those are ready you need to unlock the bootloader of your phone. First enable developer options: Go to settings -> about device and tap on build number 7 times in a row quickly, you'll get a confirmation that developer options are enabled. Go to settings -> system -> developer options, there enable USB debugging and OEM unlock.
When done, connect you phone to your computer with the USB cable. Your phone will show an info in the statbar that USB debugging is enabled.
On you computer open a terminal in the folder where you installed ADB and type in the upcoming commands and press enter after each.
First type: adb devices
ADB should now detect your device, and a request for access will pop up on your phone asking to allow permission. Allow it.
Next type: adb reboot bootloader
The phone will reboot into fastboot mode, wait a few seconds until "fastboot mode" is shown on the bottom left of your phone's screen.
Now type: fastboot devices
Fastboot should detect your device
Next type: fastboot flashing unlock
Fastboot and your phone will ask you to confirm that you want to unlock your bootloader, confirm it using the volume buttons on your phone according to the instructions on your phones screen.
After the bootloader has unlocked successfully you need to format your device, type: fastboot erase userdata
You'll receive a confirmation that data has been formatted.
Type: fastboot erase system
You'll receive a confirmation that system has been formatted.
Now you can flash the system image, type: fastboot flash system system.img
This will take a while until all the data is sent and installed on your phone. You will receive a progress report and confirmation when it's done.
Finally type: fastboot reboot
You phone will reboot and load the new system for the first time, this takes around 2-3 minutes, be patient. You can disconnect the USB cable now. When the welcome screen pops up set up everything as usual and enjoy

Thanx a lot for the instructions.
It's worked out. Everything works fine.

Great to hear!
AOSP really is a blessing, big thanks to @phhusson for all his work on this too.
This device even beats the legendary K10000 in endurance, my current record stands at 12 days and 34h SOT xD

The only things missing is double tap to wake and the ability to disable the second sim card. Otherwise almost perfect. :good:

After watching the WP6 violence test video and also seeing several other positive reviews I decided to buy one...
Recieved it a couple of days ago and seems like a great phone, very impressed with the speed, battery, heft and general rugged feel of it etc..
However... this morning I dropped it out of my pocket (from no higher than 3ft) onto some gravel and was horrified to discover around 7 little scratches/idents/scuffs to the screen!
How can this possibly be after all I saw it put through? In the advert video it shows someone dropping the phone and picking it up without even needing to check it's OK which kind of implies it's not gonna get scratched easily. Either way I'm gutted!!
By contrast, I've had my HTC M8 for 3 years and has been dropped loads of times and doesn't have a single one of these indented scuffs to the screen, despite it not making any of the claims to ruggedness like the WP6.

I bought my WP6 just last week, and am really impressed with it running Nova launcher, battery life and performance are great! Unfortunately the sheer mass of the phone means it will damage itself in a fall. My old Runbo X5 would probably fare better in a fall, being much lighter, but nowhere near as good a phone.

Are you running the stock ROM or also AOSP @markpab ?
v220 is out here, in-call volume not fixed, maybe the SIM issue mentioned above, would someone like to try?
@TpX Thinnr, that's surprising. Mine fell on some gravel as well last week, but the only thing I can see is a little scratch on the rubbery corner top left of the device.

Yes, I'm running totally stock ROM, been ages since I last rooted a phone (Runbo X5). 5 days since first full charge, and still at 34%!

GroovyG said:
Are you running the stock ROM or also AOSP @markpab ?
v220 is out here, in-call volume not fixed, maybe the SIM issue mentioned above, would someone like to try?
No. No changes regarding bugs in v220.
I have installed Havoc-OS 3.6 now.:
https://sourceforge.net/projects/ha...00613-Official-GApps-arm64-ab.img.xz/download
This allows you to set at least two separate tones for the simcards. I then created a silent tone for the second simcard. If you can't deactivate the second card, at least I am at peace.
Click to expand...
Click to collapse

markpab said:
Yes, I'm running totally stock ROM, been ages since I last rooted a phone (Runbo X5). 5 days since first full charge, and still at 34%!
Click to expand...
Click to collapse
And you don't have the problem that all background apps are closed and no more notifications arrive after a while?

I get notifications from emails and texts no problem, but apps from the Playstore don't update or stop, such as battery widgets, status bar calendars, and some clock widgets. All the built in apps are fine.

Hi, My New wp6 is bricked. I need stock firmware [emoji20]
Enviado desde mi F5321 mediante Tapatalk

oscarhugo said:
Hi, My New wp6 is bricked. I need stock firmware [emoji20]
Enviado desde mi F5321 mediante Tapatalk
Click to expand...
Click to collapse
You can download the original stock rom directly from the oukitel website:
https://mega.nz/file/3NFFQaxZ#Wk8S5G-iqBpJI5HDK-AXMGebNDiRVdUMAGthW_JANS0
You don't need to create an account there.
But I don´t know how to install the rom. Someone else would have to explain that here please.

Doesn't work, i tried to flash and is not possible say: chip type not match!! target chip type is mt6771 load scatter chip type is mt6737.
old firmware?

What exactly did you do to "brick" it? You can't really totally brick those devices.
Can you still access it with ADB and/or fastboot? If so, just flash a GSI and you're back in business.

Totally bricked, no power... black screen. I try to flash with sp flash tool
Enviado desde mi F5321 mediante Tapatalk

Did you manage to recover it with SP Flash Tool?
I'm still curious what you did to cause the brick, would be helpful for others too if you let us know what you did.

Was a New phone, works great without sim. Once i put sim, crashing... And Black screen.. Bricked. [emoji20]
I can flash with sp tools but i need firmware for mt6771

Using ADB in recovery mode - recovering files from a locked phone

Hello, here's my problem: I accidentally put a schematic as a code on my phone that I immediately forgot. Now that I only have access to the lock screen, I can't put my phone in file transfer mode because I'd like to retrieve it before resetting my phone (which is, by the way, a Redmi Note 6 pro up-to-date, not rooted, no TWRP, and the bootloader is still locked). It's possible to use ADB to retrieve files, but I can't allow access to the computer from my phone either, so ADb is unusable when my phone is turned on. Nevertheless, it's obviously possible to use it in recovery mode, if you have the right drivers. I went to look for them, but during the installation, Windows tells me that a better driver, ADB devices, is already installed, and I can't install my driver. I obviously tried to find a way to ignore this warning, notably by asking during the manual driver installation to search the hard drive, but it tells me via this method that no driver is contained in the indicated directory (which is wrong, at least from what I see, the necessary files are all there).
So I search either :
- a driver that won't have this problem and that will allow adb to work in recovery mode;
- a way to force the installation of this driver;
- another way to use ADB in recovery mode;
- another way to recover my files while the phone is locked and I can't give it access to the computer.
Otherwise, any idea that can solve my problem is fine with me.
Thank you in advance and have a nice day!

https://c.mi.com/thread-2207444-1-0.html
For drivers.
And use OrangeFox Recovery

He can't install any custom rec. The phone not unlocked. I don't think you have a Chance to get your data. For future make the most files that you don't wanna Lose on a sd card not on intern storage.
Update: on little search on Google i found this Blog. https://www.androiddata-recovery.com/blog/how-to-retrieve-deleted-data-from-xiaomi-redmi-phones
On method 4 is maybe a reason for your matter.

ALcAtRas500 said:
He can't install any custom rec. The phone not unlocked. I don't think you have a Chance to get your data. For future make the most files that you don't wanna Lose on a sd card not on intern storage.
Update: on little search on Google i found this Blog.
On method 4 is maybe a reason for your matter.
Click to expand...
Click to collapse
Thanks, I will try this and and I'll up the topic and say whether or not I passed. And don't worry, I won't make that mistake twice, that'll teach me...

Kyrela said:
Thanks, I will try this and and I'll up the topic and say whether or not I passed. And don't worry, I won't make that mistake twice, that'll teach me...
Click to expand...
Click to collapse
The message wasn't sent... well, I was saying that the website was affiliated with a software, and was totally lying since the data recovery function is only compatible with samsung. So it looks like there's no solution for me...

Kyrela said:
The message wasn't sent... well, I was saying that the website was affiliated with a software, and was totally lying since the data recovery function is only compatible with samsung. So it looks like there's no solution for me...
Click to expand...
Click to collapse
Unfortunately for you you cannot recover your files. As your phone's bootloader is locked and even though some softwares claim to work even with formatted phones they don't because of encryption and this new type of formatting where the data gets destroyed. Even It happened to me once I had unlocked and rotted my phone by for some reason when I was going back to stock ROM my phone data got destroyed dueto my carelessness during encryption and that's the story. After that I tried different softwares to recover photos but non of them worked. Only thing is you can get your Device unlocked

Redmi Note 6 Pro Unbrick in EDL Mode - I Need Help!

Hi everyone,
I seriously need some advices since I can't manage to solve my problem.
BEFORE YOU READ:
A month has passed, and I couldn't manage to recover my phone. I decided to buy a brand new phone for my brother.
The thread is going to stay there, since I hope it could be useful for people luckier than myself
The Problem:
My brother found his phone (the Redmi Note 6 Pro) turned off.
He wasn't able to turn it on.
I could manage to wake it up by pressing volume-up + power
very strangely, it directly turned into the OS (and not into the TWRP)
"but ok, at least it turned on" I thought
After only a few minutes, the phone suddenly turned off and from there my journey started to became a p**p
I'm not able to enter into recovery, and I'm not able to enter into fastboot neither.
I realized that the phone is fu--- ehmm I mean bricked. The funny thing is that we haven't done anything strange.
Some useful informations:
latest TWRP was installed
I was on the latest Pixel Experience Extended ROM (Android 11)
No custom kernel (I kept the kernel included in the PEE ROM)
No Root
What I tried:
Since it was impossible to do anything, I followed some guides (found here and on Youtube as well) and I opened my phone (if I'm lucky, I haven't destroyed anything ---- YET ).
I managed to enter in EDL mode
my Windows PC is able to recognize it on the COM / LPT ports as Qualcomm HS-USB QDLoader 9008
I downloaded the Mi Flash Tool
I downloaded the Boot Firmware and the two special files (prog_emmc_firehose_Sdm660_ddr.elf and prog_emmc_firehose_Sdm660_lite.elf) following this video link (please don't blame me, but I haven't found anything here)
I put the files inside the image folder
I tried to flash the firmware via Mi Flash but I got a funny error: "cannot receive hello packet"
Thinking that I was doing something wrong, I downloaded the latest Mi Flash Tool but nothing
I downloaded the latest tulip global image but nothing
I authenticated with the mi account into the tool (technically it shouldn't be needed) and... guess what? nothing.
I'm totally out of ideas. Of course I tried to reconnect the phone multiple times (shortening the two pins every time). I also tried to disconnect the battery and going USB-power-only.
Every time I get the "cannot receive hello packet" error, and suddenly the procedure fails saying "Riferimento ad un oggetto non impostato su un'istanza di un oggetto" (italian, that means "Object reference not set to an instance of an object").
EDIT: this error is also listed as "Null Reference Exception" (since it seems to be caused by the following exception: "System.NullReferenceException" - as you can read in the log I included)
Any ideas? What else can I try? Have I done anything wrong?
This never happened me before in almost 10 years of flashing. And, you know what? I just learned how to destr--- ehm open a phone! (...I used the little metal tab inside a Monster Energy can as tool *coff coff* -- C Y B E R P U N K)
Thanks to everyone that will try to help me. Every suggestion is appreciated*
*but please don't suggest me a trash can
Mi Flash Log:
Spoiler: Mi Flash Log
[15:18:15 COM6]:MiFlash 2020.3.14.0
[15:18:15 COM6]:vboytest index:6
[15:18:15 COM6]:flash in thread name:COM6,id:15
[15:18:15 COM6]:sw in images
[15:18:15 COM6]:flash in thread name:COM6,id:15
[15:18:15 COM6]:vboytest do open :
[15:18:15 COM6]: serial port COM6 opend successfully
[15:18:15 COM6]:[COM6]:start flash.
[15:18:16 COM6]:cannot receive hello packet,MiFlash is trying to reset status!
[15:18:17 COM6]:try to reset status.
[15:18:17 COM6]:Switch mode back
[15:18:17 COM6]:cannot receive hello packet,MiFlash is trying to reset status!
[15:18:17 COM6]:System.NullReferenceException: Riferimento a un oggetto non impostato su un'istanza di oggetto.
in XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer(Int32 programmertype)
in XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() in XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer(Int32 programmertype)
in XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash()
[15:18:17 COM6]:no provision exit:COM6
[15:18:17 COM6]:flashSuccess False
[15:18:17 COM6]:isFactory False CheckCPUID False
[15:18:18 COM6]:before:flashSuccess is False set IsUpdate:True set IsDone True
[15:18:18 COM6]:after:flashSuccess is False set IsUpdate:false set IsDone true

Little Update:
tried to disable windows' driver signature: same issue
tried to disconnect the phone display (seems weird, but why not giving it a chance): same issue.
I also downloaded Mi Flash Pro, which should work even without an authorized Mi account. But I get the same damn error.

Disperate up. You guys are my last hope.

Hello @Gh_Racer I got the exact same problem. Found my phone turned off 2 days ago, when I tried to turn it on the miui logo appeared. turned off and that was it. Not been able to turn it on after that. Did u by any chance fix the problem? Thanks!

fawziX said:
Hello @Gh_Racer I got the exact same problem. Found my phone turned off 2 days ago, when I tried to turn it on the miui logo appeared. turned off and that was it. Not been able to turn it on after that. Did u by any chance fix the problem? Thanks!
Click to expand...
Click to collapse
Damn, really? That's pretty disappointing. These cases are becoming suspicious... maybe that could be some kind of programmed obsolescence(?)
Just for curiosity: were you on stock MIUI or did you have any kind of modifications?
Unfortunately, I couldn't manage to do anything so far.
I loaned my old OnePlus 5T to my brother for now and I think that we'll buy a Redmi Note 10 as soon it will became available in our country. Of course I'm still here for any kind of suggestion until then.

Gh_Racer said:
Damn, really? That's pretty disappointing. These cases are becoming suspicious... maybe that could be some kind of programmed obsolescence(?)
Just for curiosity: were you on stock MIUI or did you have any kind of modifications?
Unfortunately, I couldn't manage to do anything so far.
I loaned my old OnePlus 5T to my brother for now and I think that we'll buy a Redmi Note 10 as soon it will became available in our country. Of course I'm still here for any kind of suggestion until then.
Click to expand...
Click to collapse
I was on the official MIUI, I didn't do any kind of modifications to the phone. I found it also weird that we have the same problem around the same time. Maybe it's related to an automatic update? mine was like that when I woke up in the morning the day before it was in perfect condition. Let me know if u manage to somehow fix it and I'll let u know if i get it working. (btw I also ordered a new XIAOMI phone red note 9 pro lol)

fawziX said:
I was on the official MIUI, I didn't do any kind of modifications to the phone. I found it also weird that we have the same problem around the same time. Maybe it's related to an automatic update? mine was like that when I woke up in the morning the day before it was in perfect condition. Let me know if u manage to somehow fix it and I'll let u know if i get it working. (btw I also ordered a new XIAOMI phone red note 9 pro lol)
Click to expand...
Click to collapse
I was on a custom ROM, as I said in my original post, so I won't point my finger to an automatic update. Maybe, maybe, some google-thing update? But I'm really sceptical that it would even be possible to hard brick a device in this way.
That's really weird, anyway.
Ps. Have you tried to open the phone and flash the fastboot + ROM in EDL mode?

I have not tried it yet. Do u have some links or tutorials on how to do this? I just received the kit to open the phone. I thought at first it might be a battery problem since the phone doesn't seem to charge at all when I plug it in electricity.

fawziX said:
I have not tried it yet. Do u have some links or tutorials on how to do this? I just received the kit to open the phone. I thought at first it might be a battery problem since the phone doesn't seem to charge at all when I plug it in electricity.
Click to expand...
Click to collapse
Here are some videos I followed. Do it at your own risk.
Phone Open + EDL Test Points *
Mi Flash Procedure in EDL Mode**
if the phone is not recognized as Qualcomm HS-USB QDLoader 9008, you need to install the drivers
This should work for both locked and unlocked bootloader devices, if I'm not wrong.
Here's another useful and complete guide.
This guide is not for the Redmi Note 6 Pro, so don't use the provided ROM and fastboot. Just follow the procedure, that it's the same for every Xiaomi phone.
* I don't know what kind of nails that guy has lol Keep in mind that you have to heat the phone up with an hair dryer in order to be able to work with the tools (the body is pretty tight).
In the video is not clear, but the phone has two slots: the first one is made for replacing the screen, and the second is made for taking apart the back cover. Pay attention to this (I didn't know this detail, and I took apart my screen during the first attempt).
** During the flash procedure, I get the error I mentioned in my original post. I'm not sure if it's related to having an un-authorized Mi account or whatsoever, I haven't found any clear confirmation about that.

Gh_Racer said:
Here are some videos I followed. Do it at your own risk.
Phone Open + EDL Test Points *
Mi Flash Procedure in EDL Mode**
if the phone is not recognized as Qualcomm HS-USB QDLoader 9008, you need to install the drivers
This should work for both locked and unlocked bootloader devices, if I'm not wrong.
Here's another useful and complete guide.
This guide is not for the Redmi Note 6 Pro, so don't use the provided ROM and fastboot. Just follow the procedure, that it's the same for every Xiaomi phone.
* I don't know what kind of nails that guy has lol Keep in mind that you have to heat the phone up with an hair dryer in order to be able to work with the tools (the body is pretty tight).
In the video is not clear, but the phone has two slots: the first one is made for replacing the screen, and the second is made for taking apart the back cover. Pay attention to this (I didn't know this detail, and I took apart my screen during the first attempt).
** During the flash procedure, I get the error I mentioned in my original post. I'm not sure if it's related to having an un-authorized Mi account or whatsoever, I haven't found any clear confirmation about that.
Click to expand...
Click to collapse
Thank you for the infos! I'll try to do this when I have some free time in the coming days and I'll let you know if I have any success.

fawziX said:
Thank you for the infos! I'll try to do this when I have some free time in the coming days and I'll let you know if I have any success.
Click to expand...
Click to collapse
I hope you'll be able to do something. Please update me in that case! Good luck.

Gh_Racer said:
I hope you'll be able to do something. Please update me in that case! Good luck.
Click to expand...
Click to collapse
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!

fawziX said:
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
Click to expand...
Click to collapse
Btw I also had the hello packet problem. But if u remove the usb cable from PC and then attach it again and refresh it dissapears but then after some time I have the weird xml error (resdump: <?xmlversion="1.0".........)

fawziX said:
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
Click to expand...
Click to collapse
I need to search for them, since I downloaded things from a lot of different sources (I also deleted the one I downloade, since I did lost my hopes). I’ll update you in case I’ll be able to find them.

fawziX said:
Btw I also had the hello packet problem. But if u remove the usb cable from PC and then attach it again and refresh it dissapears but then after some time I have the weird xml error (resdump: <?xmlversion="1.0".........)
Click to expand...
Click to collapse
So, exactly, what did you do? You unplugged the cable and attached it again shortening the two test pins? Or you simply attached it without doing anything special?
I wasn’t able to solve the hello packet error.
I don’t know what the xml error is related to, since I couldn’t manage to communicate with the phone. I have no suggestions for this, I’m sorry.

Hi everyone...
Two days ago my Note 6 Pro woke up the same and after doing everything described above and even being able to successfully flash via EDL,
it remains the same and without changes.
I explain...
It turns on and stays in the MI logo, when trying to enter the recovery it stays in the TWRP home screen and only allows to enter the FASTBOOT that is unlocked but when trying to flash from MiFlash it gives an error as when I try directly from. bat file so I decided to try for EDL and it threw the xml error (resdump: <? xmlversion = "1.0" .........), I did some research and it turns out due to "prog_emmc_firehose_Sdm660_ddr.elf" and "prog_emmc_firehose_Sdm660_lite.elf" in "images folder" to firmware uncompress files, and I replaced them with others that allowed the flash to continue and finish successfully, but to my surprise, when restarting the device, everything continued without any change...
Until this moment I do not find any information that can help with this unfortunately.
I just hope that some of the "Great GURUS" in the forum can help and provide some solution... If it exists.

fawziX said:
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
Click to expand...
Click to collapse
Tenho o redmi note 6 pro bloqueado no modo edl gostaria de saber se alguém tem como ajudar
MOD EDIT: Please post only in English according to the FORUM RULES or at least add an English translation below your foreign language(Google translator for example), translation added below:
I have the redmi note 6 pro locked in edl mode I wonder if anyone has how to help

Hi everyone, I’m sorry for having not replied yet.
As I wrote in my main post, I haven’t managed to recover my phone so far, so we decided to buy a brand new phone.
I hope you’ll be luckier than me.

Hi all, in order to flash your phone you will need authorized account normally, but if you try to flash stock firmware with Mi Flash tool and QFill you will face errors and errors.
What I recommend you is to re-flash full fastboot firmware the same version what you had on your phone or the latest stable fastboot firmware which you can get here:
Oreo Android 8 OEKMIXM
Pie Android 9 PEKMIXM
Latest version:
https://bigota.d.miui.com/V12.0.1.0.PEKMIXM/tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global_ac26982758.tgz
All versions:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Once you download firmware open it with 7-Zip archive tool, and again open firmware inside 7-Zip until you see normal folder with the name of firmware for example "tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global" and extract to desktop.
Once is Finish dowload this bypass auth files.
File with out Login
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Now copy those two files:
prog_emmc_firehose_Sdm660_ddr.elf
prog_emmc_firehose_Sdm660_lite.elf
and replace those two files inside firmware that you extracted before on Desktop for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global\images"
Next step is to use correct MiFlash tool which you can download here:
Working Mi Flash Tool:
MiFlash20160401.zip | by firmwarefile.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Now, load firmware inside Mi Flash tool:
for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global"
Next is to remove battery cover carefully because you can damage fingerprint flat cable!or use special edl cable if you don't wanna to open your device.
- Disconect battery
- short those test point pins
https://1.bp.blogspot.com/-C8bU7S6nAaI/Xqrd_PdvLXI/AAAAAAAAaLA/PK_E4oI_qPcJhBnSwlbQ0sr5J_9Ti2ycQCNcBGAsYHQ/s1600/21-14-47-images.jpg
-Plug the usb cable while you are holding those pins, once you got your device detected in Qdowloader 9008 mode relese short from test points.
Now click on Reflash on MiFlash tool and you will see your device is detected, now click on Flash and wait (it can take some time to finish). If you got error just unpplug the phone from PC and try again.
FOR FLASH OPTION:
You can check FLASH All or Flash all except storage
Once you successfully flashed your device, unplug device from your pc, plug battery back and power up your device to see if it's working or not.
The pay part if that doesn't work is reprograming or replacing emmc chip with ufi tool or something like that...
Good luck

Teddy Lo said:
Hi all, in order to flash your phone you will need authorized account normally, but if you try to flash stock firmware with Mi Flash tool and QFill you will face errors and errors.
What I recommend you is to re-flash full fastboot firmware the same version what you had on your phone or the latest stable fastboot firmware which you can get here:
Oreo Android 8 OEKMIXM
Pie Android 9 PEKMIXM
Latest version:
https://bigota.d.miui.com/V12.0.1.0.PEKMIXM/tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global_ac26982758.tgz
All versions:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Once you download firmware open it with 7-Zip archive tool, and again open firmware inside 7-Zip until you see normal folder with the name of firmware for example "tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global" and extract to desktop.
Once is Finish dowload this bypass auth files.
File with out Login
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Now copy those two files:
prog_emmc_firehose_Sdm660_ddr.elf
prog_emmc_firehose_Sdm660_lite.elf
and replace those two files inside firmware that you extracted before on Desktop for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global\images"
Next step is to use correct MiFlash tool which you can download here:
Working Mi Flash Tool:
MiFlash20160401.zip | by firmwarefile.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Now, load firmware inside Mi Flash tool:
for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global"
Next is to remove battery cover carefully because you can damage fingerprint flat cable!or use special edl cable if you don't wanna to open your device.
- Disconect battery
- short those test point pins
https://1.bp.blogspot.com/-C8bU7S6nAaI/Xqrd_PdvLXI/AAAAAAAAaLA/PK_E4oI_qPcJhBnSwlbQ0sr5J_9Ti2ycQCNcBGAsYHQ/s1600/21-14-47-images.jpg
-Plug the usb cable while you are holding those pins, once you got your device detected in Qdowloader 9008 mode relese short from test points.
Now click on Reflash on MiFlash tool and you will see your device is detected, now click on Flash and wait (it can take some time to finish). If you got error just unpplug the phone from PC and try again.
FOR FLASH OPTION:
You can check FLASH All or Flash all except storage
Once you successfully flashed your device, unplug device from your pc, plug battery back and power up your device to see if it's working or not.
The pay part if that doesn't work is reprograming or replacing emmc chip with ufi tool or something like that...
Good luck
Click to expand...
Click to collapse
I followed all the steps without any issues, since they were the same as I tried the last time, but a wanted to give a try to the files you linked me.
But... Unfortunately, I always get the same error. Probably, as you correctly pointed, that's an hw fault and there's nothing we can do.
I hope that someone will be luckier than me! I lost my hopes. RIP Redmi Note 6 Pro.