Develop Bugs

[TOOL] Lx Multi Tool v1.3.2 [WIN/LIN/MAC][Unlock/Recovery/Stock/Kernel/More]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​It has LINUX/UNIX and MAC support!
​
Because there is another tool for Android called Android Multi Tools, I renamed this one to Lx Multi Tool, future releases will go under this name.
​ Features: ​
Fastboot​​- Unlock/Lock Bootloader​- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included​- Flash any partition (Flashing submenu)​- Flash full Stock images (you can choose and add images)​- Erase partitions (you can choose which of the partitions)​- Reboot (you can choose again...)​​Adb​​- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.56 (Systemless!) included​- Backup (you can choose the name and place for your backup)​- Restore (you can choose your backup)​- Version (it just shows the version of your adb binaries) - platform-tools 23.0.1 included​- Logs (DMESG and Logcat)​- Screenshots (you can directly take screenshots to your PC with no Root)​- Reboot (lots of choices)​​Others​​- Refresh and delete files/folders from menus (Right-click or key F5 and Del)​- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)​- Tab key support for easier keyboard navigation​- Tool-tips for all buttons​- Check for updates​- Link to xda-thread (here)​​​ Download links: ​
Windows x86|x64 - Linux x64 - MAC x64​​All released versions can be found here.​​
​
(The latest versions are always on the bottom.)​​[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.​​
​ Known bugs/limitations: ​
- For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)​- For the return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)​​
​ Changelog: ​
​Check the changelog for each release here.​​​ Tutorials/FAQ: ​
​Q: How do I get in bootloader/fastboot mode?​Turn off the phone and turn it on by using Volume down + Power key.​​Q: How do I check for updates on your tool?​Follow the instructions on the screen below.​
​Q: Where can I find the device driver to install it for windows?​Click here, download the driver, and run the setup.​​Q: How do I root my stock phone?​- Unlock bootloader.​- Flash recovery.​- Use SuperSU 2.62 systemless or higher from here.​(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)​​Q: I get an error "Cannot open file" on MAC, what should I do?​Open the terminal, go to your application path and paste this command:​
Code:
chmod +x LxMultiTool.app/contents/macos/*
​Q: What do I need to do in order to be in Fastboot or in ADB mode.​Fastboot mode will be detected only while being in bootloader.​ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.​Refresh button needs to be used in order to check for what mode you are in.​​Q: Are there any other software that I need to install in order to run this tool?​On Windows and MAC everything is bundled, so nothing needs to be installed, just run.​On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.​If it's not enough, use ldd LxMultiTool in the terminal to find out what you're missing from your environment.​​Q: I have a yellow/orange/red text screen during boot, what's that?​When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.​​Q: Hey, my device is not detected, why?​On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.​Also, make sure you click the connection Refresh button after connecting the device to your PC.​​Q: What do I need to do in order to install a custom ROM?​1. Unlock Bootloader.​2. Flash a custom recovery of your choice.​3. Flash an insecure kernel (boot).​4. Flash custom ROM with no problems via recovery.​All those things are found and can be done via this tool.​​Q: Hi, I just downloaded this tool, how do i use it?​First, extract the folder somewhere.​After that, run LxMultiTool.exe on windows by double-clicking it, LxMultiTool on Linux, and the same on mac.​​Q: Do I need android-sdk installed or something else?​No! This tool uses its own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyway.​This tool is fully portable and stand-alone.​​Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?​Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:​- Enable Developer options​- Enable USB Debugging​- Look for the ‘OEM Unlock’ Option and toggle it.​​Q: How do I use the return to stock feature?​First, download the latest package from here, then extract the contents (there is an archive in the archive) until you get to a folder like angler-mda89d​that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.​​Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.​
​Q: How do I enable Developer options?​- Launch the Settings​- Scroll Down and Tap on About Phone(or About Device)​- Locate the Build Number Section​- Tap on the Build Number Option 7 Times​- Go Back to the Main Settings Page​- Scroll Down and Tap on Developer Options​​Q: Hi, I just bought a phone what should I do now?​Well, you firstly need to unlock your bootloader...​​Q: What is logcat?​Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.​It is usually used for debugging and entertainment(?).​When you report an error/bug to somebody, it will be a blessing to provide a logcat (log file)!​​Q: What is a Custom Recovery and why do I need one?​A custom recovery is that thingy that lets you flash .zip files, use your logic, and you will get it why you need one.​​Q: There are other guides/tutorials out there. Should I check them instead of this?​If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...​​Q: What is sideload and how do I use it?​Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.​Please note that you need to be in sideload mode on your recovery before doing this.​To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload​
​ Sources: ​
The official and original repository can be found here.​​
​ Bug reports/feature requests: ​
If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on GitHub for more traceability here.​​
​ Licensing: ​
Please note that this tool is open source and released under the GPL v3 license, which can be read here.​Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.​​
​ Tech and stuff: ​
Some additional marketing for stuff used in this tool​​Qt - An awesome cross-platform IDE​Vmware - For letting me test this tool on all platforms (Linux and MAC).​Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)​UnixUtils - For the sed utility for Windows.​AndroidFileHost - For the awesome file-management platform for developers.​​
​ Donations: ​
Even though this tool is provided free of charge, fully open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.​​This section will also include the hall of fame for donors and on the github repository.​​Special thanks for donations:​- @john7760​​
​ Disclaimer: ​
I will not be responsible for smashed screens, bricked phones, or any other things that you can accuse me of, I've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.​Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A, or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
XDA:DevDB Information
Lx Multi Tool, Tool/Utility for the Huawei Nexus 6P
Contributors
Lexmazter
Source Code: https://github.com/lexmazter/LxMultiTool
Version Information
Status: Stable
Created 2016-01-01
Last Updated 2016-01-16

Already tool kit?
*Damn, nexus dev support is amazing
I feel so bad for buying galaxy s6, 0 aosp roms, Mod edit: Profanity removed dev support and all because of stupid exynos ;C

You da man! Can't wait for my phone to show up.

That was quick!! Waiting for this phone to be launched in India.

It works great thanks.I mean Tool

Wow. Can't wait to get my 6P and use this
Sent from my A0001 using Tapatalk

Add to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P

Haven't even received my device yet, just wanted to say Thanks in advance!

Showing so much promise
I can't say more for this kind of support.

Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.

wilbarger said:
Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.
Click to expand...
Click to collapse
Got the 128gb monster on the way myself.

Thanks for this. Making it easy for everyone is a great thing I'm so excited to get back on a nexus

Thanks for this tool, I need to start from scratch because I don't have a Nexus since Nexus One

Thanks for this. Will be a first time user for the nexus generation. Just ordered the 6P so will definitely be doing this .

Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk

C4PO said:
Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
AFAIK, locking bootloader has nothing to do with the recovery, but then again, I never locked a bootloader...

Pretty sure you'd need to flash stock recovery. It won't hurt anything to try it without stock recovery, but if it doesn't work then you'll know for sure why.

I'm not planning to mess around with it too much until a stock system file is available. I need a Plan B. Lol

Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!

ryman222 said:
Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!
Click to expand...
Click to collapse
Unfortunately I never got the chance to test the MAC version, finally I have a tester
From what I can see at a first look is that this simple_curses.sh is some leftover from when I experimented with some UI tricks for bash to try to simulate the looks of the batch version..
Can you please check this temporary version from here -> 6PMultiTool.v0.2.1.zip

Jiofi 3 jmr540 Unlocking.

Recently I've been googling on how to unlock my jiofi jmr540 device and found nothing.
But I discovered something else. I don't think we need a custom rom to unlock the device. I'm not a expert in these stuff.
Every jiofi device has web UI.
I discovered that every jiofi device have a hidden web UI that is engineer mode.
I didn't find any rom for my device but I found for jmr520 which was in bin format. I opened it using notepad in my pc and discovered that engineer mode does exist in its coding. There is lots of options present in engineer mode like manually selecting network band, choosing between 2g, 3g, and 4g, manual network search, and I also saw some network unlock coding which I couldn't understand by entering unlock code.
Can anyone help to access engineer mode in my device. I think it is also a html just like jiofi.local.html.
It would be really great if someone helped as many jiofi users are still wanting to unlock the device.
My device details are,
Firmware Version: FXN_JMR540_R6.11
Hardware Version: FXN_JMR540_V055
Device manufacturer : Foxconn

Interesting. Did you have any success?

mGforCe said:
Interesting. Did you have any success?
Click to expand...
Click to collapse
Nope. I gave up. Jiofi is not like other devices. Other devices can be configured using data cables from any computers with the device configuration software. But jiofi can be configured only using Web UI. That is the MAJOR problem.

How to enter in engineer mode in jiofi jrm520
How to enter in engineer mode in jiofi jrm520

None of the blue whales in this ocean can fix it?

Found Some interesting Facts on JIOFI3 ( JMR540 )
I managed to make the device into FASTBOOT.
using ANDROID BOOTLOADER INTERFACE.
Able to ping the hardware and get the following:
(bootloader) version:0.5
(bootloader) version-baseband:
(bootloader) version-bootloader:V055
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x8000000
(bootloader) serialno:8*32***4
(bootloader) kernel:lk
(bootloader) product:JioFi3
Click to expand...
Click to collapse
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel: OKAY

Any firmware available till now , mdm9607 firmware can be flashed via adb.... if anyone has firmware kindly share :
unlocked devices are sold at alibaba JMR541, both are same chipset
https://www.alibaba.com/product-det...?spm=a2700.details.deiletai6.2.2ea36c5acxqHqD

tr

Jio-fi-3 JMR_541
how did you did that @ Electroboy_Prakash

Electroboy_Prakash said:
Found Some interesting Facts on JIOFI3 ( JMR540 )
I managed to make the device into FASTBOOT.
using ANDROID BOOTLOADER INTERFACE.
Able to ping the hardware and get the following:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel: OKAY
Click to expand...
Click to collapse
How did you get fastboot menu? Can you extract firmware and send it.

Here is another jio fi 2. You can log in to Jio fi. Use 192.168. Username Administrator Password is written on Jio Fi box.
ODMPegasusProduct IDM2
IMEI 911522-----------
Firmware VersionPEG_M2_B38.2Firmware Creation Date2019-11-29
Frequency Bands Supported B3,B5,B 40

I've managed it to unlock this device. Enabled diagnostic mode and adb. Custom firmwares are possible in this devices. Once modified firmware can be flashed via fastboot mode which is easily accessible without any modification.
Check my Twitter thread here https://twitter.com/ab_hi_j/status/1395394412545515521
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Can you help me with the procedure i also want to unlock my jiofi3

sksinha said:
Can you help me with the procedure i also want to unlock my jiofi3
Click to expand...
Click to collapse
Here is the unlocking guide
[GUIDE][UPDATED] Unlocking JioFi 3 JMR540 & JMR541 for all networks
Unlocked Firmware for JioFi 3 JMR540 & JMR541 Disclaimer I am not responsible for any kind of damage to your device. Use this firmware at your own risk Post is for educational purpose only. ONLY FOR JMR 540 & JMR 541 I was able to dump and...
forum.xda-developers.com

Vismay G S said:
Recently I've been googling on how to unlock my jiofi jmr540 device and found nothing.
But I discovered something else. I don't think we need a custom rom to unlock the device. I'm not a expert in these stuff.
Every jiofi device has web UI.
I discovered that every jiofi device have a hidden web UI that is engineer mode.
I didn't find any rom for my device but I found for jmr520 which was in bin format. I opened it using notepad in my pc and discovered that engineer mode does exist in its coding. There is lots of options present in engineer mode like manually selecting network band, choosing between 2g, 3g, and 4g, manual network search, and I also saw some network unlock coding which I couldn't understand by entering unlock code.
Can anyone help to access engineer mode in my device. I think it is also a html just like jiofi.local.html.
It would be really great if someone helped as many jiofi users are still wanting to unlock the device.
My device details are,
Firmware Version: FXN_JMR540_R6.11
Hardware Version: FXN_JMR540_V055
Device manufacturer : Foxconn
Click to expand...
Click to collapse
need this. please take look

abhimortal6 said:
Here is the unlocking guide
[GUIDE][UPDATED] Unlocking JioFi 3 JMR540 & JMR541 for all networks
Unlocked Firmware for JioFi 3 JMR540 & JMR541 Disclaimer I am not responsible for any kind of damage to your device. Use this firmware at your own risk Post is for educational purpose only. ONLY FOR JMR 540 & JMR 541 I was able to dump and...
forum.xda-developers.com
Click to expand...
Click to collapse
I have accidentally erased the recovery partition of JMR540 and my jiofi not starting always go in fastboot mode. Can you please provide boot.img file of JMR540 jiofi.

message removed

Jio pushed new firmware JMR540 and following changes are made.
-> locked boot loader
-> TTL RX disabled so we are not able to access root shell via UART.
only option to unlock modem is
-> boot modem to EDL( Emergency Download Mode) mode.
-> take backup and flash old recovery via QPST (qualcomm firehose prog file required for MDM9207)
@abhimortal6
sorry for chasing you again. Hope you know the exact procedure.
Can you share
1) EDL points for JMR 540 to short and boot to EDL mode.
2) Qualcomm firehose prog file for MDM9207

It's fine @jithinvp4, okay so there's no exact test points you can short. Trick is to stop power to EMMC for fraction of a second while booting. There's a single resistor 2nd one from bottom in left of EMMC. You can use RPi pico to build brute switch.
If done correctly while booting it'll fail and fall to un-secure download mode. Yes you read that right un-secure it's an old Qualcomm thing.
I had chat with one of Manager/People from JioFi device team after first exploit. I'm not sure they'll fix this too. It's doable I think. Not sure if they'll do this because not everyone can do this. So yeah private exploit is still there

@abhimortal6 Thanks for your response.
I was spending too much time for last few weeks to find a method to unlock JMR 540 . I thought there is a test-point . Don't have much knowledge to use RPi pico.
please let me know any other simple method available to boot EDL .
Otherwise i will be monitoring your tread for your next unlock solution.

[Tool] NFT - Nokia Flash Tool to flash stock ROM (For Unlocked Bootloader)

NFT 2.0.7 & 1.2.3- Nokia Flash Tool to flash stock ROM
This tool can make you easier to install stock roms
This program is made for Windows, with .NET Framework 4.5.1 This is VB.net program
v.1.1.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What the tool can do:
- Flash phone - the tool supports the following phones out of the box: Nokia 8.1, Nokia 9 PureView, Nokia 7.2, all Nokia phones on the SDM_660 family, And other Nokia Phones
- Requires the bootloader to be unlocked.
- Support for more phone models can be easily added by adding a new profile and defining the partitions to flash and matching it to file names to be flashed.
- Able to create custom flash process
- Able to import profile (partition and flash data) from a txt file (check sample format)
- Can dump your current partitions to create a flashable file for recovery (this function needs root access)
- Switch slot on A/B devices which support slot change
Thanks to:
- Hikari Calyx (hikaricalyx.com)
- Narender Singh (TechMesto.com)
System requirements:
- Windows 7, 8, 8.1,10 or higher, 32bit or 64bit
- .NET Framework 4.5.1
- USB Data Cable
- Phone
Downloads:
NFT v.1.2.4 (Stable)
NFT v.2.0.8 ( Stable )
NFT v.2.0.9 ( Stable ) - new 08 Dec 2020
NFT v.2.1.0 ( Stable ) - new 11 nov 2021
Firmware :
Firmware 7.2 (1_390)
Firmware 6.2 (1_160)
*Work with Payload
- install python 3
- make sure user Environment variables link to Python folder and Python folder\script
Bugs:
v.1.1.1
-nokia 9 profile & dump (fix on 1..1.2)
v.1.1.2
- language failed to saved on second times ( fix on 1.1.3)
- some word failed to translate to CN ( fix on 1.1.3)
v1.1.3
- abl skip not work after add language (fix on 1.1.3a)
v1.1.3a
-none
v1.1.4
- on some case Nokia 8.1 switch to A slot After flash (fix on 1.1.5)
v.1.1.5
- dump on nokia 7.2, 6.2 because new naming process (fix on 1.1.6 )
v.2.0.7
- ota flash not work (fix on 2.0.8 )

Update & change Logs
NFT v1.1.0
- New design
- Add support phone
- Add auto-detect mode
- Add some feature on profile management
NFT v.1.1.1
- Fix detect Device for MTK & A-only Device
- Fix dump for nokia 8.1
- add dump profile for nokia 8 & Sirocco
NFT v1.1.2
- FIx Nokia 9 profile and dump
- now dump partition Work on FTM mode And Normal mode
- Add Language Setting : Simplified Chinese & English...
NFT v1.1.3
- fix save language in setting
- Fix some translate in CN language
- Add warning when flash Payload.bin
- Now NFT only process payload.bin with size more than 1Gb
(make sure use full system update payload.bin..)
NFT v1.1.3a
-fix minor bugs
NFT v1.1.4
- support more python name (for multiple python installed) default : python3, python, py . can add more
- add install protobuf on script
- add check slot on dump
- add custom dump setting..
- to change saved filename partition double click file name
*for best restore dump please use default file name for splash partition
NFT v1.1.5
- Fix auto-switch to slot A, after Flashing Nokia 8.1
- add Russian Language
- add Indonesia Language
- dump files Now naming Base installed Rom.
27 Des.
- fix auto-detect for new devices (7.2 ,6.2 , etc)
29 Des
- add Donate link... for donate
- add logs
v1.1.6
- fix dump problem on nokia 6.2, nokia 7.2
- new menu - Create homebrew from OTA FILES (extracted)
3 januari 2020
- fix name file Homebrew ( Minor)
- add error handle homebrew Clean temp files
- update Logs
27 januari 2020
- fix naming dump for some devices... when dump inactive slot
-fix minor bugs
V2.0.0
- New UI
- Restore Partition from ADB
28 januari 2020
V2.0.1
- Fix restore partition From ADB
- Tweak Side menu animation(Faster)
- now support flash partition structure (for convert CN - Global)
V.1.1.7
- now support flash partition structure (for convert CN - Global)
v2.0.2 & v1.1.8
- fix 4.2 & 3.2 Support
- note for nokia 4.2 & 3.2: Before do anything on flash form set profile to nokia 4.2 and nokia 3.2
v2.0.3 & v1.1.9
- fix minor bug for nokia 9
- fix nokia 7.2/6.2 didn't boot after flash ( Vbmeta problem)
v2.0.4 & v1.2.0
- NOw Support .zip file ( Ota File & Cutom rom )
- fix English translate
v2.0.5 & v1.2.1
- NOw Support .zip file ( Ota File & Cutom rom )
- fix English translate
- add separate setting For vbmeta flash script ( because -disabled-verify on some device will cause failed to update ota )
v2.0.8 & v1.2.4
- add support raghu vagma Homebrew Firmware
v2.0.9
- remove unused messagebox
* note for nokia 4.2 & 3.2: Before do anything on flash form set profile to nokia 4.2 and nokia 3.2

Reserved
How to :
* Flash phone
- Open NFT
- Choose Flash Normal
- Select Folder which Contain Firmware File
- Select Profile ( U can create Your Own profile In manage button)
- Flash
* Flash phone With Payload.bin
- Extract Full Ota FIle .zip
- Open NFT
- Choose Payload.bin File
- Choose Slot
- FLash
* Create Dump Partition Profie
- Open NFT
- Select Tools
- Select Dump partition
- Select manage
- Connected Phone with USB Debuging SET ON With Root Permision Granted
- Add New
- Select Which Partition Do you Want to backup
- Naming Profile
- Save
* Dump Partition
- Open NFT
- select Tools
- Select Dump Partition
- Connected Phone with USB Debuging SET ON With Root Permision Granted
- Select Profile
- Select Slot
- Dump Partition
* Homebrew From FULL OTA FIle
- Extract Full Ota FIle .zip
- Open NFT
- select Tools
- Select Make HomeBrew From Full OTA FILES
- Select Payload.bin File
- Choose Folder To save Homebrew
- Make Homebrew
* HomeBrew Security update
- Root Phone
- Follow instruction How to update phone on Magisk forum
- after update don't restart and don't Pacth boot.img to other slot
- Open NFT - Tools -Dump Partition
- Select Profile Homebrew For your Device
- Set inactive Slot on Slot option (if active Slot 'a' then choose 'b' , if active Slot 'b' then choose 'a')
- dump partition

Thank you ? Now I can mod my Nokia 7.2 without worrying too much.

Nice work!

anyone have valid link to stock firmware? thank you in advance

pattiandy said:
anyone have valid link to stock firmware? thank you in advance
Click to expand...
Click to collapse
Click hikari calyx name in NFT to download firmware

I tried flashing OTA using payload mode. After the operation was finished, my devise's screen turned black and now it does not turn on anymore. Is there anything I can do to fix it?
so it's some sort of 9008 mode I guess. and I couldn't find any nb0 firmware. I am absolutely clueless about what to do now.

lilmonkw said:
I tried flashing OTA using payload mode. After the operation was finished, my devise's screen turned black and now it does not turn on anymore. Is there anything I can do to fix it?
so it's some sort of 9008 mode I guess. and I couldn't find any nb0 firmware. I am absolutely clueless about what to do now.
Click to expand...
Click to collapse
i put information in about button
for payload mode...it only for full rom OTA.. size about 1,5GB or more..
let me know what payload u use..
and what devices???
firmware download click on hikari name on NFT tools...
for 7.2 u need extract every zip in firmware and put it in one folder..
Flash using normal flash

lilmonkw said:
I tried flashing OTA using payload mode. After the operation was finished, my devise's screen turned black and now it does not turn on anymore. Is there anything I can do to fix it?
so it's some sort of 9008 mode I guess. and I couldn't find any nb0 firmware. I am absolutely clueless about what to do now.
Click to expand...
Click to collapse
Which device did you flash? And didn't you understand that you need a full OTA to use the payload method?
Check if the device is in QdLoader 9008 mode, then you can still recover it. But if it is in some other mode, then the recovery needs disassembly.

sayaoks said:
i put information in about button
for payload mode...it only for full rom OTA.. size about 1,5GB or more..
let me know what payload u use..
and what devices???
firmware download click on hikari name on app...
for 7.2 u need extract every zip in firmware and put it in one folder..
Flash using normal flash
Click to expand...
Click to collapse
I missed that payload information, and it's my fault. My device is in the 9008 mode now. Nokia 7.2.
I did not use the full OTA, and then I pretty much broke things. The OTA I used was the one I pulled out after it automatically downloaded on my phone. The device had August security patched firmware (the only one on the hikari website) installed.
---------- Post added at 12:49 PM ---------- Previous post was at 12:47 PM ----------
singhnsk said:
Which device did you flash? And didn't you understand that you need a full OTA to use the payload method?
Check if the device is in QdLoader 9008 mode, then you can still recover it. But if it is in some other mode, then the recovery needs disassembly.
Click to expand...
Click to collapse
I messed up with flashing not full OTA, and it's my fault. My device is Nokia 7.2. It's in the QdLoader 9008 mode.

lilmonkw said:
I messed up with flashing not full OTA, and it's my fault. My device is Nokia 7.2. It's in the QdLoader 9008 mode.
Click to expand...
Click to collapse
From QDLoader, we should be able to fix it, but unfortunately, Nokia has not released a rawprogram and patch0.xml files. But you can likely use the one from Nokia X71 after slightly modifying it. Then flash abl and xbl using QFIL tool. Once you have a working bootloader (fastboot mode), you will be able to flash the stock ROM again.
I think @hikari_calyx will have a better idea about which files to use.

singhnsk said:
From QDLoader, we should be able to fix it, but unfortunately, Nokia has not released a rawprogram and patch0.xml files. But you can likely use the one from Nokia X71 after slightly modifying it. Then flash abl and xbl using QFIL tool. Once you have a working bootloader (fastboot mode), you will be able to flash the stock ROM again.
I think @hikari_calyx will have a better idea about which files to use.
Click to expand...
Click to collapse
What would I need to modify in those files? And is there a possibility of Nokia releasing rawprogram and patch0.xml for 7.2 ever?

"use Payload.bin" not support Python3 for Windows Store

[email protected] said:
"use Payload.bin" not support Python3 for Windows Store
Click to expand...
Click to collapse
u need install python 3.
and install protobuf "python install protobuf"
for payload flash
if your python use "python3 / py" for running python...
use latest v1.1.4 its support

On my 7.2 im trying to go back to stock from Lineage 16.0 (unofficial) so that some things will work again and im getting:
"Flash abort!! Phone Looked Bootloader" (not a typo)
"ALL TASK COMPLETE"

Talon Pro said:
On my 7.2 im trying to go back to stock from Lineage 16.0 (unofficial) so that some things will work again and im getting:
"Flash abort!! Phone Looked Bootloader" (not a typo)
"ALL TASK COMPLETE"
Click to expand...
Click to collapse
Hi, is your device critical unlocked? If not, please do it.
Code:
fastboot oem device-info

singhnsk said:
Hi, is your device critical unlocked? If not, please do it.
Code:
fastboot oem device-info
Click to expand...
Click to collapse
The bootloader is, how do you think i got the Lineage on it? I dont how to unlock anything else, this is all new to me on the Android side, im a Windows guy. I have TWRP on it, will that matter?
Nvm, i figured it out, got it unlocked.

It gets to "Flashing system.img to system_b" and aborts. Same thing happens if i switch to system_a.

Talon Pro said:
It gets to "Flashing system.img to system_b" and aborts. Same thing happens if i switch to system_a.
Click to expand...
Click to collapse
You unpacked the system, boot and vendor image to the same folder as well, right? And not to some other folder. The file exists in the same directory?

Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial

In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset.
from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool.
with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa).
MTK-bypass credits to @k4y0z
, @chaosmaster and @xyzz on github.
REQUIREMENTS:
• Python
Download Python
The official home of the Python Programming Language
www.python.org
• libusb-win32
https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download
• Sp Flashtool
SP Flash Tool Download All versions for MediaTek Devices
SP Flash tool download is the best application to flash Stock firmware, Custom recovery and fix some extreme issues on MediaTek Android smartphones. Download SP Flash tool all versions from our official download page.
spflashtool.com
• Bypass Utility Compiled
18.9 KB file on MEGA
mega.nz
---------------------------------------------------------------
• Bypass Utility Latest Releases
Release 1.4.1 · MTK-bypass/bypass_utility
Improve handshake reliability
github.com
• Exploits Latest Releases
Release 1.5 · MTK-bypass/exploits_collection
mt6261 mt6572 mt6580 mt6582 mt6735 mt6737 mt6739 mt6755 mt6757 mt6761 mt6763 mt6765 mt6768 mt6771 mt6785 mt6799 mt6873 mt8127 mt8163 mt8173 mt8695
github.com
• Realme 3 (rmx1821) Flashtool Firmware link soon
> I will upload the realme 3 firmware with Scatter File and Auth File for Third Party Flashtool like SP Flashtool soon, but if you have an official firmware of realme 3 with Scatter and Auth File you can use it no matter what version it is.
> If you know how to extract an OFP file, you can download this realme 3|3i firmware and extract the OFP file.
https://fileload.coloros.com/30842RMX1821EX_11_C.17_201117_cb5665f2.zip
> Video Tutorial on how to Extract OPPO | REALME firmware (OFP file)
VIDEO TUTORIAL
TEXT TUTORIAL
INSTALLATION:
• Install Python (tick checkbox "Add Python X.X to PATH") and proceed.
( if you are using windows 10, Download and Install Python 3.9 through Microsoft Store )
• Install lib-usb_win32
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click Next>Next> until you see the next image
Click Finish and Launch Lunch Filter Wizard
Choose the "Install a device filter" and click next
You will see this device selection.
Now you will need to connect you phone with power off to computer.
> Hold all the buttons and connect to the computer (wait until you see Mediatek USB Port in libusb Device selection and Install)
(note: you have to select and install it very quick, because the phone disconnect in just a few seconds)
> Wait until it shows this (Click OK and close libusb and Disconnect your phone)
INITIALIZATION:
• Extract Bypass Utility, and go to extracted folder
> type "cmd" in the address bar and hit enter
> in cmd console install (Install pyusb, pyserial, json5)
by typing: pip install pyusb pyserial json5
> after that bypass mtk
by typing: python main.py
> when you see "Waiting for bootrom" , you need to connect your phone again (Holding all button and plug it into your computer and wait until it recognized.)
you should have this following output. do not close this window and remember the Found port of you phone
as you can see my port is = COM7
DO NOT DISCONNECT YOUR PHONE FROM COMPUTER THIS TIME
FLASHING FIRMWARE:
• Extract SP Flashtool and Realme 3 Firmware
• Open flashtool.exe and click Options>Connection
and tick AURT instead of USB.
Select the COM port of the phone which is COM7 in my case
then close Option Window
• Now In Flashtool choose Scatter-File from the Extracted Firmware of Realme 3
(wait until it finished the Processing)
• After that choose Authentication File
• After loading Scatter and Auth File Click Download
It should start downloading the firmware to you phone now without any error.
(wait until it finished the download.)
When finished downloading you get a check windows indicating that the flash was successful!
Thats it Congratulations! You may now disconnect your phone from your computer and POWER ON.
your DEAD [HardBricked] Realme 3 is now Alive!
(Note: This method is applicable to any MTK devices with SoC mt6735, mt6750, mt6765, mt6771, mt6785, mt8127, mt8163, mt8173, mt8695)
For more updates about MTK-Bypass visit the official github page @
MTK-bypass
MTK-bypass has 8 repositories available. Follow their code on GitHub.
github.com
all the tools and utility is not mine. credits to the developer.
Original Bypass Tool xdaThread
[MOD][DEV] MediaTek / MTK - Auth Bypass (SLA/DAA) - Utility
As some of you have already noticed, a couple of weeks ago @Dinolek and I published a utility, that allows bypassing authentication on MTK devices. The tool is based on an exploit dubbed kamakiri, which was originally found by @xyz` and released...
forum.xda-developers.com
special thanks to @popoff-r for mentioning about a thread of repairing MTK devices.

Thanks

fawazahmed0 said:
Thanks
Click to expand...
Click to collapse
so its you , i thought the two in the credits in your github bypass_utility is one who develop it. im sorry sir. im not really familliar where to see the owner of the work it github. im really sorry for not mentioning your name in this. gotta edit now. You are Great sir!

ATDteam said:
so its you , i thought the two in the credits in your github bypass_utility is one who develop it. im sorry sir. im not really familliar where to see the owner of the work it github. im really sorry for not mentioning your name in this. gotta edit now. You are Great sir!
Click to expand...
Click to collapse
Thank you for putting this altogether, this should speed up the development work for this phone(kernel etc), as people don't have to go to service center for hard brick.
Also I want to tell you, I shouldn't get the credits for bypass_utility, the two people you mentioned should be getting the credits, I just forked(copy/cloned) the repository.
I assume you are new to github, anyone can fork(copy/clone) a repository by clicking on fork button
You can differentiate whether a repository is forked(copied) or original by seeing on the top left side.
Thanks

fawazahmed0 said:
Thank you for putting this altogether, this should speed up the development work for this phone(kernel etc), as people don't have to go to service center for hard brick.
Also I want to tell you, I shouldn't get the credits for bypass_utility, the two people you mentioned should be getting the credits, I just forked(copy/cloned) the repository.
I assume you are new to github, anyone can fork(copy/clone) a repository by clicking on fork button
View attachment 5205247
You can differentiate whether a repository is forked(copied) or original by seeing on the top left side.
View attachment 5205251
Thanks
Click to expand...
Click to collapse
Thank you so much that was a very helpful information.

How to fix this error sir..

What Error?, please provide screenshot of the error, if you can't explain it.

ATDteam said:
What Error?, please provide screenshot of the error, if you can't explain it.
Click to expand...
Click to collapse
Tihis sir

What Error?, please provide screenshot of the error, if you can't explain it.
Al Djufri said:
Tihis sir
View attachment 5207505
Click to expand...
Click to collapse
try to uninstall python and reinstall again, also download the bypass_utility, the one that i attached in this thread.
and try again. make sure your usb cable is working properly, it seems that your device does not read properly by the utility. change your cable if posible. Download python 3.9, if still doest work. try using windows 10 OS.
18.9 KB file on MEGA
mega.nz

ATDteam said:
What Error?, please provide screenshot of the error, if you can't explain it.
try to uninstall python and reinstall again, also download the bypass_utility, the one that i attached in this thread.
and try again. make sure your usb cable is working properly, it seems that your device does not read properly by the utility. change your cable if posible. Download python 3.9, if still doest work. try using windows 10 OS.
18.9 KB file on MEGA
mega.nz
Click to expand...
Click to collapse
Reinstalling python
Reinstalling lib libusb
Changing usb cable
Changing port usb
Change pc, i mean borrow a pc from my friend
Changing spflashtool, same problem sir?
Do you have telegram account

thanks it works thanks for saving my phone

Its not the same in your first screenshot you reach "Disabling protection" but in the 2nd one only the utility found your phone..., did you release all the buttons emmidiately after your computer detects your phone phone? It is important that you release emmidiately. Did you try to use windows 10.? Sorry I dont have telegram.
Al Djufri said:
Reinstalling python
Reinstalling lib libusb
Changing usb cable
Changing port usb
Change pc, i mean borrow a pc from my friend
Changing spflashtool, same problem sir?
Do you have telegram accountView attachment 5208303
Click to expand...
Click to collapse

XxRRSxX said:
thanks it works thanks for saving my phone
Click to expand...
Click to collapse
Thanks for using this thread as your guide, but credits is to the developers of the Utility.

ATDteam said:
Its not the same in your first screenshot you reach "Disabling protection" but in the 2nd one only the utility found your phone..., did you release all the buttons emmidiately after your computer detects your phone phone? It is important that you release emmidiately. Did you try to use windows 10.? Sorry I dont have telegram.
Click to expand...
Click to collapse
I'm trying to with my friend pc(windows 10) using latest python and same error sir..
Always Immediately release my button when pc detection my device.. but same error

( SOLVED )
you must be use windows 10
Use latest python version
Use latest SpFlash tool version
And don't forget to chek libusb instalation
Check via cmd "pip install libusb" and "pip install libusb1"
And try to use command "python main.py"
Sorry for my English..
Thanks sir..

Al Djufri said:
( SOLVED )
you must be use windows 10
Use latest python version
Use latest SpFlash tool version
And don't forget to chek libusb instalation
Check via cmd "pip install libusb" and "pip install libusb1"
And try to use command "python main.py"
Sorry for my English..
Thanks sir..
View attachment 5208681
Click to expand...
Click to collapse
Nice thats great! sometimes you really need to be on Trial and Error before you achieve what you want. happy for you. Thank you for using my thread as guide, Credits to the developers of the utility. and you have a good english. mine is bad. :-D

Anyone who facing problem when bootrom check, you have to flash first time or it will show error. Otherwise you have to uninstall and reinstall libusb.exe and others.

Ok, thanks to ATDTEAM, very much, I bricked by patching boot image with magisk and flashing it, successfully flashed stock rom .ofp with SP Flash tool, not only this , I itentionally flashed another version , and it worked to, thnx to the bypass utility, it generates questions, the realme provides ozip files, so where are .ofp files coming from, or where we can get it, and... Fawazahmed0 , I am unable to flash twrp, I tried everything I could, I am on updated Android 10 c.19 now, so I can't flash custom recovery or root it... I can't even rollback bcoz I unable to find the older version ofp files, the ozip files just don't install, so please help for rooting Android 10, You have solved a major hurdle by introducing the method of bypass sp tool flashing but, the next step of flashing custom recovery and then rooting awaits... Pls help/ guide, Thnx...

Thanks brother, I've recently unbricked my device

How to unlock bootloader of vivo MTK devices?

Unlocking bootloader on vivo MTK devices
This thread is intended for vivo MTK devices only. However you might have seen some of the threads for unlocking vivo bootloader but it might not work for you. So let's begin our tutorial
!! WARNING !!
THIS STEP WILL ERASE YOUR USERDATA, SO MAKE SURE YOU HAVE BACKED UP ALL YOUR DATA BEFORE EXECUTING THIS​Requirements:
This is needed to make it work!
1. MTK Driver
2. Python (latest)
3. UsbDK
4. MTKClient
5. Zip extractor like 7zip
Set up all the requirements:
1. Install Python
1.1. Open Python that you have download​1.2. Tick a box called "add to PATH"​1.3. Install​2. Install UsbDK
2.1. Make sure you have downloaded UsbDk according to your architecture​2.2. Double click the installation file and install​3. Install MediaTek Drivers
3.1. Download zip that I attach on this thread​3.2. Use your zip extractor app and extract the zip​3.3. After extract, you will see 3 files inside, choose "cdc-acm.inf" and right click​3.4. Select "Install drivers" and follow all instructions​4. Setup MTKClient
4.1. They're many version releases on the github, download the source code zip from the latest version​4.2. Use your extractor app and extract it into a folder​4.3. Go into that folder and open command prompt from there​4.4. Simply type "pip3 install -r requirements.txt" on the cmd and enter. Wait for it to finish​4.5. Close the cmd​
Steps to unlock:
1. Go to mtkclient folder and open cmd from the folder
2. Type "python3 mtk da seccfg unlock"
3. Prepare your phone, make sure it's turn off
4. Connect your phone to PC with volume combination, hold both volume button and connect
5. Hold it until you heard usb connection sound and release it
6. Wait until it succeed
7. If successful, disconnect your device and turn it on
8. You will see a message saying "Orange state bla bla", ignore it
9. If it keeps rebooting, just wait for it to enter recovery and it will ask you to factory reset your device
10. Factory reset it and you're done!
You've finally unlocked your vivo bootloader
Tested devices:
1. vivo Y20 2021/Y12s (PD2036F)
2. vivo Y17/Y15/Y12 (PD1901)
3. vivo Y1s (PD2014F)
4. vivo Y91C (MTK)(PD1818HF)

However vivo have patched the BROM mode(something like download mode on mtk) on the latest update. But I have solution for that issue!

NeonzGamingYT said:
However vivo have patched the BROM mode(something like download mode on mtk) on the latest update. But I have solution for that issue!
Click to expand...
Click to collapse
way

NeonzGamingYT said:
However vivo have patched the BROM mode(something like download mode on mtk) on the latest update. But I have solution for that issue!
Click to expand...
Click to collapse
Seems like you don't?

so i was trying to use mtk client with your command. i'm not sure why my windows don't recognize python3 as installed and redirected me to microsoft store, so i used just python command which should ran python 3.11.2 on my pc. But when i did that it didn't really let me do that saying that "da" flag not found
Code:
mtk client\mtkclient-1.52>python mtk da seccfg unlock
usage: mtk [-h]
{printgpt,gpt,r,rl,rf,rs,ro,w,wf,wl,wo,e,es,footer,reset,dumpbrom,dumppreloader,payload,crash,brute,gettargetconfig,peek,stage,plstage,xflash}
...
mtk: error: argument cmd: invalid choice: 'da' (choose from 'printgpt', 'gpt', 'r', 'rl', 'rf', 'rs', 'ro', 'w', 'wf', 'wl', 'wo', 'e', 'es', 'footer', 'reset', 'dumpbrom', 'dumppreloader', 'payload', 'crash', 'brute', 'gettargetconfig', 'peek', 'stage', 'plstage', 'xflash')
MTK Flash/Exploit Client V1.52 (c) B.Kerler 2018-2021
Also i'm trying to make it work with vivo v25e which uses Mediatek MT8781 Helio G99 (6nm) (if you can believe description)
if i run adb toolkit it shows me this info for my phone
Code:
Device: V2201
Model: V2201
Brand: vivo
Android: 13
Firmware: TP1A.220624.014
Security Patch: 2023-02-01
also this is behaviour for my phone on the 4ths step
4. Connect your phone to PC with volume combination, hold both volume button and connect
Click to expand...
Click to collapse
at first it shows first line in device manager then second and then disappears at all, is this normal behaviour?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there any chances for me to unlock bootloader or i should just give up for now? Also i'm very sorry if i miss something obvious.

twq_bought_a_shit_phone said:
so i was trying to use mtk client with your command. i'm not sure why my windows don't recognize python3 as installed and redirected me to microsoft store, so i used just python command which should ran python 3.11.2 on my pc. But when i did that it didn't really let me do that saying that "da" flag not found
Code:
mtk client\mtkclient-1.52>python mtk da seccfg unlock
usage: mtk [-h]
{printgpt,gpt,r,rl,rf,rs,ro,w,wf,wl,wo,e,es,footer,reset,dumpbrom,dumppreloader,payload,crash,brute,gettargetconfig,peek,stage,plstage,xflash}
...
mtk: error: argument cmd: invalid choice: 'da' (choose from 'printgpt', 'gpt', 'r', 'rl', 'rf', 'rs', 'ro', 'w', 'wf', 'wl', 'wo', 'e', 'es', 'footer', 'reset', 'dumpbrom', 'dumppreloader', 'payload', 'crash', 'brute', 'gettargetconfig', 'peek', 'stage', 'plstage', 'xflash')
MTK Flash/Exploit Client V1.52 (c) B.Kerler 2018-2021
Click to expand...
Click to collapse
i got the same error

First i think if you got vivo device is most likely patched. If not what version of mtk exploit is it using
I see you're using security patch dated 2023-02-01 which most likely won't work

ko_hi said:
First i think if you got vivo device is most likely patched. If not what version of mtk exploit is it using
I see you're using security patch dated 2023-02-01 which most likely won't work
Click to expand...
Click to collapse
honestly i was trying to lock the bootloader just so i won't touch these stuff and my phone is not even vivo it's oppo a5s