yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] arjaylzo:
#Fastboot getvar all

(bootloader) serialno: 96791262

(bootloader) board: Insyde Cherry Trail FFD CherryTrail

(bootloader) device-state: unlocked

(bootloader) boot-state: ORANGE

(bootloader) firmware: INSYDE Corp. V1.08

(bootloader) product-name: Cherry Trail Tablet

(bootloader) secureboot: yes

(bootloader) off-mode-charge: 1

(bootloader) unlocked: yes

(bootloader) secure: no

(bootloader) partition-type:factory: ext4

(bootloader) partition-size:factory: 0x0000000000A00000

(bootloader) partition-type:config: ext4

(bootloader) partition-size:config: 0x0000000000800000

(bootloader) partition-type:persistent: ext4

(bootloader) partition-size:persistent: 0x0000000000100000

(bootloader) partition-type:userdata: ext4

(bootloader) partition-size:userdata: 0x00000005D4E00000

(bootloader) partition-type:data: ext4

(bootloader) partition-size:data: 0x00000005D4E00000

(bootloader) partition-type:DE2: none

(bootloader) partition-size:DE2: 0x0000000000A00000

(bootloader) partition-type:cache: ext4

(bootloader) partition-size:cache: 0x000000001F400000

(bootloader) partition-type:system: ext4

(bootloader) partition-size:system: 0x0000000140000000

(bootloader) partition-type:metadata: none

(bootloader) partition-size:metadata: 0x0000000001000000

(bootloader) partition-type:misc: none

(bootloader) partition-size:misc: 0x0000000000100000

(bootloader) partition-type:DE1: none

(bootloader) partition-size:DE1: 0x0000000000A00000

(bootloader) partition-type:recovery: none

(bootloader) partition-size:recovery: 0x0000000001E00000

(bootloader) partition-type:boot: none

(bootloader) partition-size:boot: 0x0000000001E00000

(bootloader) partition-type:bootloader2: none

(bootloader) partition-size:bootloader2: 0x0000000006400000

(bootloader) partition-type:bootloader: vfat

(bootloader) partition-size:bootloader: 0x0000000006400000

(bootloader) max-download-size: 0x0000000018000000

(bootloader) battery-voltage: 4086mV

(bootloader) version-bootloader: kernelflinger-02.11-10e7456

(bootloader) product: rolex

all:

finished. total time: 0.077s
[Android Q&A, Help & Troubleshooting] arjaylzo:
So I finally am able to flash an Unsecured boot.img, am able to exexute "adb root"

With my linux, Konsole indicates

"restarting as Root"

But I guess the tablet still setup a persistent reset for unroot ADB, but I am able to obtain these info from ADB as root (Kinda)

I will now commence Dumping these partitions and guess which one is Recovery

If I am able to dump these as IMG's, then I would unpack to check also will again RUN Fastboot boot Recovery.img

To check if it does gets me into STOCK recovery, this way We will now have a STOCK-Recovery image!
[Android Q&A, Help & Troubleshooting] arjaylzo:
Dmesg from ADB with Stock ROM
[Android Q&A, Help & Troubleshooting] arjaylzo:
Acer Predator 8 Gt-810 PARTITION INFORMATION
[Android Q&A, Help & Troubleshooting] livedten:
pleas backup system\etc download
[Android Q&A, Help & Troubleshooting] Ruben Craveiro:
deleted

---------- Post added at 02:20 PM ---------- Previous post was at 01:54 PM ----------

Downloaded TWRP.img i replaced with stock kernel, changed modules, fstab, and got touchscreen working and all partitions are working, no bugs that i found, i also backed up stock recovery since i booted twrp not flashed, im gonna make the stock rom flashable for twrp now, then an unbloated rom, we now need a development page for our device so it doesnt get messy, ill add twrp link after im 100% its working
[Android Q&A, Help & Troubleshooting] arjaylzo:
I've Finally been able to install my Ported TWRP with Full Functionality (including the EMU.ko file and Touch screen)

Also, through TWRP, I am able to flash the Stock Image file for the tablet.

Here is my Screen -Record https[:]//youtu.be/UpRFqTejF9U

