Unbrick Oppo A91 CPH2021. Need oppo_custom file. - Android Q&A, Help & Troubleshooting

I accidentally used SP Flash Tool "Format All" option when trying to flash a firmware.
After that, I was able to boot the phone but got stuck at the android logo with the error 0x99256658.
According to this thread https://forum.xda-developers.com/t/crash-phone-realme-8-need-image-oppo_custom.4402181/ ,
I know that the problem is caused by missing oppo_custom file.
I then used mtkclient to flash multiple different oppo_custom files on the internet (around 15 files).
Some of them boot the phone to the welcome screen but the phone touch does not work (even in recovery mode).
Does anyone have a dump of this oppo_custom file for this phone or even better, a full dump of this phone? I need the file to restore the phone touch
Thanks in advance.

tienlk19 said:
I accidentally used SP Flash Tool "Format All" option when trying to flash a firmware.
After that, I was able to boot the phone but got stuck at the android logo with the error 0x99256658.
According to this thread https://forum.xda-developers.com/t/crash-phone-realme-8-need-image-oppo_custom.4402181/ ,
I know that the problem is caused by missing oppo_custom file.
I then used mtkclient to flash multiple different oppo_custom files on the internet (around 15 files).
Some of them boot the phone to the welcome screen but the phone touch does not work (even in recovery mode).
Does anyone have a dump of this oppo_custom file for this phone or even better, a full dump of this phone? I need the file to restore the phone touch
Thanks in advance.
Click to expand...
Click to collapse
Read the last post. I think you have no luckhttps://www.hovatek.com/forum/thread-41931-page-5.html

joke19 said:
Read the last post. I think you have no luckhttps://www.hovatek.com/forum/thread-41931-page-5.html
Click to expand...
Click to collapse
I did read that post. However, there is another post on the exact phone model and the same problem as mine on that same forum https://www.hovatek.com/forum/thread-42497.html. The guy got the phone to work. I contacted him but no responses.
I tried 3 different oppo_custom from realme6 and 6i. Got the phone to boot but the touch does not work.
There is also a commercial tool (Unlock Tool) to solve this problem.
So my last hope without the tool is to try a dump from a same device.

I took a full EMMC dump of Oppo F15 phone (similar in specs to A91), extracted the oppo_custom file and flashed it back to the A91 and it works. The content of the extracted oppo_custom file is different from previous files that I used, it has more content instead of zeros block. Below is the file for anyone that faces the same trouble as mine.

hey bro can u pls give me the full backup of your emmc pls

Related

[HELP] 9300+ (mtk6577) PMT corrupted - can't upgrade firmware

