yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Will do. Glad you like it dude. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kinked:
There should be an option in the Nav bar settings. menu visibility> disabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
You're right about all that, it turns out my real problem is getting my PC to recognize the phone. I have the latest drivers installed and its a brand new ASUS like literally the only thing I've done on it is root my phone lol(because I have a tablet that I do most of my surfing on.) I know ADB enough to set it up to work to root the phone to install clockwork mod which should be enough to grab a logcat. I have uninstalled and reinstalled the i747 samsung mobile drivers multiple times from several different downloads of the drivers. When I plug my phone in and it says installing device drivers I get "No Driver Found" and my pc won't recognize my phone to get ADB to work which is why I can't grab a logcat. But toggling circleMOD did in fact toggle the problem for a little bit but then it just didn't work and toggling it never worked again.

EDIT: Forget the problem of the PC recognizing the phone. I finally after spending all morning trying to get these drivers installed correctly got my PC to recognize my phone, which it does as a MTP device. When I try to get a logcat it says something about daemon started sucessfully then waiting for device and nothing happens. I think it's because I was running your last ICS build and didn't have the 4.0 android-sdk drivers installed so I'm going to flash to 8/23 and see if I can logcat since I have them installed for 4.1 when I was troubleshooting this yesterday.

EDIT2: Okay so I flashed to 8/23 I have the android sdk drivers installed for 4.1, my pc recognizes my device, but I cannot get ADB to recognize my device. I have USB Debuging enabled, but the PC is recognizing it as a MTP device, I'm pretty sure that's why..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
I'm at work now and I have a few things to try on my laptop once I get home to get adb to recognize my device...but that is what you need from me right task? A log cat?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
log-cat would've been nice the 1st, 2nd, 3rd, or maybe 4th time you posted it bro. but i think we're now on the 6th, 7th, or 8th report with no info by now. at this point. im done looking into the issue. it works fine for me. sorry dude. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deadlyrhythm:
Im just wondering if when you go into the *#*#4636#*#* menu and change you network type if its supposed to save after a reboot or not.

For me it doesnt save but I have a feeling its not supposed to.

This rom just keeps getting better and now the Canadians can join in on the fun!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
I'll give you a logcat once I get ADB to recognize my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
you can download terminal emulator from the market.... open it...

type:

su

logcat > /sdcard/problem.txt

home + vol down to end the logcat, it'll save to the root of your sd
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
It doesn't stick yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eLDuRo212:
Question

Task everytime I reboot my device I have to go into the Developer Options to Disable HW Overlays are you experiencing this problem as well? Also, every time I plugin my headphones the vibration option is enabled is there a way to disable this? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Thank you ill try that. I also wanna figure out though why ADB doesn't recognize my phone when it did originally when I rooted and installed cwm without triggering the flash counter.

Btw task I apologize for all the questions without the appropriate information to help I just wasn't able to grab a log cat and I was doing my best to explain what could cause it. It seems with 8/23 it didn't work at all after a fresh flash without doing anything but signing into Gmail at setup. My next post asking for help will have a log at and I hope someone can help me because google voice/now is one of the main and coolest features of JB and its weird that its only happening to me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) Disable HW overlay is not supposed to stick through reboot. thats how its supposed to be.

2.) You really need to look through Rom Control/Sound. You would have found the Headphones plugged in section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eLDuRo212:
No Action

I just went into the Headphones plugged in action and it is on "No Action" so I am not sure why is going into Vibrate Mode when I plug in my headphones
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm not sure either. Have you even rebooted to see if it took?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eLDuRo212:
Rebooted

OK I just rebooted my device, plugged in my headphones and now it took the right settings :D

---------- Post added at 07:47 PM ---------- Previous post was at 07:42 PM ----------

