yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] andrewlax120:
i understand that thats a gsm version. but to get this going don't i have to flash that rom as a the base and follow the op by replacing the system files?

they would be set rw-r-r correct?

i may just hold off a few days but im anxious to get these bugs fixed :laugh:
[Samsung Galaxy Nexus] jsgraphicart:
I just re-read the OP and I guess thats what he did. Flash the GSM zip and replace files with Verizon files. I havent tried it. I, personally, am going to wait for something else.
[Samsung Galaxy Nexus] pricematthew4143:
yeah that's what worked for me, the rooted 4.2.2 and those files and i got 4g, and the correct vpn showing afterwards...even the baseband showed correct after the build prop changes so Yep...should work out just don't forget to set permissions and delete the gsm files..
[Samsung Galaxy Nexus] pricematthew4143:
yes the permission are set rw-r-r or 644 and it was kind of easy you just have to get lte/cdma files in the lib or ect so the rom knows to look for lte or cdma and not gsm...all they are are xml files and just have to add a bunch of ro.cdma and change the name in build prop..i was actually surprised how easy it was when the baseband showed correct and I got a blue 4g signal
[Samsung Galaxy Nexus] pricematthew4143:
no...I did flash the GSM 4.2.2 on my CDMA VZW GN, there is NO GSM RADIO IMAGE on the 4.2.2 GSM ROM the dev removed it.. so there is not damage to the CDMA GN... so you are just flashing a ROM meant to pick up GSM, all you have to do is replace the files so the rom picks up lte/cdma...and all they are are xml files and one .so file and the build prop to tell the phone where to look...thats all...it was actually really easy
[Samsung Galaxy Nexus] pricematthew4143:
yep, just replaced the gsm .so and xml's with lte/cdma and changed build prop so the phone can figure it out..that's it.
[Samsung Galaxy Nexus] pricematthew4143:
and sorry for the confusion that zip is NOT flashable just the files I used to get the rom over to lte/cdma..I used root explorer to add the lte/cdma files and for setting perms
[Samsung Galaxy Nexus] mkalter:
Hij,

I tried doing the same on Sprint Galaxy Nexus.. But it didn't work. Do you have any tips?

Cheers
[Samsung Galaxy Nexus] pricematthew4143:
the only way i figured it out was to look at the build prop especially the RIL lines..they give the exact file that needs to be replaced

ex. on the gsm: rild.libpath=/vendor/lib/libsec-ril.so libsec-ril.so is the driver the rom is looking for

I replaced the file in the "lib" folder and build.prop line with rild.libpath=/vendor/lib/libsec-ril_lte.so so the rom will now look for the lte driver

make sure the "telephony.lteOnCdmaDevice" line equals 1 it tells the phone that it is a lte/cdma device..if there is a 0 the phone thinks it is a gsm device

also don't forget to set permissions as rw-r-r as they are in screenshots and to delete out the gsm files ...they aren't named the same so there is no overwrite or replace.. you have to delete them. I don't know how sprint files and radios are setup though but I hope this helps...
[Samsung Galaxy Nexus] mwalt2:
You guys may as well replace the files in the gsm zip before flashing it and save yourselves some time. There's no reason to do it after unless you just like using a file explorer on your phone. Also, an easy way to see what is different is to compare CM roms for the gnex.
[Samsung Galaxy Nexus] 00negative:
Have binaries for 4.2.2 been released yet
[Samsung Galaxy Nexus] andrewlax120:
im not finding com.hardware.gsm.xml in system/etc/permissions.

did you mean android.hardware.telephony.gsm.xml?
[Samsung Galaxy Nexus] pricematthew4143:
yes sorry bout that but yes that is the file
[Samsung Galaxy Nexus] doobie711:
Wow. I can confirm this as working. I'll upload a flashable zip for those who want it. I Think I'm going to try this and see if it works with older verions of gsm Android.
[Samsung Galaxy Nexus] Alpha_wolf:
did they fix the battery drain on 4.2.2??
[Samsung Galaxy Nexus] pricematthew4143:
thanks for simplifying it, not real good at the flash-able zip stuff and thanks I was seriously surprise at how easy it was to change it to lte but also super thankful for the work bigxie did for the rooted 4.2.2, wouldn't have tried if I didn't stumble across his work
[Samsung Galaxy Nexus] andrewlax120:
hmm i don't think this worked for me. all the gsm files are still there and there is no change to the build.prop