Hi.
My 9300+ (chinese mtk6577) is dead... I have to updated wrong firmware and my phone will don't turn ON again, when I use the SP Flash Tool appears the message: "Firmware Upgrade could not be executed without PMT. Please "Download" ONLY first to create PMT on the target!
My internal partition is corrupted and i can't create PMT because my phone don't Turn On, but my USB is recognized by windows.
Please Help Me.
rstalker said:
Hi.
My 9300+ (chinese mtk6577) is dead... I have to updated wrong firmware and my phone will don't turn ON again, when I use the SP Flash Tool appears the message: "Firmware Upgrade could not be executed without PMT. Please "Download" ONLY first to create PMT on the target!
My internal partition is corrupted and i can't create PMT because my phone don't Turn On, but my USB is recognized by windows.
Please Help Me.
Click to expand...
Click to collapse
I know this is an old post, but this may help someone. (would have me a month ago)
Hopefully if your USB is seen in Windows you can convince SP Flash Tool to spew/download/write data to your phone while it's in Meta Mode.
I believe the PMT block is created by SP Flash Tool dynamically from scatter file. It's comparing the scatter file with what is sitting at the PMT address on the flash. If these two mismatch, you get the error you mentioned. If you want to force a new PMT that matches your scatter file's layout, you have to do a "Format" in SP Flash Tool. This will get you back to a PMT on flash that matches your scatter file, then SP Flash Tool will be happy and allow you to use Download (write to flash).
What is a PMT? A partition table that holds the addresses to all the other partitions.
syserr said:
I know this is an old post, but this may help someone. (would have me a month ago)
Hopefully if your USB is seen in Windows you can convince SP Flash Tool to spew/download/write data to your phone while it's in Meta Mode.
I believe the PMT block is created by SP Flash Tool dynamically from scatter file. It's comparing the scatter file with what is sitting at the PMT address on the flash. If these two mismatch, you get the error you mentioned. If you want to force a new PMT that matches your scatter file's layout, you have to do a "Format" in SP Flash Tool. This will get you back to a PMT on flash that matches your scatter file, then SP Flash Tool will be happy and allow you to use Download (write to flash).
What is a PMT? A partition table that holds the addresses to all the other partitions.
Click to expand...
Click to collapse
THANK YOU! :highfive::highfive::highfive::highfive::highfive::highfive:
LOVE YOU MAN
PMT Corrupted & Format-all done
I faced the same error.......my PMT got corrupted (possibly due to an earlier attempt to re-size (system / data) partition using Swiftbootloader)...... & un-fortunately, I clicked on Format in SP Flash Tool as well.
Now all is gone.... phone doesn't switch on.........
Please guide...... to bring the bricked handset (Spice Mi-350n) to life again. I have backups..... but that relate to different scatter file (PMT) perhaps........ do I need to search & learn webos & acmeinstaller kind of things now?
spandrd said:
I faced the same error.......my PMT got corrupted (possibly due to an earlier attempt to re-size (system / data) partition using Swiftbootloader)...... & un-fortunately, I clicked on Format in SP Flash Tool as well.
Now all is gone.... phone doesn't switch on.........
Please guide...... to bring the bricked handset (Spice Mi-350n) to life again. I have backups..... but that relate to different scatter file (PMT) perhaps........ do I need to search & learn webos & acmeinstaller kind of things now?
Click to expand...
Click to collapse
Hi spandrd,
did u manage to resolve this problem. I am also facing this problem after attempting to re-size the partition using meteos mtk6589 rom edit apk .... Although my phone is still working properly without any issue, i am unable to root or install CWM by any means (tried mtk mobileuncle tools, tried spflash tool) but not working. Can you guide me how to root and install cwm as i am unable to revert to my old backup w/o cwm.
spandrd said:
I faced the same error.......my PMT got corrupted (possibly due to an earlier attempt to re-size (system / data) partition using Swiftbootloader)...... & un-fortunately, I clicked on Format in SP Flash Tool as well.
Now all is gone.... phone doesn't switch on.........
Please guide...... to bring the bricked handset (Spice Mi-350n) to life again. I have backups..... but that relate to different scatter file (PMT) perhaps........ do I need to search & learn webos & acmeinstaller kind of things now?
Click to expand...
Click to collapse
HNaseer said:
Hi spandrd,
did u manage to resolve this problem. I am also facing this problem after attempting to re-size the partition using meteos mtk6589 rom edit apk .... Although my phone is still working properly without any issue, i am unable to root or install CWM by any means (tried mtk mobileuncle tools, tried spflash tool) but not working. Can you guide me how to root and install cwm as i am unable to revert to my old backup w/o cwm.
Click to expand...
Click to collapse
The best way to restore your phone was already answered in the previous post, that is to FORMAT your device and subsequently flash the official firmware.
syserr said:
I know this is an old post, but this may help someone. (would have me a month ago)
Hopefully if your USB is seen in Windows you can convince SP Flash Tool to spew/download/write data to your phone while it's in Meta Mode.
I believe the PMT block is created by SP Flash Tool dynamically from scatter file. It's comparing the scatter file with what is sitting at the PMT address on the flash. If these two mismatch, you get the error you mentioned. If you want to force a new PMT that matches your scatter file's layout, you have to do a "Format" in SP Flash Tool. This will get you back to a PMT on flash that matches your scatter file, then SP Flash Tool will be happy and allow you to use Download (write to flash).
What is a PMT? A partition table that holds the addresses to all the other partitions.
Click to expand...
Click to collapse
iZLeeP said:
The best way to restore your phone was already answered in the previous post, that is to FORMAT your device and subsequently flash the official firmware.
Click to expand...
Click to collapse
Hi iZLeeP
Thanks for the quick reply. I dont have any official rom. The only backup i have is using the CWM backup of the official rom before applying a custom LG rom. If it is possible, how can i utilize the CWM backup of the official rom to revert back please ? I can see boot.img and recovery.img files in cwm backup; can i utilize them somehow to revert back ? Please help. Thanks.
HNaseer said:
Hi iZLeeP
Thanks for the quick reply. I dont have any official rom. The only backup i have is using the CWM backup of the official rom before applying a custom LG rom. If it is possible, how can i utilize the CWM backup of the official rom to revert back please ? I can see boot.img and recovery.img files in cwm backup; can i utilize them somehow to revert back ? Please help. Thanks.
Click to expand...
Click to collapse
Let me remind people, the first order of business must be to have a full firmware backup from the phone manufacturer or thru MTK Droid Root & Tools. Reading that you tried to resize your system & data partition, your cwm backup should not be affected by it. Try restoring to default the partition sizes using the app/script you used to resize. It should have that function. Then flash custom recovery and root and see if it works.
phone booting to main-screen or not?
hi HNaseer....
As replied by @syserr & @iZLeeP .............you can try to "Format-All / Format-All except bootloader" type of thing PROVIDED THAT YOU HAVE COMPLETE BACKUP OF RELEVANT PARTITIONS (till Cache and / or till FAT partition length) using SP Flash Tool........ & MTK Droid Tool......... PLUS, YOU WILL NEED IMEI BACKUP (IMEI No.) in such case if you want to restore.
SP Flash Tool needs Scatter File......... (obtainable thru MTK Droid Tool) & can help in backup of various partitions even if phone not turning on. BUT IMEI backup would be good........ IF YOU ARE ABLE TO BOOT / reach main screen after boot animation.
Rest of the details can be first read / understood from my MT6589 chipset type handset link from @Atrvscet : http://forum.xda-developers.com/showthread.php?t=2514419
Or, better search exact thread on xda / elsewhere to get stock / custom rom & flashing etc.
Lastly, if you are able to boot in recovery, best thing should be to flash / force flash original cwm backup from recovery.
HNaseer said:
Hi spandrd,
did u manage to resolve this problem. I am also facing this problem after attempting to re-size the partition using meteos mtk6589 rom edit apk .... Although my phone is still working properly without any issue, i am unable to root or install CWM by any means (tried mtk mobileuncle tools, tried spflash tool) but not working. Can you guide me how to root and install cwm as i am unable to revert to my old backup w/o cwm.
Click to expand...
Click to collapse
spandrd said:
hi HNaseer....
As replied by @syserr & @iZLeeP .............you can try to "Format-All / Format-All except bootloader" type of thing PROVIDED THAT YOU HAVE COMPLETE BACKUP OF RELEVANT PARTITIONS (till Cache and / or till FAT partition length) using SP Flash Tool........ & MTK Droid Tool......... PLUS, YOU WILL NEED IMEI BACKUP (IMEI No.) in such case if you want to restore.
SP Flash Tool needs Scatter File......... (obtainable thru MTK Droid Tool) & can help in backup of various partitions even if phone not turning on. BUT IMEI backup would be good........ IF YOU ARE ABLE TO BOOT / reach main screen after boot animation.
Rest of the details can be first read / understood from my MT6589 chipset type handset link from @Atrvscet : http://forum.xda-developers.com/showthread.php?t=2514419
Or, better search exact thread on xda / elsewhere to get stock / custom rom & flashing etc.
Lastly, if you are able to boot in recovery, best thing should be to flash / force flash original cwm backup from recovery.
Click to expand...
Click to collapse
HNaseer.... I agree with everything spandrd just said. I'd like to stress though, getting a backup of your NVRAM partition is much better than having MTKDT copy your /data/nvram. So if you have a choice, backup the NVRAM partition with SPFT or if MTKDT has that option use it. (I've rarely used MTKDT as I found aspects confusing)
Incredible.
Thank you so much. HAd almost given up hope...
How to connect mtk6582device (spice dream uno) in meta mode
Plz help me out guys ??????
I have a similar issue with my Unite 2 phone. I tried the format option too but I am getting STORAGE_ERROR
[Storage Error] The load and the target are inconsistent!
A Hint message is also there :
The load to be downloaded is for EMMC.
The Target storage is .
Please select a correct load according to the storage.
Please help me in resolving this issue. My phone model is Micromac unite 2 A106 8GB model.
syserr said:
HNaseer.... I agree with everything spandrd just said. I'd like to stress though, getting a backup of your NVRAM partition is much better than having MTKDT copy your /data/nvram. So if you have a choice, backup the NVRAM partition with SPFT or if MTKDT has that option use it. (I've rarely used MTKDT as I found aspects confusing)
Click to expand...
Click to collapse
hello guys
how can i format my device Blu studio energy 2 with sp flash toolmy phone is dead after i do the format and i dont have firmware back up
thank you
---------- Post added at 01:24 AM ---------- Previous post was at 12:26 AM ----------
hello guys
how can i format my device Blu studio energy 2 with sp flash tool my phone is dead after i do the format and i dont have firmware back up
thank you
Omarod said:
hello guys
how can i format my device Blu studio energy 2 with sp flash toolmy phone is dead after i do the format and i dont have firmware back up
thank you
Not sure what you are expecting to do with a FORMAT. If you had a good backup of your NVRAM partition, then what you would need is a SCATTER file and ROM files, you could FORMAT then DOWNLOAD the ROM files and your NVRAM file to your device with SPFT. But since you don't have your NVRAM partition, you don't have an easy path. FYI, I don't know new devices... there could be more complication than MT6577/75.
Click to expand...
Click to collapse
syserr said:
Omarod said:
hello guys
how can i format my device Blu studio energy 2 with sp flash toolmy phone is dead after i do the format and i dont have firmware back up
thank you
Not sure what you are expecting to do with a FORMAT. If you had a good backup of your NVRAM partition, then what you would need is a SCATTER file and ROM files, you could FORMAT then DOWNLOAD the ROM files and your NVRAM file to your device with SPFT. But since you don't have your NVRAM partition, you don't have an easy path. FYI, I don't know new devices... there could be more complication than MT6577/75.
Click to expand...
Click to collapse
Thank you for reply
Where do i find the scatter file and the ROM for my blu studio energy 2 MT6735 chepset please
Thank you again
Click to expand...
Click to collapse
Omarod said:
syserr said:
Thank you for reply
Where do i find the scatter file and the ROM for my blu studio energy 2 MT6735 chepset please
Thank you again
Click to expand...
Click to collapse
Try google, or search xda, or needrom.com...
This may or may not help you. If I were you I would use SPFT right now to try to backup your NVRAM partition if it's not too late. Your FORMAT may have wiped the NVRAM partition already. If it has wiped it, your only good path is to find someone willing to give you their NVRAM partition. Then somehow insert your own IMEI and WIFI MAC in and pray.
Click to expand...
Click to collapse
Could you tell me step by step what can I do coz I'm new in sp flash tool and. Mtk droid root and flash tool
Thank you so much
First find proper ROM on www.needrom.com
Hello Guys
still waiting for help please
Blu Studio Energy 2 -Backup file- firmware Please

