Related
I know that this handset is not release yet but I'd like to know if there would be support for it from the community. I'm excited about it because I've been waiting for a handset that seems to meet all my niche requirements:
Medium size screen (4.5")
ARMv8 instruction set (Snapdragon 410)
Removable battery (According to quick set up manual)
MicroSD slot (full size SD would have been nice but this is good enough)
Dual Sim (not sure if it will be available in the UK though )
I know the screen is not the best and it probably won't support Qi charging but I don't think any other handset has all the aforementioned features. I'm not trying to sell the handset but this is in anticipation of posts like "why not get a Nexus" or "just get a Moto G"
It's a nice phone, I bought one for my wife
This one is not available in my region. I got the Y550 instead for a relative. Almost the same spec. Not sure about IO performance though as I didn't have time to check.
Solution?
So, I was searching Google for OT 5042 root (the internal name of Alcatel OT Pop 2 or Orange Roya (NOS Roya in Portugal)), and I've found these instructions on a russian forum. I have not tested them myself, but they do seem very legit, so if anyone who knows exactly what he's doing or has no fear of losing the phone can follow it up.
Disclaimer: The procedure that follows has not been yet tested by me. Proceed at your own risk. You are fully responsible for what happens to your phone from now on. If you have some knowledge on russian, please help translating the board mentioned on the Youtube video description (/watch?v=8tD4kR33vVE).
Note on translation: This post was initially writen in russian and translated with Google translate with some fixes here and there made by me. I'm not a native english speaker and therefore some engrish may be present. Please forgive me for it.
Note to users: This tutorial is regarding the dual SIM version of this phone. It may not work with the single SIM one.
Root dual SIM Alcatel Alcatel OneTouch 5042D POP 2 smartphone
Author: ruslan_3_ from 4pda.ru
Procedure:
1. Download the attached .zip file and extract it to some folder on your computer.
1.1. Install the phone's adb drivers (not needed under Linux or OS X; Windows drivers are available on the phone as a CD-ROM);
1.2 Copy update.zip to the root of your phone's internal memory or SD Card (one of the two may not work, and there is different feedback regarding this issue)
2. Turn on USB debugging
3. Turn on the phone in fastboot mode (press and hold both power and volume down buttons);
3.1 Connect the phone to your computer and wait for the drivers to finish installing (when applied);
4. Open a command prompt where you first extraced the files and type:
HTML:
fastboot -i 0x1bbb devices
It will list all devices connected to the computer on fastboot mode, for example a409dc4d.
6. Install CWM Recovery:
HTML:
fastboot -i 0x1bbb flash recovery image-new.img
7. Enter recovery mode (power + volume up)
8. Install update.zip
Once again, please be very carefully when executing this procedure. It can go really wrong.
If you're using Mac or Linux, paste the specific android SDK tools in the extracted folder and run fastboot with the command ./fastboot if you don't have an alias for it in your .profile or .bashrc (if you don't know what this is, ignore it ).
@imTos, Thanks for information, but you know if there is any custom rom (CM or MIUI) for this equipment, specifically for the version of the 5042A one SIM ??
Thank You ...
Regarding the root procedure, I was told on a portuguese board that it works for any 5042 model.
herbesi01 said:
@imTos, Thanks for information, but you know if there is any custom rom (CM or MIUI) for this equipment, specifically for the version of the 5042A one SIM ??
Thank You ...
Click to expand...
Click to collapse
Hey. I am not aware of any alternative ROM currently on the Internet, especially since Alcatel has not released the phone's source code yet. What I do know, however, is that there are three ROMs for this device: Alcatel's original ROM (build 010 03 single/dual SIM), Orange ROM (single SIM) and the portuguese NOS ROM (build 010 06, single SIM). Between the three, as far as I know, the portuguese one is the one that most ressembles AOSP w/ Google Play and with no bloatware installed by default, from what I've seen in pictures. I don't know if it is possible for the users of the different ROMs to make NANDroid backups and share them online, though it wouldn't be a full help. Keep in mind that both chinese and russian ROMS, from what I've read (and I have no way to confirm if this is true or not!), have a function to report stolen phones, and this text messages a foreign number if you're living outside these countries.
Offtopic: I waste more time trying to guess the captcha than replying to a post. Google, where's the new noCaptcha function?
imTos said:
So, I was searching Google for OT 5042 root (the internal name of Alcatel OT Pop 2 or Orange Roya (NOS Roya in Portugal)), and I've found these instructions on a russian forum. I have not tested them myself, but they do seem very legit, so if anyone who knows exactly what he's doing or has no fear of losing the phone can follow it up.
Disclaimer: The procedure that follows has not been yet tested by me. Proceed at your own risk. You are fully responsible for what happens to your phone from now on. If you have some knowledge on russian, please help translating the board mentioned on the Youtube video description (/watch?v=8tD4kR33vVE).
Note on translation: This post was initially writen in russian and translated with Google translate with some fixes here and there made by me. I'm not a native english speaker and therefore some engrish may be present. Please forgive me for it.
Note to users: This tutorial is regarding the dual SIM version of this phone. It may not work with the single SIM one.
Root dual SIM Alcatel Alcatel OneTouch 5042D POP 2 smartphone
Author: ruslan_3_ from 4pda.ru
Procedure:
1. Download the attached .zip file and extract it to some folder on your computer.
1.1. Install the phone's adb drivers (not needed under Linux or OS X; Windows drivers are available on the phone as a CD-ROM);
1.2 Copy update.zip to the root of your phone's SD Card (internal memory may not work)
2. Turn on USB debugging
3. Turn on the phone in fastboot mode (press and hold both power and volume down buttons);
3.1 Connect the phone to your computer and wait for the drivers to finish installing (when applied);
4. Open a command prompt where you first extraced the files and type:
HTML:
fastboot -i 0x1bbb devices
It will list all devices connected to the computer on fastboot mode, for example a409dc4d.
6. Install CWM Recovery:
HTML:
fastboot -i 0x1bbb flash recovery image-new.img
7. Enter recovery mode (power + volume up)
8. Install update.zip
Once again, please be very carefully when executing this procedure. It can go really wrong.
If you're using Mac or Linux, paste the specific android SDK tools in the extracted folder and run fastboot with the command ./fastboot if you don't have an alias for it in your .profile or .bashrc (if you don't know what this is, ignore it ).
Click to expand...
Click to collapse
this method for root work very well on my Orange Roya
thanks for share it
Worked like a charm on single sim
I would love to see running android l on this device! i mean into 5042a
Please
Hi, i did try to root this phone as you show but after some tries this stuck on load, and dont turn on ok...
i did try hard reset, wipe cache, wipe data, erase from fastboot and a lot of things but always keep on Logo... so could you do a backup from your handset and share it with me please?
i will apreciate it a lot. thanks in advance
I've asked for a backup in many online communities, but no luck. As I said, I didn't try the method myself since I didn't need to use root yet and my phone is still under warranty. Sorry.
imTos said:
I've asked for a backup in many online communities, but no luck. As I said, I didn't try the method myself since I didn't need to use root yet and my phone is still under warranty. Sorry.
Click to expand...
Click to collapse
lol mine is under warranty too.
Root it and if u need to send to warranty u can use Mobile Upgrade Q to restore original firmware.
I cant enter in fastboot can anyone help me please
rushwhq said:
lol mine is under warranty too.
Root it and if u need to send to warranty u can use Mobile Upgrade Q to restore original firmware.
Click to expand...
Click to collapse
Are you sure that can be restored By mobile upgrade?
if bricked : recover phone using Alcatel official tool
Mobile Upgrade Q 4.6.8 Setup.rar
goto http://www.alcatelonetouch.com/global-en/products/smartphones/pop_2-4-5.html
and select the "Support" tab, there download
Mobile Upgrade Q 4.6.8 Setup.rar
link:
http://www.alcatelonetouch.com/glob...OP_2-4-5/otu/mobile-upgrade-q-4-6-8-setup.rar
unrar, start and select 5042D, connect phone via USB cable, start flashing
I had my Pop 2 bricked (eternal boot loop) but got it back to life, 100%
---------- Post added at 10:10 PM ---------- Previous post was at 10:05 PM ----------
in the "russian" tutorial they tell you to copy "update.zip" to your SD card - that did not work for me !
- on the external card cwm did not find the file.
instead update.zip was only found once it was on the INTERNAL SD card !!
Hey guys.
I've found very useful information like stock recovery, stock images, and user custom images for this device on the same board I found the root method. I still haven't had the courage to root my device, though, and I feel kind of an hypocrite because of it, but this is my only phone, and if something had gone wrong I would have no money to buy a new one. I know I'm not the only one in this situation, and I do feel really bad for not helping users that have requested for my help.
I need to know if Mobile Upgrade Q can recognize the device and reinstall the ROM if anything goes wrong. To those who had any problem, was it able to fix it? Were you using stock recovery or CWM when you tryed it (I'm not sure if this is relevant)?
I will update this board (or create a new one?) regarding this device with useful information I've found online, and since stock recovery is already available (that was the main reason I didn't root in the first place (warranty)), I will provide a (not rooted) factory image of the custom build 010 06 when I have time to do so.
hey buddy
i restore my to thr original rom with mobile q. but looks like i upgrade the firmware, and now i cant root again, because i cant put in fastboot "vol - + pwr".
Which exactly build do u have ?
imTos said:
Hey guys.
I've found very useful information like stock recovery, stock images, and user custom images for this device on the same board I found the root method. I still haven't had the courage to root my device, though, and I feel kind of an hypocrite because of it, but this is my only phone, and if something had gone wrong I would have no money to buy a new one. I know I'm not the only one in this situation, and I do feel really bad for not helping users that have requested for my help.
I need to know if Mobile Upgrade Q can recognize the device and reinstall the ROM if anything goes wrong. To those who had any problem, was it able to fix it? Were you using stock recovery or CWM when you tryed it (I'm not sure if this is relevant)?
I will update this board (or create a new one?) regarding this device with useful information I've found online, and since stock recovery is already available (that was the main reason I didn't root in the first place (warranty)), I will provide a (not rooted) factory image of the custom build 010 06 when I have time to do so.
Click to expand...
Click to collapse
---------- Post added at 09:17 AM ---------- Previous post was at 08:32 AM ----------
lol i managed to enter fastboot mode via adb command.. =D
hi, mi alcatel pop 2 wass bricked. When I try to unbrick with Mobile Upgrade it say that my phone is updated and it stop.
how can i unbrick my phone??!!
Please a need a backup from a Alcatel POP 2 ROM, i had bricked. Please could anyone upload it?
seryioo write me PM
---------- Post added at 06:26 AM ---------- Previous post was at 06:11 AM ----------
imTos said:
Regarding the root procedure, I was told on a portuguese board that it works for any 5042 model.
Hey. I am not aware of any alternative ROM currently on the Internet, especially since Alcatel has not released the phone's source code yet. What I do know, however, is that there are three ROMs for this device: Alcatel's original ROM (build 010 03 single/dual SIM), Orange ROM (single SIM) and the portuguese NOS ROM (build 010 06, single SIM). Between the three, as far as I know, the portuguese one is the one that most ressembles AOSP w/ Google Play and with no bloatware installed by default, from what I've seen in pictures. I don't know if it is possible for the users of the different ROMs to make NANDroid backups and share them online, though it wouldn't be a full help. Keep in mind that both chinese and russian ROMS, from what I've read (and I have no way to confirm if this is true or not!), have a function to report stolen phones, and this text messages a foreign number if you're living outside these countries.
Offtopic: I waste more time trying to guess the captcha than replying to a post. Google, where's the new noCaptcha function?
Click to expand...
Click to collapse
Hi
Alcatel has release the source code for this model
OT_5042X_20150310.tar.xz
So now can cook some cm rom or anyelse?
rushwhq said:
seryioo write me PM
Click to expand...
Click to collapse
Hi, I have bricked my phone. I tried to restore with Mobile Upgrade and with a Backup from CWM that I did, but with no result.
I would like you did a backup with the last version of TWRP, all partitions and upload:
Download, install like CWM: https://mega.co.nz/#!tQRzibAA!7tPkqlc1BYsvCCeQRzaqn_VVs959GBsleB_4eNVq9JE
Sources TWRP Recovery: http://4pda.ru/forum/index.php?showtopic=645507&st=340#entry38938719
Thank you.
I was trying to unlock with gc pro key with sprint unlock to work with gsm carriers and it didnt work for me. So i tried a different formula which i flashed a firmware "ZV3" on Z3X Box and i was running on ZV5. Now the phone doesnt turn on and when connected to computer the usb driver says "Qualcomm Usb USB QDLoader 9008. Any solutions will be highly appreciated and would save me on having to buy a customer a new phone.
First lesson.. don't downgrade any lg latest phones, 2nd dont use boxes too flash it, use lgup so you can get warning of laf downgrade. 3rd search medusa or z3x jtag if they support jtag, or if you smart enough too find pinoits on board for jtag.
xplict310 said:
I was trying to unlock with gc pro key with sprint unlock to work with gsm carriers and it didnt work for me. So i tried a different formula which i flashed a firmware "ZV3" on Z3X Box and i was running on ZV5. Now the phone doesnt turn on and when connected to computer the usb driver says "Qualcomm Usb USB QDLoader 9008. Any solutions will be highly appreciated and would save me on having to buy a customer a new phone.
Click to expand...
Click to collapse
i also bricked my ls775 any one have system dump can write in sdcard may be get download mode thanks
ls775 rom dump.
gdeepp said:
i also bricked my ls775 any one have system dump can write in sdcard may be get download mode thanks
Click to expand...
Click to collapse
dear sr. i have zv5 and zv7 rom dumps of this phone, thing is that partitions are not the same in both versions, so you need to know which one you had on your device, if you know to flash this with sd card i'll provide both software versions for free, as long as you are willing to share the "flashing with sd" tutorial, if it actually works of course. by the way, both versions were dumped with z3x.
ls775 rom dump
hcom said:
dear sr. i have zv5 and zv7 rom dumps of this phone, thing is that partitions are not the same in both versions, so you need to know which one you had on your device, if you know to flash this with sd card i'll provide both software versions for free, as long as you are willing to share the "flashing with sd" tutorial, if it actually works of course. by the way, both versions were dumped with z3x.
Click to expand...
Click to collapse
bro i was bricked on ZV5 so u only upload it on google drive or mega.....also if u have any knowledge about Sd card flash also share it thanks
ls775 qdloader 9008
Well guys, i have one piece in the same condition, I have z3x but there is no support for this model, no firmwares no jtag files or even pinout, if any of you find the way to flash the emmc back in to the phone please let me know. i can offer you the extracted files for version zv8 and zva, if someone needs them to test or whatever i am willing to share.
have a nice day
lo solucione amigos
Hey guys,
So thanks to this thread : https://forum.xda-developers.com/pixel-2-xl/how-to/guide-qxdm-port-activation-pixel-2-xl-t3884967
I got my com ports open (see attached photo)
I cant however get past the part about pdc , as pdc gives me "QMI connection not ready, please use USB driver version 1.00.32 or later and fix the connection before using PDC tool."
I'm not sure how to go about fixing this but if we can, then there is the possibility that we could enable voLTE/voWIFI on the pixel 3 with carriers who don't support it(such as bouygues, who supports voLTE but not anything else)
I'm wondering if it is the qpst version I am using or something else?
I am on windows 7 and also had to disable driver signature enforcement.
Hello!
Did you achieve progress in this issue after the publication of the message?
Any success?? I have this damn same issue on my Redmi 4x...
Has anyone figured out the correct drivers yet?
Ingenium13 said:
Has anyone figured out the correct drivers yet?
Click to expand...
Click to collapse
Check this method! Hope this helps.
crok.bic said:
Check this method! Hope this helps.
Click to expand...
Click to collapse
He already mentioned in his last line that he is using windows 7 and also disabled driver signature enforcement.
can you tell me steps for enable QPST on pixel 3
Xdevillived666 said:
Hey guys,
So thanks to this thread : https://forum.xda-developers.com/pixel-2-xl/how-to/guide-qxdm-port-activation-pixel-2-xl-t3884967
I got my com ports open (see attached photo)
I cant however get past the part about pdc , as pdc gives me "QMI connection not ready, please use USB driver version 1.00.32 or later and fix the connection before using PDC tool."
I'm not sure how to go about fixing this but if we can, then there is the possibility that we could enable voLTE/voWIFI on the pixel 3 with carriers who don't support it(such as bouygues, who supports voLTE but not anything else)
I'm wondering if it is the qpst version I am using or something else?
I am on windows 7 and also had to disable driver signature enforcement.
Click to expand...
Click to collapse
can you tell me steps for enable QPST on pixel i am unable to open port on my pixel
Gautamgzb2 said:
can you tell me steps for enable QPST on pixel i am unable to open port on my pixel
Click to expand...
Click to collapse
Hey. I honestly dont remember now. Its been a long time and it was a lot of trial and error by reading that thread I linked. In the end it was useless because A-google no longer provides images for debugging purposes and B-PDC tool doesnt recognize pixel 3 even after opening the ports. Sorry man.
i hve enabled diag port fully edited values in qxdm took ota updates but upon re locking bootloader pixel 3 resets every change i made what the hell how can factory reset revert nvram changes.
"QPST" stands for "Qualcomm Product Support Tool". It's a proprietary tool used to directly write a binary image to the NAND devices on the device. Neither QPST nor the binary images are freely available, and are generally only used during the factory process to flash the initial firmware to the device.
V0latyle said:
"QPST" stands for "Qualcomm Product Support Tool". It's a proprietary tool used to directly write a binary image to the NAND devices on the device. Neither QPST nor the binary images are freely available, and are generally only used during the factory process to flash the initial firmware to the device.
Click to expand...
Click to collapse
Hmmm, no, not true. Qpst / qfil is freely available, We've used it many times with various LG devices especially.
The binary images are freely available for many devices, here's a list of the binary images free to download for the pixel 3 (from google):
In addition, for LG devices, anyone can freely download the kdz image, which is the entire rom, and use the kdz extraction tool to retrieve any individual partition image.
Not all carriers, like at&t / sprint, don't make their kdz available, thus no access to those images, but most do.
AsItLies said:
Hmmm, no, not true. Qpst / qfil is freely available, We've used it many times with various LG devices especially.
The binary images are freely available for many devices, here's a list of the binary images free to download for the pixel 3 (from google):
In addition, for LG devices, anyone can freely download the kdz image, which is the entire rom, and use the kdz extraction tool to retrieve any individual partition image.
Not all carriers, like at&t / sprint, don't make their kdz available, thus no access to those images, but most do.
Click to expand...
Click to collapse
So QPST can be used to flash bootloader, at which point someone should be able to use adb to flash the factory images? Wouldn't someone need to know the starting/ending addresses when writing to block devices?
Is there a reputable source from which to download QPST?
V0latyle said:
So QPST can be used to flash bootloader, at which point someone should be able to use adb to flash the factory images? Wouldn't someone need to know the starting/ending addresses when writing to block devices?
Is there a reputable source from which to download QPST?
Click to expand...
Click to collapse
QPST / qfil links can be found in many places, I've found them in LG v35, v40, v50, G8 forums in guides section, usual title names include 'unlock bootloader' as qfil is used to flash the 'engineering abl' to gain fastboot.
addresses of the partitions are in the partition table of ea device. Depending on how you flash a partition you may need to know it specifically, but almost always you don't. The RawprogramX.xml has them in it if needed though.
There is one caveat, for qfil to work (or any EDL access to happen), with any device, one has to have the 'programmer firehose', which is a signed specific file, for that specific device type. Many mfgs make that file available, Google does not.
AsItLies said:
QPST / qfil links can be found in many places, I've found them in LG v35, v40, v50, G8 forums in guides section, usual title names include 'unlock bootloader' as qfil is used to flash the 'engineering abl' to gain fastboot.
addresses of the partitions are in the partition table of ea device. Depending on how you flash a partition you may need to know it specifically, but almost always you don't. The RawprogramX.xml has them in it if needed though.
There is one caveat, for qfil to work (or any EDL access to happen), with any device, one has to have the 'programmer firehose', which is a signed specific file, for that specific device type. Many mfgs make that file available, Google does not.
Click to expand...
Click to collapse
This was going to be my next question. We aren't talking about LG devices here; we're talking specifically about the Pixel 3. So if the firehose files aren't available, exactly how is QPST any good to anyone?
V0latyle said:
This was going to be my next question. We aren't talking about LG devices here; we're talking specifically about the Pixel 3. So if the firehose files aren't available, exactly how is QPST any good to anyone?
Click to expand...
Click to collapse
I know what we're talkin about here, and I know it's not LG devices. And I never said qpst was any good to anybody here, I just said that it is available, and you said it wasn't, and I said the stock images are available, and you said they weren't.
AsItLies said:
I know what we're talkin about here, and I know it's not LG devices. And I never said qpst was any good to anybody here, I just said that it is available, and you said it wasn't, and I said the stock images are available, and you said they weren't.
Click to expand...
Click to collapse
I think you misunderstand me. As I asked before, please post a legitimate and trustworthy source of QPST. According to Qualcomm, it's only available for specific commercial use.
Secondly, I was specific by what I meant by "binary images" - files to be flashed directly to the NAND devices by means of JTAG or other hardware level protocols. This would include the firehose images, although I admit I'm not sure if those are binary.
Either way, I reiterate that we are talking about the Pixel 3 here. If you know of a trustworthy source for QPST, that's a start. However, the fact remains that the files needed are not available, so what may or may not be possible with LG devices is not relevant in this thread.
V0latyle said:
I think you misunderstand me. As I asked before, please post a legitimate and trustworthy source of QPST. According to Qualcomm, it's only available for specific commercial use.
Secondly, I was specific by what I meant by "binary images" - files to be flashed directly to the NAND devices by means of JTAG or other hardware level protocols. This would include the firehose images, although I admit I'm not sure if those are binary.
Either way, I reiterate that we are talking about the Pixel 3 here. If you know of a trustworthy source for QPST, that's a start. However, the fact remains that the files needed are not available, so what may or may not be possible with LG devices is not relevant in this thread.
Click to expand...
Click to collapse
I think you misunderstood me. You indicated that QPST / qfil is not availabel, it is, I told you where to find it, put in the effort.
And what you mean by 'binary images' is obviously open to interpretation, how in the world would I (or anyone) know you mean anything other than what is available (from google), which are the binary images one would flash with qfil for that device. So again, you're wrong as they are available.
And I'll repeat again, I know we're talking about the p3 and not LG devices. You're using that as a deflection, to try to avoid that your post was obviously wrong in it's information. I bring up LG devices only because they have lots of documentation here on XDA re these utilities, while the p3 does not.
"what may or may not be possible with LG"... yer again wrong. Ea and every qualcomm device can be put in EDL mode, that's what QPST is used for, it's relevant to all devices that have a qualcomm chip.
AsItLies said:
I think you misunderstood me. You indicated that QPST / qfil is not availabel, it is, I told you where to find it, put in the effort.
Click to expand...
Click to collapse
I asked you to provide a specific source. I don't know which forums you're talking about on what site. They could be here on XDA, or Reddit, or any LG forum out there. Your response is akin to "just Google it". The only reputable source I know of is Qualcomm themselves, who, as I stated, are pretty picky about who gets access to the software. Sure, a Google search will turn up a handful of third party sites that claim to have it, but are they trustworthy?
AsItLies said:
And what you mean by 'binary images' is obviously open to interpretation
Click to expand...
Click to collapse
Not really. Binary images = files in purely binary format. Not Java, not hex - ones and zeroes, the file you would use to directly flash a memory device. I was pretty specific about that.
AsItLies said:
how in the world would I (or anyone) know you mean anything other than what is available (from google), which are the binary images one would flash with qfil for that device. So again, you're wrong as they are available.
Click to expand...
Click to collapse
Two posts ago you stated:
AsItLies said:
for qfil to work (or any EDL access to happen), with any device, one has to have the 'programmer firehose', which is a signed specific file, for that specific device type. Many mfgs make that file available, Google does not.
Click to expand...
Click to collapse
So, since no "firehouse" files are available from Google, could QPST be used to flash the partition images in the factory zips?
AsItLies said:
And I'll repeat again, I know we're talking about the p3 and not LG devices. You're using that as a deflection, to try to avoid that your post was obviously wrong in it's information. I bring up LG devices only because they have lots of documentation here on XDA re these utilities, while the p3 does not.
Click to expand...
Click to collapse
No, I'm pointing out that information on LG devices is not relevant. There might be documentation regarding the use of QPST but if the necessary files are not available, that's not much use.
AsItLies said:
"what may or may not be possible with LG"... yer again wrong. Ea and every qualcomm device can be put in EDL mode, that's what QPST is used for, it's relevant to all devices that have a qualcomm chip.
Click to expand...
Click to collapse
I'm specifically referring to the possibility of hardware level device recovery which may be possible on LG devices due to the availability of the required files, but is not currently possible on the Pixel series because we do NOT have the required files.
I'm not going to continue this argument as we are rather OT at this point. This isn't conducive to finding a solution.
XDA thrives on the willingness of users to help out everyone else - the ability and willingness to solve problems. You said there is a solution to this problem; I am asking you provide it. It doesn't matter who is right or wrong in the end; it only matters that we find a solution.
Hi, I have a Huawei Mate 10 pro BLA-L29 C432 with unlocked bootloader frp unlocked that is hard bricked.
Reason why it was hard bricked was using HWota and flashing the wrong files
The device shows up in device manager as USB COM 1.0 (COM4) along with COMMUNICATIONS PORT (COM 1).
I have purchased the DC Phoneix + HCU timed license for 3 days ending on 3/4/2019 at 9 AM.
I have downloaded the "BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT.dgtks" board firmware directly from DC Phoenix
I have also downloaded the "BLA-L29C_8.0.0.115(C432)_Firmware_Lithuania_Latvia_Norway_Romania_Hungary_Greece_Austria_Czech_Republic_Bulgaria_Poland_Slovenia_Croatia_Serbia_Nonspecific.app" appfile directly from DC Phoenix
I begin by selecting the "BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT" file in the update file selection. Then i select the "BLA-L29C_8.0.0.115(C432)_Firmware_Lithuania_Latvia_Norway_Romania_Hungary_Greece_Austria_Czech_Republic_Bulgaria_Poland_Slovenia_Croatia_Serbia_Nonspecific.app" file in the update app file selection.
I click update and am provided with the following error message to the left of the screen
File to update: BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT.dgtks
Device detected:
COM4: HUAWEI USB COM 1.0 (COM4)
Writing bootloader...
Writing BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT_3.dtwork...
Error writing Bootloader
3/1/2019 1:09:05 PM Writing device finished - INCOMPLETE
I then proceeded to try the "use bootloader" option under the udpate oeminfo tab and chosen the Kiring970_T2_A8.0_V3
and i have successfully gotten my device to be recognized as follows
Looking for a device in fastboot mode
Device found: AQH7N17B29009368
SN:AQ********************* <- i have censored the following information intentionally
IMEI:866******************* <- i have censored the following information intentionally
IMEI1:86******************* <- i have censored the following information intentionally
MEID:A******************** <- i have censored the following information intentionally
Build number: :BLA-L29 8.0.0.158(C432)
Model: BLA-L29
Battery state: 0
When writing the board file, I get the following
Erasing nvme partition
ERASE partition nvme : FAIL failed to erase partition
Device with unsupported security patch
3/2/2019 11:47:18 AM Writing device finished OK
when writing the update.app file directly from dc-phoenix i get the following error
Extracting partition XLOADER...
Writing XLOADER partition
XLOADER partition UPDATE :FAIL download elf_xloader image verification error
Device with unsupported security patch
3/2/2019 12:02:09 PM Writing device finished - INCOMPLETE
i then though, okay let me try another more rescent .app file, so i downloaded the 8.0.0.158 BLA-L29 c432 "update.zip" file from the internet. I extracted the "UPDATE.APP" file and then selected it in DC-Phoneix and now i get the following message
Attention, this is OTA type file and can't be written via software. Writing it via fastboot may damage the phone. Please use files from our support area.
so I select no, because of this error. I chose to download more "update.zip" files from the internet, and they all give me this attention message.
i then proceeded to use huawei extractor tool to extract kernel,ramdisk,recovery_ramdisk, recovery_vbmeta, and recovery_vendor. I flashed them through fastboot successfully, but no life from the device. As a matter of fact, when i disconnect the device, I have to start from scratch again.
I am really running out of ideas here. =(
Chito307 said:
Hi, I have a Huawei Mate 10 pro BLA-L29 C432 with unlocked bootloader frp unlocked that is hard bricked.
Reason why it was hard bricked was using HWota and flashing the wrong files
The device shows up in device manager as USB COM 1.0 (COM4) along with COMMUNICATIONS PORT (COM 1).
I have purchased the DC Phoneix + HCU timed license for 3 days ending on 3/4/2019 at 9 AM.
I have downloaded the "BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT.dgtks" board firmware directly from DC Phoenix
I have also downloaded the "BLA-L29C_8.0.0.115(C432)_Firmware_Lithuania_Latvia_Norway_Romania_Hungary_Greece_Austria_Czech_Republic_Bulgaria_Poland_Slovenia_Croatia_Serbia_Nonspecific.app" appfile directly from DC Phoenix
I begin by selecting the "BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT" file in the update file selection. Then i select the "BLA-L29C_8.0.0.115(C432)_Firmware_Lithuania_Latvia_Norway_Romania_Hungary_Greece_Austria_Czech_Republic_Bulgaria_Poland_Slovenia_Croatia_Serbia_Nonspecific.app" file in the update app file selection.
I click update and am provided with the following error message to the left of the screen
File to update: BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT.dgtks
Device detected:
COM4: HUAWEI USB COM 1.0 (COM4)
Writing bootloader...
Writing BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT_3.dtwork...
Error writing Bootloader
3/1/2019 1:09:05 PM Writing device finished - INCOMPLETE
I then proceeded to try the "use bootloader" option under the udpate oeminfo tab and chosen the Kiring970_T2_A8.0_V3
and i have successfully gotten my device to be recognized as follows
Looking for a device in fastboot mode
Device found: AQH7N17B29009368
SN:AQ********************* <- i have censored the following information intentionally
IMEI:866******************* <- i have censored the following information intentionally
IMEI1:86******************* <- i have censored the following information intentionally
MEID:A******************** <- i have censored the following information intentionally
Build number: :BLA-L29 8.0.0.158(C432)
Model: BLA-L29
Battery state: 0
When writing the board file, I get the following
Erasing nvme partition
ERASE partition nvme : FAIL failed to erase partition
Device with unsupported security patch
3/2/2019 11:47:18 AM Writing device finished OK
when writing the update.app file directly from dc-phoenix i get the following error
Extracting partition XLOADER...
Writing XLOADER partition
XLOADER partition UPDATE :FAIL download elf_xloader image verification error
Device with unsupported security patch
3/2/2019 12:02:09 PM Writing device finished - INCOMPLETE
i then though, okay let me try another more rescent .app file, so i downloaded the 8.0.0.158 BLA-L29 c432 "update.zip" file from the internet. I extracted the "UPDATE.APP" file and then selected it in DC-Phoneix and now i get the following message
Attention, this is OTA type file and can't be written via software. Writing it via fastboot may damage the phone. Please use files from our support area.
so I select no, because of this error. I chose to download more "update.zip" files from the internet, and they all give me this attention message.
i then proceeded to use huawei extractor tool to extract kernel,ramdisk,recovery_ramdisk, recovery_vbmeta, and recovery_vendor. I flashed them through fastboot successfully, but no life from the device. As a matter of fact, when i disconnect the device, I have to start from scratch again.
I am really running out of ideas here. =(
Click to expand...
Click to collapse
sorry bro i never ran into situation like this
only pray for you
Anyone? =(
Chito307 said:
Anyone? =(
Click to expand...
Click to collapse
you already done what may be possible to recover
huawei can do it if it is in warranty
It's seems that the error is right there , the security patch isn't supported so it won't finish writing the files, it is stated in DC locker that some devices like mate 10 pro and newer devices are not supported the same reason why there are no new unlocked codes for bootloader on DC unlock and no new unlocked codes for sim also, have your tried flashing those files yourself through fastboot method ? With out the hcu from DC
?
I had same problème
Now phone is OK but IMEI 000000000000
This worked for me, it requires IDT and unencrypted board firmware (these are usually paid). dtgks might work if you only flash board firmware, but you have to be careful so it doesn't wipe oeminfo (if you still want to unlock after. You can still get unlock code through HCU on board firmware so it doesn't really matter).
Edit xml that comes with unencrypted board so it doesn't erase oeminfo.
Flash bootloader files with DC, phone is put in fastboot mode.
Open up IDT.
Select xml in both settings of IDT and in settings of USBMAP. In USBMAP, select com port in the list and click on Skip.
Now start flashing using IDT.
When flashing is done phone will boot to board firmware.
When on board firmware, follow this guide to get your imeis and that stuff back:
1)Flash board (already done)
2)Flash oeminfo from fastboot (own backup if available, if you edited xml you will still have your own oeminfo flashed)
3) Dump modemnvm_system, modemnvm_factory and modemnvm_backup partitions using dd and adb shell ('dd if=/dev/block/bootdevice/by-name/modemnvm_system of=/sdcard/modemnvm_system.img' and so on), board firmware has global root so you don't need to flash Magisk or anything like that (which is impossible anyway, board fw will only accept board or stock images)
4)Flash dumped modemnvm_system, modemnvm_factory and modemnvm_backup using fastboot
5)Modify and brand with HCU (check all checkboxes except the last 2, fill in any missing info)
6)Unlock Sim network with HCU
7)If you previously used HCU to get unlock code you need to generate it again (HCU patches oeminfo so their unlock code works). Also if you forgot to edit xml you'd have to generate a new code, your old code will not work if oeminfo was wiped.
8)Use dload with Service Firmware from androidhost.ru, regular update.zip does not work in dload mode.
And make sure the firmware you dload is newer than GPU Turbo firmware. (XLOADER needs to be 02, else you brick again)
Please note that you only have one shot at this... If you, for example, flash dload but forget to generate unlock code and don't have your own oeminfo flashed you will not be able to repair device without opening it up to get testpoint.
ante0 said:
it requires IDT
Click to expand...
Click to collapse
What is IDT ?
badmania98 said:
What is IDT ?
Click to expand...
Click to collapse
Image Download Tool, some leaked tool (like Odin for Samsung).
It's available on androidhost.ru iirc
I need dload with Service Firmware please
I flashed with many firmware no seccess
ante0 said:
This worked for me, it requires IDT and unencrypted board firmware (these are usually paid). dtgks might work if you only flash board firmware, but you have to be careful so it doesn't wipe oeminfo (if you still want to unlock after. You can still get unlock code through HCU on board firmware so it doesn't really matter).
Edit xml that comes with unencrypted board so it doesn't erase oeminfo.
Flash bootloader files with DC, phone is put in fastboot mode.
Open up IDT.
Select xml in both settings of IDT and in settings of USBMAP. In USBMAP, select com port in the list and click on Skip.
Now start flashing using IDT.
When flashing is done phone will boot to board firmware.
When on board firmware, follow this guide to get your imeis and that stuff back:
1)Flash board (already done)
2)Flash oeminfo from fastboot (own backup if available, if you edited xml you will still have your own oeminfo flashed)
3) Dump modemnvm_system, modemnvm_factory and modemnvm_backup partitions using dd and adb shell ('dd if=/dev/block/bootdevice/by-name/modemnvm_system of=/sdcard/modemnvm_system.img' and so on), board firmware has global root so you don't need to flash Magisk or anything like that (which is impossible anyway, board fw will only accept board or stock images)
4)Flash dumped modemnvm_system, modemnvm_factory and modemnvm_backup using fastboot
5)Modify and brand with HCU (check all checkboxes except the last 2, fill in any missing info)
6)Unlock Sim network with HCU
7)If you previously used HCU to get unlock code you need to generate it again (HCU patches oeminfo so their unlock code works). Also if you forgot to edit xml you'd have to generate a new code, your old code will not work if oeminfo was wiped.
8)Use dload with Service Firmware from androidhost.ru, regular update.zip does not work in dload mode.
And make sure the firmware you dload is newer than GPU Turbo firmware. (XLOADER needs to be 02, else you brick again)
Please note that you only have one shot at this... If you, for example, flash dload but forget to generate unlock code and don't have your own oeminfo flashed you will not be able to repair device without opening it up to get testpoint.
Click to expand...
Click to collapse
Hello
I do every thing on the tuto but i have 1 problem
I have no network it still no service
Hello guys,
i tried to flash an EU ROM on my Chinese Xiaomi Pad 5 Pro. Unfortunately, it failed
Symptoms:
Pad has full black screen.
It can not start into fast boot mode
cant be found by Xiaomi flash tool.
When i connect it to my computer and hold Power + Volume up or down, the computer beeps after a while
What happened:
i downloaded EU fastboot rom and unpacked with 7zip
unlocked bootloader of Xiaomi Pad
connected to xiaomi flash tool
copied unpacked rom files on C:\EU
start flash_all
after having an error "crclist or sparsecrclist" (Link), i added REM into the flash file, as mentioned on youtube and started again
at the end of the flash process it showed a problem with the "REM" line, that i added and the flash failed
I cant flash again because i cant get into the fastboot mode... Do you have any clue what i can do now?
Thanks a lot!
nappi
nappi90 said:
Hello guys,
i tried to flash an EU ROM on my Chinese Xiaomi Pad 5 Pro. Unfortunately, it failed
Symptoms:
Pad has full black screen.
It can not start into fast boot mode
cant be found by Xiaomi flash tool.
When i connect it to my computer and hold Power + Volume up or down, the computer beeps after a while
What happened:
i downloaded EU fastboot rom and unpacked with 7zip
unlocked bootloader of Xiaomi Pad
connected to xiaomi flash tool
copied unpacked rom files on C:\EU
start flash_all
after having an error "crclist or sparsecrclist" (Link), i added REM into the flash file, as mentioned on youtube and started again
at the end of the flash process it showed a problem with the "REM" line, that i added and the flash failed
I cant flash again because i cant get into the fastboot mode... Do you have any clue what i can do now?
Thanks a lot!
nappi
Click to expand...
Click to collapse
It seems to me that there is no EEA version for your device.
What code name, elish, dagu, enuma?
nappi90 said:
Hello guys,
i tried to flash an EU ROM on my Chinese Xiaomi Pad 5 Pro. Unfortunately, it failed
Symptoms:
Pad has full black screen.
It can not start into fast boot mode
cant be found by Xiaomi flash tool.
When i connect it to my computer and hold Power + Volume up or down, the computer beeps after a while
What happened:
i downloaded EU fastboot rom and unpacked with 7zip
unlocked bootloader of Xiaomi Pad
connected to xiaomi flash tool
copied unpacked rom files on C:\EU
start flash_all
after having an error "crclist or sparsecrclist" (Link), i added REM into the flash file, as mentioned on youtube and started again
at the end of the flash process it showed a problem with the "REM" line, that i added and the flash failed
I cant flash again because i cant get into the fastboot mode... Do you have any clue what i can do now?
Thanks a lot!
nappi
Click to expand...
Click to collapse
I guessed you downloaded and flashed the wrong firmwares/ROM to your device. This caused serious brick (the hardest brick) to your device. All the wrong firmwares have been flashed to every single partitions of your device. That's why your device can neither boot up nor enter fastboot mode. I got my Lenovo Yoga Tab 13 and some other Qualcomm devices into this serious brick. I got my Lenovo Yoga Tab 13 this brick by relocking bootloader. The only method that can fix your device error is to use QPST QFIL.
Requirements:
1.Windows 10 x64 preferred or above with WSL (Windows Subsystem for Linux) enabled. Because QFIL in QPST requires Sahara server (Linux) to run on your Windows.
2.Download and install HS-USB QDLoader 9008 driver for your Windows version.
3.Download and install QPST to your PC.
4.Download and unzip the correct fastboot ROM for your device to your PC. There are files with .img inside the zipped file. For example, boot.img, recovery.img and many others.
I am not sure if Mi Pad 5 Pro requires Provision process to flash via QPST or not? Some Qualcomm devices, for example Chuwi Hi Pad Pro, require Provision before getting permission to flash via Download mode using QPST.
Watch this tutorial to see the how-to-use-QFIL video. This video is quite old. There may be some chages in QFIL. You can google the newer tutorial about QFIL.
While your device does not show nothing but the black screen, follow the steps below:
1.Assumingly you have completed all the requirements above, open QFIL.
2.Connect USB from your PC to your device.
3.Load XML by matching all the files of rawprogram#.xml with patch#.xml. For example, If there are 6 files of rawprogram0.xml to rawprogram5.xml. You have to add rawprogram0.xml matching patch0.xml until rawprogram5.xml matching with patch5.xml to the Download list.
4.Press Download button in QFIL.
5.Hold volume Down (Some Qualcomm devices are volume UP and some are both volume at the same time) and press power button many times until the download process of QFIL starting up. This means your device has entered Download Mode.
6.Wait until the download process completed. Hopefully there is no error or no Provision process required.
7.Disconnect the USB from your device.
8.Your device should boot up showing Mi logo. If not, hold power button to try booting up your device.
Hope you can fix this. Or your device will turn into one of the most expensive paper weight.
Before step 3, i have to choose one programmer out of these:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In step 3 I matched one by one rawprogram and patch file, but in the box it only shows the last pair. Do I have to click every time on download e.g. I choose rawporgram1.xml and patch1.xml and then press download or do I match all of them first like below, then there is only the last one visible.
In the end I get some failed to open com port handle messages. Do you know where this comes from?
NOSS8 said:
It seems to me that there is no EEA version for your device.
What code name, elish, dagu, enuma?
Click to expand...
Click to collapse
unfortunately, it seems you are right... this is the reason.....
nappi90 said:
Before step 3, i have to choose one programmer out of these:
View attachment 5770983
In step 3 I matched one by one rawprogram and patch file, but in the box it only shows the last pair. Do I have to click every time on download e.g. I choose rawporgram1.xml and patch1.xml and then press download or do I match all of them first like below, then there is only the last one visible.View attachment 5770981
In the end I get some failed to open com port handle messages. Do you know where this comes from?
Click to expand...
Click to collapse
1.Choose prog_ufs_firehose_sm8250_ddr_5.elf
2.Have you enabled WSL on your Windows 10 or above? Read requirement #1 of my post.
siamese007 said:
1.Choose prog_ufs_firehose_sm8250_ddr_5.elf
2.Have you enabled WSL on your Windows 10 or above? Read requirement #1 of my post.
Click to expand...
Click to collapse
to 2: yes, i did.
About the rawprogram1 - rawprogram5: Do you know, if i need to download after matching each pair e.g. rawprogram1 = patch 1; click download; rawprogram2 = patch 2; click download etc.
nappi90 said:
to 2: yes, i did.
About the rawprogram1 - rawprogram5: Do you know, if i need to download after matching each pair e.g. rawprogram1 = patch 1; click download; rawprogram2 = patch 2; click download etc.
Click to expand...
Click to collapse
Add all the rawprogram0.xml to rawprogram5.xml matching with patch0.xml to patch5.xml files to the Download list at once and press download button.
My experiment:
I have put my Mi Pad 5 Pro 5G into Download Mode (EDL) and run QFIL > Partition Manager. QFIL cannot access the partitions of my device. This probably means my device may require Provision to do this. So it may mean yours requires Provision to flash the firmware with QFIL also.
Now it's come to my most fear that you will need the Provision file which is not included in the fastboot firmware/ROM. You have to ask this file from Xiaomi Customer Services. And your device's warranty has been voided since you have unlocked bootloader.
Try 1 of the following methods.
1.Ask someone who has the same device as yours to ask Xiaomi Customer Services for Provision file. Tell them you need the file to back up partition of your device. The Customer Services may ask the serial number and other info about that person's device for verify the customer warranty.
2.Ask Xiaomi Customer Services for the Provision file for your deivce by yourself. Tell them that your device got brick and can be accessed only by Download Mode (EDL) via QPST or QFIL.
3.Google to find the Provision file for your device on the internet. It's very difficult. I still cannot find the Provision file for my old Redmi K30 5G released in Jan 2020, around 3 years ago.
4.Google the method to work around your Sahara error. And hope your device does not need Provision to flash the firmware via Download Mode (EDL).
5.No offense. If you have extra money, buy the new one and ask Xiaomi Customer Services for the Provision file. Or buy Lenovo devices. They are not required Provision to flash firmware via Download Mode (EDL).
If you have the Provision file, ask me again of how to do Provision. Or google the way to do Provision on the internet.
Wish you best luck.
siamese007 said:
Add all the rawprogram0.xml to rawprogram5.xml matching with patch0.xml to patch5.xml files to the Download list at once and press download button.
My experiment:
I have put my Mi Pad 5 Pro 5G into Download Mode (EDL) and run QFIL > Partition Manager. QFIL cannot access the partitions of my device. This probably means my device may require Provision to do this. So it may mean yours requires Provision to flash the firmware with QFIL also.
Now it's come to my most fear that you will need the Provision file which is not included in the fastboot firmware/ROM. You have to ask this file from Xiaomi Customer Services. And your device's warranty has been voided since you have unlocked bootloader.
Try 1 of the following methods.
1.Ask someone who has the same device as yours to ask Xiaomi Customer Services for Provision file. Tell them you need the file to back up partition of your device. The Customer Services may ask the serial number and other info about that person's device for verify the customer warranty.
2.Ask Xiaomi Customer Services for the Provision file for your deivce by yourself. Tell them that your device got brick and can be accessed only by Download Mode (EDL) via QPST or QFIL.
3.Google to find the Provision file for your device on the internet. It's very difficult. I still cannot find the Provision file for my old Redmi K30 5G released in Jan 2020, around 3 years ago.
4.Google the method to work around your Sahara error. And hope your device does not need Provision to flash the firmware via Download Mode (EDL).
5.No offense. If you have extra money, buy the new one and ask Xiaomi Customer Services for the Provision file. Or buy Lenovo devices. They are not required Provision to flash firmware via Download Mode (EDL).
If you have the Provision file, ask me again of how to do Provision. Or google the way to do Provision on the internet.
Wish you best luck.
Click to expand...
Click to collapse
Thanks a lot for your big effort to help me. Seems like i need this EDL mode. Currently, i am in Beijing in lockdown and its not the best time to go around and find a mi customer service. Meanwhile, i look for a solution for the sahara problem (see point 4).
@siamese007 hi,
I tried your method to unbrick a Mi pad 5, but unfortunately an authorization is needed...
I am trying to ask Xiaomi help. I don't have any answer for the moment...
If I try to ask them the Provision file, what I should do with ?
Could you explain me your method ? Do you think it’s a file they’re capable of giving away?
Thank you in advance,
Nicolas
Heavymistick said:
@siamese007 hi,
I tried your method to unbrick a Mi pad 5, but unfortunately an authorization is needed...
I am trying to ask Xiaomi help. I don't have any answer for the moment...
If I try to ask them the Provision file, what I should do with ?
Could you explain me your method ? Do you think it’s a file they’re capable of giving away?
Thank you in advance,
Nicolas
Click to expand...
Click to collapse
Hello,
What happened with your device? Is your device Mi pad 5 nabu? Why can you not flash your device with Mi Flash Tool?
If you want to flash your device with QFIL in EDL mode, all Xiaomi devices require provision files to do it. Provision file is not supposed to be secret of company use only. Some devices have done provision for users at their factories. Otherwise users will be required to do provision by themselves. IMO provision files should be added to the firmware zip file for EDL mode.
For normal case, users can use Mi Flash tool to flash firmware. So Xiaomi might think provision files are not needed.
siamese007 said:
Hello,
What happened with your device? Is your device Mi pad 5 nabu? Why can you not flash your device with Mi Flash Tool?
If you want to flash your device with QFIL in EDL mode, all Xiaomi devices require provision files to do it. Provision file is not supposed to be secret of company use only. Some devices have done provision for users at their factories. Otherwise users will be required to do provision by themselves. IMO provision files should be added to the firmware zip file for EDL mode.
For normal case, users can use Mi Flash tool to flash firmware. So Xiaomi might think provision files are not needed.
Click to expand...
Click to collapse
Thanks a lot for your answer,
I brick my tablet by corrupting UFS files after a fake manip by following a tutorial. It is indeed a tablet pad 5 with as code name "nabu".
Only EDL works, i can't boot fastboot or recovery (black screen). Mi Flash tool needs a Xiaomi authorization to flash with EDL mode. I don't know if Xiaomi can give me a temporary permission for that ?
I tried to flash the ROM with QFIL in EDL but i had an error "Only nop and sig tag can be recevied before authentication.".
So I guess I have to get the file you were talking about to go further?
Heavymistick said:
Thanks a lot for your answer,
I brick my tablet by corrupting UFS files after a fake manip by following a tutorial. It is indeed a tablet pad 5 with as code name "nabu".
Only EDL works, i can't boot fastboot or recovery (black screen). Mi Flash tool needs a Xiaomi authorization to flash with EDL mode. I don't know if Xiaomi can give me a temporary permission for that ?
I tried to flash the ROM with QFIL in EDL but i had an error "Only nop and sig tag can be recevied before authentication.".
So I guess I have to get the file you were talking about to go further?
Click to expand...
Click to collapse
I tested with my device to access its partition tables but could not. And got error saying something about "authentication". So I guess yes you need to do provision before being able to flash the ROM in EDL mode with QFIL.
From my experience, the provision file is xml with some code to access the system on the chip that allows QFIL to flash firmware in EDL mode. Not sure if this provision for the SoC can be used widely across any devices with the same chipsets. You may look for the provision file from other devices with the same chipset as your device's. I will explain how to do provision later.