Database Users

Redmi pro rom problem

Hi everyone!
I have bougth a Redmi Pro on Gearbest and it came with Chinese/English Version of MIUI.
After a week of usage, i turned off my xiaomi and when i turned back on, it stucked on a Mi logo. Far as i discovered searching on web, it was a bug that other peopel have reported too.
I took a opportunity of having this bug to fix, to put other rom on the phone. A rom with Portuguese language witch is my mother lang.
I tried to put the new rom via "SP Flash took" with the fastboot mod but without success.
I requested the unlocking on Xiaomi Unlocking site and when they repplyed and i connected the xiaomi to the computer, the program (XiaomiMiFlash) gave me an error message telling ""Couldn´t verify device. Current account is diferent from the account info in the device"
No i can´t do nothing with the phone.
Can you guys have some idea how can i solve this?
Thank you all!

There is a good chance that the phone is already unlocked.
What was the problem with fastboot? Maybe drivers issue?
Have you tried flashing TWRP? If it takes then the phone is unlocked and you can proceed with flashing the xiaomi.eu or globerom.

kremmit said:
There is a good chance that the phone is already unlocked.
What was the problem with fastboot? Maybe drivers issue?
Have you tried flashing TWRP? If it takes then the phone is unlocked and you can proceed with flashing the xiaomi.eu or globerom.
Click to expand...
Click to collapse
Tks 4 the support!
About the Fastboot i putted the phone on fastboot mode and i disabled the Driver Signature Enforcement on Windows. I connected the phone to the computer and started to run the SP Flash Tool. After the process was completed it wont gave me any result because the phone still stucked on Mi logo..
I did'n tried the TWRP because in every tutorial tells me that i need to go to the Developer Mode and activate the USB debugging i can not access to that because the phone don't give me more than the Mi logo.

hmm the fastboot method should have worked. Have you tried it on another computer, maybe 32bit windows?
When finished flashing with miflash in fastboot did it say it was ok at the end or did it give you an error? Als tried to reboot a few times after flashing without usb cable in the phone?

kremmit said:
hmm the fastboot method should have worked. Have you tried it on another computer, maybe 32bit windows?
When finished flashing with miflash in fastboot did it say it was ok at the end or did it give you an error? Als tried to reboot a few times after flashing without usb cable in the phone?
Click to expand...
Click to collapse
Im losing my mind!
I tried again in my father's desktop wich have a 64bit windows 7 (I havent a 32 bit at home. I will try to get one borrowed)
I tried with the SP Flash Tool following a guide from "xiaomitips" and, in this computer, the program dornt even recognize my phone. I push the Download button but that give me no signal.
Is there any other way to do this? Other ways to put the rom in the phone? (Sorry the noob language)

franciscobcl said:
Im losing my mind!
I tried again in my father's desktop wich have a 64bit windows 7 (I havent a 32 bit at home. I will try to get one borrowed)
I tried with the SP Flash Tool following a guide from "xiaomitips" and, in this computer, the program dornt even recognize my phone. I push the Download button but that give me no signal.
Is there any other way to do this? Other ways to put the rom in the phone? (Sorry the noob language)
Click to expand...
Click to collapse
I'm out of ideas at this point.
I had some trouble with fastboot that my phone did restart when in fastboot mode.
Then i had to change the order of plugging in the cable and starting the program but after that all worked.
No idea what next ...

I had this issue with a Redmi 3. I can't remember the exact solution but I believe you have to have the developer ROM installed in order to unlock the bootloader. Maybe if you search for an anterior model such as the Redmi 3 you will find more information on how to load your ROM. I'm sure that it's the same method for most Xiaomi phones. Good luck!

I heard about do a Hard Reset but i dont know how to do that because i cant access to the OS of the xiaomi.
Is there a way to do a hard reset with the xiaomi stucked on Mi logo?
Tks!
Happy 2017 for all!

I tried to put my phone one Recovery Mode but it is blocked. Its like the phone on this video:
https://www.youtube.com/watch?v=tTzdQpex7BQ
How can i unlock this?

I never could get into the xiaomi recovery either but i managed to flash twrp through fastboot though.

franciscobcl said:
Tks 4 the support!
About the Fastboot i putted the phone on fastboot mode and i disabled the Driver Signature Enforcement on Windows. I connected the phone to the computer and started to run the SP Flash Tool. After the process was completed it wont gave me any result because the phone still stucked on Mi logo..
I did'n tried the TWRP because in every tutorial tells me that i need to go to the Developer Mode and activate the USB debugging i can not access to that because the phone don't give me more than the Mi logo.
Click to expand...
Click to collapse
Hi
Does your problem with sp flashtools and flashing the ROM be solved ?
Sent from my Redmi Pro