i flashed bigxies odexed rom then flashed your zip, should i go for the deodexed?
[Samsung Galaxy Nexus] pricematthew4143:
The deodexed rom from bigxies was the only one I had tried this on, and most mods usually never work good on odexed rom's...so yes flash the deodexed rom from bigxies
[Samsung Galaxy Nexus] pricematthew4143:
the aosp 4.2.2 binaries are getting pushed right now so hopeful soon wont have to bastardized the 4.2.2 rom anymore lol

AOSP 4.2.2 binaries are finish pushing
[Samsung Galaxy Nexus] doobie711:
I may not have gotten the zip right. I'll check it as soon as I can and re upload a working one.
[Samsung Galaxy Nexus] KidCuda:
I did the manual instructions from the first post, and then noticed the android.hardware.telephony.gsm.xml correction... anyway it wouldn't boot past the Google logo so I'll wait for a proper compiled ROM.

I'm sure I just overlooked something!
[Samsung Galaxy Nexus] pricematthew4143:
double check the permissions, did the boot thing 3 times before I caught a bad permissions setting
[Samsung Galaxy Nexus] KidCuda:
Of course as I post mwalt posts the compiled version, so I think we're all set!
[Samsung Galaxy Nexus] mwalt2:
It's not compiled because aosp seems to be messed up right now. I just modified the maguro rom as well. However, I think I have put in all of the toro-required stuff (most of the things get added in when compiling from aosp, so I took everything from there). It is surprising how little difference there is between gnex cdma and gsm nexus roms.

It is really easier to just add/remove files to/from the .zip on your computer. You don't have to worry about permissions or clunky android file managers.
[Samsung Galaxy Nexus] pricematthew4143:
thanks for the smoother install, your version seems to run much faster overall and the signal for wifi and 4G grab quicker...thanks..
[Samsung Galaxy Nexus] mkalter:
Thanks, I think the problem is that I've an odexed version of the ROM. What did you do with the files in system/lib?
[Samsung Galaxy Nexus] pricematthew4143:
it is actually sys/vendor/lib just got lazy and only typed lib but the original file from the gsm in sys/vendor/lib is libsec-ril.so delete that and in its place put libsec-ril_lte.so and set permissions rw-r-r (644) just pretty much taking the gsm driver out and putting in the lte driver so the phone can get lte
[Samsung Galaxy Nexus] mkalter:
Strange, still doesn't work.. Phone doesn't find baseband. Google play and other apps recognized it as a sprint galaxy nexus.
[Samsung Galaxy Nexus] pricematthew4143:
on the vzw the baseband popped up for me after all the files where in place, i had added the cdma files and change a few lines on the build prop and reflashed the radios through fastboot but it is a shot in the dark for me and sprint...I don't know if their file system is the same or even if build prop is the same but I will get a sprint stock rom and look at it

BUT REFLASH RADIOS FIRST and wipe cache and dalvik
[Samsung Galaxy Nexus] mkalter:
omg, it's working now. Looks like it was loading or what else.. Thank you so much bro for your help!

Cheers
[Samsung Galaxy Nexus] pricematthew4143:
that's exactly how I felt when the 4g kick on after moving 4 files, I was like..no sh*t..wow 4.2.2 from gsm rom

don't thank me you did the hard work, I was only familiar with vzw files , glad it all worked out...So it is showing baseband and lte and got a good signal?
[Samsung Galaxy Nexus] mkalter:
Yep all working fine, just like stock 4.2.1 from sprint ;)
[Samsung Galaxy Nexus] leanderdulac:
Is it possible make the cdma/LTE work like a GSM?

Hi guys,

I bought a GNex of the Verizon LTE/CDMA. But,I came back to Brazil.Is it possible to transform my device to work with GSM/3G/HSPA network from Brazil?

Is there any cooked rom that make this job?
[Samsung Galaxy Nexus] Phazmos:
vz hardware doesn't support gsm, cannot do. No more need to resurrect old threads
[Eee Pad Transformer Q&A, Help & Troubleshooting] akt27x:
I used to have a rooted EVO 4G through work, but recently they switched me over to an iSheep, and as you can imagine I absolutely hate it. And since it’s for work they’ve installed AirWatch so I can’t jailbreak it. But I also have a TF101 that's currently not rooted.

I got my TF101 about a year ago and rooted it like every good android user should. But after about 6 months, I found a small hair line crack in the touch screen. I unrooted it and sent it in to ASUS for them to repair. I always keep my tablet closed in the docking station when it wasn’t in use. I then found this thread, http://xdaforums.com/showthread.php?t=1498237 that stated this is why the screen cracked. So ASUS and I went back and forth for about a month before they finally covered it under warranty and repaired my tablet.

