yashsingh1/xdaforums huggingface dataset:
[Sony Ericsson Xperia Neo, Pro] cromoxx:
after root my neo v i want install cwm but my neo v can't get cwm after use x-parts..my neo v on gingerbread..do i update to my neo v to ics to get cwm:confused: sorry for bad english
[Sony Ericsson Xperia Neo, Pro] Eklado:
Don't update, all you need to do:

1- Download Flashtool.

2- Choose the customized ROM that you want to use (by searching for a stable or nighty version it's up to you).

3- Download it on your computer and unzip it.

4- Copy the boot.img file into the firmwares folder inside the Flashtool folder/directory.

5- Connect your phone to the computer.

6- Flash the boot.img from inside the Flashtool application itself.

If you don't understand any step or want the rest of the steps you will find it in the customized ROM thread.
[Sony Ericsson Xperia Neo, Pro] Attitude.SSJ:
^ this only works if he has an unlocked boatloader which he hasn't mentioned...
[Sony Ericsson Xperia Neo, Pro] Gjole86:
cwm is usually in the boot.img.

if the phone was on GB before, just flash any GB boot.img and press volume buttons on boot up (when the notification led goes blue)

that should put the phone in cwm.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] lawkev:
Hi,

I have a Verizon note 3 on Metropcs. I know I won't get OTA updates but what are the chances of me finding the updates online for download. I hear there was another update approved on 12/09. Does it make more sense to sell this phone and buy a t-mobile note 3 to use on metro? Would I have a better chance at getting updates? Should not bother with updating the phone? Don't ask how I got into this situation. It's a long story.

Thanks
[Nexus 7 Q&A, Help & Troubleshooting] hennimore:
Hi everyone,

I'm using QBKing77's tutorial to manually upgrade my Nexus 7 to Kit Kat 4.4 (and up) but haven't been able to with ClockworkMod Recovery installed.

The video I'm using is on YouTube, titled: "Manually Update the Nexus 7 to Android 4.4 KitKat" and at the step at 3:38 I don't know what to do.

(sorry I'm unable to post links bc I'm a new user:crying:)

CWM doesn't have the 'Apply update from ADB' option that stock Recovery has (or at least I'm not sure what to do in its place).

If anyone knows how I can continue the upgrade process it would really help!

Thanks in advance :good:
[Nexus 7 Q&A, Help & Troubleshooting] deny_kei:
Wow really appreciate and very useful for me Mr blake. Thanks a lot. One question, im in stock 4.4 krts160 with root and unlock bootloader with twrp cwm, i m going to flash the newest ota, will this step erase my root and relock my bootloader? Or i watch in youtube post by rootjunkies that twrp can handle ota. What would you suggest the better way. And thanks again for the information.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, deny_kei...

You will loose root, and your Custom Recovery... whether that be TWRP or CWM:(.

I'm afraid it's unavoidable - it's always been that way with OTA's. You have to fastboot flash your Custom Recovery of choice again afterwards, and re-root... not difficult, but a bit of a nuisance nontheless:).

Flashing an OTA, though, will NOT re-lock the bootloader.

The bootloader will remain unlocked until you purposefully choose to relock it with fastboot oem lock.

TWRP should be able to handle an OTA flash. I'm currently using CWM (with which I flashed the KitKat 4.4.2 OTA), but I've never had any problems myself applying OTA's with TWRP in the past.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] hennimore:
Thanks so much for the helpful response! I should have also mentioned that I currently have AOKP running on my N7

(Version: aokp_grouper_jb_build-2 Build number: aokp_grouper-userdebug 4.1.1 JRO03L eng.roman.20120916.095343 test-keys)

I'm not sure how this affects the update process, but would definitely appreciate any other help you can offer.

Thanks again! :D
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, hennimore...

As you're running a Custom ROM, you can pretty much forget about OTA's... as they are only designed to upgrade

official stock firmware

from Google. If you were to attempt to flash any OTA on your Nexus 7 as it currently stands, it would abort almost immediately during the verification phase of the OTA update process. Because nothing in /system would match what the OTA expects to subsequently 'patch' (update) in the second half of the OTA update process.

Your only option, if you wish to have official stock KitKat installed on your Nexus 7, is to fastboot flash back to factory stock.

For this, you will need the full factory stock image for your Nexus 7, available

