Database Info

[ROM][Kernel][cm13/lineage14.1]Nethunter fully patched HID and external wireless card

{
"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

[ROM][UNOFFICIAL][10] LineageOS 17.0 for K-touch i9 mini-phone (Anica i9) (MT6739)

Introduction
This is the LineageOS 17.0 (non-GSI) port for K-touch i9 a.k.a Anica i9. Due to the lack of kernel source code, this port comes with a prebuilt kernel image, but the ramdisk has been updated to support a proper System-as-Root system partition as is required by Android 10.
This is ONLY compatible with the MT6739 variant of this phone.
About the phone
The K-touch i9 is an ultra-mini phone produced by K-touch (Ktouch / Anica) based on the MT6739 SoC. I got the phone purely due to its interesting size (similar to the Palm phone) and the desire to port real custom ROMs to it to see if they can work well. I mainly use it as a backup phone, so this port might not be thoroughly tested enough for daily drive.
Known Issues
- Some particular animation / gifs will skip frames or repeat incorrectly
Images
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing instructions
1. Unlock the phone (reboot to bootloader by holding volume up on boot, run `fastboot flashing unlock` and confirm)
2. Flash TWRP image from here
3. Reboot to recovery (hold volume up and choose Recovery accordingly)
4. Backup all stock partitions whatever way you like (especially boot / vendor)
5. Flash this LOS 17 port image and format data
6. Reboot and enjoy
Please note that after flashing this LOS 17 image, you have to restore the stock boot.img before being able to install A-only Android 10 GSIs again. Although you MIGHT be able to boot phh A/B GSI 10 on the boot.img of this LOS 17 port, please note that this is not tested and you still need to shrink the image size before phh GSIs can work -- the same as the A-only situation.
Why not GSI
There is no reason why not to use a phh GSI on this phone, given that phh GSIs work pretty well and I have actually fixed a few bugs for it too and I absolutely love it. However we can't play with some certain things, for example, transitioning to System-as-Root, in a GSI, and that's why I started this port just for fun. Also this device has such a small system partition that GSIs won't work out-of-the-box and require some manual adjustments just for the device, which kind of defeats the purpose. Nevertheless, I will contribute my fixes to GSIs so that things will work as well on GSIs as on my device-specific ROM ports.
Downloads
20191025: https://www.androidfilehost.com/?fid=4349826312261605900
Alternatively, you may check the latest updates to both the TWRP and the LOS 17 port on my GitHub
Source code
https://github.com/PeterCxy/android_device_ktouch_i9
There is no kernel source code available for this device, unfortunately.
Credits
all the people that have worked on MTK devices before me.

twrp link does not work

theleftykid said:
twrp link does not work
Click to expand...
Click to collapse
It works here. It links to a GitHub release page where you can download recovery.img for TWRP

Hi,
I bought this phone, but with different CPU- MT6580, 5MP camera at the back, would this ROM be compatible with it well?
I've tried to flash the TWRP recovery, but it failed - "FAILED (remote: size too large)" so it mean the recovery image not compatible with my phone?
This device is really nice, but huge let down by the operation sys. The battery drain really fast, always "phone idle" take place at the top of battery consuming chart.
Thank you!

hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.

theleftykid said:
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
Click to expand...
Click to collapse
Based on the previous comment before you, you seem to have the MT6580 version of the phone. This means you have a different and smaller gpt than the one from the OP that uses MT6739. You can't flash this ROM or any recovery from the MT6739 since they have different hardware and different partition layout. If you flash something, it will end with a nice brick
Cheers!

Rortiz2 said:
Based on the previous comment before you, you seem to have the MT6580 version of the phone. This means you have a different and smaller gpt than the one from the OP that uses MT6739. You can't flash this ROM or any recovery from the MT6739 since they have different hardware and different partition layout. If you flash something, it will end with a nice brick
Cheers!
Click to expand...
Click to collapse
Well, I’m sending myne back to get the mt3739 so I could mount 128gb sd card and to try this buil. It look promissing.

theleftykid said:
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
Click to expand...
Click to collapse
You boot into the original OS and the recovery will be back.

Thank you for this ROM.
I used it on my K-touch i10. Its the same as the i9 but the shape is slightly different.
I have the 3gb - 64gb version and it seems OK.
I had to use BiTGApps-Q for Playstore to appear.
I also had to go into the USB developer options to set up file transfer from a PC.
And no wallpaper app from holding on home screen.
I hope you keep this up to date else I might have to try and work out how to apply security patches.
Thanks again
EDIT. Oh so are you saying I could just try and install the GSI?
Edit. OK so Wellbeing and problems with Gapps is to do with Android 10 and gapps.

I also found twrp hard to control. The swipe action and pressing near the edge was difficult.
I don't have face recognition to unlock, not sure if that's because lineage os doesn't have it or the i9 doesn't, but certainly possible on my i10.
The swipe action in lineage is also difficult.
Thanks again. Just want to let you know.
Edit. Also a problem for me is when it's charging, touch screen gives the odd ghost press when used.
Ive found forcedoze useful with this phone.

Works with K-Touch M16?
Theoretically speaking this Rom should work in the K-Touch M16 as it has the exact same specs, processors, etc. Being the only difference is that it has a fingerprint sensor.
So I was wondering does anyone know if this custom ROM and TWRP works on the K-Touch M16.?

how do i download this rom. there are no active links available!

PeterCxy said:
Downloads
20191025: https://www.androidfilehost.com/?fid=4349826312261605900
Alternatively, you may check the latest updates to both the TWRP and the LOS 17 port on my GitHub
Source code
https://github.com/PeterCxy/android_device_ktouch_i9
There is no kernel source code available for this device, unfortunately.
.
Click to expand...
Click to collapse
From the first post

m16 tried
I have tried this with my M16, which is very similar to i9, same cpu same spec, got fingerprint though... no luck, unable to boot into recovery, anyone successfully done?

It worked with my K-touch i10.
I guess you should start looking at TWRP. If you have the same processor you should be able to get TWRP going.
Sorry no help here, maybe try a TWRP forum or something.

chinese bootloader
hi, i just got the phone so i wanted to flash this rom. but my bootloader is in chinese and i don't speak/read chinese.
can anyone here please help me get trough the bootloader so i do all the steps correctly.
i attached the picture from bootloader and also what google translate offers for translation.
does volume up and down works correctly on your devices? on my it just jumps one step down and up on ether up key or down key when i press and hold the key ti gradually turns volume up on ether up or down key.

I have an i10 and am no expert.
When I reboot and hold up-volune I get 3 options. Recovery, Fastboot and Normal in that order.
Are you sure your phone is the mt3769. As I had an i10 which was was MT6580 and I got those options. I did have Fastboot though. Sorry don't still have it for reference.

I just found out on youtube this menu should pop up when you press volume down + power on. But on my phone it also boots to this menu when i press volume up + power on. Guess i received defective volume buttons on my phone. Too bad as it is such a nice little phone.

Are you able to use the volume keys to move up and down the menu you took a picture of? Moving in this menu and selecting should be the up and down volume keys. Guess then you could see for sure if you have a key problem.
I did manage to take my phone apart as when I dropped it I managed to disconnect the screen cable inside but was lucky to be able to fix it.
---------- Post added at 12:23 PM ---------- Previous post was at 11:44 AM ----------
PeterCxy said:
...you still need to shrink the image size before phh GSIs can work...
...
Also, this device has such a small system partition that GSIs won't work out-of-the-box and require some manual adjustments just for the device, which kind of defeats the purpose. Nevertheless, I will contribute my fixes to GSIs so that things will work as well on GSIs as on my device-specific ROM ports.
Click to expand...
Click to collapse
Hello I'd like to update this for myself. I thought I'd use the GSI image but you say it needs resizing before use. Can you give me any pointers as to how you do this?

free30 said:
Are you able to use the volume keys to move up and down the menu you took a picture of? Moving in this menu and selecting should be the up and down volume keys. Guess then you could see for sure if you have a key problem.
I did manage to take my phone apart as when I dropped it I managed to disconnect the screen cable inside but was lucky to be able to fix it.
Click to expand...
Click to collapse
i am unable to enter the correct bootloader that gives you three options you mentioned before. i already contacted the seller to see what we can do cause i just received the phone. on this chinese menu i can navigate only down (pressing volume up or down moves the selection down) and i can select the item via power button.

Install Any GSI ROM on the V60

I AM NOT RESPONSABLE IF YOU BREAK YOUR DEVICE OR ANY DAMAGE CAUSED BY NOT FOLLOWING INSTRUCTIONS.
Requirements:
Unlocked Bootloader
Removed Vbmeta verity (Boot Patched with magisk)
ADB and Fastboot: Adb
A GSI Rom: GSI Rom List
ENG ABL (In case you brick the device and you want to go to fastboot)
Enabled USB debugging on developer Options
Developer Options go to Settings => System => About Phone => Software Information and tap Build Number until it either asks you for your password or says you are a developer at the bottom
A Brain
Instructions:
Before doing anything make sure you have a backup of your device partitions.
All your data of the internal memory will delete.
1. Put the GSI you have downloaded from your choise (Make sure you have extracted the File) on the same folder than your Fastboot)
{
"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"
}
2. Open a CMD window on the same folder than Fastboot ( Right click + shift key on the fastboot folder and select open command prompt)
3. Run adb devices and make sure it says Device and not Unauthorized.
4. Write the command Adb reboot fastboot
5. On the Phone You will see a Fastbootd screen ( Image is an example, I dont have a camera with me at the time of doing this Guide)
6. Run Fastboot Devices and make sure your device is showing there
7. write the command fastboot getvar all to check your boot slot
8. Execute fastboot flash system_(Put your slot from previous step) the image name of your gsi.img, and wait until everything download and make sure that every single sparse sent says Okay
8. After Last step just execute fastboot erase userdata
9. just reboot the device and enjoy
Any additional question or issue just let me know and I will help you Gladly as soon as I can

