yashsingh1/xdaforums huggingface dataset:
[Android General] mygoldkenn:
Update

My device is rooted using ROOT GENIUS but still locked

Thanks for your info.

As another user said version 1.01.01 fails to update. This is indeed ridiculous. HP is well known of ignoring existing device owners.

Very frustrating.

I actually tried to provide the URL for that update but my user was not authorized. Need to post more. LoL
[Android General] roustabout:
IF you look upthread, there's a flashable 1.0.12 that I put together a few weeks ago. I used it as part of my reanimation of my slate last night. I don't know if that would work with the HP stock recovery, though - you may need to unlock your device so you can boot from the custom recovery to try a flash.

The HP site has a couple of other downloadable firmware files, too, the 05 and 09 variants

http://h10025.www1.hp.com/ewfrf/wc/...dlc=en&lc=en&os=4153&product=6608624&sw_lang=
[Android General] teskts:
Successfully updated slate 8 pro to kitkat4.4.2 ( update.zip 1.01.01 from HP website). Any root tools for 4.4.2?
[Android General] mygoldkenn:
update

Wonder how u install it?

I always get below error msg.

assert(getprop("ro.product.name") == "kadota_w_c");

The download was 587MB version 1.01.01

---------- Post added at 09:17 AM ---------- Previous post was at 09:11 AM ----------

My rom is running 1.00.12. It was update OTA last month
[Android General] roustabout:
Good deal, I'll take another run.

Was it simply a matter of bypassing the version check, leaving the rest of the file intact?

For rooting - check out Geohot's Towelroot. It's capable of rooting almost any pre-June 5 linux kernel, Android included.

Awesomely broad in its reach. And the build.prop for the 1.01.01 update references April 21, so it ought to be rootable.
[Android General] roustabout:
ro.product.name is in build.prop in /system

I've just edited mine from kadota_w_c to kadota_w_a to match what the sanity checks are looking for.

assert(getprop("ro.product.name") == "kadota_w_a");
[Android General] mygoldkenn:
update

I edited the file as u said. The error msg becomes..

E:failed to verify whole-file signature

E: signature verification failed

Installation aborted

T T
[Android General] roustabout:
Yep, I'm not there yet either. When I softbricked my device and put it back together again there were some interesting liberties that I had to take to get it booting again. (After hosing the partition table with the HP recovery, I wound up dd'ing the entire internal memory to a 32gig card after booting from the TF recovery, getting that DD image into linux and doing a filesystem recovery and save with Testdisk, then dding the resulting image back into internal memory. It worked, but I sure wouldn't recommend it!)

There appears to be some cruft left behind. I'm getting references to kooc as my device just now - the Transformer device.

The header of my updater-script now reads

(!less_than_int(1398083585, getprop("ro.build.date.utc"))) || abort("Can't install this package (Mon Apr 21 20:33:05 CST 2014) over newer build (" + getprop("ro.build.date") + ").");

if get_stage("/dev/block/platform/sdhci-tegra.3/by-name/MSC", "stage") == "2/3" then

package_extract_file("recovery.img", "/dev/block/platform/sdhci-tegra.3/by-name/SOS");

set_stage("/dev/block/platform/sdhci-tegra.3/by-name/MSC", "3/3");

reboot_now("/dev/block/platform/sdhci-tegra.3/by-name/MSC", "recovery");

else if get_stage("/dev/block/platform/sdhci-tegra.3/by-name/MSC", "stage") == "3/3" then

And this is where I may be unable to proceed.

Yep, started to run, bombed. Based on what I'm seeing in the file, this validates what I've said about not flashing the TF recovery. In order to rebuild my device at one point I had to have access to a viable recovery with ADB, and so was forced to flash the TF recovery.

I suspect that decision is now preventing this update from getting applied. Which is OK with me, though if someone has access to an untouched stock recovery from 1.0.12 or so it wouldn't be a bad idea to post it.
[Android General] mygoldkenn:
If you edit any command in the updater-script before updating the rom, please share it =s

I am stuck here with the error during verification.

---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------

Is the "KOOC" because of the CWM you use is taken from the version made for transformer device?
[Android General] roustabout:
Yep. In fact, it's because I had to flash that recovery to the firmware during one of the stages of my rebuild. I've been able to work around it up until now by editing the updater-script, but it looks as if that won't get my device over the last step with the new update.
[Android General] roustabout:
Are you doing this install by

