yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] hypocritelecteur:
I know, I'm trying to isolate the compatibility issue if not to help the dev community then to satiate my idle curiosity. I also am one of the few people that -really- uses multiple accounts on a day-to-day basis and honestly thats probably not worth your time to troubleshoot as its a decidedly niche feature. I was able to create both limited and secondary user accounts on the PA ROM, and technically everything was functional but the system became decidedly unstable especially when switching users.

Ideally I'd hope to find a way to have root, data2sd, ART, OC, and multiple user accounts on a stablish KK rom. But that's a tall order for an aging device with a small but determined developer community. Obviously you can't pile up that many experimental features and expect rock solid experience, so the goal is not explosively volatile rather than stable :P

So I continue to tinker!

On a side note, SU appears in xbin, not bin.
[Asus  Eee Pad Transformer Prime] FarSight87:
Ah, so if I dont have a blob.bin file, im toast, is that right?
[Asus  Eee Pad Transformer Prime] Xerxes-3.0:
I hate to tell you this but...yes, as far as I know. :(
[Asus  Eee Pad Transformer Prime] wilspeak:
Need somw help

Hello Namidairo, I am intrested in flashing this ROM , right no wI am running (Bake Bean bb8 Rom) (JB Android 4.2.2) (Kernal verison 3.1.10-gb71c6ae), and have TWRP recovery installed. You said the I need to NVFlash and have blob files installed , how do I go about doing this before I try to flash this ROM , thank you in advance .;)
[Asus  Eee Pad Transformer Prime] onebyside:
he's refering to following the guide and generating the files you need to recover from any problems during flash process....dont proceed without!!!

https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
[Asus  Eee Pad Transformer Prime] wilspeak:
Thank you I appreciate your help
[Asus  Eee Pad Transformer Prime] point_pt:
Hi

One stupid question.

As far as i know, doesn't exist an official cyanogenmod 11 for our tablet, am i right?

So, why is this rom unofficial? Is not possible to incorporate it on the official release channels?
[Asus  Eee Pad Transformer Prime] Namidairo:
I'd have to get the device and kernel branched to cm-11.0, then merge in all the changes again, then get that reviewed and approved on gerrit... Then I'd have to do a pull request to themuppets for the 2 vendor files that I removed (Or alternatively patch the egl loader code and submit that for review). After thaaaat, I'd have to go and reopen/nudge the patchset for legacy egl libs to be merged (http://review.cyanogenmod.org/#/c/54257/). Finally I would fork their hudson, do a quick edit and do another pull request to finally get the nightly builds rolling out.

TL;DR: I'm lazy.
[Asus  Eee Pad Transformer Prime] Omemanti:
10.2 => 11

Hey Namidairo,

Im currently running your 10.2-20130923-UNOFFICIAL-tf201 (flashed with TWRP v2.6.1.0)

would you recommend to go to this version, if so how to proceed?

Or would you rather suggest to go up to : cm-10.2-20131211-UNOFFICIAL-tf201 and wait it out for someone (or you) to build a stable Kitkat?

second, when I started it all I was on JB, I was told that I couldnt run NVflash.

Is that true, or can I run NVflash while booing on a JB bootloader?

Thnx,
[Asus  Eee Pad Transformer Prime] Xerxes-3.0:
It is not true.
[Asus  Eee Pad Transformer Prime] Omemanti:
Hey,

Thnx for the reply:

I found this in the link: "you would have the new 10.4.2.15 bootloader" I have 10.4.2.18 on my TF201.

Will this procedure that you linked to ,downgrade my bootloader from .18 to .15? and after that install NVflash.

Please correct me if Im wrong.
[Asus  Eee Pad Transformer Prime] Bastaerd:
The rom is quite stable, it's my Prime's daily driver. Only thing that doesn't work is GPS but I can live with that. 4.4 feels smoother then 4.3 imo so I would definately give it a go.