One last question today I called a few of my friends on my device and for some reason on my end I hear the person very low, I tried putting the volume up with no luck and I had perfect signal in my area, I went back to stock to verify this and I can hear everybody loud
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Hey dude. Just a word of advice for the future because I've noticed that you do post a lot about the simple things. Just slow down a little. When trying to find a feature or setting, make sure you familiarize yourself with all the ROM control settings and also the basic settings. And whenever you choose a setting and it doesn't seem to work or stick. Reboot before posting your question about it to see if it works first. Also. As a common courtesy. When someone takes the time to help you. Hit the thanks button to show your appreciation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eLDuRo212:
OK No Problem

Thanks for the advice :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Whatever you do with stock ROM or how stock ROM performs has nothing to do with aokp. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
uninstall the drivers and hook the phone up, let windows update find the drivers for you...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Windows won't find the drivers. It did originally when I rooted the phone and adb worked and everything, then I try to grab a logcat and I start having these problems. First my pc wouldn't recognize my phone at all. It would say installing drivers but it wouldn't install them, it would say drivers not found. I downloaded the drivers from the Samsung website(yes for the i747) and installed and it still wouldn't recognize the phone. I tried multiple cables and USB ports btw. I installed the i747 drivers then went into device manager(I'm running Windows 7 64) and seen the drivers there with a yellow triangle. I followed the trouble shooting steps and updated the drivers manually using the download I got from the website. Now the computer recognizes my phone, but as a MTP device. I can view and r/w to my internal and external storage, but ADB cannot recognize my device. I have the correct stuff installed in the SDK-Manager for 4.0,4.3 and 4.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Have you enabled usb debugging?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Maybe you should start a thread in Q&A and widen the field of people contributing towards a solution for the ADB issue? And did you try the suggestion posted a bit ago to just use a terminal app on the phone to run the logcat? I've done that in the past and just Dropboxed it to myself, which would let you do the "Task specific" part of this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Here is a logcat I used via the termulator method posted above, thanks. I started the logcat, then hit the home button, did a voice search, it cut me off after a few seconds, then I went to recent apps to try to stop the logcat, but the vol down + home button didn't work, and I couldn't get it to stop, eventually after I kept trying to stop it I just closed the window. For the hell of it I checked my sdcard and this file was there. So it might be longer and includes me recreating the problem as well as me trying to stop the logcat. I tried reading it but have no idea what I'm looking at, I'm sure you do.

https://dl.dropbox.com/u/49788705/prolebem.txt
[Galaxy S III Q&A, (US Carriers)] ironlood:
looking at the forums I noticed 2 development categories, Original Android development and Android development

What is the difference?
[Galaxy S III Q&A, (US Carriers)] Success100:
Straight from the original development thread:

"This is meant for the newest roms ie: aosp, cm, aokp source builds. Kernels from source also. If you are porting a rom, it belongs in the normal development section, not here. Stock, I repeat stock roms; ones from Samsung themselves as in new versions; can go here.

Also for this section. Roms an kernels that bring forth something revolutionary that other roms do not have."
[Galaxy S III Q&A, (US Carriers)] ironlood:
Just to Clarify...

android development means like stock roms and original android dev is like the custom modded roms
[Galaxy S III Q&A, (US Carriers)] EndlessDissent:
I think ports, like LewaOS, MIUI, DianXin, etc. also go in the normal development section.
[Sony Xperia S, Acro S, Ion] killerskincanoe:
Had purchased previously on my inspire and played on my Flyer... worked great.

had no problems downloading from the market. installed fine. opening i come to a black screen with loading bar. which goes to about half way... and stops.... i've uninstalled re-instaleld.. rebooted.. no dice... anyone else confirm the same?
[Desire Q&A, Help & Troubleshooting] sssimo96:
Hello guys. When I flashed the Sandvold latest build I get FC on selecting the input method. So I had to delete the Latin_IME.apk from /system/ and installed 3rd party keyboard. How can I solve that as I really love the nativa ICS keyboard?
[Desire Q&A, Help & Troubleshooting] maerte:
I think exactly this issue was discussed in the sandvold-rom-thread in the developers section. Can't remember the solution... Sorry

Regards
[Desire Q&A, Help & Troubleshooting] sssimo96:
Thanks, will take a look at his thread once again.
[Android Q&A, Help & Troubleshooting] Gitt:
Dear friend,

I bought just for try a tablet on Ebay - Name: N500 8G, Allwinner. Name of the model: BC1077, verzion of Android 4.0.3.

The problem is that the android 4.0.3 does not sync google calendar. I have read it in other phorums, it is common problem.

Do somebody know how to solve it?

Thanks, I am a beginner and I google it for 5 hours but I did not find answer. :crying:
[Android Q&A, Help & Troubleshooting] Archer:
Non-development questions should be asked in Q&A, not Development.

Thread moved.
[Android Q&A, Help & Troubleshooting] rockjazz07:
tablet china zto n500 plus brick

Buenas amigos, quisiera saber donde puedo conseguir una rom para la tablet china ZTO n500 plus y cual es el método para poder instalarla, tengo una pero se queda en el logo al momento del arranque, tambien me gustaría saber si se le puede instalar un recovery para que sea mas fácil la instalación de la rom, agradeceria su ayuda gracias

Good friends, I would like to know where I can get a rom for tablet Chinese ZTO n500 plus and what is the method to install it, I have one but he is in the logo at boot time, I also like to know if you can install a recovery to make it easier to install the rom, appreciate your help thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] stephanz1:
Hello,

