Develop Bugs

[RECOVERY][UNOFFICIAL][STABLE&DEV] TWRP [TF300T/TF201] | DISCONTINUED

TWRP for Transformer Pad (compatible with Transformer Prime)​DISCONTINUED​
{
"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"
}
Team Win Recovery Project 2.8, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. TeamWin team started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of their own features. It is a fully touch driven user interface; no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DISCLAIMER : TeamWin team and myself will never ever be responsible for any damages you do to your device !
ALL CREDIT GOES TO AND ONLY TO :
-> TeamWin & omnirom teams (TWRP tree)
-> CyanogenMod team (ROM, device and kernel trees)
-> TheMuppets team (vendor tree)
NOTE : i am not affiliated with any of the teams mentioned above...
INSTALLATION :
=> Option 1 : your device does not have any custom recovery yet ! Please download any of the flashable .zip file below that you are interested in Unzip it and flash recovery.img to your device using fastboot (your tablet must be in fastboot mode [bootloader menu]).
=> Option 2 : a custom recovery has already been flashed to your device ! Please download the flashable .zip file below that you are interested in and flash it from recovery as usual (don't forget to disable .zip signature checking in your current recovery...). From now on (2014-09-01) ALL my .zip files will be signed, so you will be able to flash them with .zip signature checking ON from recovery ! :good:
DOWNLOADS : <= CUSTOM RECOVERY FLASHABLE AND WITH DOCK SD CARD SUPPORT AS EXTERNAL STORAGE
=> STABLE branch : stable ! Includes all upstream merged commits ! EXT4+F2FS <= PLEASE DOWNLOAD LATEST OFFICIAL BUILD FROM TEAMWIN WEBSITE ! THANK YOU !
-> custom TWRP for TF300T (TF201 compatible) [without any device checking] | STABLE ()
=> DEV branch : not as stable as the regular one BUT you can safely flash and use it EXT4+F2FS
-> custom TWRP for TF300T (TF201 compatible) [without any device checking] | DEV () <= NO FILES IN THIS CATEGORY ATM...
=> TRYOUTS : because i do not have a TF300T anymore, ALL releases will be community tested BEFORE they are flagged as working... :good: (do not worry if you decide to test one out, i will give you a procedure below to test it WITHOUT installing it to your device )
PLEASE DO PREFER FILES ABOVE (STABLE & DEV), ATM TRYOUTS ARE STILL THERE AS A FALLBACK ! Thank you !
TESTING OUT A RECOVERY IMAGE WITHOUT INSTALLING IT TO YOUR DEVICE : APPLY ANY CASE :good:
-> unzip any of my zipped recovery images you might be interested in...
-> in the unzipped directory where there is recovery.img, simply input the following fastboot command :
Code:
# fastboot boot recovery.img
:highfive: :good: (your device must be loaded to its bootloader menu [fastboot enabled on it]; if you are using Linux and have adb/fastboot installed on your computer, then the above shell command works as is (you may have to add 'sudo' before it onto Ubuntu / Debian based distributions; if your are using Windows then document yourself on how send properly a fastboot command to your tablet...) =>
Code:
# fastboot -i 0x0B05 boot recovery.img
SHOULD work...
INFO 1 : If you get a failure when flashing from recovery with regular / PhilZ CWM or legacy TWRP, please use the corresponding file WITHOUT device checking... thank you ! :good:
INFO 2 : STABLE branch DOWNLOADS ARE ALSO AVAILABLE FROM THE DOWNLOADS TAB OF THIS PROJECT
INFO 3 : The 'take a screenshot' from recovery feature is now merged upstream, so both STABLE & DEV branches ship with it ! :good:... Simply press 'volume down' + 'power' hardware keys on your device in order to save a screenshot from recovery to your microSD card (files are saved on it to 'Pictures/Screenshots' directory...)
Happy flashing
NOTE : I've started building it for myself, now i'm sharing it ! I use it everyday and still do not have any issue ! Anyway you can feel free to report back Any feedback will ever be greatly appreciated !
PS : Flashing KK ROMs with this recovery is OK (it's its main purpose...), Flashing JB ones has not been tested yet so please report back if anything goes wrong with JB ROMs... Thank you !
NOTE : If you are interested in my work and download my files, please report back AND hit my THANKS button if you think i deserve it ! Thank you !​
PS : TWRP for TF300T is available as two separate download categories : STABLE & DEV branches ! The DEV branch is based off the stable one and is including features that are not available in the STABLE one yet (as upstream merged commits...) ! So the DEV branch is as stable as the STABLE one except for currently previewed features...
Have fun with it :good:​
XDA:DevDB Information
TWRP for TF300T/TF201 [UNOFFICIAL], Tool/Utility for the Asus Transformer TF300T
Contributors
ne0zone75, lj50036
Version Information
Status: Stable
Current Stable Version: STABLE
Current Beta Version: DEV
Created 2014-06-04
Last Updated 2015-02-23

Reserved

ALL my TWRP for TF300T builds are now updated to v2.7.1.0 !
Hello all,
Today i am releasing TWRP 2.7.1.0 builds for both STABLE and DEV branches. Both download sources links (Dev-Host on post number 1 and xda downloads tab) are now updated :good:
You will find TWRP 2.7.1.0 changelog below (grabbed from official TeamWin website) :
What's new in 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Various bugfixes to backup and restore
Improvements to USB storage handling
Added a class to search for files to make finding the correct brightness file automatic in most cases
Various other bugfixes and tweaks
Click to expand...
Click to collapse
Best regards

questions
When go to change file system dont appear f2fs only ext2,3,4 and fat and exfat. What should i do to convert to f2fs? should i convert system and data?
tks

nuno407 said:
When go to change file system dont appear f2fs only ext2,3,4 and fat and exfat. What should i do to convert to f2fs? should i convert system and data?
tks
Click to expand...
Click to collapse
Good afternoon,
F2FS is not supported at all in my TWRP builds for TF300T ATM (kernel side and recovery side) because i really do not know if it is possible to implement F2FS to the CyanogenMod's kernel for TF300T that i am using for compiling the recovery (linux kernel v3.1).
Stay tuned !
Sent from my TF701T

ne0zone75 said:
Good afternoon,
F2FS is not supported at all in my TWRP builds for TF300T ATM (kernel side and recovery side) because i really do not know if it is possible to implement F2FS to the CyanogenMod's kernel for TF300T that i am using for compiling the recovery (linux kernel v3.1).
Stay tuned !
Sent from my TF701T
Click to expand...
Click to collapse
Hey all,
We over at team crombi are working hard to get a CM and Asus based f2fs kernel....
Here is my github of the source code as this one is stock Asus the CM kernel is based off the same thing....
https://github.com/monolithic-droid...mmit/1f898d5b3e15a5681cf4bdfa5c5e3576475d89bd
You are more then welcome to try it out, like I said it needs more testing....
Thx Josh

@ne0zone75 interesting you have 2.7.1.0 working. If i would it from my Omni source tree i get a distorted screen.
Did you change anything in the BoardConfig.mk ?

scanno said:
@ne0zone75 interesting you have 2.7.1.0 working. If i would it from my Omni source tree i get a distorted screen.
Did you change anything in the BoardConfig.mk ?
Click to expand...
Click to collapse
Absolutely not... i am using usual build flags BUT i am picking up recovery dock keyboard layout from local recovery tree instead of device's one... that is the only thing i have recently changed in ' .mk'.
With that said, i am building TWRP along with CM 11.0 sources tree (there is no init.recovery.rc) and i am using 'Official Linaro GCC' v4.7 for recovery + kernel.
Kind regards
Sent from my GT-I9195

scanno said:
@ne0zone75 interesting you have 2.7.1.0 working. If i would it from my Omni source tree i get a distorted screen.
Did you change anything in the BoardConfig.mk ?
Click to expand...
Click to collapse
What do you mean by distorted ?
Do you see two images or does the image slant ?
Thx Josh

lj50036 said:
What do you mean by distorted ?
Do you see two images or does the image slant ?
Thx Josh
Click to expand...
Click to collapse
I am not a native English speaker, so I do not understand what you exactly mean with slant. Only half of the screen is used and it looks like the image is pressed together on the y axes and stretched on the X axes.
The lines are not clear (interlaced)

scanno said:
I am not a native English speaker, so I do not understand what you exactly mean with slant. Only half of the screen is used and it looks like the image is pressed together on the y axes and stretched on the X axes.
The lines are not clear (interlaced)
Click to expand...
Click to collapse
That is very odd... I am sure you are aware of this flag??
RECOVERY_GRAPHICS_USE_LINELENGTH := true -- fixes slanty looking graphics on some devices
Thx Josh

F2FS functionality added to DEV branch ! Update released !
Good afternoon,
I've implemented F2FS ONLY in the DEV branch,... after all this is a testing branch !
To achieve this i've used @lj50036 (from CROMBi-kk team : thank you for your work !) F2FS enabled kernel for TF300T as the kernel of the recovery : THIS PART IS EXPERIMENTAL ! Then i turned ON F2FS support while building the recovery (dedicated TWRP build flag...).
Dev-Host download links are now updated for the DEV branch on post number 1 !
Any feedback on it will be very appreciated BUT please, be very carefull if you decide to test it out ! Thank you !
NB : In order to be able to back F2FS partitions up AND to restore them as F2FS, you will have to back them up when they are already F2FS formatted and after having filled them with data : a backed up EXT4 partition CANNOT BE restored as F2FS and reciprocally !
Very kind regards
PS : F2FS filesystem by itself is probably NOT compatible with crypto ! Please DO NOT TRY to use crypto over F2FS ! Thank you...

iI it possible to iuse this recovery on Memopad HD7 (ME173X)?

bovirus said:
iI it possible to iuse this recovery on Memopad HD7 (ME173X)?
Click to expand...
Click to collapse
Hello,
I will check this out and give you an answer ASAP
Greetings
Sent from my GT-I9195

I asked that because someone explain how to unlock Memopad HD7 and how to load the recovery.
The unlock app it's the same for TFT300
The recovery point to a downlaod link of a file for TF300T
Asus Memopad
Unlock (YouTube vdieo): https://www.youtube.com/watch?v=JUeLp6hkvs0
Asus Unlock APK (v8): http://fs1.d-h.st/download/00033/86c/Unlock_v8.rar
TWRP mod: http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
What's TWRP blob file?
Thanks.

bovirus said:
I asked that because someone explain how to unlock Memopad HD7 and how to load the recovery.
The unlock app it's the same for TFT300
The recovery point to a downlaod link of a file for TF300T
Asus Memopad
Unlock (YouTube vdieo): https://www.youtube.com/watch?v=JUeLp6hkvs0
Asus Unlock APK (v8): http://fs1.d-h.st/download/00033/86c/Unlock_v8.rar
TWRP mod: http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
What's TWRP blob file?
Thanks.
Click to expand...
Click to collapse
Hey mate your in the wrong forum...
You need to start your our, in general and ask for help there not here ...
Its OK that you ask if this recovery would work on your tablet, but this is not a help thread....
Thx Josh

I have both TF300T and Asus Memopad HD7
I already check in ME173X thread and I didn't find any info about recovery.
On internet I found link (posted before) that the recovery for TF300T should be OK for other Asus devices (the bootloader unlock is the same...).
To explain that (not to ask help) I posted the link in previous post.
For this reason i asked it in this thread about TWRP device compatibility.
I believe that could be intersting also for developper if this recovery works with other device to add the device name into the list.
Because if it's true the title can contains also Asus Memopad HD7.
I didn't ask a support about ME173X but just only this specifc recovery.

bovirus said:
I have both TF300T and Asus Memopad HD7
I already check in ME173X thread and I didn't find any info about recovery.
On internet I found link (posted before) that the recovery for TF300T should be OK for other Asus devices (the bootloader unlock is the same...).
To explain that (not to ask help) I posted the link in previous post.
For this reason i asked it in this thread about TWRP device compatibility.
I believe that could be intersting also for developper if this recovery works with other device to add the device name into the list.
Because if it's true the title can contains also Asus Memopad HD7.
I didn't ask a support about ME173X but just only this specifc recovery.
Click to expand...
Click to collapse
Do not worry ! Like i already said i will check your device's compatibility out with my TWRP builds (TF201 is, ME301T seems to...) ASAP BUT i am quite busy ATM...
Now, if it is the case, it will be up to you to unlock your bootloader and then flash the recovery on your own, according to your device's needs and i do think that @lj50036 was meaning that...
Best regards
Sent from my GT-I9195

What do you to add this instruction to help to flash custom recovery first time
- Download the following files and save them to your PC http://www.mediafire.com/?4dx982z93w8z7wk
- Downlaod the TWRP recovery
- Extract the Fastboot.zip file and place the extracted files inside a single folder. You should acquire 4 files, namely:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
- Expand TWRP recovery archive file and rename the downloaded TWRP file as recovery.img (for easier reference).
- Copy or move the recovery.img file to where fastboot.exe is located. You should have a total of 5 files by now.
- Switch off your tablet.
- Boot into Fastboot Mode by pressing and holding down the [Power] and [Volume Down] buttons until you see the message “Press Vol Up to enter RCK”.
- Release the buttons when you see this message and wait for about 5 seconds. A new menu appears. Press the [Volume Down] button to select the USB icon, then press the [Volume Up] button to confirm your selection within 10 seconds, or else your tablet boots into Normal Mode.
- Connect your tablet to your PC via USB cable. Pelase check theat tehd evice is right rcognzied (you should install Asus USB driver)
- On your PC, go to the Fastboot folder and open a command prompt window. You can do this by pressing the Shift key on your keyboard and right-clicking on the empty white space inside the folder, then selecting “Open command prompt here” from the context menu.
- Enter the following command at the command prompt to install TWRP Recovery.
fastboot -i 0x0B05 flash recovery recovery.img
- After installing, disconnect your tablet and reboot.
fastboot reboot

@bovirus
Good morning,
Have you successfully tried this solution for yourself ?!
Now ! Before posting any external download link in MY thread, PLEASE refer to me over PM before doing so ! :angel:
Thank you !
Sent from my GT-I9195

[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

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Redmi Pro

{
"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"
}
I am proud to present first Dualboot project For Redmi Pro. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
What is DualBootPatcher?
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:
I have managed to support for Redmi Pro to the DualBootPatcher App, I am not the creator, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
Disclaimer:
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements:
1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What does the app do ?:
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
What's supported ?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to (eyeul) and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like RR-N-v5.8.3-20170707-omega-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps and Data sharing:
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
Click to expand...
Click to collapse
Other How to ?
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads:
All Downloads Here​Cheers ! we are officially supported ​
Note: You can download any version since "9.2.0.r295.g3b684238"
Screenshots:
No Screenshots, I need some ​
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Redmi Pro Support:
https://github.com/chenxiaolong/DualBootPatcher/pull/707
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Redmi Pro, Tool/Utility for the Xiaomi Redmi Pro
Contributors
yshalsager, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Current Stable Version: 9.2.0.r295.g3b684238
Created 2017-08-19
Last Updated 2017-10-03

Notes
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "omega" || getprop("ro.build.product") == "omega" || abort("E3004: This package is for device: omega; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- To Flash AROMA ROMs flash patched zip from TWRP

Changelogs
-19/08/2017
Initial Release, waiting for adding officially

Much thanks

yshalsager said:
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
2- To Flash AROMA ROMs flash patched zip from TWRP
Click to expand...
Click to collapse
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try

yshalsager said:
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
2- To Flash AROMA ROMs flash patched zip from TWRP
Click to expand...
Click to collapse
daffa ZRN said:
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try
Click to expand...
Click to collapse
Here are the screenshots

yshalsager said:
-19/08/2017
Initial Release, waiting for adding officially
Click to expand...
Click to collapse
Ok now it works but when rebooting to enter secondary rom (using bootUI) it just boots to twrp.
I'm using resurrection remix as the secondary ROM, also when it's flashing (through the app) the message is red not green which means a fail. Maybe the that's the problem. Pls help so I can test it out and report back

daffa ZRN said:
Ok now it works but when rebooting to enter secondary rom (using bootUI) it just boots to twrp.
I'm using resurrection remix as the secondary ROM, also when it's flashing (through the app) the message is red not green which means a fail. Maybe the that's the problem. Pls help so I can test it out and report back
Click to expand...
Click to collapse
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines

daffa ZRN said:
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try
Click to expand...
Click to collapse
You can choose zip using any explorer app like ES File

yshalsager said:
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines
Click to expand...
Click to collapse
Sorry but can you show me how(I'm a noob)

Wow, dual boot patcher stops working when pressing ROMs, I am in a redmi note 3 pro kate, since version 277 no longer works but in 257 down function without errors, someone else happens to this?
Error log:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/kate/kate:6.0.1/MMB29M/V8.2.4.0.MHRMIDL:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 13581, tid: 14315, name: pool-1-thread-1 >>> com.github.chenxiaolong.dualbootpatcher.snapshot <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xdeadbaad
Abort message: 'invalid address or address of corrupt block 0x7fa60f0090 passed to dlfree'
x0 0000000000000000 x1 0000007faf7ba7d0 x2 0000000000000001 x3 00000000007fabf9
x4 0000000000000000 x5 00000000deadbaad x6 0000000000000000 x7 0000000000000010
x8 7f7f7f7fffff7f7f x9 6471656b631f6e73 x10 7f7f7f7f7f7f7f7f x11 0101010101010101
x12 0000007faf7ba7c8 x13 58934240ef78b85e x14 58934240ef78b85e x15 0030f907887041ba
x16 0000007faf7b4a58 x17 0000000000000000 x18 0000007faca2a000 x19 0000007fa60f0090
x20 0000007faf7bb000 x21 0000007fa60f00a0 x22 0000007faf7bba70 x23 00000055995187e8
x24 0000000000000002 x25 0000005599529258 x26 0000000000000000 x27 0000000032e3dbe0
x28 00000055995a5860 x29 0000007f93a7f060 x30 0000007faf753580
sp 0000007f93a7f060 pc 0000007faf753588 pstate 0000000060000000
backtrace:
#00 pc 0000000000047588 /system/lib64/libc.so (dlfree+408)
#01 pc 00000000000195a8 /system/lib64/libc.so (free+20)
#02 pc 0000000000029054 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so
#03 pc 0000000000029224 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so
#04 pc 0000000000011b40 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so (_ZN2mb8format_vERSsPKcSt9__va_list+132)
#05 pc 000000000000abd0 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader11set_error_vESt10error_codePKcSt9__va_list+84)
#06 pc 0000000000009588 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader9set_errorESt10error_codePKcz+108)
#07 pc 000000000000d300 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so
#08 pc 000000000000c96c /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so
#09 pc 0000000000009ed8 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader4openEPNS_4FileE+308)
#10 pc 0000000000009a88 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader13open_filenameERKSs+216)
#11 pc 0000000000011ec8 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmiscstuff-jni.so (Java_com_github_chenxiaolong_dualbootpatcher_nativelib_libmiscstuff_LibMiscStuff_getBootImageRomId+300)
#12 pc 0000000000603934 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/oat/arm64/base.odex (offset 0x35c000)

I've use it for a long time,but i changed my model into Redmi Note 4(MTK) then I can use dualbootpatcher.now pro can use it with out changing model.it's great!:good:

yshalsager said:
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines
Click to expand...
Click to collapse
Ok now I know how to remove those line and I did it, I removed the 1st and the 3rd line.
But now Im facing another fail on flash please help

zhaodelin2002 said:
I've use it for a long time,but i changed my model into Redmi Note 4(MTK) then I can use dualbootpatcher.now pro can use it with out changing model.it's great!:good:
Click to expand...
Click to collapse
You know how to fix my issue?

daffa ZRN said:
You know how to fix my issue?
Click to expand...
Click to collapse
sorry,my way isn't same as yours......

Ivan Torres said:
Wow, dual boot patcher stops working when pressing ROMs, I am in a redmi note 3 pro kate, since version 277 no longer works but in 257 down function without errors, someone else happens to this?)
Click to expand...
Click to collapse
The problem is from app. Not from your device. For me r199 works perfectly. You can use version in this thread also

daffa ZRN said:
Ok now I know how to remove those line and I did it, I removed the 1st and the 3rd line.
But now Im facing another fail on flash please help
Click to expand...
Click to collapse
Remove from starting of file to the end of line 3
The file should be started with "package" line

zhaodelin2002 said:
sorry,my way isn't same as yours......
Click to expand...
Click to collapse
What's your way, maybe I can try

daffa ZRN said:
What's your way, maybe I can try
Click to expand...
Click to collapse
modify build.prop

yshalsager said:
Remove from starting of file to the end of line 3
The file should be started with "package" line
Click to expand...
Click to collapse
Still not working do you have a ROM already modified?

[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