You can use NVFlash while on JB bootloader (Flatline!): https://www.androidroot.mobi/introducing-flatline-nvflash-for-jellybean-n7v1-t201-tf300t-tf700t/

After obtaining the blobs, flash Voyager2k's TWRP: http://xdaforums.com/showthread.php?t=2595531

Afterwards do a full wipe/factory reset and flash the rom + 4.4.2 compatible gapps (PA modular ones or banks gapps).

On another topic, tried to compile Omni for our Primes but got a 21.1 MB output file. Don't want to promise anything since my time and skills are limited. If you guys want to take a look, my github can be found here: https://github.com/Bastaerd
[Asus  Eee Pad Transformer Prime] Xerxes-3.0:
No idea, seriously.

If they did just minor tweaks between the versions they did not have to change the bootloader, I think the main change is ICS/JB which is mentioned everywhere.
[Asus  Eee Pad Transformer Prime] l33tlinuxh4x0r:
I am trying to install the 0306 build using CWM provided in the downloads section. It appears that my unlock token keeps getting deleted and even after I restore it CM will not boot just stuck at the ASUS device is unlocked screen. I cannot boot the rom I even tried TWRP still no good. I have to install another rom for it to work. I would love to use this rom as I love CM11 please help.
[Asus  Eee Pad Transformer Prime] Fgarcor:
Xerxes and I have the same problem.

Sent from my GT-I9505
[Asus  Eee Pad Transformer Prime] Bastaerd:
You need an 4.2.2 compatible recovery aka Voyager2k's TWRP.
[Asus  Eee Pad Transformer Prime] l33tlinuxh4x0r:
That is what I was using. Didn't work. I ended up flashing the Hairybean bootloader flashing the tf300t recovery and tf300t CM official nightly. It works like a charm.
[Asus  Eee Pad Transformer Prime] Bastaerd:
More people are having the same problem which I find baffling since other people can flash without problems. Which bootloader was your Prime running before changing to the AW one?
[Asus  Eee Pad Transformer Prime] l33tlinuxh4x0r:
I was using the bootloader that is installed by androidroot.mobi nvflash. The stock JB one.
[Asus  Eee Pad Transformer Prime] kokopuphz:
Have you in the past used the create option of nvflash to recover your device?

This is just a theory, however I believe the LNX partition may have been moved forward 4mb by the flash.cfg used, thus the bootloader flashes the kernel blob offset by 4mb, causing any kernels larger than 4mb to overwrite the CER partition and hence the unlock token.

Or, the recovery is not properly identifying the location of the LNX partition either because of an incorrect partition table or another.

You would have to modify the zip to do only either the recovery flash or the bootloader staghng method and see which one works. Right now the kernel is flashed twice using both methods, and one or the other is not working.

---modified

I've confirmed on my own tablet that it was the recovery flashing mmcblk0p10 that was causing problems for some people.

It'd be best if the updater-script that is included in the zip file has that line removed, so that the kernel will simly be flashed via the bootloader. You could go ahead and modify the update-script and reinsert it into the zip file, and it should work.
[Asus  Eee Pad Transformer Prime] l33tlinuxh4x0r:
Yes I have recovered with nvflash. You are probably exactly right in what is wrong but I am too lazy to do a fresh CM install right now to confirm.
[Asus  Eee Pad Transformer Prime] Xerxes-3.0:
I too have the same problem, but it occured first before I ever did an nvflash recovery. However, I had another ROM installed first.

I can reproduce the problem, but: does the fact, that Androwook with its own bootloader works fine support or contradict your theory?

It's just a hint, I have no detailed insight of the inner witchcraft of the prime.
[Asus  Eee Pad Transformer Prime] kokopuphz:
I've confirmed that the issue is due to our LNX and SOS partitions being added via the kernel with locations hardcoded into the source code. The offset being used for LNX (the kernel boot image partition) is set as 31744(x 512) in the defconfig.

Which means, there'd be problems depending on the zip package that is being flashed and how the flashing was implemented. If the SOS and LNX partitions are being directly flashed from within the zip package, then the flash will not be successful. If the staging partition is being used to flash the SOS and LNX, then the flash will be fine.