here

.

(Currently, build KOT49H KitKat 4.4.2 is not yet available as a full factory image... just KRT16S KitKat 4.4... but that's not a problem...'cos once you have KitKat 4.4 installed, you can then use an OTA to bring it completely up to date... as detailed in my previous post).

Instructions on how to restore factory stock are available

here

.

This process is more time consuming than it is technically difficult... because fastboot flashing back to factory stock essentially wipes the device... so before you can begin, you need to backup all of your apps and associated app data with Titanium (requires root), and then backup the entire contents of the Nexus 7's internal storage to your PC... for later restore AFTER you've fastboot flashed KitKat.

Fastboot flashing back to factory stock resets the device, as though it where new. You'll need to set up your WiFi password again... and re-enter your Google Account (gmail) details... and restore all your data from your PC... fastboot flash CWM or TWRP in order to re-root. Once rooted, you can then use Titanium to restore all your apps.

Longwinded and tediously time consuming, it certainly is:(... but it's the only way to get official KitKat on your Nexus 7 if you're currently running a Custom ROM.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] hennimore:
Ah, I'm sad to hear that I must flash back, but I appreciate the information! Thanks again for all of you help, hopefully I can complete the process without any hiccups! :p
[Nexus 7 Q&A, Help & Troubleshooting] deny_kei:
Thanks Mr Blake i will considered using ota, nevertheless my last ota i got stuck in the softbrick although my nexus is stock,unlock an unroot.

Thanks for this useful information
[Nexus 7 Q&A, Help & Troubleshooting] hennimore:
I've been following your steps and seem to have hit a wall when I need to install the adb drivers. I went to the link included in your instructions and followed their tutorial for a Windows 7 PC. After coming back to your instructions, I continued to the step with the Command Prompt.

I entered the command correctly as written, however I get no results under the List of devices attached.

I'm not sure if this is related to the problem, but when I am in Device Manager trying to Locate Android Phone in the right pane, all that shows for me is 'Nexus 7' - which I would assume should work.

However, after Right-clicking on 'Nexus 7' (Android Composite ADB Interface doesn't appear) and selecting Update Driver, I continue through the steps to where I must manually update the driver, and I received a message stating, "The best driver software for your device is already installed"

Under that it says, "Windows has determined the driver software for your device is up to date. MTP USB Device"

I'm not sure if you can make anything of this, but I figured I'd ask since you've been so helpful thus far :angel:
[Nexus 7 Q&A, Help & Troubleshooting] Meshe:
Hi guys,

I've been having problems to update to 4.4 in the Nexus 7 wifi version, the only thing I done is unlock the bootloader and root, once I tried the OTA upgrade it starts the process and then it shows up the Android little guy with an error, and doesn't shows the error of installation. I tried once the flashing the zip file using TWRP and it just failed. After the first failed the tablet just started to lag horribly. Any suggestions on how to fix this?
[Nexus 7 Q&A, Help & Troubleshooting] hennimore:
Does anyone have any ideas? Thanks!
[Nexus 7 Q&A, Help & Troubleshooting] hennimore:
Hey again, so I was able to get beyond the point where I originally was at a standstill, and now have 4.4 installed on my N7 (Build KRT16S)

So now my question is, do I need to re-root my device, then upgrade to 4.4.2? Or am I currently rooted?

I don't see the option for USB debugging in my settings any longer...

Thanks!!!
[Nexus 7 Q&A, Help & Troubleshooting] deny_kei:
I have tried updated ota on my nexus 7 root without unlocking bootloader on 4.3 update and it works fine but you will lost root . Is your nexus root ,unlock bootloader with twrp and stock rom? If thats the case try to update via ota. Ive just manage upgrade to 4.4.2 with ota 10 minutes ago with above situation. I only lost my root not the unlock bootloader. The twrp cwm can handled ota. Thats my advise .

Lets hear advise from others because i also noob in nexus 7

Thanks
[Nexus 7 Q&A, Help & Troubleshooting] zolaisugly:
Just wanted to say how grateful we are for having you gedblake here in n7 forum while this thread doesn't apply to me I still read it and was pleased to see the well written well explained replies.

Don't mean to hijack this thread or for it come over as all gushy etc but than you.:thumbup::beer::D
[Nexus 7 Q&A, Help & Troubleshooting] Meshe:
Hey Ged, do you know any about my issues or suggestions? The 4.4.2 ota upgrade showed up and it too failed to upgrade from 4.3
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
It could be a TWRP problem...

Hi, Meshe...

You don't state which version of TWRP you're using, and what (if any) errors where displayed when the OTA aborted. If, as you say, you have performed no significant modifications to your Nexus 7, other than unlocking the bootloader and flashing TWRP (and rooted it)... then the 4.4.2 OTA should flash...

...however, there seems to be something odd about the behaviour of TWRP v2.6.3.1:(.

To elaborate... there is a known problem using TWRP 2.6.3.1 when flashing franco's latest kernel. See

here

for details on this.

This problem seems to relate to TWRP v2.6.3.1 itself, and not to franco's kernel .zip. The kernel flashes without problems using an earlier version of TWRP, namely v2.6.3.0 and also with the latest CWM recovery...

Nobody seems to know why TWRP v2.6.3.1 fails to flash franco r76, but fail it does. It appears that something is 'broken' in TWRP v2.6.3.1.

So I'm suspecting that your difficulties flashing the KitKat OTA might be similarly related to whatever is broken in TWRP v2.6.3.1... assuming of course, that this is the version you're currently running.

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

Here's what I would do... flash either TWRP v2.6.3.0 (the previous version) or CWM v6.0.4.3 (links below), and try flashing the KitKat OTA again. (I used CWM when applying the KitKat 4.4.2 OTA and it flashed without problems).

TWRP Recoveries...

http://techerrata.com/browse/twrp2/grouper

http://techerrata.com/browse/twrp2/tilapia

ClockWorkMod Recoveries...

http://www.clockworkmod.com/rommanager

(It's important you get the correct version of CWM recovery for your Nexus 7, as there are four CWM recoveries listed for the Nexus 7; two for the first generation model, and two for the second generation model.)

You'd normally fastboot flash a custom recovery, but if you're already rooted, you can flash a custom recovery directly from the Nexus 7 itself, without going anywhere near a PC:)... by using the rather excellent

flashify app

:).

To summarize...

1). Install flashify on the Nexus 7.

