yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Munk0:
I don't believe so at this stage. Things were starting to look promising, especially as of late with amrmo, but must have run into a snag.
[Miscellaneous Android Development] undrwater:
Looks like the snag is just time constraints. One of my devices went back to Asus for an RMA. Once it returns, [MENTION=7271345]amrmo[/MENTION], I can try things at my end. I've never used a hex editor, so some specificity would be useful there.
[Miscellaneous Android Development] SirVer:
I've done something similar for a Chinese intel tablet (that died a month ago), using dirtyCOW to root it, but it was very convoluted; selinux was set to Permissive, yet it behaved as if it was Enforcing - getting a root shell was simple enough, but the moment you tried to write something to a protected location, it would reboot and the writes would not have taken place. Something like this could very well happen even if [MENTION=7271345]amrmo[/MENTION] manages to edit the kernel bootstring to set selinux to permissive. The only reason I was able to succeed for that tablet was that I could unlock the bootloader - I used the shell to dd a boot image and modify the default.prop file within it to set all adb shells to root shells by default, which had the appropriate permissions to write a TWRP image to the recovery partition, reflash the boot image, write TWRP through the shell, and flashing the SuperSU zip from there.

In our case though, it's possible that the policy would allow us to write the su binary to the /system partition directly - I did not use that approach with my previous tablet, because I was not sure where to put all the various files within the zip. Or who knows, perhaps we could disable selinux entirely if we could get our hands on a boot image. Either way, if you're looking for a way to get a shell with enough privileges, this might be worth looking into - trying to modify the default.prop in the boot image.

Speaking of RAW files... I've only had this thing for a couple of weeks, and it came with Marshmallow, so I don't know what they're like - is it a proprietary archive format, or zip/tar/whatever with a different extension? If it's the latter, I may be willing to give it a shot myself once my Windows install is functional again - the former would probably require image reverse-engineering with binwalk or something, and my limited experience with that kind of thing has been disastrous.
[Miscellaneous Android Development] Bysler:
Received an update a couple days ago. I'm guessing is a security update which is always nice.
[Miscellaneous Android Development] prozack1983:
I'm pretty sure that by now they're just doing it to spite us. I have never regretted a purchase more than I have regretted buying this. Being the top of their line (at the time) I thought for sure they would encourage the dev. community. As there weren't very many alternatives for tablets with these kind of specs they could have had people swarming to this tablet if they'd only unlocked the bootloader.
[Miscellaneous Android Development] LukeHorizon:
Apperently, there is a new Update. No changelog yet though
[Miscellaneous Android Development] hkjxda:
For which one? Z580C or Z580CA?
[Miscellaneous Android Development] LukeHorizon:
CA

It's Version 5.6.0 on WW SKU, Security Patch of June.
[Miscellaneous Android Development] darkimage404:
Hi guys, I don't know if it's useful.

But I want to share how to flash any partition with fastboot after an error in asus flash tool

0. go in fastboot mode

1. open ASUS flash tool

2. select a fake zip file (any file)

3. select device and press START

(now we get an error)

from now fastboot flash command is unlocked for all partition (asus_internal_unlock 1)
[Miscellaneous Android Development] loner.:
Doesn't help much if the bootloader is locked.
[Miscellaneous Android Development] darkimage404:
we can flash droidboot from 6 to 5, install supersu with tethered CWM and reflash droidboot to 6.
[Miscellaneous Android Development] loner.:
It would be easier to adjust hammer Asus with requests for a key to unlock Bootloader, but nobody seems to want to do that.
[Miscellaneous Android Development] darkimage404:
I hard-bricked, black screen and usb device MOOREFIELD :( ,

now I need xfstk files for z580ca, only asus can help me.
[Miscellaneous Android Development] bert_747:
Fix your brick

Hey I made a post a while back fixing any bricking issues it will set the tablet back to its factory image, you'll have to go through the whole updating process again but it'll fix your tablet :)

Hope this helps.
[Miscellaneous Android Development] Chaser42:
Could the BlueBorne Bluetooth Vulnerability Allow Us to Root the Zenpad S 8.0?

