[OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS - OnePlus Nord Guides, News, & Discussion

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.

Related

[Guide] [A2017(G)] - Unlock, TWRP, Flash with Toolkit

About
Hi there,
I created this guide not so much as a substitute for the other guides or because this would be the best way to do it.
When I looked into rooting my new Axon 7 (international) I studied all the other guides first, but then did it very differently, mainly
because
- I am on Win 7 32-bit and some of the tools used in the other guides don't work for that
- since the other guides were created the Axon7Toolkit came along - that simplified a lot of steps.
The guide is actually very similar to this one for the 2017U:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Only now with the toolkit it pretty much works for the 2017G as well without the need for tenfar's TWRP (see comments). In case I left out anything, this guide will be of help, too.
So this guide is for you if
- You want to root or flash a custom rom and don't mind unlocking the bootloader OR
- You are on Win32 and cannot use the axon7tool command line tool OR
- You want to use the Axon 7 Toolkit for the job to keep things simple
Please read all the notes below before attempting anything...
Disclaimer
- This worked well for me - no claims it does for anyone else. For the record: I was on Stock 6.0 MM B08 A2017G, no fingerprint/lock etc and went straight to RR.
- Use at your own risk, if you are unsure what you are doing stay stock - I'm not responsible for bricked devices, dead SD cards, Donald Trump, or you getting fired because the alarm app failed...
Regarding Drivers
- Qualcomm ones for MiFlash (link below)
- QUSB_BULK if going with eg the axon7tool commandline version (edl mode)
- You can use the Toolkit to install (some of) the needed drivers
- ZTE drivers - phone is set up to install them upon connect to the PC. Don't.
- Uninstall incorrect drivers, just installing the correct ones won't necessarily do the trick.
MiFlash
- right click & 'run as admin' (flashing didn't work for me without this)
- Correct driver: Qualcomm HS-USB QDLoader 9008 when in edl (check with device manager open)
Boot modes
- power phone down and boot into
- EDL by holding Volume UP/DOWN & POWER simultaneously
- recovery/TWRP (once installed) by holding Volume UP & POWER simultaneously
- fastboot: Not enabled in A2017G Stock
Windows
- 32-bit: MiFlash needed, commandline axon7tool not working
- The toolkit seems to run on Mac/Linux using a Windows emulator/virtual machine (not tested, Wine helps I guess)
TWRP
- versions: Signed tenfar TWRP 3.0.2 that is used in a lot of other guides is buggy and can do a lot of harm - not needed if you unlock
the bootloader first. You can (and should) use the latest official TWRP version.
- dm-verity: https://twrp.me/devices/zteaxon7.html
- USB OTG: Axon 7 supports this, so does TWRP - no need for SD cards. Simply use a thumbdrive with a OTG cable (with included Adapter if needed), boot into TWRP (thumbdrive needs to be connected beforehand) and click 'Mount' in TWRP, then select USB storage
Bootloader
- Afaik DO NOT lock again with custom rom installed or rooted (brick)
Root/Unlock
- Can create problems with Android Pay, playstore etc - see https://www.xda-developers.com/tag/safetynet/
- Root disabled by default in Lineage, needs flashing Magisk or SU - see other guides
- Some features root provides on Android 6.0 MM won't work in Nougat (so far anyway, eg xposed)
Links
- Axon7Toolkit: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
- TWRP: https://twrp.me/devices/zteaxon7.html
- Zadig (if needed): http://zadig.akeo.ie/
- Qualcomm driver: https://build.nethunter.com/misc/axon7/Qualcomm_QUSB_BULK_Drivers.zip (link from https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514)
- Lineage Os thread: https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679
- Modem & bootloader from Lineage Os thread: https://www.androidfilehost.com/?w=files&flid=148464
- OpenGApps: http://opengapps.org/?arch=arm64&api=7.1 (arm64 version for OS version to flash, e.g. 7.1 Nougat)
Thanks
bkores (for the tool), dnlilas (help in the forum), DrakenFX, Unjustified Dev, Controllerboy & all the guide/rom creators etc in this forum. (And the poor souls who came first and discovered all the ways not to do it, preventing my fall)
1) Prep
- Note down IMEI(s) from your settings/about phone/status/... just in case
- Unlock developer options (Phone settings > "About Phone" > Click "Build Number" 7 times...)
- Check "Allow OEM unlock" and "USB Debugging" there
- Connect your Axon 7 to your PC with the original USB cable - do not disconnect with MiFlash/Toolkit running.
- Open device manager to check your drivers (will show up differently depending on the boot mode)
- Run Axon7Toolkit
- Select Option 1 - Install/Test Drivers
2) Unlock
- This will RESET your device, did you save your data? (using Toolkit etc)
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
- The unlock files the Axon7Toolkit offers are in a folder 'A2017U_FASTBOOT_UNLOCK_EDL' - works for A2017G
(- Axon7Toolkit preview version offers different folder content to flash - have not checked that)
- One can restart MiFlash (e.g. to 'run as Admin') anytime and try again, but after the flash was succesful, do not disconnect the phone but
- Finish off with the Toolkit 'press a key to continue' (or one will have only fastboot enabled)
- A message will appear on the phone: Confirm that you want to unlock the bootloader (using volume & power buttons to navigate)
- Done. From now on you will get an annoying message on booting the phone about your device being unlocked. Just ignore and wait for a re-boot...
3) TWRP
- Unlock developer options - AGAIN etc as device was reset. And - again - enable debugging...
- In the toolkit (main screen) go to '11 Advanced Options', select <Flash boot/bootloader/modem/recovery<choose recovery partition
- In 'Open' dialog select C:\Axon7Development\Axon7Toolkit\twrp\twrp-3.1.0-ailsa_ii.img (or newer version)
- Flash as 'recovery'
- Reboot, check system boots up fine
4) Flash Custom Rom etc.
- Generally: Follow instructions provided with the custom rom you are going to flash (as they might differ)
- Boot into recovery/TWRP (Volume UP + Power after shutdown)
- No need to swipe to 'Allow system modification' - this can actually brick things...see https://forum.xda-developers.com/axon-7/help/a2017u-stuck-zte-screen-boot-factory-t3584062
- Mount/Select storage (for OTG USB)
- Backup boot, recovery, data(if needed), HLOS, System image or System (image was recommended but that did not work in my case, so I backed up system)
- Wipe/Format
- ***If you like to avoid your data partition to be encrypted, follow that thread: ( format your data partition to ext4 instead of f2fs (wipe -> advanced)????)
- Install Bootloader & then modem (or Nougat won't install if coming from MM) - A2017X_B15_Universal_Bootloader.zip & A2017G_N_Modem.zip
- Rom & Magisk/SuperSU
- GAPPS (version)
- Re-boot: Unlocked message, long first time boot - After RR, my phone show up as 2017U... well, who cares...
Any comments to correct errors in this guide or fill out any blanks are highly appreciated...
I dunno why now one has thanked this yet, it is a well written guide imo and useful for those not yet unlocked.
THANKS SOO MUCH FOR THIS!! The timing could not have been any better. I literally just bought this phone from a guy on craigslist for $270 (Couldn't pass that up coming from an LG G4) less than a hour ago. Quick question. It's a 2017u with build B25. Will the toolkit work with it. I don't see an option for this build
Hi Senny,
thanks a lot - I hope the guide is helpful, as mentioned it worked for me. Hopefully I included at least most of the pitfalls one could encounter...
Hi raphi809,
The toolkit should work fine with the 2017U (it should detect your version).
To be sure, also have a look at the toolkit thread (https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108) and the thread linked above (https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128), as it is more specific for the 2017U.
The main thing I am not 100% sure with the 2017U is (as I am on a 2017G and started from Android 6.0 MM), if you have to downgrade from Nougat/certain versions before unlocking etc.
If someone could shed some light on this, that would be great!
Whoooo? said:
About
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
Click to expand...
Click to collapse
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?
Volumetrik said:
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?
Click to expand...
Click to collapse
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps
Whoooo? said:
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps
Click to expand...
Click to collapse
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi there,
Obviously I have not tried this myself, so I only can refer to these two posts from the Toolkit thread:
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71673370#post71673370
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71861250#post71861250
...stating that 'Bootloader mode is disabled in G variant with Nougat update' and one has to either
- revert to MM or
- flash a different Unlock package with MiFlash (linked in the second post)
(There is also a note in the instructions saying that the toolkit's Bootloader unlock with MiFlashdoes not work on A2017U B25)
marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi Marcus,
I tried to find some time to reply and explain how I used this guide and two others to get my device unlocked, twrp'ed and LineageOS. It's running like a charm.
I started with a A2017G device basis with MM B03. My device was updated to the latest official update available via MyFavor network. I didn't try to update OTA.
I Used Axon7ToolKit v1.1.1 + Update_Install.bat / Qualcomm Drivers / A2017U_Bootloader_EDL. I worked under windows x64, because I experienced too many troubles to get Axon7toolkit working properly under 32bits. The only one differences I experienced and not written in the threads:
- I saw a FTM mode (Factory Test Mode) displayed in a white square centered on the device screen after unlocking bootloader. In my memory, it disappeared after TWRP flash.
- I got a problem with Flashlight, didn't work, associated with a problem to call (sms working). I flashed the modem firmware once again, it solved the problem after reboot.
- At the end, LineageOS installed, LineageOS updater strangely saw the same update version installed on the device. The only difference was the"signed" at the end of the update name I launched the update and installed it succesfully, without issue. No more update after that (until a new one of course)
Hope this will help someones
Volumetrik said:
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:
Click to expand...
Click to collapse
Hi, when are you planning to release your complete guide? This would really help me.
I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...
Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?
still_living said:
Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?
Click to expand...
Click to collapse
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).
Apocalypse12345 said:
I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...
Click to expand...
Click to collapse
Hi there,
I think (memory blanks setting in) that's the error I got when MiFlash was not running as admin.
Whoooo? said:
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).
Click to expand...
Click to collapse
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
still_living said:
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).
Click to expand...
Click to collapse
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
Only stock recovery for me. No twrp unfortunately. Really want to change from miflavour
djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
HURRAY! ! !
Well no it didn't work until today I tried the option to restore from bricked device to b10. Out took me to miflash and asked me to unlock bootloader? Dunno why, it's already unlocked, anyway , after that was successful I went back to the option page of the toolkit and selected 'install twrp', and this time it flashed! It didn't stop on the 'failed to flash twrp' message but still gave me a 'flash to boot into twrp' then I followed your advise to go to twrp directly from there and it had installed. I'm so happy thanks loads dude. :laugh:
Worked like a charm! Thanks for posting the guide
Edit: Went from locked Nougat to Unlocked Lineage.
Whole process took me about 2 hours, but if you are better at following the steps than me you'll probably be able to do it in 1 hour.

