Hello dear gurus.
Purchased a Motorola (Lenovo) moto G6 smartphone on the Anroid 8.0 Oreo platform.
Performed OTA security updates.After that, it was suggested to upgrade to Anrdroid 9.0 Pie.Updated.
Next, I installed a custom recovery (TeamWin Recovery Project (TWRP)) on a new loader,and created a backup system for this recovery.
Next, I tried to fill in a new custom (Amateur) firmware (ViperOS), but TWRP refused to install this firmware.
So I tried about 10 different firmware versions,including official ones that were compatible with my Moto G6 device.
In the end, through trial and error, I turned a brand-new phone into a Hard Brick.
Currently, neither the recovery, nor the system,nor even the PBL,aboot, or SBL bootloader chain is running.
The only way the phone is detected (after installing specific drivers for my device and processor) in the system is Qualcomm HS-USB Qload 9008. That is, Emergency Download mode (EDL mode).
To convert the device to SoftBrick (9006) - a light brick.I need to restore the entire loader chain, starting with the SBL of the secondary loader.
There is a special BlankFlash_PPS29.26 utility for my device (see Attachment) that runs automatically when Blank_Flash is started.bat, re-marks MBR partitions, creates a partition table, and restores the entire chain of loaders.
But there is one significant "BUT", this utility completely refuses to ReWire the chain of device loaders, giving an I/o error in the logs (see Attachment).
After talking with smart people from the forward, I realized that for a successful firmware of my device, the OTA security update is not suitable,what is in the utility later, and what is newer and more secure on the device and the singleimage configuration file.the bin located in this utility is not suitable.
If there are people who can write the correct script for .bash for my firmware and security version and embed it all directly into singleimage.bin, then please respond.
Data for unbrick 1925-5 RU_ru.
This is archive for unbrick XT1925-5 on version Android 8.0 Oreo.
Someone, help me with the development blankflash on version Android 9.0 Pie.
reply
ZulC_Silence said:
This is archive for unbrick XT1925-5 on version Android 8.0 Oreo.
Someone, help me with the development blankflash on version Android 9.0 Pie.
Click to expand...
Click to collapse
rescue_and_smart_assistant_v5.2.0.10_signed_setup and nothing to add .
mickelek said:
rescue_and_smart_assistant_v5.2.0.10_signed_setup and nothing to add .
Click to expand...
Click to collapse
Please tell us in more detail how can I restore my smartphone via LMSA if I have rubbed all the bootloaders except the primary one (PBL) and in this utility it is absolutely not detected?
Related
I was running a MarshMallow update for the last 6 months and suddenly today morning I just decided to flash the "rootedsystemh960a.tot" from one of the forums here at XDA. First it did flashed the ROM using LGUP but then the Phone was stuck with LG LOGO for minutes and then I flashed it again with my stock UAE MM 6.0 ROM. It did work. Then I reflashed again hoping for the ROOTED ROM to work on my phone and ever since LGUP is giving me this error code with a message " lgup error code 0x2000 invalid command response" and it keeps crashing. Now I have tried to switch windows and tried to flash many ROMs and it wont stand a chance. Why this error message is coming? Can anyone of you experts figure this out? Even the COM ports are matching at LGUP and in my DEVICE MANAGER. Please help me. I am stuck with this mobile. ...:crying:
Little info about my phone. It is a UAE/DUBAI Variant of LG V10 - H960A, and officially I am not allowed to unlock my BOOTLOADER by the LGE itself. I had tried before bootloader unlock modes.. Anyways its not the point here right now.. The main thing is LGUP is crashing again and again.. Is there any other utility in place of LGUP for flashing LG ROMS ????
Well that .tot file was for Lollipop only that was your mistake in this probably and it has corrupted your system somehow. I'm afraid I have no idea how to deal with this phone as I don't modify this one myself because of the lack of development/devs.
I think there is something called LGFlashTool also.
dannejanne said:
Well that .tot file was for Lollipop only that was your mistake in this probably and it has corrupted your system somehow. I'm afraid I have no idea how to deal with this phone as I don't modify this one myself because of the lack of development/devs.
I think there is something called LGFlashTool also.
Click to expand...
Click to collapse
Even flashtool aint doing a job.. When I try to run Get device info from within the LG FlashTool, the application crashes...God! Cant they develop some stable running apps for their customers?
Hi,
can you enter the download mode on your V10? Then it might be possible to flash a clean (unrooted) MM via LG Bridge. Some time ago I tried to install the latest MM Version V20e on my V10 with LGUP. For some reason that failed and left me with a phone without ROM, too. Afterwards the V10 was not recognized by LGUP anymore.
Luckily I was still able to enter the download mode manually. So I connected the phone to my PC and started LG Bridge which still did recognize it as a V10 H960a. So selecting Firmware update and then clicking in the bottom right corner of the window on a link saying something like "repair flash errors" or "repair update errors" (I'm currently at work and cannot check) did a complete clean install of the latest firmware.
Maybe you're lucky and this works for you too.
cyvr1 said:
Hi,
can you enter the download mode on your V10? Then it might be possible to flash a clean (unrooted) MM via LG Bridge. Some time ago I tried to install the latest MM Version V20e on my V10 with LGUP. For some reason that failed and left me with a phone without ROM, too. Afterwards the V10 was not recognized by LGUP anymore.
Luckily I was still able to enter the download mode manually. So I connected the phone to my PC and started LG Bridge which still did recognize it as a V10 H960a. So selecting Firmware update and then clicking in the bottom right corner of the window on a link saying something like "repair flash errors" or "repair update errors" (I'm currently at work and cannot check) did a complete clean install of the latest firmware.
Maybe you're lucky and this works for you too.
Click to expand...
Click to collapse
Well hello, I found the solution for my problem and I was able to flash the ROM successfully. Its some kind of new utility amalagamated with LGUP and it does flash without any problems. Found out it was related to some corrupt dll file or incompatible file I had in my LGUP library for the ROM FLASHING to fail all the time... You just read this first post on this link and you will be all fine. Trust me ...:highfive::good::fingers-crossed::fingers-crossed:
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
Just dont forget to follow the rules exactly as mentioned and if you can run it in the Virtual Machine I would prefer you to do that but you have to do everything like installing LG DRIVERS + LGUP + LGUP DLL FILE + UPPERCUT as mentioned in this post. Because if you are running antivirus on your PC, it will detect this UPPERCUT TOOL as some trojan horse or some kind of malware. I did that in my VM as I already had my VM configured for my LG V10 Flashing process.
Do it and do let me know should you encounter any problem. May be I can help later on.
Hey guys. I've been in touch with Motorola about my bricked Moto G6, and they seem way too incompetent to simply provide me with a blank-flash file for my device. Allow me to begin by copy pasting the paragraph i typed to Motorola.
"Hi. I am in search of the Blank-flash file for the Moto G6 XT1925-6. Lenovo seems to be very bad at understanding what the blank-flash file actually is which is sad when you take into consideration that they developed the software for the device. Again, to clarify, it is the BLANK FLASH file for the device, not the ROM. I am not attempting to unlock the boot-loader as it has already been unlocked (motorola seems to think this is what i want to do as well and are refusing to support me in unlocking the boot-loader). I repeat, I am in search of the B L A N K F L A S H file for the moto G6 XT1925-6. If somebody out there could either extracty theirs from their device and send it over, or better yet, one of the bright minds over at Motorola who designed the device could graciously bless me with a small piece of their software so I can enjoy their phone again, that would be great. Please do respond as soon as possible. I have provided a blank-flash file as example so you don't get too confused, as well as the blank-flash folder I am using which will actually contain logs about the attempted flash of the blank flash file. I attempted to use the blank-flash file from Android PIE, as you can see it is labeled PPS and not OPS.
AGAIN, since this seems to be so difficult for motorola to understand, it is the blankflash file i am in search of, not the method to unlocking the boot-loader. Thank you."
The device is being detected in Windows 10 as a Qualcomm device which suggests it is still possible to flash it with a blank-flash file in order to reach fast-boot and re-flash the stock firmware.
NOPE see below
I have been searching for this little piece of software for over a week only to fine the blank-flash files for the G6 PLUS and PLAY versions, not just the mid-range G6 model. Below, as promised to be included, is the blankflash file i was attempting to use which does contain logs of the attempted flash. For ease's sake i have also provided a link to just the logs so you don't have to extract the rar.
Logs: NOPE see below
Blankflash file attempted to use: NOPE see below
Thank you for taking the time out of your day to search for this file. I'd love to start actually using the Moto g6 again rather than using it as a paperweight and relying on my Samsung J3 Orbit as a main driver. Sad.
EDIT: even SADDER, I have been prevented from providing crucial informational links aiding in resolving the issue due to XDA policy. If you would like these links, you're going to have to obtain them from me elsewhere (unless i circumvent the policy and post them in a broken link like suuuuch.)
https ://pastebin.com/QE6UBZq6
I also need a blank flash file for moto G6. we can find the flash file of G6 play and plus but not mid-range Moto G6. It's not fair My phone was dead after OTA update and now it is a totally useless piece of ****. If we get that small blank flash file then we may bring our devices back to life. Please help us.:crying::crying:
error blankflash
Hi guys, have you solved it?
running the file I get this error: sahara download()-io error
dibarbosaa said:
Hi guys, have you solved it?
running the file I get this error: Sahara download()-io error
Click to expand...
Click to collapse
No, still searching for a solution and yes the existing blank flash file gives us that error. So we need to wait for another working one.:crying:
Приветсвую привратники здравого смысла!
Hello dear happy owners of Moto G6 bricks.
Please, would you be so kind as to accept me into your team of elite owners of useless nutcrackers based on the Motorola Moto G6.
My XT1925-5 device was also hardbricked, after upgrading to Android 9.0 Pie and installing the latest security updates.
Also, when trying to flash the blankflash_PPS29.26 utility.bat receive
error: Sahara Download IO Error.
Email me if there are any positive results when getting a smartphone memory dump and creating a new blankflash for the latest OTA.
This is my contact email ([email protected]) if there are people willing to collaborate to write a new Blank Flash together.
I have to admit, when I joined XDA not long ago, I thought my easily bricked Moto G6 Play (Jeter) was a special case or that I was uniquely special when it comes to comatosing devices. Now, a few months and several more limping devices later, I see there truly is a seemingly growing mass of useless Motorola Moto owners out there. Whats worse is the Lenovo/Motorola Rescue Assistant wont rescue me because the Baseband and IMEI are erased on my device. Guess its time to take the next big step...invest in another G6 and see how long it is before I tater that one too!
Any news here, guys?
So I searched on internet to find any solution of the problem i am facing and i couldn't find one. I had a rooted LG G5 (RS988) with the nougat version RS98821c, or at least that's what LG UP is detecting now. I decided to do a factory reset (first mistake). The phone started looping by rebooting into my TWRP recovery, So I wiped data and cache, and then tried flashing the KDZ file RS98811c (It's the only thing available for my device on LG's website) via LGUP. But after booting into firmware update (second mistake ) the LG UP tool won't allow me flashing RS98811c no matter what option i choose. The firmware on LG website is MArshmallow and I had Nougat so i guess that's that. Now there are other 3 files, i tried 2 of them RS98810h and RS98810d, same problem. Tried flashing recovery via fastboot too but it won't boot into recovery anymore. Now my device can only go into fastboot or Firmware update. So what are my options now? Is my device truly ****ed? coz i don't have warranty now and i am no more in US now (The device is from US).
akshay.shah said:
So I searched on internet to find any solution of the problem i am facing and i couldn't find one. I had a rooted LG G5 (RS988) with the nougat version RS98821c, or at least that's what LG UP is detecting now. I decided to do a factory reset (first mistake). The phone started looping by rebooting into my TWRP recovery, So I wiped data and cache, and then tried flashing the KDZ file RS98811c (It's the only thing available for my device on LG's website) via LGUP. But after booting into firmware update (second mistake ) the LG UP tool won't allow me flashing RS98811c no matter what option i choose. The firmware on LG website is MArshmallow and I had Nougat so i guess that's that. Now there are other 3 files, i tried 2 of them RS98810h and RS98810d, same problem. Tried flashing recovery via fastboot too but it won't boot into recovery anymore. Now my device can only go into fastboot or Firmware update. So what are my options now? Is my device truly ****ed? coz i don't have warranty now and i am no more in US now (The device is from US).
Click to expand...
Click to collapse
Update : I forgot to mention, I tried LG Bridge (it doesn't recognize my device) I tried LG support tool(it needs MTP enabled i suppose, since my device won't boot it isn't possible), it does recognize the device but says i am on the latest firmware for my product.
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.
Hi, is there a possible way to flash with Huawei Smartphone Multi Download?
When I reboot to edl, the drivers are working fine (I unlocked the bootloader this way). When I open the app, load in the flash file and click Scan&Download, the phone isn't being detected. I tried huawei, mediatek and qualcomm edl drivers, but I still can't get the phone to show up.
The only way for the phone to actually show up is to boot into fastboot, but you can't flash every partition with that. It just says fastboot download fail.
So is there a way to get this program to work with the phone?
UPDATE
I used IDT and it worked.
If someone wants the firmware file, it's here.
WARNING! That is some kind of testing firmware. Look up how to update a huaewi phone manually to get regular firmware.
Sucharek 233 said:
That is some kind of testing firmware
Click to expand...
Click to collapse
that is the official Huawei board software.