yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] amzkyz:
Hi guys,got a huge problem with my nexus..so here it is, i play around with my nexus 4 twrp recovery mode and came to this option of format/sytem, cache and everything in to that option becoz someones suggested to format my fone thru here, what i did is i click all the options that started with 'format' so i think that was all written in there..after doin it.,i go back to twrps first page and choose reboot now and there,option of not beeing rooted appeared and also ask to root or not..so i click yes becoz i already had a rooting state.then i was waitin for about 5mins and still im in a google logo screen and expecting nexus circles will came up..but not,i was stuck here..

What causing this..did i wipe all the files including the os installed?

I can go back to fastboot mode/bootloader and twrp recovery but still stuck from google logo

I did factory reset, clear cache and everything in twrp but still no luck..

And even the backups not showing..

So the question is,if i will flash image thru fastboot,do i need specific files of stock rom?baseband?country related roms?

Im sorry for all this noob questions, but if anyone could suggest will be greatly appreciated..
[Nexus 4 Q&A, Help & Troubleshooting] Zehlek:
I would suggest rebooting into bootloader and flashing factory images with ADB or a Toolkit
[Nexus 4 Q&A, Help & Troubleshooting] amzkyz:
Need to close this thread..got my nexus back to life..all in the process of adb flashing.img files..thanks to all of u guys who help..love ya all.:)

SOLVED!!
[Nexus 7 (2013) Q&A] kbrn:
Title says it.. I'm new to the whole Nexus thing. I'd like to know what is the most effective way to root. I'm currently running 4.4 Nexus 7 wifi

Thanks in advance!! :good:
[Nexus 7 (2013) Q&A] melander:
This is also my first time using a Nexus device.

My friend recommended NRT for rooting.

Here is the thread for that:

http://xdaforums.com/showthread.php?t=2389107
[Nexus 7 (2013) Q&A] ThaiDai:
the most effective way to root and protect your device is:

start reading the tutorials here.

then you'll understand what you are doing.

this will save you a lot of time - or else you will continue asking questions...
[Nexus 7 (2013) Q&A] Joppykid:
http://xdaforums.com/showthread.php?t=2382051

This is a little more in depth of how to do it. It's what I used. I hadn't rooted a device for a few years and this worked pretty good for me. Video is helpful too IMO.
[Nexus 7 (2013) Q&A] kbrn:
Awesome!! Thanks for your help! :good:
[Nexus 7 (2013) Q&A] therock11:
My ASUS Nexus 2013 edition running 4.4 (and previously 4.3) randomly reboots while charging and idle. It does it at least once a day while display pictures in "DayDream" on my desk at work. I contacted Play Support and they had me factory restore and the problem continues. I contacted ASUS support and they created an RMA but I'll be without my tablet for 15 to 30 days (annoying). I'm considering just living with it like this till Google pushes a fix or trying to determine if it is a hardware issues.

Is anyone else experiencing this issue and finding a solution short of ASUS's awful support option?
[Nexus 7 (2013) Q&A] beanboy89:
Yes. I just created a thread about this last night: http://xdaforums.com/showthread.php?t=2557666

It's happened to me twice now and I know someone else who had to get their Nexus 7 replaced under warranty a few weeks back because the same problem. I just got the tablet last night and I have about five weeks from the retailer that I purchased it from to return it.
[Nexus 7 (2013) Q&A] jtdc:
when i was running 4.3 i have some random hangs (for a few seconds then works again normally) and unreproducible random reboots.

update to 4.4 (which is still use today) the random hangs disappeared, but the random reboots still happen sometimes.