Bricked Alcatel Pop C1 4015X (Mediatek MT6572)

Hey all.
Easy question I hope! I've been following the guide to unbrick MTK devices, and have managed to get an original factory ROM to flash to the phone, green tick in SP Flash Tools. However, the phone still won't power on at all, save for the light if plugged into usb.
The ROM I've been using is an original factory rom named "ONE-TOUCH-4015X_POP_C1_FULL_STOCK_BACKUP" which is readily available online. I'm not sure what I did to brick it in the first place, but it was within SP flashtool. I May have formatted accidentally.
If someone coudl help I'll try to provide all logs or files requested but please tell me where these could be found as I'm not that good with flash tool.
To confirm the phone won't boot into any mode, recovery is dead, fastboot is dead....
same problem hope somone help us
also share ur backup please
darkglobe87 said:
Hey all.
Easy question I hope! I've been following the guide to unbrick MTK devices, and have managed to get an original factory ROM to flash to the phone, green tick in SP Flash Tools. However, the phone still won't power on at all, save for the light if plugged into usb.
The ROM I've been using is an original factory rom named "ONE-TOUCH-4015X_POP_C1_FULL_STOCK_BACKUP" which is readily available online. I'm not sure what I did to brick it in the first place, but it was within SP flashtool. I May have formatted accidentally.
If someone coudl help I'll try to provide all logs or files requested but please tell me where these could be found as I'm not that good with flash tool.
To confirm the phone won't boot into any mode, recovery is dead, fastboot is dead....
Click to expand...
Click to collapse
Did you ever get the above rom to work? If so what did you do? Or did you find another method to unbrick the phone? Thanks.
Managed to unbrick my 4015 using Mobile Upgrade S 4.3.0 from the Alcatel Website.
http://www.alcatelonetouch.com/global-en/support/download/one_touch_idolx.html
Very simple to use, just install and follow instructions.
darren1 said:
Managed to unbrick my 4015 using Mobile Upgrade S 4.3.0 from the Alcatel Website.
http://www.alcatelonetouch.com/global-en/support/download/one_touch_idolx.html
Very simple to use, just install and follow instructions.
Click to expand...
Click to collapse
no work this version. yes 4015 but no 4015x
Sorry I should have put my phone is a 4015X not 4015. The application does say 4015 which I selected and all went well.
my 4015x no update, it not load, only work flash mode connected to pc and no work mobile upgrade.
4015X Partitions
the 4015x has a different set of partitions to the older (dual sim) 4015
i have a modded rom (kitkat), a modded stock recovery (as stock is also wrong, wont mount data) and a modded cwmrecovery.
i will be posting these soon
i will create a new post for the 4015x version
and will also be asking for other versions of the 4015 users to post me there partition trees and i will repack some recoverys and some roms for you all
note: there are 6 versions that i have seen and they may all have diff tables
hope these will help the pop c1 community
recoverys and rom
Stock Recovery (Fixed)
https://drive.google.com/file/d/0B4ZKFXlQiHioVUExRW1sZkdzSFk/view?usp=sharing
CWMRecovery (Fixed)
https://drive.google.com/file/d/0B4ZKFXlQiHioUTJqOTMtbUNPTEU/view?usp=sharing
kitkat-cm11-modROM.zip (Fixed)
https://drive.google.com/file/d/0B4ZKFXlQiHioUUI3V2Jsd0lTN1k/view?usp=sharing
(I am currently using this rom my self and all seems to be good except vibration, it also thinks its a dual sim but not causing a probb)
Hello!
This thread is quite old but near my case.
I have an Alcatel Pop C1 4015X (cpu MTK6572M) that can't start at all (only the power LED is ON).
I have a backup of this device made with "SP Flash Tool V5.1532.00" but I've error "not enough space" when
I try to restore it.
Same error when I try to restore just one file.
For example, I've tried to restore only the "Stock Recovery" you give above.
I do this:
- I start Flash_Tool v5.1532.00
- I open scatter file from my backup done with the same tool
- I unselect all pieces of the backup except "Recovery" and I browse to the "Stock Recovery" file I've dl
from this thread.
I've got this error : "not enough storage space (1011)"
What could be the problem ?
I makes me totally crazy !
By advance, thanks for your help.
Regards,
Freeman.
Fr33M4n! said:
Hello!
This thread is quite old but near my case.
I have an Alcatel Pop C1 4015X (cpu MTK6572M) that can't start at all (only the power LED is ON).
I have a backup of this device made with "SP Flash Tool V5.1532.00" but I've error "not enough space" when
I try to restore it.
Same error when I try to restore just one file.
For example, I've tried to restore only the "Stock Recovery" you give above.
I do this:
- I start Flash_Tool v5.1532.00
- I open scatter file from my backup done with the same tool
- I unselect all pieces of the backup except "Recovery" and I browse to the "Stock Recovery" file I've dl
from this thread.
I've got this error : "not enough storage space (1011)"
What could be the problem ?
I makes me totally crazy !
By advance, thanks for your help.
Regards,
Freeman.
Click to expand...
Click to collapse
What i did was i used SPFT to flash a backup i found online. Can't post links, just google "ot 4015X Original SPFT ROM", what i used was the algerian rom. Then i flashed the EE stock rom. My own backup didn't flash back correctly either, that's why i used that one i fould online.
4015X unbricked !
Hello,
I found a similar solution here (replace * with . to get a correct http link):
forum*gsmhosting*com/vbb/f317/ot-4015x-firmware-arabic-bulgaria-africa-kenya-1946694/index2.html
It took me hours to find good stock ROMs (bulgarian & arabian then french via OTU) !
You'll have to "play" with pro_info and scatter file...
Good luck to all to unbrick your 4015x !
Regards,
Freeman.
how to partition system storage space of onetouch pop c1?

