yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] mini4mw:
All,

I've been trying to change the bootloader and root this tablet but I can not find a TWRP img version that is compatible. I've tried about 30 different phone variants that should be close to the tablet specs. I've been loading via PC command line and adp/fastboot commands. All TWRP images load fine to recovery partition (or seem to be), but all I get at this point is a FASTBOOT where I can load another TWRP image via adp/fastboot (instead of a bootloader) or just load the OS. I have two of these tablets. One I bought off ebay and has a different build and one from a Yamaha side by side that has original software/build. The specs on both are exactly the same. Ideally I'd like to get TWRP running, then take an image of the OEM tablet OS and load it onto the ebay tablet. They both work, but the ebay tablet will not run the Yamaha software for some reason . I haven't been able to find any logs, another reason for root access. Any guidance would be appreciated., maybe a specific TWRP to try. This is what I know about the tablet:

Made by Mio, subsidary of MiTac. They make 'industrial' tablets, weather proof, drop proof, etc

Android Recovery shows (when bootloader would show up)

Mio/chiron/chiron

6.0.1/MMB29M/buildmach05141147

Model: Yamaha Adventure Pro by Magellan (chiron)

Manufacturer: Mitac_International_Corp

Brand: Mio

Board: msm8909

Hardware: qcom

Ram: 2GB

Storage: 12GB

API level 23

Security Patch Level: 2016.05.01

Bootloader: unknown

Build: R27.2.5640.1116

Java VM: ART 2.1.0

Kernel Arch: armv7l

Kernel Ver: 3.10.49-ga91d917

Snapdragon 210/212 1.27GJz

Arch: 4x ARM Cortex-A7 @ 1.27GHz

Revision: r0p5

GPU: Adreno 304 @ 456MHz

Thanks-
[Android Q&A, Help & Troubleshooting] mini4mw:
So just checking back in to see if anyone can help. I tried another 10 or so TWRP versions and same result. When it powers on, it vibrates and loads the OS. On some TWRP images it powers on/vibrates and then after 3 sec or so vibrates again and loads the OS, like it can't see the bootloader at all and fails to backup? The TWRP images I've tried are all based on Android 6 and when I can verify, the Snapdragon 210/qualcomm CPU. I reboot to bootloader (which just goes to fastboot) after install to make sure it doesn't get overwritten.

Anywho, I've searched for many hours, tried many programs (surprised I haven't bricked it yet) and can't get root access or TWRP to load. I called Yamaha and I can send it in and have them re-image. I just wanted to check back in here and see if anyone had ideas or wanted to try something before I give up. I just want the Yamaha apps to work anyway. I'll give it a few more days and see if anyone has an idea.
[Android Q&A, Help & Troubleshooting] mini4mw:
Is there some kind of default image I can boot from the microSD and then mount the tablet FS? Similar to what you would do to reset a Linux root pass?
[Android Q&A, Help & Troubleshooting] mini4mw:
So i sent this off to Yamaha and they had it for a few months and couldn't fix it. Not sure what was done, but now its just in a reboot cycle. I can get to a fastboot prompt, but it shuts off - I think I just need to charge it for a bit, but its annoying as when ever its plugged in, it powers on automatically.

Anyone have any fastboot images that may work? I tried a bunch last time from twrp.me but none worked. Seeing how its completely useless at this point, I'm just going to start a record of everything I try until (hopefully) I can find one that allows it to at least boot and perhaps get twrp loaded and root it out to get it functional again.
[Android Q&A, Help & Troubleshooting] mini4mw:
messing around with this again and through some mix of commands I was able to get it to boot again. I was in fastboot and tried

fastboot boot .\twrp-3.2.1-0-chiron.img

and that rebooted the device, but not to TWRP but to the actual OS. I then rebooted to the bootloader and the original showed up from when I first got the device and I wiped to factory defaults.

ok so now we are booting and all is somewhat normal, except I still don't have root or twrp installed.

rebooted to fastboot and tried booting twrp again. again it just went to the yamaha adventure pro screen and loaded the OS.

I tried via shell to see if it hasa recovery folder, but I can't access the directory (access denied)

ok, screw it. Its not working the way I want it so

adb reboot fastboot

fastboot flash recovery .\twrp-3.2.1-0-chiron.img

adb reboot recovery

again, reboots, no bootloader/recovery, just loads the OS. If I hit power/vol down I can get the fastboot screen. power/vol up, just constant reboots (feel unit vibrate on reboot).

