yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Gear] big_pongo:
Um... my device and GEAR are NOT ROOTED also. ... I think you just missed some parts...
[Samsung Galaxy Gear] fOmey:
In that case its not possible. Your gear MUST BE ROOTED in order to modify the system partition.
[Samsung Galaxy Gear] acheney1990:
Getting Standard App Back

So does anyone have the APK for ChatON which came preinstalled?
[Galaxy S 4 Q&A, Help & Troubleshooting] i9apps:
When i try to flash stock 4.2 rom with odin i get "unsupported version"

Aby solution?
[Galaxy S 4 Q&A, Help & Troubleshooting] i9apps:
BUMP...Someone?
[Galaxy S 4 Q&A, Help & Troubleshooting] samersh72:
you meant that you flashed stock 4.3 and you can not downgrade to 4.2.2?

what is written in download mode?
[Galaxy S 4 Q&A, Help & Troubleshooting] i9apps:
Yea...its writing "unsupported version"
[Galaxy S 4 Q&A, Help & Troubleshooting] samersh72:
i guess you can not downgrade due to the 4.3 locked bootloader (like I9505 new firmwares)

did you try with odin 3.09?
[Galaxy S 4 Q&A, Help & Troubleshooting] superbegita:
Sadly it look l'ile you tôt the famous KNOX....you are not being autorhized to make modifications...

Bootloader us locked with récent firmwire on the 9505.It s the same for the 9500.

Me i have on problème on the rom Echoes.it had ben removed there us ni Knox despote the MJ5 modem
[Galaxy S 4 Q&A, Help & Troubleshooting] exclaimed:
Are you flashing a ROM that matches your CSC? If not try that, I had the same problem, I flashed the stock firmware that came with my phone and it all worked out.
[HTC One V] miths17:
when switching to the new ROM, is it require to flash mods like TURBO BOOST and CrossBreeder again??? or there is no need..curious to know....inconvenience regretted if this point already covered :)
[HTC One V] tonyryan:
If you need this MODs you must flash them again, bacause wipe is erasing everything
[Themer General Discussion] aerce:
Hi, I am wondering if it is possible to force the launcher into memory. Sometimes when I unlock my phone it jumps into Touchwiz instead of the default launcher which is themer. It also happens sometimes when I close games and it jumps right into Touchwiz, so I have to double tap home button to get into themer again. I am currently using Galaxy S4 so RAM should not be a problem, but I do not know why it is getting killed all the time.
[Themer General Discussion] Nilotpal12:
ro.HOME_APP_ADJ=1

Copy paste the above at the end of your build.prop file using root explorer which can be found

here:

system/build.prop
[JASJAR, XDA Exec, MDA Pro General] Morituri:
Hello,

Great forum. Just got my M5000 a day ago and it is already going back because of a duff battery!!

Anyway, does anyone here have a definitive list of what each CAB does and what needs to be run from the Extended_ROM after you do the soft reset hack?

Is there any benifit, or indeed can you, install the generic S/W for the JasJar?

Thanks in advance
[JASJAR, XDA Exec, MDA Pro General] Southern_Man:
Has anyone managed to dump the Orange rom and post it here yet, for the M5000. Had a good hunt about here but I haven't found anthing!
[JASJAR, XDA Exec, MDA Pro General] decebal:
no yet guys , not yet ...
[JASJAR, XDA Exec, MDA Pro General] Morituri:
OK, i'm going to bump my own thread because I only have 7 days to figure out if I want to keep the M5000 or not.

Does someone with a big brain know if flashing the M5000 with the latest ROM and radio version from I-Mate and then selectively applying the extended ROM CABS makes any difference to the M5000, i.e. do you get more usable memory, is it more stable, etc. or for that matter it can even be done?

Any help would be great as I am on a tight time scale here.

Cheers
[Captivate Q&A, Help & Troubleshooting] kalda01:
I had Slim 4.3 build 1.8 and tried to flash Semaphore Kernel 3.2.0sc.

After flashing the kernel phone started to boot loop.

Can't get into recovery or download mode using any known method.

Sometime I get the little charging icon or just a boot loop.

any help will be appreciated.
[Xperia Z Q&A, Help & Troubleshooting] wmiswm:
The google gmail app is starting to put ad in the mail tray. Is it possible to hide the ads?
[Xperia Z Q&A, Help & Troubleshooting] laceex:
????? :S Don't scare us

Ads in Gmail?

I hope Google will not start on their native apps.