You may have heard the buzz about the BlueBorne Bluetooth vulnerability that affects many platforms - Android in particular. Supposedly remote code execution is possible and I can't help but wonder if somebody with the technical ability could use that against the new Marshmallow update on the z580c/z580ca. Like the rest of the user community I am also very frustrated with ASUS for gimping this fine tablet and giving us no love regarding root. The BlueBorne exploits (there are several) can remotely take over an Android device from a distance without pairing and the user has no idea they have been hacked as it all happens silently in the background. I'm not advocating that anyone create a malicious hack tool that silently roots ZenPads from afar (although that does sort of amuse me considering how long we've been trying to make it happen). In fact, if you haven't heard about this thing yet, you should have Bluetooth turned off on Android, Apple IOS, Linux, and Windows until you get patched and can verify that you are no longer vulnerable. But if it is a vector that could be used to obtain root I would be happy to keep my two z580ca tabs unpatched while somebody cooks up a way to actually do it. Maybe this is another dead end, but I thought I'd throw that out to you guys as it could be worth a close look...
[Miscellaneous Android Development] prozack1983:
At this point I would give my first born child to whoever can come up with a viable unlock. Plus my undying admiration.?
[Miscellaneous Android Development] Munk0:
I think whoever solves it would be happy with the admiration part. :)
[Miscellaneous Android Development] mulperi:
Asus are loosers. They made a great tablet but did not understand the possibilities of unlock.
[Miscellaneous Android Development] Nfk:
My screen is cracked and touch panel. Can i factory reset and get any use without fixing screen.
[Miscellaneous Android Development] TheQuicksilver:
I'm right there with you. It's unfortunate more folks didn't pick up this tablet to drive interest in custom ROMs for it. It seems like there just isn't anyone with the skillset interested in tackling it harder. Damn shame. This tablet would be so good if it was just debloated.
[Miscellaneous Android Development] gerdawg:
intel bug

This uses intel based processors, correct? Maybe some brave engineer would be able to apply the exploit to our device ane fully unlock it's potential since this is a physical hardware problem and not OS specific?

https://www.intel.com/content/www/u...side-channel-analysis-and-intel-products.html
[Miscellaneous Android Development] shakalaca:
Hello gentlemen, I got good news and bad news ..

Good news is, the device is unlockable ;)

Bad news is, the device won't boot once unlocked, to boot up the device you have to relock it. :(

So here's the procedure if you're interested:

1. downgrade/upgrade device to v4.7.1.0

2. boot into cwm and execute the following command under adb shell:

echo -n -e "\x01" | dd of=/dev/block/by-name/persistent seek=1048575 bs=1 count=1

3. reboot and upgrade your device to v5.6.0

4. reboot device to bootloader and execute the following command:

fastboot flashing unlock

5. unlock bootloader by following the instructions on screen, note your data will be wiped.

To boot up the device you have to relock it by executing this command in bootloader mode :

fastboot flashing lock

So what's next ? any ideas ? :)
[Miscellaneous Android Development] shakalaca:
ah, bootable in v5.4.3 .. :D

let's start the party ... lol

---------- Post added at 01:38 AM ---------- Previous post was at 01:20 AM ----------

After unlock bootloader, Install MagiskManager, patch boot.img, flash it and boot .. boom !

Happy hacking ! :)

View attachment 4390180
[Miscellaneous Android Development] loner.:
So what's the best way to downgrade?
[Miscellaneous Android Development] prozack1983:
No ****ing way.
[Miscellaneous Android Development] shakalaca:
I use the ASUS Flashtool 1.0.0.45 from here : https://www.asus-zenfone.com/2017/03/download-asus-flashtool-10045-for-zenfone-3.html

And firmware here : https://drive.google.com/file/d/0Bw0MLebdBUaGQS1BOUNCYWZvcGM/view

Reboot ZenPad S to bootloader (important) and select the zipped raw file (yes, zip it !) remember to wipe data also
[Miscellaneous Android Development] loner.:
To be clear, are you saying use the raw file as is or convert to a zip?
[Miscellaneous Android Development] shakalaca:
Put the raw inside a zip file ;)

AFT only accept zip file and it will extract raw file out of the zip and flash into your device
[Miscellaneous Android Development] loner.:
Unlocking the bootloader did not work.
[Miscellaneous Android Development] shakalaca:
What's your step ? How do you know it's not working?
[Miscellaneous Android Development] loner.:
How do I know it's not working? Are you serious?

Step 2. Command line errored out.

---------- Post added at 11:12 AM ---------- Previous post was at 11:06 AM ----------

Fom what I remember it said something about not a "dd" command.
[Miscellaneous Android Development] shakalaca:
If you know something went wrong and you know only by providing the message that I can figure out how to help, then you know I'm not kidding.

I'm here to help, if you don't trust me then I won't waste my time here :(
[Miscellaneous Android Development] loner.:
Refresh this thread and see what I added.

---------- Post added at 11:38 AM ---------- Previous post was at 11:25 AM ----------