When I got my tablet back I found they upgraded it to 9.2.1.27. I connected it to a computer so I could reroot it, but my tablet is no longer detected by a computer. I tried two computers and two data cables. I’ve also tried all the methods for installing the drivers. I didn’t want to send it back to ASUS due to the issues I previously had with them. I’ve been following Thing O Doom’s thread, http://xdaforums.com/showthread.php?t=1681155 because he stated he's working on a rooting apk, but he no longer has his TF101 so progress has been slow.

But in my searching I found this thread,http://www.transformerforums.com/fo...rmed-fix-gain-root-after-8-6-5-21-update.html that stated I can get the zip out of an old ASUS update and put that on my sdcard and let the tablet update itself to an older version. ASUS made an instruction sheet for manually updating with a zip, http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101G/e6754_TF101_Update_SOP.pdf. Once downgraded I could use RazerClaw http://xdaforums.com/showthread.php?t=1345049 to root, and then flash a recovery, rom, etc.

Will this method work? I have to believe no, it just seems too easy. I haven’t tried it yet because I worried about bricking my tablet and not being able to fix it since it won’t connect to a computer.

Any response, opinion, recommendation, experience would be greatly appreciated.
[Eee Pad Transformer Q&A, Help & Troubleshooting] frederuco:
I am not sure that will work. It worked when you had 8.6.5.X because it was upgrading to a "newer" version that is 8.6.6.X (for the TF101G).

Now you are on a 9.X, so it most likely will not work.

Have you tried APX mode? I used that to root from the .27 firmware without having to downgrade. Turn off your tablet, hold VOL UP and then press the POWER button for about 3 seconds. The screen will be black, but when you plug it into a computer it should be detected.

If it does work, use EasyFlasher and install a custom recovery (HIGHLY recommend TWRP over CWM).

Here is a guide I wrote on how to root and ROM: LINKY
[Eee Pad Transformer Q&A, Help & Troubleshooting] akt27x:
Thanks for the reply. I did try APX mode but I would get a message on both computers I tried stating the device was unrecognizable. I then tried to load the drivers but it still didn't work on either computer.
[Eee Pad Transformer Q&A, Help & Troubleshooting] frederuco:
I guess you could try the other method. Since it is using stock recovery there is very little chance of bricking IMO. It will either install the older firmware, or it will not.
[Eee Pad Transformer Q&A, Help & Troubleshooting] benmatlock:
You may be able to use Wolf's tut for this...
[Eee Pad Transformer Q&A, Help & Troubleshooting] akt27x:
Thanks for the response, but I'm unable to successfully connect my tablet to a computer so I can't use ADB. I'm looking for a way to root it without a computer.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Lethe6:
air adb, there's at least 1 good free one in the play store.
[Eee Pad Transformer Q&A, Help & Troubleshooting] akt27x:
Thanks for the response, I looked into that and I thought you had to be rooted for it to work. I'll look at it again.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Woody:
Just curious, did you reboot your PC after you installed/uninstalled the drivers?

I had this same problem once. What I did was pulled up Device Mgr and checked for APX drivers. If there was some, I uninstalled and Rebooted the PC. I downloaded these Universal Naked Drivers and saved them where I knew where they would be. I left the Device Mgr open and booted into APX mode. It asked to install drivers. I said yes and it failed. I then pointed it to the Naked Drivers and and it found them pretty easily. Once I saw APX pop up in Device Mgr, I was good to go. I then used EasyFlasher to flash back to .27 with Root. The link in the EasyFlasher OP for stock firmware is off for some reason. I posted the direct link near the last pages. Here it is.
[Eee Pad Transformer Q&A, Help & Troubleshooting] benmatlock:
You don't /need/ adb to root it this way, all you need is a terminal interface on your tablet. If you can download and unpack the zip file containing the blob for whatever recovery you wanna use, then link the mmcblk0p4 to tmp, you should be able to be good to go after a dd and reboot.

--edit--

start here: Instructions - Method 2 - UnRooted

then replace step two with "download terminal emulator from the play store"

then replace step three with 'open terminal emulator'

continue with the rest of the tut, using whatever recovery you want (i use Rogue XM)
[Eee Pad Transformer Q&A, Help & Troubleshooting] akt27x:
I tried this and you're right it didn't install the older firmware. It looked like it was going to because the status bar was moving at the bottom, but after a few minutes it went to an android laying down with his guts open and a exclamation mark above him.
[Eee Pad Transformer Q&A, Help & Troubleshooting] akt27x:
I think I've tried this. I have a terminal emulator installed and I followed some instructions about entering things like this in but I think I got a message stating access denied. But I'll try it again tonight and reply back with the results.
[Eee Pad Transformer Q&A, Help & Troubleshooting] akt27x:
Re: [Q] Possible Downgrade to Root