If they do, I will go back to my W880i :S
[Xperia Z Q&A, Help & Troubleshooting] wmiswm:
Sorry, I finally find out that it is a mis-setting. No problem now. Thx anway.
[One (M7) Q&A, Help & Troubleshooting] knudsen81:
Hello

My htc one is s-off with supercid and locked bootloader, i run RUU for wwe 1.20 firmware, but now my phone is stuck with controlling header 7% why does it not work??
[One (M7) Q&A, Help & Troubleshooting] qzcgd:
Is your modelid supported by the RUU?
[One (M7) Q&A, Help & Troubleshooting] knudsen81:
I have supercid so i should flash all???
[One (M7) Q&A, Help & Troubleshooting] qzcgd:
Can you please copy/paste the results of "fastboot getvar all" ?

Just follow this guide. I think you may have to relock bootloader (using revone) before using the RUU
[One (M7) Q&A, Help & Troubleshooting] knudsen81:
here

C:\>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.54.0000

(bootloader) version-baseband: 4A.18.3263.15

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.07.1700.1

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: HT37SW901541

(bootloader) imei: 357864051186268

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 4291mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-94cf81a8fd

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.086s

But i have google edition on now, before was my main 1.24.401.8 and cid HTC__Y13

i try the ruu exe RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4

I just want to downgrade
[One (M7) Q&A, Help & Troubleshooting] knudsen81:
My bootloader is locked with use of revone
[One (M7) Q&A, Help & Troubleshooting] qzcgd:
What are the "modelid" listed inside the android-info.txt of your RUU?
[One (M7) Q&A, Help & Troubleshooting] knudsen81:
modelid: PN0710000

cidnum: HTC__001

cidnum: HTC__E11

cidnum: HTC__102

cidnum: HTC__203

cidnum: HTC__405

cidnum: HTC__Y13

cidnum: HTC__304

cidnum: HTC__032

cidnum: HTC__A07

cidnum: HTC__J15

cidnum: HTC__016

mainver: 1.20.401.1

btype:1

aareport:1

DelCache:1

hbootpreupdate:3
[One (M7) Q&A, Help & Troubleshooting] qzcgd:
For some reason SuperCID is not listed. That might be the issue.
[One (M7) Q&A, Help & Troubleshooting] knudsen81:
Yes i have see it, i try to change cid to htc__001 and see
[One (M7) Q&A, Help & Troubleshooting] knudsen81:
Thanks man now i got past it and my phone is updating
[Ubuntu Touch General] HyperEscape:
Hello,

Running i9250 on stock 4.2 android.

Want to try the Ubuntu stable build on it. I can see the Ubuntu Installation steps on Ubuntu website.

However just want to know what would be the way back to android. Would I be able to keep CWM recovery partition and restore an old nandroid backup. ?

Secondly is it possible to run Android and Ubuntu in a dual boot mode..

Thanks for your replies.
[Ubuntu Touch General] dermaze:
Hello,

at least for 2012 Sony Xperias (S, Acro S and ION) there exists a dual boot tool by [MENTION=834547]letama[/MENTION], which can be found here and is verified to run the Ubuntu OS as one of the two roms (or both, whatever sense that should make...).

Of course this specific minikernel will not help you directly, but maybe it'll point you in the right direction to continue your search. Maybe you can find out, whether a similar tool can be made / exists for your device in the thread mentioned.
[Ubuntu Touch General] qnc:
I installed the stable version on my I9250. I'm not sure about the dual boot as this was not my daily driver.

From my experience after installing I could not go back to a CWM ot TWRP back up.

I had to do a reinstall a fresh 4.2.2 and then re-root.

I tried to restore back up from TWRP, but for some reason I had issues with a complete restore.

it was no biggie for me, since it was not my daily driver, but I made sure to back up the data I had on it just in case.

My experience.
[Galaxy S 4 Q&A, Help & Troubleshooting] bunleab:
I have Galaxy S4 I9500 with the original firmware out of box is I9500XXUAMDK.

I want to ask can I flash official firmware region Asia. It has problem or not if we flash firmware another region?
[Galaxy S 4 Q&A, Help & Troubleshooting] Carl Blance:
Give it ago, but download the original firmware first incase it doesn't work out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DMF1977:
Why not copy anything that u want to keep to the external sd and or pc, and then format internal storage? Might help...
[Omni Q&A] dkflint723:
So I have followed the guides here http://docs.omnirom.org/Setting_Up_A_Compile_Environment and here http://docs.omnirom.org/Build_for_mako.