In the 2. Command line: /by-name/ is probably not correct.

I pasted the line exactly as you had it.
[Miscellaneous Android Development] brackenhill_mob:
Please don't upset [MENTION=567635]Loner[/MENTION] - he's one of the best people on this board. Very helpful and knowledgeable particularly as a TWRP hacker for various devices over many years ;)
[Miscellaneous Android Development] mad4some:
Many thanks for discovering and sharing [MENTION=1813976]shakalaca[/MENTION]!! I'm curious, did you try the other 2 (WW) updates in between 5.6.0 and 5.4.3??
[Miscellaneous Android Development] nonperson:
A somewhat misguided defence of strop. Loner, maybe not considering English likely isn’t Shakalaca’s native language, seemed in a huff because he didn’t get a happy result straight away. Yes, Shakalaca’s instructions are vague and difficult to follow, and they may well be in error – should it be dd if= not dd of=? – but often better to first clarify than immediately castigate.

Now for the good news, in addition to that reported by Shakalaca earlier. His method works. Not necessarily, though, as related in his post. While researching the above dd command, I stumbled on an automated process Shakalaca has compiled. It’s dead easy: connect to PC, click a .bat file and wait. Won’t link to it here, will let Shakalaca do that if he wants (and if he hasn’t been run off from the thread). Otherwise, seek and ye too shall easily find.

Granted such automated root procedures can be dodgy, but haven’t found anything suspicious, not yet. Meanwhile, I’ve a Z580CA rooted on 5.6.0.0 and running fine. Thanks very much Shakalaca.
[Miscellaneous Android Development] shakalaca:
I've build a package for the whole complicated process, so here you go:

https://mega.nz/#F!F1FlzAoY!u6zR1Y14xvqoSbz-YQGFrw

It will flash V4.x bootloader (ifwi) to ZenPad and set the unlock flag, then update the *correct* version of V5.x bootloader (ifwi) and do the unlock process. As far as I know the bootloader (ifwi) from V5.5.7 considers unlocked ZenPad as "device with corrupted software" and won't boot up. So we have to use the bootloader (ifwi) come from V5.4.3 (which is the same with V5.5.1)

If your ZenPad is on V4.x, or just want a rooted ZenPad with latest firmware:

1. grab the files under folder "For_ZenPad_with_V4.x"

2. extract the split archive 'FreeMyZenPad.7z'

3. put libwinpthread-1.dll, mke2fs.conf and mke2fs.exe into "files" folder

4. click "Root.bat" and minutes later your'll get a rooted ZenPad. Please install 'MagiskManager-v5.5.5.apk' manually since I left the system.img clean.

If your ZenPad is on V5.x and want to stay with current version

1. grab files under folder "For_ZenPad_with_V5.x"

2. extract FreeMyZenPadLite.zip

3. click Unlock.bat to unlock your ZenPad.

4. Grab the stock ROM with the same version in your ZenPad, extract boot.img and put into your device

5. Install 'MagiskManager-v5.5.5.apk' and then patch the boot.img

6. Fastboot flash boot patched_boot.img and you'll have root now.

Please let me know if you have problems :)

---------- Post added at 05:40 PM ---------- Previous post was at 05:38 PM ----------

I've found a method to boot 5.6.0, please see my above post :)

---------- Post added at 05:41 PM ---------- Previous post was at 05:40 PM ----------

Haha I'm not running off, just spent time building the automation process ;)
[Miscellaneous Android Development] loner.:
After step 4, I try to flash the boot.img that I extracted from the firmware and it fails because the boot.img is no signed. How do I extracted the boot.img as signed? Is there a Windows utility I can use?

---------- Post added at 09:47 AM ---------- Previous post was at 09:41 AM ----------

Failed (remote: check_sign_key fail : no allow update kernel)

---------- Post added at 10:25 AM ---------- Previous post was at 09:47 AM ----------

So close.

Looking for a signed www 5.6.0 boot.img
[Miscellaneous Android Development] mad4some:
When I extract the split archive (FreeMyZenPad.7z 001 thru 007) and then open the "files" folder, it appears that the 3 items that you say to put in there are already in there........so just skip this step, correct???

Also, when connecting to PC, just connected and recognized or ADB connected???

edit: Also, data never gets wiped during this process, correct???

edit: answers below!!
[Miscellaneous Android Development] mad4some:
*****SUCCESS!!!!!!!!!!!!!!!!!!*****

OK, I answered my own questions:

1. Your step 3 in the "on V4.x" instructions is not needed because the items are already there. :good:

