yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Accessories] icedmayhem:
Actually I believe the issue lies in the control talk cable itself. I bought a pair of mixr and had the same issues as everyone else with an Android phone. Apple devices the wiring is done backwards inside the cable. So I got to thinking about reversing but my soldering skills aren't the same. So I thought maybe a new cable, so I found one on ebay, obviously a 3rd party beats knockoff, where it has 2 black rings on the plug and 3 rings where it gets plugged into the phone. And viola they work perfect all features Inc volume.. See the picture I uploaded and u see what I mean
[Galaxy S III Accessories] saf100792:
I personally wouldn't buy any beats by dres unless u get a large discount. Like almost half. Otherwise you're being ripped off. But I don't believe any control talk headphones work fully
[HTC Droid DNA] t1gartist:
So I decided to be the lab rat and took the update and tried unlocking bootloader and I confirmed this myself I am unlocking and about to flash kernel and root tools I will post in a few minutes wish results
[HTC Droid DNA] cmay227:
It can all be done. did it earlier. all is still good.
[HTC Droid DNA] SAMPCam:
I just did the same thing. I updated the firmware going back to stock via RUU and accepting the OTA Update, and re-flashing my original Unlock_code.bin. Now running ViperDNA 1.1.2 with the new firmware just fine.
[HTC Droid DNA] cmay227:
You do know that since u flashed the venom Rom your back to old firmware?

Check your update the Verizon one will be there again. I did the same thing. Decided to stay stock until venom is updated.
[HTC Droid DNA] binzokun:
does anyone know if I flash the current system write kernel, will it undo any of the new update from the OTA?
[HTC Droid DNA] cmay227:
Not entirely sure, the update flashes a new boot.img, try it and see. U can always revert. It won't hurt anything.
[HTC Droid DNA] SAMPCam:
Not entirely. I don't have the Rom portion of the new update, but the radio firmware and other portions of the update are still there (the underlying framework). But yeah, I'm not making full use of it until I use a 2.04-based ROM.
[HTC Droid DNA] t1gartist:
sadly i tried 10 times last night it would unlock until rebooted and i would be showed locked again to im not sure what the hell
[HTC Droid DNA] binzokun:
tried flashing the system write kernel, and all hell breaks loose. Its gonna take some time for the dev to incorporate all the changes.

Flashed back to RUU for now.
[HTC Droid DNA] uppon2:
Are you certain it wasn't 9 times or 11 times? ;)
[HTC Droid DNA] cmay227:
Turn phone off all the way. Then boot into bootloader and run unlock.bin command.
[HTC Droid DNA] zone23:
Backing up my internal memory guess I'll give it a go what the heck its Friday right?
[HTC Droid DNA] orangechoochoo:
Custom kernels won't work on the update?
[HTC Droid DNA] zone23:
Here are the steps I took YMMV

Backup Internal Memory

Verify Fastboot and ADB Drivers are properly installed

Boot into Bootloader

RUN "fastboot OEM Lock"

Phone reboots

Run RUU as Administrator

Wait

Boot Device

Connect to WiFi

Run Software Update from Settings

Wait

Install Update

Checked for Updates Again (Nothing)

Copy Unlock_Code.bin to your fastboot directory

ADB Reboot Bootloader

Open command prompt from fastboot directly

Run "fastboot unlock token Unlock_code.bin"

Follow the prompts

Reboot bootloader verify unlocked

Place Recovery.img in fastboot directory

RUN "fastboot flash recovery recovery.img"

Reboot

Copy over Rooted ROM

Reboot into Recovery and flash

Profit
[HTC Droid DNA] supertoast92:
Sorry for the noobish question, but will I have to go through such a complex procedure as this if I'm on stock rom, unlocked and rooted? Rooting alone the first time was quite time consuming for me :\

I know I could simply stick with what I have now. I'd really like to have the new firmware though, which supposedly fixes audio and wifi issues.
[HTC Droid DNA] zone23:
My suggestion then would be to wait and see if someone comes up with a way to flash the radios. That is the only reason I went through the process.
[HTC Droid DNA] jc332986:
If I have a backup of stock rooted, do I still have to use RUU?
[HTC Droid DNA] supertoast92:
Will do, thanks!
[HTC Droid DNA] binzokun:
Word of caution people, once you install the OTA update, your HBoot get updated, so the current RUU stops working. Once you apply the update, there's no going back. All custom kernels don't work, I spend all night trying all of them, the phone just stuck at the boot animation.

I would suggest holding out until all the kernels/custom roms/RUUs are updated, cause if anything goes wrong you have very little tools to work with, especially when we don't have S-Off.
[HTC Droid DNA] BBEgo:
That's good to know. Thank you!