Using wolf's instructions I tried this with a terminal app on my tablet and got the following.

app_283@android:/ $ mv /data/local/tmp /data/local/tmp.bak

failed on '/data/local/tmp' - Permission denied

I then tried this and got the following.

app_283@android:/ $ dd if=/sdcard/recoveryblob.bin of=/dev/block/mmcblk0p4

/dev/block/mmcblk0p4: cannot open for write: Permission denied
[Eee Pad Transformer Q&A, Help & Troubleshooting] akt27x:
This weekend I tried to install the drivers again. I first went through the control panel and device manager and deleted anything that said android and asus, then rebooted my computer. I then tried to install PDANet because I read that it'll install the drivers needed and if you're having a problem it's an easy way to install them. During the PDANet install it told me to plug my transformer in to load the drivers. When I did it said it was installing new drivers but then it said they didn't install. My transformer came up as an unknown device in device manager.

I then went through and deleted the unknown device and checked in the control panel again, then rebooted my computer. I then put my tablet in APX mode to try and get it to load the drivers. Again it didn't install them and my transformer came up as an unknown device. I deleted the unknown device agian, rebooted, and went to ASUS website and installed ASUS Sync. When it finished I rebooted and then started ASUS Sync. Again when I connected my transformer to my computer it said it was loading the drivers, then it failed, and the computer showed my transformer as an unknown device. ASUS Sync also stated there was no device connected to it.

All the reading I've been doing, it seems like there are some other people experiencing the same issues I am, and I haven't seen where anybody has posted a solution. If anybody has any input please let me know.
[Eee Pad Transformer Q&A, Help & Troubleshooting] akt27x:
I think I'm getting closer. I downloaded WLanAdb from the play store and followed the directions and downloaded the needed files to my computer. In the command prompt I type "WLanAdbTerminal devices" and my tablet will show in the list of devices. But WLanAdb is only setup to except a few commands, the main purpose of the app is for pushing files. It was the only wireless ADB app that I could find that didn't require root.

I then found SSHDroid in the play market and I downloaded putty to my computer. I connect to my computer using that. When I type "adb devices" I get a mesage that states

daemon not running. starting it now on port 5038

daemon started successfully

List of devices attached

I then left putty and went back to the command prompt and typed "adb connect (with my ip address and port from SSHDroid)" and it said it connected to that ip address and port. I then type "adb devices" and there are no devices listed.

Again I think I'm very close to getting my tablet connected wirelessly to adb. I think there is just one simply thing I'm missing. Any help would be greatly appreciated.

I'll continue to update this thread until my tablet is rooted or I reach a dead end, so this will be a reference for anybody experiencing the same issues as me.

Thanks in advance.
[Eee Pad Transformer Q&A, Help & Troubleshooting] presbypenguin:
akt27x, did you ever come to a solution?
[Eee Pad Transformer Q&A, Help & Troubleshooting] akt27x:
I haven't. I'm now trying to make a Linux boot flash drive to see if I can get my tablet to connect that way, since I've read that Linux doesn't require drivers. I downloaded LinuxLive USB Creator but haven't had the time to try it yet.
[Nexus 4 Themes and Apps] xx1182:
Hi, where do i get this lockscreen?

I'm now on ParanoidAndroid, but that one seems a lot more custumizable..
[Nexus 4 Themes and Apps] DinoSoup:
It seems to be built into the actual ROM. However, you can try this app - https://play.google.com/store/apps/details?id=com.teslacoilsw.widgetlocker&hl=en
[Nexus 4 Themes and Apps] LudoGris:
According to what the ROM says it is called LockClock (Chronus).

Here is the app pulled straight from CM which is where Chronus came from. Try this...Chronus LockClock.