I had this problem, but I'd installed TWRP already. But you shouldn't need USB Debugging on to flash TWRP. If you manage to flash TWRP, flash a new ROM (I recommend xiaomi.eu (I think they have Portuguese)) and wipe the Dalvik cache, /cache, and /data (you probably won't have to wipe /data/media).

Miui themes
Sorry will start new item

Have you tried a different cable, that is why mine wasn't recognized at first.

I'm having the same problem here. The phone rebooted itself when I changed the locale, and hung at the Mi logo. I already had TWRP flashed. I also took the opportunity to install a new ROM; the Global Dev ROM. It installed with no errors and I wiped the Dalvik, cache, etc. Still hangs at the Mi logo, but this time without the little loading dots at the bottom. Any suggestions?
Update: I can bring it back to the original state with the loading dots and "powered by Android" at the bottom with a backup I took before flashing the new rom, but still no progress.

I managed to restore my phone using the video:
Flash Xiaomi Redmi Pro Using SP Flash Tool [Locked Bootloader]
I can't post links since I don't have enough posts here yet, but search for it on Youtube.
Update: It seems like the unlocking permissions on my account have been retroactively rejected, I wonder if that has something to do with it. I also can't seem to find the Global ROM for the Redmi Pro anymore, just the China one. Does anyone have a link for the official Global ROM on the Xiaomi site?
Update 2: Suddenly I have unlock permission again, without reapplying, so that's cool. I installed the Eu HMPro ROM, everything's working well so far.

Phosphenes said:
I managed to restore my phone using the video:
Flash Xiaomi Redmi Pro Using SP Flash Tool [Locked Bootloader]
I can't post links since I don't have enough posts here yet, but search for it on Youtube.
Update: It seems like the unlocking permissions on my account have been retroactively rejected, I wonder if that has something to do with it. I also can't seem to find the Global ROM for the Redmi Pro anymore, just the China one. Does anyone have a link for the official Global ROM on the Xiaomi site?
Update 2: Suddenly I have unlock permission again, without reapplying, so that's cool. I installed the Eu HMPro ROM, everything's working well so far.
Click to expand...
Click to collapse
What I did bro ?
I still have the same problem?

franciscobcl said:
Hi everyone!
I have bougth a Redmi Pro on Gearbest and it came with Chinese/English Version of MIUI.
After a week of usage, i turned off my xiaomi and when i turned back on, it stucked on a Mi logo. Far as i discovered searching on web, it was a bug that other peopel have reported too.
I took a opportunity of having this bug to fix, to put other rom on the phone. A rom with Portuguese language witch is my mother lang.
I tried to put the new rom via "SP Flash took" with the fastboot mod but without success.
I requested the unlocking on Xiaomi Unlocking site and when they repplyed and i connected the xiaomi to the computer, the program (XiaomiMiFlash) gave me an error message telling ""Couldn´t verify device. Current account is diferent from the account info in the device"
No i can´t do nothing with the phone.
Can you guys have some idea how can i solve this?
Thank you all!
Click to expand...
Click to collapse
You could try dowloading the official rom and then download the CHINESE version of mipc suite then enter fastboot and connect the phone
Normally the chinese mi pcsuite automaticly detects the phone is in fastboot mode, you could use google translate to translate it all just choose redmi pro on model selector (the top selection bar)the text there is untranslateable just choose the one that says pro
And then under it chose the one that translate to chinese
After That there's two tick box under it, choose the ROM you downloaded
After that chose the one that translate to install brush package, if it doesn't work choose the download brush package next to it
Thus method worked for me when my phone bricked hope it helps you

Extracting media from a locked Huawei P8 Lite with lost passphrase

Hello all,
I'm in possession of a Huawei P8 Lite of which the owner lost the passphrase. The question is whether the photos on the device can still be recoved. The bootloader of the device is currently locked. Debug mode is not enabled (nor is my computer authorized).
I was hoping that it would be possible to unlock the bootloader (which supposedly does not trigger a factory reset on this model?) - and then install a custom recovery from where I could backup the pictures. In order to unlock the bootloader, I would need IMEI-1 + IMEI-2 and the S/N. I was able to obtain one of the IMEIs by typing *#06# on the emergency call screen. Is there a way to obtain the other codes somehow (perhaps via fastboot)? Once I obtain the necessary information, my assumption is that I would be able to get an unlock code from Huawei after which I can unlock from fastboot. (Or does OEM unlock still need to be enabled from the developer options in Android?)
Edit: seems like the S/N is shown when connecting in fastboot mode and listing "fastboot devices".
Edit2: seems like obtaining the IMEI through the emergency call functionaltiy combined with the S/N is enough: I modified the "Product ID Generator" tool to include the "ALE-L21" model, and now it generates valid Product IDs that can be used on the Huawei website to obtain an unlock code.
Alternatively, I've noticed that there's an "emergency data backup" mode on this model, which I accidentally entered. I was hoping anyone knows more about this mode (note that this is different from the fastboot & rescue mode). I got booted into this mode because somehow the ext4 partition failed to mount during one of the many times I rebooted the phone. This mode also allowed me ADB access - however, this was a rescue OS which did not actually contain the user data. I would like to attempt to boot into this mode again, gain root access via a kernel exploit, and either read out the unlock code from /dev/block/mmcblk0p** or directly copy the media onto an SD card. Does anyone know how to "trigger" booting into this mode? The kernel code for the p8 lite seems to have a flag "CONFIG_FEATURE_HUAWEI_EMERGENCY_DATA" which enables this feature.
Pointers welcome
Note, I'm not desperate to recover the data - but this has become more of a "challenge" I'd like to solve.
Edit: I was able to unlock the bootloader with details obtained from the device. Unlocking the device did not initiate a wipe. Now it comes down to installing a recovery image and pulling the data

ce3c said:
Hello all,
I'm in possession of a Huawei P8 Lite of which the owner lost the passphrase. The question is whether the photos on the device can still be recoved. The bootloader of the device is currently locked. Debug mode is not enabled (nor is my computer authorized).
I was hoping that it would be possible to unlock the bootloader (which supposedly does not trigger a factory reset on this model?) - and then install a custom recovery from where I could backup the pictures. In order to unlock the bootloader, I would need IMEI-1 + IMEI-2 and the S/N. I was able to obtain one of the IMEIs by typing *#06# on the emergency call screen. Is there a way to obtain the other codes somehow (perhaps via fastboot)? Once I obtain the necessary information, my assumption is that I would be able to get an unlock code from Huawei after which I can unlock from fastboot. (Or does OEM unlock still need to be enabled from the developer options in Android?)
Edit: seems like the S/N is shown when connecting in fastboot mode and listing "fastboot devices".
Edit2: seems like obtaining the IMEI through the emergency call functionaltiy combined with the S/N is enough: I modified the "Product ID Generator" tool to include the "ALE-L21" model, and now it generates valid Product IDs that can be used on the Huawei website to obtain an unlock code.
Alternatively, I've noticed that there's an "emergency data backup" mode on this model, which I accidentally entered. I was hoping anyone knows more about this mode (note that this is different from the fastboot & rescue mode). I got booted into this mode because somehow the ext4 partition failed to mount during one of the many times I rebooted the phone. This mode also allowed me ADB access - however, this was a rescue OS which did not actually contain the user data. I would like to attempt to boot into this mode again, gain root access via a kernel exploit, and either read out the unlock code from /dev/block/mmcblk0p** or directly copy the media onto an SD card. Does anyone know how to "trigger" booting into this mode? The kernel code for the p8 lite seems to have a flag "CONFIG_FEATURE_HUAWEI_EMERGENCY_DATA" which enables this feature.
Pointers welcome
Note, I'm not desperate to recover the data - but this has become more of a "challenge" I'd like to solve.
Edit: I was able to unlock the bootloader with details obtained from the device. Unlocking the device did not initiate a wipe. Now it comes down to installing a recovery image and pulling the data
Click to expand...
Click to collapse
Now simply install twrp, connect to PC and you will be able to see all the files in Explorer

faby GT said:
Now simply install twrp, connect to PC and you will be able to see all the files in Explorer
Click to expand...
Click to collapse
With twrp you can delete lockscreen specific files to remove lock

Audriuskins said:
With twrp you can delete lockscreen specific files to remove lock
Click to expand...
Click to collapse
If you think about this, you can see how easy it is to unlock a phone (also for bad purposes...)

Agreed, I'm surprised that Huawei didn't force a device wipe before allowing OEM unlock. Especially because you can obtain all the details you need from the phone to obtain an unlock code on the Huawei website.
I indeed ended up installing TWRP and remove the password.key file to remove the lock

Flash Lenovo Tab M10 TB-X605L LTE with Stock Image Android 8 Oreo

Dear all,
Background: I’ve bought a brand new Lenovo Tab M10 TB-X605L LTE. It’s for my grandma, so that she can video-call her great-grandchildren during the Corona crises, and I learned that I require to have Android 8 Oreo on it, as Teamviewer Host has to run on it and start automatically (my grandma is almost 90 years and she can operate a toaster, but not a tablet). Unfortunately, I’ve upgraded to Android 9 Pie, which by design doesn’t support Teamviewer host.
The problem is: I need to get back to Android 8 Oreo, but I almost bricked my Lenovo Tab M10 by trying to do so. I’ve already spent a few days and read/tried tons of instructions/suggestions/forum discussions, and I’m completely stuck. I would really enjoy some help or the decisive tip – and especially my grandmother would really enjoy seeing her four great-grandchildren after three weeks of quarantine.
This works:
I managed to get a M10 TB-X605L stock ROM Android 8 Oreo: techswizz com/lenovo-tab-tb-x605l-stock-rom-firmware-flash-file/
I can reboot to fastflash mode (reboot and hold Volume-Down), and I can use ADB and Fastboot.
I can install TWRP recovery mode (by flashing recovery.img) and start/use TWRP (reboot and hold Volume-Up+Down).
I think I’ve unlocked the bootloader, but I’m not sure how to verify it.
I have installed the Qualcomm_USB_Driver_v1.0 and the tablet gets a COM port (can be seen in Device Manager).
This doesn’t work:
General
I cannot boot in normal mode (device stops or constantly reboots when I try).
I managed to install Magisk (in TWRP), but the devices still can’t boot in normal mode afterwards, so I cannot start Magisk.
Lenovo Moto Smart Assistant
I can start it, download the stock image. When I try to flash the device, the progress bar jumps to 33% immediately, and after a few seconds a “FAIL” button appears without any further information.
Fastboot
I can flash boot.img and recovery.img, but system.img is splitted in system_1.img, system_2.img, etc., and when I connect these files with packsparseimg.exe, the resulting system.img seems to be invalid (devices doesn’t start).
QFIL
I can see the devices on the COM Port. I can load rawprogram_unsparse.xml and patch0.xml.
When the device comes online, I try to hit Download immediately, and I either get the following error:
[*]ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
[*]ERROR: function: sahara_main:924 Sahara protocol error
[*]ERROR: function: main:303 Uploading Image using Sahara protocol failed
[*]Download Fail:Sahara Fail:QSaharaServer Failrocess fail
[*]or it says the device is not in EDL mode (which is easy to fix by booting in EDL mode from TWRP, but then the sahara error comes up).​
QPST
I can connect the phone via QPST Configuration (COM3, Q/QCPP-XXX (Sarah Download), USB)-
When I open the “eMMC Software Download app”, I can open the Sahara XML file rawprogram_unsparse.xml – I hope, that’s the right one.
When I “Load XML def…”, I don’t know which xml file to open:
[*]rawprogram_unsparse.xml and rawprogram0.xml.bak show an error “Document error on element type ‘raw program’ and name/value ‘true’”.
[*]Patch0.xml shows no error, but I think it’s the wrong file for “Load XML def”.​
Dowloading with “Patch0.xml” leads to an error “Timeout waiting for device”
QcomDLoader.exe (1.3.2.0)
I can „load“ the stock image directory, and set the settings (eMMC programmer: prog_emmc_firehose_8953_lite.mbn, Raw program: rawprogram_unsparse.xml, patch0: patch0.xml).
Wenn I press ‘Start’ the Step/Status “Sahara/Flashing” appears for 5 seconds, followed by messages “failed.
Any help or suggestion is highly appreciated.
Kind regards,
Walter

Hey,
i have the same device and a similar situation - any news on this?
@OP: How did you proceed? Different device, any alternative to teamviewer?

Solution for flashing Qualcomm based Android devices
Dear all,
please find the solution for for flashing Qualcomm based Android devices (sahara_rx_data error) here: https://android.stackexchange.com/questions/224369/cannot-flash-qualcomm-with-stock-image-lenovo-tab-m10-tb-x605l-lte-android-8-o?noredirect=1#comment291391_224369
Kind regards
PS: I'm not allowed to post links here. Can someone please copy-paste the link and add it here?

--SOLUTION TO FLASHING QUALCOMM BASED ANDROID DEVICES-----
Cannot flash Qualcomm with Stock Image (Lenovo Tab M10 TB-X605L LTE, Android 8 Oreo)
Background I’ve bought a brand new Lenovo Tab M10 TB-X605L LTE. It’s for my grandma, so that she can video-call her great-grandchildren during the Corona crises, and I learned that I require to have
android.stackexchange.com

Mi A1 QPST Backup file

Hi guys,
Anyone got a full qualcomm backup of their mi A1? I've suffered power failure during Mi Flash and it seems it corrupted the whole memory and altho it's in download mode(I get it to qualcomm 900E and 9008 ports), I think the only solution is full phone factory image backup since if I try with Mi Flash or QPST I get the Sahara error 9 regardless of what programmer (prog_emmc_firehose) I try.

It's ALIVE!.
Just to update that after debugging the whole windows com stack I struck on a wall and it seems that windows 7 and 10 block something there (I manage to get out of the driver to win kernel on debug but then it fails and didn't had any more nerves to deal with and I'm not a windows guy myself).
So the only solution for low lvl writing is to use linux with point boot to EDL. It seems that for mi A1 even if Qualcomm's boot chain is broken (https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html) it should fall to EDL in most cases but in our phone (global version at least) it goes to diagnostic mode (not to be confused with Download mode) regardless of drivers in windows - this is hardwired in the chip. So under linux you should fall in to download mode with hardware short of motherboard points to fall in to the correct mode. You should forget about windows as it depends too much on the selected driver (yes you can manually change driver and fu** the whole chain of communication). You need to hardwarely go to Download mode. Don't believe what windows reports.
From there you can use QDL (check documentation on how to install (you'll also need to install gcc (ubuntu - apt get install gcc) https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md).
Then download a full firmware flash from xiaomi (that's for MiFlash) and use the files in the images folder for the command ( for instance to be more easy copy images folder to qdl folder and:
./qdl --debug --storage emmc --include 'images' 'images/prog_emmc_firehose_8953_ddr.mbn' 'images/rawprogram0.xml' 'images/patch0.xml')
This will fix the first part of the qualcomm bootchain from there you will have access to fastboot and then use all other tutorials concerning fixes from fastboot.
If enough ppl want it I'll write extended tutorial in the other section.

Kindly do an extend tutorial... And tag me please, if you decide to.
Thanks.

(SOLVED) Urgent ! My OP8P is dead I think, stuck Fastboot

Hello everyone !
I'm new on this forum but I really need your help. I tried to fix my mistake all day long yesterday (9am to 2am non stop).
So, basically, I have a OnePlus 8 Pro, Model IN2023.
I had OOS 11 updated. I tried to install OOS 12 Bêta and I did but I had a indian version so a lot of bugs.
I wanted to go back to OOS 11 but it was impossible because I was now in an indian version.
I tried with MyApplication2 to local upgrade and downgrade as recommand in Internet.
I tried to unlock bootloader and the following steps but here my problem:
I unlocked my bootloader then I misclick and I locked again my bootloader.
Then my phone just crashed and put this message:
"The current image (boot/recovery) have been destroyed and can not boot."
So, I forced to turn off the phone and try to go in EDL mode but:
1. ADB doesn't work anymore
2. Fastboot work fine
3. EDL mode is impossible
So, my bootloader is unlocked again. My phone is stuck on Fastboot mode:
Fastboot mode
Product_name - kona
Variant - SM8 UFS
Bootloader version -
Baseband version -
Serial number - eed52b71
Secure boot - yes
Device state - unlocked
I used the official firmware on OnePlus website, I used Python and Payload_dumper.py to have the .img from the .bin of the official firmware.
I tried to flash all the images, I tried to install TWRP, I tried almost everything I found but still stuck in Fastboot. Recovery mode doesn't work.
I tried to boot, to flash, to do everything I could.
I also tried MSM Download Tool but nothing appears inside.
Now, when I connect my phone, it's with a cable in USB-C but 3.0, not 2.0. Maybe that's the problem ?
When I plug my phone, in Device Manager, I have a "!" but the phone is recognized under
"Qualcomm HS-USB QDLoader 9008 (COM6). When I click on it, it says (sorry, I'm about to translate from french):
"Windows can not verify the numeric signature for the drives required for this peripheric. It is possible that a material ou software modification has been installed a corrupted file or with an incorrect signature, or it is a malware from an unknown source (Code 52)"
Please help me, contact me on Whatsapp, or here. Let's do this in direct.
Btw, I have a Macbook Pro to do all this. I used also Windows with Bootcamp.

So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.

andshura said:
So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.
Click to expand...
Click to collapse
Im happy you fixed your phone.
Read this before you even think to go to A12 again on this device.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com