yashsingh1/xdaforums huggingface dataset:
[Windows Phone 8 Q&A, Help & Troubleshooting] MauzaoFilho:
Try to update your system to version GDR2, I think this is a problem of incompatibility between the interop unlock with the GDR1 and FS.
[Windows Phone 8 Q&A, Help & Troubleshooting] Randοm Hero:
Are you running software on the PC that interacts with the phone (eg windows media player syncs, etc.)? If yes, turn that program off.
[Windows Phone 8 Q&A, Help & Troubleshooting] sandro1900:
No, everything is turned off.

My problem now is: can I directly update my device to GDR3 - now I have GDR1 - while preventing the interop-unlock ?

Thanks
[Windows Phone 8 Q&A, Help & Troubleshooting] Randοm Hero:
I think first you have to update to GDR2, then GDR3 (someone confirm this, please). If you Interop-unlock GDR2, then yes, you can indeed prevent your phone from unlocking, using the SamWP8 Tools & following the instructions in this thread
[One (M7) Q&A, Help & Troubleshooting] affu2004:
i need RUU for my HTC one x.xx.415.x – Arabic (UAE/Middle East) anyone can help me i will be thankful
[One (M7) Q&A, Help & Troubleshooting] nkk71:
can you post a "fastboot getvar all" (excluding IMEI and s/n); on the M7 the GCC version seems to be the .401. edition
[One (M7) Q&A, Help & Troubleshooting] affu2004:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.54.0000

(bootloader) version-baseband: 4A.18.3263.15

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.24.401.8

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: SH

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__J15

(bootloader) battery-status: good

(bootloader) battery-voltage: 4236mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-d959c75800

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.046s
[One (M7) Q&A, Help & Troubleshooting] raghav kapur:
Ur phone is the .401 firmware. Even mine which i bought from UAE. Flash this:

http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/

Ive flashed this nd given my phone fr repair also. Warranty is valid in Middle East fr this RUU
[One (M7) Q&A, Help & Troubleshooting] nkk71:
what do you need to achieve? (ie what's your ultimate goal?)
[Nexus 7 (2013) Q&A] photonate:
Hey all, long time lurker and first(ish) time poster. I have a Nexus 7 (2013) that is great, except for a problem I've been having upgrading from 4.4 to 4.4.2. I am unlocked and rooted, and have the latest version of TWRP installed for the device (flo).

The problem originally started with the OTA. When the OTA would come down and I would click it, it would boot into TWRP and then just restart without installing anything. I attempted this five or six times before trying something else. From there, I downloaded and attempted to install manual update zips for the Nexus to take it from 4.4 to 4.4.2. When I would try and install these, it would say "error executing updater binary in ...". I have tried downloading the updating zip from multiple websites, and I've checked the MD5's, which always match up.

I'm sorry if this is a stupid question, but where can I go from here? I've exhausted my knowledge of what other possibilities are out there, or what could be causing the update to fail.

Thanks!
[Nexus 7 (2013) Q&A] TheAltruistic:
If the stock finds that any system files have been altered and the md5 check is different from what it should be, a OTA stock update will not go through.

In my personal opinion, flashing a stock root / unrooted image found in the development section of these forums is one of the easier ways of applying an update.

For example if you want a rooted one here's one: http://xdaforums.com/showthread.php?t=2563017
[Nexus 7 (2013) Q&A] wantabe:
TheAltruistic is right, that is probably the easiest way to get updated. Another option would be to download the 4.4 factory image and pull the system.img from there and flash that with fastboot then the OTA would work. But really if you go through that you might as well flash the 4.4.2 factory image. I'm not a huge fan of doing the OTA and would rather flash factory images while skipping the userdata image which wipes the device.
[Nexus 7 (2013) Q&A] oldsoldier2003:
/agreed

from the factory image:

Open flash-all.sh (linux) or flash-all.bat (windows) in a proper text editor (for windows users edit++ is a proper editor- linux people can use their editor of choice):

Find this line:

fastboot -w update image-razor-kot49h.zip

change it to

fastboot update image-razor-kot49h.zip

and it will leave your user data intact
[Nexus 7 (2013) Q&A] wantabe:
You're right, thanks for pointing that out! I've done that before but I'm so used to flashing the images separately I forgot about it for a minute! ;)
[Sprint Samsung Galaxy S III] vaddekittu:
hey all,

i recently updated my sprint galaxy s3 to rooted cNexus stock 4.3. few months back i restricted background data for few apps to conserve mobile data while i was 4.1.2. now i want to remove those restrictions. but it looks that option is disappeared after the update. i attached few screenshots to show u the issue. as you guys can see there is no option to set/remove the the background data. i am banging my head to remove those restrictions as i cannot receive hangout messages while am on mobile data. i am hoping u guys can help me. let me know if u need more info.

thanks in advance.
[Sprint Samsung Galaxy S III] vaddekittu:
any help? if anyone has 4.3 rom, can u tell me if u can see the option to enable background data?

does anyone know where does android store the restrict background data settings? i am trying to see if can manually modify them.
[Sony Xperia T, TL, TX, V] nreuge:
Requirements : rooted & deodexed

Instructions : Backup first and flash the attached zip via CWM.

Credits :

[MENTION=4694376]DavidMKD[/MENTION] for his tutorial

[MENTION=4555495]kongaz2[/MENTION] for the mod for TX
[Sony Xperia T, TL, TX, V] PeterGeorgiou:
Mate, i don't get the point of this..please explain :-s
[Sony Xperia T, TL, TX, V] nreuge:
After applying this mod you can install apps with different signature like Xperia Z1 or newer Sony apps or custom themes, for instance the niaboc79's HeXaReD theme.
[Sony Xperia T, TL, TX, V] Midleo:
It is very good thing, but can you make it for TX to?!
[Sony Xperia T, TL, TX, V] nreuge:
It might work for TX. If you use the leaked rom 4.3 for TX, try it and let me know if it works. I think it will.
[Sony Xperia T, TL, TX, V] Midleo:
Perfect!!! I just tried on my SXTX JB 4.3 deodexed (DaRk L0rD)... after flashing coming the bootup with update everything working then i installed HeXaReD v1.0 theme which need patched services.jar and its work perfectly!!!

You can change your thread for: [MOD][T/TX][4.3][.278/.131] Patched Services.jar
[Sony Xperia T, TL, TX, V] nreuge:
Thanks for the feedback mate :)
[Sony Xperia T, TL, TX, V] seeker07:
is it work on .295?
[Sony Xperia T, TL, TX, V] nreuge:
Don't know. I won't test it, I'll update the mod from the .295 file.
[Sony Xperia T, TL, TX, V] seeker07:
ok it's not working for. 295