I got a Samsung Galaxy S (I9000) and I saw the HTC One X, I like it. Is there a way to put the HTC's UI on the I9000? I got a ICS rom now but I like the HTC One X, UI.

I hope you guys understand me.

Thnx.

stephanz1
[Galaxy S I9000 Q&A, Help & Troubleshooting] Mav_tx:
You might want to try out this one :)

http://xdaforums.com/showthread.php?t=1759344
[Galaxy S I9000 Q&A, Help & Troubleshooting] stephanz1:
Very nice! Thanks. But look at this:

-=What isn't working=-

-WiFi
-2G/3G
-Bluetooth
-Random reboots
-SD Card
-HTC widget (Android widgets are working)
-GPS

I want a stable one, it looks very nice but I want to internet.
[Nexus 7 Android Development] chris.wueste:
First of all, I am in no way responsible for anything you do to your tablet period.

I have seen a couple of people asking how to return the Nexus 7 to stock after it has been unlocked, rooted and so on, so I figured I would write a quick guide as its super easy to do. Also, please make sure you make a backup of anything you don't want to lose. This is important.

Before you begin, please make sure you have ADB and Fastboot drivers installed and working.

1) Download the factory image for the Nexus 7 at https://dl.google.com/dl/android/aosp/nakasi-jwr66v-factory-d341d356.tgz

2) Extract the factory image into the same directory as your ADB and Fastboot executibles (e.g. "\android-sdk\platform-tools")

3) Plug in your device. If you are booted into Android, open a command prompt to your ADB and Fastboot directory, then type

adb reboot bootloader

If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.

4) Type

fastboot flash bootloader bootloader-grouper-4.23.img

5) Next type

fastboot reboot-bootloader

6) Now type

fastboot -w update image-nakasi-jwr66v.zip

7) Optional: If you would like to relock your bootloader for warranty or security purpouses, make sure you are in your bootloader screen again and type

fastboot oem lock

8) If your tablet hasn't already rebooted automatically, type

fastboot reboot

That should do it. You should now be on stock Android 4.3 and ready to send in your tablet for warranty purposes if you so desire.

Additionally, here is an instructional video courtesy of XDA user SladeNoctis.

Also, thank you to XDA user Shano56 for the formatting help on this post.
[Nexus 7 Android Development] SladeNoctis:
You should change the title to [Guide] How to return to Stock / Unbrick your Nexus 7

Helps out those getting bootloops or softbricks from geting root access in certain ways or messing with the build.prop
[Nexus 7 Android Development] chris.wueste:
Not a bad idea. Done and done. Also, I have proofread it several times over to ensure it is correct but would you mind making sure that all of the commands were typed correctly. My eyes are going crosseyed over here.
[Nexus 7 Android Development] Shano56:
Nice guide man, I changed the format a little to make it easier to read. Use it if you want, won't be offended if you don't.

