Dont panic Just use the NRT http://xdaforums.com/showthread.php?t=2015467 and select "back to stock" with the bricked option.
I have tried this, it doesnt help
Last edited:
Dont panic Just use the NRT http://xdaforums.com/showthread.php?t=2015467 and select "back to stock" with the bricked option.
Can u boot into fastboot mode or even into recovery? Does your tablet react somehow when u press the power button?
Ones you are in fastboot verify the connection viaYeah i can access fastboot but not recovery. It bootloops on "google", i dont see the X logo.
fastboot flash recovery openrecovery-twrp-2.3.2.1-manta.img
fastboot reboot-bootloader
Started working on the 4.2.2 update... hopefully will get it done this week...
Oh... hell yea!Started working on the 4.2.2 update... hopefully will get it done this week...
Started working on the 4.2.2 update... hopefully will get it done this week...
Started working on the 4.2.2 update... hopefully will get it done this week...
Two bugs that I have found
1. Switch time format to 24 and set time to something which contains a zero, eg 07:00. Turn screen of and on again to get into screen lock window. Now the last digit of the time is cut at the half. Dont know if this is caused by your rom.
2. Everytime I plug-in my keyboard any app that is open right now will crash or do some kind of reload.
Well, 4.2.2 is a considerably big change... way more than I expected... I have to manually port all my changes
If I can help in any way, please let me (us) know. I would gladly "beta" test. :thumbup:
Sent from my Nexus 10 using Tapatalk HD
Well, 4.2.2 is a considerably big change... way more than I expected... I have to manually port all my changes
@freshlysqueezed & @havi007, I'll share a few iterative build with you guys... slowing building up the entire feature set...
1. Has been discussed before. This is the AOSP lock clock widget. Just remove it and add the clock widget to get the one which works with 24 hrs...
2. Will look into it...
Which kernel do you use?Well,the keyboard issue is not ROM-specific.I face it everytime even on my stock rooted Nexus 10.