In the CM11 zip, the LNX is being flashed both directly from within recovery, and then through staging afterwards. The direct LNX flashing (mmcblk0p10) is the part that is corrupting the unlock token.

One way to fix this would be to have a specific recovery compiled for wherever our LNX and SOS partitions lay. However this is not a good solution as it would screw up everyone else if they accidentally use such recovery.

Another solution is to have all developers for the tf201 understand that the partition tables may be different between devices, and not use the direct flashing method within their installation packages.

The best solution is for those who have partition configurations that are not the same as the default partition layout redo the partitions so that it will be back to the default layout.

As for androwook prime hairy bean, the installer uses the staging method, thus no problems result.
[Asus  Eee Pad Transformer Prime] alternator2:
unable to install this ROM

Hi all,

I've been trying to install various versions of this ROM several times, never successfully. I've also tried several TWRP versions, with official TWRT up to version 2.6.3 it didn't finish zip installation. On VoyagerTWRP v1.2 the cm-11-20140306-UNOFFICIAL-tf201 installed successfully but during boot I ended up with the following error message:

no certificate to inject

Signature Mismatch.

Booting failed

Unrecoverable bootloader error (0x0000008).

Any idea how to get this ROM up and running? I'm using WW_10.4.2.18 bootloader. Luckily my Prime is nvflashed.

Thanks for replies.
[Asus  Eee Pad Transformer Prime] kokopuphz:
Once you download the zip, find the file named updater-script under the folder META-INF/com/google/android/.

Open the file with a text editor, and find the line near the end of the file that reads something like:

package_extract_file("boot.img", "/dev/block/mmcblk0p10");

Remove the line and save and replace the one in the zip file with the modified one.

Now it should be flashable.
[Asus  Eee Pad Transformer Prime] Fgarcor:
[MENTION=3168536]kokopuphz[/MENTION] is there any place where I can find some info on:

- how to redo the partitions

- what should be the right sizes of every partition

Shouldn't the partitions be properly made when flashing a stock Rom?

Sent from my GT-I9505
[Asus  Eee Pad Transformer Prime] onebyside:
+1
[Asus  Eee Pad Transformer Prime] golokipok:
Hello, I can't seem to flash the kernel from here http://xdaforums.com/showthread.php?t=2606892. The x axis is still inverted. I'm using the prior version of this ROM and the kernel is still working but now it doesn't seem to work on this version. Any help?
[Asus  Eee Pad Transformer Prime] l33tlinuxh4x0r:
Is there anyway that we could get CM to build these nightly? Is all that needs to be done is give the device files to CM upstream or is it more complicated.

Also is there a list of bugs/things that are not working for this rom other than the GPS and why is the GPS broke? Is it a kernel issue?
[Asus  Eee Pad Transformer Prime] kokopuphz:
Will post again once analyzed
[Asus  Eee Pad Transformer Prime] Namidairo:
It's more complicated than that, I detailed it in a wall of text rant a page or two back.

Bugs: May or may not spontaneously brick you on flash because of the releasetools? I should fix that... (I did say use nvflash...)

I suspect the GPS is either the kernel's or my fault. :S
[Asus  Eee Pad Transformer Prime] kokopuphz:
[MENTION=3607492]Fgarcor[/MENTION]

There's a semi-automated Linux based Nvflash recovery script that was posted by [MENTION=2322613]craigacgomez[/MENTION] a while back in his recovery thread. This tool uses the --create option of Nvflash to completely repartition the internal mmc.

http://xdaforums.com/showthread.php?t=1927818

The nvflash --create option uses the contents from the configuration file given (flash.cfg) to recreate all partitions. In order to change the partition layout, you'd have to modify the contents of the flash.cfg to the partition layout that you would like, and then use that to run the create option instead.

Flashing stock rom usually does not redo the partition layout. Although there is a "PT" partition that is included in the stock ROM, to my knowledge, this does not actually repartition the mmc.