Worked perfectly on my att LG v60. Cheers. it's my backup phone but thanks for giving it new life. LG software sucks. Doing this later on with my second LG v60.

Jaimesco12 said:
Worked perfectly on my att LG v60. Cheers. it's my backup phone but thanks for giving it new life. LG software sucks. Doing this later on with my second LG v60.
Click to expand...
Click to collapse
I agree. Oem software is so loaded with bloatware and bull****. And then of course ALL the carriers pile on their **** and suddenly you have a smartphone that's not really a phone anymore. It's now just a tracking/marketing device that happens to let you make phone calls, send emails. and surf the web so you can provide cookies to be uploaded when you're not looking.
I do give credit to Apple for pulling in the reins on Facebook. Hopefully, Google will be forced to do the same. They're the biggest tracker/marketer of information out there.

Btw, I've been running an a12 gsi rom for several weeks now. First, I tried the Andy Yan LOS19 vndklite secured rom but unfortunately it didn't gapps capability which is sort of a no go for a lot of people. I then switched to Phhusson' vndlite secure with gapps rom and it's been great. So far everything seems to work great except Qdaq.

Damn. Now I may have to build my phone for the second time in a week. One question:
1) How/where do I get the LG apks to properly make use of the phone's hardware? I'm thinking camera, FM Radio and DAC specifically. Plus any others I may be missing. Or is that step not necessary?
[NG]Owner