2). Download to your Nexus 7 any custom recovery other than TWRP v2.6.3.1.

3). Ensure the

KitKat 4.4.2 OTA update .zip

is located somewhere on the Nexus 7.

-----

4). Use flashify to flash the custom recovery (It will request root privileges).

5). Boot (via the bootloader) into your custom recovery.

6). Using that custom recovery, flash the OTA... again:).

Finally, if the above doesn't work, and the OTA aborts again, write down any error messages that are displayed. They can sometimes prove invaluable in diagnosing the problem, in order to decide what the next step is to take. Whenever I embark upon some project, for which taking screenshots isn't an option, I always keep my camera handy, such that I can take photographs of the screen... affording me a complete photographic record of the process, errors included, that I can review later. Very useful when things go wrong... as sometimes they do:(.

Hope this helps... and good luck.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Wow, erm, I mean yes... thanks... [MENTION=3745523]zolaisugly[/MENTION]... not quite how to respond to that.:o(blushing/embarrassed).

But thank you for your kind words, they're hugely appreciated.

I just try to help as best I can... 'cos I know what it feels like when you think you're 'bricked' or otherwise have problems with your device, as I had last year, with my (the then new) Nexus 7....and it's a uniquely horrible feeling.

You can read about my fumbling efforts

here

.

But it was posts here on XDA that got me back on track... and got my Nexus 7 working again:).

So now, I try to give something back to XDA... my way of saying thanks I guess... and always I remember the stress I went through back in November of last year with my Nexus 7... so I can empathise with those who might not be so knowledgeable, or confident, or sure of their own capabilities, as some of the more experienced XDA veterans. And I try to help... when and where I can. Nobody can know everything... and everybody begins somewhere.

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

To all...

The primary rule I've learned in this past year, is if you think you've bricked your Nexus 7, or have some other seemingly intractable problem, is...

--- DON'T PANIC ---

Panic is an emotional response, and is the enemy of logical, rational thought.