I have synced up everything and when I execute the cd ~/android/omni; . build/envsetup.sh; brunch mako command I do not get a .zip file created. Is there an extra step I need to do to have the .zip created so I can flash to my device?

Thank you all in advance.
[Omni Q&A] makkeonmies:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-10.2" />
<project name="omnirom/android_kernel_google_msm" path="kernel/google/msm" remote="github" revision="android-msm-mako-3.4-jb-mr2" />
<project name="omnirom/android_device_lge_mako" path="device/lge/mako" remote="github" revision="android-4.3" />
</manifest>

u add these to ~/android/omni/.repo/local_manifests/roomservice.xml

i believe this should get you a build, but u should w8 for someone more experienced to confirm those.

E: also remenber to sync after adding those lines

repo sync -j4
[Omni Q&A] Nburnes:
You made sure to have a local_manifest folder under ~/android/omni/.repo/ ?

Inside my local_manifest.xml (Or really whatever you want to name it .xml) is

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_broadcom.git" path="vendor/broadcom" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_nvidia.git" path="vendor/nvidia" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_elan.git" path="vendor/elan" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_invensense.git" path="vendor/invensense" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_widevine.git" path="vendor/widevine" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_nxp.git" path="vendor/nxp" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_asus.git" path="vendor/asus" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_imgtec.git" path="vendor/imgtec" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_samsung.git" path="vendor/samsung" remote="github" revision="cm-10.2" />
<project name="omnirom/android_device_asus_flo" path="device/asus/flo" remote="github" revision="android-4.3" />
<project name="omnirom/android_kernel_google_msm" path="kernel/google/msm" remote="github" revision="android-msm-mako-3.4-jb-mr2" />
<project name="omnirom/android_device_lge_mako" path="device/lge/mako" remote="github" revision="android-4.3" />
<project name="omnirom/android_kernel_lge_mako" path="kernel/lge/mako" remote="github" revision="android-4.3" />
</manifest>

TheMuppets repo is where CM team keeps their blobs for all devices they build for. (I have most of them because I build for quite a couple) You're going to need the lge one. Then the omnirom ones are device specific for mako and flo and then subsequently mako's kernel.

Using this I have made working builds for my N4.
[Omni Q&A] parker09:
These are the steps I do first to build (and get the same errors as OP)

parker@laptop:~$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 23618 100 23618 0 0 54252 0 --:--:-- --:--:-- --:--:-- 57604
parker@laptop:~$ chmod a+x ~/bin/repo
parker@laptop:~$ echo "export PATH=${PATH}:~/android/sdk/platform-tools/:~/bin" >> ~/.bashrc
parker@laptop:~$ export PATH=${PATH}:~/android/sdk/platform-tools/:~/bin
parker@laptop:~$ git config --global user.email "me@[B]EMAILREMOVED[/B]"
parker@laptop:~$ git config --global user.name "ejparker"
parker@laptop:~$ cd ~/android/omni
parker@laptop:~/android/omni$ repo init -u https://github.com/omnirom/android.git -b android-4.3
remote: Counting objects: 16, done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 12 (delta 4), reused 11 (delta 3)
Unpacking objects: 100% (12/12), done.
From https://github.com/omnirom/android
68adae3..4a32d1c android-4.3 -> origin/android-4.3

Your identity is: ejparker <me@[B]EMAILREMOVED[/B]>
If you want to change this, please re-run 'repo init' with --config-name

repo has been initialized in /home/parker/android/omni
parker@laptop:~/android/omni$

That seems to go all fine.

I then sync the repo and that goes well as far as I can tell

repo sync -j4

Does the fetching of the project and sync'ing the work tree and I get

Fetching projects: 100% (378/378), done.
Syncing work tree: 100% (378/378), done.

Which seems like its worked - so all good up to this point I'm guessing.

I then do the

cd ~/android/omni; . build/envsetup.sh; brunch mako

and then when it's finished I don't get a build.

