As title said. At the first time, I used msm without windows drive (9008). I notice that and stop msm immediatly. And, my 9R could not turn on again. I tried to use msm to fix it, everytime I followed the guard using msm, it allways showed "Automatic detection of DDR failed" in red. Can anyone help me get rid of this? My 9R is 12GB+256GB.
Saltyinory said:
As title said. At the first time, I used msm without windows drive (9008). I notice that and stop msm immediatly. And, my 9R could not turn on again. I tried to use msm to fix it, everytime I followed the guard using msm, it allways showed "Automatic detection of DDR failed" in red. Can anyone help me get rid of this? My 9R is 12GB+256GB.
Click to expand...
Click to collapse
MsmDownloadTool V4.0:
Manual Choose DDR → Download to DDR5
(I think 9R 12G/256G is DDR5. )
haroldf1racing said:
MsmDownloadTool V4.0:
Manual Choose DDR → Download to DDR5
(I think 9R 12G/256G is DDR5. )
Click to expand...
Click to collapse
if i choose DDR5, it show the sahara error.
Saltyinory said:
if i choose DDR5, it show the sahara error.
Click to expand...
Click to collapse
I would try another port, make sure you have the correct drivers installed and the phone recognizes the 9008 in device manager, also disable driver verification.
Related
hello folks.
i had nothing to do so i made a QFIL flashable system image of a Marshmallow VibeUI backup, which was released for Latin Amerians (dunno what lenovo software engineers were smoking when they decieded to keep MM from the rest of the world ).
So, this ROM (or rather backup) is ported by me as a qfil flashable file for A6020a41 phones, which are popular for not having unlockable bootloaders.
since this rom is official, it passes dm-verity and boots fine on locked BLs.
this package only flashes system.img and boot.img, so no device specific files are flashed. it worked fine on my SD415 device with locked BL.
link: https://www.androidfilehost.com/?w=files&flid=283731
HOW TO FLASH:
1) wipe data from recovery (twrp or stock, doesn't matter). Your internal might be wiped too.
2) install revelant drivers (hint: look for them on "return to stock" thread or at the link at the bottom of this post).
3) flash the package (same procedure when recovering stock rom)
and don't blame me if your phone or your kitten dies because of this rom (i'm gonna laugh at you if you do so), i made this just because SD616 users can't flash custom roms, despite me having SD415 w/ unlocked bootloader. HAVE FUN!!!
Note: if you have SD415 variant then proceed to here
Notes:
1. VoLTE appears to be not working, this depends on whether lenovo decides to update it for lat. america.
2. If you want to make a qfil flashable rom, then pm me for a template (or just replace system and boot images in this zip).
Normal things to expect:
1) device name change to a6020l36
2) (probably) being banned from play services. (important: no dev is responsible for a6020 being banned. Do not waste your time blaming, not only on this thread but on the whole K5(Plus) forum).
oh, and before i forget, remember to choose .mbn file accordingly to your SoC.
msm8929 -> SD415
msm8939 -> SD616
Is it possible to get volte in this?
Good work ,but please mention that volte won't work in the OP since I have tried this long back .
Harry8242 said:
Good work ,but please mention that volte won't work in the OP since I have tried this long back .
Click to expand...
Click to collapse
Thanks for sharing. Volte is a thing which is rarely or never used here in Turkey so i didn't have a chance to test it.
Hi.
I flashed this on my a6020a41 sd415. Device chagned name to a4020a36 and I had problem with network. Maybe because my device is single sim?
kolar666 said:
Hi.
I flashed this on my a6020a41 sd415. Device chagned name to a4020a36 and I had problem with network. Maybe because my device is single sim?
Click to expand...
Click to collapse
Device name change is normal. But network issue is strange... I didn't have that. Flash stock using qfil to revert, I'll look into it later.
Did you format the data before flashing? Seems i forgot to include that point in the OP. Silly me...
Sorry for that.
Have a nice weekend.
Thanks :fingers-crossed:
Anyway to do an TWRP-Backup? I dont have an pc now
Tks =D
Luelu said:
Anyway to do an TWRP-Backup? I dont have an pc now
Tks =D
Click to expand...
Click to collapse
Use External SD Card
Luelu said:
Anyway to do an TWRP-Backup? I dont have an pc now
Tks =D
Click to expand...
Click to collapse
What do you want to do with twrp? You can't even boot twrp with a locked bootloader.
Sent from my Lenovo Vibe K5 using XDA Labs
Bricked anphone using this method its a A6020a41 now when trying to flash something back on it it says sahara fail.(probably because of device model change what to do?)
Is it possible modify some files on stock a6020a41 file to continue flashing when it sees a6020l36?
JovanSijacki said:
Bricked anphone using this method its a A6020a41 now when trying to flash something back on it it says sahara fail.(probably because of device model change what to do?)
Is it possible modify some files on stock a6020a41 file to continue flashing when it sees a6020l36?
Click to expand...
Click to collapse
This rom doesn't have anything bootloader-related, so your sahara error is likely a driver issue. The model change is only seen in the system itself, but nothing on the hardware level is changed. So your a41 is still an a41.
There is a "back to stock" thread in the k5 plus forum, if you need to flash stock rom. Btw, that guide can be used to flash this vibeui port, the only difference is you need to change stock rom zip to vibeui port. The drivers part is important.
Sent from my Lenovo Vibe K5 using XDA Labs
Thanks for replying on this old thread i guessed that. I tried bunch of drivers and everything but will try different win machine soon so wish me.luck
JovanSijacki said:
Thanks for replying on this old thread i guessed that. I tried bunch of drivers and everything but will try different win machine soon so wish me.luck
Click to expand...
Click to collapse
Whether it's and old thread or new, doesn't matter, I'm always behind everything i do here
Forgot to say, you might need to disable driver signature check. Just open cmd as admin and type
Code:
bcdedit /set testsigning on
To revert;
Code:
bcdedit /set testsigning off
Sent from my Lenovo Vibe K5 using XDA Labs
eurodiesel said:
Whether it's and old thread or new, doesn't matter, I'm always behind everything i do here
Forgot to say, you might need to disable driver signature check. Just open cmd as admin and type To revert;
Click to expand...
Click to collapse
Yea did that, but had a couple installs and reinstalls so they maybe got confused and corupted who knows...i ll try in virtual machine or something like that.
JovanSijacki said:
Yea did that, but had a couple installs and reinstalls so they maybe got confused and corupted who knows...i ll try in virtual machine or something like that.
Click to expand...
Click to collapse
I would not use a vm if i was you. The risk is big if a connection suddenly drops.
In my AFH repo there are drivers which I'm able to confirm working.
There's also a tool that removes unused usb drivers from windows, can't remember it's name. Search for it.
It is possible that you might have a problem I've never experienced before,
Sent from my Lenovo Vibe K5 using XDA Labs
eurodiesel said:
I would not use a vm if i was you. The risk is big if a connection suddenly drops.
In my AFH repo there are drivers which I'm able to confirm working.
There's also a tool that removes unused usb drivers from windows, can't remember it's name. Search for it.
It is possible that you might have a problem I've never experienced before,
Sent from my Lenovo Vibe K5 using XDA Labs
Click to expand...
Click to collapse
Well uninstalled drivers with a tool and installed again.
Again i get download fail:saharafail sahara fail
Is there any way to force dload mode or edl mode because i cant see whats happening because my phone is dead(no vibration, no screen just red led i upper right corner) but it gets recognised as qualcom hs usb qdloader 9008 when i connect it.
Anyhow tried all versions of qfil and roms. Any more ideas?
JovanSijacki said:
Well uninstalled drivers with a tool and installed again.
Again i get download fail:saharafail sahara fail
Is there any way to force dload mode or edl mode because i cant see whats happening because my phone is dead(no vibration, no screen just red led i upper right corner) but it gets recognised as qualcom hs usb qdloader 9008 when i connect it.
Anyhow tried all versions of qfil and roms. Any more ideas?
Click to expand...
Click to collapse
What is your phone's SoC and what exactly did you flash on it? So that i can tell if its a hardbrick.
What windows are you running? I haven't got any probs on win7.
I assume you have tried the drivers i told you to use.
There is a program called Lenovo Moto Smart Assistant. It's foolproof, and installs any driver it needs (afaik). "Repair" your phone through there. Then start flashing roms afresh.
Sent from my Lenovo Vibe K5 using XDA Labs
EDIT: Fixed with unbricking service. No other way AFAIK. The error is caused by flashing to US998 20d from V300L 21k. Another user ran into the same error flashing from V300 21 to H930 20. So I guess the takeaway is to be careful when downgrading.
So I think I messed up and now my phone is stuck in UEFI crash (text screen with "LGE crash handler: UEFI crash"). It keeps bootlooping and I can't even turn it off.
QPST says it's in download mode when I plug it in.
Any chance I might be able to fix this?
Picture of the error screen attached
I think you need QFIL to find the emmc prog file, I also experienced the same problem.
sandking707 said:
I think you need QFIL to find the emmc prog file, I also experienced the same problem.
Click to expand...
Click to collapse
I've been messing with QPST but of course there isn't much I can do as-is.
I can use QPST by Port Qualcomm HS USB QDLoader 9008, but I do not have a .mbn file if you have a share file thanks
sandking707 said:
I can use QPST by Port Qualcomm HS USB QDLoader 9008, but I do not have a .mbn file if you have a share file thanks
Click to expand...
Click to collapse
it's a hard brick there is no solution for now (lg g5 .g6.v20.v30 ....) jus twait
im in the same situation on my v300s.:crying:
Read some other threads, there was a mention of a built in fastboot in the PBL but that seems to be untrue.
Maybe this isn't the PBL considering screen is working and there's LG branding.
I've also heard of a recent exploit for SD chipsets, something about the PBL's signature verification. If this works for the firehose, then maybe someone can modify an existing firehose to adapt for the V30, this way a leak won't be necessary. Though if anyone will bother is another matter.
seloka180 said:
it's a hard brick there is no solution for now (lg g5 .g6.v20.v30 ....) jus twait
im in the same situation on my v300s.:crying:
Click to expand...
Click to collapse
edit:
my device solved with jtag in repair shop.
Sent from my LGM-V300S using XDA Labs
So I still haven't managed to fix this, but did some reading. The phone isn't even in 9008 mode so remote repair probably isn't possible. It shows up as a LG AndroidNet device or something. It might be in 9006 mode except with LG's USB ID (1004:6340) and without an interface to the internal storage.
I tried using a tool to communicate in sahara mode but it's outdated so it can only connect to the device and not much else, the commands are mostly invalid. Interestingly when I tried to switch to download mode it requests a 1KB "AMSS" image.
Anyway I'll need a way to enter 9008 mode if I'm to get it repaired. If anyone know of a way I'd appreciate it if you share.
test point lg v30
Duo8 said:
So I still haven't managed to fix this, but did some reading. The phone isn't even in 9008 mode so remote repair probably isn't possible. It shows up as a LG AndroidNet device or something. It might be in 9006 mode except with LG's USB ID (1004:6340) and without an interface to the internal storage.
I tried using a tool to communicate in sahara mode but it's outdated so it can only connect to the device and not much else, the commands are mostly invalid. Interestingly when I tried to switch to download mode it requests a 1KB "AMSS" image.
Anyway I'll need a way to enter 9008 mode if I'm to get it repaired. If anyone know of a way I'd appreciate it if you share.
Click to expand...
Click to collapse
there are two golden points near the ribbion of battery but not the big ones under the ribbion wehen you connect both the phone will go 9008 mode
i am stuck in the very same situation as OP please if anyone has any way or idea on fixing this issues let us know and so others can benefit from it as well
thanks
Sahara mode LG v30, please help!
Hello there,
my lg v30 us998 was 10% battery. I was browsing the web and suddenly it freezed up. I cound´t do nothing until it shut down itself after a few minutes. I plugged in to the charger and the same message showed: UEFI crashed. Sahara mode... Any help please?
Not sure if it is actually possible for me. Still no solution. I was waiting for a more complete reply ...
I was able to successfully boot Liquid Remix on a US998 converted H933. However, my data was not working properly. So I tried the Guide the Canadian H933 compatibility with H930 ROMs guide in the forum. After the third step where
Step 3 - PARTITION DL US998 (Relevant)
Close LGUP and disconnect phone and restart
Reopen LGUP and reconnect phone
Select PARTITION DL
Load US998 KDZ
Start, Select All, Yes to partition changes window
When its done it will attempt to boot and you'll get flashes of an image, perform Master Reset
I ended up with my screen just flashing and I was not able to perform a Master Reset. The message header says LGE Crash Handler: UFEI Crash! picture attached.
Can anybody point me in the right direction?
Anyone?
hossein7292 said:
Anyone?
Click to expand...
Click to collapse
looks like you got a kind of "hard brick" according to:
https://github.com/openpst/sahara
It should be noted that devices that are hard bricked and in Sahara mode (Qualcomm USB PID 9008) and have secure boot enabled (pretty much EVERY production device) will only accept signed programmers. This means that it is not only device specific (i.e. MSM8x26,MSM8974,etc) but vendor specific as well (i.e. LG, HTC, etc) since OEMs generate their own private keys to sign all firmware images, including EDL images.
Click to expand...
Click to collapse
Must use firehose 8998 lg to fix.
I searched for 7 months Finally, end with the box 30usd.
zacharias.maladroit said:
looks like you got a kind of "hard brick" according to:
https://github.com/openpst/sahara
Click to expand...
Click to collapse
Thanks for the tip, I'll check it out.
sandking707 said:
Must use firehose 8998 lg to fix.
I searched for 7 months Finally, end with the box 30usd.
Click to expand...
Click to collapse
Do you know where to find the firehose 8998 lg files? Thank you in advance.
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8 and OP8Pro here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord.
You can also rollback your phone to a previous release of OOS with them if for some reason you would like to go back to an older firmware
You can download the following versions:
AC01AA tools (global firmware):
ANDROID 10:
OOS 10.5.2
OOS 10.5.3
OOS 10.5.4
OOS 10.5.5
OOS 10.5.7
OOS 10.5.8
OOS 10.5.9
OOS 10.5.10
OOS 10.5.11
Mirror for first and last MSMs: https://onepluscommunityserver.com/
AC01BA tools (european firmware):
ANDROID 10:
OOS 10.5.2
OOS 10.5.3
OOS 10.5.4
OOS 10.5.7
OOS 10.5.8
OOS 10.5.9
OOS 10.5.10
OOS 10.5.11
Mirror for first and last MSMs: https://onepluscommunityserver.com/
AC01DA tools (indian firmware):
ANDROID 10:
OOS 10.5.2
OOS 10.5.3
OOS 10.5.4
OOS 10.5.7
OOS 10.5.8
OOS 10.5.9
OOS 10.5.10
OOS 10.5.11
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Warning:
As this happened on OnePlus 8 and OnePlus 8 Pro Pro, it is advised to take backup of /persist partition before crossflashing (eg going from European to Indian build) as fingerprint reader may give an error related to enrollment issue. You can do so by using dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img (you must have root access, see https://forum.xda-developers.com/oneplus-nord/how-to/guide-how-to-root-oneplus-nord-t4139411 for that) and moving it to your computer/cloud.
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select O2 while using global tool or India while using indian tool or EU when using european tool.
Press Start button (this is done so that device will be "captured" automatically by tool instead of going back to normal boot after 10 seconds)
Power your device off.
Let it cool down for one minute.
Maintain volume up and volume down keys for at least 40 seconds to get into Qualcomm EDL mode.
Plug your device to your computer using stock OnePlus cable. (You may let volume keys go once done.)
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61, all credits to @Shadow12347 for finding it out.
Credits:
@Lord Ace for testing 10.5.2 Indian tool on his device.
OnePlus for the device and OS
Related: [OnePlus Nord][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
It worked for me,
After unlocking and locking bootloader and ended with corrupted device on locked bootloader
This method helped to solve it.
Thank You
Big thank you!
Thank you very much, just what I'm looking for
Thanks a lot
Good stuff man. Appreciate it!
Does anyone have a persist.img for Global firmware.
I have a different issue which I'd like to try resolve with persist.img
https://forum.xda-developers.com/oneplus-nord/help/nv-backup-warning-t4148599
Big thanks, fixed my semibricked Nord, time to try an GSI again
Small token for the help: Transaction ID: 5NF52401AU895305W
NisseGurra said:
Small token for the help: Transaction ID: 5NF52401AU895305W
Click to expand...
Click to collapse
Thanks for your donation, appreciate
@ Some_Random_Username
I have a NVBackupUI(thread here) error msg that refuses to go away.
I have used your guide to reflash OOS 10.5.2 but the error message is still there.
Do you by any chance have any idea on a way to resolve this?
norder said:
@ Some_Random_Username
I have a NVBackupUI(thread here) error msg that refuses to go away.
I have used your guide to reflash OOS 10.5.2 but the error message is still there.
Do you by any chance have any idea on a way to resolve this?
Click to expand...
Click to collapse
How you got this error..
And is this affecting your phone functionality?
cultofluna said:
How you got this error..
And is this affecting your phone functionality?
Click to expand...
Click to collapse
This is a brand new set and I first noticed it after I set up my phone. The usual data transfers, reinstalling apps etc. But now, it will not go away. Im thinking it's like that out of the box, just that I did not notice it earlier.
So far I have not had any issues functionality wise and my local OP support tells me to ignore it and a future update will fix it. They're not sure of the cause either and could not fix it.
This message keeps coming back even after multiple factory resets + a ROM reflash. I'm trying to rule out a hardware issue.
I did notice that this app is one of those that you remove when you debloat your OP set. I'm sure it would go away if I did that but if theres an underlying issue I might just be setting myself up for a catastrophic failure in future.
Hi, my friend really messed up with his phone. Phone currently have encrypted data partition. Problem is that msmtool doesn't detect phone at all, also device manager doesn't show it while its in msmtool. Anything he can do?
norder said:
This is a brand new set and I first noticed it after I set up my phone. The usual data transfers, reinstalling apps etc. But now, it will not go away. Im thinking it's like that out of the box, just that I did not notice it earlier.
So far I have not had any issues functionality wise and my local OP support tells me to ignore it and a future update will fix it. They're not sure of the cause either and could not fix it.
This message keeps coming back even after multiple factory resets + a ROM reflash. I'm trying to rule out a hardware issue.
I did notice that this app is one of those that you remove when you debloat your OP set. I'm sure it would go away if I did that but if theres an underlying issue I might just be setting myself up for a catastrophic failure in future.
Click to expand...
Click to collapse
norder said:
@ Some_Random_Username
I have a NVBackupUI(thread here) error msg that refuses to go away.
I have used your guide to reflash OOS 10.5.2 but the error message is still there.
Do you by any chance have any idea on a way to resolve this?
Click to expand...
Click to collapse
Unfortunately no idea, MSM tool in upgrade mode doesn't touch to NV items.
Either wait a new OOS build after 10.5.4 or RMA your device.
skayii said:
Hi, my friend really messed up with his phone. Phone currently have encrypted data partition. Problem is that msmtool doesn't detect phone at all, also device manager doesn't show it while its in msmtool. Anything he can do?
Click to expand...
Click to collapse
Make sure his device is off before trying to get in Qualcomm HS-USB 9008 mode, that was something we ran into during testing.
Also as a sidenote encryption state of the phone doesn't matter to use this tool.
Thanks a lot for the unbrick tool!
Some_Random_Username said:
Unfortunately no idea, MSM tool in upgrade mode doesn't touch to NV items.
Either wait a new OOS build after 10.5.4 or RMA your device.
Click to expand...
Click to collapse
Understood. Thank you
Works great thanks a lot for the links i had to install the driver and your post was well made to avoid me any hassles
By the way, it re-locks the bootloader
@ Some_Random_Username
can you tell me how you got this tool?
i could try getting the tool with oxygen os 10.55
thanks for this.
Hello everyone! I just found out my OTT Android TV from SDMC so if anyone have same device with me can you help me to get original firmware and probably custom rom? or maybe if anyone successfully rooted this device. thank you in advance.
I managed to unlock the bootloader but I can't go into mask mode & not detecting any devices in Amlogic Burn Tool
Try reboot update and then quickly plugging in usb cable. It should then be recognised by the burning tool.
kalehrl said:
Try reboot update and then quickly plugging in usb cable. It should then be recognised by the burning tool.
Click to expand...
Click to collapse
Same result, still not recognized by burning tool, but i have fastboot access
Maybe i need to change my M2M Cable?
Chicada said:
I managed to unlock the bootloader but I can't go into mask mode & not detecting any devices in Amlogic Burn Tool
Click to expand...
Click to collapse
what version Amlogic Burn Tool are you use ?
Refer to kalehrl's post below.
Normally yes, but oftentimes the operators disable the normal use of their device once the contract has expired and customers don't want to continue using the service. After a reset, you are greeted by a screen with the serial number of the device and you cannot proceed. So the only option is to flash the box with custom firmware loosing the widevine L1 and Google certification with Google chromecast in the process.
kalehrl said:
So the only option is to flash the box with custom firmware
Click to expand...
Click to collapse
I have deleted my opinion since you seem so sure about this. With such certitude, you couldn't possibly be wrong. Although you are.
kalehrl said:
Normally yes, but oftentimes the operators disable the normal use of their device once the contract has expired and customers don't want to continue using the service. After a reset, you are greeted by a screen with the serial number of the device and you cannot proceed. So the only option is to flash the box with custom firmware loosing the widevine L1 and Google certification with Google chromecast in the process.
Click to expand...
Click to collapse
I saw someone had success to connect the box with UBT , Thank you very much for your help and the tips!
nightbb said:
what version Amlogic Burn Tool are you use ?
Click to expand...
Click to collapse
V3.1.0