i got this error in recovery mode when i crosflashed my LG-V600am with the firmware name V600EA30c_00_0616.kdz android 12 with this crossflash method :
Crossflash modern Qualcomm LG Devices
i got a message nt code missmatch every reboot and that was annoying so i decided to get back to the original stock backup of my LG V600AM
when i returned to my stock rom at&t android 10 with qfil and erase and load all the partition images (bin) of my full read backup the phone booted succesfully and everything works fine
but the error in the Recovery still appear and the phone is not recognisable in QPST Qfil in QCN restore and backup even if i selected the proper diag port
and also in QPST Configuration program it says No phone also in diag port
i think i messed up something i dont know even if i recovered all the stock LG-V600AM partitions (lun0.1.2.4.5)
can someone explain who has knowledge about this error in recovery
Related
i tried many methods for unbricking it...even in the lg flash tool it started but after 6% it shows error partition system change and on my phone it show D855v10i and on the next line it shows D855v10e.......and i cannot see any tot file for the version d855v10i....when recovery working ...i have tried adb sideload but it also shows error and now nothing works...no recovery no fastboot......i know there must be some way .....
Have you had any backups of stock or previous rom(working rom) ?
Try to restore that or download one at www.needrom.com
Hello.
I'm struggling with this for days now without any result, so I decided to ask for some help.
I had this phone staying in my closet for a few months. A couple of days ago when I tried to charge it, I got the logo saying "Powered by Android" and get stuck there. (the phone was working perfectly before)
Interesting thing was, that most of the time I was not able to power it up at all.
Sometimes I managed to got it into Fastboot Mode TA, but not always.
Reading post here, I tried to reflash with stock ROM using YGDP.
It went smoothly, but now the bootloader is completely corrupted. Not able to get into Fastboot Mode anymore. Doesn't respond to any key at all.
It is recognised as Qualcomm hs-usb qdloader 9008.
After reading some more, I tried to get yhe bootloader back using QFIL without success.
No matter what I try, I get:
13: C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn
14:37:07: Requested ID 13, file: "C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn"
14:37:07: ERROR: function: is_ack_successful:988 SAHARA_NAK_INVALID_DEST_ADDR
14:37:07: ERROR: function: sahara_start:825 Exiting abruptly
14:37:07: ERROR: function: sahara_main:854 Sahara protocol error
14:37:07: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
Same errors with prog_emmc_firehose_8936.mbn
It doesn't even get any acknowledge back from the phone?
Any help is highly appreciated.
Thanks.
Hi , I think you need a full emmc backup.img from working device in order to put your device in fastboot mode and be able to normaly flash stock firmware ....
https://forum.xda-developers.com/general/general/guide-unbrick-coolpad-dazen1-qualcomm-t3362253
Where to get an eMMC dump from?
I've tried with that dump in that post, but absolutely no change at all.
Will the phone read the SD card while it's off? At least that's what that post is telling me to do.
• After successful completion of writing eMMC backup image to SD card, insert the MicroSD card in your device and remove all sim cards. Insert battery into your device now. Do not power it on yet.
• Now you can boot to fastboot mode with the eMMC image on SDCARD.
Click to expand...
Click to collapse
I don't really get this part...
Hi you can't use backup from another device so you need to have the same working device it need to be rooted in order to do make debrick.img which you will make it bootable on micro sd card with Win32DiskImager tool . So then you should put your device in fastboot mode and flash normaly official stock firmware with YGDP tool ... If you don't know someone who can do that for you , check on the internet or YouTube who has device like your to make full emmc dump .
But it you don't have it then you can try Qualfast flash tool , but it required device to be into fastboot mode also you need to extract CPB firmware
Qualfast flash tool
https://androiddatahost.com/asaew
Download firmware from here :
http://www.mediafire.com/file/b3xdr59s6roj0jz/Coolpad_7576U_4.4.230.33.T3.140715.7576U.zip
Example how to extract CBP firmware files .
https://www.youtube.com/watch?v=OEbWKkzfiSA
Example how to use Qualfast flash tool :
https://www.youtube.com/watch?v=R4Bvy0Sax6Q
Just select path from extracted firmware for example C:/Users/SZabio/Desktop/Coolpad 7576U estracted firmware/ , wait all bars to be colored ....
Another option what you can try is one chinese app called COOLPAD DOWNLOAD ASSISTANT SETUP :
Download from here :
English language:
https://drive.google.com/file/d/0B5vyMGZJJmcnclVJb2Y2cHNNQkU/view
Chinese language
http://www.mediafire.com/file/e28degd1vjvevh3/Coolpad+Download+Assistant+Setup+V1.89_141231.rar
add path of CPB firmware (4.4.230.33.T3.140715.7576U.vf_ro.CPB) on number 2 ( browse) and click on green button ( Check Rom) , from up will be 100% loaded , now connect your device without the battery once the app detect your tool it will start writing files to your device .
Example how it should be :
https://www.youtube.com/watch?v=ZhWtvNVlqzE
Good Luck my friend , I hope you will finally get him to work again .
Thank you for trying to help, but as I said, the phone cannot be put into FastBoot mode.
It is completely dead, does not react to any button presses, does not even charge the battery anymore.
It is detected by the PC as "Qualcomm hs-usb qdloader 9008".
That's all.
I know nobody to get a full eMMC dump from unfortunately.
I've found out, that the phone's CPU is a Qualcomm MSM8210 Snapdragon 200, so I tried prog_emmc_firehose_8x10.mbn programming file.
Now QFIL is able to communicate with the phone, but all I'm getting is a bunch of errors, because the configuration .xml files are wrong.
I need rawprogram0.xml patch0.xml and partition.xml for this phone.
I don't understand why the bootloader was not blocked, so it could not have been overwritten by mistake.
Does anyone have some info on how the partitions are organised? Would be enough to write the bootloader in correctly, to get fast boot mode working again?
hello sir
i have an lg g850um at&t , bootloader is locked, was android 9 stock
did backup first thru qfil lun0-6 and mentioned partitions
then did flash open ca version 10r (G850UM20b_00_OPEN_CA_OP_0427.kdz)
i messed up here because i did not use partition dl option, rather refurbish....or was i doing something else also wrong?
now phone is stuck at bootloader screen
and qfil outputting multiple sahara errors
could anyone please guide me in right direction thanks very much!!!]
i was trying to follow this method: https://forum.xda-developers.com/t/tutorial-crossflash-bypass-opid-mismatched-error.4345963/
dl mode and edl mode is still avaialable, so is fastboot.. and backups.. im just not sure what to do?
Hi, I am using a oneplus 7t pro mclaren edition. I have soft-bricked the device. I tried to change the filesystem in twrp to f2fs when i was in stock rom (I know it was a stupid mistake). Now the boot and recovery partitions are destroyed. I can boot to actual fastboot mode. Tried to use payload dumper but whenever it tries to boot fastbootd it says
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Tried erase everything I got the following error using "fastboot -w"
Erasing 'userdata' OKAY [ 0.229s]
/home/abhijith/Documents/op7t/output/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
I have heard of MSM unbrick tool but as far as i know it only works in windows , before installing VM with windows , I want to know if there is any other way i can recover my device. I have a11 fastboot rom and a12 stock rom. Please help
I have exactly the same problem, same errors etc. if I find any solution I'll post it here. Can't use my phone until then I guess. It all happened after my phone was bricked after trying to install TWRP (previously used LineageOS Recovery).
I followed this guide which resulted in the same errors as for you: https://forum.xda-developers.com/t/...ock-fastboot-roms-for-oneplus-7t-pro.3991189/
Okay, I managed to unbrick my phone, but you won't like the (probably only) solution:
- You NEED Windows (7-10) for this, as the tools are only available on this platform, sadly
- There is this one Indian Guy that will save you:
- Includes how to install all drivers and how to get your phone into COM Mode
- This uses the MSM tool. For 1+ 7T Pro, get it here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
- This is going to STOCK RESET you phone 100%, meaning that your bootloader will be locked etc.
- If you get into any Chinese menu after the phone reboots, you can use Google Lens for translation
I can't believe this worked because it just feels so hacky, but trust me, it's a good last resort as you can always put your phone into COM Mode, regardless of how hard you messed up the system [citation needed].
For me even in device manager qualcomm device itself is not showing :0
abhijiths362 said:
For me even in device manager qualcomm device itself is not showing :0
Click to expand...
Click to collapse
Follow the video. When all drivers are installed and you hold both volume buttons while the device is off, it will show up as a COM/serial device for a few seconds before booting.
Important: Only connect the cable while already pressing the buttons or it won't work.
I was able to get to edl mode and msm tool was detecting but now i am facing sahara communication error i dont have official cable so maybe that might be the reason will try that also
@Colin_T Thanks for the help. I was able to install stock rom to my oneplus 7t pro. I really want to install pixel experience, in the instructions it is saying flash oos 12 firmware. But in the official website i am only seeing 11. What to do?
Hi everyone, I bought this phone working from second hand but the seller told me he tried to unlock the bootloader without success and the phone still loose the fingerprint sensor, so I decided to unlock the bootloader successfully following THIS thread and made a downgrade to Android 9 according to THIS other tutorial hopping to get it work again but I wasn't able to do it, so I decided to just use LGUP to install the same Android 12 that I had but the problem started at this point because once the KDZ was installed successfully, the deviced got a bootloop but I still was able to get into EDL, Fastboot and Download Mode, so I tried the steps from THIS other thread to unbrick it but it got even worse at this point, I flashed all the abl, xbl, etc. partitions and the "rawprograme files" via QFIL and then the phone won't even gave any life signals. I contacted someone that some months ago had the same problem and he told me that I could get into EDL by short pining the test point on the motherboard, which actually worked, so I extracted the KDZ Android 9 rom that I flashed in the first place to get the original abl, xbl, etc. partitions that I crossflashed from a v50 (Which I downloaded from the corresponding thread for unbrick), in other words I flashed the same partitions with the correct v50s files instead other model ones. So now this is where I'm right now, the phone don't turns on at all but when I connect it to the PC it gets recognized as LGE Android Platform USB Serial Port (COM11) and the buttons combinations don't work at all, so still can't get into Download mode by any method or even turn off the device, but I still can disconnect the battery and short pin the Qualcomm 9008 mode to use QFIL.
Would someone please be so kind of telling me how could I recover the Download Mode to use the COM4 and COM5 ports to flash the phone via LGUP?. According to THIS other thread, I could get the correct XML "rawprograme files" for my device (which I crossflashed with the v50) from a KDZ using some tools and Python, but I have to be honest: I DON'T KNOW HOW, even with the step by step tutorial.
At this point I think this would be the right step, to flash all the original files for my model and get the Download Mode back to be able to flash the KDZ rom via LGUP and update via OTA to Android 12 again to avoid the bootloop problem.
try to reflash(QFIL method) modified abl should get the download mode back
darrelama said:
try to reflash(QFIL method) modified abl should get the download mode back
Click to expand...
Click to collapse
Thanks for replying, but I have some questions:
1. The abl file you mean is the engineering one? And...
2. Would you be so kind of telling me how to flash via QFIL? I've seen that it's possible but as far as I know, I need a specific type of rom files to do it, and I don't know how to convert a KDZ or where to download a QFIL ROM.
Thanks!
iMarzateD said:
Thanks for replying, but I have some questions:
1. The abl file you mean is the engineering one? And...
2. Would you be so kind of telling me how to flash via QFIL? I've seen that it's possible but as far as I know, I need a specific type of rom files to do it, and I don't know how to convert a KDZ or where to download a QFIL ROM.
Thanks!
Click to expand...
Click to collapse
yes, engineering one mentioned here （THIS）
QFIL>Tools > Partition Manager
read abl_a and abl_b to backup then load abl engineering file to both
basically the same steps up to the following:
"Go back to Partition Manager and right click on abl_a again then select Manage Partition Data, then Select Load and choose the abl engineering file.
Do the same for abl_b."
then try download mode
darrelama said:
yes, engineering one mentioned here （THIS）
QFIL>Tools > Partition Manager
read abl_a and abl_b to backup then load abl engineering file to both
basically the same steps up to the following:
"Go back to Partition Manager and right click on abl_a again then select Manage Partition Data, then Select Load and choose the abl engineering file.
Do the same for abl_b."
then try download mode
Click to expand...
Click to collapse
Hello again, already tried flashing the engineering abl but I still can't get into download mode. The phone keeps off the whole time and by plugging in the USB cable, no matter what button combination, the PC always recognizes it as the same LGE Android Patform USB Serial Port (COM11), the only other state of the device is the Qualcomm 9008 by pinning the motherboard. This specific COM11 state never was able to flash anything by PC, I don't know what actual mode is, but when I was able to set the devide in Download Mode the PC always showed 2 devices in the Device Manager, the COM5 and the COM4, that way I knew I was able to use the LGUP to flash. I'm thinking that I'm not setting the phone on the correct state to flash by any method, but since the buttons seems not to work, I don't know how could I do it.
While on this mode "LGE Android Patform USB Serial Port (COM11)", try to hold both power and vol- for some seconds until the "LGE Android Patform USB Serial Port (COM11)" disappear from your PC device manager and immediately release both and now hold vol+ button to get into download mode.
You can do it while on the 9008 mode too though.
Maybe that can help.
I have LUNs backup for v50s but I can't upload it due to my internet plan quota limit.
ardian1899 said:
While on this mode "LGE Android Patform USB Serial Port (COM11)", try to hold both power and vol- for some seconds until the "LGE Android Patform USB Serial Port (COM11)" disappear from your PC device manager and immediately release both and now hold vol+ button to get into download mode.
You can do it while on the 9008 mode too though.
Maybe that can help.
I have LUNs backup for v50s but I can't upload it due to my internet plan quota limit.
Click to expand...
Click to collapse
Thanks, I'll try that for sure to see if I can get into the Download Mode or something. I would appreciate so much if you could share your backup, since I think I could restore the whole firmware with it, but I don't have any experience on the "LUNs" tho. I'm any case, I don't have too much time every week to give it a try, so I hope tomorrow I could test the combo you say.