First of all, I am in no way responsible for anything you do to your tablet period.

I have seen a couple of people asking how to return the Nexus 7 to stock after it has been unlocked, rooted and so on, so I figured I would write a quick guide as its super easy to do. Also, please make sure you make a backup of anything you don't want to lose. This is important.

Before you begin, please make sure you have ADB and Fastboot drivers installed and working.

1) Download the factory image for the Nexus 7 here

2) Extract the factory image into the same directory as your ADB and Fastboot executibles (e.g. "\android-sdk\platform-tools")

3) Plug in your device. If you are booted into Android, open a command prompt to your ADB and Fastboot directory, then type

adb reboot bootloader

If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.

4) Type

fastboot flash bootloader bootloader-grouper-3.34.img

5) Next type

fastboot reboot-bootloader

6) Now type

fastboot -w update image-nakasi-jrn84d.zip

7) Optional: If you would like to relock your bootloader for warranty or security purpouses, make sure you are in your bootloader screen again and type

fastboot oem lock

8) If your tablet hasn't already rebooted automatically, type

fastboot reboot

That should do it. You should now be on stock Android 4.1 and ready to send in your tablet for warranty purposes if you so desire.

Additionally, here is an instructional video courtesy of XDA user SladeNoctis.

If you want to use it and are too lazy to quote my post :p - http://pastie.org/pastes/4279753/text

The commands look good to me however I've never used "fastboot -w update" so can't say for that
[Nexus 7 Android Development] chris.wueste:
I updated the OP with your edits in it. Thanks for the help. I quoted you at the bottom
[Nexus 7 Android Development] jarjar124:
omg thank you so much. u saved my device :)
[Nexus 7 Android Development] chris.wueste:
Very welcome
[Nexus 7 Android Development] chrisjm00:
Assuming you have a nandroid, can you boot into the bootloader, and simply ADB reboot recovery? Or does that bug prevent you from even doing that?
[Nexus 7 Android Development] SladeNoctis:
In some cases due to the CWM not being official it cause bootloops by going to recovery in the bootloader.
[Nexus 7 Android Development] Shano56:
There's a CWM official out?
[Nexus 7 Android Development] chris.wueste:
Assuming you have already flashed CWM, then the command would actually be fastboot reboot recovery. Not sure what but you speak of.
[Nexus 7 Android Development] chris.wueste:
Yes. There sure is. If you have Rom Manager installed it can be flashed directly from there.
[Nexus 7 Android Development] nicknowsky:
I dont think you can really hard brick this device anyways
[Nexus 7 Android Development] kimbernator:
I'm sitting here at the command prompt with it on "erasing userdata"

It's been a couple minutes and I'm freakin' out! How long is it supposed to take? Everything flashed correctly, if I start the device now will there be an issue?

EDIT: Nevermind, just rebooted from the bootloader in the tablet and it booted fine. I'll get the OTA to 4.1.1 and that should probably fix any outstanding little issues.
[Nexus 7 Android Development] nugalonious:
hard brick?

I am stuck at the Google logo with a padlock and I'm pretty sure I have a hard bricked tablet. fastboot doesn't see the tablet or my computer for that mater through dmesg.

I've rebooted it countless times with vol + and vol - pushed and any combo thereof. It will only turn off completely when the battery dies because holding down the power key for 10 secs just reboots it back to the Google logo in about 5 seconds. I guess at this point I'm just waiting for Google to give me a RMA for a refund and I'll move on unless someone has any other ideas?
[Nexus 7 Android Development] Nexus Phreak:
Pressing and holding the

Volume down + Power buttons

works just fine to launch the bootloader (at least for me).

No need to press (and force) the entire volume rocker button at all. ;)
[Nexus 7 Android Development] caanda45:
Try and press and hold just the power button for 30 seconds or so to re-boot the tablet and you should be fine and it should boot up just fine. From fastboot you cannot go into cwm recovery because of a bug.
[Nexus 7 Android Development] yeahthatsme:
I'm trying to return to stock but get this message in the window from the ADB command after flashing the stock ROM:

​