fastboot boot recovery.img

and then using Clockwork from there? If so, you can turn off signature verification in zip files, it's in an advanced settings item.

If you're trying to use the stock recovery, you can't disable the verification and hence can't edit the commands.
[Android General] mygoldkenn:
update

The verification error message came from stock recovery (3e)

When I tried to update with CMW, the error was

Asserted failed ..

E:Error in /tmp/sideload/update.zip

(Status 7)

Installation aborted
[Android General] okusare:
Downloaded the update.zip but not working. When I try to install I get a black screen and have to force a reboot.

I'm updating from 1.00.12, should I root the tablet first? Damn it! So close and still so far. At least HP is giving us some hope throwing us an update although it doesn't work :silly:
[Android General] mygoldkenn:
update

We are on the same boat. Hopefully, any expert can show us the way.
[Android General] roustabout:
Here is what I would try

- unlock your device if it is not already unlocked

- fastboot boot clockwork - this boots your device using the custom recovery but does not write that to your device. The custom recovery does not check signatures

- edit the updater-script to remove the device check built into it

- copy the update to your device (in recovery, mount /sdcard, then an adb push update.zip /sdcard.zip lets you make changes to the update and try again without rebooting)

But, if you make any changes to the updater, the stock recovery will fail.

The alternate recovery will cause problems if you fastboot flash it, thus the recommendation to fastboot boot it instead.
[Android General] teskts:
I updated from 1.00.05. Non rooted. 1.00.05 version available in HP website. You may try to restore it first. During update tablet rebooted several times...during fist reboot I got black screen and waited few minutes.. Strange, but finally I got 4.4.2 which works flawlessly. Found speed improvement for browser. Also fixed audio issues for sensitive headsets.
[Android General] roustabout:
Looking at the script, one of the first things the install does, or tries to do, is to install a stock recovery and issue a reboot. On my device, it looks as if that step is failing after I strip the device model # checks, but I will give it more time to cook and see if it completes. My memory is that it's just been going straight back to a completed boot, but I'll stage it once more.
[Android General] okusare:
Tried to flash 1.00.05 back but doesnt work, looks like Im stuck in 1.00.12. Also where is Hp rom image of 1.00.12? Shouldn't it be available along 1.00.05 and 1.00.09? Are they trying to fool us pretending it never existed?

Anyway the update is real, what we now need to know is how to make it work! (well only a few of us) sigh :crying:

---------- Post added at 11:02 PM ---------- Previous post was at 10:34 PM ----------

Well it finally worked! I restored the tablet to factory settings and it grabbed the update right away. So people of Hp I advice you to do include a factory reset in your how-to-install prior to updating, so users like me can stop bothering the good people at xda-developers :laugh:

First thing I notice the tablet now goes smooth as butter, this tablet was and still is a good investment.
[Android General] mygoldkenn:
Do you mean you version 1.01.01 works?

I am still stuck with 1.00.12. I could not get the latest update.zip installed.

Dont know why HP does not just release it OTA
[Android General] okusare:
Yes it works, and I updated from 1.00.12, just make sure you use a formatted microsd card and put there update.zip.

When doing the factory reset of your tablet choose United States as your country (don't know if it makes a difference, just in case you're from another country).

Follow the Hp instructions to update:

1. Download the update.zip file to your computer.

2. Copy the update.zip file to the root folder of a microSD card. Do not unzip the file.

3. Fully charge the tablet, and then disconnect the charging cable.

4. Power off the tablet.

5. Insert the microSD card containing the update.zip file into the tablet.

6. Press and hold the Volume Down button and Power button simultaneously. When the boot menu appears in the top left corner of the screen, release the buttons.

7. In the boot menu, use the Volume Down button to highlight Recovery Kernel, and then press the Power button.

8. After a few seconds, an Android graphic appears with the message, No Command. Press and hold the Power button, and briefly press the Volume Up button simultaneously.

9. In the Android system recovery menu, use the Volume Down button to highlight Apply update from external storage, and then press the Power button to select.

10. Use the Volume Down button to highlight update.zip, and then press the Power button to begin the update.