the volume button is a rocker switch so I can only hold one or the other down and there is no lock button. only power and vol up OR down.

When it does boot I have the welcome widget, android back/apps/open apps button and some Yamaha icons, but nothing on the screen is working/responding. I can use vol up/down physical button and power, but if I hit power button, the shutdown/reboot touch options don't respond. No swiping in any direction responds either. I can access via adb shell, but permissions to most places are still an issue.

Trying some more things to see if I can get touch screen back or to the original bootloader to see if I can factory wipe and start over again.
[Android Q&A, Help & Troubleshooting] mini4mw:
so the touchscreen works, but not from the home screen/yamaha splash. If I unplug I get a pop-up low battery continue or shutdown and I can click those options and another pop-up related to power when I unplug the USB. swiping/hitting anything else does not.

power/up - constant reboot, probably the twrp I flashed to recovery that doesn't work

power/down - fast boot
[Android Q&A, Help & Troubleshooting] mini4mw:
I also tried all 7 chiron imgs from twrp and all fail to boot at fastboot pc shell. it just loads the OS, no bootloader or fastboot comes up.
[Android Q&A, Help & Troubleshooting] mini4mw:
ok, so looking at this:

How to Root Android 14 via Magisk Patched Boot/Init_Boot [Video]

In this guide, we will show you the steps to root your Android 14 device via Magisk patched boot/init_boot.img.

droidwin.com

Since I have access to copy over the boot image via adb, I can

- copy boot to Downloads folder

- run magisk to patch boot.img

- restart to fastboot and boot the magisk test image

- verify it works, reboot to boot loader and then flash the boot partition with the patched image

Yes?

thanks-
[Android Q&A, Help & Troubleshooting] mini4mw:
ok, so did a dd copy on the aboot/boot/config/oem/recovery copied from an identical system. Booted into recovery, which now shows the original recovery and performed a wipe/reinstall. screen still is not fully functional in that I can't click on any icons, but if I hold down I get the widget menu and request for Launcher3 to access media, photos, files but I can't click on allow. Again a permission issue. I flashed the system partition from fastboot, rebooted and I got the android upgrading/optimizing, rebooted on its own and same main screen, but again same screen issue.

So there would appear to be a permission problem somewhere, ie launcher3 but maybe more, that is not making its way over from the good tablet to the faulty one. Maybe something from keystore?

digging around again.
[Android Q&A, Help & Troubleshooting] mini4mw:
farting around with this for a few hours. Tried:

adb shell getevent -l

and I can see the screen respond in some areas, such as holding in one spot and getting the widget menu. Others never register a touch. If the widget menu comes up, an area that was not responding now does respond.

I disabled magellan and yamaha packages, rebooted. Same issue.

I did a factory wipe and when it first comes up, some areas respond while others do not - you have about 30 seconds when it comes up with plain android before it reboots to the yamaha build.

So it would appear to be some android config. I saw an article about this:

/data/data/com.android.providers.settings/databases/settings.db

but that file doesn't exist so I can't check some individual settings that helped others.

I checked overlay windows and that doesn't appear to be an issue either.

Ironcically, you don't even need to root this thing as when you turn on developer options and USB debugging you can run adb as root. Wish I had know that a long time ago. I did install Magisk on the 'good' unit, but since you can get root from adb, not sure there's much purpose.

onward we go

what would cause some screen resolution (which appears fine) , touch areas, Android main buttons (screen only - home/back/open apps) to not respond to events? it doesn't even register as a screen touch..
[Android Q&A, Help & Troubleshooting] mini4mw:
going through logcat for a boot on the good and bad system, i did find the resolution is reversed. doesn't seem right, but can't say thats the issue. trying to find the display_settings.xml in the /data dir

Bad

12-31 16:06:48.257 777 818 I DisplayManagerService: Display device added: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 1024 x 600, modeId 1, defaultModeId 1, supportedModes [{id=1, width=1024, height=600, fps=60.0}], colorTransformId 1, defaultColorTransformId 1, supportedColorTransforms [{id=1, colorTransform=0}], density 160, 159.568 x 160.421 dpi, appVsyncOff 0, presDeadline 17666667, touch INTERNAL, rotation 0, type BUILT_IN, state UNKNOWN, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}

Good

