Related
Ok folks, thanks to some leakage, some awesome users/testers, Chainfire and his root magic, and me with so of mine, you all have a fully functioning TWRP Recovery.
Official TWRP
Confirmed working on:
G900F
G900T
G900W8
G900I
G900P
G900M
Confirmed not working on:
G900H - exynos - Its recovery can found here
G900V - locked bootloader (thanks Verizon!!!)
G900A - locked bootloader (thanks AT&T!!)
Note: No one but yourself is responsible for what you do to your device.
People to Thank
TeamWin - for their awesome recovery.
TeamWin - for their hlte device repo I ported to the klte (kltexxx in this case)
ricky310711 - for providing dumps and testing
leoaudio13 - for providing access to device and testing
utkanos - for his original work on hlte (which all this is based off of)
Known Issues
Write permissions to internal storage.
How to install via adb shell
Have USB drivers installed
Connect phone to PC
Open terminal or cmd
Code:
adb push recovery.img /data/local/tmp/recovery.img
Code:
adb shell su -c dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
How to install with Odin
(USB) Disconnect your phone from your computer
Start Odin3-vX.X.exe
Click the PDA button, and select twrp-klte.tar
Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
(USB) Connect the phone to your computer
Make sure Repartition is NOT checked
Click the Start button
Wait for Android to boot
Done (if it took you more than 30 seconds, you goofed)
NOTE: Sometimes the device does *not* boot into recovery mode. Just do the entire procedure again if this happens. If it still will not install, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
The Goods
twrp-klte.tar - flash with ODIN.
recovery-twrp-klte.img - for manual flashing.
Official TWRP can be found here.
XDA:DevDB Information
TWRP for the Samsung Galaxy S5, Tool/Utility for the Samsung Galaxy S 5
Contributors
PlayfulGod, leoaudio13, utkanos, biggbiff
Version Information
Status: Stable
Stable Release Date: 2014-04-22
Created 2014-03-28
Last Updated 2014-06-08
Test imgs!!!!!!
Reserved
Yep the write permission is painful PG! but i accept to live with it for now )
Does this work on a SM-G900H?
0mega007 said:
Does this work on a SM-G900H?
Click to expand...
Click to collapse
Dunno until someone tries it.
PlayfulGod said:
Dunno until someone tries it.
Click to expand...
Click to collapse
PG, for some reason while flashing the CWM swipe, it fked up the platform.xml in /syste/etc/ . That caused Titanium Backup to stop function properly while doing a backup to external SD. Is it the recovery or its a problem with Kitkat ? I got the same problem with Note 3 ( Exynos and SnapDragon too ). The only way to fix was to do like this picture below :
{
"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"
}
( Source : http://forum.xda-developers.com/showthread.php?t=2537793 )
leoaudio13 said:
PG, for some reason while flashing the CWM swipe, it fked up the platform.xml in /syste/etc/ . That caused Titanium Backup to stop function properly while doing a backup to external SD. Is it the recovery or its a problem with Kitkat ? I got the same problem with Note 3 ( Exynos and SnapDragon too ). The only way to fix was to do like this picture below :
( Source : http://forum.xda-developers.com/showthread.php?t=2537793 )
Click to expand...
Click to collapse
umm I dont see that file in the system dump nor in cwm. So my guess is its a tibu issue.
not to mention, those look like app manifest permissions. And the Write permission overrides the read permission.
PlayfulGod said:
umm I dont see that file in the system dump nor in cwm. So my guess is its a tibu issue.
not to mention, those look like app manifest permissions.
Click to expand...
Click to collapse
Yup maybe. On the Nexus 5 Kitkat, TB made restored apps force closed. But TB team fixed it. But as far as i remember, When i was testing your recovery ( pretty sure it was cwm swipe) after 2 or 3 flashes, problem arose. Ricky and me thought it was an SD card issue ( wrong permission, full sd card or something like that ) but it turned out the problem was the platform.xml . Not so sure as if TB made any change to platform.xml or not.
leoaudio13 said:
PG, for some reason while flashing the CWM swipe, it fked up the platform.xml in /syste/etc/ . That caused Titanium Backup to stop function properly while doing a backup to external SD. Is it the recovery or its a problem with Kitkat ? I got the same problem with Note 3 ( Exynos and SnapDragon too ). The only way to fix was to do like this picture below :
( Source : http://forum.xda-developers.com/showthread.php?t=2537793 )
Click to expand...
Click to collapse
this was on a SM-G900H?
Did the recovery worked?
I just want it to completely wipe the phone before install new roms. so this bug doesnt matter to me if it worked
0mega007 said:
this was on a SM-G900H?
Did the recovery worked?
I just want it to completely wipe the phone before install new roms. so this bug doesnt matter to me if it worked
Click to expand...
Click to collapse
No its a F model. BTW, there is no Rom right now to install. ^^
according to a PM I just got, this doesnt work on G900H. By the description I was giving I think its the kernel and/or dtb. So I asked for a dump of the G900H stock recovery so I can extract the kernel & dtb from it.
PlayfulGod said:
according to a PM I just got, this doesnt work on G900H. By the description I was giving I think its the kernel and/or dtb. So I asked for a dump of the G900H stock recovery so I can extract the kernel & dtb from it.
Click to expand...
Click to collapse
Ok, thanks i hope you release H model recovery soon too
0mega007 said:
Ok, thanks i hope you release H model recovery soon too
Click to expand...
Click to collapse
Do you have one? According to PM CF-Root not working for H either. I told him to contact Chainfire and see what he needed to get that working for it.
PlayfulGod said:
Do you have one? According to PM CF-Root not working for H either. I told him to contact Chainfire and see what he needed to get that working for it.
Click to expand...
Click to collapse
Not yet, in about 2 weeks, but i wont order it until there is a root method available, and if it is from chainfire better
PlayfulGod said:
Do you have one? According to PM CF-Root not working for H either. I told him to contact Chainfire and see what he needed to get that working for it.
Click to expand...
Click to collapse
Different chip maybe ? Pretty sure the one that test the H will be messed up cos there is no stock recovery atm
leoaudio13 said:
Different chip maybe ? Pretty sure the one that test the H will be messed up cos there is no stock recovery atm
Click to expand...
Click to collapse
From what I been told/seen its exynos. :\
PlayfulGod said:
From what I been told/seen its exynos. :\
Click to expand...
Click to collapse
I know its Exynos , but i guess the recovery will be different as well. Thats why i didnt dare to flash the root tool also gotta haave to wait. We can't dump recovery if there is no root ....
leoaudio13 said:
I know its Exynos , but i guess the recovery will be different as well. Thats why i didnt dare to flash the root tool also gotta haave to wait. We can't dump recovery if there is no root ....
Click to expand...
Click to collapse
yea it will be different. Ricky has a plan to try for root. And I'm just waiting for a recovery/boot dump lol
PlayfulGod said:
yea it will be different. Ricky has a plan to try for root. And I'm just waiting for a recovery/boot dump lol
Click to expand...
Click to collapse
Let see how it goes 2mo. I might ask for the H again hehe!:good:
Hi mate,
many thanks for the S5(G900F) TWRP recovery,
i have a question about the backup to extSD, it do not work
Error code:
E: Unable to create folder: /external_sd/TWRP/BACKUPS (error13)
E: Faild to make a backup folder
I have set this folder manuelly but the error comes again
Backup to internal SD works ok (big file with 3,4GB without set all Apps)
thanks in advance
Sorry guys, I've underestimated this hugely, just spoken to the EFIDroid team on Slack and this is never going to boot Windows without MS' help as, like the Pi 2's CPU, the MSM8226 CPU in the Moto G, like all Qualcomm CPUs, requires a HAL extension and custom drivers which are basically impossible to write without MS' source. So yeah, enjoy EFIDroid, it doesn't support Android booting yet, but hey, proof of concept of EFI on a phone! I'm leaving this thread alone now as I really am not the best person to ask, but if you have a question their Slack is great!
EFIDroid Port to Moto G 2013
Based on EFIDroid
EDIT: I know this has been ported to falcon already, but this image is up-to-date as of 17/04/16
Update: I compiled the app and whilst falcon is supported by EFIDroid, the app has not been updated for this. I'm therefore going to create a forked version of the app using my forked GitHub repo instead which adds back that support... hopefully the efidroid devs will add back in falcon to /ota soon
Download: https://www.mirrorcreator.com/files/IFZ9ABGF/lk_sideload.img_links
Proof:
{
"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"
}
RIP my laptop's keyboard :crying:
Compiled for the Moto G 2013, based on 4.4.4 boot.img, had to disable CIL in SELinux as there were errors compiling it. Also had to remove metadata info due to python incompatibilities
LCD works OOTB, volume key selection
DO NOT FLASH, ONLY BOOT USING FASTBOOT BOOT [NAME].IMG - THIS CANNOT BOOT ANDROID YET!
Here's a clearer image of it.
Here's some instructions for people who wants to try it out..
Boot into fastboot mode
Type in fastboot boot imagefile.img
And you are done.
The touchscreen didn't seam to work. Also @androidonlinx, Good luck trying to boot windows RT or windows mobile because it's closed source.. That means you can't make your own version of it...
Anyways... Best Regards -Chris
chris36202 said:
Here's a clearer image of it.
Here's some instructions for people who wants to try it out..
Boot into fastboot mode
Type in fastboot boot imagefile.img
And you are done.
The touchscreen didn't seam to work. Also @androidonlinx, Good luck trying to boot windows RT or windows mobile because it's closed source.. That means you can't make your own version of it...
Anyways... Best Regards -Chris
Click to expand...
Click to collapse
I've built the installer APK which is just compiling now, I can upload soon.
RT should work - obviously without drivers of course
Couple of updates.... the install kinda works and does manage to install it but it's not booting up at the moment
Stuck on decompression, this could be down to lack of battery so I'm going to give it a good charge and see what happens from there. Both TWRP and Android show up in the menu, though.
androidonlinx said:
I've built the installer APK which is just compiling now, I can upload soon.
RT should work - obviously without drivers of course
Click to expand...
Click to collapse
That's good on the installer side.. But regarding Windows RT. To quote "RT cannot "run on any ARM-Based device" for one simple reason. Microsoft is not providing Windows 8 RT as a separate Software package and is ONLY available pre-installed on certified hardware." -- > http://answers.microsoft.com/en-us/...-toshiba/b47e1b85-0cc7-4422-a1dc-23b38be1ba8d
Yes i do know that the moto g runs on a ARM Processor which is the Snapdragon 400..
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
androidonlinx said:
Couple of updates.... the install kinda works and does manage to install it but it's not booting up at the moment
Stuck on decompression, this could be down to lack of battery so I'm going to give it a good charge and see what happens from there. Both TWRP and Android show up in the menu, though.
Click to expand...
Click to collapse
Just use a little script. the boot partition is at /dev/mmcblk0p31 so you just dd the image over to it... For example
dd if=/sdcard/image.img of=/dev/mmcblk0p31
Or you could just use fastboot..
fastboot flash boot boot.img
There is really no need for an app...
chris36202 said:
That's good on the installer side.. But regarding Windows RT. To quote "RT cannot "run on any ARM-Based device" for one simple reason. Microsoft is not providing Windows 8 RT as a separate Software package and is ONLY available pre-installed on certified hardware." -- > http://answers.microsoft.com/en-us/...-toshiba/b47e1b85-0cc7-4422-a1dc-23b38be1ba8d
Yes i do know that the moto g runs on a ARM Processor which is the Snapdragon 400..
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
Just use a little script. the boot partition is at /dev/mmcblk0p31 so you just dd the image over to it... For example
dd if=/sdcard/image.img of=/dev/mmcblk0p31
Or you could just use fastboot..
fastboot flash boot boot.img
There is really no need for an app...
Click to expand...
Click to collapse
Yeah, I had the idea that the app would allow me to boot Android but actually DDing the image results in inability to boot Android whatsoever, even after the original image is restored
I'm going to flash back to stock seeing as this isn't working, but I'll try again using fastboot boot instead
We could try Windows 10 Mobile take some image from a phone that has MSM 8226.
Sent from my Lenovo TAB 2 A8-50LC using Tapatalk
androidonlinx said:
Yeah, I had the idea that the app would allow me to boot Android but actually DDing the image results in inability to boot Android whatsoever, even after the original image is restored
I'm going to flash back to stock seeing as this isn't working, but I'll try again using fastboot boot instead
Click to expand...
Click to collapse
Just an idea. But couldn't you use a script to backup the original boot partition then replace it with your img. So when you press the android button it just loads that image file you backed up.. or you could just do some type of hybrid boot thingy that multirom does
Eurofighter_ty said:
We could try Windows 10 Mobile take some image from a phone that has MSM 8226.
Sent from my Lenovo TAB 2 A8-50LC using Tapatalk
Click to expand...
Click to collapse
The problem is there's no way to select an image as USB devices are not detected. This means that we have to install it to an internal partition first. I'm going to try get the Windows kernel to at least give output by putting boot.wim from the Surface RT recovery image on an internal NTFS partition, though I doubt this will work
chris36202 said:
Just an idea. But couldn't you use a script to backup the original boot partition then replace it with your img. So when you press the android button it just loads that image file you backed up.. or you could just do some type of hybrid boot thingy that multirom does
Click to expand...
Click to collapse
I have very little Android experience and I've only got this to work by hacking various strings in the installer app and following a build tutorial. Whilst I could probably do the script on the Android side, I couldn't on the EFIDroid side.
I'm going to leave this as a PC-tethered boot then.
You need to flash it on a FAT32 partition because UEFI supports booting from FAT32 only.
Sent from my Lenovo TAB 2 A8-50LC using Tapatalk
Back to stock now, just required reflash back to stock boot.img in TWRP. Going to put Win10 boot files on the /sdcard which should hopefully show up... hopefully
androidonlinx said:
Back to stock now, just required reflash back to stock boot.img in TWRP. Going to put Win10 boot files on the /sdcard which should hopefully show up... hopefully
Click to expand...
Click to collapse
A Windows 10 boot image?. Isn't Windows 10 X86-64?
Sent from my Moto G using Tapatalk
chris36202 said:
A Windows 10 boot image?. Isn't Windows 10 X86-64?
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Damnit. Meant 8.1, didn't work anyway... I don't think this will work
androidonlinx said:
Damnit. Meant 8.1, didn't work anyway... I don't think this will work
Click to expand...
Click to collapse
Good luck. On that one
Sent from my Moto G using Tapatalk
---------- Post added at 07:31 PM ---------- Previous post was at 07:22 PM ----------
Eurofighter_ty said:
We could try Windows 10 Mobile take some image from a phone that has MSM 8226.
Sent from my Lenovo TAB 2 A8-50LC using Tapatalk
Click to expand...
Click to collapse
The Nokia lumia 630 has the same specs except from the ram size. And also i found the image
http://www.allflashfiles.com/nokia-lumia-630-rm-978-latest-flash-file-download/#more-2194
EDIT: That link didn't work so i did some googling and i found this http://forum.gsmhosting.com/vbb/f60...care-suite-download-nokia-1320-added-1660094/
chris36202 said:
Good luck. On that one
Sent from my Moto G using Tapatalk
---------- Post added at 07:31 PM ---------- Previous post was at 07:22 PM ----------
The Nokia lumia 630 has the same specs except from the ram size. And also i found the image
http://www.allflashfiles.com/nokia-lumia-630-rm-978-latest-flash-file-download/#more-2194
Click to expand...
Click to collapse
The difficulty in that is finding a way to boot it - USB devices aren't supported and it won't accept a keyboard to interact with the EFI shell.
Unless someone has a Moto G to sacrifice Android off to just simply restore that image and fastboot EFIDroid to boot from it I don't think there's a way we can boot it
link removed
Might as well post the app I compiled - warning, potentially very dangerous, hugely hacky code, although it does install and boot it fails to load Android
Runs off the github repo /meagain0/ota which is cloned from the EFIDroid repo
EFIDroid cannot boot android yet so I'm not providing the link anymore, if you want the app go compile it yourself!
androidonlinx said:
The difficulty in that is finding a way to boot it - USB devices aren't supported and it won't accept a keyboard to interact with the EFI shell.
Unless someone has a Moto G to sacrifice Android off to just simply restore that image and fastboot EFIDroid to boot from it I don't think there's a way we can boot it
Click to expand...
Click to collapse
thank you for raping the project iam following since it had been started as grub4android.
https://github.com/efidroid/projectmanagement/wiki/Device-Maintainers
https://github.com/efidroid/device/commit/8e781cd8bd4db78914c7cd6947dc7dde88f843c5
Raping the project? I just provided a prebuild binary as I thought it might be useful, porting it myself as I didn't see your port until afterwards.
If you want me to remove this or something then fine, but I just tried to make a helpful post.
Do you by any chance have any idea where I'm going wrong? I simply followed the porting to a new device tutorial - are those extra variables in your link necessary? Do you have a prebuild image in that case you could share?
Sent from my Moto G using Tapatalk
its on my afh, but i wait until efi's multiboot is working. without its useless.[
extra variables, du bist der hammer.
Hi,
So long i've dont active my account on XDA Developers because my studies. Finally i've found to update Oukitel K9 by using Treble Img
{
"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"
}
Video Review : https://youtu.be/EMbBpCc0R-Y
Please make sure you have download Generic GSI from Google and already unlocked bootloader.
Here the link ( Download Generic GSI )
Choose ARM64+GMS / ARM64, if you want to flash android Q treble rom, just download Android Q only.
Let's start it.
1. Flash to stock firmware using MTK Tools
2. Extract vbmeta.img from Generic GSI.
3. Connect to usb to device (enter fastboot mode) hold volume up and power button, choose fastboot mode.
4. Type this and make sure using generic vbmeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. Next erase file system
Code:
fastboot erase system
6. a) Flash file system
Code:
fastboot flash system ######.img
# = your file system name
or
6. b) Using TWRP > Flash> Click image> find img to flash> Select system>then swipe to flash
7.
Code:
fastboot -w
8.
Code:
fastboot reboot
PLEASE TAKE NOTE OUKITEL K9 IS A/B DEVICES
Test
Working GSI:
system-quack-arm64-ab-gapps.img.xz
Evolution X , Lineage 17.1 - All Working
Havoc 3.3 - RIL bugs, no simcard detect
All GSI Rom list you can find here : Phhusson GSI
Thanks @Levered
I've flashed stock Android 9 using SP Flash Tool, is that what you're talking about when you say 'MTK Tools'?
Step #3 - My PC doesn't recognize my device. (see #2 below)
A few other questions:
1) What build number are you coming from? I'm on OUKITEL_K9_V21_20190524
From what I've read there was some sort of 'lock' put in place at around that time so that only certain firmware could be flashed.
2) Fastboot? on a MTK device? I thought that was impossible too, even though it canbe put in to Fastboot mode by holding Vol+&PWR. I'm new to MTK devices so am very much a newb.
3) The link you provided correct? It takes me to the page for Android 11 GSI's, but the video shows Android 10
4) At bottom you have generic GSI linked—which one to flash, the one linked at top or bottom?
Also, perhaps worth mentioning, I've successfully temporary-rooted using this method from @diplomatic
https://forum.xda-developers.com/an...ing-temp-root-mediatek-armv8-t3922213/page101
Thanks again
TiTiB said:
Thanks @Levered
I've flashed stock Android 9 using SP Flash Tool, is that what you're talking about when you say 'MTK Tools'?
Step #3 - My PC doesn't recognize my device. (see #2 below)
A few other questions:
1) What build number are you coming from? I'm on OUKITEL_K9_V21_20190524
From what I've read there was some sort of 'lock' put in place at around that time so that only certain firmware could be flashed.
2) Fastboot? on a MTK device? I thought that was impossible too, even though it canbe put in to Fastboot mode by holding Vol+&PWR. I'm new to MTK devices so am very much a newb.
3) The link you provided correct? It takes me to the page for Android 11 GSI's, but the video shows Android 10
4) At bottom you have generic GSI linked—which one to flash, the one linked at top or bottom?
Also, perhaps worth mentioning, I've successfully temporary-rooted using this method from @diplomatic
https://forum.xda-developers.com/an...ing-temp-root-mediatek-armv8-t3922213/page101
Thanks again
Click to expand...
Click to collapse
Sorry for this.
Use fastboot mode on windows. You can find this on others thread using cmd.
I suggest you flash img using twrp for more faster.
3) Yes, i will check later.
4) All linked has work on our devices. I will update what rom has worked.
thanks
Levered said:
Sorry for this.
Use fastboot mode on windows. You can find this on others thread using cmd.
I suggest you flash img using twrp for more faster.
3) Yes, i will check later.
4) All linked has work on our devices. I will update what rom has worked.
thanks
Click to expand...
Click to collapse
Thanks for the reply, but the question remains,
Which firmware version did you start with?
I believe the bootloader is locked on my device, no fastboot.
TiTiB said:
Thanks for the reply, but the question remains,
Which firmware version did you start with?
I believe the bootloader is locked on my device, no fastboot.
Click to expand...
Click to collapse
Pixel experience, havoc 3.3, lineage 17.1 and EvolutionX
Please unlocked your bootloader, if that. Your device will get brick.
Levered said:
Pixel experience, havoc 3.3, lineage 17.1 and EvolutionX
Please unlocked your bootloader, if that. Your device will get brick.
Click to expand...
Click to collapse
nvm, you are obviously not going to share useful information
1) build# you were able to root
2) what you mean by 'MTK Tools'
3) and other important stuff
Additional information I have discovered
The vbmeta generic file is needed http://www.mediafire.com/file/lpdpocvn76n7cyo/vbmeta.img/file
The rom is https://www.mediafire.com/file/i9jo...20200413-UNOFFICIAL-treble_arm64_bvN.img/file
The Trebel test app stated the my Oukitel k9 was A only I found out it is A/B this rom works.
Also after flashing Lineage 17 there is not enough space for Gapps. Solution after flash reboot recovery again go to wipe select system select repair then adjust size of partition. Then reboot to recovery again then flash Gapps. I have successfully flashed Gapps stock and works great. Note I flashed Magisk last. So far this GSI works great, better than the phones original. Xposed works! Gravity box beta 6 works. Apps now auto start properly.
Thank you.
Thanks
hello, my name is bausette i'm italian, i'm sorry for my bad English i hope you cand understand me. First of all
thanks for your work, that's amazing my Oukitel k9 has new life :fingers-crossed::victory:, that's amazing Everything work better, than Stock Rom.
Can i Ask you some question please? i had Flash Vmeda generic files, Open Gapp, Orange State fix message, Lineage Rom project Treble, TWRP recovery, but i think i forgot something, because after install Magisk it say that the device is not Rooted, please can you tell my step by step Guide to Root the phone? thanks so much
Levered said:
PLEASE TAKE NOTE OUKITEL K9 IS A/B DEVICES
Click to expand...
Click to collapse
My Oukitel K9 is A-Only partition when I use Treble checker. Every guide seems to reference A/B for the Oukitel K9. Mine is not or at least it is being reported incorrectly.
How do I update to a custom rom when I have only A-Partition? The stock image is so buggy it's almost unusable.
Thanks!
Lannie
lschafroth2 said:
My Oukitel K9 is A-Only partition when I use Treble checker. Every guide seems to reference A/B for the Oukitel K9. Mine is not or at least it is being reported incorrectly.
How do I update to a custom rom when I have only A-Partition? The stock image is so buggy it's almost unusable.
Thanks!
Lannie
Click to expand...
Click to collapse
You can try A partition images.
Levered said:
You can try A partition images.
Click to expand...
Click to collapse
Is the process any different? I found the following list of files:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
It shows Treble A only image as an option. Mine supports Treble but not seamless updates due to the A-only partition.
Will the image listed above work with the normal guides? Do I need the vbmeta.img for the Oukitel K9?
I'm very new to this so I'm afraid to mess it up.
Lannie
lschafroth2 said:
Is the process any different? I found the following list of files:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
It shows Treble A only image as an option. Mine supports Treble but not seamless updates due to the A-only partition.
Will the image listed above work with the normal guides? Do I need the vbmeta.img for the Oukitel K9?
I'm very new to this so I'm afraid to mess it up.
Lannie
Click to expand...
Click to collapse
you can try both, but i think our k9 is A/B partition.
yes you need vbmeta.img
follow this guide:
https://forum.xda-developers.com/mi-9-se/how-to/guide-how-to-flash-twrp-gsi-roms-mi-9-se-t3939254
Levered said:
you can try both, but i think our k9 is A/B partition.
yes you need vbmeta.img
follow this guide:
https://forum.xda-developers.com/mi-9-se/how-to/guide-how-to-flash-twrp-gsi-roms-mi-9-se-t3939254
Click to expand...
Click to collapse
I have tried 4 different Treble checking apps and they all say Treble supported but seamless updates not supported because A-only partition exists.
This is a Oukitel K9 OUKITEL_K9_V21_20190524
Wonder why everyone else seems to have A/B and I only have A.
Lannie
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
nation888888 said:
The vbmeta generic file is needed http://www.mediafire.com/file/lpdpocvn76n7cyo/vbmeta.img/file
The rom is https://www.mediafire.com/file/i9jo...20200413-UNOFFICIAL-treble_arm64_bvN.img/file
The Trebel test app stated the my Oukitel k9 was A only I found out it is A/B this rom works.
Also after flashing Lineage 17 there is not enough space for Gapps. Solution after flash reboot recovery again go to wipe select system select repair then adjust size of partition. Then reboot to recovery again then flash Gapps. I have successfully flashed Gapps stock and works great. Note I flashed Magisk last. So far this GSI works great, better than the phones original. Xposed works! Gravity box beta 6 works. Apps now auto start properly.
Thank you.
Click to expand...
Click to collapse
How do you verify you are A/B? Mine says A only on 4 different treble apps. Is there a way to verify for sure? I have a Oukitel K9.
Lannie
lschafroth2 said:
I have tried 4 different Treble checking apps and they all say Treble supported but seamless updates not supported because A-only partition exists.
This is a Oukitel K9 OUKITEL_K9_V21_20190524
Wonder why everyone else seems to have A/B and I only have A.
Lannie
Click to expand...
Click to collapse
You can try it first both partition. If not boot, try another partition. :fingers-crossed:
Everything seems to work except hotspot
The no verity, Lineage rom a/b, vbmeta, resizing system partition size, installing stock gapps all works making this one of the nicest roms I have worked with. The only issue I find so far I cannot get the mobile Hotspot to stay on. Mobile Hotspot works in safe mode. I did a fresh install and does the same. Modded buildprop, no results. Installed module tether enabler, no results.
Mobile Hotspot switches off right away. Any ideas?
---------- Post added at 06:01 AM ---------- Previous post was at 05:57 AM ----------
It is this one a/b I have not seen any other variants. Both Global and Chinese have same partition setup. Yes I have tried a only and doesn't boot.
How do I check? I've tried the ADB SHELL commands and it returns an empty line. The article said it would show TRUE if it did. All it returns is an empty line. I have yet to find any app that shows my Oukitel K9 is A/B. All of them say it is not.
lschafroth2 said:
How do I check? I've tried the ADB SHELL commands and it returns an empty line. The article said it would show TRUE if it did. All it returns is an empty line. I have yet to find any app that shows my Oukitel K9 is A/B. All of them say it is not.
Click to expand...
Click to collapse
If recovering to stock is easy, I guess I can dive in and try the A/B image and see if it works.
Lannie
use the lineage ab... it is ab. Make sure to do the no verity first with vbmeta line. Then flash lineage ab the file is not clear it states b. I tried them all see my post for direct download.
Same result
lschafroth2 said:
How do I check? I've tried the ADB SHELL commands and it returns an empty line. The article said it would show TRUE if it did. All it returns is an empty line. I have yet to find any app that shows my Oukitel K9 is A/B. All of them say it is not.
Click to expand...
Click to collapse
I have same firmware, K9 OUKITEL_K9_V21_20190524, and same results for Treble check (see screenshots for info).
Also, device not recognized using fastboot.
Code:
adb devices
OUKITELK90007961
Code:
adb reboot bootloader
success; 'FASTBOOT mode. . .' on phone
Code:
fastboot devices
blank line
From what I understand, this is because our devices' bootloaders are locked; and there is nothing we can do to change that, period. So, no flashing anything but stock. I hope I'm wrong, and someone more knowledgeable corrects me, but I'm pretty sure this is correct.
For now I'm just stuck, and using temporary root as mentioned in previous post.
repacksuper
===========
Copyleft uluruman 2021-2022
(for LINUX/WSL only)
This is the minimalistic set of tools + a script for Linux for the automated
ground-up repacking and flashing of the Samsung Galaxy super.img, replacing
the stock Android system with something much less intrusive and obtrusive
(e.g. LineageOS). Or just some other GSI (Generic System Image).
Additional included scripts (since v1.1) simplify flashing of stock firmware or
separate image files under Linux using Heimdall.
Theoretically should work for any Samsung A-series phones, and may be even for
some others. Tested on SM-A127F/DSN made in India and Vietnam and SM-A325F/DS
made in India, on Debian Linux 11 x64. There are reports of successful flashing
of SM-A127M, SM-A032M and SM-A226B.
Why this method?
----------------
Repacking of super.img is the only method which allows changing of the phone's
operating system without screwing up the Verified Boot (VB) protection
mechanism. Keeping the VB allows you to be sure that everything besides the
platform was indeed compiled by Samsung and wasn't tampered with, no matter from
where you downloaded your stock firmware.
The other reason is that although there are alternative methods of changing the
OS, for phones with dynamic partitioning and no working version of TWRP
available they may be even more complicated than repacking of super.img
externally by this script.
Requirements
------------
Install the following tools from the official repositories of your Linux distro:
simg2img xz-utils lz4 unzip gzip jq file
Basic instructions
------------------
repacksuper.sh: main script for changing your phone's operating system
heimdall_flash_stock.sh: script for flashing stock firmware under Linux
heimdall_flash.sh: script for flashing any custom image file under Linux
Just run a script without any arguments to see help.
Extra tools used (x64 binaries and sources included)
----------------------------------------------------
GitHub - LonelyFool/lpunpack_and_lpmake: android super.img tools
android super.img tools. Contribute to LonelyFool/lpunpack_and_lpmake development by creating an account on GitHub.
github.com
GitHub - amo13/Heimdall: Heimdall is a cross-platform open-source tool suite used to flash firmware (aka ROMs) onto Samsung Galaxy devices. This is a fork of the original repository with a few crucial pull requests merged.
Heimdall is a cross-platform open-source tool suite used to flash firmware (aka ROMs) onto Samsung Galaxy devices. This is a fork of the original repository with a few crucial pull requests merged....
github.com
Additional notes
----------------
The included binaries for the lpunpack, lpmake and Heimdall were compiled for
the x86_64 architecture. If your PC architecture is different (e.g. x86 32-bit
or ARM) you have to compile these tools yourself. The full source code is
included (or otherwise available on GitHub).
Spoiler: Changelog
0.9: Initial release
0.91: Non-sparse new system is now correctly moved into the super dir
0.91a: Bug in the new system file format checking fixed
0.91b: Better support for spaces in paths
0.92: Added checking for system requirements and an optional parameter for
setting of the final tar archive name.
0.92a: Fixed file ownership issues inside the tar distribution archive
0.93: Added support for SM-A325F. Several minor improvements.
0.94: Added support for gzip-packed GSI images. Packing into .tar is now done
without question if the command line parameter is given. Tar parameter
now can include the full path. Without the full path the default tar
location is now the same as the GSI. Several other minor changes.
1.0: Finally added working native Linux flashing using Heimdall (HUGE thanks
to amo13 and Benjamin Dobell). Two new options: using empty product.img
and silent (non-interactive) mode. Colored text. Bugfixes and minor
changes.
1.01: Option to specify the SUPER partition name manually (needed for flashing
SM-A127F with Heimdall). Now it is possible to place output .img and .tar
files in any directory and give them any name. Text terminology a bit
clarified, help text expanded. Done many internal optimizations,
additional sanity checks and minor changes.
1.02: Support for SM-A032F/M and similar firmwares with non-packed super.img.
Support for firmwares with/without additional partitions. Support for
arbitrary partition group names. Very experimental option to use empty
system_ext.img for additional privacy (applicable to some phone models/
regions). Lots of minor fixes.
1.03: Multiple .img files are now supported in GSI archive files (one of them
should be system.img in that case), e.g. Android AOSP zip files are now
supported directly. The logic of flashing with Heimdall now includes more
complex cases, such as flashing in two steps with a reboot. Unnecessary
code in GZ unpacking removed. Some other small fixes and optimizations.
1.1: New scripts heimdall_flash_stock.sh and heimdall_flash.sh added.
Lots of refactoring in repacksuper.sh (because of that there may be some
bugs left), improved and clarified UI logic, changes in where the files are
now placed (see help for details), direct work with stock Zip firmware
files, lots of minor changes.
1.11: Colored text now should be correctly displayed in almost any shell that
supports it except if it's explicitly disabled with NO_COLOR.
1.11.1: heimdall_flash.sh now can flash Super partitions unconditionally in one
step when using both the -s parameter and manually specifying parition
name (e.g. SUPER for SM-A127F).
1.12: The heimdall_flash_stock.sh script was significantly upgraded with lots of
new features. Now it theoretically allows upgrading of stock firmware
without erasing user data, keeping the GSI and custom recovery, etc.
(although it's not that straightforward, read the help for details).
A couple of fixes in the other scripts.
1.12.1: changed unlz4 to lz4 -d, as some distros don't have the needed symlink
1.13: In repacksuper.sh support added for the Vendor DLKM and ODM DLKM
partitions, as well as the experimental -v option to add or replace Vendor
DLKM with a custom image. A couple of minor fixes.
1.14: Greatly improved logic of heimdall_flash.sh, now it's possible to specify
both or either custom partition name and custom file name, and acquiring
PIT from device is done only when it's needed. Versioning scheme of the
scripts was unified: the script that was updated receives the updated
version number of the whole pack, the rest retain the old numbers.
1.15: up_param_tool.sh script was added: it allows altering of the boot
sequence images (logo, "not official" warning, etc.), as well as the
Recovery and Download internal graphics. Happy hacking, but please pay
attention to the warning displayed after extracting the JPEG files.
A couple of minor fixes in the other scripts.
1.15.1: Bug with failing LZ4 uncompression fixed in repacksuper.sh and
heimdall_flash_stock.sh.
1.15.2: Added the Ctrl+C trap in heimdall_flash_stock.sh, so now the temporarily
renamed files are correctly renamed back in case of flashing being
aborted with Ctrl+C. Upgraded Heimdall with the git pull requests, but
it seems those still do not cure the relatively rare issue when flashing
specific files gets completely stuck at some point.
1.15.3: The "file" tool used to identify PIT files was replaced with direct
reading of the file header as the first method proved to be unreliable.
1.15.4: Fixed a bug in heimdall_flash.sh (missing g flag in sed)
1.15.5: Fixed the compatibility issue with the older LZ4 compressors
1.15.6: Fixed compatibility issues with systems where /bin/sh is Bash, such as
ArchLinux
1.15.7: repacksuper.sh: fixed using the existing "repacksuper" dir as source,
also in this mode you can now specify "-" as new system image to reuse
everything inside the "super" subdir. New experimental -w parameter.
All scripts: the Ctrl+C trap now switched on and off the correct way.
Several other fixes.
1.15.8: Fixed using the heimdall_flash_stock dirs as source for repacksuper.sh.
A couple of other fixes.
1.15.9: heimdall_flash_stock.sh: fixed skipping of duplicate partitions (e.g.
vbmeta) for some shells; fixed upgrade-flashing of Galaxy A32 (default
behavior).
Spoiler: Known issues
During the script run you can see several "Invalid sparse file format at header
magic" warnings, just ignore them.
For some firmware files Heimdall may not work at all (freeze indefinitely or
exit with an error), in that case you have to resort to Odin. In many cases
Heimdall freezes when uploading files for some time, but that does not mean it
is completely frozen, just be patient.
In LineageOS, Dot OS and some other GSIs I tried on SM-127F the touch screen
remains not responsive for about 6 seconds after waking up. The problem is not
present at least with SM-127F/DSN phones made in India, but present at least in
those made in Vietnam. Another problem in the most, if not all, GSIs is that the
MTP USB file transfer does not work (at least on Linux) because of the "wrong"
(Samsung's instead of Google's) default MPT driver used by the kernel.
Both of the aforementioned problems can be solved by installing the fixed and
recompiled kernel.
For the last problem alternative solutions include using apps such as
Warpinator, Syncthing or ftpd.
Spoiler: Food for thought
When choosing a GSI to install I really don't recommend using ones which include
GApps and therefore use any of the Google services. Don't let corporations
gather your data. You bought the phone and from now on it should be all yours,
with all of its data, like a PC in the good old days. You own your device, and
nobody has the right to stick their nose into how you use your phone, gather any
statistics and push you any ads. You always have a choice to turn down
privacy-unfriendly stuff, the price of that "inconvenience" is actually
ridiculous. From my point of view, there is simply no point in using non-stock
systems if they are still littered with the privacy-unfriendly bloatware.
For the step-by-step guide (slightly outdated) read this and this post. Also be sure to read this post concerning the importance of optics.img. Concerning the up_param_tool.sh be sure to read this post.
The included binaries for the lpunpack, lpmake and Heimdall were compiled for the x86_64 architecture. If your PC architecture is different (e.g. x86 32-bit or ARM) you have to compile these tools yourself. The full source code is included (or otherwise available on GitHub).
Latest stable combinations of stock firmware and LineageOS (updated February 5, 2023):
SM-A127F: A127FXXU7BVI4 + LineageOS 20.0-td 20230115 arm64 bvS
SM-A325F: A325FXXU2CVK3+ LineageOS 20.0-td 20230115 arm64 bvS
Some recommendations (updated February 5, 2023):
If you are a newbie and don't know how to do unlock the bootloader and other such stuff, here is a good guide by LAST_krypton (follow the "Unlocking the booloader" section) or a shorter guide by cldkrs.
First flash the phone with the whole set of stock firmware using the heimdall_flash_stock.sh (Linux only) script with the -d parameter: the latter forces flashing the unsafe partitions, which are needed for complete re-flashing.
If you're on Windows use Odin instead. Although there is a "leaked" Linux version of Odin, it's still closed-source (of course), so I don't recommend using it on your main Linux PC. For using the Windows version of Odin on Linux you have to either use Windows in QEMU (tested and works) or probably Wine (untested). When using QEMU remember to add the SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="685d", MODE:="0666" line to the udev rules (e.g. /etc/udev/rules.d/30-qemu.rules) to enable the write access to the phone.
Sometimes Heimdall cannot flash the stock firmware and gets stuck at some particular file. Although you can successfully flash such a firmware using Odin, I recommend to better to find another firmware, may be one release older, because that may indicate some sort of incompatibility with your particular version of the phone.
The stock firmware comes in different revision numbers (also known as the baseband version), which are upgraded about once a year. Generally it should be beneficial to use the latest revision, but note that once you have upgraded it to a later revision there is no way back (at least known to me). In case you want to experiment with flashing of special kernels and other flavors provided by the XDA developers, if possible, you should probably stick to the very first revision.
If you already have the bootloader unlocked (OEM unlock) then after flashing the stock firmware there is no need to set up the Android, just go straight into the download mode again and flash the repacked super.img.
When downloading LineageOS or any other GSI select the normal arm64 bvS version, not vndklite version.
After flashing the OS go into the Recovery mode (hold volume up and power when rebooting) straight away and do the Factory reset. If you cannot get into the Recovery mode be sure to connect the USB cable before trying to.
If flashing with Heimdall completely freezes at some point make sure you've downloaded and repacked the correct arm64 b or a/b GSI and not arm and not a or a-only variant. If "sw rev check fail" message appears on the screen at some point just ignore it.
You can forcefully reboot your phone at any time, even if it seems bricked, by holding the volume down and power buttons for several seconds.
To upgrade your system to the recent version of the same OS just repackage it again using the same script and flash it normally. If the phone does not boot, get into the Recovery mode and try wiping the Cache partition (all your apps and settings should remain intact).
Most probably you don't need TWRP or any other 3rd party recovery tool at all, as the stock recovery tool works fine for just the factory reset after flashing the super file.
Try to avoid using Magisk if you just want to install another OS and nothing else. It is also not needed for LineageOS bvS version as it already has the su utility integrated, you just need to install the additional Superuser app by Pierre-Hugues HUSSON from the F-Droid store (although it's very old it works just fine).
It's possible that SM-127F/DSN internally is not A12 but actually M12, at least most of the tools and kernels made for M12 work on SM-127F/DSN while those made specifically for SM-125 and even other SM-127 versions do not. Therefore you can find more relevant info and tools in the corresponding XDA thread (my script is still remains relevant though).
I should test this for a127f
Bugs fixed: v0.91 & v0.91a
Bug fixed: v0.91b
Added the "file" utility to the list of requirements, updated readme.txt.
Thanks A LOT, this works! I am finally able to run LineageOS on my phone!
For Windows 10+ users: WSL runs this script just fine with a few additional steps.
1. Install WSL 2 and any Linux distribution from Microsoft Store
2. Run the distribution to finish setup
3. Install the required packages from the post (sudo apt install for Ubuntu/Debian)
4. Shift + Right Click in the folder where you have the script, the AP and the GSI packages
5. Open Linux shell there
6. Unpack & run script as stated in its help
Voila!
Wow ! Great job! I want to try it, but i'm getting many "Invalid sparse file format at header magic" while running the script, is it OK to flah the super.tar anyway?
jadfa said:
Wow ! Great job! I want to try it, but i'm getting many "Invalid sparse file format at header magic" while running the script, is it OK to flah the super.tar anyway?
Click to expand...
Click to collapse
It is totally OK
jadfa said:
Wow ! Great job! I want to try it, but i'm getting many "Invalid sparse file format at header magic" while running the script, is it OK to flah the super.tar anyway?
Click to expand...
Click to collapse
Yes, it is fine. These are just warnings produced by lpmake, they can not be suppressed. I could only suppress all the stdout/stderr from lpmake but it's no good in case of more serious warnings.
Updated to v0.92 with a couple of minor improvements.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What should I do next with the raw file?
"Unknown super file format" is this how it should be?
ANDARXapi said:
View attachment 5490897What should I do next with the raw file?
"Unknown super file format" is this how it should be?
Click to expand...
Click to collapse
Of course not. The format of each file is checked using the "file" utility, it should return the string "Android super image". Try to run file /home/toor/APfilles/super.stock.raw . What is the response? And try doing it all without sudo. There is no need in root privileges.
uluruman said:
Of course not. The format of each file is checked using the "file" utility, it should return the string "Android super image". Try to run file /home/toor/APfilles/super.stock.raw . What is the response? And try doing it all without sudo. There is no need in root privileges.
Click to expand...
Click to collapse
The raw file opens as a picture
uluruman said:
Of course not. The format of each file is checked using the "file" utility, it should return the string "Android super image". Try to run file /home/toor/APfilles/super.stock.raw . What is the response? And try doing it all without sudo. There is no need in root privileges.
Click to expand...
Click to collapse
run without sudo: 168: ./lpunpack_and_lpmake/lpunpack: Permission denied Cannot correctly unpack the super file. Exiting ...
I managed to fix the script, you just need to give chmod +x rights to the files in the folder "lpunpack_and_lpmake": lpunpack, lpmake, lpflash, lpdump, lpadd
ANDARXapi said:
I managed to fix the script, you just need to give chmod +x rights to the files in the folder "lpunpack_and_lpmake": lpunpack, lpmake, lpflash, lpdump, lpadd
Click to expand...
Click to collapse
Hmmm. I have updated it, may be it'll help. Could you please test the latest version (v0.92a)? I want to work it out of the box for everyone, without sudo or any tweaks.
uluruman said:
Hmmm. I have updated it, may be it'll help. Could you please test the latest version (v0.92a)? I want to work it out of the box for everyone, without sudo or any tweaks.
Click to expand...
Click to collapse
Okay, I'll test it tomorrow, today I want to relax at the computer all day
uluruman said:
Hmmm. I have updated it, may be it'll help. Could you please test the latest version (v0.92a)? I want to work it out of the box for everyone, without sudo or any tweaks.
Click to expand...
Click to collapse
Checked, it works right away
Is there a way to install magisk and root?
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