here's hoping the 4.4.1 update fixes it. waiting for OTA or until my patience for it runs out. :)
[Nexus 7 (2013) Q&A] wweeii:
Don't wait for a software fix. If your device is rebooting randomly it is likely a hardware problem, get it exchanged/RMA while you still can.
[Nexus 7 (2013) Q&A] jtdc:
i would like to, but as i said i cannot reproduce it (and it rarely happens). hard to bring to service center and unable to show it on their face. what do you suggest about that?
[Nexus 7 (2013) Q&A] Matrix_19:
Mine is rebooting randomly but sometimes it is juste once a week or two and sometimes it can reboot twice the same day. KitKat didn't fix it but I installed 4.4.1 yesterday... I will see if this issue is still there in the next days/weeks

EDIT : first reboot on 4.4.1 :(
[Nexus 7 (2013) Q&A] lmacmil:
I got mine in June and it was updated to 4.4 a couple weeks ago. It reboots randomly once or twice a week with no discernible pattern. Today I had an ebook reader (FB Reader) open and was in Chrome when it reset. The battery was above 95%. If it never got any worse I could live with it but I'm worried that it might get worse over time.

I am trying to register it on the ASUS site but it rejects the serial number from the "about tablet" screen. There is no sticker on the Nexus and I might have tossed out the box. Any suggestions? I have emailed Asus but don't know how their support is so I don't know when (or if) I'll get a response.
[Nexus 7 (2013) Q&A] Pjstaab:
I was charging mine one day and it did it several times in a row, then I yelled at it and it stopped. The longer i've had it the less often it seems to happen though.
[Nexus 7 (2013) Q&A] shams6:
My device 16GB wifi has random reboot issue. It reboots so much time everyday.

I have done every possible way to solve my problem but no luck :(

Now in stock 4.3 (franco kernal) which gives less reboot than any other ROM.

1st i think, its a apps issue, soon i felt its not a app issue rather its a hardware issue. I have used 4.3, 4.4, 4.4.1, PA, CM, Slimbean, Slimkat, and many other roms and kernals , also i open back cover to solve reboot problem but no luck, reboot occurs as usual.

Also talk to google help center, give factory reset and they suggest me to send to RMA for replacement. I bought it by my cousin from US play store.

I am now outside of USA, so cant send to RMA now but i have cousin in usa who can help me to send it RMA.

Before doing that i want to know every details about RMA and how to send it from my cousin home? how much time would it take, Any cost for sending and receiving of the product (Any Courier charge)

Pls someone give details about RMA, I am kinda noob about that.....
[Nexus 7 (2013) Q&A] therock11:
They use the MAC address of the wireless under wifi/advanced settings instead of a serial.
[Verizon Samsung Galaxy S 4] tech_head:
Hi,

Here's a unique idea.

Let's pass the word to boycott Samsung over the whole KNOX fiasco.

Use social media, ie. twitter, facebook, etc. to pass the word.

Tell everyone you know not to buy a Samsung phone this holiday season.

The only thing that will make companies take notice is if we take action.

1. Just the attempt to downgrade firmware or load unauthorized firmware triggers KNOX in 4.3 and voids your warranty.

2. Now that's not bad enough, because even if you now load a signed piece of firmware KNOX still stays triggered.

3. If my warranty is now void, I should be able to do what I want, but nooooo, my bootloader is still locked and I have no warranty.

So Samsung should fix this. Just trying to do something should not void my warranty, especially since they block the possibility of being able to change the bootloader.

This is not Samsung's device.

Everyone does not need nor want KNOX and those that need it, know it.

The majority of devices are not enterprise, so why are they forcing an enterprise and NSA solution down our throats!

BOYCOTT SAMSUNG!!!
[Verizon Samsung Galaxy S 4] joshm.1219:
I was going to say a lot of the obvious, but let's just say this is um admirable. :p
[Verizon Samsung Galaxy S 4] richii0207:
For your #1, how did you load unauthorized firmware?

I don't understand your #2...what "piece of firmware"?

How do you know it voids your warranty? Did you have issues with the warranty?
[Verizon Samsung Galaxy S 4] prstorero:
I really doubt something like this would work. The only people on board would be those of us who mod, which make up such a small portion of Samsung's sales, they wouldn't care. The general consumer is where they get their money and said general consumer couldn't care less about Knox.

prshosting.org
[Verizon Samsung Galaxy S 4] tech_head:
Tell your friends and family. Word of mouth is huge.
[Verizon Samsung Galaxy S 4] xsalemx:
Samsung sold 213 million phones in 2012.
[Verizon Samsung Galaxy S 4] JeeperDon:
Two things...

1) Though XDA and all seems huge, only a really really small percentage of cell phone users play around with crap that will effect knox. I doubt a large number of those "don't care" people are going to want join your campaign.

2) There are a lot of great things about Samsung phones and products. It's like people complaining about VZW cost and billing and marketing, but they have great coverage and I'd never switch because someone starts a "boycot Verizon for $$ reasons".