Looking into the source code from the below commit, it appears that the 15360 and 31744 is an offset that is used as a number from the end of the boot block as defined by the mmc extended csd. The commit also implies that 32Gb and 64Gb models may have different boot block sizes defined in the CSD (especially since some are Kingston, some are Hynix). This also explain why some end up bricked whilst others do not.

https://bitbucket.org/cyanogenmod/a...mits/1c59573e4618d27d461296315647287b718e9853

The 64Gb Hynix extended CSD defines the boot block to be 4Mb(8192 sectors), which signifies that the first 8Mb(8192 x 2 since there are 2 blocks) of the mmc are allocated for boot, and is not visible in userspace once the kernel begins to load. The kernel thus is looking for the LNX partition to be located at 31744 + 16384 = 48128 sector. The flash.cfg has configured the LNX to start at 39936, thus anything over 4Mb spills over into the actual CER partition.

Initially, I thought that this was simply a misconfiguration of the flash.cfg and that our partitions were not the same as asus default, however I have come to think otherwise upon examination of various documents. The above commit showing that there are various boot blocks being defined in the 32Gb as opposed to the 64Gb suggests that the flash.cfg is actually correct, and that the kernel code needs to be update to reflect the above commit. Simply stated, we do not need to re-partition, but it was simply a bug in the kernel code that was affecting the flash process for owners of devices with certain mmc cards (most likely 64Gb Hynix, as this is what I have)

Sorry for the incorrect assumption earlier.
[Asus  Eee Pad Transformer Prime] Fgarcor:
However, now that you mentioned it, I will try nvflashing via Linux.

Thanks for the detailed explanation.

Sent from my GT-I9505
[Asus  Eee Pad Transformer Prime] Namidairo:
Well, I got around to changing up the releasetools.

No more double kernel weirdness that would have been overwriting stuff it shouldn't have in some devices. (It should have never been writing directly to mmcblk0p10, that's a sure way to mess **** up.)

That and I removed the horrendously old prebuilt kernel, since I'm pretty sure it wouldn't have booted anyway (I think it was there since ICS), and since prebuilts are deprecated and confusing anyway.

New build will be up whenever it's done uploading. (Them 1mbit upload speeds... Mmmm Australia.)

Edit: It's up.
[Asus  Eee Pad Transformer Prime] qubz:
Ozi oi! Melbourne here.

Nice one bro.
[Asus  Eee Pad Transformer Prime] Bastaerd:
TY for changing the releasetools, saves me a lot of time figuring those out in order to build Omni for our Primes.

Also, noticed some commits adding F2FS support. Did you try f2fs [MENTION=3168536]kokopuphz[/MENTION] already? and if so what is your experience?
[Asus  Eee Pad Transformer Prime] kokopuphz:
[MENTION=4224959]Bastaerd[/MENTION], currently have been working on trying to optimize some code for our kernels, so I haven't gotten around to trying out f2fs completely yet.
[Asus  Eee Pad Transformer Prime] Bastaerd:
Ah, ok! Let us know how it goes. Would love to pitch in but still figuring out how to build omni + not much time because of internship.

Maybe starting a dev thread is a good idea?
[Asus  Eee Pad Transformer Prime] Fgarcor:
Thanks Namidairo and Kokopuphz!

The latest version flashed without any problems. No more bricks.

Amazing job finding the issue.
[Asus  Eee Pad Transformer Prime] onebyside:
TP201 64gb

Battery 95%

TWRP v2.6.3.0

Factory Wipe

Installing cm-11-20140331-UNOFFICIAL-tf201.zip

check md5

skip md5

set_metadata_recursive: some changes failed

E:Error executing updater binary in zip cm-11-20140331-UNOFFICIAL-tf201.zip

Error flashing zip /external_sdcard/cm-11-20140331-UNOFFICIAL-tf201.zip

Updating partition details...

FAILED