waiting for the update
[Sony Xperia T, TL, TX, V] Amiga4ever123:
Same here. Doesn't work on .295 :/
[Sony Xperia T, TL, TX, V] nreuge:
Thanks for the feedback, but I won't update till we can get the .295 update (rom+kernel) with full operational CWM.
[Sony Xperia T, TL, TX, V] kongaz2:
hi. i have maker for my Xperia TX based 9.2.A.0.295 :) :)

http://d-h.st/BlS
[Sony Xperia T, TL, TX, V] y9420045825:
Good job

It is so convenient ~

Thank for your work :fingers-crossed::fingers-crossed::fingers-crossed:

Can I use it in my ROM? :cowboy:
[Sony Xperia T, TL, TX, V] randymess:
You know if this is working on T?
[Sony Xperia T, TL, TX, V] nreuge:
You can,just give credits. ;)

I don't know, it might. Anyway, I'll do a update for T in 1 or 2 days.
[Sony Xperia T, TL, TX, V] nreuge:
Update 24/02

Mod updated for the last stock T&TX roms 4.3 (.295)
[Sony Xperia T, TL, TX, V] Leo:
hey smart guys~

have u ever considered an odex one ?
[Sony Xperia T, TL, TX, V] randymess:
And... have you ever consider moving to a deodex rom? It is way better than odex, that's why, usually, there is no support for ODEX.
[Sony Xperia T, TL, TX, V] nreuge:
That's true :good:
[Samsung Galaxy Nexus] Namtaru:
Thanks for your roms, they have been the daily driver on my wifes GN since you started posted them way back when.
[Samsung Galaxy Nexus] kielby:
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.

The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.

Any ideas?
[Samsung Galaxy Nexus] baldwinguy77:
Are you sure it's only when plugged into a wall charger? If that's true, it sounds like a hardware issue, but I think you probably just happened to notice it at that time. You may want to try out the 1/4 build as that one seems to work well for people with mobile data-related problems in the newer builds.
[Samsung Galaxy Nexus] hotrodwinston:
How did you flash the radios? Also are you using any mods/3rd party kernels? First step in fixing radio issues for me is to restore back to stock - this makes sure good radio files get installed then after allowing to settle for 24 hours I flash back to a custom Rom then checking without installing any mods for a day.