I don't like the S4 lockdown either, but I'd rather have a locked S4 than an unlocked G2.
[Verizon Samsung Galaxy S 4] SirHoover2010:
Not sure I'd agree with this. At the same time o hate Samsung, I'd have a Motorola phone if I wouldn't have had to upgrade when I did. Kind of screwed me.
[Verizon Samsung Galaxy S 4] JeeperDon:
You don't have to.
[Verizon Samsung Galaxy S 4] SirHoover2010:
Yea ik. Exactly why I put "at the same time I hate Samsung" so I'm kind of biased
[Verizon Samsung Galaxy S 4] The D3mon:
They can make lock downs most of this is to stop forms of piracy in my opinion. I'm new to rooting but I'm from the modding scene. I have no worries do to developers here as I do on game system modding. Give them time nintendo,Sony and Microsoft have done similiar things with updates the push regularly to their gaming consoles and boycoting will not work do to the modding group is a small group that has a small impact they already planned on loosing.
[Verizon Samsung Galaxy S 4] richii0207:
Boycott yourself, this would defeat the purpose of "DEVELOPER" phones...you knew what you were getting into when buying a consumer s4.

When will people think logically? Samsung wants security. They sell the developer phones completely unlocked for US.
[Verizon Samsung Galaxy S 4] KennyG123:
Knox is high security put on the phone as a bid to gain military contracts. They only want the most secure phones. Do you think Samsung will stop trying to get that military high $$$ over a few people saying they won't buy anymore? Also add to this many corporate businesses that buy bulk phones and contracts and want a more secure phone for their Exchange and corporate software. XDA users are barely a ripple in that ocean of waves.
[Verizon Samsung Galaxy S 4] Batttie:
you should have bought a developer edition if locked bootloader was a concern.
[Verizon Samsung Galaxy S 4] eklipz3:
not that it matters but i believe a korean family controls 46% of samsung husband wife and 3 kids. just saying.
[Verizon Samsung Galaxy S 4] orangechoochoo:
Okay, so you're going to tell their kids that their daddy is a bad man for locking bootloaders? Tell their kids they won't get Christmas presents if they don't get their parents to unlock bootloaders?
[Verizon Samsung Galaxy S 4] JeeperDon:
The kids don't care. They have the Developers Edition. :cool:
[Verizon Samsung Galaxy S 4] eklipz3:
sorry i should have made myself a little more clear about the kids but they are adults as well and are vp's and such of samsung and i think the oldest girl was just promoted to run some part of sammy. and yes i bet there's is not locked.
[Verizon Samsung Galaxy S 4] KennyG123:
Umm...yeah...because the international versions are not locked...neither is Sprint...it is a carrier request to lock bootloaders on Samsung phones, otherwise all phones would be locked. Locked bootloaders and Knox are not the same thing. This thread states it is about Knox. True that Knox in the bootloader prevents you from downgrading the firmware...but does not equal locked. There are many phones with locked bootloaders but no Knox.
[Verizon Samsung Galaxy S 4] tech_head:
It's not just about a locked bootloader.