06-19 19:11:54.746 784 824 I DisplayManagerService: Display device added: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 600 x 1024, modeId 1, defaultModeId 1, supportedModes [{id=1, width=600, height=1024, fps=60.0}], colorTransformId 1, defaultColorTransformId 1, supportedColorTransforms [{id=1, colorTransform=0}], density 160, 171.235 x 171.115 dpi, appVsyncOff 0, presDeadline 17666667, touch INTERNAL, rotation 0, type BUILT_IN, state UNKNOWN, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
[Android Q&A, Help & Troubleshooting] mini4mw:
root@chiron:/ # wm size

wm size

Physical size: 1024x600

PS C:\> adb shell wm size

Physical size: 600x1024

this is later in the logs

No existing display settings /data/system/display_settings.xml; starting empty

I did look for this file on the good and bad system and neither has it. Not sure how the physical size is getting improperly set. Rotation does not work on the bad one either, when moving around by hand.
[Android Q&A, Help & Troubleshooting] mini4mw:
ok, so the size is not it. I can open settings from adb and the size is right there. No rotation is turn on as well. Keep on trucking.
[Android Q&A, Help & Troubleshooting] mini4mw:
aight, so this has long since gone off topic of just trying to get this stupid tablet to work...

took a break and messing around with it again and I think i found the issue with the touch screen for the 3rd, 4th, 10th or whatever time. This time its firmware. Looking at the good tablet I have a different firmware version than the 'bad' tablet. The vendor is 'KD' on both. FW on good tablet is 0x0 1.0.2. It also lists an 'Advanced Mode'. On the partial touch screen working tablet the firmware is 0x6.0x1.0x9 and no advanced mode. Now to try and find firmware to install.

probably asking myself, but can anyone point me in the right direction, perhaps pulling from the good tablet?
[Xiaomi Mi A2 Lite Questions & Answers] Mapuku:
My signal is always fluctuating. I use sim1 and only 1 sim card. Why is that. And signal shows in the settings as -100 dbm which is not very good. below -90 is the good signal.

And my wi-fi icon is always showing the bars for connection, then losing the bars (arrows), than coming again, so the icon dances on the screen which is frustrating. Is it supposed to be like that? Is it constantly losing and regaining signal?
[General Questions and Answers] Peelp5090:
Let me know your thoughts down below 🙂
[General Questions and Answers] mvikrant97:
Try 3u Tools which may have the blob for older version which would show you the version number you can flash.
[General Questions and Answers] Peelp5090:
I did that i got SHSH error
[General Questions and Answers] Agret:
Yes, if you have a device older than iPhone X / iPad Pro 1st generation you can flash most of them with lower unsigned firmware with no blobs.

For most firmware you will need to use checkm8 bootloader exploit, this is usually done via checkra1n. Unfortunately because the firmware is unsigned if your iphone/ipad turns off or reboots you need to reconnect it to a PC with checkra1n to boot it up again as they need to perform the exploit each bootup.

For old devices there is often a firmware that is 'intermediate' when upgrading from a brand new device, like you can't go direct from iOS 5 to iOS 9 you would have to go iOS 5 to iOS 7 to iOS 9 so you can get third party tools that allow to downgrade that device from iOS 9 to iOS 7 since iOS 7 is always signed for these devices.

One that comes to mind for that is the iPad Air 2nd Gen you can downgrade without blobs to the old version that runs 32 bit apps, if you update it to the latest iOS supported it only runs 64 bit apps. They are a good choice to buy used since whatever firmware it comes with you can downgrade to old version + jailbreak it and run any game you want on it, great retro iOS gaming device.
[General Questions and Answers] Peelp5090:
The device I was using were the iPad mini 2 and iPhone 6
[General Questions and Answers] Agret:
iPad mini 2 can be downgraded to iOS 10.3.3 using an Intel based Mac and after the downgrade is completely untethered.

GitHub - MatthewPierson/1033-OTA-Downgrader: First ever tool to downgrade ANY iPhone 5s, ANY iPad Air and (almost any) iPad Mini 2 to 10.3.3 with OTA blobs + checkm8!

First ever tool to downgrade ANY iPhone 5s, ANY iPad Air and (almost any) iPad Mini 2 to 10.3.3 with OTA blobs + checkm8! - MatthewPierson/1033-OTA-Downgrader

github.com

GitHub - MatthewPierson/Vieux: Vieux - A tool for 32/64 Bit iOS downgrades using OTA Blobs

