yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Android Development] piit79:
Got my Nexus 10 this morning.

Initially the touch version seemed to be working but when I clicked "Mounts and storage", it displayed the menu for a few seconds and then the tablet rebooted.

Now it won't boot :( Gets stuck on the Nexus logo. Guess it's not as safe as it seemed!
[Nexus 10 Android Development] The-Kevster:
Did you flash the recovery or just boot it with the fastboot boot recovery /path/to/<recovery>.img command?
[Nexus 10 Android Development] shimp208:
Like Kevster said did you just boot from it using fastboot or did you flash it using fastboot. Either way I appreciate the feedback, sounds like I have to try and fix the mount points.
[Nexus 10 Android Development] shimp208:
Edit: Can you provide any error messages you get or try connecting your tablet to the computer and use ADB to get a locate output
[Nexus 10 Android Development] piit79:
I just booted recovery using the command above... Strange.

Anyway, all is well after re-flashing factory image.

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

Further to my reply above - CWM did show 4-5 essages about "Cannot mount <path to what looked like a file>"

Sorry I didn't write it down... Stupid me:)

Also, after it wouldn't boot I was lazy to debug so I didn't try attaching to adb logcat. I just wanted to play with my new toy:)
[Nexus 10 Android Development] shimp208:
I understand we all want to play when we get new things ;). Again thank you for testing, like I said sounds like I need to fix the mount points.
[Nexus 10 Android Development] piit79:
Not sure if it is of any use but this is what "mount" shows in console:

/dev/block/platform/dw_mmc.0/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/efs /factory ext4 ro,nosuid,nodev,noatime,data=ordered 0 0

And

ls -l /dev/block/platform/dw_mmc.0/by-name/

lrwxrwxrwx root root 2012-11-15 09:37 boot -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-11-15 09:37 cache -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-11-15 09:37 efs -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-11-15 09:37 metadata -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-11-15 09:37 misc -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-11-15 09:37 param -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-11-15 09:37 recovery -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-11-15 09:37 system -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-11-15 09:37 userdata -> /dev/block/mmcblk0p9
[Nexus 10 Android Development] shimp208:
Thank you very much for providing this information :highfive:! I was able to use this information to rebuild the recovery images (Touch and Non-Touch Versions) and fix the recovery.fstab mount points, they ones that were orginally generated in the first ones I ran through clockwork builder were wrong which was what caused your tablet to reboot when selecting the mounts and storage option.
[Nexus 10 Android Development] snunez:
Just received this good news...

Scheduled For Early Delivery On:Friday, 11/16/2012, By End of Day

Originally Scheduled For Delivery On:Monday, 11/19/2012, By End of Day

This has never happened with anything ive ever ordered before lol

i mean seriously and i didn't have to pay more to get it early? Pure awesomeness :)

I will be trying this out as soon as i get my nexus in tomorrow. Will let you know if i run into any issues.
[Nexus 10 Android Development] mbirth:
In the non-touch-version (which I prefer), I was unable to access the "Apply zip from sdcard" menu. After selecting "Advanced Options", the N10 rebooted.

The touch version showed "Unable to mount /sdcard" when trying to access "Apply zip from sdcard" and rebooted 10-20 seconds after that.
[Nexus 10 Android Development] The-Kevster:
No luck here either.

I'm running

adb boot D:\recovery-clockwork-touch-unofficial-6.0.1.5-mantaray.img