If that was all, no issues.

KNOX and SE Linux are now baked in from the bootloader up.

No it was not on my phone when I first got my phone and was not detailed before they rolled it out.

Messing with the bootloader in anyway even an attempted downgrade, void your warranty.

Not tampering by using unauthorized software, but just trying to go to an older version of *SIGNED* firmware will void your warranty.

My issue is this, if my warranty is now void, why can't I install any *SIGNED* firmware that came on the phone?
[Nexus 5 Q&A, Help & Troubleshooting] menboi1:
Hello i have little question

What is better the

cm11 snapshots versions

or the

cm11 nightlys versions

???

Thankss!!!
[Nexus 5 Q&A, Help & Troubleshooting] dabbill:
Snapshots are more stable then nightlys
[Nexus 5 Q&A, Help & Troubleshooting] ronwi2:
I want to experiment with NFC tags, but I have read there are some compatibility issues.

Has anyone purchased NFC tags that work with the N4? If so, what type should I be looking for, and where can they be purchased?

TIA.
[Nexus 5 Q&A, Help & Troubleshooting] ljesh:
I ordered these: http://www.ebay.com/itm/160923054515

Still have not received them (I guess in 2 weeks or something like that I will) so I don't know if they will work, but they should.
[Nexus 5 Q&A, Help & Troubleshooting] Glutt0ny:
Ordered these and they work like a charm ! (you can find the stickers and hand tags separated) www (.) amazon (.) co (.) uk/RapidNFC-Tags-Task-Launcher-Pack/dp/B00A0Y97C8
[Nexus 5 Q&A, Help & Troubleshooting] hollywoodfrodo:
Most tags will work, but the ones to stay away from are the Mifare Classic Tags - those only work with devices that have a specific manufacture's NFC Chip.

NTAG203 Tags are the most popular and affordable NFC tags for general use that also are universally compatible with all NFC devices. For uses requiring a little more memory, there are the Topaz 512 Tags.

We have both over at AndyTags.com (disclosure - it's my store) as well as NTAG203 key chains, but most NFC suppliers these days will have either type so no obligation to get them from us. :)
[Galaxy Note II N7105 Android Development] mrjayviper:
I'm not the developer

but kitkat nightly is out.

ROM download: http://download.cyanogenmod.org/?type=nightly

gapps download: http://wiki.cyanogenmod.org/w/Gapps

Change log: http://changelog.bbqdroid.org/#/t0lte/next

You might experience problem with twrp so it might be better to use CWM.

Also I believe it'll be a full wipe installing the ROM the first time. Good luck.

ps. if the cm dev wants to create a new thread for this ROM, please do so and I'll ask a moderator to close/delete this one.
[Galaxy Note II N7105 Android Development] mrjayviper:
here are the results of my trials earlier today. ROM is working nicely now. at least on the apps I've tried it on. Still using dalvik though.

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

some tips (all my testing was done using official CWM 6.0.4.1):

1. Definitely do not use TWRP unless there's an update to 2.6.3.7. (seems TWRP could work if one use the modified version. see message below. I haven't tested this myself.)

2. using CWM and exFAT is a hit and miss. A fresh install and the ROM can't see sdcard. The only time the sdcard was detected was after a nandroid restore.. Since all the files in my SDcard is < 4GB, I can use FAT32.

3. nandroid restore = no mobile connection for me. this was fixed by reflashing the even if it's the same nightly (example: say I made a nandroid backup of 17-Dec nightly ROM. due to having messed up stuff, I decided to restore my backup. as said above, this will result in no mobile connection. but if I reflashed the zip file for 17-Dec nightly, this will fix the problem)

4. the hangouts included in the gapps (See link above to CM wiki) resulted in FCs when trying to make a video call. this was fixed by uninstalling hangouts using titanium and reinstalling it via the playstore.

5. I believe all official recoveries need updating to support 4.4 properly.

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