Ask anything here! Don't be shy [ROOTING, BRICKED, ROM'S, DEVELOPMENT, OTHER]

SORRY WAS INACTIVE FOR SOMETIME... NOW IM BACK YOU CAN ASK AGAIN...
ALL CHIPSETS UNBRICKING METHOD HAS BEEN POSTED
Hi you may ask me anything related to android and I promise to answer within 24 hours and m reply will definitely work for you.
*****************************************************
SPECIALIST IN ROOTING, DEVELOPMENT, HACKING, SECURITY BYPASS, RECOVERY, FLASHING, CUSTOM ROM'S
*****************************************************
SEE YOU SOON
*****************************************************
•NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE•
LG Aristo v10g Metropcs
How do i start configuring this phone without a google account?
A friend who was using it gave me this phone but forgot the boot password and the google account was not of him. So, now, we can´t use the phone.
Mephis96 said:
How do i start configuring this phone without a google account?
A friend who was using it gave me this phone but forgot the boot password and the google account was not of him. So, now, we can´t use the phone.
Click to expand...
Click to collapse
You mean to say that the phone is in frp mode?
(Factory reset protection)
Yes
FRP..... thanks, id did not know what it means.
Yes, it is in FRP
Mephis96 said:
FRP..... thanks, id did not know what it means.
Yes, it is in FRP
Click to expand...
Click to collapse
Can you please tell me the phone model and it's info.
LG Aristo v10g from Metropcs
x.ak**** said:
Can you please tell me the phone model and it's info.
Click to expand...
Click to collapse
Ita LGMS210 v10g.
What's more do you want me to send? I dont know which information do you need?
[PC] HOW TO CURE A BRICKED M-TEK DEVICE!!
///////////////////////////////////////////////////////////////////////////////////////////
• Download and Install the Android USB drivers for your device that I have mentioned below.
• Power Off your device and remove the battery (only if it's removable)
• Download the stock ROM or the Custom ROM on your PC that you want to flash. (GIVEN BELOW)
• Download and extract SPFT (Smart Phone Flash Tool) on your PC, you will be able to see the files shown in the picture below. (Pic 1.1)
• Open Flash tool.exe (Pic 1.2)
• Once SPFT is launched tap on Download tab. (Pic 1.3)
• In download tab click on Scatter-Loading button. (Pic 1.4)
• Now locate the Scatter File that you will find in the Stock ROM folder that you downloaded in step 3. (Pic 1.5)
• Click on Download button to start the flashing process.(Pic 1.6)
• After finishing a success message will appear. (Pic 1.7)
///////////////////////////////////////////////////////////////////////////////////////////
Downloads:-
https://androiddatahost.com/b9cyw (DRIVERS)
https://spflashtool.com/download/SP_Flash_Tool_v5.1744_Win.zip (SPFT)
https://www.needrom.com/download/lenovo-s850/ (ROM FOR LENOVO S850, REGISTRATION NEEDED ON WEBSITE TO DOWNLOAD THE ROM)
///////////////////////////////////////////////////////////////////////////////////////////
Mephis96 said:
Ita LGMS210 v10g.
What's more do you want me to send? I dont know which information do you need?
Click to expand...
Click to collapse
I was working on another project that you can see below give me 1 hour I'll get back to you ASAP.
Best tool like SetCPU for controlling CPU with profiles?
SetCPU doesn't allow core control though
Mephis96 said:
Ita LGMS210 v10g.
What's more do you want me to send? I dont know which information do you need?
Click to expand...
Click to collapse
How to BYPASS FRP LOCK!
Test conducted on Virtual Machine on my PC
****************************************************************
I am not responsible for any damage you may cause to your device!
****************************************************************
****************************************************************
Never wanted to upload it but did it because I aim at helping people.
****************************************************************
Google FRP (factory reset protection) is aimed at making a stolen phone less valuable.
We usually keep our phones locked with a password or pattern but once its stolen it is easy to erase the data (via Hard Reset) and reuse the phone. With Google FRP in place, whenever the phone is formatted using hardware keys it will ask for the last synced google account details before proceeding further.
///////////////////////////////////////////////////////////////////////////////////////////
Until now, everytime some sort of hack comes out to bypass this screen and then its patched with a security update very soon. Same is the case with LG Aristo. There is a working solution as of now but it may not last long. Let’s see how to get this working –
///////////////////////////////////////////////////////////////////////////////////////////
How to Bypass LG Aristo Google Account –
This process is lengthy, but it’s a sure shot method and works every time.
We need 2 apps to complete this bypass process. They are Shortcut Master Lite and Sidebar Lite. Download the zip file from below link.
DOWNLOAD
>Extract the zip file and transfer the apk files to a micro sd card. Install the SD card in your LG Aristo before proceeding further.
///////////////////////////////////////////////////////////////////////////////////////////
Mephis96 said:
Ita LGMS210 v10g.
What's more do you want me to send? I dont know which information do you need?
Click to expand...
Click to collapse
Done
Drop a like on all my replies so I can stay encouraged and help you further.

			
				
YeshYyyK said:
Best tool like SetCPU for controlling CPU with profiles?
SetCPU doesn't allow core control though
Click to expand...
Click to collapse
You may use Kernel Manager it's super useful and will do what you're asking for!
Hi ! Could you help me with my problem ?? https://forum.xda-developers.com/search.php?searchid=446201503
No one seems to be able to help me... thanks a lot!!!!
antoflos said:
Hi ! Could you help me with my problem ?? https://forum.xda-developers.com/search.php?searchid=446201503
No one seems to be able to help me... thanks a lot!!!!
Click to expand...
Click to collapse
I will definitely help you just give me one hour but can you post the following info:
Model Number:
Exact Problem:
How that problem occured:
Model Number: SM-G935F / Galaxy S7 edge
Exact Problem : I can't go back to the dock ROM
How that problem occured : Last week, I wanted to try to change my phone a SM-G935F on a custom rom " Minotaurus Oreo V10". I did it successfuly but didn't like it so much so I decided to go back to stock Rom.
I used Odin and a stock ROM for that but I think I made a big mistake by not wiping with TWRP before flashing with Odin.
It resulted that my phone was stocked on the S7 edge logo. Luckly I can go on download mode so it's not hard bricked but Odin failed on every flash I've tried. It stoped at the step "config.msi"
To flash I used this dock Rom : SM-G935F_1_20161201150115_pbdym44h2s_fac
x.ak**** said:
I will definitely help you just give me one hour but can you post the following info:
Model Number:
Exact Problem:
How that problem occured:
Click to expand...
Click to collapse
Hey man this quite difficult and i need to install this phone's firmware on my VIRTUAL Machine, basically I request you to wait for the time being so I can save your phone.
Drop a like on all my comments above to encourage me.
Huawei P10+ Firmware on Huawei P10 - by accident
Hi:
On my P10, I used Firmwarefinder for Huawei to find the firmware (Oreo with EMUI 8) and after verifying, I downloaded and upgraded the P10 to new firmware. After reboot, the dpi is seemed changed (as picture attached) and when I went to check it on about phone, it says Model is VKY (which is Huawei P10+) - picture attached.
Is there a way to rollback and install the correct firmware on this phone somehow?
antoflos said:
Model Number: SM-G935F / Galaxy S7 edge
Exact Problem : I can't go back to the dock ROM
How that problem occured : Last week, I wanted to try to change my phone a SM-G935F on a custom rom " Minotaurus Oreo V10". I did it successfuly but didn't like it so much so I decided to go back to stock Rom.
I used Odin and a stock ROM for that but I think I made a big mistake by not wiping with TWRP before flashing with Odin.
Click to expand...
Click to collapse
***********************************************************************************
I AM NOT RESPONSIBLE FOR ANY FURTHER DAMAGE THAT MAY BE CAUSED TO YOUR DEVICE...(UNLIKELY TO HAPPEN)
***********************************************************************************
For being able to make the downgrade operation you will have to use a Windows based computer on which you will then install Odin (an official program developed by Samsung and used on update types of operations).
***********************************************************************************
Download Odin on your computer; afterwards install the program by following on screen prompts.
The Samsung Galaxy S7 Edge USB drivers must be installed on your PC too – use Samsung KIES in that respect.
Download the stock / official Android OS for your S7 Edge – from SamMobile or from Samsung’s official website.
Power off your device and reboot into download mode: press and hold the Power, Volume Down and Home buttons for a few moments; then connect your phone with your computer with the help of the USB cable.
After making sure that Odin has recognized your device (the “added” message must be displayed and the ID:COM field should be turned yellow or blue) from the program select the PA option.
Load the firmware file; don’t select the Re Partition and Auto Reboot options; click on Start when done.
Wait while your SGS7 Edge is being updated; when done, remove the USB cord and reboot your phone.
For further info related to the update process reply to my thread
LIKE ALL MY COMMENTS TO ENCOURAGE ME TO HELP YOU.
xironimoh said:
Hi:
On my P10, I used Firmwarefinder for Huawei to find the firmware (Oreo with EMUI 8) and after verifying, I downloaded and upgraded the P10 to new firmware. After reboot, the dpi is seemed changed (as picture attached) and when I went to check it on about phone, it says Model is VKY (which is Huawei P10+) - picture attached.
Is there a way to rollback and install the correct firmware on this phone somehow?
Click to expand...
Click to collapse
No pictures attached!! and yes you can roll back to the stock ROM or even customize the DPI according to your phone [ROOT REQUIRED]
Let me know which one you prefer?
Also like all my comments above to encourage me to help you even faster.

[ROM] [PORT] [QFIL] [A6020a41] MM VibeUI For Locked Bootloaders

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

Feedback after unlocking / flashing India ROM on sealed China ROM K20 Pro (8/256)

Hi guys,
Hope it's ok if I start this thread, I just wanted to give new users some feedback before/ after unlocking and flashing an India ROM on my sealed China ROM K20 Pro (8/256). It might be useful to some, or maybe even help others. Thanks a lot to Robbo.5000, Madsponge and Hursty UK (hope I got it right?) among others for their help and advice.
- [BUYING PROCESS] My trip with the K20 Pro started here: https://forum.xda-developers.com/k2...ice-to-buy-t3939616/post79918346#post79918346 (about 18 days to get it from China during high season, not too bad I guess). (FYI, the real Global version will come out in Europe in a few weeks but the 8/256 won't be available here.)
- [UNLOCKING PROCESS] I then started the "infamous" unlocking process which triggered the even more "infamous" unlocking wait time. Why did Xiaomi choose to do that? Pretty strange if you ask me. Why should you wait 5 days or more? Anyways, in my case it was almost 6 days. That part of the process went smoothly (I run a kinda old Windows 7 PC). I rebooted the phone and it was unlocked indeed. Then started the stressful process: flashing a +400 euros phone without knowing if it would actually work. Kinda reminded of the time when we "backuped" PS1 (PSX) games, haha.
- [FLASHING PROCESS] I used the official MiFlash tool, with the official India ROM (fastboot file, .TGZ extension). First problem : MiFlash couldn't install the drivers because a /log/ folder was missing, which I had to create manually (didn't see that mentioned on the forum, but might be my OS? Oh well). The rest was OK until I launched the flashing process and hit the "clean all" button (I carefully didn't choose the clean all and lock which would have bricked the phone).
>> Link to the official India ROM Fastboot .TGZ -> http://bigota.d.miui.com/V10.3.3.0....FKINXM_20190711.0000.00_9.0_in_a1c0a15dec.tgz
>> Link to the official MiFlash tool I used -> https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
>> Use the official Xiaomi USB-C cable - do not try another USB cable
>> Important reminder: please change the default option in the flashing tool and DO NOT choose "clean all and lock". Change it to "clean all" only (you don't want to lock it as you might brick it - see posts below about this)
- [STRESSFUL REBOOT] The flashing process ran for about 10 minutes, said "error: Not catch checkpoint (\$fastboot -s .*lock)". Needless to say I was very stressed out at that point, especially with the not cool red message "error" on the right of the tool, in the column "result". I thought the phone was bricked...but no, it just rebooted normally with the India ROM on it. Honestly I don't know what happened, if it was normal or something but I didn't see anyone mentioning this.
Some feedback post flash: everything is fine, the phone seems even faster than on China ROM but it might be just an impression. I do not like the POCO launcher at all, when you're used for 4 years with the classic MIUI launcher it's honestly a pain, I like to see all installed apps on the home and next screens. I had an issue with my Mi Cloud backup (home screen): Mi Cloud said there was no backup even though I did one just before flashing. The rest of the sync process (except home screen - maybe because of POCO launcher?) was fine though: pics, notes, calls, messages, etc. Too bad we're missing NFC but it feels good to be back on "Global" (was coming from a Mi 8 Global phone). Oh yeah, missing the multiple shots option from the China ROM (where you can choose the "best" shot), but it will come to Global one day I guess.
- [MI CLOUD BACKUPS] I can confirm the Mi Cloud home screen backup issue described above is indeed because of the POCO launcher: my previous backups didn't have it (Mi 8 Global, K20 Pro China) and so Mi Cloud couldn't restore from those backups. I now have a POCO launcher backup (daily in Mi Cloud) and I can restore from those. So keep that in mind: if you come from non POCO you won't be able to restore home screen, but same thing if you move from POCO to a non POCO launcher. If you're not familiar with those backups, it's very practical (usually...) when you change phone because you just have to restore it and you'll have all your icons, apps and stuff like before.
[UPDATE] As you might know, a European Global version will be released in a few weeks, let's see if it has the POCO launcher or not.
Thanks again all for the help and let me know if you have more feedback.
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
hippo2s said:
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
Click to expand...
Click to collapse
You need to fully unpack the ROM. It requires unzipping twice. You now need to extract everything from the tar file. After extracting the tar file you should have a folder with all the ROM image files and some .bat files. Point the Mi Flash Tool to this folder.
The phone needs to be booted into fastboot mode. The PC should recognise the phone automatically if it has all the correct drivers installed.
ive been using the indian rom for like 2-3 weeks now, my question is, does it support auto updater trough the updater? or we need to install back trough the mi flash tool
i failed multiple times to flash the global india rom before(using winzip to extract). and I tried again extract the files using winrar and it succeed. i'ved been using it almost 2 weeks now. the issue that i am facing is i cant use earphone mic on discord and whatsapp call. the rest is fine. for the updates, i get it from system app updater in settings.
OK - Managed to get the image folder recognised - the file path was too long - so i renamed it and moved it closer to where the miflash .exe was.
Now MiFlash is not detecting my device - when plugging in phone windows comes up with a 'USB device not recognised' message as well.
In Device Manager it says Unknown USB device (Invalid Configuration Descriptor) - I looked for Xiaomi usb drivers but Windows say i already have the best driver installed...
Any ideas?
hippo2s said:
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
Click to expand...
Click to collapse
I forgot to mention it, yes you do have to extract it (using WinRAR or similar) until you get an actual folder like Robbo.5000 said. I then renamed the rom's parent folder as "raphaelin" because another user mentioned we could have issues if the folder's name was too long.
About the USB connection i didnt change anything, i left it by default.
hippo2s said:
OK - Managed to get the image folder recognised - the file path was too long - so i renamed it and moved it closer to where the miflash .exe was.
Now MiFlash is not detecting my device - when plugging in phone windows comes up with a 'USB device not recognised' message as well.
In Device Manager it says Unknown USB device (Invalid Configuration Descriptor) - I looked for Xiaomi usb drivers but Windows say i already have the best driver installed...
Any ideas?
Click to expand...
Click to collapse
I'm guessing your phone is already in fastboot mode (with the little Mi cartoon guy)?
I installed ADB minimal, the MiFlash drivers but also ADB Lite drivers (mentioned in the big Madsponge thread where you can find the links). That might help.
In MiFlash when i hit Refresh it saw the phone as some ID like 1d23456 or something.
Just installed Qualcomm drivers - didn't help either...
set USB debugg mode - what was the USB connection type? if you remember - thanks in advance
piqiee said:
ive been using the indian rom for like 2-3 weeks now, my question is, does it support auto updater trough the updater? or we need to install back trough the mi flash tool
Click to expand...
Click to collapse
I dont think there is an update since 10.3.3.0 but i guess we'll find out with the next OTA update. I read somewhere an automatic update might lock the phone back (and brick it) so i disabled them for now, until we know more...
Of course Chinese OTA was fine on the China ROM.
hippo2s said:
Just installed Qualcomm drivers - didn't help either...
set USB debugg mode - what was the USB connection type? if you remember - thanks in advance
Click to expand...
Click to collapse
In fastboot mode you cant change it on the phone if i remember, and its set automatically in file transfer mode i think.
Yes I installed those drivers too. I might try a different laptop and usb cable tonight.
Thank you so far for your help.
FYI i used the USB cable shipped with the phone. As for the laptop, is its OS up to date? I installed the latest Windows update before the flashing process.
Hope its gonna work!
DontDamnMe said:
FYI i used the USB cable shipped with the phone. As for the laptop, is its OS up to date? I installed the latest Windows update before the flashing process.
Hope its gonna work!
Click to expand...
Click to collapse
I own the Indian variant, stock rom, bootloader unlocked and rooted. Widevine L1 is still present.
So, I am curious. When you flashed the Indian ROM, did your Widevine level changed from L3 to L1?
If you didn't check, if you don't mind, please install "DRM Info" from playstore and let me know!
I am trying to find whether the Widevine is implemented based on Stock ROM level or its just at device variant level. Thanks in advance!
theincognito said:
I own the Indian variant, stock rom, bootloader unlocked and rooted. Widevine L1 is still present.
So, I am curious. When you flashed the Indian ROM, did your Widevine level changed from L3 to L1?
If you didn't check, if you don't mind, please install "DRM Info" from playstore and let me know!
I am trying to find whether the Widevine is implemented based on Stock ROM level or its just at device variant level. Thanks in advance!
Click to expand...
Click to collapse
I just checked and it says I have L3. Honestly I don't really see a difference (if it's about Netflix HD or not), Netflix videos are still great quality.
DontDamnMe said:
I just checked and it says I have L3. Honestly I don't really see a difference (if it's about Netflix HD or not), Netflix videos are still great quality.
Click to expand...
Click to collapse
Thanks mate. Just one more thing. Could you play "Test Patterns" - S1:E1 video, zoomed out for 2 mins, in Netflix app?
It will initially show "960x540" (right top corner of the screen in zoomed out mode), but after 2 mins, does it change to "1280x720" or still stays at "960x540"??
Again, thanks in advance!
Ok it was the USB cable - device was detected on original USB cable.
Flashed - BUT i made a mistake and had it default to Clean all and Lock !!! ugh...
Flash went thru - but now i am in some thing called Redmi-Recovery 3.0. Red message say "This MIUI version can't be installed on this device."
I can still get into Fastboot and MiFlash can still detect the device - Upon trying to reflash again MiFlash gives error 'Erase Boot Error'
So i think i am F-ed....
Any advice, anyone?
I think its only "soft bricked". Another user had a similar issue and created a thread below. Experts here will be able to help you for sure. If its locked i believe you have to reinstall the China stock ROM.
About Netflix it stays on 960, so no HD i guess...
hippo2s said:
Ok it was the USB cable - device was detected on original USB cable.
Flashed - BUT i made a mistake and had it default to Clean all and Lock !!! ugh...
Flash went thru - but now i am in some thing called Redmi-Recovery 3.0. Red message say "This MIUI version can't be installed on this device."
I can still get into Fastboot and MiFlash can still detect the device - Upon trying to reflash again MiFlash gives error 'Erase Boot Error'
So i think i am F-ed....
Any advice, anyone?
Click to expand...
Click to collapse
Just download the china latest stock rom or china latest dev rom (recovery rom will be enough), no need of mi flash.
Then go to this link and follow the instructions. Since you can access the recovery, you are fine mate.
PS: Use the latest official Mi Assistant app from the MIUI site, not the one given in the link above. But the steps are the same.
Thanks guys I will try. Really worried that phone doesn’t shut down it keeps going into recovery (doesn’t power off) and charging doesn’t seem to work in all these conditions.
Will work quickly
---------- Post added at 12:15 PM ---------- Previous post was at 12:04 PM ----------
err... thats not the Mi PC Suite is it? when i google miphone assistant thats what comes up...
Err...not detecting my phone so the PC Suite can't find the device

