JB Update file (for devs to verify)

[jojosilvera]

Just know that once you've flashed JB -- you won't be able to get into CWM Recovery or TWRP, and reflashing either isn't advised. Currently there are at least three people(including myself) who have completely unbootable* units after attempting to flash a recovery once JB was in place.

*- it gets into Tegra's APX mode, but no tools (nvflash) for the TF300T exist yet.

oh gosh now i'm kinda reluctant, yes i'll have root but to have an unlocked bootloader and unable to get into twrp sounds like a major deal breaker. u think they will find some work around to get twrp or cwm recovery working?

 

[krhainos]

oh gosh now i'm kinda reluctant, yes i'll have root but to have an unlocked bootloader and unable to get into twrp sounds like a major deal breaker. u think they will find some work around to get twrp or cwm recovery working?

I'm sure at some point, fairly soon I hope, there'll be an updated image that you'll be able to flash over fastboot or dd from the shell.

 

[ncguy68]

I renamed dlpkgfile -> JellyBean.zip and modified the updater-script to remove lines 3 and 4 as mentioned in this post
http://forum.xda-developers.com/showpost.php?p=30405431&postcount=26
no other changes were made.

part one:

http://www.mediafire.com/?7cggde3e3k333xf

part two:

http://www.mediafire.com/?9xcrlgfmlkya4b9

If you rename this zip file to US_epad-user-#.#.#.##.zip and copy it to the root af an SD Card the tablet recognizes it at a System Update file and offers to install it. What would happen if it tried to install it?

 

[krhainos]

If you rename this zip file to US_epad-user-#.#.#.##.zip and copy it to the root af an SD Card the tablet recognizes it at a System Update file and offers to install it. What would happen if it tried to install it?

Only one way to find out

Honestly, since the file was modified, the Asus stock flasher might refuse to flash the update if the hash doesn't match.

However, if it actually does go through -- it might work as the only modification done to the zip file compared to the original Asus download, is that two lines in the install script that perform a check have been removed. Modifications described in steps 3-5 here : http://forum.xda-developers.com/showthread.php?p=30405431#post30405431

Feeling brave?

 

[i-l-l]

ugh. I've been trying to flash this all day.