Bricked k8 plus (3gb ram indian variant)

hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
hey did you get it fixed and can you please send the link to the stock rom
yayjk said:
hey did you get it fixed and can you please send the link to the stock rom
Click to expand...
Click to collapse
TRY ASKING THE QUESTION ON THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
---------- Post added at 05:00 PM ---------- Previous post was at 05:00 PM ----------
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
TRY ASKING IN THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
How to Unbrick Lenovo K8 Plus 4GB
Hi All
I tried many stock roms and many versions of SP flash tool but none helped me to unbrick my lenovo k8 plus (4gb ram).
I was trying to downgrade it to Naugat from Oreo but it shows same error every time.
Error is (SP Flash tool version latest 5.18)
" Error_Status_Sec_Insufficient_Buffer( 0xC002004B)
[Hint]:
Verified boot is enabled.
Please download signed image (md1img-verified.img) or disable verified boot."
Plzzz help same problem
Enabled verified boot ...how to disabled
Same problem my lenovo k8plus
Enabled verified boot ...how to disabled
You need to use "Lenovo Moto Smart Assistant" instead of SPFlash tool to flash and you will be good to go. You can get the tool from the Lenovo official website.
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
Try with Lenovo Moto Smart Assistant. I too have bricked my phone... but I've successfully started my phone using this tool. you will get official signed ROM from here.
you can use LMSA tool to rescue,90% sucessfully ,don't use splashtool beacause it's many error if you choose wrong version
Had the same problem. Can confirm Lenovo's tool sucessfully recovers ohone from bricked state. A lifesaver!
Downloaded from https://lenovomobilesupport.lenovo.com/br/pt/downloads/ds101291-rescue-and-smart-assistant-lmsa
then updated to version 5.9.2.4 from inside the app itself