Question OnePlus 10T 5G Hard Brick/Boot Loop Issue

The Issue:
The phone is constantly booting looping (flashes the Oneplus logo).I am unable to go to fastboot through either adb or through the on-phone buttons.
When plugged into a charger, it immediately begins to bootloop once enough power is supplied.
The only way to turn it off is by letting it get to 0%.
What caused the issue:
My phone got soft bricked all of a sudden, so I followed some tutorials that I found online showing me how to flash firmware using adb in fastboot and by unlocking my bootloader. This temporarily fixed the issue, but it told me that after doing everything I should relock it through ADB. Foolishly, I did so and am now stuck in this situation.
What I've tried:
I am able to get into EDL mode by holding both volume buttons, even while in the boot loop state.
I have downloaded the latest version of QPST and this firmware file (https://firmwarefile.com/oneplus-10t-5g-cph2415).
Quick note: I'm not sure if that's how it's meant to be, but QPST always detects my phone as "Download" (ESN: Download, Phone Number: Download, Banner: Download).
I am not quite sure how to use QPST and have tried following the guide, which told me to select some.hex files from the firmware I downloaded, but I was unable to find any.hex files at all and therefore could not proceed.
I also tried QFIL by selecting prog_firehose_ddr.elf from the IMAGES folder and tried multiple times in both UFS and emmc mode, selecting all of the rawprogram 1-5.xml files with their corresponding patch1-5.xml files from the IMAGES folder, but I always got the same error:
ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes
ERROR: function: sahara_main:982 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail process fail
Finish Download
I have tried the leaked EDL flasher from here: https://forum.xda-developers.com/t/edl-flash-tool-leak.4494211/. However, I have been unsuccessful in doing so, though I may have been doing it wrong, and it would be greatly appreciated if someone could explain or tell me how to do it. As you can see in the attached image, I tried to flash it by using the images folder located in the firmware that I have downloaded. But it just gets stuck at 3%
indefinitely as the time goes up forever.
Thanks for reading looking forward to any replies/info
uh do not flash it by qfil it will just not work because oneplus actually blocked qfil and qpst so the only way is their edl tool and you cannot flash it on the edl tool unless you have an (actual) account and (not) bypassed
oneplus is really starting to nerve me really their merge with oppo is like a mistake
oneplushypergaming said:
oneplus is really starting to nerve me really their merge with oppo is like a mistake
Click to expand...
Click to collapse
the Merge was a mistake, its laughable that OnePlus went from being with the opensource community to being completely against it.. What annoys me the most is, instead of just locking their bootloader, they post the source code for their phone, probably as they have to, yet they give no way to utilize that code without developers running the risk of bricking their device.. Developers are willing to dedicate their time and money, to build for a device, all they ask, is for the ability to be able to unbrick, that is humble, Devs ask for donations, they do not force it.. Oppo do not even allow their bootloader to be unlocked, which prevents users from bricking their device.. OnePlus allow users to unlock their bootloader, knowing full well that Developers will understandably not be willing to develop for a device without a potential 60-80% brick chance.. The code could very well build for said rom, but once flashed it has the potential to turn the dev's device into a paper weight, meaning something they do to provide, turns into something that ultimately takes..
hosthere247 said:
the Merge was a mistake, its laughable that OnePlus went from being with the opensource community to being completely against it.. What annoys me the most is, instead of just locking their bootloader, they post the source code for their phone, probably as they have to, yet they give no way to utilize that code without developers running the risk of bricking their device.. Developers are willing to dedicate their time and money, to build for a device, all they ask, is for the ability to be able to unbrick, that is humble, Devs ask for donations, they do not force it.. Oppo do not even allow their bootloader to be unlocked, which prevents users from bricking their device.. OnePlus allow users to unlock their bootloader, knowing full well that Developers will understandably not be willing to develop for a device without a potential 60-80% brick chance.. The code could very well build for said rom, but once flashed it has the potential to turn the dev's device into a paper weight, meaning something they do to provide, turns into something that ultimately takes..
Click to expand...
Click to collapse
Well said to be honest that clears my suspicion about oppo they are greedy and dirty and maybe it is oppo who is making oneplus act like this in the first place oneplus should really consider all of this and give the people what they want instead of being a monopoly like oppo i never even liked oppo from the beginning actually i trusted oneplus with my 7t because i knew if i were to brick it the msm tool will always be there it has been months since the release of the 10t and ace pro and yet still no msm tool for it or a way to even get it back yet but there are many msm tools for the rest of the oneplus devices so maybe i am wrong they can tell us but i still think it is wrong that th 10 pro has to have an actual account.
I'm stuck with a Hard Brick and my device screen is black, only entering EDL for a few seconds.
Qmiclient it's the new MSM
AkayamiShurui said:
Qmiclient it's the new MSM
Click to expand...
Click to collapse
Hello , I found this topic because i'm facing the same problem as OP after relocking bootloader .... As anyone found solution to flash on edl mode ? Thanks
mybrickplus said:
Hello , I found this topic because i'm facing the same problem as OP after relocking bootloader .... As anyone found solution to flash on edl mode ? Thanks
Click to expand...
Click to collapse
the only thing i can think of is a slot switch
Yes Probably what happened but now i'm totally stuck on the bootloop until no baterry left.
Cant access fastboot because the phone boot and 2 seconds later reboot ... I can only access edl mode with Oneplus Flasher (bypassed by Hexa change) but after that, like op described the time keep increasing ,and circle progress stays at 3%, nothing seems change on phone
You have no option but to use the official flashing revovery via Oneplus / oppo whoever does it which means paying them to reflash the phone correctly
Ok thank you, so ive to send back the phone or i can do it on my own ?
mybrickplus said:
Ok thank you, so ive to send back the phone or i can do it on my own ?
Click to expand...
Click to collapse
no need to send the phone to oneplus just contact them directly and arrange for one of their techs to reflash your phone over the internet
leezaal said:
no need to send the phone to oneplus just contact them directly and arrange for one of their techs to reflash your phone over the internet
Click to expand...
Click to collapse
He could try but I'm not that sure that they are continuing to offer this service.
Thank you for your help and answers
So anyone who still watching this thread I made progress on this whole problem I took the 11r firmware file and it has script.sh commands in there and I ran them and it extracted all of the firmware files and made a bin folder that has only two folders inside of it and it took all the files to make it it puts it in your recovery section of your computer but it compiled all the empty files so they actually have things on them if you want to know how I did it and what I used just private message me cuz I will not be posting public because Oppo

Categories

Resources