suggestions
[Asus  Eee Pad Transformer Prime] Fgarcor:
I flashed with the cwm added in the attachements. That one sees also the external sd card. I would give it a try.

Sent from my GT-I9505
[Asus  Eee Pad Transformer Prime] onebyside:
I used the lastest off the front page..same one as you I guess

edit...ahh the recovery

---------- Post added at 08:53 PM ---------- Previous post was at 08:14 PM ----------

fastbooted the CWM recovery.img.SOS

reboot then back into recovery

load cm-11-20140331-UNOFFICIAL-tf201.zip

all well now

thank you
[Asus  Eee Pad Transformer Prime] ruggie0:
Yay! New build! Downloading now. However, a question on installing:

Given that I don't use this too often (my Nexus 7 2013 is my daily driver), and since I don't really have any important data stored on the internal SD card (I have a microSD &/a regular SD in the keyboard dock card slot), is a clean install of the latest build recommended to limit problems? I've noticed since installing the 3/06 build, my Prime has been running a little slow. I have killed most apps, although I am running avast! & facebook in the backround.

Or will a dirty flash work just as well?
[Asus  Eee Pad Transformer Prime] trubul:
Newest build's working properly, thank you.
[Asus  Eee Pad Transformer Prime] andrewjt19:
Progression of this development for our aged Prime has truly been excellent. Thanks to the fine gentlemen who have tirelessly kept it alive!
[Asus  Eee Pad Transformer Prime] caolfin:
+1

You guys are first class !
[Asus  Eee Pad Transformer Prime] hypocritelecteur:
Where are developer options in the new build? Pounding build number in about does nothing for me.

-nm, just a glitch-
[Asus  Eee Pad Transformer Prime] draftsman:
The USB port and SDcard on the keyboard dock don't appear to be working. Is this a known problem? If so is there a work around?
[Asus  Eee Pad Transformer Prime] tHoMaS-1:
Glad to see a new version

Downloading now....

Thank you
[Asus  Eee Pad Transformer Prime] HydroSkillet:
What I was waiting for! Thanks for the hard work on this!
[Asus  Eee Pad Transformer Prime] lukcinek:
Downloading...thx for an update

Wysłane z mojego EPAD przy użyciu Tapatalka
[Asus  Eee Pad Transformer Prime] tsc123:
update successfully

Hi

I updated to the latest CM-11-20140103 successfully.

Camera is now working !

Many thanks

:)
[Asus  Eee Pad Transformer Prime] lukcinek:
Battery life is superb comparsion to first rom. Since today I use it at a daily rom. I think it works better than HB. Thx a lot Namidairo

Wysłane z mojego EPAD przy użyciu Tapatalka
[Asus  Eee Pad Transformer Prime] tsc123:
Did you manager to get your calenda sync?
[Asus  Eee Pad Transformer Prime] lukcinek:
Yes but on newest gapps. First I install rom, than gapps I think from 31.10. Than the newest for kitkat...I think it was 08.12.2013...on this gapps calendar sync normall. I have one problem in the stock browser...when I check "most recent sites" as my start page in browser there is an error "net err: access denied". Good luck flashing new gapps

Wysłane z mojego EPAD przy użyciu Tapatalka
[Asus  Eee Pad Transformer Prime] Makrilli:
[MENTION=4460243]Namidairo[/MENTION] Any chance to get data2sd kernel in the upcoming weeks?
[Asus  Eee Pad Transformer Prime] mm284781423:
I use 12.08.2013 Gapps for cm11(no ART). calendar sync works.
[Asus  Eee Pad Transformer Prime] hypocritelecteur:
God you are the man. Seriously, you must walk around all day with a gigantic boner because yours is the face you see in the mirror every morning.

Is it really fair to start calling this tab old?
[Asus  Eee Pad Transformer Prime] Namidairo:
Sure, just not from me.