Vieux - A tool for 32/64 Bit iOS downgrades using OTA Blobs - MatthewPierson/Vieux

github.com

checkra1n is supported on iPhone 6 but once again you will need access to an Intel Mac or you can download bootable usb iso for PCs to load it onto your phone but this is less than convenient having to reboot your PC off a USB stick every time you want to reboot your phone.
[General Questions and Answers] Peelp5090:
Thanks!
[OnePlus Nord 3 / Ace 2V] maxsteelvishak:
Luckily the Kernel of Oneplus Nord 3 is compatible with Kernelsu, however after flashing the right kernel image, my phone goes into boot loop. I have also disabled vbmeta verfication (fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img).

I dont know where I'm going wrong.

Eventually I can boot again by flashing the stock boot, but unable to get KSU boot image to work
[OnePlus Nord 3 / Ace 2V] well83:
Hi. Did you resolve your problem, if yes could you post solution please.
[OnePlus Nord 3 / Ace 2V] maxsteelvishak:
Hi , I resolved it, if you need to root oneplus nord 3 5G using KSU, please DM me, the solution may not work for oyu
[OnePlus Nord 3 / Ace 2V] maxsteelvishak:
Hi , I resolved it, if you need to root oneplus nord 3 5G using KSU, please DM me, the solution may not work for you
[OnePlus Nord 3 / Ace 2V] KP6_Xda:
Please share solution, thnx
[OnePlus Nord 3 / Ace 2V] pawelmiernik:
Don't know what version kernel you guys have, but in the op it says it's compatible. The easiest solution is to be rooted with magisk, have the stock image stored locally, and have kernel flasher installed. Download the kernelsu version compatible with your kernel in the form of the ak3 zip file. Use kernel flasher to back up your current boot, then flash your stock boot image .img file, use kernel flasher again to flash the anykernel3 ak3 file you downloaded to patch the stock image, use kernel flasher to back up your now patched boot image. Transfer this backed up image file to your PC, and use kernel flasher to restore the backed up boot image from the very beginning that is magisk patched. Your phone should now be back to where you were before you started. Install kernelsu APK and if you open it, it should say not installed. Now you reboot to bootloader and use fastboot boot <the boot image you downloaded from your phone.img> and if your phone boots successfully and when you open kernelsu app and it says working, you have successfully patched your stock kernel with ksu. Now all you have to do is boot back to bootloader and use fastboot to permanently flash the image to your phone. If your phone doesn't boot with the fastboot boot command then you messed up patching your stock image or you used the wrong stock image for your os, or you used the wrong version of ksu ak3 file, but it's okay because you didn't actually flash the boot image you just tried to boot it temporarily, you can restart your phone to try again. And if you can't boot your phone at all, then that is a sign that you shouldn't try to flash anything on your phone if you don't understand how and let it be the way it is, the same applies if all of what I typed above sounds too confusing.
[OnePlus Nord 3 / Ace 2V] 4llurb4s3:
Please share solution, thnx
[Galaxy S6 / S6 Edge Unified Development] uomotesla:
Hi ronnz, thanks a lot for this development!!! It was great to install it on my S6 G920F and honestly is running really smooth!!!

I am reporting just a small annoying thing about wifi: if I try to connect to password protected networks, even if I insert the right password it will never connect to the network, saying that the password is not right (tested with 1 device over 2 networks). WiFi is correctly connecting and working over unsecure (no password protected) wifi network. Can you maybe have a look, maybe is something easy to solve but with huge impact!!

Thank you so much again for your effort, it is HUGELY appreciated!!!
[Galaxy S6 / S6 Edge Unified Development] ronnz98:
I did not yet have that feedback. Wifi should work- do you maybe use WPA3 only?
[Galaxy S6 / S6 Edge Unified Development] yotag.yg:
@uomotesla @ronnz98

tested & working

WIFI with (WPA2-PSK AES) password is OK.

voice Call is OK.

cannot capture video when was on first boot (a toast writes 'failed to write file'), after 2nd boot is OK.

'USB storage' is hidden under > System > Advanced > Developer Options > 'Default USB configuration' and was disabled by default.

tested with NetGuard (a no root firewall, VPN technic) is OK.

nevertheless - cannot connect to WIFI when has hidden SSID, even I add the needed under WIFI > add network, seems that never resolves the WIFI network...

[ [ great experience ] ] - finally a ROM can be used...

[edit]