NGOwner said:
Damn. Now I may have to build my phone for the second time in a week. One question:
1) How/where do I get the LG apks to properly make use of the phone's hardware? I'm thinking camera, FM Radio and DAC specifically. Plus any others I may be missing. Or is that step not necessary?
[NG]Owner
Click to expand...
Click to collapse
I'm already working on porting stock apps to Custom including the Quad-Dac, i dont have an ETA for ir right now but its on the way

Jaimesco12 said:
Worked perfectly on my att LG v60. Cheers. it's my backup phone but thanks for giving it new life. LG software sucks. Doing this later on with my second LG v60.
Click to expand...
Click to collapse
I'm happy to hear that it helped you

Does Android Pay work on this?

Will this process also work for the v40 as well? And if so, can I expect the IMS stack to work on the v40 such that VoLTE and WiFi Calling on Tmo can be enabled?
For that matter do/will VoLTE and WiFi Calling work on TMo using GSI ROMs on a v60?
[NG]Owner

failed, kernel crash, dont't know the reason
update: show no command

I'm assuming that if I install a GSI on the V60, I lose dual-screen usage correct?

jblparisi said:
Does Android Pay work on this?
Click to expand...
Click to collapse
Depends of the GSI you have chosen, some of them comes with Safetynet already approved

peterwode said:
failed, kernel crash, dont't know the reason
Click to expand...
Click to collapse
Make sure alll sparces says OK, also if you are on android 11 you cannot flash a GSI with android 10

