New update today (TF300T, 10.6.1.27.1 - 20130711)

farmtool33

Senior Member
Dec 21, 2011
168
31
0
mechelen
Not sure if this is the correct place to post my issue or not, but ever since updating to JOP4OD.us_epad 10.6.1.27.1-20130711 the tablet no longer recognizes the dock/keyboard when docked and charging no longer works when tablet is docked and charger is plugged into dock. Charges just fine when plugged directly into tablet.
TF300T - Stock - Locked - Unrooted.
Only thing I've noticed is when doing a Cold Boot the line of text at the top of the screen shows "Android cardhu-user" - "bootloader1.00e" - "key driver not found...booting os" - "start fastboot usb download protocol"
Not sure if that will help anyone, I'm wondering if I should download the update and try installing it again if that's even possible?
I think the update that you did was not good installed , you should backup all your apps and data , and then download the newest update from the ASUS site and then install that. It's a reflash and I think something is wrong with the firmware of your keyboard , so when you update let the keyboared pluged in in your tablet.
 

robgee789

Senior Member
Jan 19, 2012
3,209
803
253
www.hacksden.com
I've built a test build of CROMi-X off this update and it's pretty good. A few bugs from Asus but nothing serious. Going to do some more testing this weekend but the kernel and ROM feel very snappy and stable to me. :)
not sure how your gonna top 4.7.0 mate to be honest, i use that's v4 kernel and everything just simply works :)
 

musthunt

Member
Apr 5, 2007
14
0
0
55
Millican
I think the update that you did was not good installed , you should backup all your apps and data , and then download the newest update from the ASUS site and then install that. It's a reflash and I think something is wrong with the firmware of your keyboard , so when you update let the keyboared pluged in in your tablet.
Not sure how exactly to do that but I'll do some reading and learn how so I can give it a try.
 

Tuna9351

Member
Dec 27, 2011
24
9
0
The Home Button is now back to it's former glory!

Something I did just notice with the update, not that it matters, but it did to me when I saw it was the Home button is now back to the middle LOL. I can finally rest in peace.
 

fractiousg

Senior Member
Apr 21, 2012
60
17
0
Centurion
fractiousg.blogspot.com
Something I did just notice with the update, not that it matters, but it did to me when I saw it was the Home button is now back to the middle LOL. I can finally rest in peace.
If you are referring to the use of the 4.2 style launcher, then you can still switch back to the 4.1 style (Settings -> Launcher). I guess that they just made it the default (finally). I switched to the new launcher with the first 4.2 update and haven't looked back :D
 

Tuna9351

Member
Dec 27, 2011
24
9
0
If you are referring to the use of the 4.2 style launcher, then you can still switch back to the 4.1 style (Settings -> Launcher). I guess that they just made it the default (finally). I switched to the new launcher with the first 4.2 update and haven't looked back :D
Nah I switched to 4.2 launcher a while ago! But the last update if you took notice - the home button itself , was displaced from the center of the apps button to the left just so ever slightly. And if you saw it, it could not be unseen https://encrypted-tbn3.gstatic.com/images?q=tbn:ANd9GcTQM3KrA4KKVhSft7lkZ8O24700Yy1DXAEQR1EAXCzxYBqGnnNwGw But in this update they actually put it back in the middle centered LOL. Like I said not that it matters but I can rest easy now.
 

fractiousg

Senior Member
Apr 21, 2012
60
17
0
Centurion
fractiousg.blogspot.com
Nah I switched to 4.2 launcher a while ago! But the last update if you took notice - the home button itself , was displaced from the center of the apps button to the left just so ever slightly. And if you saw it, it could not be unseen https://encrypted-tbn3.gstatic.com/images?q=tbn:ANd9GcTQM3KrA4KKVhSft7lkZ8O24700Yy1DXAEQR1EAXCzxYBqGnnNwGw But in this update they actually put it back in the middle centered LOL. Like I said not that it matters but I can rest easy now.
Oh wow, and I never even noticed...and now I won't get to notice since they fixed it :D
 

jon9314

Senior Member
May 8, 2012
65
11
0
Did anyone save the ota file before applying it? If so can you upload it?

Sent from my ASUS Transformer Pad TF300T using Tapatalk 4
 

joelalmeidaptg

Senior Member
May 25, 2012
1,505
1,349
0
Just had a reboot with an untouched and fresh install of the last version while playing candy crush saga... This hasn't happen in A LONG TIME...
 

