Database Develop

Semi working PRA-LX1C432

Hi !
I bought in January the nice P8 Lite 2017 and received a PRA-LX1C432 (dual sim europe no carrier).
It was with Android 7.0 and EMUI 5.0 and i wanted to root it.
I did it well, and was with the firmware PRA-LXA1C432B182 in stock and rooted with the tuto from this thread
https://forum.xda-developers.com/p8...ck-rom-huawei-prague-pra-xxxc432b182-t3727816
and uninstalled TWRP to put back stock recovery.
Later, I wanted to unroot my phone, and that's where things went wrong. I tried to do it with the superSU option and after a hard reset it was working and not rooted, but i'd still have the message "this phone can't be trust" so i tried to relock the bootloader and it did hard reset the phone again and now, i'm stuck with a phone that can send sms or go through the internet with LTE, but can't access fm, camera, google music, nfc is going on and off, calls don't work, etc... In dev options, Allow OEM unlock is greyed and I can't change anything. Phone is recognized by computer and I can acces memory of the phone.
I can hard reset it won't change, i ca also accessFastboot, or recovery or eRecovery, but in Fastboot mode it says "PHONE Unlock FRP Lock" and from my computer i can't do anything : if i try to flash twrp with fastboot command, i have the message "FAILED remote the command is not allowed", if i try to lock/unlock/relock bootloader it says "FAILED remote root type is risk".
Clearly, I don't know what to do. I'm used with rooting/unrooting smartphones from different brands (Samsung, LG, Sony, Huawei...), even though i'm far from being a master, and using Fastboot/ADB commands, but... I don't know.
If someone has any idea, I'm taking. I'm thinking about dload method but, of cooourse, I do NOT have a sdcard, so it's the last thing i would have tried from all i have seen on xda and elsewhere.
Thanks for reading and taking time to answer and help me, and sorry for not perfect english, i'm french but trying my best !

Run a eRecovery restore , it restore the entire smartphone to stock and also lock bootloader. Idk if this can solve your problems but i had ur same problem a days ago and i restored my phone enterely.

Fr0nK said:
Run a eRecovery restore , it restore the entire smartphone to stock and also lock bootloader. Idk if this can solve your problems but i had ur same problem a days ago and i restored my phone enterely.
Click to expand...
Click to collapse
I can't, it says that it can not get package infos from server. :/

MrCrumble34 said:
I can't, it says that it can not get package infos from server. :/
Click to expand...
Click to collapse
If you have twrp or if you can install it in someway , i can provide to you and ominfo.img to flash via twrp in ominfo partition to restore and remove package info error.

Fr0nK said:
If you have twrp or if you can install it in someway , i can provide to you and ominfo.img to flash via twrp in ominfo partition to restore and remove package info error.
Click to expand...
Click to collapse
TWRP is not installed, and I can't flash it in any way. Fastboot says "FAILED (remote : command not allowed)" if I try flashing recovery or system or anything. It also says "FAILED (remote : root type is risk) if I try to lock/unlock/relock the bootloader.

Ok, I'm actually trying something. I plugged the phone into my computer, and HiSuite told there was an update available for my phone, so I just clicked on it. It's doing right now, I will edit my post after it has finished (for good or bad).
EDIT : Ok, si it did work ! My phone is now on PRA-LX1C432B194, everything is working, not rooted. I relocked the bootloader with Fastboot, the command did work (guess I can root it again if I need now). But I think I'll leave it like that ^^'
Allow OEM unlock isn't greyed anymore, I came back to the original state of my phone but with an update not (yet) available in my country, no more "Device can't be trusted" message. Like if nothing had ever happened (expect it will be written PHONE Relocked).
This phone is really sensitive, haha^^
But as anyway I made it
Thanks anyway for trying to help !

Please Help_After OTA Update Xiaomi Mi A2 died