Play4Zeta said:
I'm assuming that if I install a GSI on the V60, I lose dual-screen usage correct?
Click to expand...
Click to collapse
I havent tested that, I broke mine a while ago

Kratos574 said:
I havent tested that, I broke mine a while ago
Click to expand...
Click to collapse
Any reason you would think it wouldn't? Mostly just have my V60 for the dual screen.

Jaimesco12 said:
Worked perfectly on my att LG v60. Cheers. it's my backup phone but thanks for giving it new life. LG software sucks. Doing this later on with my second LG v60.
Click to expand...
Click to collapse
Hey mate, you could tell me how you did the prep work to install the GSI room on the ATT variant? Ive been trying to unlock it and installing TWRP but i havent found a reliable way of doing it.

Do you know what rooms work well with the v60? (like having QDAC functionality for instance)

Kratos574 said:
I'm already working on porting stock apps to Custom including the Quad-Dac, i dont have an ETA for ir right now but its on the way
Click to expand...
Click to collapse
wait Quad-Dac

Just wanted to say a big thanks to Kratos for putting this post together. I had some early issues but it turns out that's because I was using 'Minimal ADB and Fastboot'
For whoever comes next here's how I fixed a couple of problems as I went.
ERROR: Failed: remote partition not found - You need to be in fastbootD via ADB REBOOT FASTBOOT, not the fastboot/bootloader via turning off device, holding vol down and plugging in a usb cable.
ERROR: Remote: Operation not permitted. - Minimal ADB and Fastboot is not new enough - download latest SDK platform tools and open an administrator CMD prompt from that directory instead.
Other errors or failure of individual parse files can be fixed by using a better quality cable - you're sending a lot of data via fastbootd. Give yourself the best shot at success.
I installed OctaviOS yesterday and was absolutely blown away - it's extremely fast, the battery life is incredible and the level of deep customisation rivals any rom I've ever used.
Unfortunately, haptic feedback / vibration does not work AT ALL, and nor does the 3.5mm Jack. Also GCAM, nor any other camera app I tried was able to access the wide angle lens so I'll be trying to figure out how to get back to EA firmware today for now.
If someone with the skills could manage a non-gsi port of OctaviOS with cam, haptic and 3.5mm working properly I'd be on it in a heartbeat. THAT is what Android should be. Bloat free but highly customisable.

bandario said:
Just wanted to say a big thanks to Kratos for putting this post together. I had some early issues but it turns out that's because I was using 'Minimal ADB and Fastboot'
For whoever comes next here's how I fixed a couple of problems as I went.
ERROR: Failed: remote partition not found - You need to be in fastbootD via ADB REBOOT FASTBOOT, not the fastboot/bootloader via turning off device, holding vol down and plugging in a usb cable.
ERROR: Remote: Operation not permitted. - Minimal ADB and Fastboot is not new enough - download latest SDK platform tools and open an administrator CMD prompt from that directory instead.
Other errors or failure of individual parse files can be fixed by using a better quality cable - you're sending a lot of data via fastbootd. Give yourself the best shot at success.
I installed OctaviOS yesterday and was absolutely blown away - it's extremely fast, the battery life is incredible and the level of deep customisation rivals any rom I've ever used.
Unfortunately, haptic feedback / vibration does not work AT ALL, and nor does the 3.5mm Jack. Also GCAM, nor any other camera app I tried was able to access the wide angle lens so I'll be trying to figure out how to get back to EA firmware today for now.
If someone with the skills could manage a non-gsi port of OctaviOS with cam, haptic and 3.5mm working properly I'd be on it in a heartbeat. THAT is what Android should be. Bloat free but highly customisable.
Click to expand...
Click to collapse
Just go to Phh Settings and click on Alternate audio policy, That fixes 3.5mm jack