It clouds good judgement... and may lead you to make BAD DECISIONS. Which will likely lead you to make a BAD SITUATION... WORSE:(:(:(.

Don't make any rash, uninformed decisions. It's understandable you want to get your Nexus 7 working again... but do some research first. Review your options. Read... and understand what you're doing... before you do it.

Carpenters and people who work with wood, have an old saying...

~ "Measure twice, cut once." ~

This axiom, I feel, is just as true and applicable to technology as it is to making chairs, tables and putting up a set of shelves:).

Use XDA... If you've got a given problem, chances are good, somebody has had it before you, or has it now. A solution may already have been posted.

Use the XDA search engine... or go to Google search, and type "XDA ..." followed by some keywords that distill the essence of your problem.

I've never known Google search to NOT display something that might be pertinent to an Android problem... and usually it's almost always XDA that comes at the top of the Google search results.

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

Right... I'll shut 'up now.. I've waffled on far too long. And I don't want to earn the ire of the moderators for taking this thread wildly off topic:).

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] jeep447:
OK well if you don't mind I'd like to pick your brain too :D. I am without a doubt no stranger to Android, rooting, custom roms, and so on, however this is my first experience with the nexus 7 (or with tablets in general for that matter), so there's just a couple of things I'd like to clarify if possible. I recently got a great deal on a 2012 32gb Nexus 7 WiFi, but I guess one reason why it was a great deal is because it came with 4.1.2 lol. So I have successfully unlocked the bootloader, rooted it, and flashed cwm recovery to it using wugs toolkit (what a great tool by the way!), and I originally assumed from this point on that I'd just be flashing custom roms like normal. After reading around for awhile I guess I must've confused myself, because now I'm not really sure what the "best" route to take would be anymore. First of all would I really need to flash every ota and build all the way up to 4.4.2 like described earlier? I found another thread that shows how to extract the boot, system, and bootloader images from the 4.4.2 ota off of Googles site, and then you could use wugs toolkit to flash them without losing data, would that work though considering I'm only on 4.1.2? Or should I just do all of the ota updates that pop up until I'm up to 4.4.2? I guess what I'm asking is what would be the best and or easiest way to get from 4.1.2 all the way to 4.4.2? I'm not concerned about losing data whatsoever just to clarify because I just got this so I haven't done hardly anything with it yet. I'm just under the impression that I can't even flash a 4.4 custom rom considering how old the version is on this, but I'm not sure if that's even correct or not.Anyway I'd really appreciate any insight or suggestions you might have because the last thing I want to do is rush into something and cause twice the work for no reason lol.
[G2 Q&A, Help & Troubleshooting] TheTanker23:
Just wondering if this is even possible? The black and white notifications on the moto x look so sleek.
[G2 Q&A, Help & Troubleshooting] compumasta:
If I'm not mistaken it wouldn't work right because this is an ips display. The moto x is an oled display. Difference is that the x can turn on just those individual pixels needed for that notification while the rest remain completely off. With ours, the whole screen would have to be lit up (although in black) which would make it drain far more battery.
[G2 Q&A, Help & Troubleshooting] Higgins12:
You could use Knock2 which does almost the same. Although impact on Battery will be higher for sure.

But you can try it at least https://play.google.com/store/apps/details?id=com.knock.knock.demo
[G2 Q&A, Help & Troubleshooting] truckroot:
Dynamic Notifications works pretty good.

Sent from Verizon logo plastered G2 bastard
[G2 Q&A, Help & Troubleshooting] lazer77:
Or, try this?

http://xdaforums.com/showthread.php?t=2436473
[G2 Q&A, Help & Troubleshooting] DesertHawk:
Use OmniROM. It's built in
[G2 Q&A, Help & Troubleshooting] NyPlaya513:
gimme some of that carbon rom goodness. active display in the rom settings
[G2 Q&A, Help & Troubleshooting] bigfau:
http://xdaforums.com/showthread.php?p=44360028
[G2 Q&A, Help & Troubleshooting] TheTanker23:
Thanks for the replies. I'll have to try out active notify and the dynamic notifications for now until I root and can install a custom rom.
[Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin] pranoy407:
Hi guys,