2. Just standard PC connection, script does all the work (except input needed to allow unlock)

3. DUH!! after I added that question I realized that by including bootloader unlock.......ENTIRE DEVICE IS WIPED........so due diligence as far as backups to your PC.

[MENTION=1813976]shakalaca[/MENTION], thank you VERY much!!!!!
[Miscellaneous Android Development] shakalaca:
Thanks for your report, sorry for the misleading "missing file" description, a friend of mine told me there're missing files but due to bandwidth limitation I couldn't verify myself. I'll take down those redundant files :)
[Miscellaneous Android Development] loner.:
All done here if I can get a ww 5.6.0 signed boot img. Any help always appreciated.
[Miscellaneous Android Development] FirePsych:
So, to be clear, this is for any ZenPad S 8.0?

I have a model #P01M running Marshmallow 6.0

Thanks for all the hard work!
[Miscellaneous Android Development] mad4some:
[/COLOR]

[MENTION=1813976]shakalaca[/MENTION], you've takin this old tired thread in a completely new direction :good: This should become a new thread IMO!.......and many, many thanks to [MENTION=1534145]madsquabbles[/MENTION] for having root to begin with!! :cool:

---------- Post added at 09:36 PM ---------- Previous post was at 09:26 PM ----------

Mine is ASUS ZenPad S 8.0 (Z580CA) P01MA, but if your updates are the same as these then it should work.
[Miscellaneous Android Development] FirePsych:
What do you mean by"updates"?

This is a purely stock, never rooted or unlocked tablet.
[Miscellaneous Android Development] mad4some:
From here: https://www.asus.com/us/Tablets/ASUS_ZenPad_S_80_Z580CA/HelpDesk_BIOS/