Sent from my HTC DNA
[HTC Droid DNA] cmay227:
I Updated last night re unlocked, flashed recovery and rooted. Then flash vipers rom and flashed stock write enabled kernel and all is good. so you didn't try all the kernels.
[HTC Droid DNA] binzokun:
When you flashed vipers rom, you're not longer using the ota stock rom, reverting back to pre-updated firmware so the stock system write kernel works. The incapability occurs between the ota updated rom and the custom kernels. :)
[HTC Droid DNA] cmay227:
Was kinda thinking that. Thanks
[HTC Droid DNA] Sjflowerhorn:
Thanks for taking the plunge for us all. Ill be joining you either in the next hour or so or in the morning. When you have a decent idea you should report back with battery life and radio signals stregnth in the OP, thanks again.
[HTC Droid DNA] t1gartist:
the incompoatible i noticed was the screen flickered a lot about every 5-8 seconds or so

and as far as how i feel about the battery and so far i really enjoy a linaro kernel dsb/palmer mix wide open performance for 30 minutes gpu oc 1890 mhz cpu my battery drained from 80 to 68 so not bad imo i have had phones do way worst (droid x and incredible) now my og droid **** performance all day long no problem to get 16 hrs of battery cranked out

my service is great alot better normal i would have 2 bars of 4g now im full tower and i live in the heart of 4g lol speeds have picked up so im thankful just pissed no s-off lol there is a way and if i can get a s-off on ebay i will find out :D
[HTC Droid DNA] karn101:
S-Off is sold online (the procedure). It's about $60 I believe. There's a thread on it in General.

http://xdaforums.com/showthread.php?t=2017674
[HTC Droid DNA] trickster2369:
Dude, I think your keyboard is broken.
[HTC Droid DNA] Flip35:
Thanx for the heads up, I've been running Viper ROM for a while decided to RUU back to stock n almost took ota, but I decided to hold off and read here. I think I'm going to wait because I know some people confirm rooting with the ota but I don't see the Devs yet updating their thread so I think they're probably want to make sure that everything is right before confirming cuz if something doesn't work properly I don't want to be stuck with the a new hboot and not be able to return to old, that's just me though I'm sure we'll get conformation soon especially I saw somewhere that they had s-off for it
[HTC Droid DNA] CovXX:
If you copy'd over rooted ROM then you wouldnt been rooted on the update...
[AT&T Samsung Galaxy Note II] livingaboard:
on cleanrom and if so which cleanrom. I am running cleanrom 4.0.5 on my daily note 2 and tried the known methods on cleanrom 4.5 on my other note 2.

I would like to know who has wallet running, in the United States, on Cleanrom. If so how EXACTLY did you accomplish this?

The method I attempted on cleanrom 4.5 at least got me to the 'setting up google wallet, this may take 5 minutes" or something before it had the "unfortunately wallet has stopped" or something.

Any help would be appreciated.

these are the instructions I used. from junior member op**********************************************

To start with, I did no real development on this, I just figured out what needed to be changed from the original method discovered by WarlockLord. All credit for this goes to him. See his thread at http://xdaforums.com/show....php?t=2031127 for more details.

I searched through the CleanROM topic (non-Verizon specific) and only saw people saying they wanted a way to get Wallet as the original method did not work for CleanROM, so I apologize if this was discovered already. I wanted to use CleanROM and Wallet so I played with it for a while and found out how to get it working.

1. Either extract the Wallet APK from WarlockLord's ZIP or download it from below.

2. Copy it to \system\app\ and give it permissions of rw- r-- r--.

3. Modify your build.prop to represent the Galaxy Nexus with the info in the original thread.

4. Reboot.

5. Open Wallet and do the setup of the account and card(s).

6. Modify your build.prop back to original settings.

7. Reboot.

After this it continues to open the app and keeps the selected card, I haven't attempted to make a purchase with it yet but it functions the same as it did after following the steps in the original method so I presume it would work the same afterwards. ***********************

****************************************************************************************************
[Verizon Samsung Galaxy Note II] bigdade:
How can you remove the write disk permission from the card so you can transfer files bigger than 2 GB? Any help will be appreciated.
[Galaxy S III Q&A, Help & Troubleshooting] SalTNutz:
I live in a refarmed area (jacksonville) and I just switched to tmobile today. I can't get anything but EDGE. Is there something i should have to do to make my i9300 use TMobile on the 1900mhz band?
[Galaxy S III Q&A, Help & Troubleshooting] alankstiyo:
I9300 can get only 2g data over tmobile, not sure if it will change when they change their infrastructure,