sbdags

Inactive Recognized Contributor
Jun 24, 2007
12,753
15,556
0
Kenilworth, Coventry
Just had a reboot with an untouched and fresh install of the last version while playing candy crush saga... This hasn't happen in A LONG TIME...
Yeah I don't like the new kernel. Asus seem to have introduced some old 4.1.1 bugs. I was getting a jumping cursor on the browser which going back to a 10.6.1.14.8 kernel fixed.

Asus may have released a bit of a duffer here.

---------- Post added at 08:44 AM ---------- Previous post was at 08:43 AM ----------

Did anyone save the ota file before applying it? If so can you upload it?

Sent from my ASUS Transformer Pad TF300T using Tapatalk 4
You can download the full ROM from their website.
 

d-generated

Member
Apr 16, 2012
8
2
0
update problems?

hi,

also installed this update. coming from cm10.1 with the 4.1 bootloader, it was rooted and had unlocked bootloader. then i installed the update via twrp 2.4.4.0, installed fine but then it won't boot at first, got stuck at the asus bootlogo. i did "wipe data" and it solved this issue. now it boots up fine. and i'am on the newest stock fw. but not rooted anymore. when tried to install a new twrp with fastboot i found out that "fastboot getvar all" brings up the info "bootloader unlocked:no". i read in another thread where people are having issues with using fastboot due to the installation of a wrong recovery, having the same output when doing "fastboot getvar all". now i am concerned that i wont be able to install any recovery, because bootloader seems locked again. i am now too afraid to just try it, because i fear getting bricked. anyone can clarify this or tell me if i am too cautious? or anyone who has the same issue?

edit: i read i another thread that it's normal fastboot puts out "bootloader unlocked:no"?
 
Last edited:

UndisputedGuy

Senior Member
Dec 13, 2011
8,510
219
0
Since the update doesn't change the Android version, would it effect the current guides on the forum for rooting, unlocking your bootoader and changing your ROM?

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

funnel71

Senior Member
Jan 24, 2011
958
209
0
Since the update doesn't change the Android version, would it effect the current guides on the forum for rooting, unlocking your bootoader and changing your ROM?

Sent from my ASUS Transformer Pad TF300T using xda app-developers app
If you are unlocked, it would seem not, but it seems if you use the motochopper method to get root, that doesn't work any longer. Some are reporting success with backing up their root, while others report failure

Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
 
  • Like
Reactions: UndisputedGuy

al89nut

Senior Member
Apr 20, 2010
596
35
0
Southampton
If you are unlocked, it would seem not, but it seems if you use the motochopper method to get root, that doesn't work any longer. Some are reporting success with backing up their root, while others report failure

Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Well, I'm staying away from this update for sure now. I thought a few days ago that reports were wrong, but it seems to be as you say.
 

hgoldner

Senior Member
hi,

also installed this update. coming from cm10.1 with the 4.1 bootloader, it was rooted and had unlocked bootloader. then i installed the update via twrp 2.4.4.0, installed fine but then it won't boot at first, got stuck at the asus bootlogo. i did "wipe data" and it solved this issue. now it boots up fine. and i'am on the newest stock fw. but not rooted anymore. when tried to install a new twrp with fastboot i found out that "fastboot getvar all" brings up the info "bootloader unlocked:no". i read in another thread where people are having issues with using fastboot due to the installation of a wrong recovery, having the same output when doing "fastboot getvar all". now i am concerned that i wont be able to install any recovery, because bootloader seems locked again. i am now too afraid to just try it, because i fear getting bricked. anyone can clarify this or tell me if i am too cautious? or anyone who has the same issue?

edit: i read i another thread that it's normal fastboot puts out "bootloader unlocked:no"?
Once you've installed the update, you need a TWRP that ends in 4.2 (preferrably 2.6.0.0 but certainly no less than 2.4.4.0). Have you got that going on the unit? I'm wondering whether it's necessary to re-unlock the bootloader (in which case you need v8 of the unlocker; v7 won't work on the new bootloaders starting with 10.6.x.x.
 

paokaras45

Senior Member
Jan 23, 2009
207
16
38
Hi. After last update my bt mouse does not pair.
The tablet finds it but I click on it and nothing happens.
Does anyone else have problem with bt mouse or other bt devices???

Sent from my Nexus 4 using Tapatalk 2