I'm facing a strange problem, if I cover my proximity sensor then the volume decreases and profile gets switched to vibration mode. I don't know whether its a feature or what, but everything is disabled under "Motions and gesture". I tried flashing stock rom with odin but problem still persists. Any help ? :(
[Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin] asifcheer:
Did you restore your apps after Odin flash....?
[Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin] pranoy407:
No.. also no 3rd party apps installed..
[Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin] asifcheer:
Download your firmware from www.sammobile.com and make sure you have given the correct country specification....
[Nexus S General] nstant:
Well ive made my switch to the Galaxy S4. Nice knowing everyone in the NS forums, Thanks for all the help and all the great people who have done great things in this sections
[Nexus 4 Q&A, Help & Troubleshooting] Luke00123:
Hi I installed a custom ROM to my nexus 4 but after I did this and rebooted it said I was on a roger's network. What is heppening? Can I still use it? Will I be charged differently?
[Nexus 4 Q&A, Help & Troubleshooting] ziddey:
Fido = Rogers
[Nexus 4 Q&A, Help & Troubleshooting] Luke00123:
Thank-You

Thank-you very much! I was a bit worried.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] KTamas:
I think this deserves its own topic. Original post from Tuatara:

For further information and download, visit the WiKi.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] KTamas:
Personal thoughts: I think this ROM gives some performance boost indeed, not much, but it is noticable. Nearly every bug is fixed now, only the bluetooth disconnect issue is left. My BA is fianlly shows itself disconnected when i take it off the cradle (with the previous ROMs, it often showed that it is still connected).
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] paullim29:
Enabling SmartDialing

Hi, I've tried this ROM & this definitely faster! Thanks!

But I can't seem to enable SmartDialilng by removing the "_" from the mfc80u.dll_ and msvcr80.dll_ files for SmartDial will start to work? These 2 files are missing from this ROM but even after I've copied these 2 files into the \Windows folder, SmartDialing still doesn't work. Any ideas?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] KTamas:
Re: Enabling SmartDialing

I should take a look at one of the early versions of "New menu for WM5" (anything below 1.0.0 beta). Does anyone still have the CABs?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] rschell:
Re: Enabling SmartDialing

Here you go.

paullim29. These correct the problem for me.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] KTamas:
Re: Enabling SmartDialing

Created a cab file and added to WiKi. Thanks.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] deepakr:
Missing MMS client?

Hi,

I s to be missing my MMS client. I see an option for the MMS configuration but am missing the MMS application? Anyone facing this issue?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] KTamas:
Re: Missing MMS client?

Hmm it seems that MMS is broken in this ROM indeed. Will add to WiKi.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] a771la:
mediaplayer still have a problem for playing in background :(

anybody solve this problem?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] KTamas:
You should try a different program, such as GSPlayer or TCPMP.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] a771la:
ok... i use TCPMP

but i want to know mediaplayer don't work on this rom

ok himalaya's rom work for me
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Mr Chicago:
I downloaded the new Rom and having a little trouble trying to download to my SX66. I have upgraded and downgraded the WM5 on my SX66 several times. I was wondering since the rom file is nba instead of nbf does that make a huge difference. I admit have have not messed around with my device data cause I find that a little complicated. I usaully use the MA_Upgrade cause I don't have to tweak too much. Any suggestions?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] KTamas:
In this case, you should use the harder way. Read step 4 of the upgrading process (see wiki) to upgrade via BaUpgradeUt.exe.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] rschell:
The nk.nba file needs to be converted back to nk.nbf regardless of whether you use MA_Upgrade or BA_Upgrade. I use MA_Upgrade. There is an modelid entry of the USER.rgu that should be changed to PH20B1. I'm not sure whether these *.rgu files need to be copied to the \windows dir or added back into the nk.nba file. Any thoughts KTamas, i'm thinking the later.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] KTamas:
You don't have to do anything with RGU files at all. You need to use xda3nbftool (with editfix.bat if you want) to patch the ROM.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] kluggie56:
Hi,

just upgraded to new rom and noticed i can't sync calender and contacts.

anybody has the same?

Gr

Paul
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] KTamas:
Both works well for me...What error exactly do you get?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] kluggie56:
Nothing....that's strange. I'ts syncing, but Outlook has all data and my BA nothing. I've tryed reinstalling all, but no luck, even reinstalled my BA. No luck sofar.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] kluggie56:
Sorry,

Activesync gives the following message,

There is not enough free memory on tour device to synchronise information. Close programs that are free to up memory, or restart the device.

Ondersteuningscode 8007000e

gr

Paul