I can just say you sir made a huge mistake hehehe
[Galaxy S III Q&A, Help & Troubleshooting] SalTNutz:
So, that is not true. T-Mobile, in an effort to steal some of the unlocked iPhone business from ATT, has been moving "refarming" their 3G/4G network to the 1900mhz band, which is what ATT uses for 4G. So, if you live in an area that has been refarmed, which I do, any phone that works on ATT's 4G HSPA network, should get HSPA from T-Mobile.

With that said, I am only getting EDGE, and I live in a refarmed area. So, does anyone knowledgeable on this subject know if there is anything I need to do to my phone to make it use the 1900mhz band with T-Mobile?
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
A guess modem and CSC compatible for TMobile .

jje
[General Questions and Answers] Pkb2003:
hello

I want ics rom for my karbonn a7+. if anybody have plz provide link.

thanks
[General Questions and Answers] prasad12ka4:
Use the search option before you post mate..

There is a A7+ development thread here which has the ROM
[General Questions and Answers] manav113:
here is the link

http://www.mediafire.com/?aqvnuoe6uv1z158

ENJOY...:cyclops::D:D:):););)
[Nexus 7 Q&A, Help & Troubleshooting] williamlaw:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....

after reboot from TWRP, it still 4.2.1 ......

what happened ?? how to fix it ??

Thanks
[Nexus 7 Q&A, Help & Troubleshooting] .torrented:
you probably need stock recovery to complete the update... I would just wait for someone to root the update and then flash it that way
[Nexus 7 Q&A, Help & Troubleshooting] phonic:
While your post doesn't make much sense, I assume you ran into the same issue I did on my N73G.

If so, you have a 90% upgraded tablet. All of the system and kernel patches applied, but it got stuck on the radio firmware update. For some reason, this also breaks the bootloader update (for me at least) right before the radio, even though it said it worked. The reason why your tablet still shows 4.2.1 is because the build.prop change, which shows what version you are on, is after radio and didn't get applied.

Without going into too many details, you are a bit stuck. You can't reapply the OTA because it will fail the system asserts now that they were already patched. I would suggest downloading the FULL 4.2.2 IMAGE from Google here:

https://developers.google.com/android/nexus/images#nakasig

And do the following:

adb reboot-bootloader

fastboot flash bootloader (new bootloader file)

fastboot reboot-bootloader

fastboot flash recovery (new recovery file)

fastboot flash radio (new radio file)

Then reboot into recovery mode and let the stock recovery apply the radio firmware update.

You need the stock recovery to apply the radio firmware. Custom recoveries (at least some/most/all) don't support the bach_update.modem function. You can go back to TWRP after you upgrade.

The instructions above will fix everything BUT the build.prop file, which will still be the 4.2.1 version. You can either fastboot flash system with the 4.2.2 system image, or get a copy of a 4.2.2 build.prop file and replace yours with that. Or if you are creative, you can modify the OTA update, remove everything BUT the build.prop patch and apply that manually (but I wouldn't suggest this unless you know what you are doing).

Also, in the future, [Q}s should go in the Q/A section.
[Nexus 7 Q&A, Help & Troubleshooting] williamlaw:
is this problem caused by flashed kernel ??
[Nexus 7 Q&A, Help & Troubleshooting] phonic:
Did you not bother to read anything I wrote?
[Nexus 7 Q&A, Help & Troubleshooting] grieshmp:
I had the same problem. If you have a TWRP backup from a previous android version that allowed the ota to work just flash that and you'll still receive the ota for 4.2.2
[Nexus 7 Q&A, Help & Troubleshooting] iElvis:
This happened to me too, though I have the wifi-only version. So it's not just the radio.
[Nexus 7 Q&A, Help & Troubleshooting] codmaster:
I got the same problem with my Wifi version. Is there any fix yet? I only rooted the device but the rest is still stock. How come the update failed?
[Nexus 7 Q&A, Help & Troubleshooting] rexxxxx:
the same here - stock and rooted only WIFI version.

During install gave ERROR and after manual reboot - now is shows 4.2.1 version and there are not new system updates.

any solution ?
[Nexus 7 Q&A, Help & Troubleshooting] spiou:
Got the same problem and I think it was caused by stick mount.

The app seems to modify the "debuggerd" file in system/bin.

Problem solved by replacing the file by the original one.
[Nexus 7 Q&A, Help & Troubleshooting] williamlaw:
finally flashed back to stock 4.2.1 then OTA update 4.2.2
[Nexus 7 Q&A, Help & Troubleshooting] rexxxxx:
how ? I indeed have the mount stick installed for the OTG cable !
[Nexus 7 Q&A, Help & Troubleshooting] spiou:
Someone posted the original file here : http://xdaforums.com/showthread.php?t=2145265

You can replace the file simply with es file explorer :)
[Nexus 7 Q&A, Help & Troubleshooting] JohnRM:
I'm also in the same boat as the OP.