On Saturday appeared an OTA update to do on my mi A2 but after installed and restarting it died. It does not enter recovery mode and the screen is always on with android one bootscreen logo.
PS: I never flash the phone and i never change anyting in the system of the phone.
The only response that i have in the phone is enter in it Fastboot menu. I read some threads and untill now i cant fix my phone.
I will try to explain what i do:
I've tried using this tool https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585.
I try option 3 (Unbrick/Revert to Stock/Force update and the program tell me to unlock the bootloader.
When i tried to unlock bootloader by option 1 and then 1, 2 and 3 ( Unlock flashing critical, unlock OEM , unlock flashing ) the programs says: Failed Unlock is not allowed.
Then i try the response 9 to this thread https://forum.xda-developers.com/mi-a2/help/impossible-flashing-xiaomi-mi-a2-t3837565 to try unlocked the bootloader
But i have the same response ( Flashing Unlock is not allowed )
I read and i try but i cant unbrick my phone, someone can help?? Thanks

We are in the same boat buddy, the same thing happened to the phone of my wife.

It *sounds* like the update failed, and normally that would mean it would switch the slot back to the one that was working and boot that.
But you've tried a bunch of options from some tool, I've no idea what it did, as the tool doesn't tell you what commands it's doing.
I'd suggest to go to fastboot and see if you can tell which slot is active, then switch it to the other slot, then do fastboot reboot and cross your fingers

I have the same problem (for other reasons, but exactly the same problem). You can also try "fastboot oem edl", but it did not work for me, so I suppose you have little chance for it to work.
I have been searching and it looks like there are some "deep flash cables" that can make the phone enter edl mode to flash it using mi flash tool. Maybe these could work for us. There is apparently other way to enter edl mode, but it requires opening the phone (that I do not want to do) to short two test points.

I cant enter revorymode only fastboot mode. But when in fastbootmode my connected pc cant even find the phone. Im going to return the phone.

I have the same problem, I have this edl cable but so far no luck.
Do not realy k Ow how to use.

Are you sure it was the OTA update that bricked your phone? That Treble system isn't just there for the kicks, its there to prevent serious issues like these.

I'm stucked on fastboot, I don't want to open my phone. Could anyone help us? I already tried a lot of things, my computer doesn't recognize my mobile when is on fastboot mode. I already tried to install a lot of drivers or try to use differents adbs.

NEM-L21: Stucked with wrong version of boot.img, no more possibility of flashing

Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day

I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll

Xiao Mi A2 "Can't load Android system"

Hi Guys,
My phone suddenly stuck at this screen since may :
Android Recovery
Xiaomi/jasmine/jasmine_sprout
9/PKQ1.180904.001/V10.0.9.0.PDIMIXM
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data store on this device.
- Try again
- Factory data reset
If i press try again, sometime it will go to fastboot screen.
I can go into recovery mode here but i not sure which step i should do next.
Reboot system nowreboot to bootloader
apply update from ADB
apply update from sd CARD
wipe data/factory reset
Mount/sstem
view recovery logs
run graphics test
run locale test
power off
I'm not a very tech savvy person, i would really appreciate some help as i have data inside my phone which i need. So if possible i would like to retain the data.
I tried like EDL,fastboot,and flashing none seem to work. Of course I may be doing it wrong.
Can anyone guide me step by step I be happy to give an reward via paypal.

I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?

blazessdd said:
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
Click to expand...
Click to collapse
Thank you so much for replying.
Nope, but I can do EDL to unlock bootloader, I already disassemble the device a few times.
Just that every time I try to flash it , it give me some error. like Bluetooth error or the version error .
Which I watch thousand of video to work but it's doesn't help. Or maybe I just watched the wrong video

Ok tell me exactly what are you doing and where you have downloaded the rom.
If it's corrupted and you try to flash it you will lose the data... Was debug USB activated on developer settings?

My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:

epilifio said:
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
Click to expand...
Click to collapse
You can try to short the edl points so you can flash the ROM again

blazessdd said:
You can try to short the edl points so you can flash the ROM again
Click to expand...
Click to collapse
I already made this attempt, "adb reboot edl" reports the message "error: '(null)' not found
Xiaomi never again

Question Can't install fastboot roms

Hi everyone, I'm writing this post to ask for your help regarding an issue that is driving me to exhaustion. I also apologize in advance for any errors. It all started after trying to overclock the gpu with the konabless app, previously the app made me make a backup of the vendor_boot image in case of post modification problems, so next i edited the frequencies of the gpu, I applied the changes, rebooted and BOOM, a phone freezed at mi logo. So I rebooted in twrp to reflash the stock vendor_boot image, and for my great intelligence I flashed it on the boot image partition, and what did I get? A phone stuck in fastboot.
Oh well, a phone that turns on in fastboot is not a big problem you'll say, and I thought the same as i previously had a problem and solved it by reflashing the stock rom in fastboot, so I took my nice computer (actually it's a 12 year old pc that runs on carbon, but that does its job), I opened the mi flash tool, connected the phone, selected the fastboot rom, precisely the EEA 12.5.7.0 (like the one natively installed before the damage) and started the installation. 20 minutes later ... error: cannot load bla bla bla, ok ok, i seached various solutions on Google and tried every metods, i changed the directory of the mi flash, of the rom, I updated the version of mi flash, i installed both on C:/ drive, reinstalled the drivers, i edited the batch file to remove the anti rollback but nothing, it arrives at flashing the super image and after some minutes it fails the flashing. Before you ask, YES, the bootloader was unlocked. I also tried to flash the rom in twrp, but ... the phone no longer had the twrp. The only way to start it was via command (fastboot boot twrp.img), the onekey injection did not make it permanent, and connecting the phone to the pc it revealed the device, but not the internal memory, I tried to make a format data but nothing. I managed to make it permanent only once, manually flashing only the vendor_boot and boot images in one of the boot_ * slots, in that case incredibly the pc also detected the internal partition, I copied the flashable rom and ... the twrp said to restart the recovery for I don't remember what, but basically I couldn't install the rom via twrp. At that point I finally gave up and took the phone to an authorized xiaomi service center where they fixed it (bye bye 25€), I don't know how exactly, I would opt through edl mode I think, and now i have my working phone...but heeeeeey, they flashed me the 12.0.1 TW version, not the EEA... Ahhhhh come on. They also re-locked the bootloader, so... agaaaain i re-unlocked the bootloader, this time i downloaded the unofficial tool xiaomi flash tool v2, it installed every needed driver, i clicked on "my phone works and i want to mod it", this time i tried to flash the global rom 12.5.7.9 and when it arrives at flashing the super image IT FAILS (fast boot flash_all failed, exit code:1, output: flash super error), and like a nightmare the phone was stuck in fastboot again, fool once but never fool twice, this time I had previously made a twrp backup of everything except the data partition, I install it and the phone restarts perfectly, I also notice that despite the attempted flash of the rom in fastboot after restoring the twrp backup without the data partition, nothing has been deleted from the data partition. So benevolent gods of xda, how the heck should I change rom region? Thanks for your attention and I hope I haven't stressed you out any more than I already am.

you are probably uploading rom miflashem pro and hence this error - I had the same. Use miflash's built-in pro miflash and it should go - it worked for me

SpYneX_ said:
Hi everyone, I'm writing this post to ask for your help regarding an issue that is driving me to exhaustion. I also apologize in advance for any errors. It all started after trying to overclock the gpu with the konabless app, previously the app made me make a backup of the vendor_boot image in case of post modification problems, so next i edited the frequencies of the gpu, I applied the changes, rebooted and BOOM, a phone freezed at mi logo. So I rebooted in twrp to reflash the stock vendor_boot image, and for my great intelligence I flashed it on the boot image partition, and what did I get? A phone stuck in fastboot.
---
Click to expand...
Click to collapse
1/ OMG, take your time, espace your words, compact your questions...
2/ For old configuration a user have fix adb/drivers/detection problem with an another driver pack, and a old is btter than the lastest for some old configuration (so if your conputeur jhave 12 years, maybe...)
So try to install this drivers here
Change your USB port and verify your cable
3/ If problem occur, change computer (family/friend computer), just for flash, for be sure it's a communication/usb/detection problem
PS : Finally, why trying to overclock a soc already overclock by Snapdragon and always overheat ? It's really want finding problems ^^