11. The update package progress is displayed at the bottom of the screen. Wait while the device is updated.

12. An HP logo appears on the screen, and then the screen goes black. Wait while the device is updated.

13. An Android graphic appears with the message, Installing system update..., with two white dots. Wait while the device is updated.

14. An HP logo appears on the screen, and then the screen goes black. Wait while the device is updated.

15. An Android graphic appears with the message, Installing system update..., with three white dots. Wait while the device is updated.

16. When an Android graphic appears with the message, No Command, press and hold the Power button, and briefly press the Volume Up button simultaneously.

17. The device reboots. A window displays the message, Android is upgrading.

18. When the update is complete, the Android Home screen appears, and an updated version of the Android operating system is installed on the tablet.

If everything works and it should you're good to go! Just remember to factory reset your tablet first, yes you will lose everything but it's worth it.:good:
[Android General] mygoldkenn:
Was it OTA or update.zip?

Was it KitKat?
[Android General] okusare:
update.zip and kitkat, OTA is not working with this update
[Android General] mygoldkenn:
Downloaded the update.zip again from HP website.

With Android System Recovery <3e> , the error still remains..

Finding update package...

Opening update package...

Verifying update package...

Installing update package...

assert failed: getprop("ro.product.name") == "kadota_w_c"

E:Error in /tmp/sideload/package.zip

(Status 7)

Installation aborted

I am sure product name is correct as it's stated on top of bootloader screen

:confused:

---------- Post added at 10:20 PM ---------- Previous post was at 10:03 PM ----------

Can anyone who successfully updated to 4.4.2 do the ROM backup via CWM?

So people who fail can do the restore T T including myself.

:p:p:p
[Android General] okusare:
Is your slate locked or unlocked? That's really the only thing that I can think about of keeping you off updating. Make sure it's locked and in its original state, unrooted.
[Android General] roustabout:
Something I'm looking into now: there are at least two variants of the software stack for the device.

They are referred to as kadota_w_a and

kadota_w_c

Extract any update.zip file you may have and get a look at the updater-script -- it will tell you if it's looking for the a or c version.

Now look at your device's build.prop file and verify that it's the matching version.

If your device gets the big exclamation mark Android when it tries to update the OS, it is accessible by ADB, but in read-only mode.

You can do an

adb ls / to see the file tree in the recovery, and an

adb ls /tmp to see the temp file tree.

You can also pull some of the files, the most useful one probably being gotten via

adb pull /tmp/property.list

That tells you what your recovery is reporting about the device. It seems possible that one could have a kadota_w_c recovery on a kadota_w_a device, although so far my device is reporting itself consistently as a kadota_w_c in build.prop and in recovery properties using the stock recovery.

Your update to 4.4.2 needs to match what's in your recovery
[Android General] mygoldkenn:
Thanks for the info..

As I saw on the black screen of bootloader, it says my device is kadota_w_c

In the updater-script, it also checks kadota_w_c