flash failed on rooted s5neo

guys i think i got a real problem here.
First of all i apologize for my english and thank you in advance
i was trying to flash magisk on my with twrp rooted device (samsung galaxy neo, G903F) and since i had some problems i thought i could try it on a fresh system again.
so i just wanted to flash a stock image from updato (i am kinda sure it is the right version).suddenly odin says the progress failed and after a few minutes waiting i disconnected and took out the battery.
when i wanted to start it, i got "error occurred while updating software. use emergency recovery function in smart smitch PC software"
after watching a short video i tried this smartswitch-thing, but its just telling me my device isnt supportet.
the problem is that my phone was rooted while i tried to flash the stock image right? so smartswitch wont work for me? what do you advice? only thing i can do is download modus.
help pleease
Bombadadil said:
guys i think i got a real problem here.
First of all i apologize for my english and thank you in advance
i was trying to flash magisk on my with twrp rooted device (samsung galaxy neo, G903F) and since i had some problems i thought i could try it on a fresh system again.
so i just wanted to flash a stock image from updato (i am kinda sure it is the right version).suddenly odin says the progress failed and after a few minutes waiting i disconnected and took out the battery.
when i wanted to start it, i got "error occurred while updating software. use emergency recovery function in smart smitch PC software"
after watching a short video i tried this smartswitch-thing, but its just telling me my device isnt supportet.
the problem is that my phone was rooted while i tried to flash the stock image right? so smartswitch wont work for me? what do you advice? only thing i can do is download modus.
help pleease
Click to expand...
Click to collapse
You should never remove the battery of your phone when an update failed , you just corrupted your system.
What you have to do now is enter in bootloader mode , plug you phone to your PC , and flash the stock system.img and boot.img.
Search how to do that on your device , watch videos and guide on XDA , then do this.
Remember to always make a backup of your system before doing that.
TY for the fast answer!
do you mean the recovery mode(home + power + vol.up)? i cant enter anything except of the downloadmode (home+power+vol.down). I extracted the boot.img and system.img from the tar.md5 file with 7zip and coverted it to .tar, can i flash that per Odin the same way i tried to flash the whole firmware? and if yes, in which order should i do it or sould i convert boot.img and system.img to one single .tar file? sry i googled more than an hour but didnt find instructions to do this. just the extracting and converting part and thousands of how to flash whole firmwares or fixes via smartswitch-.-
Bombadadil said:
TY for the fast answer!
do you mean the recovery mode(home + power + vol.up)? i cant enter anything except of the downloadmode (home+power+vol.down). I extracted the boot.img and system.img from the tar.md5 file with 7zip and coverted it to .tar, can i flash that per Odin the same way i tried to flash the whole firmware? and if yes, in which order should i do it or sould i convert boot.img and system.img to one single .tar file? sry i googled more than an hour but didnt find instructions to do this. just the extracting and converting part and thousands of how to flash whole firmwares or fixes via smartswitch-.-
Click to expand...
Click to collapse
I'm not an Odin expert at all , but I think you should use the .IMG file , starting with the system.img , and after the boot.img
But I'm not sure at all , take another hour to make searches.