original message is below. you can see the problems I've encountered during testing.

just flashed the nightly for t0lte using TWRP 2.6.3.7 and somehow it can't see my SIM. Will be flashing again using latest CWM (6.0.4.1 as of now).

initial observations:

1. NTFS work on SD cards

2. 2 launchers are present (launcher and launcher3)

3. looks better than Jb (it could be placebo effect because kitkat is new)

update: definitely use CWM at least for t0lte. ROM has recognized my SIM.

update2: been playing around with the ROM and when I tried to access my NTFS-formatted SDcard, it cannot see. I had no problems at all with my SDcard using TWRP. I can even browse the folders inside it using file manager. I also had a problem with the built-in hangouts and video chat. I'm getting FCs.

update3: restoring from CWM nandroid backup = no cellular/mobile connect. Can't even call anyone.

update4: update to update3. I did lose cellular/mobile connectivity (phone can't find sim) BUT it can recognize my NTFS-formatted sdcard now! :D :(

update5: removing hangouts via titanium and then reinstalling the playstore version, I can make a video call.

update6: restore from nandroid (which gives me a working NTFS-formatted sdcard) and then reflashed the ROM. I got mobile signal but no sdcard. I guess I can always format it at as FAT32 which I'm doing now.
[Galaxy Note II N7105 Android Development] Sheikx800:
Keep us posted. Would love to know how to sort out the data connection/sim issues before I flash.

Cheers.
[Galaxy Note II N7105 Android Development] mrjayviper:
gave up on making an NTFS-formatted sdcard work on a new flash. I'm formatting my sdcard now to FAT32. It'll probably be fixed down the road.

and I think flashing the ROM after restoring from nandroid backup will bring back mobile signal. At least that's my conclusion.

But I do get a signal only if I use CWM

.
[Galaxy Note II N7105 Android Development] Unknownkj:
Yea twrp 2.3.6.7 is buggy. Look for twrp 2.3.6.1, it's modified and will work with cellular signal. Keep us posted.
[Galaxy Note II N7105 Android Development] contramundi:
The modded twrp is linked on one of the last pages in the beanstalk thread iirc
[Galaxy Note II N7105 Android Development] mrjayviper:
updated 2nd post to give some tips on how to install ROM properly. seems to be working nicely now. That said, I don't have much app/games installed on my phone compared to my tablet (50-60 apps on the phone compared to 90+ on the tablet. mostly games).

a sample list of apps installed on phone are dashclock, lightflow, dynamicnotifications, various messaging. various Google apps and 1 game.
[Galaxy Note II N7105 Android Development] -P3P-:
Installed with latest CWM and Data works great, no issues with Calls / LTE etc.

ROM seems really good so far, using Google's OK Google is fun but does tend to drain the battery faster, that said I will switch to a different kernel as I miss Viper so will most likely go with Devil, hopefully it helps with the battery.

I've never had an issue with CWM, I upgraded to the latest version using ROM Manager.

My tip for flashing is to always wipe perform a full wipe plus Cache, Davlik and System before flashing and Cache, Davlik after.

Miss some features / tweaks from other Roms but I know that CM is the best stock experience out there so no problems there.

IMO no issues running as a daily driver.
[Galaxy Note II N7105 Android Development] richyy74:
Proximity sensor not working. Is it just me or...?

Tapatalk-kal küldve az én GT-N7105-el
[Galaxy Note II N7105 Android Development] terpin32:
I had problems to are you running any other kernels or are you on the stock one?
[Galaxy Note II N7105 Android Development] EmptyArea:
CWM 6.0.3.1 Touch (I think!) doesn't work, got bad flash error 7 (I think!) every time.

ROM manager update to 6.0.4.1 to non-touch* worked like a charm.

(*because I'm both tight and lazy)

---------- Post added at 10:14 PM ---------- Previous post was at 10:04 PM ----------

Definitely not working on a clean install, with a few apps installed.

According to a test app the light sensor is responding but the prox is not.
[Galaxy Note II N7105 Android Development] EmptyArea:
Camera app is buggy, useless in fact. 3rd party camera is fine temporary replacement.

Facebook edit post doesn't allow cursor placement, facebook app 4.4 problem I assume.
[Galaxy Note II N7105 Android Development] charkey:
Is anyone able to successfully set the DPI to another value in build.prop? Mine always defaults to 320 after each reboot.

Update:

I seem to be able to edit/save build.prop changes fine in 12/07/13 nightly.
[Galaxy Note II N7105 Android Development] leebag:
Had the same flash error 7 corruption had boot loop into recovery and had to use a nand backup to get back. Did a clean install, and the process went well. Only issues so far are my Microsd can't be seen. And can't manage to get the 'Ok google' stuff working. A few random crashes but overall working well so far.

So would love some help with the Microsd issue as this is quite important?
[Galaxy Note II N7105 Android Development] mrjayviper:
my NTFS-formatted sdcard can be seen when I use TWRP 2.6.3.7. not so with CWM 6.0.4.1.

I'm running the modified TWRP mentioned in page1 but my sdcard is still FAT32. I'll format my sdcard and see if it works.
[Galaxy Note II N7105 Android Development] mrjayviper:
I'm going back to CWM. just noticed all sorts of problems on my phone running the modified TWRP. :/ sucks!
[Galaxy Note II N7105 Android Development] AkiraBBQ:
No radio signal when flashing with TWRP 2.6.3.7. Flash again with CWM 6.0.4.1 radio is back. No problem with the external SD card (FAT32).
[Galaxy Note II N7105 Android Development] contramundi:
[MENTION=4832480]mrjayviper[/MENTION] Wasn't twrp 2.6.3.7 a bugged and accidental upload?

(At least people kept telling me a short while ago. )

Try the modded twrp 2.6.3.1 been linked a few days ago in the beanstalk tread
[Galaxy Note II N7105 Android Development] -P3P-:
Updated to the latest nightly and running Agni kernel and all running well.

Battery life is great, loving this ROM so far!
[Galaxy Note II N7105 Android Development] mrjayviper:
is anyone been able to successfully make a video call on hangouts? it's been FCing on me. using cwm and twrp.

I just tried the PA full gapps and no luck with that. thanks
[Galaxy Note II N7105 Android Development] blecap:
VPN and lockscreen

hi guys i download a program called privateinternetaccess which i uses it for my VPN and after connecting, nothing can send out, such as whatsapp, etc until i disconnect it.

Second issue to report is lockscreen. when i disable it to none, and then wanting to setup another it has no options anymore.
[Galaxy Note II N7105 Android Development] jdstrydom:
Known vpn issue on 4.4.3 Android which I hope gets resolved soon. All vpn apps that seem to depend on openvpn seem to have routing / forwarding issues. You get connected, but no data traverse the tunnel.

Have tried everything eg. tun.ko and openvpn binary installers, google got no solution currently as well. We'll have to wait for the cm/4.4.3 devs to provide magic, the 4.4.3 release is still quite new.

Orbot seems to mostly work over the tor network.
[Galaxy Note II N7105 Android Development] MarlinFF:
Wish there was a tmobile version.
[Galaxy Note II N7105 Android Development] blecap:
there's an update of the rom dated 16th. wonder where can i view those changes?
[Galaxy Note II N7105 Android Development] zain0300:
in case you do not know N7105 roms can be flashed on tmobile note 2 and everything works the same
[Galaxy Note II N7105 Android Development] erwinsie:
hi all. im from sydney and will flashing my N7105 with nightly CM11.

currently using DN3 (android 4.3) but its time to try 4.4.2 and CM.

I just thought why not having something different (no samsung bloats) on my mobile.

hope everything is fine!

ps. i will just run the installer