I always get a assert failed: apply_patch_check ("/system/app/Phonesky.apk", hash number, another hash number
E: Error in /sdcad/JellyBean.zip
(Status 7)

Phonesky is the Play Store. I've uninstalled all updates to the Play Store so it goes back to stock and no change in this error. I even changed the script so it skips that file and still get the error. Here's the weird part, I've never used a modified Play Store apk on this device.

Any clue on what could be the problem?

 

[bimmerboii]

Ok guys I managed to identify a file in /root/cache that was downloaded when downloading the firmware straight from the tablet. The file is named "dlpkgfile" and its about 230Mbs, hopefully this can help some ppl. I don't recommend you use this file if you aren't a dev, since I don't know if it can do something bad to your tablet. I have no knowledge of this type of thing, just trying to give a helping hand....

Anyways I uploaded it to my dropbox, so please only devs download it for now I don't want to get a lot of traffic in my dropbox and be shutdown or something lol

To download it just right click and save link as: Download here

OP your dropbox link is disabled..

Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

 

[krhainos]

OP your dropbox link is disabled..

Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

Check out page 5 for some mirrors! (scroll a bit down)

http://forum.xda-developers.com/showthread.php?t=1840397&page=5

 

[jvanassche]

ugh. I've been trying to flash this all day.

I always get a assert failed: apply_patch_check ("/system/app/Phonesky.apk", hash number, another hash number
E: Error in /sdcad/JellyBean.zip
(Status 7)

Phonesky is the Play Store. I've uninstalled all updates to the Play Store so it goes back to stock and no change in this error. I even changed the script so it skips that file and still get the error. Here's the weird part, I've never used a modified Play Store apk on this device.

Any clue on what could be the problem?

The updater ensures that the original file matches a hash and then patches it, instead of replacing it completely, so you need to make sure that your version is as up to date as it would be on a normal .30 install. It probably needs to be fully updated. No idea why it wouldn't have worked the first time you tried it with a fully updated version, though.

 

[i-l-l]

The updater ensures that the original file matches a hash and then patches it, instead of replacing it completely, so you need to make sure that your version is as up to date as it would be on a normal .30 install. It probably needs to be fully updated. No idea why it wouldn't have worked the first time you tried it with a fully updated version, though.

I checked the version number of the Play Market installed and it was the lastest version that was released a few days ago. No luck with the flashing. Then I uninstalled all the market updates and still got the same error message. I've never been this stomped on anything Android related in 3 years. I've spent more time messing with this tablet today than I have total in the last 3 months.

 

[jojosilvera]

I'm gonna wait out just a bit longer to see if more advances can be made available

Sent from my ASUS Transformer Pad TF300T using xda app-developers app

 

[gmillz]

Has anybody gotten a recoveery to work? If so could you make a backup and upload system.img from it?

Or anybody that has it installed, could you get me a system dump?

 

[Capt-CDD]

I renamed dlpkgfile -> JellyBean.zip and modified the updater-script to remove lines 3 and 4 as mentioned in this post
http://forum.xda-developers.com/showpost.php?p=30405431&postcount=26
no other changes were made.

part one:

http://www.mediafire.com/?7cggde3e3k333xf

part two:

http://www.mediafire.com/?9xcrlgfmlkya4b9

Thanks for your work! I have to ask why 2 zip files for one update.zip? Is there a MD5 checksum for this?

 

[Paschalis]

Just know that once you've flashed JB -- you won't be able to get into CWM Recovery or TWRP, and reflashing either isn't advised. Currently there are at least three people(including myself) who have completely unbootable* units after attempting to flash a recovery once JB was in place.

*- it gets into Tegra's APX mode, but no tools (nvflash) for the TF300T exist yet.

What do you mean?
You flashed TWRP or CWM and your device is now not bootable???

I was from a unlocked rooted TF300, returned to stock, flashed JB update, restored root.
For recovery: i installed twiceTWRP using goo app, with no luck, tried 2 more times with fastboot, and also tried CWM using fastboot.

My device is bootable, but no recovery yet!

 

[untermensch]

Thanks for your work! I have to ask why 2 zip files for one update.zip? Is there a MD5 checksum for this?

I had a file size limit, so it was split into 2 files, sorry no MD5
someone re-posted the original file some where in this thread.
http://forum.xda-developers.com/showpost.php?p=30412941&postcount=49


---------- Post added at 08:13 PM ---------- Previous post was at 08:09 PM ----------

What do you mean?
You flashed TWRP or CWM and your device is now not bootable???

I was from a unlocked rooted TF300, returned to stock, flashed JB update, restored root.
For recovery: i installed twiceTWRP using goo app, with no luck, tried 2 more times with fastboot, and also tried CWM using fastboot.

My device is bootable, but no recovery yet!

I got recovery too work by swapping the recovery kernel of ClockWorkMod with the recovery kernel from this Jelly Bean update.
I have erased and re-flashed 4 times and have not encountered any thing scary, and have now re-rooted. I'm sure the recovery
devs will have updates in a few days.

http://forum.xda-developers.com/showpost.php?p=30451422&postcount=17

 

[Paschalis]

If i flash that file, and then twrp, will twrp work?

Also bricked guys received ota, and after that tried to install custom recovery?
That means they were 'locked' before, got ota, and then install custom rec.

If not, i was lucky since i have a non working recovery and bootable device.
I will wait before flasing the testblob file!!

Jb is goddamn smooth!!!

I still have it bloated, with no OC, and its faster/smoother than debloated OC'ed ics!!!!

Sent from my ASUS Transformer Pad TF300T using xda app-developers app

 

[untermensch]

It is ClockWorkMod with a new kernel and is more for the recovery devs.
wait a few days and you will have official updates from people with better
knowledge about the kernel and recovery partition than I do.

If i flash that file, and then twrp, will twrp work?

Also bricked guys received ota, and after that tried to install custom recovery?
That means they were 'locked' before, got ota, and then install custom rec.

If not, i was lucky since i have a non working recovery and bootable device.
I will wait before flasing the testblob file!!

Jb is goddamn smooth!!!

I still have it bloated, with no OC, and its faster/smoother than debloated OC'ed ics!!!!

Sent from my ASUS Transformer Pad TF300T using xda app-developers app

 

[Capt-CDD]

Ok I have read and searched now until my eyes are crossed. Still not sure what the consensus is.
If:
1. I'm on stock .30 and all system apps. are intact.
2. I am rooted now and have installed and been using superSU. and have a root backup via voodoo OTA
3. If I unlock the bootloader and install TWRP 2.2.13 prior to installing the JB via the zipfile in this thread.
4. Install stock JB using the dlpkg.zip from this thread.
5. Restore root via VOODOO OTA and reboot.
Will I still have Recovery and Root?
Sorry if I'm dense and I realize it just released, but I hate to unlock and lose
warranty only to have it removed with the update. I have been reading about
this all evening in all of the thread addressing the issue and some claim success
some not so much.

Thanks

 

[Zamboniman]

I got recovery too work by swapping the recovery kernel of ClockWorkMod with the recovery kernel from this Jelly Bean update.
I have erased and re-flashed 4 times and have not encountered any thing scary, and have now re-rooted. I'm sure the recovery
devs will have updates in a few days.

Thanks, that worked perfectly. I now have root and CWM recovery on JB.

 

[DMardroid]

Ok I have read and searched now until my eyes are crossed. Still not sure what the consensus is.
If:
1.............

Thanks

You'll have it all but no custom recovery. That fix should be available soon.

Sent from my Nexus S 4G using Tapatalk 2

 

[jojosilvera]

Ye I expect in the next couple days it will be up look how quickly the jb update was made available. U guys are awesome I must say

Sent from my ASUS Transformer Pad TF300T using xda app-developers app