Remember that the ROM has it themed though so it won't look exactly the same.
[Galaxy S II Q&A, Help & Troubleshooting] edd_g:
Hey i need help, i'm trying to unlock my galaxy s2 I9100 but i got a problem, i already got the "nv_data" file but i can't get the code , i try to use the SamsungUnlocker ( http://xdaforums.com/showthread.php?t=1360174 ) i didn't work also :(

I will post the NV_data file if someone could help that would be great ,

thanks
[Microsoft Surface] marcux:
On the surface pro desktop, I used to be able to drop the resolution and it would scale to fit the screen. Now when I drop the resolution you see black borders around the desktop. Desktop was dropped to 1366x768 and is in the middle of the display non-scaled with black borders. It used to work,scale. I don't think I changed anything. Anyone else having this issue with the pro? does yours scale to fill screen?
[Microsoft Surface] schettj:
Sounds like a display setting/video card driver/bios option - same thing happens on laptops if set to not stretch display.
[Microsoft Surface] marcux:
That's what i'm saying, but there doesn't seem to be any options to turn the scaling back on, it was working, then now it's not, nothing loaded, just desktop. >.>
[Microsoft Surface] marcux:
UPDATE: Figured it out, Really stupid Bug.... if you press f7, and then select pc screen only display, lower resolutions will not fill LCD, if you use duplicate the second screen it will expand to fill lcd.

Why.. just.. why!? How did that get by Q&A!?
[Microsoft Surface] Tundrok:
You can update to newer graphics drivers. I posted this as well on a reddit:

"I think this could help you out:

downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22375&lang=eng

This is the latest driver for the HD 4000. Looks like it just hasn't been pushed out via Windows Update for some reason. I haven't seen any issues using it, but it does enable the advanced graphics settings. It looked like the scaling was done appropriately with this driver after install automatically. If you change the resolution and it doesn't scale full-screen, do the following:

1) right click on desktop 2) Go to "graphics properties" 3) Under Display->General Settings you can change the option under Scaling (this is also can be done by pressing <Ctrl><Alt>F11 **remember to press Fn and F11 on a type/touch cover to actually press F11)"
[Microsoft Surface] bountygiver:
I am supposed to set that settings to "Scale full screen" But that option is not available. There is only "Maintain display scaling" in the drop list.
[Microsoft Surface] bountygiver:
Found a solution. You got to change to a lower resolution in our display settings for that option to appear. Have to change my resolution manually first before launching games with lower resolution...
[Microsoft Surface] GoodDayToDie:
If you select a lower res, then change the option, then change back to normal res, then launch the low-res app/game... that might remember what setting it was at least time you used a lower resolution. I can't be sure (not having a Surface Pro, and in general I despise Intel graphics drivers as featureless and poorly designed) but based on what you said, it's worth trying.
[Microsoft Surface] marcux:
new display drivers fix all issues.
[Microsoft Surface] sivsiv:
Thank you!

My surface pro worked great, then one day, out of nowhere, my games stopped scaling. What used to cause the problem was directx11 not scaling and i could simply hit the F7 key which would bring up screen sharing and click on duplicate which would solve the issue. But at some point, and for seemingly no reason, my display scaling broke for both games that used both directx11 and lower versions. But doing what you said (after installing intel's drivers) fixed the problem.

So thank you again. :) Searching the web with google was very unhelpful up until i saw this post.
[Microsoft Surface] GoodDayToDie:
Glad to hear it. I don't usually say this, but please do remember to click "Thanks" on helpful posts; it improves their visibility.
[Galaxy S III Mini Q&A, Help & Troubleshooting] bruno.trudo:
Hi guys,

is there a way how to use UMS on SGS3m without having a root access?
[Galaxy S III Mini Q&A, Help & Troubleshooting] ppero196:
MTP?

I can use both internal and external SD with MTP
[Galaxy S III Mini Q&A, Help & Troubleshooting] bruno.trudo:
With or without Kies installed on your computer?
[Galaxy S III Mini Q&A, Help & Troubleshooting] enox.co:
...without Kies
[Galaxy S III Mini Q&A, Help & Troubleshooting] lukabike:
Please let me know what exactly you did in order to get this done. We've bought some 10 S3 minis where I work and I've had no success in doing so. I've found no settings which would le me do that. My Galaxy Note has no problem with this at all. I also tried installing samsung usb drivers but no luck. The only thing that happens on the phone once it's connected is the sound of battery charging.
[Galaxy S III Mini Q&A, Help & Troubleshooting] Nazri786:
i guess by default u can choose for MTP or PTP (Camera) when u inserted the usb cable...
[Galaxy S III Mini Q&A, Help & Troubleshooting] lukabike:
Yes, that should be normal. However, on one of those phones nothing happens at all. I tried another one meanwhile and it works :eek:

---------- Post added at 09:21 AM ---------- Previous post was at 09:07 AM ----------

I hate it when a reboot solves stuff. Like this one. Spent hours figuring it out, at the end rebooted and all works now. Thanks anyway!
[Galaxy S III Mini Q&A, Help & Troubleshooting] kicker63:
Sometimes plugging the USB cable into another USB port helps, well it do with me.