OTA came down, installed fine, rebooted which went into twrp, tablet still says 4.2.1.

So, is there any way of doing this without doing a wipe ? Or losing any of your data ?

What about putting the update, downloaded from google, on a USB stick and booting into twrp then flashing from there ?

I don't mind losing root, although I have rootkeeper installed, and I don't mind losing custom recovery, all of this can be fixed.

I also have the trinity kernel installed, so will I lose this as well ? Again, don't mind since I am about to test the m-kernel, anyway.

What I don't want to do is lose my data. I have plenty of full twrp backups done, but then these are 4.2.1 backups. Backing up my apps isn't really feasible at the moment because of their sheer size. Horn, NOVA 3, the GTA games, bards tale, all gigs and gigs of data. Infact, I only have 1 gig left on a 32Gb N7, and I just don't have anywhere left to put a full backup of apps on to. I also don't want to download them all again, NOVA 3, for example, took me 6 hours to download on wi-fi.

I have read a lot of advice and help on here, plenty of googling which simply sends you back here anyway, and most advice centers around losing your data in some way. So, any help without losing data would be most appreciated,
[Nexus 7 Q&A, Help & Troubleshooting] rexxxxx:
Done this but the problem remain.

About menu shows 4.2.1 and there is no system update for me.

I think update go trough and it changed some files and now these files tells the system update that I am with newest version.

Any solution for this. How to make the system update think that I need an update?
[Nexus 7 Q&A, Help & Troubleshooting] sharpt71:
After reading many threads and articles, I finally upgraded to 4.2.2 with stock recovery. Your mileage may vary.

Based on the discussions on http://xdaforums.com/showthread.php?t=2148456, the failure may be caused by an app you installed

that corrupted some system files. Therefore, you have to flash 4.2.1 stock system and boot images back. The nice thing is your data and settings remain intact.

Although you lost root, it can be easily re-rooted using nexus root toolkit.

Now you're back to 4.2.1 which is allowed to upgrade, use OTA RootKeeper to keep su and then upgrade thru OTA. If you can not longer get OTA, you can clean data/stop/start Google Framework service, Google play service, and Google play store, and then re-check update. The last tip I read it somewhere but I forgot where I read it.:confused: Sorry.

Good luck. :laugh:
[Nexus 7 Q&A, Help & Troubleshooting] khaytsus:
Which part of STOCK is unclear? You cannot use OTAs unless you are STOCK. That means stock ROM contents. Stock kernel. Not twiddled with, not renamed, not deleted, not modified, not OverAmplifiedWithSuperBaseBoostLOLZKewlBeatsified, etc.....
[Nexus 7 Q&A, Help & Troubleshooting] spiou:
You must clear the data of the Google framework (in the list of apps) and reboot immediately the tablet. Then the update will be proposed again.

One more thing : when you replace the file, check that the permissions are identical.
[Nexus 7 Q&A, Help & Troubleshooting] phonic:
Exactly. I don't understand why we need to see posts like that over and over and over again. Hell, the OTA update will even tell the user what failed, and yet people still complain and ask what's wrong.

Also, while in most cases a custom recovery is OK (though the update will overwrite it), with the N73G unit, you need to use the stock recovery, otherwise it will fail without warning ahead of time.
[Nexus 7 Q&A, Help & Troubleshooting] digixmax:
Can you elaborate? E.g., where do you get the original debuggerd from, how do you replace it (adb push?), etc.
[Nexus 7 Q&A, Help & Troubleshooting] wtek:
I think he provided the link to the original debuggerd file, but here it is again: http://xdaforums.com/showthread.php?t=2145265

I also had to install root browser lite app from the app store to be able to write to /system/bin/ and replace the debuggerd file in there already. Managed to update to 4.2.2 successfully after that.
[Nexus 7 Q&A, Help & Troubleshooting] digixmax:
I went to Settings->Apps, and only found "Google Play services" and "Google Play Store" but no "Google framework".

