{
"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"
}
Disclaimer: I'm in now way, shape or form a developer. The following steps are to be used as a guideline for installing nethunter onto your device. If something goes wrong during the install/set up process, I won't be held responsible. By installing the roms/nethunter zips you're voiding your warranty so do so at your own risk.
Click to expand...
Click to collapse
Nethunter is in short a set of apps for network penetration testing, you should only use these tools for testing your own network security or other networks YOU HAVE PERMISSION FOR! If you get caught using these tools illegally, do not come crying to me, I'll laugh in your face and point you to this thread.... That being said, let's get on with it.
You're going to need a rooted device for this to work, this thread isn't about rooting, if you're not yet rooted check out the other threads on XDA. Great community with plenty of topics showing you how to root. You have the options of:
cm-13.0 running on Marshmallow with kernel 3.4.111
Lineage-14.1 running on Nougat 7.1.2 with kernel 3.4.113
Both have fully patched kernels and whilst they all have a few issues (not related to the kernels or the first rom you install, check known issues below for updates), you should be able to use 99% of the functions. I'll list the issues at the bottom of this post and the steps to try and fix them if any.
Links
Cm-13.0 links:
CM-13.0: https://www.androidfilehost.com/?fid=817550096634766544
Nethunter: https://www.androidfilehost.com/?fid=529152257862723757
Lineage-14.1 7.1.2 links:
Lineage14.1:https://www.androidfilehost.com/?fid=529152257862728021
Nethunter:https://www.androidfilehost.com/?fid=529152257862723623
Install
Download and copy both of the above files to the root of your device along with the Gapps of your choice.
Reboot into recovery and wipe Dalvik, Data and Cache
Install the CM-13.0/Lineage-14.1 rom
Install Gapps
If you're S-off then reboot into your phone.
If you're S-on, extract the boot.img from the CM-13 file and place it in your fastboot folder.
Run the following command and reboot: fastboot flash boot boot.img
After the boot.img has flashed, run the following command: fastboot reboot
After you've allowed your phone to boot fully, reboot back into recovery and install the nethunter file.
Be PATIENT!! The install can take up to half hour! Once the install has finished, reboot system and you should be golden.
If at any point during the install process TWRP asks you if you want it to install root, select the "Do not install" option. Nethunter will handle this for you.
That's it, you should be fully loaded with nethunter.
Features
HID is fully functioning on both versions.
Supported external wireless drivers are fully functioning. Check the useful links below to find supported devices.
Csploit
DroidDrive
Hackers Keyboard (This comes in so handy when using terminal)
Nethunter VNC
Nethunter Terminal
OpenVPN
Shodan
USB Keyboard
Known issues
Unless stated otherwise, any issue related to lineage-14.1 applies to both the android 7.1.1 version and the 7.1.2 version
Csploit on CM-13.: For some reason, nethunter installs an outdated cSploit for the marshmallow build. If you constantly receive an error message saying "No exploits found", uninstall cSploit and install the latest version from here: http://www.csploit.org/downloads/
cSploit arp poisoning on both cm13 and lineages14: Arp poisoning exploits aren't working for any MITM attacks, I've spoke to the devs and they've confirmed it is a bug, as soon as it's fixed, I'll update this thread.
HID Interface on both cm13 and lineage14: If you have no HID interfaces showing in the nethunter home panel. Open an exploit that uses HID (rubberduck will suffice) and launch an attack, don't worry about plugging your phone into your computer. It's sheerly for forcing nethunter to check the relevant directories for HID interfaces. Once you've launched an attack, they should appear.
Terminal crashing on Lineage14: If your terminal keeps crashing when you try to start it, long press your home screen to bring up the active apps tabs. Close the terminal, open the main nethunter app and wait for it to be granted root privileges, now minimize and try opening the terminal again. For some reason, the terminal requires the nethunter app to be open and with root.
Rubberduck HID not launching attacks: Connect to your target computer, change the USB connection to MTP for file transfer and also enable ADB via the developer menu. Try again
Useful links
Official nethuner wiki: https://github.com/offensive-security/kali-nethunter/wiki
There's a link on there titled "known working hardware" that's where you can check if your wireless card is supported.
Official cSploit wiki: https://github.com/cSploit/android/wiki
Again, links on the page full of useful information.
Kernels:
For some reason, trying to just flash the kernel to an already installed rom doesn't work, so if you'd like to try and build the zImage into your boot.img fell free to.
3.4.111: https://www.androidfilehost.com/?fid=457095661767158370
3.4.113: https://www.androidfilehost.com/?fid=529152257862724031
Thanks and credits
@9Lukas5 for letting me use his kernel
@AndroGeek974 both the cm-13 and lineage-14.1 roms are his, with my kernels and nethunters.
@ZpanicZ The cm-13 nethunter build is his.
Screenshots
Can i use only internal card wireless for airmon-ng start wlan0 ? Or i need external one with otg cable
99% certain the answer will be no if you intend to use it in monitor mode. There's a device that does support monitor mode on the internal card but can't remember what one it was. You can always try it by opening a terminal and typing the following:
Airmon-ng start wlan0
If it works then you'll see a new interface pop up called:
Wlan0mon
I wouldn't hold my breath though, you're better of getting a cheap otg off eBay for a couple of quid and get an external wireless card. There's a link in the first post to the nethunter wiki, they have a list of devices that have been confirmed as working.
Just for your reference. The may unofficial CM14.1 based off 7.1.2 is at https://www.androidfilehost.com/?fid=529152257862723521
Maybe I can dirty flash it?
mobileman88 said:
Just for your reference. The may unofficial CM14.1 based off 7.1.2 is at https://www.androidfilehost.com/?fid=529152257862723521
Maybe I can dirty flash it?
Click to expand...
Click to collapse
Perfect, cheers, downloading it now. May try it out tonight, prob be tomorrow though.
Update
Updated to include the latest lineage-14.1 build running on android 7.1.2, I'm still testing it but the same issues listed in the first post seem to be present with no other issues appearing!
michael8t6 said:
Update
Updated to include the latest lineage-14.1 build running on android 7.1.2, I'm still testing it but the same issues listed in the first post seem to be present with no other issues appearing!
Click to expand...
Click to collapse
Awesome to hear that. Take your time dude. Understand this fixes many rom issues except for Bluetooth which is still funky. Left my m7 at work so can't do anything this weekend. Bummer.
Sent from my Nexus 6P using Tapatalk
mobileman88 said:
Awesome to hear that. Take your time dude. Understand this fixes many rom issues except for Bluetooth which is still funky. Left my m7 at work so can't do anything this weekend. Bummer.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
haha unlucky!! I'd be tempted to drive back and get it
Yeah the bluetooth doesn't like my headset on this build, doesn't find it in pairing mode at all! The rom does seem a lot more stable for sure though.
michael8t6 said:
haha unlucky!! I'd be tempted to drive back and get it
Yeah the bluetooth doesn't like my headset on this build, doesn't find it in pairing mode at all! The rom does seem a lot more stable for sure though.
Click to expand...
Click to collapse
Haha. Work is too much of a drive for me over the weekend. Should I dirty flash from your earlier release? Or spotless I do a full wipe and start anew?
Sent from my Nexus 6P using Tapatalk
mobileman88 said:
Haha. Work is too much of a drive for me over the weekend. Should I dirty flash from your earlier release? Or spotless I do a full wipe and start anew?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
One of the perks of working from home, I only have to drive to the storage unit to collect my eBay orders, other than that I get to spend the rest of my time at home.
Think you have to do a clean flash mate, I tried a dirty flash when I was testing the kernels and although it said it went fine with no errors, when I flashed the nethunter build, none of the apps were showing. I then done a clean flash and everything was working fine. Although, if you do try a dirty flash and it works, let me know please :good:
Some one help me step by step .
i have htc s-on hboot 1.61
When i flash rom i reboot full boot phone
And coming back to recouvery and flashing nethunter . but when i run nethunter app terminal cruch .. Please some one telp hiw to make it true step by step and sorry for my bad english
michael8t6 said:
One of the perks of working from home, I only have to drive to the storage unit to collect my eBay orders, other than that I get to spend the rest of my time at home.
Think you have to do a clean flash mate, I tried a dirty flash when I was testing the kernels and although it said it went fine with no errors, when I flashed the nethunter build, none of the apps were showing. I then done a clean flash and everything was working fine. Although, if you do try a dirty flash and it works, let me know please :good:
Click to expand...
Click to collapse
Thanks for trying it out first. I have also tried dirty flash . It's the same, no go. Everything boots up fine but none of the nethunter apps are showing although the kernel is able to show the hidg devices as checked using adb. The apps are all not showing. Bummer. Doing a full flash now. Hopefully we can easily update to the new daily builds so I don't have to do a full wipe of the device each time. Let me know if there's anything else I can help test it with.
Btw how did you modify the 0501 unofficial build to your 0.0.1 file?
---------- Post added at 10:41 AM ---------- Previous post was at 10:39 AM ----------
Tafabil said:
Some one help me step by step .
i have htc s-on hboot 1.61
When i flash rom i reboot full boot phone
And coming back to recouvery and flashing nethunter . but when i run nethunter app terminal cruch .. Please some one telp hiw to make it true step by step and sorry for my bad english
Click to expand...
Click to collapse
There are steps in the OP for S-ON devices . You need to do a few more steps to get it going
-----
If you're S-on, extract the boot.img from the CM-13/14 file and place it in your fastboot folder.
Run the following command and reboot: fastboot flash boot boot.img
After the boot.img has flashed, run the following command: fastboot reboot
After you've allowed your phone to boot fully, reboot back into recovery and install the nethunter file.
After flashing rom 7.1.1 should i go back to fastboot imidiatly and flashing boots.img or let the phone boot fully and then going back to fastboot and flash boot.img ?
mobileman88 said:
Thanks for trying it out first. I have also tried dirty flash . It's the same, no go. Everything boots up fine but none of the nethunter apps are showing although the kernel is able to show the hidg devices as checked using adb. The apps are all not showing. Bummer. Doing a full flash now. Hopefully we can easily update to the new daily builds so I don't have to do a full wipe of the device each time. Let me know if there's anything else I can help test it with.
Btw how did you modify the 0501 unofficial build to your 0.0.1 file?
Click to expand...
Click to collapse
aye, I'm not quite sure why we're not able to dirty flash, I know when the nethunter app updates you'll get a message next time you open the nethunter main app asking if you want to update, it then downloads the latest apk so you're able to update the nethunter apps. But for some reason, you're not able to just flash the boot.img over a existing install or dirty flash! Annoying I know but I'm not a developer so am stuck on that bit.
As for renaming the build, after I built the kernel, I used a program called android kitchen, extracted the boot.img from the build, then extracted the zImage and ramdisk file, replaced the zImage with mine, repacked and rebuilt the rom whilst renaming.
Tafabil said:
After flashing rom 7.1.1 should i go back to fastboot imidiatly and flashing boots.img or let the phone boot fully and then going back to fastboot and flash boot.img ?
Click to expand...
Click to collapse
Go back to fastboot immediately, once the rom and gapps have finished installing, DO NOT BOOT INTO SYSTEM! Boot into bootloader and run the following commands:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Once it's done flashing the boot image, run the next cmd:
fastboot reboot
Click to expand...
Click to collapse
if at any point during the install process, twrp or your other custom recovery asks if you want it to root, select DO NOT INSTALL..
Wait for the phone to have one full boot after issuing the reboot command before install nethunter.
michael8t6 said:
aye, I'm not quite sure why we're not able to dirty flash, I know when the nethunter app updates you'll get a message next time you open the nethunter main app asking if you want to update, it then downloads the latest apk so you're able to update the nethunter apps. But for some reason, you're not able to just flash the boot.img over a existing install or dirty flash! Annoying I know but I'm not a developer so am stuck on that bit.
As for renaming the build, after I built the kernel, I used a program called android kitchen, extracted the boot.img from the build, then extracted the zImage and ramdisk file, replaced the zImage with mine, repacked and rebuilt the rom whilst renaming.
Go back to fastboot immediately, once the rom and gapps have finished installing, DO NOT BOOT INTO SYSTEM! Boot into bootloader and run the following commands:
Once it's done flashing the boot image, run the next cmd:
if at any point during the install process, twrp or your other custom recovery asks if you want it to root, select DO NOT INSTALL..
Wait for the phone to have one full boot after issuing the reboot command before install nethunter.
Click to expand...
Click to collapse
Cool to know that. I am quite familiar with Kali Linux but am not as familiar with the internals of Android. Learning something new everyday. There are tons of Y-cables on Amazon, not sure if they are all the same and I should simply buy the cheapest one. Definitely need one to power mouse/keyboard/hdd
mobileman88 said:
Cool to know that. I am quite familiar with Kali Linux but am not as familiar with the internals of Android. Learning something new everyday. There are tons of Y-cables on Amazon, not sure if they are all the same and I should simply buy the cheapest one. Definitely need one to power mouse/keyboard/hdd
Click to expand...
Click to collapse
I paid £12.99 for mine from maplins just because I wanted it that day haha, my patience is non existent when it comes to waiting on things in the post. To be honest though I suppose as long as it does what it says on the tin then I'd get the cheapest.
I've got kali and windows 7 as a dual boot, bit of a strange one with kali though, when I installed it with my external graphics card, it would crash and kill my session as soon as I tried to do anything graphic intensive! Worked out it was the external graphics card, so removed it, went to download and install the drivers for it, soon as I tried to install it, the GUI said that it couldn't detect a card (obviously it wasn't plugged in). I tried to plug it back in and install the driver again, then it just killed my session and logged me out like it was before so I'm now having to run onboard graphics! No idea why it was doing that but meh, both windows and kali are running fine with onboards so not to bothered!
I was using kali back when it was called backtrack 4!! Great little distro for testing networks, currently studying for the CEH exams, dream job to be a certified pen tester. Suppose that's why it only took the week to learn all about kernel compiling with toolchains and so on, always been a quick learner, especially when it comes to technology! A computer will only do what it's told to do, so if somethings not working then you just have to find out what went wrong, 99% of the time the developers always code in a escape to a debug log so you can find a fix and apply it!!
If you want any help with kernel compiling, feel free to drop me a pm and we can sort out adding each other on Skype or something, make it a bit easier to communicate. Now I've learnt the basics of it, it's a lot lot easier than it sounded!
This was a great video that explained kernels in a really good informative way!
[YOUTUBE]
https://www.youtube.com/watch?v=AheWTTFwV6k[/YOUTUBE]
michael8t6 said:
I paid £12.99 for mine from maplins just because I wanted it that day haha, my patience is non existent when it comes to waiting on things in the post. To be honest though I suppose as long as it does what it says on the tin then I'd get the cheapest.
I've got kali and windows 7 as a dual boot, bit of a strange one with kali though, when I installed it with my external graphics card, it would crash and kill my session as soon as I tried to do anything graphic intensive! Worked out it was the external graphics card, so removed it, went to download and install the drivers for it, soon as I tried to install it, the GUI said that it couldn't detect a card (obviously it wasn't plugged in). I tried to plug it back in and install the driver again, then it just killed my session and logged me out like it was before so I'm now having to run onboard graphics! No idea why it was doing that but meh, both windows and kali are running fine with onboards so not to bothered!
I was using kali back when it was called backtrack 4!! Great little distro for testing networks, currently studying for the CEH exams, dream job to be a certified pen tester. Suppose that's why it only took the week to learn all about kernel compiling with toolchains and so on, always been a quick learner, especially when it comes to technology! A computer will only do what it's told to do, so if somethings not working then you just have to find out what went wrong, 99% of the time the developers always code in a escape to a debug log so you can find a fix and apply it!!
If you want any help with kernel compiling, feel free to drop me a pm and we can sort out adding each other on Skype or something, make it a bit easier to communicate. Now I've learnt the basics of it, it's a lot lot easier than it sounded!
Click to expand...
Click to collapse
I have already dropped you a PM about the rom packaging and kernel compiles. No hurry. Let me know when's a good time for us to get something going. Btw a new unofficial build just dropped for 0506 . Seems to have been reported to fix the bluetooth issues we are getting.
https://androidfilehost.com/?fid=457095661767159226
---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------
michael8t6 said:
This was a great video that explained kernels in a really good informative way!
[YOUTUBE]
https://www.youtube.com/watch?v=AheWTTFwV6k[/YOUTUBE]
Click to expand...
Click to collapse
Can't seem to get the Youtube link working. (Embedded one does not work, but it works using a separate browser tab, so it's ok)
New 0515 unofficial build out. https://www.androidfilehost.com/?fid=745425885120732208
Related
Here are the steps required to backup the Fuhu Nabi 2, install a custom recovery, root, and gapps using Ubuntu(12.10) Linux.
This also works on Windows(other than installing adb and fastboot) if you just remove the 'sudo' from the commands.
For a scripted Windows install, check out Nabi Lab: http://forum.xda-developers.com/showthread.php?p=36758895
Original root from jmztaylor, Includes the new gapps(t499user) and the new TWRP 2.3.3.0 from aicjofs(thanks!)
You should do all of the OTA updates before rooting(otherwise you might lose WiFi) When I posted this the latest version was 1.9.37. Settings>About Tablet>Update>Check Update
Download the needed files then extract all of the files to your home folder to begin. http://dl.dropbox.com/u/6529005/Fuh...Backup-Root-Recovery-Gapps 30December2012.zip
Open a terminal(ctrl+alt+t) and run the following command to install ADB and Fastboot (Universe).
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On the device, enable USB debugging in Settings>Developer options, then connect USB cable.
Just in case the adb server is already running, lets kill it using:
Code:
adb kill-server
Now we will start the server and reboot the device:
Code:
sudo adb reboot-bootloader
Once the device has rebooted into the bootloader, we will flash the new recovery image using fastboot:
Code:
sudo fastboot flash recovery recovery.img
When fastboot is finished, boot the new recovery kernel on the Nabi2 by pressing vol+ then vol-(down to recovery) then vol+ to select.
{
"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"
}
We will push the follwing files to the device.
First we will push the Root file.
Code:
adb push root.zip /sdcard/root.zip
Now we will push the Google Apps File
Code:
adb push gapps.zip /sdcard/gapps.zip
This is the script that will backup then install Root and Google Apps onto the device.(you can also skip the script and do it manually if you like, but make sure you do a backup)
Code:
adb push backup-root-gapps.openrecoveryscript /cache/recovery/openrecoveryscript
Now we will reboot the device and let the script do it's thing.
Code:
adb reboot recovery
Once you log into your device, start up SuperSU to make sure that root 'sticks'.
Your Fuhu Nabi2 is now rooted, w/gapps, and a custom recovery, Now click on the "thanks" button
NOTE: The following is if you ever need to do an OTA update, which requires the original Nabi2 recovery.
Download the original Nabi2 recovery image to your home folder https://www.box.com/s/9ogqkk8uu71bqrnpz9w1
Reboot the device into the bootloader
Code:
sudo adb reboot-bootloader
Finally we will flash the original recovery image to the device
Code:
sudo fastboot flash recovery nabi2_original_recovery.img
Thank you very much! In about 10 minutes, everything was the way things should be! Specifically, a nicely rooted tablet so that my son could thoroughly his tablet! Now if I can get XBMC working properly, then life would be perfect! Thanks again!!!!
Fuhu Nabi2 Common issues and FAQ.
Glad it helped you out! It's a great little tablet.
To make Nabi2 more like a regular tablet now that you have Root and Google Play, you can prevent the tablet from starting Nabi Mode/Monarch UI by checking the box in Settings>Security>'Set Parent Mode as default mode'.
You can also remove the files in the /vendor/app/ folder if you want to free up some space. Just make sure to have 'Parent Mode as default mode' checked before you remove these files, or when you reboot the tablet it will give you a blank screen.
Code:
NvCPLSvc.apk, fuhu_AddApps.apk, fuhu_AppZone.apk, fuhu_Books.apk, fuhu_ChoreList.apk, fuhu_Crafts.apk, fuhu_Fan-a-tech.apk, fuhu_KidzMode.apk, fuhu_NabiCare.apk, fuhu_NabiCloud.apk, fuhu_NabiSpinletsPlusICS.apk, fuhu_NabiSpinletsPlusParentICS.apk, fuhu_NabiSync.apk, fuhu_OOBE.apk, fuhu_ParentalDashboard.apk, fuhu_SpinletPlusVideo.apk, fuhu_SwitchKids.apk, fuhu_TreasureBox.apk, fuhu_University.apk, fuhu_Videos.apk, fuhu_Web.apk, fuhu_nabiMD.apk
I used ES File Explorer to remove the files. First you have to go into the ES File Explorer settings and check all the boxes in 'Root Settings'. Alternatively you could use the file manager in the custom recovery we flashed in the first post or any other file manager with root capabilities.
If you need to get into fastboot or recovery manually, turn off the Nabi2 and then hold the vol+ and power button until the menu comes up. You use the vol- to navigate and the vol+ to select.
Nabi2 Teardown Thread: http://forum.xda-developers.com/showthread.php?t=2024105
Technical Specs for the Fuhu Nabi2
Display: 7-inch, Capacitive, Multi-Touch Display, 1024 x 600 Resolution
CPU: NVIDIA® Tegra® 3, Super 4-PLUS-1™ Quad Core with 5th Battery Saver Core
Storage: 8 GB, Expandable via MicroSD (Up to 32 GB); Plus 2 GB FREE Cloud Storage
Memory: 1GB RAM
Camera: 2MP Front Facing Camera; 720p Video
Battery: 3,850 mAh Rechargeable Lithium-ion Battery
Size & Weight: (with Drop-Safe Bumper) Width: 8.69 Inches (220.8 mm) Height: 6.05 Inches (153.7 mm) Depth: 1.14 Inches (29.08 mm)
Weight: 1.31 Pounds (596 g)
OS: Android 4.0, Ice Cream Sandwich
Network: Wi-Fi 802.11 b/g/n Bluetooth 3.0
Input / Output: Micro USB 2.0 Port, Mini HDMI MicroSD Compatible Cartridge Slot, 3.5 mm Standard Audio Jack, Built-In Microphone, DC Connector
Audio + Video Format:
Audio: MP3, AAC
Video: MPEG-4, H.263, H.264
Charger Output: 5vdc 2000mA
Charger Plug: 2.35mm OD and 0.7mm ID
Gmail App will force close if you don't have gmail checked in Settings>Accounts&Sync>Click on email>Checkmark Gmail.
Some games on the Fuhu Nabi2 use openfeint, to disable/block this you can install AdAway https://play.google.com/store/apps/details?id=org.adaway and add the following to the blacklist. This prevents the program from contacting the openfeint servers.
Code:
openfeint.com
api.openfeint.com
scoreloop.com
Some Games that use openfeint:
Code:
Fruit Ninja, Tiny Wings, The Moron Test, Robot Unicorn Attack, Championship Manager series, Bomberman Touch 2: Volcano Party, Fieldrunners, geoDefense, geoDefense Swarm, Minigore, Pocket God, Rollercoaster Rush, Jetpack Joyride
Here is a copy of the build.prop http://pastebin.com/5hCHd4bb
If you really, really messed up and have to restore the device back to stock because you didn't follow directions and lost wifi etc etc, I created a thread for restoring to factory from scratch. http://forum.xda-developers.com/showthread.php?p=35287470
ANDROID UPGRADING MESSAGE:
If you used a different gapps other than the one posted above or http://forum.xda-developers.com/showthread.php?t=2065878 you will probably get an "Android Upgrading" message every time you reboot. This is caused by two stray odex files that need to be removed/deleted. You can just install the new gapps package or take care of the files manually.
Code:
/system/apps/Gallery2.odex
/system/framework/com.google.widevine.software.drm.odex
Thanks for this man. The only thing I'd recommend is adding a piece, or a URL, on how to add the repo's for apt to pull those adb packages. These commands you step through are handy in *nix or Windows(-sudos). Thanks again!
Thanks, I didn't even notice that adb and fastboot were in the Universe repos as I had it enabled already.
I'll go double check then. I am running Ubuntu 13 off USB stick now and had enabled universe repo but maybe didn't get a clean update before checking for pkg. Will try again and see what's up...
I thought it required some custom repos, nothing preconfigured. If it is in universe my bad.
Thank you, for this thread was able to root daughter tablet with this tutorial. Tried the script in other thread but did not help. Thanks again
Sent from my NABI2-NV7A
Yup, its in universe, my bad.
Sent from my SPH-D700 using Tapatalk 2
Here is a quote from tikiral on installing ADB and Fastboot on Windows.
tikiral said:
Speaking of posts
@shizzy t499's post is really an excellent guide. The only thing you'd change if you're on Windows is that instead of doing the 'apt-get' you'll just download and install the SDK Tools from Google (http://dl.google.com/android/installer_r21.0.1-windows.exe) > Start up the SDK Manager.exe file from the install directory > Scroll to the very bottom > Check off Extras>Google USB Driver > Click Install packages...
After install, you should be able to go into Device Manager and update the driver's on any stray android devices and bam, you should be all set to go.
Thanks again for all the info @t499.
Click to expand...
Click to collapse
Finally got a chance to perform this on my Nabi 2. Installed with no problems what so ever and was quick too. I performed the install using Ubuntu 12.10. I found it much easier and less stressful this way. Now I have to do this to both my daughters Nabi 2 tablets.
I just finished up removing the Monarch UI apps for a normal tablet. Man I really love this tablet. I have almost all my G apps installed which I have been wanting for some time now.
Just follow the instructions to the letter and you can't go wrong with Linux. Now if we could get Jelly Bean on this it would be awesome! I posted a question about the Nabi XD in the Q&A and posted specs comparing both if anyone caught it. I am pretty sure it's possible if someone can get a hold of the XD and port it over.
Thanks again t499user and all the devs that worked to make this tablet usable.
Glad it worked for you! I would love to see some JB action on here.
Just wated to shout out and say thanks many texts were sent over getting my sons tablet rooted but we got it finally no thanks to WINDOWS, Linux is the way to go! Thank you so much for the support and late night time spent working on this! :good::victory:
Hi,
Thanks so much for your new gapp package, got it working great now. Can I check if I install the default nabi recovery image again will I loose access to google play store...?
caughron01 said:
Just wated to shout out and say thanks many texts were sent over getting my sons tablet rooted but we got it finally no thanks to WINDOWS, Linux is the way to go! Thank you so much for the support and late night time spent working on this! :good::victory:
Click to expand...
Click to collapse
I am so glad that we got it working, after switching to Linux it was pretty easy eh
dave2986 said:
Hi,
Thanks so much for your new gapp package, got it working great now. Can I check if I install the default nabi recovery image again will I loose access to google play store...?
Click to expand...
Click to collapse
The default recovery would only be needed if you have to apply a new OTA update. Other than that, I would just leave the TWRP recovery, but it has no effect on the play store.
t499user;36219934
The default recovery would only be needed if you have to apply a new OTA update. Other than that said:
I have to say, that I have never been able to reflash the stock recovery after I first flashed TWRP. Every time I tried, all I got was the defective kernelpanic-Android lying on his back and I had to reflash TWRP via fastboot. So far I installed all updates from zip-files via TWRP. However, every update resulted in a defective recovery and after every update I had to reflash TWRP.
If you know that, it takes very little time but I wonder what might have gone wrong in the first place....
If some of you could spread some light, please feel free!
Cheers
DiePlage
BTW: I've tried the stock recovery from this thread http://forum.xda-developers.com/showthread.php?t=2041224
Click to expand...
Click to collapse
DiePlage said:
I have to say, that I have never been able to reflash the stock recovery after I first flashed TWRP. Every time I tried, all I got was the defective kernelpanic-Android lying on his back and I had to reflash TWRP via fastboot. So far I installed all updates from zip-files via TWRP. However, every update resulted in a defective recovery and after every update I had to reflash TWRP.
If you know that, it takes very little time but I wonder what might have gone wrong in the first place....
If some of you could spread some light, please feel free!
Cheers
DiePlage
BTW: I've tried the stock recovery from this thread http://forum.xda-developers.com/showthread.php?t=2041224
Click to expand...
Click to collapse
Have you tried to restore the unrooted stock backup that was made in the beginning of jmz rootpackage, if you didn't make 1 or use it. There are some stock posted. Unrar and put in TWRP/BACKUPS/your number folders and restore from TWRP recovery RESTORE. I have and was completely back to stock.
You can find stock in jmz files but it is any older version. Look thru the many post tho and others have posted stock 1.9.37
http://forum.xda-developers.com/showthread.php?t=1905674
ALD3 said:
Have you tried to restore the unrooted stock backup that was made in the beginning of jmz rootpackage, I have and was completely back to stock.l]
Click to expand...
Click to collapse
I have tried to just flash the stock recovery. I thought this should be enough to do OTAs. Maybe I could find another stock recovery besides the one noted...
DiePlage said:
I have tried to just flash the stock recovery. I thought this should be enough to do OTAs. Maybe I could find another stock recovery besides the one noted...
Click to expand...
Click to collapse
Forgot that I had 1 downloaded already. Try this 1 from my Box. Stock 1.9.37
https://www.box.com/shared/but3ihiutkw62pa4gayd
DiePlage said:
Android lying on his back and I had to reflash TWRP via fastboot.
Click to expand...
Click to collapse
That is the stock recovery, it will happen that way if you don't install root.zip, and possibly after an update.
To get to the menu of the stock recovery, after getting to android laying down, you push the vol buttons.
Really hoping someone can help me. Im trying to Root the Nabi 2 on my Mac. Im following the command lines, without the "sudo" text, and when i flash the recovery, my terminal says waiting for device, and nothing happens.
i know my adb is working, bc it detects the Nabi 2 when i run the ADB devices command, and it will reboot into the bootloader.
Any suggestions??
Edit
Found this link, and all worked out. Didn't have to root, or flash recovery or anything like that, but i only really need youtube as of right now, so it worked well for me
http://everythingnabi.blogspot.ca/2012/08/googlie-booglie.html
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
New twrp 331-test 1 for this device is builded!
Now need period of tests...
http://www.mediafire.com/file/cnqw8d2qkjqtp6k/Twrp_331_test1_Umi_Power.rar/file
reserved 1
Reserved 2
TWRP Not Working for Me
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
I confirm the first part of this, same issue here... i'd like to flash a twrp for gsi purposes, but for now no luck
SeekerofLight.iz said:
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Root UMIDIGI Power with Magisk
mr A V said:
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Click to expand...
Click to collapse
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
Step 0 - Download the Attached Zip File Below
Google Drive Mirror
Mediafire Mirror
MEGA Mirror
Step 1 - Drivers
Install the MediaTek drivers by running "DriverInstaller.exe". These are the drivers that worked for me. But if you have issues with them in Step 5, Google "Mediatek MT65xx USB VCOM Drivers" (or some variation of that) and try some others you can find.
-----------------------------------
Step 2 - Install ADB Interface
Install the Android SDK (ADB Interface). To do this drop the platform-tools folder (from the Step 2 folder) into your C:\ directory. Press the windows start button and search for "Environment Variables" and click on "Edit environment variables" from the results. Under SYSTEM VARIABLES on the bottom (not User variables above it) click on the "Path" variable, and click edit. In the new window that appears, hit "Browse..." and click on the "platform-tools" folder that you placed in your C:\ directory.
All this does is allows you to easily input adb commands into command prompt with no issues. This will be used to verify that the device is appearing properly and issue commands in case of emergency.
{
"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"
}
-----------------------------------
Step 3 - Install Magisk
Copy the Magisk.apk to your phone and install it.
(This is where you can then copy the boot.img to your device and patch it via the Magisk app to create the "magisk_patched_boot.img" file, however I have included the already patched file in Step 6 for the UMIDIGI Power so you don't need to.)
Also, this is the Magisk v19.3 Beta, but you can install another version.
-----------------------------------
Step 4 - OEM Unlocking/USB Debugging Mode
On your phone, go to Settings >> System >> Developer Options. (If you haven't activated Developer Options yet, do that by going to About Phone >> Build number, and tap it a bunch of times, but I'm sure you already know this lol)
In Developer Options, turn on "OEM Unlocking" to unlock the bootloader, and USB Debugging.
-----------------------------------
Step 5 - Verify That Your Phone is Detected with ADB
Connect your phone to your PC. Make sure you click "Allow USB debugging" on your phone. Then open up Command Prompt. (Protip: Type "color a" and press Enter if you want to feel like a REAL HACKERMAN.) Now, type in "adb devices" and verify that your phone is detected by your computer. If it's detected, then that's perfect you can move on to Step 6. If not, then uh... you may have to try and find some other MediaTek drivers mentioned in Step 1.
-----------------------------------
Step 6 - Set up SP Flash Tool
Open up SP Flash Tool on your computer by running "flash_tool.exe" in the SP Flash Tool Folder. (If at any time it shows a "Processing" window for some reason, just close and reopen the program if it doesn't go away on its own.)
On the first line choose "MTK_AllInOne_DA.bin". And the third line "Authentication File" can be left blank.
On the second line where it shows "Scatter-loading File", hit "choose" and find the "MT6765_Android_scatter.txt" file in the Step 6 folder. It'll load up and show a bunch of green/white rows in the space below.
Now this looked intimidating to me at first, but it's actually quite simple. As far as I understand (and I could be wrong but), the scatter file just tells the program where to place certain files, like a map for the program to follow. The scatter file I provided is for the UMIDIGI Power. The only thing we'll worry about for now is the boot.img file (but in the future, this is where you could also install a TWRP recovery once we get one that is confirmed to work.)
So in the white/green list, scroll down to where it says "boot" in the "Name" column, and click on the blank area in the "Location" column. It will bring up a window where you can browse to the "magisk_patched_boot.img" that I provided.
-----------------------------------
Step 7 - The Big Huzzah (Rooting)
Power off your phone and make sure it's UNPLUGGED. On SP Flash Tool, click "Download". This prepares the program to begin flashing your phone as soon as it is connected. Grab your phone with one hand, and with your other hand plug in the USB cable (if you only have one hand, use your mouth I guess). Your screen should not turn on at all throughout this process, but if it's successful, you should see that the program begins to flash your device after a second or two. Now just wait until it reaches 100% and says "Download Ok" with a green checkmark. And you're pretty much done!
You can then boot up your phone and check the Magisk app, as well as download a root checker from the Play Store to confirm that your phone has root access! Have fun!
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
mr A V said:
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
Click to expand...
Click to collapse
No problem! Unfortunately I don't see many custom ROMs coming to this phone, considering it's not a very popular device. I'd guess our best bet is to hope that the UMIDIGI F1 gets some support, and that anything on there can hopefully be ported over to this phone, but even that device isn't very popular either. For me though, that's not a huge issue because I'm actually quite satisfied with the stock firmware it has on board. It's basically stock Android Pie, and I've been able to add all the extra goodies I want into the phone through Magisk Manager and EdXposed with very minor issues. Most notably Viper4Android to fix the slightly tinny speakers and pump up the overall headphone experience too, and Gravity Box for some extra minor software customization.
Overall, I'd say the biggest downside to this device is the limited camera capabilities, and its somewhat limited performance for heavier tasks like 3D games / game streaming. But other than that, this feels like a very premium device. :good:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
mr A V said:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
Click to expand...
Click to collapse
I definitely consider myself to be a major noob with the more advanced Android development stuff. I only know enough to find my way around the internet and flash compatible software, haha. I've never looked into creating ports myself, but it's certainly something I think might be worth learning, especially with the limited device support on these phones.
And yeah, in terms of performance I don't expect much out of a phone at this price point, but for all the essentials - music, 1080p YouTube, web browsing, and mid to light gaming, it's surprisingly great considering the price. I haven't had any issues with the memory as of yet, so I wouldn't be too concerned, although you're definitely right in that they probably source some pretty cheap parts for these kind of phones.
SeekerofLight.iz said:
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
"stubbed guide"
Click to expand...
Click to collapse
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
---------- Post added at 09:30 AM ---------- Previous post was at 09:29 AM ----------
ghost45 said:
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
Click to expand...
Click to collapse
Can i ask you a guide on how were you able to boot it? i'm only getting a bootloop after flashing that from SPFlash
I will build one other version of recovery soon...
mg95tux said:
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
Click to expand...
Click to collapse
Glad to hear it worked for you!
Still nothing. Unfortunately I haven't had any luck with booting into TWRP since I last tried it. Hoping ghost45 will be able to help us out with that when he gets the chance.
Bootloop - Secureboot
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Andre_Filho said:
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Click to expand...
Click to collapse
remember to allow oem unlock from developer settings in stock rom, otherwise it will fail!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Andre_Filho said:
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Click to expand...
Click to collapse
The trick to getting Viper4Android to work is to make sure you have SELinux set to "PERMISSIVE" rather than "ENFORCING" on your phone. Here's a handy little app designed to automatically set it to permissive on boot!
https://forum.xda-developers.com/devdb/project/?id=1561#downloads
And for BusyBox, I was having issues too at first because I think with systemless root, BusyBox can only be installed in /sbin, which gets wiped after each boot. So I searched for "BusyBox" in the Magisk app and found a module called "BusyBox for Android NDK" which has worked perfectly for me.
One thing to note...
Sometimes SELinux doesn't always get changed automatically everytime you boot up. It's pretty consistent, but every once in awhile you may need to manually set it to permissive mode again if things don't seem to be working. But it's literally just pressing a single button, so not a big deal.
The other thing is with Viper itself- At times when I launch the app, the driver status says "abnormal" even after I've toggled SELinux to permissive. If you go into settings and toggle "compatibility mode" or "attach audio effects" on and then off that seems to refresh the driver status. Not sure why, but it works.
Let me know if you have any issues.
TWRP for UMIDIGI POWER
I ask for help in creating TWRP for UMIDIGI POWER firmaware ROM v1.5
Please make for this model TWRP
I am very grateful to you - I unlocked the phone and got the rights Root rights.
It remains only to create a TWRP for UMIDIGI POWER
At this forum, competent specialists and for other models everything is already done.
Maybe there is a website where you can make an order to create a TWRP?
Unfortunately, I do not know English and I do not know how to apply.
I would be very grateful and ready to test your work.
{
"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"
}
Amlogic G12*/SM1 Family Devices
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Amlogic G12*/SM1 SoC family of devices.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed:
Official Builds:
deadpool - Google ADT-3
wade - Dynalink TV Box (4K)
Disclaimer: My unofficial builds have full Android TV Google Apps and some other goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.
Unofficial Builds:
deadpool - Google ADT-3
dopinder - Walmart Onn UHD Box
sabrina - Chromecast with Google TV
wade - Dynalink TV Box (4K)
We also support a few development boards, but at least (for now, until we have time to write up instructions), you're on your own to figure out the install process and set things up:
m5 - Banana Pi M5
odroidc4 - Odroid C4
radxa0 - Rock Pi Radxa Zero
EDIT: The development boards don't boot on LineageOS 19.1 at the moment for some reason, we're looking into it.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Recent apps/Multitasking menu doesn't launch.
(sabrina only) The remote firmware sometimes gets hung up, you can reboot to solve this issue.
(dopinder/sabrina) L1 is currently broken, this is what is holding up official builds for these devices.
Notes:
GApps are baked in on Unofficial builds - No, I will not be building without GApps included for this device. These builds are built, packaged, and signed by me, and not affiliated with LineageOS whatsoever.
Firmware is shipped in the ROM package for this device, so you'll end up on the newest version of compatible firmware after install. Please don't touch firmware partitions after install.
On the unofficial OTA is provided the same way officials would have them.
Find any more on an official build? Report them according to this guide.
FAQ:
Does L1 Widevine DRM break when I unlock my bootloader?
Nope, it works fine. L1 certificates, and the mechanism that reports is all still exist and work as expected.
Can I haz Netflix?
Yup! Play Store has it for you. Unless you're on dopinder or sabrina, but that will be fixed soon hopefully.
Is this Android TV or Google TV?
Android TV, with some of the better components of Google TV.
Can I go back to stock and relock the bootloader?
Yeah, grab the factory image for your device and flash it just like you would for a Pixel device, you can find the factory images here. Don't know it I'd relock though, consider that process largely untested on these device. Especially on sabrina, where you can't necessarily re-unlock should you ever want to.
Are these the stock codenames for these devices?
Astute observation, no, they are not. The ADT-3 is actaully `adt3`, but earlier in production is was `deadpool`, which is much cooler. The Dynalink box internally is extremely similar to the ADT-3, so we coined it `wade` after Wade Wilson, AKA deadpool. The Onn box is in the same family, but different enough to coin it `dopinder`, after, well, go watch Deadpool the movie I guess. sabrina is actually the codename given by Google - no clue as to the reason.
Does it pass SafetyNet?
Maybe - the only sure fire way it Magisk, as our boot loader is unlocked and can't be relocked safely.
Does the stock remote work?
Yup, just like it would on stock, in-remote-microphone and all! If it's an IR remote like wade's, it will even work in recovery!
Can we we support higher resolution than 4K, higher FPS, or HDR on non-certified screens?
Nope.
I have a very similar device! Can I install these builds and use them?
No. Please don't do that. You will brick your device, as we include firmware and bootloader images.
If you're a developer looking to help port to a new device, contact me.
Kernel Source: https://github.com/LineageOS/android_kernel_amlogic_linux-4.9
Contributors:
npjohnson
bgcngm
stricted
webgeek1234
deadman96385
trautamaki
luca020400
aleasto
i probably will write up install instructions for the `BananaPi-M5` and `Odroid C4` Soon™
its a bit more complicated than just booting into recovery and flashing it unfortunately
I managed to install this on the onn 4k tv box (I used a usb keyboard and flash drive in the recovery) and everything went fine while installing but now I'm just stuck at the boot animation. I've left it on for at least 30 minutes and it never goes anywhere. Here's the serial log: https://paste.ee/p/7PAxS
It pretty much just stops there except for the occasional healthd battery message.
Do these builds support Signature Spoofing to replace GApps with MicroG?
Big Dumb Object said:
Do these builds support Signature Spoofing to replace GApps with MicroG?
Click to expand...
Click to collapse
No, as MicroG doesn't emulate what Android TV needs. Different GMSCore.
lmore377 said:
I managed to install this on the onn 4k tv box (I used a usb keyboard and flash drive in the recovery) and everything went fine while installing but now I'm just stuck at the boot animation. I've left it on for at least 30 minutes and it never goes anywhere. Here's the serial log: https://paste.ee/p/7PAxS
It pretty much just stops there except for the occasional healthd battery message.
Click to expand...
Click to collapse
yeah, aware of the issue, it's video firmware not loading, building new builds now.
But for what it's worth, you don't need a keyboard or drive - you can adb sideload it over usb - easiest method, just like the wiki describes.
npjohnson said:
No, as MicroG doesn't emulate what Android TV needs. Different GMSCore.
Click to expand...
Click to collapse
Sad. I vaguely recalled something about that, but couldn't find any concrete proof when asked.
Please consider releasing the full Android as it was with Shield TV. I believe it will be in demand, given the negative attitude of a lot of power users towards Android TV.
Big Dumb Object said:
Sad. I vaguely recalled something about that, but couldn't find any concrete proof when asked.
Please consider releasing the full Android as it was with Shield TV. I believe it will be in demand, given the negative attitude of a lot of power users towards Android TV.
Click to expand...
Click to collapse
Eh, maybe once we're in a more functional state (eg. Hardware OMX gets fixed).
npjohnson said:
yeah, aware of the issue, it's video firmware not loading, building new builds now.
But for what it's worth, you don't need a keyboard or drive - you can adb sideload it over usb - easiest method, just like the wiki describes.
Click to expand...
Click to collapse
I couldn't figure out how to navigate the recovery menu. I tried the button on the side like in the stock recovery but pressing it did nothing and holding it would change the highlight color to green but it didn't actually run the option that was highlighted. It was detecting the button presses (there were keyevents in the serial log) so it isn't just a broken button. I tried doing adb sideload without selecting the option but I just got `adb: sideload connection failed: closed`
lmore377 said:
I couldn't figure out how to navigate the recovery menu. I tried the button on the side like in the stock recovery but pressing it did nothing and holding it would change the highlight color to green but it didn't actually run the option that was highlighted. It was detecting the button presses (there were keyevents in the serial log) so it isn't just a broken button. I tried doing adb sideload without selecting the option but I just got `adb: sideload connection failed: closed`
Click to expand...
Click to collapse
okay, figured it out, you need to hand flash DTB before booting recovery, will update instructions
npjohnson said:
okay, figured it out, you need to hand flash DTB before booting recovery, will update instructions
Click to expand...
Click to collapse
Sounds good. One more question, is this build using a 64-bit kernel? I'd like to use the app for my drone on a big screen and this box would've been perfect if the stock kernel wasn't 32-bit.
lmore377 said:
Sounds good. One more question, is this build using a 64-bit kernel? I'd like to use the app for my drone on a big screen and this box would've been perfect if the stock kernel wasn't 32-bit.
Click to expand...
Click to collapse
64-bit kernel, 32-bit userspace - aiming to do 64 bit userspace someday.
Do you have an ETA for when the next builds will be done?
lmore377 said:
Do you have an ETA for when the next builds will be done?
Click to expand...
Click to collapse
they're uploaded now - sorry, got caught up putting out fires at work all day today lol
npjohnson said:
they're uploaded now - sorry, got caught up putting out fires at work all day today lol
Click to expand...
Click to collapse
I'll try it and flashing dtb for the button in recovery in a bit
lmore377 said:
I'll try it and flashing dtb for the button in recovery in a bit
Click to expand...
Click to collapse
DTBO/DTB - they need to be in sync.
npjohnson said:
DTBO/DTB - they need to be in sync.
Click to expand...
Click to collapse
I flashed the two (I got them from here) and now the button and usb otg don't work at all. I tried to flash back to stock but the box got stuck on the can't load android system screen and it was ignoring all my attempts at interacting with it (it was even ignoring Ctrl+C in uboot), but luckily I managed to boot into the lineage os recovery by putting it on a flash drive and holding down the button then wiping /misc thru the serial console.
lmore377 said:
I flashed the two (I got them from here) and now the button and usb otg don't work at all. I tried to flash back to stock but the box got stuck on the can't load android system screen and it was ignoring all my attempts at interacting with it (it was even ignoring Ctrl+C in uboot), but luckily I managed to boot into the lineage os recovery by putting it on a flash drive and holding down the button then wiping /misc thru the serial console.
Click to expand...
Click to collapse
I'll look into this... Can you try flashing the newest build through lineage recovery and wipe data?
npjohnson said:
I'll look into this... Can you try flashing the newest build through lineage recovery and wipe data?
Click to expand...
Click to collapse
Is there any way to activate sideload mode through adb shell or the serial console? Again, since the button isn't working (still works in uboot so it isn't a hardware issue) with the new dtb I can't navigate through the recovery menu.
lmore377 said:
Is there any way to activate sideload mode through adb shell or the serial console? Again, since the button isn't working (still works in uboot so it isn't a hardware issue) with the new dtb I can't navigate through the recovery menu.
Click to expand...
Click to collapse
Adb reboot sideload works, maybe just reboot sideload?
I'll go grab an Onn box at Walmart tmrw afternoon.
I know it works as 3 of our developers have and use it.
Just a matter of install process it seems...
{
"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"
}
Proudly Presents
Another Exclusive Release
Supported Model
UMX U696CL
Recoveries
TWRP_11 Recovery
Roms
GSI Roms - Arm32 Binder64 Required
AssuranceRom Custom Stock * WIP *
-AIO ToolKit Prerequisites-
1- Linux: Linux Mint Cinnamon Suggested
2- Python 3
Rom Notes/Disclaimer/Warning
* WIP *
Contributors
@gregeerg / BVK - for using his device as a ginuea pig to make this happen
@AndyYan - for his GSI knowledge and wisdom
@deadman96385 - for uploading dumped files to github
@Jet! - for flashing twrp and dumping stock super image
Big Thanks To The Folks In My A-Team Telegram Group
Big Thanks To The Folks Who Have Come To The A-Team Telegram Group To Help Test
Device Downloads
UMX U696CL Downloads
Recovery Device Trees
Device Source
A-Team Website
A-Team Supported Devices
TeleGram Live Support
A-Team Digital Solutions
-Updates-
5-18-2022- Initial AIO ToolKit v0.01 Release
I don't have telegram, is there anywhere else I can download some of this stuff from?
Thanks..
karl615 said:
I don't have telegram, is there anywhere else I can download some of this stuff from?
Thanks..
Click to expand...
Click to collapse
No sir, I don't put out untested stuff. I've gotten 0 feedback on the toolkit
How do we get feedback if no one can download here? we are not forcing anyone to install tiktok whatsapp instagram facebook telegram or any other crappy pipapo, keep development on xda-developers. Think about it
aIecxs said:
How do we get feedback if no one can download here? we are not forcing anyone to install tiktok whatsapp instagram facebook telegram or any other crappy pipapo, keep development on xda-developers. Think about it
Click to expand...
Click to collapse
I left a download link, unsure what you mean. If XDA would allow me to upload a 1.7gb 7zip file I would but that's not reality. I need stuff tested and chat to be fluid and prompt. That's not possible on a forum. In reality, If I had the device, I could test in 1 day what it would take a week to do on Telegram or 3 months to do on XDA forum. So for getting things done in a timely fashion, Telegram is my go to. I've been a member of XDA since 2012, I've done my time. If people don't want the toolkit or if joining telegram is too much, that's fine, not the people I want to help me test my software then anyways. The people who just want to grab a download and go can wait for the rest of the backend process. Again, I don't even have this device. So why am I even doing this is what i'm now wondering. I guess next time someone comes to me with a untouched device I won't help and use my resources to get something going....
it's alright though, you can consider this project shelved as I have a different hands on device I've already moved on to. Enjoy the twrp I built for you guys!.....
PizzaG said:
I left a download link, unsure what you mean. If XDA would allow me to upload a 1.7gb 7zip file I would but that's not reality. I need stuff tested and chat to be fluid and prompt. That's not possible on a forum. In reality, If I had the device, I could test in 1 day what it would take a week to do on Telegram or 3 months to do on XDA forum. So for getting things done in a timely fashion, Telegram is my go to. I've been a member of XDA since 2012, I've done my time. If people don't want the toolkit or if joining telegram is too much, that's fine, not the people I want to help me test my software then anyways. The people who just want to grab a download and go can wait for the rest of the backend process. Again, I don't even have this device. So why am I even doing this is what i'm now wondering. I guess next time someone comes to me with a untouched device I won't help and use my resources to get something going....
it's alright though, you can consider this project shelved as I have a different hands on device I've already moved on to. Enjoy the twrp I built for you guys!.....
Click to expand...
Click to collapse
Appreciated..
Update: flashed the recovery using 'fastboot flash recovery /path-to-.img' and the recovery works fine as far as I can tell, but the system is gone. Or something is up anyway, I can't get it to boot normally.. only to recovery. What did I do wrong?
Sorry Pizza i havent had the time to give feedback on it but i have the same issues booting. please dont let one person ruin it for everyone. i will hyu on telegram later today
PsYk0n4uT said:
Sorry Pizza i havent had the time to give feedback on it but i have the same issues booting. please dont let one person ruin it for everyone. i will hyu on telegram later today
Click to expand...
Click to collapse
Actually i havent had the time to get my linux machine setup correctly because of a memory leak issue that kept crashing my system but i finally got it running stable. i tried using relive on virtualbox but couldnt get it working properly due to driver issues in the host OS on this windows machine and for some reason i had more than one python version installed causing me conflicts. i ended up just using adb to flash the images and the phone no longer boots. i want to test it on a native linux os first
Well, folks...I'm about to give this a go....I still have a BLU View 3 to root today. Much gracias for all the effort
Cinephile 74 said:
Well, folks...I'm about to give this a go....I still have a BLU View 3 to root today. Much gracias for all the effort
Click to expand...
Click to collapse
Well I seem to have faux pas along the way.... bootloader unlocked easy-peasey. But I can't get fastboot to flash TWRP no matter what directory I use....RELP!
Is this the ROM or the bootable zip?
I'm back and about to try this again with an actual thumb drive with the ReLiveDVD on a thumb drive now that I have one
I downloaded A-Team-UMX_U696CL_AIO_ToolKit-v0.01.7z from the tg group and here's my feedback. I don't mean to sound ungrateful but:
Root does not work. I opened Main_Menu.sh and the root option literally does nothing. The lines are commented out and the image it was supposed to flash doesn't exist. Bootloader unlocking works (seems to literally be a single fastboot command i.e. "fastboot flashing unlock", seems like the new "oem unlock") and TWRP does work, but only once. If I flash it in fastboot and immediately reboot to recovery from there, I can get in. If I try to go to recovery after restarting, I get the dead android with the red ! triangle saying "no command". TWRP won't mount data (I think it said it couldn't decrypt, but I don't even have a lock code on it) so you need a micro sd to store the boot.img in order to patch it in Magisk. It would've been nice if you included it, though it seems you intended to but haven't gotten around to it since it's only v0.01. Still, it's not much of an all-in-one if it can't do the primary thing most people will want from it. I do fortunately have micro sd cards so I was able to save (manually in TWRP terminal using dd, annoying as hell on a touchscreen, can't even type "=" without going through 2 keyboard menus) and patch it in Magisk and now do have root working.
I don't understand why this requires Linux. The AIO doesn't do anything you can't do in Windows. The Python file is just an ASCII logo that makes you wait 10 seconds for no reason. It would have more user friendly as just a bunch of separate partition IMG uploads and instructions. I wish I had actually looked at the shell scripts beforehand instead of downloading a Linux distro and booting it as a live cd. If you make a new version, consider just including a portable adb/fastboot with it and skipping Linux/Python since it's not necessary.
After googling the "no command" screen, I held down power and pressed volume up and got into the regular Android recovery. So despite the bootloader being unlocked, it appears TWRP got overwritten by the default recovery. I flashed TWRP at least 3 times, immediately entering TWRP each time afterward, but it never stuck.
I'm attaching my Magisk'd boot.img in case anyone else gets stuck at that part. If anyone chooses to use it, MAKE YOUR OWN BACKUP FIRST, obviously. I'm not responsible for anything that happens using that file.
Eric janaika said:
TWRP does work, but only once.
Click to expand...
Click to collapse
proof that TWRP works for you, anything beyond is usage problem.
aIecxs said:
proof that TWRP works for you, anything beyond is usage problem.
Click to expand...
Click to collapse
I got twrp to stick but could not do anything with it since I didn't have an SD card before I misplaced the phone. Yes the scripts unfinished but as stated above somewhere, the dev did not have a device to test on.
If you wanna help, and it's probably the only way anyone else who isnt so knowledgable as many visiting xda seeking a way to root their device is gonna get this finished as well, please consider joining the telegram chat and contribute to this forum whatever you learn. Maybe Pizza will still be interested in helping. I tried but somehow misplaced the phone in the middle of filling in my huge gaps of knowledge on the subject.
I could not mount or wipe /data in twrp and even flashing the super.imgwould not allow me to boot because I was unable to do anything with the data partition. Had to flash the stock recovery to get it to boot period.
Maybe twrp will get you root if you patch your boot image with Magisk and flash it in twrp.
I'm not sure what else could be done. And not even sure that would work without being able to mount /data.
It's really hard for anyone working on a device they don't have to finish the work without some feedback from people who have enough knowledge to give them useful feedback.
The unlock bootloader option and the flash twrp recovery options work.
Script could be finished but I doubt there's much motivation for them since th3y don't own the device.
But the script is there. Most of the work on that part is done.
would only take some contributions by interested people.
PsYk0n4uT said:
I got twrp to stick but could not do anything with it since I didn't have an SD card before I misplaced the phone. Yes the scripts unfinished but as stated above somewhere, the dev did not have a device to test on.
If you wanna help, and it's probably the only way anyone else who isnt so knowledgable as many visiting xda seeking a way to root their device is gonna get this finished as well, please consider joining the telegram chat and contribute to this forum whatever you learn. Maybe Pizza will still be interested in helping. I tried but somehow misplaced the phone in the middle of filling in my huge gaps of knowledge on the subject.
I could not mount or wipe /data in twrp and even flashing the super.imgwould not allow me to boot because I was unable to do anything with the data partition. Had to flash the stock recovery to get it to boot period.
Maybe twrp will get you root if you patch your boot image with Magisk and flash it in twrp.
I'm not sure what else could be done. And not even sure that would work without being able to mount /data.
It's really hard for anyone working on a device they don't have to finish the work without some feedback from people who have enough knowledge to give them useful feedback.
Click to expand...
Click to collapse
what do you need a script for? read any random TWRP install guide steps are more or less same
- unlock bootloader
- patch avb/dm-verity/vbmeta
- install TWRP
- makesysrw super.img (optional)
- disable encryption (optional)
PsYk0n4uT said:
The unlock bootloader option and the flash twrp recovery options work.
Script could be finished but I doubt there's much motivation for them since th3y don't own the device.
But the script is there. Most of the work on that part is done.
would only take some contributions by interested people.
Click to expand...
Click to collapse
Agreed. PizzaG has done a bang up job with his UMX U696CL offerings, and his knowledge is extensive regarding custom ROMs and recoveries.
Eric janaika said:
I downloaded A-Team-UMX_U696CL_AIO_ToolKit-v0.01.7z from the tg group and here's my feedback. I don't mean to sound ungrateful but:
Root does not work. I opened Main_Menu.sh and the root option literally does nothing. The lines are commented out and the image it was supposed to flash doesn't exist. Bootloader unlocking works (seems to literally be a single fastboot command i.e. "fastboot flashing unlock", seems like the new "oem unlock") and TWRP does work, but only once. If I flash it in fastboot and immediately reboot to recovery from there, I can get in. If I try to go to recovery after restarting, I get the dead android with the red ! triangle saying "no command". TWRP won't mount data (I think it said it couldn't decrypt, but I don't even have a lock code on it) so you need a micro sd to store the boot.img in order to patch it in Magisk. It would've been nice if you included it, though it seems you intended to but haven't gotten around to it since it's only v0.01. Still, it's not much of an all-in-one if it can't do the primary thing most people will want from it. I do fortunately have micro sd cards so I was able to save (manually in TWRP terminal using dd, annoying as hell on a touchscreen, can't even type "=" without going through 2 keyboard menus) and patch it in Magisk and now do have root working.
I don't understand why this requires Linux. The AIO doesn't do anything you can't do in Windows. The Python file is just an ASCII logo that makes you wait 10 seconds for no reason. It would have more user friendly as just a bunch of separate partition IMG uploads and instructions. I wish I had actually looked at the shell scripts beforehand instead of downloading a Linux distro and booting it as a live cd. If you make a new version, consider just including a portable adb/fastboot with it and skipping Linux/Python since it's not necessary.
After googling the "no command" screen, I held down power and pressed volume up and got into the regular Android recovery. So despite the bootloader being unlocked, it appears TWRP got overwritten by the default recovery. I flashed TWRP at least 3 times, immediately entering TWRP each time afterward, but it never stuck.
I'm attaching my Magisk'd boot.img in case anyone else gets stuck at that part. If anyone chooses to use it, MAKE YOUR OWN BACKUP FIRST, obviously. I'm not responsible for anything that happens using that file.
Click to expand...
Click to collapse
Did you flash this from fastboot or from twrp?
Assurance Wireless
KonnectONE Moxee m2160
4G-LTE Smartphone
Model No. MH-T6000
{
"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"
}
Rooting Guide
OVERVIEW:
This guide outlines simplified instructions for rooting the Assurance Wireless Moxee MH-T6000 4G-LTE smartphone. To cater this guide to new and inexperienced members, I have provided a stock boot image pre-patched with the Magisk v26.1 systemless root solution.
PREREQUISITES:
First and foremost, you need an unlocked bootloader. If your bootloader is not yet unlocked, complete that task and then return here. XDA hosts a plethora of how-to guides on standard bootloader unlocking. You will also need a Windows PC or laptop running the Minimal ADB & Fastboot Tools (link provided below). It should be noted that this guide can be carried out on a Mac or Linux computer as well; however, for purposes of this guide, I am focusing solely on a Windows setup. It is highly recommended that your device be running firmware build number MH-T6000V1.0.OB010, with the March 5, 2023 security patch level. As OTA updates are rolled out for this device, I will try to keep this guide updated with a patched boot image that corresponds with the latest firmware build.
Finally, you will need the factory supplied, or a quality equivalent USB-A to USB-C charging/syncing cable.
DISCLAIMER:
By proceeding further, you are assuming sole responsibility for the integrity and operability of your smartphone. Rooting your device is a task that carries with it the inherent risk of bricking or otherwise rendering your phone inoperable. While this guide has been thoroughly tested on my own device, you have been warned. Proceed at your own risk.
INSTRUCTIONS:
Download the ADB & Fastboot tools from the link below and install the program on your PC or laptop;
Open your Windows File Explorer, navigate to your C: drive, Program Files x86, and locate the Minimal ADB & Fastboot folder. Copy this folder and paste it to your desktop. (This step is not required, but is recommended for easier access of the ADB & Fastboot path);
Download the patched boot image from the below link and save the image in your ADB & Fastboot folder. Note: the filename for the patched boot image is patched_boot.img. The flashing commands assume that you leave the filename unchanged;
Boot your phone into fastboot mode by first powering your device off, and then holding the power and volume down keys simultaneously until fastboot mode appears on your device display;
Connect your smartphone to your Windows computer using the factory supplied or a quality equivalent USB-A to USB-C charging/syncing cable;
Open your ADB & Fastboot folder and double click cmd-here.exe to open a command window. Execute this command to verify a proper fastboot connection:
Code:
fastboot devices
If properly connected, the command window will return an alphanumeric string consistent with your device serial number;
Once a proper connection has been verified, execute this command:
Code:
fastboot flash boot patched_boot.img
Now execute:
Code:
fastboot reboot
Upon reboot, open your app drawer and tap on the Magisk app or its placeholder stub. Ensure you are connected to the internet, grant any permissions, and follow any prompts given by Magisk to update to the full version in order to complete the root environment setup. Magisk may reboot your device during this process.
That's it. You're now rooted via the Magisk v26.1 systemless root solution.
IMPORTANT NOTE:
In the unfortunate event that you get stuck in a boot loop or brick your device using this guide, my guide on unbricking this smartphone will get you back up and running fairly quickly. This guide can be used to restore both soft bricked and hard bricked devices. You can then return here and give rooting another go.
Moxee MH-T6000 Unbricking GuideDOWNLOADS:
• Minimal ADB & Fastboot v1.4.3
• Magisk Patched Boot Image
THANKS & MENTIONS:
A huge thanks and shout-out to @omb714.1980 for donating the Moxee smartphone that made this rooting guide possible. You are a scholar and a gentleman, good sir. Thanks also to KonnectONE support specialist Faith Flores for releasing to me the factory firmware for this device.
Viva La Android said:
Assurance Wireless
Moxee MH-T6000 4G-LTE
View attachment 5893661
Rooting Guide
OVERVIEW:
This guide outlines simplified instructions for rooting the Assurance Wireless Moxee MH-T6000 4G-LTE smartphone. To cater this guide to new and inexperienced members, I have provided a stock boot image pre-patched with the Magisk v26.1 systemless root solution.
PREREQUISITES:
First and foremost, you need an unlocked bootloader. If your bootloader is not yet unlocked, complete that task and then return here. You will also need a Windows PC or laptop running the Minimal ADB & Fastboot Tools (link provided below). It should be noted that this guide can be carried out on a Mac or Linux computer as well; however, for purposes of this guide, I am focusing solely on a Windows setup. It is highly recommended that your device be running firmware build number MH-T6000V1.0.OB010, with the March 5, 2023 security patch level. Finally, you will need the factory supplied, or a quality equivalent USB-A to USB-C charging/syncing cable.
DISCLAIMER:
By proceeding further, you are assuming sole responsibility for the integrity and operability of your smartphone. Rooting your device is a task that carries the inherent risk of bricking or otherwise rendering your phone inoperable. While this guide has been thoroughly tested on my own device, you have been warned. Proceed at your own risk.
INSTRUCTIONS:
Download the ADB & Fastboot tools from the link below and install the program on your PC or laptop;
Open your Windows File Explorer, navigate to your C: drive, Program Files x86, and locate the Minimal ADB & Fastboot folder. Copy this folder and paste it to your desktop. (This step is not required, but is recommended for easier access of the ADB & Fastboot path);
Download the patched boot image from the below link and save the image in your ADB & Fastboot folder;
Boot your phone into fastboot mode by first powering your device off, and then holding the power and volume down keys simultaneously until fastboot mode appears on your device display;
Connect your smartphone to your Windows computer using the factory supplied or a quality equivalent USB-A to USB-C charging/syncing cable;
Open your ADB & Fastboot folder and double click cmd-here.exe to open a command window. Execute this command to verify a proper fastboot connection:
Code:
fastboot devices
If properly connected, the command window will return an alphanumeric string consistent with your device serial number;
Once a proper connection has been verified, execute this command:
Code:
fastboot flash boot patched_boot.img
Now execute:
Code:
fastboot reboot
Upon reboot, open your app drawer and tap on the Magisk app or its placeholder stub. Ensure you are connected to the internet, grant any permissions, and follow any prompts given by Magisk to update to the full version in order to complete the root environment setup. Magisk may reboot your device during this process.
That's it. You're now rooted via the Magisk v26.1 systemless root solution.
DOWNLOADS:
• Minimal ADB & Fastboot v1.4.3
• Magisk Patched Boot Image
THANKS & MENTIONS:
A huge thanks and shout-out to @omb714.1980 for donating the Moxee smartphone that made this rooting guide possible. You are a scholar and a gentleman, good sir. Thanks also to the KonnectONE support team for releasing to me the factory firmware for this device.
Click to expand...
Click to collapse
Lol. Now you post this. After unsuccessfully scouring the internet for the stock firmware. I finally did the same as you and simply reached out to konnectone and asked for it. I just came here to see if there was anyone here that is by far more knowledgeable than myself (not hard) interested to have the firmware and would post a guide like this one. Well done!
Would you happen to have a twrp recovery compiled for this device by chance? Or if not but planning on it would you let me know please. I would appreciate it!
scottfan81 said:
Lol. Now you post this. After unsuccessfully scouring the internet for the stock firmware. I finally did the same as you and simply reached out to konnectone and asked for it. I just came here to see if there was anyone here that is by far more knowledgeable than myself (not hard) interested to have the firmware and would post a guide like this one. Well done!
Would you happen to have a twrp recovery compiled for this device by chance? Or if not but planning on it would you let me know please. I would appreciate it!
Click to expand...
Click to collapse
I just got KonnectONE to agree to release firmware a couple of days before you mentioned having firmware. It's been a long wait indeed.
I don't have source code to compile TWRP; only the firmware. I will be attempting to port a TWRP build for this phone very soon. My legal battle with KonnectONE was in regards to source code under the General Public License 2.0. Because they were ultimately unable to provide kernel source, their legal team and support department finally acquiesced to provide firmware to device owners upon written request. I compromised for the firmware release, but was not able to get kernel source code for building TWRP. I am pretty confident that a ported TWRP can be ironed out as a stable build. I already have the base build selected.
Thank you so much! I have 3 of these devices and been waiting lol. I see the stock kernel has hot-plug . What's some good tuning profiles? I tried to debloat permanently with LP but it didn't work. I think it's read-only so I flashed the magisk overlay for rw and going to play. We definitely need TWRP! I see a port may be in the works. Awesome. Thanks again
Viva La Android said:
I just got KonnectONE to agree to release firmware a couple of days before you mentioned having firmware. It's been a long wait indeed.
I don't have source code to compile TWRP; only the firmware. I will be attempting to port a TWRP build for this phone very soon. My legal battle with KonnectONE was in regards to source code under the General Public License 2.0. Because they were ultimately unable to provide kernel source, their legal team and support department finally acquiesced to provide firmware to device owners upon written request. I compromised for the firmware release, but was not able to get kernel source code for building TWRP. I am pretty confident that a ported TWRP can be ironed out as a stable build. I already have the base build selected.
Click to expand...
Click to collapse
They never replied when I emailed them about it several months ago . This is so awesome. I got rid of most of the lag with kernel manager. Kudos
Argonon said:
They never replied when I emailed them about it several months ago . This is so awesome. I got rid of most of the lag with kernel manager. Kudos
Click to expand...
Click to collapse
Several months ago they weren't releasing firmware to the public. I got it released by battling with them over open source code and I ultimately compromised for factory firmware. It was only recently made public.
Yeah I've noticed a nice performance boost too with some debloating and sone kernel tweaks. I'm using EX Kernel Manager. Keep in mind this device uses dynamic partitioning (super.img). As such, even with root, it isn't always possible to mount /system r/w. I extracted the super.img on a PC and then mounted /system, /vendor and /product, debloated, and then repacked and reflashed super img.
Awesome. I don't have a good pc now unfortunately. I do have viper4android repackaged version with driver and effects pre-installed. I used smart pack kernel manager to tweak kernel. The device is very useable now! I have a Blu View 3 android 11 mtk device id love to root but can't even unlock bootloader. Maybe I should look into emailing them
Argonon said:
Awesome. I don't have a good pc now unfortunately. I do have viper4android repackaged version with driver and effects pre-installed. I used smart pack kernel manager to tweak kernel. The device is very useable now! I have a Blu View 3 android 11 mtk device id love to root but can't even unlock bootloader. Maybe I should look into emailing them
Click to expand...
Click to collapse
BLU won't unlock your bootloader. It is locked per contractual agreement with the branded carrier of the phone. However, if it's MediaTek, you may be able to use MTK Client to exploit the bootloader into an unlocked state.
Viva La Android said:
Several months ago they weren't releasing firmware to the public. I got it released by battling with them over open source code and I ultimately compromised for factory firmware. It was only recently made public.
Yeah I've noticed a nice performance boost too with some debloating and sone kernel tweaks. I'm using EX Kernel Manager. Keep in mind this device uses dynamic partitioning (super.img). As such, even with root, it isn't always possible to mount /system r/w. I extracted the super.img on a PC and then mounted /system, /vendor and /product, debloated, and then repacked and reflashed super img.
Click to expand...
Click to collapse
Would you plz share your super.img ? I'm on latest firmware and have attached screenshot of build etc.... I understand if you can't or don't want to. Can I pull mine since I'm rooted? Problem is I have a old Chromebook that I installed endeavor os on its arch based Linux but I don't have much hard drive space to do work
Viva La Android said:
Several months ago they weren't releasing firmware to the public. I got it released by battling with them over open source code and I ultimately compromised for factory firmware. It was only recently made public.
Yeah I've noticed a nice performance boost too with some debloating and sone kernel tweaks. I'm using EX Kernel Manager. Keep in mind this device uses dynamic partitioning (super.img). As such, even with root, it isn't always possible to mount /system r/w. I extracted the super.img on a PC and then mounted /system, /vendor and /product, debloated, and then repacked and reflashed super img.
Click to expand...
Click to collapse
Would you plz share your super.img ? I'm on latest firmware and have attached screenshot of build etc.... I understand if you can't or don't want to. Can I pull mine since I'm rooted? Problem is I have a old Chromebook that I installed endeavor os on its arch based Linux but I don't have much hard drive space to do work
Viva La Android said:
I just got KonnectONE to agree to release firmware a couple of days before you mentioned having firmware. It's been a long wait indeed.
I don't have source code to compile TWRP; only the firmware. I will be attempting to port a TWRP build for this phone very soon. My legal battle with KonnectONE was in regards to source code under the General Public License 2.0. Because they were ultimately unable to provide kernel source, their legal team and support department finally acquiesced to provide firmware to device owners upon written request. I compromised for the firmware release, but was not able to get kernel source code for building TWRP. I am pretty confident that a ported TWRP can be ironed out as a stable build. I already have the base build selected.
Click to expand...
Click to collapse
I have 3 of these devices. I surly can test TWRP port if needed
Argonon said:
Would you plz share your super.img ? I'm on latest firmware and have attached screenshot of build etc.... I understand if you can't or don't want to. Can I pull mine since I'm rooted? Problem is I have a old Chromebook that I installed endeavor os on its arch based Linux but I don't have much hard drive space to do work
I have 3 of these devices. I surly can test TWRP port if needed
Click to expand...
Click to collapse
Sure. I don't mind sharing my super.img. I'll need to upload it and then I'll message you a link. It's pretty much exactly 2.5 GB in file size, so I'll first compress it to a zip before uploading.
The edited one. Just clarifying so appreciated
Argonon said:
The edited one. Just clarifying so appreciated
Click to expand...
Click to collapse
I don't yet have all my mods made to the /super partition in that regard. Having encountered some force close issues with certain apps, I debloated from scratch and and have now begun my kernel tweaks and edits to the.varuous .prop files. So when finished, I'll share both my boot.img and super.img.
Just the stock super.img would be fine then. I think I can figure how to decompile, debloat and recompile then flash.
Argonon said:
Just the stock super.img would be fine then. I think I can figure how to decompile, debloat and recompile then flash.
Click to expand...
Click to collapse
MH-T6000 super.img unmodified
I was experimenting and flashed the super.img with dsu side loader apk as a gsi lol. The app description said can replace various partitions and I was just trying to get system rw on the dsu loader. I know that makes no sense. What windows 11 compatible software do you recommend to unpack, repack etc? I see a few magisk modules but not quite sure how to use. Like ro2rw magisk module
Viva La Android said:
MH-T6000 super.img unmodified
Click to expand...
Click to collapse
Thank you!
Argonon said:
Thank you!
Click to expand...
Click to collapse
When I have completed debloating, kernel tweaks and .prop files edits of the OS, I'll share my modified super.img and boot.img. I have a TWRP v3.6.0 port build that is currently booting properly on this phone. But, I have bugs to work out on logical partition mounting, as well as the backup & restore functionality.
Argonon said:
I was experimenting and flashed the super.img with dsu side loader apk as a gsi lol. The app description said can replace various partitions and I was just trying to get system rw on the dsu loader. I know that makes no sense. What windows 11 compatible software do you recommend to unpack, repack etc? I see a few magisk modules but not quite sure how to use. Like ro2rw magisk module
Click to expand...
Click to collapse
Check out CRB Android Kitchen here on XDA. Great for unpacking / repacking partition images, including super.img.
Viva La Android said:
When I have completed debloating, kernel tweaks and .prop files edits of the OS, I'll share my modified super.img and boot.img. I have a TWRP v3.6.0 port build that is currently booting properly on this phone. But, I have bugs to work out on logical partition mounting, as well as the backup & restore
Click to expand...
Click to collapse
Have you had anymore luck with this