If unsure that radios flashed cleanly or having strange signal issues that make no real sense it is a good idea to try stock install.
[Samsung Galaxy Nexus] kielby:
I flashed the zip files from this thread using CWM before flashing the ROM the first time. I'll try going back to stock for a couple of days to see if it fixes the issue.

To the previous poster, I'm pretty sure it's related to charger somehow. My wife started complaining that should couldn't reach me on my cell during the work day (hmm is this a *feature* or a bug?!). I was sitting at my desk during those times with my phone plugged in. I tried calling the Nexus from my desk phone and it wouldn't ring until I unplugged it. It only started after I flashed the new radios and ROM.

Thanks guys.
[Samsung Galaxy Nexus] kielby:
By the way I reflashed the 4.1.1 (JRO03O) radios from radio thread without changing anything else and the problem seems to have gone away.
[Samsung Galaxy Nexus] Mineturtle33:
What kernel should I use with this ROM to get the best performance/battery life combo. Link please! :D

Sent from my 2013 Kindle Fire HD
[Samsung Galaxy Nexus] RoxRedEye:
Is an upgrade to KVT in the works?

UPDATE -- I'm running the latest version with the latest franco and Xposed Framework and - wow. Rock stable, fast and melted chocolate smooth (boom - trademarked.) I don't know why I haven't done this sooner. This is all I need for awhile. Truly happy with my GNex at this moment haha.
[Samsung Galaxy Nexus] baldwinguy77:
Hey there! I'm sorry, somehow I missed your post earlier! Anyways, glad to hear you're liking the ROM so much :D There is an updated build available as of today so check the download post. More info is coming in a few seconds ;)
[Samsung Galaxy Nexus] RoxRedEye:
No worries. Thanks for the reply and thank you for your hard work bringing us a stable stock KitKat. Glad I have extra batteries with me - gonna download and flash asap.
[Samsung Galaxy Nexus] klobkelosh:
Hey [MENTION=2393080]baldwinguy77[/MENTION], can't access rootz right now, but was systemui.apk updated for today's build? I have a home cooked mod from last version that I'd like to use. Thx
[Samsung Galaxy Nexus] asilentcivilian:
ART isn't sticking when I change from dalvik. I flashed on top of the last build. Did not do a full wipe yet.
[Samsung Galaxy Nexus] asilentcivilian:
full wipe did the trick. thanks for keeping this ROM alive!
[Samsung Galaxy Nexus] baldwinguy77:
Hmmmm I would just give it a try, I think it will probably work fine especially if it only modifies SystemUI :)

Glad to hear it! Thanks for your support! :)
[Samsung Galaxy Nexus] klobkelosh:
Yes it worked fine, thanks for the response. Unfortunately, this build is not very nice to my battery :(
[Samsung Galaxy Nexus] baldwinguy77:
Glad to hear it! I would give it some time before making any conclusions; charge it up tonight, grab it in the morning and see how it is with normal use :)

If you want, you can put the APN refresh delay back to its value from the previous build. To do this, you need to be rooted so that you can edit the build.prop. You simply have to remove this line:

persist.radio.apn_delay=5000

I don't think it should be making a big difference, but that's the only change that could (in theory) have some effect on battery life. Of course, removing that line may come at the price of having longer/trickier data handoffs. Unfortunately, Verizon's network certainly isn't making it easy for us to give everyone good battery life and good data handoffs :(
[Samsung Galaxy Nexus] klobkelosh:
I'll take that under consideration, but man it was really killing me. Following new rom flash, for everything set up, charged up to 100 percent. Good. Drive to dinner, 30 mins, in and out of 4g and 3g, battery at 80 percent. After 2 hour dinner on 3g, 60 percent. Back home 40 percent, lots of hand offs. She's nearly dead now and I haven't even used her tonight. I love this ROM, but she's not right...
[Samsung Galaxy Nexus] V1215:
Slight issue a few days in, albeit kind of minor. So, upon flashing, I used the updated bootloader addon in the first post (out of curiosity). When rebooting, my Nexus tends to fall into a bootloop (easily corrected with a battery pull, but still troublesome). I'm only attributing it to this because it seems the only likely cause, so - is there any way to remove this addition, or will I have to reflash?
[Samsung Galaxy Nexus] ThePhantom97:
I noticed this too a few times. I just thought I was alone because no one else mentioned it...lol. I don't have the add on.
[Samsung Galaxy Nexus] RepeatUntilTheEnd:
Would it be possible for changes to be made to enable mirroring as described in this post? http://xdaforums.com/showthread.php?p=54062732
[Samsung Galaxy Nexus] mastertech007:
Had this gone dark?
[Samsung Galaxy Nexus] Maximinus I:
It's not dark there really isn't anything to be added until android l drops. There a post from Baldwinguy about 3 pages back explaining it. It has always worked flawlessly for me.
[Samsung Galaxy Nexus] RW-1:
Hi all,

For anyone following shiny or BWG, not much occurring, Baldwin has decided to concentrate more on other aspects of his life, which is fine and understandable, if significant things occur with Lollipop, he may or may not decide to return to something for us. That's up to him, and we'll need to respect that either way.

However it appears that it was more popular with the Rootzwiki thread (for VZW toro) than over here, whereas members had been discussing any issues they have on the current build, other builds, and following FML for VZ toro, as that seems to be the next hot thing for us :)