if this is your model and your updates......it will work. BUT!.....only if you have WW firmware (I'm pretty sure)
[Miscellaneous Android Development] shakalaca:
Can you boot your device into bootloader mode and take a picture ? I want to know the version of IFWI and droidboot ..

The above message only shows up when device is locked, the boot.img from stock ROM is indeed signed one.

---------- Post added at 12:16 PM ---------- Previous post was at 12:12 PM ----------

As far as I know the two model have exact the same software in V5.4.3.0, so my unlock method should be working on Z580C too.
[Miscellaneous Android Development] loner.:
[MENTION=1813976]shakalaca[/MENTION] you said if any problems let you know. I have posted a few times about the need of a signed ww 5.6.0 boot.img or a way around it and I hear nothing and the tablet is not useable like it is.
[Miscellaneous Android Development] shakalaca:
Did you really see my above reply ?????

THE BOOT.IMG IN STOCK ROM IS SIGNED OR YOUR TABLET WON'T BOOT UP EVEN WITHOUT UNLOCK
[Miscellaneous Android Development] loner.:
No I did not see your reply, I think it was posted while I was typing mine.

I tried the 5x method and all it does after I successfully ran the bat file is boot to bootloader.View attachment 4393857
[Miscellaneous Android Development] loner.:
I may have found the problem. It seems I may have used the 4x method instead of the 5x method thus it flashed a 4x boot.img to a 5x system. [emoji37]
[Miscellaneous Android Development] loner.:
It appears that when I used the 5x root method it flashes the image 4.7.1.0, not good for my system since I have the 5.6.0 system. It made me think I used the wrong root procedure. But since I tried again using the 5x method I got the same result. It shouldn't flash the 4.7.1.0 like it does when I have a 5.6.0 image loaded.

---------- Post added at 01:48 PM ---------- Previous post was at 01:01 PM ----------

At this time the root does not work if you are on the latest 5.6.0 firmware.

Hopefully it can be corrected soon.
[Miscellaneous Android Development] S. Prime:
[MENTION=1813976]shakalaca[/MENTION] I have attached an image of the bootloader on my Z580CA. Do I need to change anything to root and which method do I use? Thanks for all of your work.View attachment 4394098
[Miscellaneous Android Development] mad4some:
From what I recall watching and reading the 4.x script do it's thing, it flashes part of 4.7.1.0 (bootloader only I believe) and then does the unlock. There is a point where you must select "unlock" with the power button and then there is a lengthy pause while it erases everything......after that it finishes by flashing the entire 5.6.0 system. Is this what you are seeing?? If not, seems like doing it again should overwrite and correct whatever state you are in now.
[Miscellaneous Android Development] loner.:
I did flash again on 5.6.0 it does not work but I am willing to try again as soon as I get time. Thanks
[Miscellaneous Android Development] shakalaca:
Not everyone knows how to use MagiskManager and flash the patched boot.img, so I reorganized the folder and from now on there's only one version, just unzip it and click root.bat :)

---------- Post added at 11:21 AM ---------- Previous post was at 11:01 AM ----------

The bootloader of 5.x supports "oem unlock" command for unlocking the bootloader but it won't let us do so because the "allow oem unlock" option is hidden from developer settings menu. We have to flash the bootloader back to 4.x and set the flag by using the Intel Bootloader Exploit.

Then we restore the 5.x bootloader and issue the command "fastboot flashing unlock", this time it won't block us because it received the message "user is able to unlock the bootloader now, show him the warning message and see if he really wants to do so". If you select "yes" by pressing volume up then power button, the bootloader will immediately wipe out your data and set the ZenPad in unlocked state.

I'm not sure why the program isn't working on your ZenPad, but I've unlock and re-lock the bootloader of my ZenPad with 5.6.0 about 50 times to build this program. I know it is difficult for general user like you to provide detailed information, but maybe you can take a video recording and let us figure out what the problem is with your ZenPad.

---------- Post added at 11:27 AM ---------- Previous post was at 11:21 AM ----------

No, there's no 4.x boot.img in this package, only bootloader. The boot_sign.img under "files/560" is actually boot image of 5.6.0.

If you're having 4.x bootloader with 5.x system.img in your ZenPad it won't boot. If this is the current state of your ZenPad, then please follow the instruction to restore 5.x bootloader:

fastboot getvar sofia_support
fastboot flash token 551/BOM_TOKEN_v89.0056_CRAK_DEV.bin
fastboot flash ifwi 551/IFWI_v89.0056_CRAK_DEV.bin
fastboot flash fastboot 560/droidboot_sign.img
fastboot flash splashscreen 560/splash.img
fastboot reboot-bootloader

and check if the "Image versoin" changed to 5.6.0.0
[Miscellaneous Android Development] loner.:
I don't think I would qualify for just "a general user" I have flashed images, roms, etc on 10 to 15 devices in the last eight or nine years. Usually whenever I unlocked a Asus bootloader, Asus provided a unlock key. They did this for the transformer tf700 and for the tf701 but not for the ZenPad S 8.0 or the ZenPad 3s 10 (z500m) I have now that are from Asus. I recently unlocked the (z500m), thanks to [MENTION=8132642]diplomatic[/MENTION]. I have used superuser, Magisk and others quite a few times. I use fastboot and adb to flash, push or sideload to recovery or boot partitions.

I may have been glitched though. We will see. You currently have 7 zips to download, which one do you want me to use?

---------- Post added at 09:56 PM ---------- Previous post was at 09:48 PM ----------

I have returned the device to firmware ww 5.6.0 and then tried your root again earlier today making sure that I ran your 5x version and again it put a 4.7.1 boot image on the device. Not my fault after all. So then I had to restore the device to the latest firmware 5.6.0 again. I have not tried your new version yet because I don't know which of the seven zips to use yet.

---------- Post added at 10:01 PM ---------- Previous post was at 09:56 PM ----------

Yes it did. The 5.x was used and did put a 4.7.1 boot image on the device twice. So it wasn't a mistake on my part, sorry.
[Miscellaneous Android Development] shakalaca:
If you mean "IMAGE VERSION" message on bootloader that is the version of bootloader not boot image, as I mentioned earlier, to give the bootloader the ability to unlock, we have to flash bootloader of 4.x (in my package it is 4.7.1)

There's no 4.7.1 boot image inside my package

There's no 4.7.1 boot image inside my package

There's no 4.7.1 boot image inside my package

If you found one, please tell me ... lol

The only part of 4.7.1 in my package is bootloader, not boot image, they are two different things

And back to your question, what I know is:

1. The bootloader of your ZenPad is not unlocked.

2. Your ZenPad stays with 4.7.1 bootloader at last and you can not flash 5.6.0 boot.img

3. You did it again and still get the same result

From my understanding if you're an experienced user you should at lease provide screenshot of command line output or error message on your computer during the unlocking process, or take a picture of your ZenPad when something went wrong in bootloader mode. I know my language sucks but please give me as much information as possible. As I suggested earlier, maybe you should take a video recording of your whole unlocking process.
[Miscellaneous Android Development] nonperson:
Don’t know if it’s relevant or will help anyone, but when I ran Shakalaca’s unlock/root tool I had just downgraded to 4.7.1.0 and then upgraded to 5.4.3.0. (WW). If script isn’t working for you maybe try on 5.4.3.0.