LineagOS - Jingpad

Has anyone looked into compiling / porting LineagOS for the Jingpad A1? They released the source code. Why use LineagOS and not their released because theirs is in Chinese and it's lacking features available in LineagOS. I understand that the company has stopped developing their default OS and everyone with them now kind of has a dead product. I someone ported UBports to it, but Ubports lacks somethings that LineagOS / Android brings to the usefulness for a tablet. I know they had android app support that you could install on their default OS, but it has bugs and some apps were slow or errored out upon launch.
jingpad-bsp
jingpad-bsp has 421 repositories available. Follow their code on GitHub.
github.com
Android ROM source code for JingPad A1
The source code has been zipped into the 8 packages below, you have to download them all before you compile. How to compile Full compilation (take the userdebug version as an example, if you are editing the user version, just change the ud710_3h10_native-userdebug-native in the instruction to...
forum.jingos.com

[Guide] Install Gapps on JingPad (Android ROM)
Here are some extra changes I made in my pac file: Changed internal software version to 1.0.002.014 (Previously 1.0.002.013) Just to distinguish my build from the official pac file Changed OS name to “Android 10” (Previously “JingOS 1.0”) Because it is Android 10 Changed...
forum.jingos.com
Follow the instructions to the letter and you will have gapps and all languages... Be careful when rebooting after installing the ROM to change from Chinese to English...
Let me explain: after installing the ROM you restart; change the language from Chinese to English (for the moment you will not see other languages); set developer mode; restart in recovery and go ahead following the guide.
That's already something waiting for lineage OS

Excellent thank you for this. I am trying to flash my system with the image in the post. The process worked, thank you for showing me the post.
How to change to english
edit the following file in the source code
/source/device/sprd/roc1/ud710_2h10u/jingos/device.mk
edit the following lines.
persist.sys.language=en
persist.sys.country=US
persist.sys.timezone=America/New_York
persist.sys.locale=en-US
ro.product.locale.language=en
ro.product.locale.region=US
and compile
cd /source/vendor/sprd/release/IDH/Script
./build_pac.sh -a ud710_3h10u_native-user-native -b all 2>&1 | tee build.log
​

Have there been any new developments for the JingPad? I have one and I would consider putting Lineage OS on it. However, I'm not competent enough to build it from scratch. Is anyone developing AOSP for this tablet?
I am presently running UBPorts (Ubuntu Touch) and it is certainly less than stellar. I can't get WayDroid to run. Things might change when UT upgrades from 16.04 to 20.04 in the near future. But for now, I am checking everything before I stick it in the closet.

Hmm, I guess no one has mirrored the instructions?
Because all jingos.com links are now dead.
Maybe someone who has copied the instructions or the original author could add them to this thread?

I have a lot of the files for this tablet including the flashing application Research Download, the .pac file from January 2022, and USB drivers for Windows. I have the .docx file with the Research Download instructions.
I am leary to reinstall the JingOS without clear instructions on how to do it since I now have UBPorts installed.

LoTo62 said:
[Guide] Install Gapps on JingPad (Android ROM)
Here are some extra changes I made in my pac file: Changed internal software version to 1.0.002.014 (Previously 1.0.002.013) Just to distinguish my build from the official pac file Changed OS name to “Android 10” (Previously “JingOS 1.0”) Because it is Android 10 Changed...
forum.jingos.com
Follow the instructions to the letter and you will have gapps and all languages... Be careful when rebooting after installing the ROM to change from Chinese to English...
Let me explain: after installing the ROM you restart; change the language from Chinese to English (for the moment you will not see other languages); set developer mode; restart in recovery and go ahead following the guide.
That's already something waiting for lineage OS
Click to expand...
Click to collapse
Is there any chance you keep the guide or somehow remember how to do it? The link is dead already. I got developer mode ready.

r3d10tu5 said:
Is there any chance you keep the guide or somehow remember how to do it? The link is dead already. I got developer mode ready.
Click to expand...
Click to collapse
No. Sorry. The only files I have are the original files distributed with the JingPad.

I found those links, and hope they can help those who come across this topic. I can share the original files either.
-
- http://web.archive.org/web/20220823...ow-to-flash-android-rom-on-jingpad-a1-c1/2716
- https://web.archive.org/web/2022052...ide-install-gapps-on-jingpad-android-rom/3007

r3d10tu5 said:
I found those links, and hope they can help those who come across this topic. I can share the original files either.
-
- http://web.archive.org/web/20220823...ow-to-flash-android-rom-on-jingpad-a1-c1/2716
- https://web.archive.org/web/2022052...ide-install-gapps-on-jingpad-android-rom/3007
Click to expand...
Click to collapse
Great work. Thanks.
Edit: I downloaded the gapps file and I have all the rest I need. Now I need to look into if this will flash OK after installing UBPorts.

jmd8800 said:
Great work. Thanks.
Edit: I downloaded the gapps file and I have all the rest I need. Now I need to look into if this will flash OK after installing UBPorts.
Click to expand...
Click to collapse
I can confirm it would be no problem since I got utouch on my device before I reloaded it with android as an experiment; you can see. It would be a piece of cake.
ANW, in case you and everyone miss this part by caten (the one who makes the above video). I did follow him/her and success to get a working gapps. I want to add that you properly should clear the storage of the google play store and google play services, also CACHE (not storage) of google services frameworks in one go before trying to stop those services and try to sign in again.
GL.
How did you install the gapps?
I tried again today, and finally found how I was able to use gapps before.
You should have booted to the system once, before you boot to recovery and flash gapps.
“open_gapps-arm64-10.0-pico-20220215.zip” and “open_gapps-arm64-10.0-nano-20220215.zip” are probably the only two available version that work.
After reboot, you should get an error like “This device isn’t Play Protect certified” which keeps popping up, not “There is a problem contacting with google server”.
Steps:
Go to play store, click sign in;
It said “This device isn’t Play Protect certified”, click that green link “g.co/AndroidCertifiedDevice”;
Follow Google’s instructions to register your device;
Go to Settings, try your best to force stop gms & play store and clean their data;
(But do NOT clean gsf’s data! Clean cache is enough)
Go to play store and sign in before gms know it.
Click to expand...
Click to collapse

r3d10tu5 said:
I can confirm it would be no problem since I got utouch on my device before I reloaded it with android as an experiment; you can see. It would be a piece of cake.
ANW, in case you and everyone miss this part by caten (the one who makes the above video). I did follow him/her and success to get a working gapps. I want to ask that you properly clear the storage of the google play store and google play services, also CACHE (not storage) of google services frameworks in one go before trying to stop those services and try to sign in again.
GL.
Click to expand...
Click to collapse
Looks like I have some work cut out for me. If I can get this to work and cover my needs I'll be happy. If not .... back in the closet it goes and I will buy an Apple or Samsung next week as I need something for travel.
Thanks

r3d10tu5 said:
I can confirm it would be no problem since I got utouch on my device before I reloaded it with android as an experiment; you can see. It would be a piece of cake.
ANW, in case you and everyone miss this part by caten (the one who makes the above video). I did follow him/her and success to get a working gapps. I want to add that you properly should clear the storage of the google play store and google play services, also CACHE (not storage) of google services frameworks in one go before trying to stop those services and try to sign in again.
GL.
Click to expand...
Click to collapse
This afternoon I set up a Windows computer and I have the pac file loaded into the Research Download program but it will not flash. I am wondering if I am missing something.
When I boot the JingPad to recovery (UB Ports orange) and look in the command line adb see the Jing Pad. (Windows actually mounts the device if I am fully booted to UTouch.) It will not flash the pac file to the JingPad. I waited 5 or 10 minutes and tried 2 or 3 times. USB drivers are working although I did get an error that the USB drivers are out of date.
I have developer mode ON in UTouch.
Once I get to recovery are there options I need to select?
For some reason, I cannot reboot to bootloader if that matters.
What am I missing?

jmd8800 said:
This afternoon I set up a Windows computer and I have the pac file loaded into the Research Download program but it will not flash. I am wondering if I am missing something.
When I boot the JingPad to recovery (UB Ports orange) and look in the command line adb see the Jing Pad. (Windows actually mounts the device if I am fully booted to UTouch.) It will not flash the pac file to the JingPad. I waited 5 or 10 minutes and tried 2 or 3 times. USB drivers are working although I did get an error that the USB drivers are out of date.
I have developer mode ON in UTouch.
Once I get to recovery are there options I need to select?
For some reason, I cannot reboot to bootloader if that matters.
What am I missing?
Click to expand...
Click to collapse
Did you follow the below step til the progress showing on the ResearchDownload (be sure to press start button on the ResearchDownload)? I have had to wait a bit and it was a success without any issues. I actually did flashing the device three times. In my case, there was no logo, just a progress bar on the ResearchDownload.
- Click the “Power” button then the “Volume Down” button. Do not release the buttons until the JingPad logo appears

r3d10tu5 said:
Did you follow the below step til the progress showing on the ResearchDownload (be sure to press start button on the ResearchDownload)? I have had to wait a bit and it was a success without any issues. I actually did flashing the device three times. In my case, there was no logo, just a progress bar on the ResearchDownload.
- Click the “Power” button then the “Volume Down” button. Do not release the buttons until the JingPad logo appears
Click to expand...
Click to collapse
I have 2 questions:
1) How long do I need to wait to see the progress bar for the flashing part? (I see the progress bar loading the pac file)
2) When I press ' power' and then 'volume down' the tablet boots to UB Ports recovery screen. Is this what is supposed to happen?
Thanks again