I purchased the device from the US and the website I downloaded the file is also US. =[

I think variant probably refers to 7600us, 7600ca, 7600ea,....etc Mine is 7600us
[Android General] mygoldkenn:
The device was once rooted but now unrooted. Never unlocked.

CMW is still there. And I can enter both stock and custom recovery.

Error message occurs on both recoveries with different content.

On stock, "Assert failed get(prop.............." << about kadota_w_c

On CWM, product name does not match the rom version. I guess this happens because the CWM was made for transformer tegra 4. Therefore, the script sees the device as "KOOC" instead of "FIG" in which the device is actually "FIG"
[Android General] roustabout:
You can boot from CWM without doing a fastboot oem unlock command?

Wild.

Something I discovered today: if you boot into the CWM recovery, you can go to /tmp/recovery and pull logs - including logs written by the stock recovery.

On my device, a lot of the errors I see (using stock recovery and untouched update.zip files, or using CWM) are references to MSC

The update script calls for MSC several times:

/dev/block/platform/sdhci-tegra.3/by-name/MSC

With commands like

if get_stage("/dev/block/platform/sdhci-tegra.3/by-name/MSC", "stage") == "2/3" then

My partition table doesn't include an MSC, a side effect of the hosing the HP recovery did at one point.

I did get a bootable CWM that does not call the device a K00C device yesterday, but it does not call the device a fig yet, so it can't run the truly stock update.zip file yet.
[Android General] roustabout:
set_stage and get_stage - what does it mean for us?

This is interesting - I wanted to know more about set_stage and get_stage:

https://android.googlesource.com/platform/build/+/9b23f2cd786b46991b7c0198e69264b17875288d^!/

"install the new recovery first, so that the rest of the installation

is done with the new recovery. This can be useful if (say) the

package installation needs some features from the newer kernel.

For incremental packages, the verification phase is still done with

the old recovery.

This is only supported on devices where the misc partition is EMMC

(not MTD).

Two-step packages are slower to install and possibly confusing to

users (they will see their device reboot four times instead of twice),

so only use this option if necessary."

My device either does not have or does not see MSC, but I have other emmc partitions in the recovery.fstab

/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP

/metadata emmc /dev/block/platform/sdhci-tegra.3/by-name/MDA

I need to look, but I think I have USP, and probably can hack the script to apply the set_stage and get_stage to USP rather than MSC.
[Android General] mygoldkenn:
Yes, I did install recovery.img using flashify app downloaded from play store.

No oem unlock neccessary. Besides, I have never been able to enter fastboot.

My device is really defective...
[Android General] roustabout:
Did you back up the stock recovery before flashing the TF701 recovery, and if so, would you be so kind as to post it?

My stock recovery appears to work but gives absolutely no indication onscreen that it's doing anything. Not sure how that happened, but it means I'm attempting recoveries in the dark with stock...

Actually, I've looked more carefully at my parititions, and I'd really appreciate it if someone could do this next time they're booted up in CWM on the Slate 8:

connect a USB cable

adb connect slate in CWM mode

At ADB, type

parted /dev/block/mmcblk0

then type

print

Copy the output from that command

then type

quit

to exit parted.

Don't change anything in your partition table, but if you could print it out for reference it'd be very helpful.
[Android General] mygoldkenn:
Do you mean the screen becomes entirely black when you select "boot recovery kernel"?

If so, that happens to me also. Can never see dead android. It's just black.

The time that I can see is when I messed up the rom with modified command. The device just boots up into dead android (stock recovery)

What a weird device from HP.

Still.. kitkat update does not work T T
[Android General] roustabout:
Exactly that. I know the recovery is booting, because I can see the device as an ADB device in recovery. But I get no indication that it's working until it dies.

But I discovered when I booted into CWM that I can see a lot of info from prior attempts at recovering in the logs - and that the logs contain both CWM and stock recovery entries.

The stock recovery posts:

I:timed out waiting for key input; rebooting.

__bionic_open_tzdata: couldn't find any tzdata when looking for America/Los_Angeles!

__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!

__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!

Starting recovery on Tue Jun 24 15:12:16 2014

recovery filesystem table

And when either one tries to set up its filesystem, it errors out on

stat /dev/block/platform/sdhci-tegra.3/by-name/MSC try 1: No such file or directory

That partition is what the stock recovery is trying to access during the KK update, to note its progress.

My filesystem table is barely working - I imaged my internal memory to an sdcard and repaired it offline, then imaged it back to the device when I first got the tablet, because of this bug in recovery - at one point, in mid-recovery, I reset the tablet.

In parted, I currently have:

parted /dev/block/mmcblk0

GNU Parted 1.8.8.1.179-aef3

Using /dev/block/mmcblk0

Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) print

print

print

Model: MMC 016G92 (sd/mmc)

Disk /dev/block/mmcblk0: 15.8GB

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Number Start End Size File system Name Flags

1 143MB 948MB 805MB ext4 APP

2 1216MB 2290MB 1074MB ext4 CAC

3 3390MB 15.8GB 12.4GB ext4 UDA

I know that's badly wrong, which I why it'd be so nice if someone could run the command (from CWM, or by copying /sbin/parted from recovery to /xbin/parted and chmodding it to 755 on a rooted device, and running it from the regular OS)
[Android General] roustabout:
not with a bang