Sorry that I am unable to upload the TWRP-Ported.img file, does not allow me here and my bandwidth is quite limitted.

My next plan is booting a Full GNU Linux, wish me luck.
[Android Q&A, Help & Troubleshooting] Ruben Craveiro:
For that im certain that you need to access the UEFI to disable secure boot, but first you need to make a backup of the EMMC partitions in order to restore back to android, theres also a few things that can be done to easily dual boot this device with another OS like Ubuntu, accessing UEFI with keyboard and keypressing is impossible since by default the option to enable keyboard is disabled, a way of getting to UEFI is to flash the stock rom on twrp (with edited script to flash and fail on uefi update), and when it fails and goes to shell mode you connect keyboard simply type exit and it shows secure boot option, and option to enter UEFI, from there you can boot whatever you want.. I could try to get reefind (a boot manager allows to dualboot in case u didnt know) but i need root.. i made the unsecboot myself but can never seem to be able to get root working without making the rom unbootable.. can you tell me how you did it?
[Android Q&A, Help & Troubleshooting] arjaylzo:
I forgot to mention, I got into the UEFI by deliberately erasing bootloader partition, I was confident that I'de still be able to boot the device via DNX mode and into it's OEM fasboot mode. I got into the shell, typed exit. It then shows me the Setup Utility and Option to boot from device or option to boot from File.
[Android Q&A, Help & Troubleshooting] Ruben Craveiro:
it really seems like your just ignoring the replies im giving, please take a bit of time and read replies ive sending, ive ported the TWRP 3.0.2, so its not using the older one, 2.8.7, and i was also able to boot into uefi, i could also try to get something another bootloader very easily to be able to multiboot different OS'es, since my other tablet uses an intel cpu and process is the same, all i need now, is to know how did you root this device? whever i try to root this device it allways falls into a bootloop or if i manualky push files it constantly says binaries need an update and it fails everytime to update.. just tell me how you did it..

---------- Post added at 12:20 AM ---------- Previous post was at 12:14 AM ----------

I think we need to somehow work togueter, the things you have been making its things ive done very easily, the only thing i wasnt able to do is root the device, other than that, i was able to boot TWRP 3.0.2, the so called unsec boot and few other things, i have an idea that is very safe that will allow to load a bootloader that gives you the power to choose if you want to boot with flash drive, android, or an .img stored on the tablet in order to dualboot android/linux/windows.. But what we dont need is youtube videos just showing you did stuff like that, its unnecessary, and you dont even give any kind of tutorial on how you did it.. if your not going to share anything and keep making useless youtube videos, just tell me how you rooted the device without it getting into a bootloop, and ill do the rest by my own.
[Android Q&A, Help & Troubleshooting] arjaylzo:
Apologies for the lack of tutorial. Honestly I was teasing you, though I might have teased you too much. I am able to revive my tablet and eventually smoked the Display Driver chip. Tablet still boots into Grub (the last bootloader I had to get into the UEFI) and eventually slipped the Aluminum casing and poof, smoke came out of the chip. Moreover, here is how I did it. I will most likely unable to provide you the commandline from Fastboot at the moment as I am using a Diff PC to reply to you.

Key is, I did had a bootloop whenever I flash the ported TWRP recovery if I flash it as .img.

Instead, what I did is simply unpack the Teclast TWRP recovery using umkbootimg. So that gives me three things:

1 initramfs.cpio file

1 zImage file

and the commandline to repack the img.

"But I did not actually repack back to IMG"

I then replace the zImage file from the GT810, this makes the Touchscreen work

So, the secret was:

- that should enable you to boot and test the new Recovery, Touch and all the rest should work. also check TWRP log screen for errors. If no error, then you can flash those "two files"

While you have the initramfs, modify the default.prop according to the GT-810's build prop. Especially the part where SKU and all the rest of values are indicated on the GT-810, there is no need to edit those init-RC files. Keep them as is.

Going back to the Flashing. So you have the Following:

1: GT810-initrd file

2: modified initramfs (which has the Gt-810 bulidprop contents pasted into the default.prop)

3: Commandline to repack the Teclast TWRP recovery.

Flashing part. Bear with me as I do not have my PC where I worked, but again, do not flash your TWRP recov as IMG. Rather flash it as RAW, and make sure to flash unsecboot first.