@ronnz98 - seems after use :

the developer options - disappear and user has to press again 9 times to 'about phone' to reappear

seems when developer options disappear losing also any configuration made on this activity (6 page switches)

dumb and solved - seems that this happened because I turn OFF the developer options switch on TOP of activity. But at least on previous androidOS versions did not act like that... @ronnz98
[Galaxy S6 / S6 Edge Unified Development] yotag.yg:
@ronnz98 - should be a problem with the activities garbage collector..

There is an issue with the battery, for example today ~12pm full charged on 100% (not fast charge)...

at 7pm was at 89% (without use the phone)...

No applications open when use the default task manager. On some moment tried to plug the usb, nah, impossible, the scenario always was on tray to appear the usb1 (winxp) symbol.. 5-6 tries / change port nothing changed..

-stopped trying-

after hours, saw the mobile memory on developer options 2.7gb used out of 2.8gb, I restarted the phone, success USB connection, and added an Appkiller application, show me that there were 14 (third party) applications running on background (all installed by me the previous day) !!
[Galaxy S6 / S6 Edge Unified Development] yotag.yg:
USB connectivity problem continuous

:(
[Galaxy S6 / S6 Edge Unified Development] ronnz98:
Update for /e/OS-T 1.21:

Galaxy S6 (SM-G920F) (zerofltexx):

e-1.21-t-20240330-UNOFFICIAL-zerofltexx.zip

https://sourceforge.net/projects/eo...t-20240330-UNOFFICIAL-zerofltexx.zip/download

Galaxy S6 Edge (SM-G925F) (zeroltexx):

e-1.21-t-20240330-UNOFFICIAL-zeroltexx.zip

https://sourceforge.net/projects/eo...-t-20240330-UNOFFICIAL-zeroltexx.zip/download
[Galaxy S6 / S6 Edge Unified Development] ostrikerX:
Hello, will this rom work on the galaxy note 5 (N920C)? thanks.
[Galaxy S6 / S6 Edge Unified Development] ronnz98:
No, but you might try this:

[UNOFFICAL BUILDS] Samsung Galaxy Note 5 series for /e/OS-Q

Samsung Galaxy Note 5 for /e/OS-Q 1.17 Note 5 International: e-1.17-q-20231205-UNOFFICIAL-noblelte.zip https://www.androidfilehost.com/?fid=16385555061192798954 Note 5 North America: e-1.17-q-20231205-UNOFFICIAL-nobleltetmo.zip https://www.androidfilehost.com/?fid=16385555061192798952...

community.e.foundation
[Galaxy S6 / S6 Edge Unified Development] ronnz98:
For Galaxy S6 (SM-G920F) (zerofltexx):

e-2.0-r-20240508-UNOFFICIAL-zerofltexx.zip

https://sourceforge.net/projects/eo...r-20240508-UNOFFICIAL-zerofltexx.zip/download

For Galaxy S6 Edge (SM-G925F) (zeroltexx):

e-2.0-r-20240508-UNOFFICIAL-zeroltexx.zip

https://sourceforge.net/projects/eo...-r-20240508-UNOFFICIAL-zeroltexx.zip/download
[Galaxy S6 / S6 Edge Unified Development] ronnz98:
Updates for /e/OS-R 1.21:

For Galaxy S6 (SM-G920F) (zerofltexx):

https://sourceforge.net/projects/eosbuildsronnz98/files/SamsungSmartphones/e-2.1-r-20240605-UNOFFICIAL-zerofltexx.zip/download

For Galaxy S6 Edge (SM-G925F) (zeroltexx):

https://sourceforge.net/projects/eosbuildsronnz98/files/SamsungSmartphones/e-2.1-r-20240605-UNOFFICIAL-zeroltexx.zip/download
[Galaxy S6 / S6 Edge Unified Development] ronnz98:
Final Updates for /e/OS-R 2.2:

For Galaxy S6 (SM-G920F) (zerofltexx):

e-2.2-r-20240719-UNOFFICIAL-zerofltexx.zip

https://sourceforge.net/projects/eo...r-20240719-UNOFFICIAL-zerofltexx.zip/download

For Galaxy S6 Edge (SM-G925F) (zeroltexx):

e-2.2-r-20240719-UNOFFICIAL-zeroltexx.zip

https://sourceforge.net/projects/eo...-r-20240719-UNOFFICIAL-zeroltexx.zip/download