Database Info

[TOOL] AAFC ADB Fastboot Commander - Cross Platform - 0.8.5b (28-06-18)

Code:
*** Disclamer
Be aware that you are able to brick your phone with this tool. I take no responsibility for your actions and/or damage and/or malfunction on your device. If you don't know how to use ADB or Fastboot, read tuturials first. You will be responsible for you actions all alone!
Introduction
Hello guys
Beacause many newbies don't want or to mess with the shell or simply dont know how and experienced users and developers are pretty lazy people i developed a tool which takes over basic actions like flashing/wiping partitions, sideloading zips, push/pulling files, taking screenshots or screen video and a lot more. Of course adb and fastboot commands can be executed as usual over the build-in shell.
Until now its a early beta only able to process basic tasks, not everything works as expected yet.
I've sometimes more, sometimes less time to work on this project, so i cant give etas to future releases!
Click to expand...
Click to collapse
Images
{
"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 to expand...
Click to collapse
Installation instructions
Download the latest build by following the download link down.
Once downloaded, there is no need to install - just run it and you're ready to go
The ADB/Fastboot binaries are packed with the application, no need to download them aftwerwards. However - if you want to use your own android sdk, you're able to change the working path to your sdk.
Click to expand...
Click to collapse
Download
Download the latest version (build 2801) from 15-06-28 here:
> > http://aafc.leonhard-kuenzler.de
Click to expand...
Click to collapse
Changelog
Code:
Changelog:
(sorted by builds)
2776
[fixed] runCommand handling
[fixed] auto device detection
[added] screenshot feature
2778
[fixed] device serial for auto detect
[fixed] screenshot
2779 - 21.05.15
[fixed] icon settings
[deleted] unused code
2783 - 25.05.15
[changed] Gui title
[added] screen recording
2875 - 28.05.15
[fixed] sideload
[added] preferences window
[changed] Frame behavior
[fixed] insert path (drag_drop)
[fixed] sdk not found error
2801 - 28.06.15 | latest build
[added] apk install/uninstall
[changed] device detection
Click to expand...
Click to collapse
FAQ
-- in progress
Click to expand...
Click to collapse
Thanks To/Credits
Code:
all people testing and giving feedback so far :)
XDA:DevDB Information
AAFC Android ADB Fastboot Commander, Tool/Utility for all devices (see above for details)
Contributors
92lleo
Version Information
Status: Beta
Current Stable Version: -
Current Beta Version: 0.8.5
Beta Release Date: 2015-06-28
Created 2015-06-04
Last Updated 2015-06-28

How-To
After downloading:
(1) startup
On first start you will have to read & accept the disclaimer. You're able to turn that message of.
Now the main frame should show up. If you have installed android sdk, you can use yours instead the build in by setting the sdk path in ">SDK>change path" to your sdk path (most likely C:/Programm Files/Android/android-sdk). Select the android-sdk folder.
(2) connecting your phone:
connect your phone to your computer. on phone, go to "settings>developer options" and enable "usb debugging". if there is no "developer options", go to "(device) info>software info" and tap 7 times on "build-number". Developer options should be visible now.
Your phone should now ask you to confirm usb connection to your computer. if not, go on with (3)
(3) driver-troubleshooting
some vendors ship their drivers with windows update, they should be installed on first connect. Google also ships drivers for its devices with the android sdk. In all other cases, unplug your phone and go to ">options>device drivers". Now you have two options: 1. try the easy way universal-usb drivers from clockworkmod. Install them, connect your phone and try again. You may open the
windows device manager (WIN+R > devmgmt.msc), there you should see your device (either with warning, or successful connected) 2. search for the right vendor driver.
Choose from the list and install the drivers. May you also search for lite packed drivers on xda/web.
.. more comeing soon