Here are my Root-files:

Make sure to unlock your bootloader. Flash the unsecboot.img first

The Fun part

Reboot to Recovery (Power + Vol-UP, its the button closest to the power button)

flash the SU.zip file above.

there your go :)

I am out to buy another Predator tablet at the moment. Mine is half-gone. Later I'll post more details.
[Android Q&A, Help & Troubleshooting] Ruben Craveiro:
Alright, thus thing is a bit messed up. I send comments to you for another thread and then u send to this one its a bit of a mess, but anyway i was hoping that after you buy your tablet again, that you could try this TWRP and maybe try to fix a bug i couldnt fix? (backup folder name keeps changing), its a more updated version of TWRP, it does backup and install stock rom, but backups after being made and if you reboot twrp, twrp changes the folder name (/sdcard/TWRP/BACKUPS/18373829_thesechangeeveryreboot)) which makes it having the problem of transfering the backup to the new folder.. Link: http://xdaforums.com/android/development/acer-predator-8-twrp-3-0-2-t3500801/page1 also i flashed everything with fastboot, and temporarily booted to twrp and made a backup of stock recovery.. also im trying to get refind to work, if we get this it should be very easy to put anything we want in here.. i tried once but forgot to disable secure boot and uefi failed to load refind_x64.efi ill try again this afternoon after i get back from school..
[Android Q&A, Help & Troubleshooting] arjaylzo:
refind

I tried refind as well, tried three of these. The downloadable zip, ISO and I recall and the standalone efi file. With the secure_boot disabled, I only got into the fallback Grub Commandline and refind fails to identify bootable partitions including the EMMC:bootloader, SDCARD (Yes I have flagged by SD as Bootable, even has it's 100mb efi partition itself) and bootable USB via OTG. Couldn't make it work. While using Grub.efi from LInux Iso's works flawlessly. I made a couple of dumps. One of which was SMBIOS and devicetree, well not Android related but handy as I unravel the devices through it's core.

The store I went to no longer has stocks of the tablet at my price-range. Other do have but were 3x the Selling price. So not today, I guess.

Regarding the TWRP latest version you are working onto. I am not sure if it's necessary to have it, the older version worked for me flawlessly, primarily rooting the device, making backup and Instant ADB connection. Oh! Sideload doesn't work :) but not that much of a drawback.

The later part, the Tablet gets rooted using the old TWRP and I personally can't check as to why the folder changes. I recall, on the old version: the backup you made would create SKU+SystemTimeAndDate as the folder's filename. Thus you'd be able to distinguish which set of backup worked.

BE CAREFULL not to flash the Stock AVOLO firmware very often. Which was one of my perv. I had the instance where the Charging IC and UEFI/Bios chip gets out of sync and thereby the Battery gauge gets wrong Calibration.

I come to Discover how to Reset the UEFI chip as well as the EMMC chip in cases where The USB port gets disabled if you ever decide to tinker the USB configuration and UEFI. Or should there be a need to do so, such as in my case, the unit bootloops in 2sec as soon as the Acer logo and backlight comes on. Turns out that the Bootloader and UEFI update got corrupted. Worse part is, DNX also no longer works.

PLUS, I recommend not to CLEAR the UEFI Security Footer inside the UEFI, this part is Where Acer embedded their RSA security description. This part cannot be recovered and undone. If so, You will have a BootFlag or Notice to Press Vol+ twice whenever the unit is turned on. Well, that is if you go through the route of having android on this device.

But again, given that this is _x64 based hardware, we certainly can boot other os's, part missing on my end is how to go through these OS's installation without the USB3.0 deactivated when WinPe(windows) or InitRamFs(Linux) is executed.