jmd8800 said:
I have 2 questions:
1) How long do I need to wait to see the progress bar for the flashing part? (I see the progress bar loading the pac file)
2) When I press ' power' and then 'volume down' the tablet boots to UB Ports recovery screen. Is this what is supposed to happen?
Thanks again
Click to expand...
Click to collapse
In my case, I start the process on the ResearchDownload, then hold the combo keys power + volume down. Next, release combo keys when I see the progress bar start loading and wait until the Status becomes Finish, and the Progress is Passed. Afterward, I just unplugged my tablet and restarted it.
Something's like this.
{
"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"
}

r3d10tu5 said:
In my case, I start the process on the ResearchDownload, then hold the combo keys power + volume down. Next, release combo keys when I see the progress bar start loading and wait until the Status becomes Finish, and the Progress is Passed. Afterward, I just unplugged my tablet and restarted it.
Something's like this.
Click to expand...
Click to collapse
Thanks. I was just about to try again when I saw your post. Using this method I got better results but I cannot install because 'my driver version is too low'. I'll have to dig into this. But it appears to contact the JingPad and even errored out in the status bar. Progress!
I don't use Windows so I don't have a legitimate Windows OS working. It says it is test mode as I've not registered it. I can source the BIOS to find the key and hopefully that will let me get to a point where I can update the driver required to connect the PC and the JingPad.
Thanks again

Success! Thanks for all of your help @r3d10tu5
Well.... Success installing the pac file. I'm still working on the gapps. the adb command said it was a successful instal but Google software is not on the screens.

Just a thought as I was playing with this. Has anyone tried to use microG instead of going through all the hoops to get Google services running?

[UMX U696CL- RELEASE THREAD]

{
"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?