Since I believe [MENTION=3828422]Voyager2k[/MENTION] will be spitting out a PA4.4 rom since he's merged in my commits, and he generally spits out Data2SD kernels that are more or less compatible (Same source and all).
[Asus  Eee Pad Transformer Prime] Tempie007:
gj on the rom! trying this in an hour once i got my lazy ass out of bed to flash the new recovery!
[Asus  Eee Pad Transformer Prime] xperi:
alternate recovery

For anyone who prefers twrp over cwm, there's a modified version for kk roms. I tried it myself with this rom and it works perfectly. here's the link:

http://xdaforums.com/showthread.php?t=2595531
[Asus  Eee Pad Transformer Prime] Tempie007:
Running the rom for 2 hours now, and i must say it feels way snappier than cm10. Also it seems the youtube lag is gone (video's stuttering with no reason). Last thing; the Cyanogen cLock isn't eating battery anymore (i had to freeze this app with titanium in cm10 because it was eating battery (gps) ) Good job, will report any errors, but i'm no power user (browsing, youtube, tapatalk, that's it ;) )
[Asus  Eee Pad Transformer Prime] llothar:
Keyboard and location service is crashing on me instantly both with and without Gapps. I have modified TWRP, wiped, flashed twice, same thing happens.

What can be the cause?

edit: found it, wrong Gapps.
[Asus  Eee Pad Transformer Prime] demercie:
Hi, I installed it with success but it looks like that the external sdcard is not mounting, am I the only one with this problem ?

OK, forget that, I have just removes and reinserted the sdcard, and now I see it ;)
[Asus  Eee Pad Transformer Prime] kelddaug:
Namidairo, Is it as good as your 4.3.1.?
[Asus  Eee Pad Transformer Prime] Bastaerd:
Read the OP, we have tot wait for some stuff tot be fixed first ;)
[Asus  Eee Pad Transformer Prime] kelddaug:
I have read it, there is still some minor issues with 4.3.1, so that's why i asked.
[Asus  Eee Pad Transformer Prime] HORiZUN:
Flashed a few hours ago. Battery seems to be pretty solid, wifi works great along with camera and bluetooth.

It does feel a bit laggy. It's hard to describe, but the UI feels bogged down. Slow to the point that it's noticeable, but not slow enough that I could be upset by it.

Overall it's a great start to CM11! Very nice work!
[Asus  Eee Pad Transformer Prime] pagantek:
I haven't tried the latest build, I've been concentrating on the 0306 build. It was a pain to install, mostly my fault, but it's working awesomely. Never before have i had battery life like this :

Yes, it was parked most of the time, but I've never had uptime longer than 3 - 4 days parked. <edit> This was with both tablet and dock fully charged.

Thanks, and I'll take a look at the latest build.
[Asus  Eee Pad Transformer Prime] Namidairo:
Are you sure? I used the sdcard slot a couple days ago on a fat32 sdcard to grab some files the other day.
[Asus  Eee Pad Transformer Prime] draftsman:
The pop up shows when you insert and remove both USB and SDcard. Occasionally file explorer will display the contents of the USB if you reinsert the stick, restart the program and stand on your head with your left leg horizontal. The SDcard doesn't show anything.
[Asus  Eee Pad Transformer Prime] scote:
I dont have storage in my usb but I have a combined usb hub and ethernet with a wireless mouse adapter in one of the ports and it works. Sometimes the network goes off when the tablets been idle and I have to pull the patch cable and put it back again.
[Asus  Eee Pad Transformer Prime] draftsman:
Follow Up: ES File Explorer and Office Pro see the presence of the USB but doesn't see any content on the USB.
[Asus  Eee Pad Transformer Prime] grandmaster_b:
Really good ROM I have balls of steel so I flashed voyagers twrp and then flashed latest version of this ROM with no NVFLASH backup :eek:

It all worked perfect was running it for about a week then decided to try ART ........big mistake ! Android service closes on boot so had to reinstall fresh because I neglected to do a nandroid backup so if anyone is thinking of trying this ROM then make sure you have a backup if you try ART.

Other than ART not working this ROM is great !