(terminal output too many characters for XDA so put it in pastebin

http://pastebin.com/439iaqtm
​

-----

My local manifest is under: ~/android/.repo

Yeah I have in my local_manifest.xml

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-10.2" />
<project name="omnirom/android_kernel_google_msm" path="kernel/google/msm" remote="github" revision="android-msm-mako-3.4-jb-mr2" />
<project name="omnirom/android_device_lge_mako" path="device/lge/mako" remote="github" revision="android-4.3" />
</manifest>
[Omni Q&A] Nburnes:
You have the .repo folder in the wrong place

From your own terminal you have

parker@laptop:~/android/omni$

as your build location

But .repo in

~/android/.repo

It needs to be in

~/android/omni/.repo/

and then a local_manifests folder as I said. (The period means it is a hidden folder if you didn't know, so CTRL+H in your file manager to view/access it)
[Omni Q&A] Gnome:
try:

.build/envsetup.sh && lunch 16 && make otapackage
[Omni Q&A] parker09:
Ah okay.

I moved it, I'll try build it now.

Does that mean the Wiki article on docs.omnirom.org is wrong? http://docs.omnirom.org/Build_for_mako

mkdir -p ~/.repo/local_manifests/

shouldn't it be

mkdir -p ~/android/omni/.repo/local_manifests/
[Omni Q&A] Gnome:
It's not wrong, it means that you should be inside your source folder to do that command.

mkdir -p ~/.repo/local_manifests/
[Omni Q&A] Nburnes:
You also seem to have

<project name="omnirom/android_kernel_lge_mako" path="kernel/lge/mako" remote="github" revision="android-4.3" />

Missing from your manifest, else it won't actually pull (all) the mako kernel source.
[Omni Q&A] parker09:
Ah okay, I get you.

Ah thanks.

Doing another sync and I'll try again.
[Omni Q&A] caspian154:
Isn't wrong if you want the .repo folder in ~/android/omni? The ~ qualifies the command to start at the user's home directory. it doesn't matter what folder you are in when the command is executed. I agree that this is misleading.
[Omni Q&A] gyrene2083:
MOD please delete
[Omni Q&A] caspian154:
Correct - you would want to follow instructions for your specific phone. The previous posts mention adding binaries/blobs for the Nexus 4 specifically. Sorry I can't be more help than that.
[Omni Q&A] gyrene2083:
It was when I read that, that I totally realized it was specific to the Nexus 4. It's my own fault for reading while be up for 18 hours....lol. I suppose I'm going to have to try to figure this one out....but thanks for the answer.
[Omni Q&A] kldoc:
Actually, i did modify a bit omni's wiki toward mako's build, local_manifest isn't needed anymore for the kernel since roomservice got merged, it will get synced when you launch brunch. Themuppets should be declared in local_manifest.xml

Do not edit roomservice.xml, as it is generated by roomservice.
[Omni Q&A] Javier.D:
Hi, I'm trying to compile omni for this device, I'm in ubuntu 13.04 64 bits but, when I try to put this:

repo init -u https://github.com/omnirom/android.git -b android-4.3

It says me this error:

javierd@javierd-GE70-2OC-2OD-2OE:~/android/omni$ repo init -u https://github.com/omnirom/android.git -b android-4.3

/home/javierd/bin/repo: línea 1: error sintáctico cerca del elemento inesperado `newline'

/home/javierd/bin/repo: línea 1: `<!DOCTYPE html>'

javierd@javierd-GE70-2OC-2OD-2OE:~/android/omni$

Does somebody know how can I patch this error, it says me with all the roms, but i don't know why :,,(
[Omni Q&A] karamelos:
Hi delete ~/bin/repo

&

$curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$chmod a+x ~/bin/repo

If you have key error delete

~/.repoconfig
[Omni Q&A] Assis Brandão:
I'm with this error

target SharedLib: libril (/home/assis/android/omni/out/target/product/mako/obj/SHARED_LIBRARIES/libril_intermediates/LINKED/libril.so)
/home/assis/android/omni/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /home/assis/android/omni/out/target/product/mako/obj/SHARED_LIBRARIES/libril_intermediates/ril.o: file is empty
collect2: error: ld returned 1 exit status
make: ** [/home/assis/android/omni/out/target/product/mako/obj/SHARED_LIBRARIES/libril_intermediates/LINKED/libril.so] Erro 1
[Omni Q&A] Entropy512:
Please provide a full logcat as an attachment.

There is insufficient information to determine what went wrong, although my first guess based on the limited information provided is that something weird happened like you running out of hard drive space. It's rare for "file is empty" to occur instead of "file not found" unless there was an issue related to running out of disk space.
[Omni Q&A] Assis Brandão:
I'm in the final stage of compilation omnirom, this error occur in the penultimate and the last command:

cd ~/android/omni
repo sync -j16 -c --no-clone-bundle
. build/envsetup.sh
breakfast mako
export USE_CCACHE=1
brunch mako
make
[Omni Q&A] Assis Brandão:
I got the logcat (attached) and below the code I use to build:

mkdir -p ~/bin
mkdir -p ~/android/omni
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
echo "export PATH=~/bin:$PATH" >> ~/.bashrc
git config --global user.email axbrandao@gmail.com && git config --global user.name axbrandao
cd ~/android/omni
repo init -u https://github.com/omnirom/android.git -b android-5.0
repo sync -j16
echo "export USE_CCACHE=1" >> ~/.bashrc
~/android/omni/prebuilts/misc/linux-x86/ccache/ccache -M 25G
cd ~/android/omni
repo sync -j16
. build/envsetup.sh && breakfast mako
export USE_CCACHE=1
brunch mako
[Omni Q&A] zelendel:
Gotta do the breakfast command first to get the kernel. Also not sure with omni but you will also have to get the binaries for the n4 and install them first if omni doesn't have them already.
[Omni Q&A] Assis Brandão:
How to binary I did the downloading, extracting and moving with the commands:

https://developers.google.com/android/nexus/drivers#makoLRX22C

cp -R vendor ~/android/omni
# fix the makefile name - not sure why omni expects the file to be mako-vendor.mk
cd ~/android/omni/vendor/lge/mako
cp device-vendor.mk mako-vendor.mk

what would be the small command lunch?
[Omni Q&A] Assis Brandão:
found the fault, trouble in the cache of previous failures due to the following command to try to use files already created, but empty.

echo "export USE_CCACHE=1" >> ~/.bashrc
~/android/omni/prebuilts/misc/linux-x86/ccache/ccache -M 25G
export USE_CCACHE=1

the site has the warning

*Only to use after initial build has been complete
[Omni Q&A] Assis Brandão:
Solved problems, the error was happening because I used the command "export USE_CCACHE=1" and as the first compilation gave error, the cache was empty or corrupted. I deleted all the "out" folder and restarted
[Nexus 7 Q&A, Help & Troubleshooting] halfamind:
Device: Nexus 7 (2012) WIFI only

After 4.3 update device started locking up and had to repeatedly long-press power to reboot. Factory defaut fixed first time, Second time (because it started happening again) could not recover from factory default. boot.img will not install and returns a (remote: FileWriteFailed) error.

I've tried multiple cables, PCs, and toolkits with no luck.

I can load bootloaders without issue.

I can format and load system, userdata, recovery (have loaded stock, TWRP, CWM recoveries) all appear to load without issue and work fine but haven't been able to fix this issue.

Once the boot.img flash is attempted, the device locks up hard and a long-press of power is needed to bring it back.

I can boot to Google screen with (Start, Power off, Recovery mode, Restart bootloader options) or directly to bootloader without issue.

First tried restoring 4.3 factory, but have since been trying 4.2.2 factory using Nexus Root Toolkit, Nexus 7 Toolkit, and a lot of SDK command line of fastboot commands. I can run ADB commands if I first get into recovery.

Is there a option I can tickle or something else anyone knows I can try? I'm beginning to think the boot sector of the flash is defective (if this makes sense).

Here's an example of a fastboot update. It hasn't mattered the method, the outcome is always identical. It fails at boot.img flash write failure.

>fastboot devices

015d490651281e0e fastboot

>fastboot erase boot

erasing 'boot'...

OKAY [ 1.186s]

finished. total time: 1.186s

>fastboot erase cache

******** Did you mean to fastboot format this partition?

erasing 'cache'...

OKAY [ 0.998s]

finished. total time: 0.998s

>fastboot erase recovery

erasing 'recovery'...

OKAY [ 0.796s]

finished. total time: 0.796s

>fastboot erase userdata

******** Did you mean to fastboot format this partition?

erasing 'userdata'...

OKAY [ 4.649s]

finished. total time: 4.649s

>fastboot flash bootloader bootloader-grouper-4.18.img

sending 'bootloader' (2096 KB)...

OKAY [ 0.312s]

writing 'bootloader'...

OKAY [ 9.875s]

finished. total time: 10.202s

>fastboot reboot-bootloader

rebooting into bootloader...

OKAY [ 0.031s]

finished. total time: 0.031s

>fastboot -w update image-nakasi-jdq39.zip

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: 4.18

Baseband Version.....: N/A

Serial Number........: 015d490651281e0e

--------------------------------------------

checking product...

OKAY [ 0.031s]

checking version-bootloader...

OKAY [ 0.016s]

sending 'boot' (4944 KB)...

OKAY [ 0.686s]

writing 'boot'...

FAILED (remote: (FileWriteFailed))

finished. total time: 5.210s

>
[Nexus 7 Q&A, Help & Troubleshooting] halfamind:
This issue has been resolved. The Nexus 7 was returned to Asus support and the motherboard was replaced under warranty.