Bugs & Features
Known bugs:
When starting tool not from its parent directory, but e.g. from chrome downloads, setting paths somehow fails (you'll get an error message). To start, navigate to your download folder and start it from there. If you still face problems, delete the "adbfbdata" folder in the same directory
Video recording/screenshots not working (stuck after pulling screenshot/video)
(This happens cause some devices don't allow to pull or write from/to /sdcard. Working on a fix right now)
When returning to internal sdk, the realSdk variable in the properties file is erroneously set to true, which results in an exception at the next start.
To solve this, delete the properties file in the /adbfbdata folder or set "realSdk" to false
Planned features:
Backup over adb or recovery
Multi-device support
Device specific actions (e.g. unlock bootloader on htc devices)
device info storage (online) for specific actions, downloads links etc.
Fastboot support for samsung devices via haimdall command line tool
workspace monitoring and intelligent file suggestions
A lot of gui improvement

Version 0.8.4 online
Version 0.8.4 (build 2787) is now online.
Changes:
You don't need to fill in your devices serial number from now - whenever a device is detected, its serial will be shown.
Currently, only one device can be handled (except from your own commands).
Tool will automatically search for updates and notify you in case of a newer version. You also can check manually by clicking Options->Check for Updates
Version is ready for download here.

Version 0.8.5 online (multi OS support)
Version 0.8.5 (build 2798) is now online.
Changes:
You now can use AAFC on your Mac, Windows or Linux machine! All adb & fastboot binaries are packed within the tool (even 64 & 32bit versions for some linux distributions) Please note: Support for Mac OSx and Linux distributions is still in early development (alpha) which means, you'll be able to run commands on every os, but may not use every gui function cause the gui is only optimized for windows for now. Please post your experiences in this thead or write me a message!
Tool will modify internal files and watchdogs for the current os
Tool will now delete whole temp folder, not only files
Look and feel changed to "Nimbus" on Linux because of Gui problems. On Windows and Mac OSx its the known OS layout
Version is ready for download here!
Troubleshooting:
If you're not able to tick the checkboxes in the disclaimer frame, check if there is a information dialog behind it. May the UpdateChecker tries to lay over the frame, but the disclaimer cannot be overlaid. I'm working on that.
If you get an exception like "File not found", please post it here (like any other exception). To solve this problem, try deleting the adbfbtool folder in the same directory (to reset the preferences)

Hey,
i tried your tool (build 2798) and really liked it!
I used it on my macbook and it worked well. Sometimes it gives me an exception like "file not found", but after a restart, it works again. I just needed it to flash diffrent recoverys while bringing my phone back to stock.
i would like the tool to remember the last directory i choose a file in, so i dont have to navigate through all my folders again. Also it would be cool, if you implement the shown backup/restore and apk install function. and maybe some quick actions like flashing a recovery with just a file chooser dialog.
I'm looking forward to the next update and will try it then!

friFroAndro said:
Hey,
i tried your tool (build 2798) and really liked it!
I used it on my macbook and it worked well. Sometimes it gives me an exception like "file not found", but after a restart, it works again. I just needed it to flash diffrent recoverys while bringing my phone back to stock.
i would like the tool to remember the last directory i choose a file in, so i dont have to navigate through all my folders again. Also it would be cool, if you implement the shown backup/restore and apk install function. and maybe some quick actions like flashing a recovery with just a file chooser dialog.
I'm looking forward to the next update and will try it then!
Click to expand...
Click to collapse
Hey, thanks for your feedback! The file not found exception will be gone on linux and mac within the next release, it's left from windows-only.
Remembering directories is planned, in fact, i planned to set a working directory/directories, where the tool searches for .imgs and zips and stuff, so it can suggest them.
Quick actions - or something like that- are comeing when everything else is working
APK install is implemented, you're able to use it with the next release, I'm working on backup (both adb and recovery) right now. Maybe it's usable in the next release, or maybe in other future releases.

New Build 2801 (still 0.8.5) online
Build 2801 is now online.
Changes:
You can now install / uninstall apks over the gui with setting command flags
Device detection now start/stoppable
Small GUI changes
Version is ready for download here!
Im currently working on:
Backup over adb or recovery
Multi-device support
Device specific actions (e.g. unlock bootloader on htc devices)
device info storage (online) for specific actions, downloads links etc.
Fastboot support for samsung devices via haimdall command line tool
workspace monitoring and intelligent file suggestions
A lot of gui improvement
If you miss something or have other feedback, feel free to contribute!
_____
edit:
looks like there is a bug in screenshot/video recording, it doesn't work in older versions as well. You may try it, but it wont work. I'll fix it with the next release!

[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!
​
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename 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.65 (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.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.
​
[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 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 in your tool?
Follow the instructions in 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 terminal to find out what you're missing from your environment.
Q: I have an 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 it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
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) untill you get the 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 entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others 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 GPL v3 licence 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, full 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, as well as 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!

Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc

Getting an error
FAILED(remote: oem unlock is not allowed)

Skies/SANKE said:
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Click to expand...
Click to collapse
Well, I've looked at your edit and I don't understand what looks better than mine... It might be subjective though...
Pikezer1337 said:
Getting an error
FAILED(remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Will investigate this problem and I hope I will get a solution fast
Edit: The information from this link might help with your problem.

I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?

paOol said:
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
Click to expand...
Click to collapse
The problem should be fixed in the V0.2, the Linux and MAC versions are not tested before posting, so bugs could still be around there...

added to index

Hi all, imusing linux and just tried to unlock my 5X. it worked but my question is, it is normal that it formated automatically?
after reboot, i have to start all over again with my account and setup.

Yes it's normal

Thanks mate, I'm new with nexus devices. One last thing, do I have to locked again or its OK leave it like that since on every reboot its showing me that I'm unlock. Sorry and thanks
Sent from my Nexus 5X using Tapatalk

You can leave it like that as long as you can deal with that message on every boot. If you lock it, you would have to unlock (and wipe) again if you ever want to flash anything again. Personally, unless you want to stick with the stock ROM OTAs, I'd leave it unlocked.

Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?

Born<ICs said:
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Click to expand...
Click to collapse
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.

Lexmazter said:
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Click to expand...
Click to collapse
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks

Born<ICs said:
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Click to expand...
Click to collapse
To be honest I never locked my bootloader, didn't found a reason to, so I didn't tested.
But technically speaking, the only thing that happens is that you cannot flash other custom recoveries (fastboot stuff basically) without unlocking again and wiping all the stuff on your device.

OK, thank you. ReLocking to flash factory image was what I was thinking. I read doing so can lead to bootloop. Just trying to make note of things to avoid doing.
Cheers

You can lock and unlock your bootloader as much as your heart desires without consequence

skulldreamz said:
You can lock and unlock your bootloader as much as your heart desires without consequence
Click to expand...
Click to collapse
Well, wiping your data partition can be a pretty big consequence...
-edit-
You used to be able to use BootUnlocker for Nexus Devices to lock and unlock the bootloader from within the OS, but it looks like that's a no-go on the 5X...

I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?

owenrg said:
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
Click to expand...
Click to collapse
You will definitely lose root. I don't know about the bootloader since I've never taken an OTA, but I would guess that, unless there are bootloader changes in the update, your bootloader would stay unlocked. And to my knowledge the bootloaders are pretty much never updated for incremental OTAs.

[ROOT][TWRP][OUTDATED] Oppo R9S (China edition) exploit and TWRP flasher

This tool is out of date. See the main R9S thread for an updated tool by Wu Xianlin which gives you an improved TWRP recovery and access to more ROMs.
Original post is below for historical purposes only.
Oppo R9S (Chinese version) TWRP installation tool
Only works on Chinese OS release 005 which can be downloaded here and flashed in stock recovery.
Earlier versions will not work, nor will later versions. It has to be this specific version.
P̶r̶o̶b̶a̶b̶l̶y̶ doesn't work on international editions either.
DOWNLOAD - R9S_TWRP.zip - V1.01
DOWNLOAD - R9S_TWRP.zip - V1.0
Changelog
1.01 - Tweaked timings to try and improve success rate
1.01 - Changed how text is output to hopefully improve appearance on Windows 7
This script uses an exploit by Chinese developer Wu Xianlin to gain temp root, then it flashes his TWRP build that works on the R9S despite the locked bootloader.
From there you can attempt to perma-root your phone, install a custom ROM etc. etc.
Thanks to the following XDA members, without whom this would not have been possible:
jacksmack
celoxocis
{
"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"
}
Antivirus issues
Some AV's may complain about this file containing a Trojan. They are technically correct. It's called "dirtycow" and is being used in the wild to hack into Linux systems. It cannot affect Windows systems, but I use it to hack a linux-based system (your phone)
If your AV refuses to let my script run you will have to disable it temporarily. Feel free to read through my script (root1.bat) to check what it is doing.

Useful things to flash in TWRP
CyanogenMod13 - by Wu Xianlin
Stock Recovery - by Wu Xianlin
GApps (ARM64) - by opengapps.org
Updated basebands, ripped from ColorOS
Use these only if you have issues with phone/GPS/etc. after installing CM. Otherwise leave alone.
[2017-01-11 v0180] - released ROM (China) - by me!
[2017-01-24 v1470] - ALPHA ROM (China) - by me!
Note: The version number on basebands stays the same, but the MD5s are different. No idea what has changed, but they work!

Unbrick instructions:
Does not work in Windows 10. Tested working in Windows 7
Download this unbrick package
Install the quallcommmtkdriver package
Run daanav-enabler as administrator
Run msmdownloadtool as administrator
Click through any timeout error you get
Click on the titlebar of MSMDownloadTool and press F6 to enable the options
Fully power down your phone by holding vol-, vol+ and power for 10 seconds
Hold vol- and vol+ while connecting the USB cable (use the stock Oppo cable)
MSM should now show your phone.
Press F5 to decide what to flash. For the first attempt choose "All except userdata".
Click the start button.
After 5 minutes your phone should reboot into ColorOS.
If ColorOS hangs on boot, then repeat the above staps and this time flash all, including userdata. This will wipe your photos etc. sorry!
This will leave you on V004 of the OS. You will need to upgrade to 005 before attempting to root again.

Can I request a version of this that stops at permanent rooting? Unless you think there would be a problem with the fact that I intend on using it on a r9s plus.
Or a link to what I maybe overlooked, in case it already exists.

Unfortunately this program doesn't perma-root. It gains a temp root and uses that to flash TWRP. TWRP can then be used to flash a custom ROM or a rooting tool.
It also doesn't unlock the bootloader. Wu Xianlin somehow managed to make a version of TWRP that the locked bootloader is happy with!
however if you edit root1.bat and scroll down to line 181. Change it from:
Code:
type root3.txt | adb shell /data/local/tmp/root2.sh
to:
Code:
adb shell /data/local/tmp/root2.sh
Then the script will just drop you to a root shell. Unfortunately you are then on your own as to how you get perma-root.
I have no idea whether this method will work on the R9SPlus. In theory it should do but I've not tried it. I won't be held responsible if you brick your phone and probably won't be able to help, though you should be able to do a three-finger reboot and then boot into recovery and reflash ColorOS.
Optional modifications you can make that will make the script neater:
You can also remove lines 178 and 179
Code:
echo Copying TWRP
adb push r9s-twrp-3.0.2.0-20170107.img /sdcard/twrp.img
and change line 184 from
Code:
pause
REM ---- CHINESE TWRP HELP ----
to
Code:
pause
exit
REM ---- CHINESE TWRP HELP ----

I will take your "I have no idea if this will work fo r9s+" at face value and try to be patient for something more certain, thanks for your contribution nonetheless
I saw the translation you posted and am a bit depressed Wu recommended to return the phone...

Oppo make amazing hardware but terrible software that is never updated. I used to be ok with this because they actively encouraged rooting and custom ROMs but this change in attitude from them makes it very hard to recommend the phone.
I would be interested to know if this exploit does gain root on the Plus. In theory it should work, and there's also a decent chance that TWRP will too as the hardware is very similar, but will require someone very brave/stupid to try it

BTW. Anyone who is going to try this on the Plus. Ensure you have a flashable .ozip of a working ColorOS (full install, not OTA) saved to internal storage as the stock Oppo recovery is a POS that doesn't provide ADB, MTP or USB.
If you end up wrecking your OS and don't have that image in place ready to flash from recovery you are screwed.
Likewise do not flash TWRP until you are sure that your OS is still bootable, and also take a dump of the stock recovery first! (and post it in the other thread as it's bloody useful to have!)
Sent from my OPPO R9s using XDA Labs

Hi the Unbrick pack RAR is corrupted and can not unzip.
Also there is Trojan in DOWNLOAD - R9S_TWRP.zip - V1.0 - Dirtycow file and the NOD Antivirus is deleting this file.
Please advice how to proceed ?

NOD is correctly detecting that this is a hacking tool using a well known exploit (dirtycow).
Since you actually want to do that, you're going to have to disable NOD until you're done.
Sent from my OPPO R9s using XDA Labs

Lum_UK said:
NOD is correctly detecting that this is a hacking tool using a well known exploit (dirtycow).
Since you actually want to do that, you're going to have to disable NOD until you're done.
Sent from my OPPO R9s using XDA Labs
Click to expand...
Click to collapse
Hi I got to somewhere but I am stuck now...
Please check the pic and advice how to install the CyangenMode. (I have uploaded the pic in your thread in Oppo Community forum please check it there because I am new here and can not post with external links..)
Sorry for the inconvenience. Looks like I am few steps away to finish the job but something is missing...

Goro1234’s image: http://s27.postimg.org/8usudi9g3/IMG_20170207_133854.jpg
You need to do a wipe data/cache/dalvik as CM won't install on top of incompatible data.
Note that this will wipe your installed apps, settings, app data, saved games etc. but will not wipe your photos, music, downloads or anything else saved to internal storage.
You may wish to take a backup from within TWRP first. Apps like Titanium Backup and Nandroid Manager are reasonably good at restoring apps and data from a TWRP backup.
Also don't forget to install GApps
Sent from my OPPO R9s using XDA Labs

For the unbrick package you need 7-Zip to extract it.

Lum_UK said:
`Also don't forget to install GAaps`
Hi I am on Cyanogen now !!! Thanks for the help. Can you please tell me now which is the correct gapps version for our device. I have installed random one which does not make connection with google. I have tried to install ARM 64, but cant flash because systems says that is incompatible... Thanks
Click to expand...
Click to collapse

Select ARM64, android 6.0 and whichever variant you like (I recommend the Pico version)
Sent from my OPPO R9s using XDA Labs

Sorry for the English, I made a mess with the phone, after unlocking everything, and held the phone for several days with CM13, I saw that GPS was not working, so vovelo return to the origin, but now I can not installing Stock Recovery more to put the stock rom, I tried to do unbrick, but when I press start of msmdownloadtool, the program stops and closes. If some kind soul gives me some advice. Done everything under win 7 reset. Thank you so much Gianfranco.

GPS should be working. I'm using it all the time on CM13 as my phone is my satnav.
Maybe wipe and reflash, or try one of the baseband updates?
Sent from my OPPO R9s using XDA Labs

Now, the problem is more to do so that I can not leave,
I installed through the files Stock TWRP Recovery as a boot, and I hand the boot source and installing the original rom, after the reboot remains on oppo screen. what can I do. Thank you so much Gianfranco.

hold all three buttons for 10 seconds to forceibly power off the phone and then try to boot to recovery.
If you get the Oppo recovery then try to do a factory reset and then flash the stock ROM,
if you get TWRP then try to flash Cyanogen.
If you can't do either then you're going to have to run the unbrick tool. Do you have another PC you can try it on?

Thanks, but I have tried various solutions, when I install the boot ROM from stock, is successful, the reboot hangs installation applications. I wanted to know if you can other software for unlocking. Thank you very much for giving me some advice, thanks ancora.Gianfranco.

TWRP-3.4.0.0 for Ulefone Armor X5 (aka Bretzel)

{
"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"
}
TWRP FOR Ulefone Armor X5​DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION
- Go to developer settings and turn on OEM unlock
- Power off the phone and boot to fastboot mode (power and volume +)
- Open a comand prompt and type:
Code:
fastboot flashing unlock
All the data will be loss
- Confirm the oem unlock by pressing the volume + button
- And now type:
Code:
fastboot reboot
- When the phone is turned on, and you complete the setup wizard, type:
Code:
adb reboot bootloader
- When fastboot mode appears in a corner of the phone, type the following command:
Code:
fastboot flash recovery recovery.img
- Now Boot into TWRP, and format data, and reboot to system
If you wanna root it:
- When you are at TWRP and you have formatted data, flash Magisk by sideload
- And reboot to system
Sources:
Device Tree
Download:
TWRP v1
TWRP v2
TWRP v3
Thanks to [Alphabetical Order]:
* Hadenix
* Maanush
* R0rt1z2
* SebaUbuntu

Just a note: This is NOT for the newer mt6765 Android 10 Q phone, If your fone is android 10 Q it will NOT work.

Pachacouti said:
Just a note: This is NOT for the newer mt6765 Android 10 Q phone, If your fone is android 10 Q it will NOT work.
Click to expand...
Click to collapse
Hi
How are you?
My variant is MT6763 one, if you want open pm and we will work for make TWRP for MT6765 variant.
Thanks!

A Only
Thanks dude, but my phone is an 'A' only partition, and as far as I'm aware, only johnwu's phone has actually been done, his being 'A' Only... He made a magisk for his 'A' only phone, but it dont work on mine. To see my firmware, just look at the ulefone stock firmware for android 10_Q, you'll find all you need there... ? It's an armour x5, aarch64, meaning 64bit only I think...
Tried everything I know of, and I do know a bit so not shy in testing any files, I am a competant programmer electronics style, flashing chips etc, so no prob re-flashing errors etc
Edit google johnwu 'A' only and you'll see why its not been done yet... whoever does it will create root for what is coming for all fones...!

X5 pro variant
FYI, this method isn't working on Ulefone Armor x5 Pro variant. (MT6765 - Android 10) Dont know why, but it causes bootlop. Reflashing stock boot img restores the phone functionality (without TWRP obviously). As i'm a new user, i can't post the link to the stock Boot and Recovery images, but if anyone needs them for porting, feel free to PM me.

It wont work because android 9 is the old version of 64bit capable of running 32bit apps, android 10 is pure x64bit. The bootloader is NOT the bootloader anymore, but a preloader, loading BEFORE the bootloader. so flashing bootloader over preloader causes bootloop, makes sense dunnit?
All fones will soon adopt this, and it has already started, since johnwu was bought by apple, and will be made too busy to produce anything anymore, by design of course, and since this new version of a only partitioning has been succesfull in thwarting him, no more root for you. Now you get another file system running on top of your unrootable fone to make you think you have root, pretty much sums it up, this overlayfs...
Shows how good the devs really are nowadays, when nomoretech (hovatek) found out his work dont work on android 10, he ignored my thread, too busy with old android 9 for old fones. upgrade, update, move on, say 'tata root'....

thanks good job on android 9

jmpf_bmx said:
TWRP FOR Ulefone Armor X5​DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION
- Go to developer settings and turn on OEM unlock
- Power off the phone and boot to fastboot mode (power and volume +)
- Open a comand prompt and type:
Code:
fastboot flashing unlock
All the data will be loss
- Confirm the oem unlock by pressing the volume + button
- And now type:
Code:
fastboot reboot
- When the phone is turned on, and you complete the setup wizard, type:
Code:
adb reboot bootloader
- When fastboot mode appears in a corner of the phone, type the following command:
Code:
fastboot flash recovery recovery.img
- Now Boot into TWRP, and format data, and reboot to system
If you wanna root it:
- When you are at TWRP and you have formatted data, flash Magisk by sideload
- And reboot to system
Sources:
Device Tree
Download:
https://github.com/jmpfbmx/android_...eleases/download/twrp_bretzel_v1/recovery.img
Thanks to [Alphabetical Order]:
* Hadenix
* Maanush
* R0rt1z2
* SebaUbuntu
Click to expand...
Click to collapse
Hi,
We try to install it on a Armor X5 with android 9, build Armor_X5_MH1_EEA_V01 and all we have is a green line in the top of the screen then the phone reboot...
Is it many hardwares for the same phone ?
Thank you

wargreen said:
Hi,
We try to install it on a Armor X5 with android 9, build Armor_X5_MH1_EEA_V01 and all we have is a green line in the top of the screen then the phone reboot...
Is it many hardwares for the same phone ?
Thank you
Click to expand...
Click to collapse
Hi,
Can you share a pic of the screen?
Can you try to use adb? (Try adb shell, if works make this, adb shell cat /tmp/recovery.log, and send me the file by here)
Thanks
Regards
Jose

Tomorrow you will have a huge update of TWRP and some news about A11 hehe

"- Now Boot into TWRP, and format data, and reboot to system"
Could you explain exactly How to do this, please
bootloader activated, do I hard reboot pressing power and vol+, and when do I stop pressing ?
thanks
ulysse

"- Now Boot into TWRP, and format data, and reboot to system"
Could you please explain exactly how to do this ?
Bootloader activated, Do I press power and vol+ and keep then pressed ? until what ?
thanks a lot
ulysse

ulysse_21 said:
"- Now Boot into TWRP, and format data, and reboot to system"
Could you explain exactly How to do this, please
bootloader activated, do I hard reboot pressing power and vol+, and when do I stop pressing ?
thanks
ulysse
Click to expand...
Click to collapse
Hi
How are you?
Have you got Bootloader unlocked? (Idk wdym with bootloader activated)
For do that you just need to flash TWRP, reboot phone pressing vol+ and power as you say and when TWRP boots, just go to Wipe -> Format Data (Type yes) and then when the format data has finished, clic on reboot to system

TWRP Updated!
Now MTP and ADB are working better!!

thanks, i try
ulysse

jmpf_bmx said:
- When the phone is turned on, and you complete the setup wizard, type:
Click to expand...
Click to collapse
I start in Engish , skip connect to mobile network (no sim), skip WI-Fi, adjust good date and time, without "use location" and without "send usage and diagnostic data"; acept; "not now" for "protect your phone"
Then I activate the developper mode and in "system/ options for developers" I turn on USB debogage.
Did i miss sommething at this stage ?

jmpf_bmx said:
Can you try to use adb? (Try adb shell, if works make this, adb shell cat /tmp/recovery.log, and send me the file by here)
Click to expand...
Click to collapse
Hello thanks for your help.
Phone powered on, I can go on "Armor_X5:/ $ " if I type "adb shell".
but I don't understand "adb shell cat /tmp/recovery.log,"
I have "cat: tmp/recovery.log: No such file or directory"
appologize for my low level in English and in computering, I write code more on ImageJ and Rstudio.

ulysse_21 said:
I start in Engish , skip connect to mobile network (no sim), skip WI-Fi, adjust good date and time, without "use location" and without "send usage and diagnostic data"; acept; "not now" for "protect your phone"
Then I activate the developper mode and in "system/ options for developers" I turn on USB debogage.
Did i miss sommething at this stage ?
Click to expand...
Click to collapse
Did you opened bootloader?

ulysse_21 said:
Hello thanks for your help.
Phone powered on, I can go on "Armor_X5:/ $ " if I type "adb shell".
but I don't understand "adb shell cat /tmp/recovery.log,"
I have "cat: tmp/recovery.log: No such file or directory"
appologize for my low level in English and in computering, I write code more on ImageJ and Rstudio.
Click to expand...
Click to collapse
I guess that you aren't at recovery, or you didn't disable and enable MTP

Pachacouti said:
Just a note: This is NOT for the newer mt6765 Android 10 Q phone, If your fone is android 10 Q it will NOT work.
Click to expand...
Click to collapse
It works in mt6762 Android 10 version? model Armor_X5_Q_EEA

[ROM] Modified Stock Android 11 (Go Edition) ROM for KonnectONE Moxee m2160 (MH-T6000) 4G-LTE

Android 11 (Go Edition)
Modified Stock ROM​
{
"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"
}
Assurance Wireless
KonnectONE Moxee m2160
4G-LTE Smartphone
Model No. MH-T6000​
OVERVIEW:
This is a heavily modified build of the stock Android 11 (Go Edition) ROM which comes preinstalled on the KonnectONE Moxee m2160 smartphone. Please note that, while flashing this ROM will not network unlock your device, the ROM does include added support for most GSM based providers on devices which have previously been network unlocked.
In a nutshell, this modified build focuses on the removal of bloatware and a slimmed-down, more responsive stock OS experience. In addition, once installed, the ROM supports full R/W mounting of all logical partitions encompassed within /super. (The unmodified stock ROM, notwithstanding Magisk systemless root, restricts proper R)W mounting of these partitions due to the stringent codebase changes which implemented the dynamic partition scheme back with the release of Android 10.) This ROM also disables force encryption to /userdata (DFE), disables AVB/dm-verity, and includes several mods for improved performance and responsiveness. While certainly nothing special in terms of custom development for the Moxee m2160, this ROM should provide users with a sufficient daily driver ROM with an optimized stock feel.
FEATURES & BUILD INFO:
• Based on firmware build MH-T6000V1.0.0B010
• Kernel version: 4.19.157-perf
• Security patch level: March 5, 2023
• GMS version: 11_202111.go
• VNDK version: 30
• Quick boot sequence
• Systemless root via Magisk v26.1
• Enabled Power Stamina mode for better battery life
• /system mounts R/W
• /system_ext mounts R/W
• /product mounts R/W
• /vendor mounts R/W
• Force encryption of /userdata disabled (DFE)
• OTA notifications & persists disables
• AVB/dm-verity disabled
• Stock launcher locked in memory
• Zipaligned /system/app & /system/priv-app
•Zipaligned /system_ext/app & /system_ext/priv-app
• Zipaligned /product/app & /product/priv-app
• Custom TCP congestion algorithm presets
• Heavily debloated w/minimal Google framework
• Kernel level performance optimizations
• Google Pixel 2 dark bootanimation
• Optimized RAM management
• Schedutil tuned CPU governor parameters
• Enabled fast charging (1100 mAh stable)
• GSM support for network unlocked devices
PREREQUISITES:​
An unlocked bootloader ​
A PC or laptop running on Windows 7, 8.1, 10 or 11​
Smartphone must be running Firmware Build No. MH-T6000V1.0.0B010​
The SDK Platform Tools on your Windows computer (link provided below)​
Installation of the proper ADB & Fastboot device drivers on your Windows computer​
The factory supplied, or a quality sufficient, USB-A to USB-C syncing/charging cable​
A reliable internet connection for downloading the required files ​
NOTE: We will not be using a custom recovery for installation of this ROM, but rather the dynamic user space implementation of fastboot mode, formally called FastbootD. This fastboot protocol was first introduced with the release of Android 10, and is primarily utilized for the management of dynamic partitions (devices with a /super partition).
DISCLAIMER:
This guide involves the invasive procedure of flashing the partitions of your device, thus modifying the configuration of the device from its factory stock state. This is always inherently risky to the integrity and operability of your mobile device. By proceeding further, you are assuming sole responsibility for the functionality and physical wellbeing of your mobile phone, thus absolving me of any liability in the event things go badly. This ROM has, however, been tested thoroughly on my own device with no negative issues. Moreover, in the unfortunate event your device becomes bricked or otherwise inoperable by way of a botched adherence to this guide, my firmware restoration guide for this device can restore both soft and hard bricked phones. Moxee m2160 Unbricking Guide
INSTRUCTIONS:
WARNING:
These instructions include steps for initiating a factory data reset, a procedure which will effectively erase all saved user data, app data, app preferences, photos, videos, music, documents and other media files from your smartphone. Make a backup at this point of all data, files and media that you wish to preserve.​
Download the SDK Platform Tools from the link below and extract the contents of the archive to an empty folder on the desktop of your Windows computer​
Download the ROM from the link below and extract the contents of the archive to your platform tools directory created in the previous step​
Because this ROM has been modified to disable DFE force encryption, it is first necessary to format the /userdata partition. With your phone in a powered off state, press the Volume Up & Power keys simultaneously until the Moxee logo appears on your display, at which time you should release the Power key, but continue holding Volume Up until an Android logo and a corresponding No Command notification appears on your phone display. Now quickly press and hold Power, tap Volume Down and then Volume Up to enter stock recovery mode.​
Use the Volume Down key to navigate to the Wipe data/factory reset option, then press Power to select. Confirm this selection on the next screen to initiate the factory data reset.​
Once the factory reset is complete, navigate to the option to Enter Fastboot, then press Power to select. Your phone should now boot to FastbootD mode.​
In the platform tools folder created in the first step, click on cmd-here.exe, then right click and opt to run it as an administrator. A command window will be launched. Now connect your Moxee m2160 to your Windows computer using a sufficient USB-A to USB-C data syncing/charging cable.​
In order to verify proper fastboot communication between your phone and PC, execute the following command:
Code:
fastboot devices
If properly connected, the command window will yield an alphanumeric value consistent with your mobile phone serial number.​
Execute the following commands once a proper fastboot connection has been verified. Note, the user may copy these commands and paste the full text to the fastboot command window for systematic execution:​
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.patched.img
fastboot flash vbmeta_system vbmeta_system.patched.img
fastboot flash vbmetabak vbmetabak.patched.img
fastboot flash vbmeta_systembak vbmeta_systembak.patched.img
fastboot erase super
fastboot flash super super_rw.img
fastboot erase metadata
fastboot erase cache
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
** Please note that the super_rw.img file is large in size. Fastboot may initially give a header magic notification error. However, the super_rw.img will then be allocated into a number of smaller sparsechunk files, which will subsequently be flashed to your device one at a time, until complete. Just remain patient during this process. This can take five minutes or more, but the process will not require any user action.​
Upon first reboot following installation, and after completing initial device setup, open your app drawer and search for the Magisk app or its stub placeholder. Open Magisk, grant any requested permissions, and follow any prompts by Magisk to update the version or complete setting up the root environment. If you do not see the Magisk app or stub, download the Magisk v26.1 APK from the link provided below and install the app on your phone. Be sure to then open Magisk and follow all prompts.​
DOWNLOADS:
• SDK Platform Tools r34.0.3
• Modified Stock ROM Package
• Official Magisk Releases / GitHub Repo
BUGS:
Please report any bugs or instabilities you may encounter using this modified stock ROM. Those who know how to submit an official bug report are urged to do so. Otherwise, please give a concise and detailed description of the issue, including photos or screenshots if possible. I will work diligently to patch any reported bugs or instabilities.Moxee m2160 Firmware Restoration & Unbricking Guide​

Instructions were great and I had no problems following them. I did have an error when I first entered the command "fastboot erase DDR" but only because I did not capitalize DDR. My only issue is I cannot get past the phone set up when first booting because it says there is an update and can not pass verification and there is no option to skip. And in my case I don't have a computer still so cannot use qfil to return to full stock to update. Any suggestions?

scottfan81 said:
Instructions were great and I had no problems following them. I did have an error when I first entered the command "fastboot erase DDR" but only because I did not capitalize DDR. My only issue is I cannot get past the phone set up when first booting because it says there is an update and can not pass verification and there is no option to skip. And in my case I don't have a computer still so cannot use qfil to return to full stock to update. Any suggestions?
Click to expand...
Click to collapse
Okay. At the time I completed modifications on the ROM, the latest OTA had not yet rolled out. What I'll do is add another mod to kill the OTA service entirely. That should prevent any issues like you're facing. I'll expedite this task and will let you know just as soon as I've made the fix and changed out the ROM file with the new one. Thanks for your feedback. By the way you won't have to repeat the process, but will only need to flash the super_rw.img file.
Update: I have disabled system updates and OTA notifications. Proved trickier than I thought, since system updates on Android Go Edition are governed by Google Play Services. I had to decompile the Google Services apk, manually disable the individual system update service and listeners, then recompile and reinstall the Google Services core app. I am presently uploading the new super_rw.img.
One thing that should work for you in the meantime, while I get these new files uploaded, is to perform another factory data reset. During initial boot and setup, opt to complete setup offline, without connecting to WiFi or a mobile data network. Accordingly, your device will not be able to check for pending system updates and you should, therefore, be able to complete setup.

Viva La Android said:
Okay. At the time I completed modifications on the ROM, the latest OTA had not yet rolled out. What I'll do is add another mod to kill the OTA service entirely. That should prevent any issues like you're facing. I'll expedite this task and will let you know just as soon as I've made the fix and changed out the ROM file with the new one. Thanks for your feedback. By the way you won't have to repeat the process, but will only need to flash the super_rw.img file.
Click to expand...
Click to collapse
That would be awesome. I really appreciate your help.

scottfan81 said:
That would be awesome. I really appreciate your help.
Click to expand...
Click to collapse
The files should be finished uploading within the next 15 minutes or so. I will then update the download link and will inform you here when that's done.

@scottfan81, the latest files are uploaded and the download link has been updated accordingly.

Viva La Android said:
@scottfan81, the latest files are uploaded and the download link has been updated accordingly.
Click to expand...
Click to collapse
That's great! I just got done with my dinner and going to download it now. I will let you know how it goes. And I did see that I only need to flash the super_rw.img file. So I should know shortly.

scottfan81 said:
That's great! I just got done with my dinner and going to download it now. I will let you know how it goes. And I did see that I only need to flash the super_rw.img file. So I should know shortly.
Click to expand...
Click to collapse
Do a factory reset beforehand. Then flash the super_rw.img

@Viva La Android
I haven't had any luck since my last post. Before I posted about the verification issue I had when setting up my phone I made sure I double checked that I did not have the option to skip the update as you suggested. That was not an option for some reason and that is when I came here. I have followed your steps with the new super.rw.img you updated but I am worse off than I was before. Now I cannot do anything as the phone is not recognizing any network or available WiFi connections. I have tried a factory reset and started over from your first step with no success. I should also include that since flashing the updated super.rw.img file, when the phone first boots the screen quickly flashes black and blue for about 10 seconds before finally starting the set up process then I get 2 error messages. The first being "system UI isn't responding" and second "Android setup keeps stopping" After all of that the setup starts and that's as far as I can go because I can't connect to anything. Trying to give you as many details I can think of. Before the screen flashing when powering on the phone, the boot animation just function properly. Only between the boot animation and setup process do I experience the rapid black and blue screen for roughly 10-15 seconds. I am including some screenshots of the error messages and setup screens showing no connections available. I almost forgot. I also tried manually adding my network and scan qr code with no success.

Unfortunately I have physically damaged my device beyond any hope of restoring it, so I won't be able to support this device any longer -- until & unless I can get a replacement display. But before my device went kaplut, I did test this ROM and had no issues. I wish I could be more help.
I would recommend performing all steps over again from the top -- formatting /userdata before doing anything. Have you tried by completing all the steps over?