as they say, but a whimper (or more, a moan of 'you knucklehead, you're *never* getting that connector back on') my slate is kaput.

I wanted to get a look at the mainboard layout (and did) but to do so I needed to unseat two ribbon cables, one being the LCD connector.

The LCD connector proved impossible to reseat properly, and now the display on my slate will not illuminate.

I did find the issue I was having with getting a completely restored image on my updates, though: the partition in use as /system was not large enough to hold the entire system.

It held *most* of it, enough that I could apply normal updates and get some benefit from them - but the last few files in the extraction were failing, it turns out, and so my recovery was never being reimaged at teh end of an update. (The script fixes recovery not with a recovery.img file, but with a patch process.)

In the course of resizing it, or trying to, I terminally bollixed my partition table, and was no longer able to get even CWM to boot enough to try to repair it.

One lesson: it is worth looking in /cache/recovery to see your logs, even if it seems that updates have been succeeding!

Another: if your partitions aren't in order, don't reboot thinking the device will reorder them - it won't. Delete them all and recreate them in the correct order before rebooting.

I have to admit, I'd been using the tab pro a lot more than the slate - lighter and faster, and with CM11.

But the battery life on the slate was really fantastic, and I enjoyed having it.

Best of luck to all Slate owners!
[Android General] okusare:
I think you should return your Slate and have it replaced under warranty. HP has a fantastic customer service and if you contact them I am sure they will provide you with a solution that might well be a replacement. Give it a try :fingers-crossed:

Just don't say you opened it, tell em the display doesn't work anymore and that's all. Best of luck.
[Android General] roustabout:
I might be able to get a replacement from HP, but I did in fact break it. I do really like the aspect ratio and the battery life, but I'm not too interested in misrepresenting how much I know about the display malfunction.

The counterargument, I suppose, would be that more customers bought and kept the device because it was rootable using the tool I tested :)
[Android General] mygoldkenn:
I believe the black screen when u enter recovery can be solved by re-installing recovery.img again.

I actually tried installing recovery.img found in update.zip.

The dead android logo appears now.

Guess it's kindda software problem
[Android General] eseregin:
Hi guys!

It looks like HP removed update.zip for KitKat from servers, or I cannot find it ...

Could anybody point me to file, or upload zip somethere and give a link please?
[Android General] mygoldkenn:
kitkat update released earlier was not fully compatible to all 8 pro devices due to some hardware differences from production. hence, hp decided to remove 1.01.01 rom download. the information comes from hp support.
[Android General] eseregin:
Thank you.

Yeah... I thought so.

May be somebody has zip locally and can share with us? 8-)
[Android General] mygoldkenn:
Let me know the location where I can upload.
[Android General] eseregin:
Do you use Google drive or Dropbox? 400 mb should go good to any fileshare system...

Or Mega, pretty good free service

https://mega.co.nz/
[Android General] astralgunner:
rooting

you can also try using framaroot, but sometimes it doesnt fully root certain arm-processor phones
[Android General] eseregin:
Framaroot does not work...

---------- Post added at 05:19 PM ---------- Previous post was at 05:13 PM ----------

Towelroot does not work as well
[Android General] mygoldkenn:
TRY

http://www.shuame.com/en/root/

IT WORKS
[Android General] zaccika:
Hi,

Yes, it's works, but performance problem with TotalCommander. TC worked very slowly.

After install it SuperSU, and TC works perfectly!

BR,

zacci
[Android General] eseregin:
Yes it IS works!

and so easy...

Think this methode really need to be in OP 8-)
[Android General] mygoldkenn:
I still canot get my 8Pro updated to Kitkat

Any suggestion? Anyone? Plsssss

The downloaded file from HP server (1.01.01) really kills the device. Fortunately, I have backup of previous rom via CWM.

My device is kadota_w_a

Thanks in advance...
[Android General] eseregin:
Mine kadota too

But even have no zip file 8-)
[Android General] tcsfoong:
Just rooted HP Slate Pro 8

Hi,

I am new to the forum and very, very new to rooting. After reading the whole 11 pages, I decided to try rooting my 2 months old HP Slate Pro 8 using recommendation from Post#107 and it worked. I checked using Root Checker and also installed Titanium Backup and Greenify, all "root" apps.

My question is: If there's an OTA update from HP, should I install it? If I do, will it unroot the tablet? If do not install, how can I prevent automatic updates to the system?

Thanks to all for an excellent forum.

Chan