Am I looking at the wrong place?
[Nexus 7 Q&A, Help & Troubleshooting] spiou:
I think the exact name is framework service (sorry but i'm French). There are a lot posts talking about this trick, including this one :http://xdaforums.com/showthread.php?t=1937183
[Nexus 7 Q&A, Help & Troubleshooting] ubervince:
You need to scroll to the left so that you are showing 'All', then look for 'Google Services Framework'. The debuggerd trick worked great for me BTW.
[Nexus 7 Q&A, Help & Troubleshooting] JohnRM:
Thanks for acting a TWAT. The net is full of extremely conflicting info regarding the upgrade. Some are saying as long as your ROM is stock then everything else - recovery, kernel - will get overwritten to stock recovery, stock kernel, something as I said I would be ok with. But as usual with this place there are some that expect the rest of us to read 5 thousand pages of answers that also conflict with each other while never giving a direct answer. There are also threads everywhere, so again I just don't have that kind of time to go through them all.
[Nexus 7 Q&A, Help & Troubleshooting] khaytsus:
You're welcome ;)
[Nexus 7 Q&A, Help & Troubleshooting] styckx:
He was firm and accurate, not a twat.

P.S. ROM includes a kernel.. You can't have a "stock rom" with a modified kernel (Trinity).. That renders the ROM not stock now.. Stock isn't ambiguous. It's all or nothing.
[Nexus 7 Q&A, Help & Troubleshooting] phonic:
While that is technically true, most people consider a custom ROM a complete package including a different kernel, system image, etc.. Many people will keep a stock system and just replace the kernel and/or recovery. Under the latter circumstances it's trivial to swap custom and stock out, which means even if you have a custom kernel you can easily restore back to stock and use an OTA upgrade. Not so easy with full custom ROM's.
[Nexus 7 Q&A, Help & Troubleshooting] rthisp:
Phonic, I had a 4.2.1 device with TWRP installed. The OTA obviously failed;

So, I flashed stock ROM, did that framework trick, updated via OTA and root manually. I did not installed any custom recovery.

Can I assume I have a 100% stock ROM,even with root ?

My device is a Nexus 7 32gb 3g (no radio problem...)

Enviado do meu PC mesmo...
[Nexus 7 Q&A, Help & Troubleshooting] chimpanzeexda:
If you take a look at what the OTA update package contains, there would no longer be confusion of what is stock or not(from the OTA perspective)

It is a patch system with specific checksum for the file it attempts to patch. The only way they can generate these checksums are to base them off the prior released version(why OTA must go from version to version and not say 4.1.2 directly to 4.2.2)
[Nexus 7 Q&A, Help & Troubleshooting] rexxxxx:
so guys I have a development on my case.

today out of nowhere the update to 4.2.2 showed again.

I haven't done nothing in the couple of days and the last I did was to copy the 2 files debuggerd and build.prop. After i replaced them and restarted the update was not available.

now I got the Update again.

Can you advice me how to proceed so I don't receive the error again. Should I uninstall StickMount ?

thanks
[Nexus 7 Q&A, Help & Troubleshooting] Leonhan:
As it was stated before in numerous threads, if your rom's stock files has been tampered in any way, you should flash the old stock files back, then you can proceed with the update with no problems.
[Nexus 7 Q&A, Help & Troubleshooting] rexxxxx:
I didn't tampered it anyway - but maybe the program SrickMount changed some files.

Also I have another question - if I go and update and everything is successful - I have to root the device again - right ? and also when I root it will my data be deleted.

I am asking because my Nexus 7 32 Gb is almost full.
[Nexus 7 Q&A, Help & Troubleshooting] phonic:
If the original OTA update failed and you flashed back to 100% 4.2.1 stock and reapplied the 4.2.2 OTA update (with stock recovery), then yes, you should be good to go.

Root is irrelevant, at least from the OTA point of view. While it will strip su of it's suid root capabilities, it doesn't care if it's there. Userdata is also irrelevant. You need to be stock system, kernel and recovery.

Once the OTA update completes, you can flash TWRP back.

Also, you can easily regain root by going into custom recovery, mounting /system, and then going into 'adb shell' and typing:

chmod 6755 `which su`

(those are single ticks under the tilda on your keyboard).

Assuming your build.prop says 4.2.2, that will validate the OTA completed since it's the last step. If it still says 4.2.1, something broke.
[Nexus 7 Q&A, Help & Troubleshooting] Wayno-san:
My OTA just says "Error!"

Received the OTA update and it fails with a dead android and a red triangle and just the message "Error!" below it. No other codes so I have no idea why it failed. Just uninstalled stickmount and copied over the original debuggerd file back into /system/bin and set the file permissions accordingly but it still fails the same way.

I didn't mess with the ROM or bootloader/recovery at all but the Nexus 7 is rooted.

What's the best way to get 4.2.2 without losing my data?