FAILED (remote: (FileWriteFailed))

Anyone seen that before or have any ideas to fix?

I tried wiping cache/factory reset from CMW but no joy.
[Nexus 7 Android Development] Kas206:
Thanks. Worked for me. I did get worried when i got (data transfer failure (too many links)) error when trying to flash the bootloader.

Turns out it was the USB port. I switched the ports and all was well.

But I followed the commands in side the flash-all.sh file

fastboot erase boot

fastboot erase cache

fastboot erase recovery

fastboot erase system

fastboot erase userdata

fastboot flash bootloader bootloader-grouper-3.34.img

fastboot reboot-bootloader

fastboot -w update image-nakasi-jrn84d.zip

---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------

Try the commands i posted above and see what happens
[Nexus 7 Android Development] yeahthatsme:
Nuts. I tried it on many USB ports and did your commands one by one. Ended up in the same spot. It happens when writing 'userdata'...
[Nexus 7 Android Development] nugalonious:
Now I've tried it all. Definitely bricked.

Took back cover off for easier troubleshooting and now have rebooted it hundreds of times with all four of the buttons pressed in different combinations. No idea what the forth button (Key 4 its labeled) even does because there's no button on the outside to access it but I've tried it anyway
[Nexus 7 Android Development] Shano56:
How did you brick!!??
[Nexus 7 Android Development] nugalonious:
I'm not sure what happened but the last thing I did was flash a recovery then a fastboot reboot. After that only Google logo no matter what I do. Actually had to pull back cover off and pull the battery cause it wouldn't turn off any other way

Went back through my terminal session and the exact commands went like this.

./adb reboot bootloader

./fastboot flash recovery ~/Downloads/openrecovery-twrp-2.2.1-grouper.img

./fastboot reboot

thats it.
[Nexus 7 Android Development] Shano56:
If you still see an image...you shouldn't be bricked. U should try turning your tablet off for 20-30 mins, then holding all 3 buttons at once. Try it plugged in and not plugged in
[Nexus 7 Android Development] nugalonious:
Thanks for the suggestion but it is still doing the same thing. I have to unplug to battery to turn it off otherwise it just continually boots to the Google with padlock within 5 seconds and stays there until the battery dies or i unplug it.

Wish Google would actually get back to me. Waited on hold for an hour yesterday just to have a trouble ticket opened.
[Nexus 7 Android Development] Atmazzz:
Try the Nexus root kit. Use the option flash stock and unroot. Check the wont boot box. Don't know if it will work but worth a shot.
[Nexus 7 Android Development] goku16:
im getting stuck after step 2?

it said waiting for device

anyone have a picture instruction?

thanks a lot
[Nexus 7 Android Development] spences10:
It's not bricked if you see an image

You need to be able to get into the bootloader by using the hardware keys, I read this post thinking they would be in the OP

When the Nexus 7 was announced at I/O JBQ told everyone how to get into bootloader using the hardware keys rather than adb commands. adb commands are fine if the device boots but if you have a semi brick you need to know these keys [and the OP updated accordingly]
[Nexus 7 Android Development] jaxadv:
Great tutorial!

Thank you so much, have tried the MCR rom but I still think we need to wait to have more roms available...
[Nexus 7 Android Development] spences10:
I found that if you hold down Vol Up + Vol Down + Power takes you into the bootloader

Maybe update the main post with this OP?
[Nexus 7 Android Development] nugalonious:
I've literally tried all the keys. Including the vol +and vol- and power probably 25 times. Still the only way it will turn off is by pulling the battery connection. At least the case is easy to open. Google needs customer support badly
[Nexus 7 Android Development] fung58745:
EOCD not found,not zip

i use the same modern to dobut after

fastboot -w update nakasi-jrn84b-factory-8b0bd791.zip

this word come out

EOCD not found,not zip

what wrong please help
[Nexus 7 Android Development] EVOXGSR:
I bricked a few weeks ago prior to the official release of the Nexus 7, luckily I managed to unbrick and load the factory images. I am really glad to see this type of guide out now to help people with my similar sticky situation! Great job!