Rootzwiki appears to have been sold and abandoned, and on the corresponding RW thread I've recommended shiny members still rocking it to come here, myself included.

Just on case anyone wonders why the influx of people to it. :)
[Samsung Galaxy Nexus] Winkz7:
Thanks for keeping the "Dream Alive"...
[Samsung Galaxy Nexus] gtdriver0036:
Thanks for the link Marc. I'll keep coming around in the off chance a lollipop build drops. Till then, back to my regularly scheduled Nexus 6 programming.
[Samsung Galaxy Nexus] Dirty_Jerz:
So I used a bunch of MWizBest's commits and I finally got shiny ported to 5.0. As of now not much works. And all of the gapps need to be updated and radio doesn't work yet but it did boot. I guess it's more of a kang of FML and shiny 4.4 but with the old ddk, the camera works. Gonna work on it later this week if I have time. What is the best way to get in touch with baldwinguy? I have a few questions about how he originally made shiny.
[Samsung Galaxy Nexus] zzpianoman:
That's great news! How did you get it to boot with the old drivers? I've been trying to get it to work, but I keep getting some kind of bad address error when it tries to init the egl libraries.
[Samsung Galaxy Nexus] Dirty_Jerz:
I used the pvrsrvinit instead of the pvrsvrctl and called it in init.d the way mwis did. only instead of it pointing to the PVR that gets compiled inline (new ddk). it uses the imgtec vendor libs. It's here: commit. I think the only repos that need to differ from MWiz's were device/tuna (lots of changes), device/toro, kernel/sam/tuna, and vendor/samsung. It really helped having a UART cable when it wouldn't boot past the google splash. Also, I added the option to disable selinux from the cmdline of the kernel but that also required a small change to system/core (reverting this). That ruled out any selinux problems.
[Samsung Galaxy Nexus] zzpianoman:
Brilliant! I had similar idea - messing around with pvrsrvinit (even trying to use the old pvrsrvctl linker, but it wouldn't execute because of PIE error) but I think I was using the wrong vendor libs. I'll give it another go and see if I can finally get it to boot.
[Samsung Galaxy Nexus] Dirty_Jerz:
So how do i update vendor/shiny to 5.0? Just backup the apps on MWiz's 5.0 and extract the libs? there must be an easier way.
[Samsung Galaxy Nexus] zzpianoman:
Are you referring to google apps?
[Samsung Galaxy Nexus] Dirty_Jerz:
yep, baldwinguy had them baked in and removed a bunch of the AOSP ones.
[Samsung Galaxy Nexus] zzpianoman:
Ah yes. I remember having to remove a lot of them when I ran Shiny a while back. I prefer the bare minimum of google apps and then install them later as needed. I'm wondering though, that since there is no Xposed yet for ART, if having a purely stock ROM is the best way to go for Lollipop. I know there are certain things that I miss like volume button wake, or the ability to customize the navigation bar buttons - although I've been using UDN pro whenever I'm on ART.
[Samsung Galaxy Nexus] RW-1:
Boy, you two have been busy!
[Samsung Galaxy Nexus] zzpianoman:
I've got an "almost" working port of FML with the old GPU drivers. Camera and Youtube both work. Just trying to fix some kernel side issues with data connection and bluetooth.
[Samsung Galaxy Nexus] RW-1:
Now that's something ! :)

There's only so much Kerbal and Left 4 Dead that I can play this weekend .... hehehe
[Samsung Galaxy Nexus] Dirty_Jerz:
I'm right there with you....data issues. I cherry-picked all of the recent commits dc95fe5^..ea92ab8 and f77b58d. booting now so we'll see how it goes. I know the camera works, which is what I was going for, and it's booting so almost there. :D

UPDATE: Data works. Use the libsec_ril_lte.so that MWizBest modified in his vendor/samsung repo. I'm gonna put the Shiny port on hold and push the branches for this fml fork. There is still a few things to cover Bluetooth and NFC are going crazy and now the camera causes a reboot. Needs work.
[Samsung Galaxy Nexus] zzpianoman:
I managed to get everything working except video recording is distorted and auto focus isn't as snappy as it could be. I ended up making a tar of my entire /system/vendor folder from KitKat and then via trial and error, mixing and matching with the vendor libs from FML 11/16. I'm actually not entirely sure which is which because I had to rename a few, but I the way I have it seems to work now.
[Samsung Galaxy Nexus] Dirty_Jerz:
It was MWiz's GApps zip that was causing bluetooth and NFC to go crazy as well as the camera to crash. Flashing PA Gapps Micro alpha now to see how that fairs. If everything is copacetic, I'll push my branches to my git and put a otapackage here. I don't really want to start a thread 'FML-fork 5.0 old ddk.' Kinda **** move. [MENTION=2707287]RW-1[/MENTION] you seem to be in contact with Baldwinguy, can you get in touch and see what his intentions are with Shiny wrt 5.0?

EDIT: Well, I found out what was making the camera crash; as well as my random reboots. It was the piece of **** 2700mAh battery that I got at firesale price (free) from sprint. the thing has absolutely horrid capacitance. So much so that the flash and subsequent shutter sound forced the battery below 2700mV. Just tried the camera with logcat & cat /proc/kmsg running in two seperate shells and this is what it spit out on kmsg before reboot:

twl6030: BAT_VLOW interrupt; threshold=2700mv

OMG. THE AMOUNT OF TIME I LOST BECAUSE OF A POS BATTERY!!!:mad::crying:

Stock bat reinstalled.

Turns out it was not MWiz's GApps making the NFC & BT go crazy, they're still going apesh1t with the PA GApps. That still needs addressing.

Is it the libs installed or new NFC/BT? [MENTION=1048318]zzpianoman[/MENTION] do you still get the

phlibnfc_mgt_configuredriver() returned 0x00ff

after a reboot? It was fine for me until then. Maybe a hint?

Camera works though! WOOO! Video playback through gallery is still borked. Youtube works (Rocking out to Mix - Tool as I type). Snapchat pic works, no bueno on the video. Will test more tomorrow.

moral of the story: If you think you have failing hardware/just an old device, run the mofo off of a benchtop PSU to verify you dont have an assed out battery. :good:
[Samsung Galaxy Nexus] RW-1:
Hi,

I tossed him a message thru RW site, but haven't been in contact as of late. I'll message him here as well, this is what I sent:

"Hey,

Just of note, seems Rootzwiki's been sold and abandoned, look at the spam in the forums.

A lot of us have moved to the XDA thread you have on Shiny toro for VZ ....

If you can take time out to pop in, Dirty_Jerz and a couple of others are working out a port of Lollipop, but don't want to step on your toes, etc.

We know it's not likely that you may pursue shiny 5.0, but if you can pop over there and give your blessing, plans, etc. that would make us all feel better.

Thanks! hope your holiday was grand.

Marc (RW-1)"

Lovely story about your battery ;)
[Samsung Galaxy Nexus] zzpianoman:
What exactly is your bluetooth issue? Are you getting a bunch of FC's on Bluetooth Share? That was happening to me until I copied the libbt-vendor.so from /system/vendor/lib of FML. See, I had literally just overwritten my entire /system/vendor folder with the one from KitKat and then restored the gps and bt libraries from whatever was in the new FML. I know it's a bit confusing and not the most elegant solution, but I was literally just trying everything I could think of until things worked. Not sure about NFC though because I don't have any way of testing that out at the moment, but I wasn't getting any FC's related to NFC.

At the moment I am running a build I did of the latest FML (new DDK) with all of the commits as of yesterday afternoon. Camera preview is now working and video recording is where it was for me on my own build with the older drivers, but camera is still borked which means I can't use any of the barcode scanner apps and pictures are all out of focus. I tried reverting to the old GPU drivers on this build by flashing my working /system/vendor as well as my previous kernel but that broke the camera entirely. Everything else worked though.
[Samsung Galaxy Nexus] Dirty_Jerz:
I don't get any FCs anymore. From bluetooth share or otherwise. It's logcat that is being spammed by the NFC err. I'm going to work on it tonight.