[Solved] Qualcomm China Phone hangs in a bootloop Hisense A5 (HLTE202N)

I have a bricked Hisense A5 (Qualcomm, China) device which stays in a bootloop and I don't know how I can unbrick it.
Facts are:
Device: Hisense A5 (HLTE202N)
Firmware: Stock L1657 6.03.02.00 / Kernel 4.9.112
- I could flash in edl mode successful a stock firmware, but nothing changed after a reboot
- Device stays with "Hisense and powered by Android screen".
- The bootloader can't be unlocked
- teardown device and disabled battery for some minutes and tried to charge it with a wall charger -> bootloop
What I can (like before flashing in edl-mode):
- Entering edl-mode with a xiaomi edl-cable (Qualcomm HS-USB 9008er mode and diagnostic mode 900E after flashing)
- entering fastboot (pressing volume up while rebooting and connecting pc)
What I can't:
-flashing TF-Mode (Firmware on microSD)
-rebooting to system
-shutdown
-recharging wall charger (bootloop)
-not detected as usb-drive for filetransfer
This bootloop mode you can read quite often. The Xiaomi guys can fix this by flashing a fastboot Firmware, but they have an unlocked bootloader
Anybody knows a solution or what I can try to fix this?
Solved:
https://forum.xda-developers.com/showpost.php?p=82726877&postcount=7
JLowe said:
I have a bricked Hisense A5 (Qualcomm, China) device which stays in a bootloop and I don't know how I can unbrick it.
Facts are:
Device: Hisense A5 (HLTE202N)
Firmware: Stock L1657 6.03.02.00 / Kernel 4.9.112
[...]
Anybody knows a solution or what I can try to fix this?
Click to expand...
Click to collapse
Have you already considered trying to use the 6.09.06.00 ROM available via forum.xda-developers.com/showpost.php?p=82583733&postcount=28 ?
defylogic said:
Have you already considered trying to use the 6.09.06.00 ROM available via forum.xda-developers.com/showpost.php?p=82583733&postcount=28 ?
Click to expand...
Click to collapse
Yes, sorry forgot that to mentioned. Good point. That was the first I tried with some other guys in the thread but it doesn't work at all. Tried different microSD and formatting.
Well if the TF Mode not working with 6.0.9 and you have 6.0.3 which is already rooted logic say to try not with 6.0.9 but with 6.0.4 update or better with 6.0.3 but original i.e not rooted. I think something in 6.0.3 is not compatiblle with something in 6.0.9. Simply as that. I remember I say guy in thread for Hisense A5 root which had all update files and WeChat group?
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
gowin132 said:
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Click to expand...
Click to collapse
Do you have the same files of 6.09.06 version? If yes, please share. I have same problem but my phone has latest OS version.
gowin132 said:
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Click to expand...
Click to collapse
Great, these files are working flawless in qfil. Could recover the system and then update in Tf-Mode to actual 6.09
These are the original boot, recovery and vbmeta image from 6.09.06.
https://drive.google.com/file/d/1JeUEaBxpH5zu22v-6V_6LAqZzGuXmUhf/view?usp=sharing
Mehedi34 said:
Do you have the same files of 6.09.06 version? If yes, please share. I have same problem but my phone has latest OS version.
Click to expand...
Click to collapse
Do you guys have full firmware with system and other imgs?? Mine seems to still bricked
lillo9546 said:
Do you guys have full firmware with system and other imgs?? Mine seems to still bricked
Click to expand...
Click to collapse
I'm sorry for asking what is probably a silly question, but how exactly do you flash files like boot.img using Qfil ?
I can get into fastboot., but not edl mode.
I know old thread, but am having problems with a bricked A5. After a lot of trial and error, it sometimes gets into Fastboot mode. I can then ask for fastboot device and it responds with a hex number and fastboot.
When I try to flashall new partitions, it fails with:
fastboot: error: ANDROID_PRODUCT_OUT not set or non allowed.
Once I could flash individual partition with:
fastboot flash boot boot_recovery_vbmeta_6.03.02/boot.img
Sending 'boot' (65536 KB) OKAY [ 2.113s]
Writing 'boot'
But then it just sits there and nothing seems to happen.
Anyone has suggestions on what to try, am running out of ideas
.
It would be amazing if anyone could share:
- Stock ROM 6.12 full QFIL backup.
- EFS/QCN backup files.
Thanks
JLowe said:
Great, these files are working flawless in qfil. Could recover the system and then update in Tf-Mode to actual 6.09
Click to expand...
Click to collapse
Hi. I have the same problem as you, but I don't know how to flash those files with qfil. Can you please explain it to me?

Categories

Resources