(this doesn't break the device or cause any future issues BTW!)

It rebooted into recovery but reboots on its own 10-20 seconds later.

Also adds a "Nexus 10" device to device manager but non of the drivers I have work. I have the SDK drivers and samsung drivers for mobile phones.

I need to root this device already :D
[Nexus 10 Android Development] shimp208:
I suspect that root is going to be needed to fix the problems as I'm guessing it's encountering permission problems when accessing and manipulating files and directories necessary for recovery to perform it's various functions.
[Nexus 10 Android Development] alias_neo:
I was wondering what the deal is, cause I was thinking that if insecure adbd was working and root is fine from the recovery, I could adb shell, manually mount system and push the su binary over to root it.

If I can't get root shell there's no point unlocking (or rather, the wiping part) right now.
[Nexus 10 Android Development] gruppler:
Can you provide a mirror for the recovery images? Google Drive keeps getting stuck in a redirect loop when I try to download either of them.
[Nexus 10 Android Development] vmpn:
My 32GB model also reboots after 10-20 seconds. adb logcat command did not seem to work. Got error:

/sbin/sh: exec: line 1: logcat: not found

here is a dump of dmsg: http://pastebin.com/u68X48X5
[Nexus 10 Android Development] jarnow94:
My tablet also restarts itself after twenty or so seconds in recovery; I have the 16 gig model.
[Nexus 10 Android Development] impulse101:
So should I not bother unlocking now and just wait for a root solution? I wanted to unlock it now so I don't have to wipe everything by unlocking a few days later
[Nexus 10 Android Development] markus4000:
Hey there,

I didnt quite get to the CWM part yet :(

I tried to unlock my bootloader with "fastboot oem unlock" and select "yes" on the device, but now it shows forever the nexus boot logo.

Have I done something wrong? And how can I fix this?

When I try to go into "Recovery Mode" in the bootloader the broken Android logo shows up...

I have just bricked my new Nexus, please help :fingers-crossed:

EDIT:

I already tried to lock and then unlock the bootloader again to go a second time through the steps, but it didnt help :(

EDIT2:

I will try to flash the android factory image with fastoot -w update <factoryimage> in a couple of minutes... I hope this will fix it.

EDIT3:

sitting in front of the nexus boot logo now for 5 minutes.... whats wrong with my device?

LAST EDIT:

OK I found out that the "broken android" is normal in stock recovery (sry for that...) and I wiped all (factory reset) within that and now its booting again.

Dont know if this will be helpful for others. Do with this post what you want :P
[Nexus 10 Android Development] byock1:
It should, I just finished doing that to mine and it came back.
[Nexus 10 Android Development] shimp208:
You can still unlock the bootloader now that way you don't have to loose a lot of stuff latter (Or backup a lot of stuff) when you unlock the bootloader and it whipes everything.
[Nexus 10 Android Development] shimp208:
For the factory image put the device in fastboot mode and then double click the flash-all.bat included in the factory image this should reflash things back to stock for you.
[Nexus 10 Android Development] kidgoo:
I got root using the method below. CWMR is still rebooting for me, so this requires some speed. I typed out the commands before entering CWMR.

1. Download the SuperSU zip from http://xdaforums.com/showthread.php?t=1538053

2. Download the touch version of CWMR from the first post of this current thread thread.

3. Connect the N10 to your computer.

4. Boot CWMR using fastboot. Do the next steps quickly.

5. Touch "Install from sideload" in CWMR.

6. Sideload the SuperSU zip file you downloaded in step 1 by saying: ./adb sideload /path/to/CWM-SuperSU-v0.94.zip

7. It will install.

8. Reboot to system from CWMR. (This part is important to clear the boot mode flags if you're stuck in a recovery mode bootloop.)

9. Enjoy.
[Nexus 10 Android Development] WannaB101:
Awesome?!

Can anyone confirm this? :D

A rooted nexus 10 = AMAZING.
[Nexus 10 Android Development] kidgoo:
I updated the post to cut out a few (potentially dangerous) steps. You shouldn't directly flash CWMR like I said in step 5.
[Nexus 10 Android Development] shimp208:
I would edit the wording to read "Boot CWMR using fastboot" so there is no potential confusion or misunderstanding of your directions.
[Nexus 10 Android Development] The-Kevster:
Yes....it works!!! :D

I rebooted to fastboot, booted the touch cwm (didn't flash it), quickly pressed sideload, ran adb sideload D:\CWM-SuperSU-v0.98, lastly adb reboot once the install had finished.
[Nexus 10 Android Development] kidgoo:
Good idea. Done.
[Nexus 10 Android Development] specimen12:
This happened to me as well, I also had to flash a factory image.

That sounds hilarious. I'm tempted to give it a go, but a little concerned. How likely is cmw to reboot while side loading su? And just to help my understanding: After flashing cmw and rebooting, does it return to stock recovery?
[Nexus 10 Android Development] shimp208:
If you don't do it quickly enough it will reboot on you while side loading su. And you should not be flashing CWM you should only boot it using fastboot don't flash it, if you only booted it then when you reboot it returns to stock recovery if you flashed it when you reboot it will still be installed.
[Nexus 10 Android Development] vmpn:
The following solution of resetting data from recovery worked for me without flashing: http://xdaforums.com/showpost.php?p=34188192&postcount=32
[Nexus 10 Android Development] specimen12:
Ahh right, thanks for clearing that up for me. If there's a 20-30 second window, how long does su usually take to run? I'd love to give this a go, but a reboot part way through the script sounds pretty hairy.

Thanks for all your hard work!
[Nexus 10 Android Development] shimp208:
Super SU and the binary it installs (Su binary) shouldn't take more then 10 seconds, the zip you would flash can be found here CWM-SuperSU-v0.98.zip.
[Nexus 10 Android Development] Monk33y:
Is this recovery different than the one Koush posted here for the n10??:

http://clockworkmod.com/rommanager
[Nexus 10 Android Development] billbradford:
I've got the SDK updated, I can see the N10 in "fastboot devices" and "adb devices", I can reboot from ADB to bootloader, I can boot from any of various CWM/CWMT images, but once I boot into CWM the N10 shows up in Device Manager as "manta" and I can't find any USB drivers that will work with that to give me ADB (in order to do "adb sideload") once CWM is running...

I've done this plenty of times with other devices (N1, GNex, etc) but this has me stumped.

Edit: resolved. Downloaded the CWM zip file to the "sdcard" (Download directory), booted Koush's official touch recovery, and did:

Mounts and Storage -> Mount /sdcard -> Back -> Install Zip from sdcard -> choose zip from sdcard -> 0 -> download -> zipfile -> yes -> back -> reboot

*whew* :D
[Nexus 10 Android Development] shimp208:
Yes I will update post, with the official release thanks!
[Nexus 10 Android Development] maxwintrobe:
SMART!!!!!!!

had that same "manta" crap in Win7, did like you said, copied CWM-SuperSU-v0.98.zip to /Download, got it flashed a split second before it auto-rebooted, never had chance to hit reboot myself, but upon reboot ... there it is, rooted N10.

awesome dude!!!!!
[Nexus 10 Android Development] damien667:
Fix for reboots

I posted a fix for random reboots on the other thread, let me know if you guys have any questions :victory:

http://xdaforums.com/showpost.php?p=34256732
[Nexus 10 Android Development] Egooktamuck:
I need the Stock-Recovery - Got anyone a link?
[Nexus 10 Android Development] joeski27:
Good to go, thanks
[Nexus 10 Android Development] shimp208:
Here you are my friend https://docs.google.com/open?id=0B1S0LCuXCnnmZmF1WEx0b0syM0U :).
[Nexus 10 Android Development] mskip:
Obsolete Thread.

Thread closed.

Mark.
[Samsung Galaxy Nexus] carberoz:
hello everybody..

we know that galaxy nexus super amoled screen easily burned in

especially in status and navigation bar..

so what do you do to prevent your galaxy nexus screen burned in?

share ur trick here please.. thanks :D
[Samsung Galaxy Nexus] bioan:
LMT + expanded desktop.
[Samsung Galaxy Nexus] bmg1001:
No real way to prevent it, but you can fix it easily by using Screen Diagnostic from the Play Store.
[Samsung Galaxy Nexus] Smokeey:
Its not a burn in, but a ghosted image. I watch YouTube videos and keep auto-rotation on. However, when I replaced my last Nexus (because of ghosting) this Nexus hasn't had the issue and I've had it longer. It may just be an actual display issue. If you get the issue you can bug Samsung/Verizon/Sprint and they'll probably send you a replacement.
[Samsung Galaxy Nexus] MikLSP:
Don't use a high brightness setting.
[Samsung Galaxy Nexus] carberoz:
i use that app but it didnt fix my nexus..
[Samsung Galaxy Nexus] right7left:
LMT + pa
[Samsung Galaxy Nexus] chronophase1:
The only area where I have any type of "ghosting" is where the status bar sits, and even that isn't noticeable unless the brightness is cranked up to full on a white screen. I don't really worry about it. My Nexus S has it where the status bar sits and I haven't had the issue anywhere else on the screen.
[Samsung Galaxy Nexus] MS.:
I do... I do nothing. I just use my phone the way i like and have no issues. It's been nearly year and screen is absolutely fine.
[Samsung Galaxy Nexus] arzbhatia:
First of all, if you got warranty, go get it replaced. They might do it! I broke my screen and I bought another one officially and it's PERFECT. ABSOLUTELY perfect! So try that first!

If that doesn't help, try playing with some color values and gamma options - This helped my previous screen from ghosting and all.
[Samsung Galaxy Nexus] carberoz:
isnt all super amoled device suffer that?

or it just defected one?

is anybody using galay nexus for 8 months++ without getting screen ghost?
[Samsung Galaxy Nexus] arzbhatia:
Some screens really are perfect :)

It's a defected one my man.
[Samsung Galaxy Nexus] schmoove:
On amoled screens the pixels 'fade out' over time. The pixels basically get less intense the more you use them. Because the notification bar and the soft buttons on a Galaxy nexus have a black background these pixels are hardly used at all. The rest of the screen is. So the rest of the pixels wear out faster than those in the notification bar and the soft buttons. That is how the ghosting forms. So a new screen should have zero problems, but after a year or less, the effects can already be seen.

I had this with my Nexus One and now with my Galaxy Nexus, although the ghosting was far worse on the Nexus One. Next time no more amoled for me.
[T-Mobile myTouch 4G Slide] Thurge:
Okay, I bought a used MT4GS from a fairly reputable phone reseller called CPR (cell phone repair.) I bought it back in March or April of this year. I immediately rooted and installed a custom rom and CWM. A few months ago I upgraded my rom to CM9 and about a month ago I began having problems. The isses were minor at first, the hardware buttons on the outside of the phone would stop working but I could open the phone and use the ones on the keyboard. Then in the past two weeks all of the buttons would stop working. I thought it was a hardware problem so today I dropped it off at CPR and they took it apart and tested all of the buttons. According to them all the buttons tested out fine. So I have a phone that the only thing that works is the touch screen. Here is the odd thing. If I hold the volume down while booting I get the fastboot menu and can navigate it using the volume keys. If I go into recovery mode none of the buttons work same as in the phone. So either this is a software problem or a systemboard problem. Because my power and volume buttons work on the recovery menu I'm inclined to believe it's a software problem but I'm a little lost on how to fix it. I just tried to boot the phone again and it's now stuck on the boot animation and does nothing. Please help!!!
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
I was curious if you tried a reinstall before your keys went completely berserk...but no matter now. Sometimes a person will get a bad download though and you can get some WEIRD results from them.

Anyway....this is how I answered on the CM9 Thread if you hadn't seen it......

I've never heard of a ROM brickng a phone especially gradually but I suppose anything is possible. If what you're wanting to do is to return to stock & just kinda "start over" then just go to This Thread and scroll down to the files labeled as "Return to Stock" & download the correct file according to your installed software. Then you can just place it in the root directory of your SD card and reboot into Hboot. PG59IMG files are designed to run from your bootloader and you just answer the few questions it asks as it does.
[T-Mobile myTouch 4G Slide] Thurge:
Yeah I actually did that last night. Got to watch the intro animation from HTC/T-Mobile etc. Still no buttons. I'm guessing that the system board has a bad chip since the buttons tested out okay. That is more consistent with the gradual failure than a software bug. Now if there were a rom made for a phone without buttons then I'd be in good shape. Luckily I found an identical phone on Craigslist for $85 which I feel is reasonable for a discontinued phone. Does anybody have recommendations on QWERTY Android phones for T-Mobile that are better than the MT4GS?
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
Someone mentioned that Samsung is coming out with one soon but I can't remember the name for squat.
[T-Mobile myTouch 4G Slide] Riyal:
If it's for T-Mobile then I suggest the Samsung Relay 4G. Else better wait for Samsung Stratosphere 2 fior Verizon if you might consider changing networks for the sake of a better phone.
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
THAAAAT'S the one! Samsung Relay 4G. Thank you kind sir!:good:
[T-Mobile myTouch 4G Slide] blackknightavalon:
Samsung took over for HTC, who took over for crApple.
[T-Mobile myTouch 4G Slide] Riyal:
Samsung also.
[T-Mobile myTouch 4G Slide] onebornoflight:
First off let me say I'm sorry about the death of your MT4GS - mine died over a month ago and I'm still in mourning. However, the Relay is a nice little device. I don't want to be accused of attempting to recruit people again, but at the risk of saying so it is an upgrade from the HTC product in MOST ways - some people don't like the screen as much and the camera is definitely inferior. However, it's a nice device. I'm happy with it honestly. TouchWIZ takes some getting used to but since HTC didn't give us ICS, even ICSense... and Samsung has ICS on here with JB to come... I'm satisfied. If you are still curious we have a thread in the G2/Desire forum that we are using until XDA gives us a dedicated forum.
[T-Mobile, Samsung Galaxy SIII] rickm8384:
So I don't think this was asked yet but if it was, forgive me. Is there a way to get the split screen in the messaging app like I had on my S2? I notice that the Note 2 has the split messaging ability. Why not S3?
[T-Mobile, Samsung Galaxy SIII] Android_Monsters:
how did you used to do it on the s2. Never did that with my Hercules.

Paranoid Android and the note 2 port probably do that, however.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I think dj just released a experimental build, x4, that may do this
[T-Mobile, Samsung Galaxy SIII] thran8:
Hey Everyone

Not sure what is going on, but my SG3 always shows a red led on, if a notification light comes on it just changes to that color and once I look at it or clear it , it goes back to red.

Has anyone had this issue?
[T-Mobile, Samsung Galaxy SIII] thran8:
i think i may have found a solution after some more research
[T-Mobile, Samsung Galaxy SIII] thran8:
ok nvm my solution didnt work

Even when i turn my phone off the led is still on....
[T-Mobile, Samsung Galaxy SIII] mattedwards2686:
doing a factory reset should resolve it..
[T-Mobile, Samsung Galaxy SIII] thran8:
going to try that now , i hope it works
[T-Mobile, Samsung Galaxy SIII] thran8:
Arg i just reset everything and the red led light is still on....
[T-Mobile, Samsung Galaxy SIII] thran8:
Super interesting when i charge my phone the red led light turns off, and there is nothing (thats including i turned off every display notification led light battery and apps) but when i unplug it from the charger it goes back to red.....
[T-Mobile, Samsung Galaxy SIII] thran8:
also the color is a very faint red not a bright red.... tried light flow and it still didnt change it
[T-Mobile, Samsung Galaxy SIII] thran8:
The last observation that makes me believe this is just a hardware problem at this point, if i turn off the phone, the led is still red, when i take out the battery it slowly dims, as soon as i put the battery back in it lights up red again....
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Try flashing the syock or root66 fw via odin.

http://xdaforums.com/showthread.php?t=1949687
[T-Mobile, Samsung Galaxy SIII] mattedwards2686:
Sounds like hardware, if you Odin'ed back to stock and did a factory reset/cleared cache. Make sure your counter isnt tripped, flash stock, and return to store. They should replace it for free, as long as there is no water damage or a tripped counter;)
[T-Mobile, Samsung Galaxy SIII] thran8:
Yup looks like thats what i am going to do, do i have to go through samsung or just take it to tmobile?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you got it at a T-Mobile store, take it there. Otherwise, call customer care for a return/exchange. Be warned, they will probably try to give you a refurb!

Before you Odin back to stock, download

Triangle Away

and run it to make sure your flash counter is at zero! Then flash the stock FW with Odin. (Triangle Away requires root)
[T-Mobile, Samsung Galaxy SIII] thran8:
Perfect

Thank you very much for the info and the help, ill read up on everything and start this whole process tomm
[T-Mobile, Samsung Galaxy SIII] kulo604:
worked

worked for me
[Sprint HTC EVO 4G LTE] jejb:
I've had my phone for like 3 months. I did RegawMOD unlocker, S-On, root after about a week. I know that at first I could get to TWRP via the power off, hold down the volume down key and press the power button. I didn't do much else with playing with stuff after that. Just being rooted so I could wifi tether was what I was after. But the above process does not work any more to get into TWRP/bootloader. I've tried it dozens of times the last couple of days as I was doing the Team Unlimited s-off (which worked really well). I have to go through Goo Manager to get there.

The volume key works normally otherwise, as does the power button. I can scroll through bootmanager with it, turn the volume up and down, etc. I was thinking it was just something to do with RegawMOD, although I know it worked a few times after I did that mod. So I made sure to test it at different stages while doing the s-off since I had to relock and flash the original RUU. No joy.

Is it most likely a busted phone, or has anyone heard of this one?
[Sprint HTC EVO 4G LTE] drob311:
Make sure fastboot is unchecked in your power options.

Sent from my EVO using Xparent Blue Tapatalk 2
[Sprint HTC EVO 4G LTE] jejb:
Thank you so much, Drob! That was it. Working perfectly now, and I do remember checking that box on a while back. So that explains it.