Hello! I'm trying to restore my imei on my Mi 5. Im using QPST to dump the qcn file, change the hex bytes corresponding to imei then restoring it. My Mi 5 is unlocked with TWRP and is rooted. When I use QPST to restore the .qcn file I get the following error.
{
"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"
}
hxxps://imgur.com/a/KTxYx change xx to tt. sorry I can't post proper links
Any ideas on how I can fix this or restore my IMEI by other means? I will provide any other information that is needed.
EDIT1. Reinstalled QUALCOM drivers. No luck
EDIT2. Managed to solve the error that QPST was showing using an older build 378. I have tried to resotre the qcn file with its respective imei to no avail even though the restore process finishes with no errors. I have tried with the backup I did and with samples download from internet.
Thank you for your time and effort.
with twrp/mount and mount system....go into twrp go to dev/block/byname and delete modemst1 modemst2 and fsg......and then try......but first back em up before you delete em
Tech_Savvy said:
with twrp/mount and mount system....go into twrp go to dev/block/byname and delete modemst1 modemst2 and fsg......and then try......but first back em up before you delete em
Click to expand...
Click to collapse
Hello Tech_Savvy. Did that, no change. Any other idea?
I encounter the same problem, and when I flash the early rom with android 6, then I can restore full qcn file with modified IMEI.
On marshmallow miui or on lineage?
Which one did you use?
succeded with early MIUI 8 (android 6), I tried with lineage 14.1 and failed.
sentegote said:
Hello! I'm trying to restore my imei on my Mi 5. Im using QPST to dump the qcn file, change the hex bytes corresponding to imei then restoring it. My Mi 5 is unlocked with TWRP and is rooted. When I use QPST to restore the .qcn file I get the following error.
hxxps://imgur.com/a/KTxYx change xx to tt. sorry I can't post proper links
Any ideas on how I can fix this or restore my IMEI by other means? I will provide any other information that is needed.
EDIT1. Reinstalled QUALCOM drivers. No luck
EDIT2. Managed to solve the error that QPST was showing using an older build 378. I have tried to resotre the qcn file with its respective imei to no avail even though the restore process finishes with no errors. I have tried with the backup I did and with samples download from internet.
Thank you for your time and effort.
Click to expand...
Click to collapse
where di you get the older build ?
Related
anyone knows how to unbrick HONOR 9 LITE ?
the only mode i can go in is FASTBOOT MODE only.
Can't go to ERECOVERY nor RECOVERY not even VOLUP+VOLDWN+POWER working.
any idea how to recover from this?
What was you doing before the device bricked?
Also which version do you LLD-L31 / LLD-L21 / LLD-A00 need to know that info if anyone is able to help you.
Sent from my LLD-L31 using Tapatalk
Mine is LLD-AL10
LLD-AL10C675CUSTC675D2
i accidentally deleted SENSORHUB and TEEOS partition through twrp after that nothing is working k can't go in ERECOVERY nor twrp recovery it just freezes showing your device is booting. Though I've twrp backup of everything but phone isn't booting up in twrp recovery so don't know how to restore the backup.
Firstly your going to need the stock firmware.
I linked them in this post:
https://forum.xda-developers.com/showthread.php?p=77140647
Secondly your going to need the extractor tool :
https://forum.xda-developers.com/showthread.php?p=45317807
You then need to load the update.app in the extractor tool from the full update too see if the partitions you've wiped are there.
If they are there then you will be able to return back to stock hopefully this fixing the issue
Sent from my SHIELD Tablet K1 using Tapatalk
I've STOCK ROM with me and have these files SENSORHUB AND TEEOS too but the problem is i can't flash these two files from FASTBOOT.
FASTBOOT FLASH SENSORHUB SENSORHUB.IMG gives error.
Ok your using a stock rom however you wiped two partitions with twrp, i take it your rooted?
Also whats with the capslock this is classes as shouting and rude. I am trying to help you solve your issue.
So the only other way i think it can be done is to follow the HuRUpdater tool way
Download the zip from here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Now find the files required for your device, now as i am not sure about the difference between LLD-AL10C675CUSTC675D2 and LLD-AL10C675CUSTC675D1 i will take the responsibility if your phone decides to spit flames or kills your cat that's on you.
Your going to need the update_LLD-L22A_hw_in.zip update.zip and update_data_public.zip files downloaded.
Now on a SDCard make a folder say called C675CUSTC675D2 and in that folder place the update_LLD-L22A_hw_in.zip update.zip and update_data_public.zip files along with the HuRUpdater_0.3.zip file. Now place that SDCard into the phone and reboot into TWRP if you can then simply flash HuRUpdater zip file and that should fix it.
I've flashed twrp through fastboot but it's freez
{
"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"
}
ing after restarting from bootloader.
Have you done a factory reset etc after flashing??????
If that doesn't work ERecovery should now be there try pressing Vol up and Power whilst phone is off till you see the menu then there should be an option to download and recovery this should help after else its a ride to the service centre.
Hello, I am a owner of a ZUK Z2 Pro from Brazil, apologies for my english.
I tried to update the mooke rom to pie, but it wasn't working via central mooke, so I downloaded and tried to flash on TWRP, but I was possesed by a demon and instead of not deleting the internal storage, I delete all files. The problem now is that the mobile isn't reconigze in the computer and the device manager shows this:
{
"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"
}
The USBView show this:
Maybe it's something related to the vendor folder that can't be mount on TRWP. I tried adb push, but don't display my device and I don't have acess to allow the usb debugging. I tried USB OTG, but the pendrive is unrecognized. I don't know what to do anymore, but I don't think the mobile is bricked. May day may day!
In twrp you have to click mount otg to make it visible in the file system (if you already did this you can try different adapters/usb sticks). If you deleted the vendor partition I think you should be able to fix it by going back to stock or finding a vendor image/backup. If the only problem is that you ran the vendor to factory script and now twrp dies not find it you can just update twrp. Updating twrp could also help with the unrecognized usb issue.
craftandbuild said:
In twrp you have to click mount otg to make it visible in the file system (if you already did this you can try different adapters/usb sticks). If you deleted the vendor partition I think you should be able to fix it by going back to stock or finding a vendor image/backup. If the only problem is that you ran the vendor to factory script and now twrp dies not find it you can just update twrp. Updating twrp could also help with the unrecognized usb issue.
Click to expand...
Click to collapse
I can't mount otg because twrp don't let me selected the option, I had install all drivers I found of zuk, lenovo and qualcomm and still unrecognizable on the computer, therefore I can flash stock or the vendor image/backup, the version of my twrp is the 3.3.0.0, the most updated. You know if there is a way to force the computer to recognize the device?
Solved doind this.
Hi,
There is this bug on LOS16 that if the pop up camera is up and then the device switches off, the camera stays up permanently until a stock rom is reflashed. I had this issue before, so I restored a backup I made on MIUI 10.3.16 using TWRP, but the device was stuck in a bootloop, and the camera was still stuck, so after restoring different backups I made, I decided to finally use MiFlash to fastboot flash MIUI 10.3.16, and I chose the 'keep user data' option, however this also bootlooped and went into MIUI recovery. I reflashed TWRP and now I face this issue:
TWRP does not recognise that my phone is encrypted, and does not ask for my password, so I can see that my files are here, but they have random folder and file names. (example shown below)
{
"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"
}
I managed to get MIUI running, however it does not ask me for my password, only my Mi account password.
I restored a LOS16 backup I made ages ago, and that also does not ask me for my password - the files I see in the file manager are all encrypted like TWRP.
I attempted the 'twrp decrypt' command, but that does not work either.
I attempted flashing backups and custom roms from a USB, using PitchBlack recovery, OrangeFox, and two TWRP versions.
All I want is for either a recovery or a rom to ask for my unlock password, so it can use that to decrypt my files.
I am not 100% sure if using MiFlash is what caused this, but is there anything else I could try? Are all my files gone? I cannot copy my encrypted files over to my PC and Windows returns an error when trying to do so. Are there any 3rd party tools I can use to decrypt my stuff?
I know I could just wipe my storage and start again, but I do not really want to do that until I know for sure that my files are gone.
I was thinking that MiFlash wiped the decryption keys from my device, but wouldn't a backup restore them?
If it is not possible to save my files, could someone explain why, so I do not make the same mistake again?
Any help would be appreciated.
Format Data, you cant go from miui to aosp or vice versa without doing that. backup your data to pc before or whatever cuz it wipes all internal.
Best thing to do is to fastboot flash again, but use the clean all option.
It's never a good idea to dirty flash when doing anything other than updating a ROM. You might sometimes be OK if flashing from one AOSP ROM to another AOSP ROM.
If your going from MIUI to a custom ROM, or from a custom ROM to MIUI, then it's not worth the aggro you'll most likely get by dirty flashing. Just spend the extra time backing up your data and save the headache.
As for the data, try installing a different TWRP and see if that will then ask for a password to decrypt the phone, before you do a clean install of MIUI.
{
"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"
}
As you can see, I accidentally erased all the partitions. I meant to just clear boot_a.
I tried recovering through these steps:
Download (https://drive.google.com/drive/folders/1WQaaM35SWiF_UbXAM8hiRB95D2CDkIEq) the backup. Unzip it to find 7 luns (0-6).
1. Open QFIL
2. Select Flat Build
3. Click load xml and select the rawprogram(#) XML that is in the lun(0-6) folder.
4. If it asks you for a patch xml, click cancel. It's not needed to flash this backup.
5. Click download
6. Repeat steps for each lun folder
I kept getting this failure message in qfil:
I'm not sure if these are even the steps to fix it. Any Idea on what I need to do to resolve this?
nasedase said:
View attachment 5786719
As you can see, I accidentally erased all the partitions. I meant to just clear boot_a.
I tried recovering through these steps:
Download (https://drive.google.com/drive/folders/1WQaaM35SWiF_UbXAM8hiRB95D2CDkIEq) the backup. Unzip it to find 7 luns (0-6).
1. Open QFIL
2. Select Flat Build
3. Click load xml and select the rawprogram(#) XML that is in the lun(0-6) folder.
4. If it asks you for a patch xml, click cancel. It's not needed to flash this backup.
5. Click download
6. Repeat steps for each lun folder
I kept getting this failure message in qfil:
View attachment 5786723
I'm not sure if these are even the steps to fix it. Any Idea on what I need to do to resolve this?
Click to expand...
Click to collapse
Yes the best thing, or easiest rather, would be to determine which partitions are needed to get lgup to work, then flash a kdz with it.
Don't remember exactly which partitions are needed, google search for that. But flash those, from that backup, one by one, think there's only like 6 partitions needed.
That's the thing about qfil, if yer not sure what yer doing, don't do it
AsItLies said:
Yes the best thing, or easiest rather, would be to determine which partitions are needed to get lgup to work, then flash a kdz with it.
Don't remember exactly which partitions are needed, google search for that. But flash those, from that backup, one by one, think there's only like 6 partitions needed.
That's the thing about qfil, if yer not sure what yer doing, don't do it
Click to expand...
Click to collapse
The problem with the backup is that I wasn't able to get them to work through QFIL. Is there another method of flashing those partitions?
nasedase said:
The problem with the backup is that I wasn't able to get them to work through QFIL. Is there another method of flashing those partitions?
Click to expand...
Click to collapse
one by one. I've done it, it's time consuming, but it can be done. And be sure to pay attention so you don't flash the wrong one to the wrong partition. If you get a message about 'data overflow', immediately cancel, that means you are trying to flash to a partition too small for the image, and you'll overwrite the partition next to it, and probably end up with a brick.
Hi,
My Huawei P20 Pro broke, but earlier I did an backup of Pictures on it using Huawei HiSuite if I remember correctly. Now I tried to open those pictures on my computer but got this:
{
"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"
}
Then I tried to open using ImageGlass but got this:
Then I checked if Linux file command can identify if it's an jpg file and it can't.
file IMG_20190428_115443.jpg
IMG_20190428_115443.jpg: data
This is because Magic bytes of the file starts with 6425 b4a7 which doesn't match JPG magic bytes https://en.wikipedia.org/wiki/List_of_file_signatures
It does not match file on that page.
So what kind of images are these?
Have you been asked to set a password before you did the backup?
adamdvd said:
Have you been asked to set a password before you did the backup?
Click to expand...
Click to collapse
Nope not from what I remember.
When was that backup done and what was the HiSuite version? It used to create the backup by just copying the files from the phone, but since some time (I believe few years now), every time when you start creating a backup, it is asking to set the password and then all the files are being encrypted.
adamdvd said:
When was that backup done and what was the HiSuite version? It used to create the backup by just copying the files from the phone, but since some time (I believe few years now), every time when you start creating a backup, it is asking to set the password and then all the files are being encrypted.
Click to expand...
Click to collapse
The backup was done 2022-07-26 and I used HiSuite version that was used at that point since I downloaded it when I backed it up. So I don't exactly which version it was.
If you've downloaded the newest version at that time, it was surely the version, which is always asking to set a password, when the backup is done. Your files are encrypted and you need to decrypt them (if it's even possible) or rather restore a backup on your phone (but you need to know that password anyway).
adamdvd said:
If you've downloaded the newest version at that time, it was surely the version, which is always asking to set a password, when the backup is done. Your files are encrypted and you need to decrypt them (if it's even possible) or rather restore a backup on your phone (but you need to know that password anyway).
Click to expand...
Click to collapse
I see. But yeah since the phone broke, I can't connect a phone to HiSuite on my computer and restore them. I would need to have the phone for it which sucks..
I tried downloading HiSuite on my computer but can't import the folders I have from the backup into it because it wants to connect to a phone first..