Lastly, I have uploaded and provided a link to DL the Stock Recovery which is 30MB+ using DD from ADB. These Img's are now flashable IMG's.
[Android Q&A, Help & Troubleshooting] Ruben Craveiro:
my twrp does all that too.. one of the only problems is that it backups, but if you reboot the supposed serialnumber(deviceid of /TWRP/BACKUPS/929293/ changes every reboot, if it wasnt for that i guess it would be better than the old one, and supports much better themes.. Also ive tried unpacking system from stock image i can never make it boot.. it never boots.. what could it be?
[Android Auto General] jlccyoung:
This one is driving me nuts. The advertising for this unit shows an icon page. Messages, phone etc. That only seems to be for Carplay with the iphone. When I connect to the unit with the usb, i can't look at or receive any texts that are on my phone at the time I connect. There is no home page with the icons that show my phone aps. It won't even show the apps it's supposed to work with on Android. It seems that you can with the Apple aps. Am I doing anything wrong? It looks like Android auto was an after thought to sell more of these Kenwood units. I'm having issues navigating thru this unit. I use Android music but can't get this thing to default to my playlists. Do I have to buy an iphone just to use the potential of this $1700.00 mistake?
[Android Auto General] aplusmiami:
Wow now i am really glad i passed on this. After being burnt with 990hd i was really down on Kenwood. Went with a joying Chinese android unit and LOVE IT
[Android Auto General] gshadow325:
First, the unit only retails at $1299.

Second, try running a stock rom then complain about it. Its the custom rom that breaks Andoid auto and bluetooth.

Third, apps NOT installed from play store will not show up on the andoid auto screen.

Learn how to use the info from this page to your advantage. when you follow it, you will be able to get spotify, pandora etc on your AA screen

https://pixplicity.com/setting-install-vendor-debug-app/

990hd was such a turd. the new 893s is running on with a dual core processor, much faster and now is linux based vs before was android 2.3. it will run circles around your andoid unit from china. I have had them all since the 990/991/992/ DNN series, DNX 690/691/692 and dnx890/891/892 and now my current 893s. 893s is such a great unit compared to the rest of them out there
[Android Auto General] leonkernan:
I wouldn't waste too much time, he's only made 2 posts and they're both to complain about it because he didn't do his research first.
[Android Auto General] doitright:
Yours is not the only dollar in the world.

$1299 US --> $1740 CAD / $1790 AUD

Eh...

1) Android *is* Linux.

2) Dual core ARM... REALLY??? You think a DUAL CORE ARM is going to "run circles" around a QUAD CORE INTEL? While it is certainly an improvement over their previous SINGLE core TURDSLUGS, twice nothing is still nothing.

3) You've HAD THEM ALL.... means that ALL of them have been inadequate. LOL, you're doing a bad job of marketing for them.

Also from Kenwood literature... "Dual Core Processor w/ Faster Start-Up Time: The Kenwood navigation receiver utilizes a Linux based system and dual core processor for faster operating speeds and enhanced stability. The unit has start-up time of approximately 17.7 seconds from OFF to the last source selected or navigation map screen."

*** YOU SERIOUSLY THINK THAT WAITING NEARLY 20 SECONDS TWIDDLING YOUR THUMBS IS FAST?

I'll take my Joying **ZERO** seconds startup ANY DAY over that. Yep, I sit in my car, turn the key, wait precisely ZERO seconds and have Google Maps up, tap in the input field and START TYPING AN ADDRESS. By the time you finish waiting, I've already backed out my driveway and am on my way up the street!

I've had kenwood too. BOY was it ever nice to get that junk out of my car.

Oh one more thing, since you are very aggressively attacking "your andoid unit from china", your kenwood is made in MALAYSIA. Yeah, that is SO MUCH BETTER than 'Made in China'. LOL
[Android Auto General] gshadow325:
It's the only dollar that matters.

Everyone else compares theirs to this one.

Good luck with your China joy.
[Android Auto General] doitright:
You speak like a typical american -- thinking that you are the center of the universe.

NOBODY cares about US dollars any more.

People talk about THEIR OWN dollars.

Luck? Not needed.

I think I know what your problem is: you spent sooooo much money on those pieces of junk that you're trying to tell yourself that they're somehow better than something you can buy for 1/3rd of the price. Its called SHAME and EMBARRASSMENT. I pity you.

But like I said... I've already owned kenwood products, so there is NOTHING you can do to convince me about how good you want me to believe that it is.... I KNOW BETTER.
[Android Auto General] gshadow325:
Hey have a good life. Best of luck.
[Android Auto General] doitright:
Yep, shame and embarrassment.
[Android Auto General] CadillacMike:
while I dont agree with the arguing, I would have to say the new Joyings are pretty fast. I had the older MTCD with 1GB of RAM and it was brutally slow.

However the new 2GB of RAM and Intel processor units are smooth, pretty quick, and I would say hard to beat.

Edit to add- I don't want to derail this thread, I was looking at the DNX893S pretty heavy. But it is crazy expensive, however it does look cool
[Android Auto General] Karchut78:
You can't get the same sound out of China no name brands. There good for the money, but with all audio out , there is a big price increases to get the best sound. If you just want options, go with the cheaper one's . You can spend $ 10 000 to $ 15 000 on speakers if you want the best, but $ 500 are good to
[Android Auto General] aplusmiami:
Yes but for the money you save you buy amps and kick [MENTION=237736]SS[/MENTION] speakers and you are there. Kenwood is just awful. Bad support and way behind the times.
[Note 7 Questions & Answers] millicent:
Speaking for myself I've always been kinda aware of the failure potential of these batteries. For instance, I tend to not leave the phone unattended during charging and also use such tasker profiles as to shutdown when charge below 5% or alert when charging above 95%. These latter measures and others are mostly to help with battery longevity as well as or rather my ocdness on this subject.

My only gripe is that I never succeeded in instilling the same 'respect' for battery in my wife..;) Pre or even post-note she always forgets her tablet or her phone plugged in the charger, even when no one's at home, sometimes for days!

But this recent note7 'mishap' let me tell you, made me even more wary of the destructive potential of the batteries in our phones. Especially since most of my latest snapdragon devices (m7, z5) get very warm while performing various mundane tasks (syncing via wifi/lte, camera, games rendering etc), much warmer then the defunct note.

Did this event affect the way you use your mobile devices and how? Is there any particular strategy you use with this respect? Or do you rather think that the failure rate being so low it's rather silly to worry about it?
[Note 7 Questions & Answers] br0adband:
Nope, it hasn't made me change anything so far. I don't believe the issue with the Note 7 is directly a result of the battery since Samsung had two manufacturers make batteries and in both instances Note 7 devices with either battery still failed.

As long as the device is working properly meaning there's no defect that I am aware of (as in no global recall in effect, etc) in any part of the power or charging systems then I tend to leave my devices plugged in until they charge to 100% status then I'll usually leave them connected to the charger for up to 30 minutes past that point then disconnect. With the GS7A I have, I only charge it once every 2.5-3 days typically and that's from 5-10% back to 100% using a Samsung 2A charger - I don't use the factory fast charger and I don't use fast charging because I believe that ends up shortening the potential lifespan of the battery cell itself.

I did not say that's a fact for everyone to live by or accept as the gospel truth, I said for myself personally I believe that fast charging shortens the lifespan of the battery cell itself.

For the record I've owned several hundred devices over the decades, some with Ni-Cad batteries, most with Li-Ion over the past decade, and a few with Li-Po technolology and I only had one instance of a battery having a problem (not a failure). It was a knockoff cheap Chinese clone battery for my Galaxy S4 Active several years ago and it bloated up one afternoon - thankfully that GS4A had a removable back cover and I caught the swelling up very fast because as soon as it started to bloat up the back cover literally popped off about 4 inches above my desk and landed on my keyboard. I of course took the battery out immediately and put it in a small ceramic box my Wife had laying around, nothing else happened and I ended up taking it to a local battery store here in Las Vegas and turning it in for safe destruction.

See, there really is a good reason to have removable batteries and removable back covers on some devices. ;)

As stated above, I don't believe the actual point of failure with the Note 7 is the battery directly - the burning up and explosions of the battery cells is the effect, not the cause. Something is happening to cause the battery (now two different ones, which most of us know about now) to fail.

Now it remains to be seen if the cause can be determined for the failures.
[Note 7 Questions & Answers] millicent:
There is one other, perhaps more placebo induced effect, routine I'd do every once in a while, related to battery calibration. So I'd let the battery go as low as can possibly go, or let it turn off by itself, charge at cold until 100% then power on while still plugged in and finally unplug when os fully booted up.

Is this still a proper thing to do or it rather stresses the battery uselessly?