yashsingh1/xdaforums huggingface dataset:
[Verizon LG G2] Dutt1113:
For some reason when i go to carbon download page and click link for any of the nightlies the download will start and instantly say download unsuccessful on my phone. ...any ideas?
[Galaxy S 4 Active Q&A, Help & Troubleshooting] xAjCx:
Since we got the new official 4.3 update, that means we got a new bootloader with the update right? If so, does anyone know if anyone has tried to get this unlocked even though we had no success with 4.2.2? I don't know if I can help get it done or not cause I don't have much background with actually unlocking it but I'm willing to help if possible. :fingers-crossed: Might run into problems with KNOX though.. idk.
[Galaxy S 4 Active Q&A, Help & Troubleshooting] drakul123:
Samsung GS4 locked bootloader. HELP

Hello,

I bought an unlocked Samsung S4 Active I537 from ATT, but I use it in Canada.

I have tried to use Goomanager, TWRP manager, safestrap, quickboot; but the phone goes back to the normal bootloader.

When I try to install a ROM from my SD card (by normal bootloader) it does not do anything at all; just stays on the same screen for a minute then reboots normally.

I am guessing the bootloader isnt unlocked.

What tips you got?

Thanks!
[Galaxy S 4 Active Q&A, Help & Troubleshooting] Devo7v:
The bootloader is still locked and currently there's nothing you can do about it. If you want to follow the progress read through this thread.
[Galaxy S 4 Active Q&A, Help & Troubleshooting] drakul123:
I learned that the hard way

In advance: sorry to sound bitter; but wasn't fun how useless can be a device with a locked bootloader.

So the google apps stopped working and the whole thing is pretty much gone to hell/

IF samsung hadnt locked it so good (in a non-compliment kind of way) I could just install a new ROM and done, even better than with their weird touch wiz. But they locked it well so the phone is pretty much an average control remote in present time.

All samsung devices are locked like this one?

or that's their only garbage version ?

If that's the way they roll... no more Samsung phones ever for me.

There is a reason I stopped buying apple stuff... I dont like buying a device that is limited not because of its hardware, but because of the useless things a brand adds to make it useless. (like locking the bootloader)

Anyways... I am considering buying another phone for now.:silly:
[Galaxy S 4 Active Q&A, Help & Troubleshooting] Devo7v:
The device is far from useless, you can still root and flash custom ROMs, just not CM or AOSP based ROMs. I've posted all the stock ROMs and instructions on how to flash them, so if you do mess up your phone you can always start from scratch.

To answer your question about all Samsung phones, pretty much all Samsung phones from the GS3 an later that were sold by AT&T and Verizon have locked bootloaders. Nearly all the international versions as well as T-Mobile versions are sold with an unlocked bootloader, so you don't necessarily need to boycott Samsung, you just need to be more careful when purchasing a Samsung phone in the future.
[Galaxy S 4 Active Q&A, Help & Troubleshooting] drakul123:
Hey there

Where did you post these ways of re installing all?

I saw many posts around here about reinstalling but I couldnt move on after they required the Samsung to do something through the bootloader.

Also there was a post to uninstall using Odin, but the post had missing files so couldnt do it.

Keep me posted!
[Galaxy S 4 Active Q&A, Help & Troubleshooting] Devo7v:
http://xdaforums.com/showthread.php?t=2835481
[Verizon Samsung Galaxy S 4] linuxthinker:
CM11 is great, but the libraries it's got appears to be heavily targeted toward CDMA mode and less so GSM. If you're a traveler or want to use your device with AT&T/T-Mobile, you'll want to install this patch which loads the AT&T ril onto your device. Without it, I couldn't receive any incoming calls and calls I placed couldn't be hung up (I would be stuck at the "hanging up" screen).

This patch is just two files (libril-qc-qmi-1.so and libril.so) pulled from the AT&T version (jflteatt) of CM11 (specifically, this version: https://download.cyanogenmod.org/get/jenkins/53825/cm-11-20140104-SNAPSHOT-M2-jflteatt.zip).

I'm overseas right now, so I'm only able to test GSM mode, but it's working just fine for me now. If it's not enough for you, you might want to try the two other changes suggested here: https://jira.cyanogenmod.org/browse/CYAN-2362

To summarize, they are:

Set telephony.lteOnCdmaDevice=0 in /system/build.prop

loki_flash the jflteatt CWM with jfltevzw aboot - see here. Note that this is specific to MDK, so don't do this if you're on any other bootloader. Let me know if you want me to create a flashable version of this possible fix.

I didn't need to do either of these things to get it working for me, but you may need to do the first item if you want LTE (I'm currently in a country without LTE, so I can't test).

Flash this for GSM-optimized rils: View attachment 2559158

Flash this to revert to CDMA-optimized rils: View attachment 2559157
[Verizon Samsung Galaxy S 4] mbastats:
Are these the updated files?

I see above that the flashable zip files were removed due to being broken. Are the ones attached good now? Also, these are AT&T files so will they work the same way with T-Mobile service since its fixing the issue with GSM and is not carrier specific?

If so, I'll give it a shot tonight. Thanks!
[Verizon Samsung Galaxy S 4] linuxthinker:
No. Attached files are no-good; I've now removed them. I made a mistake in building the packages that'll likely brick your phone. I quickly removed the links while trying to fix my own device but forgot to remove the attachments. I'll repost when it's working properly.
[Verizon Samsung Galaxy S 4] mbastats:
Glad I didn't trust the files! I noticed that someone else in the same cyanogenmod ticket thread recommended an update to a line as a fix. On my mobile, or I would post a link. Thanks for trying to find a fix though!
[Verizon Samsung Galaxy S 4] linuxthinker:
I just tried the fix in the CM thread - stuck in a segfault loop :(

Now that I've unbricked myself, I've updated the zip packages and they should be usable now.

Lesson learned: mount partitions by name whenever possible! I'm lucky I didn't blow away anything that I couldn't recover from. I was just unlucky that it was a partition not normally included in odin reset tars.
[Verizon Samsung Galaxy S 4] mbastats:
Recap of how to

So to recap how this is done, please correct me or agree.

If someone was installing CM 11 for the first time, they would:

1) Download the CM rom.

2) Download the GAPPS they prefer.

3) Download your 2 zip files for GSM ril provided in this thread.

4) Flash into recovery (assuming they had a custom recovery in place already)

5) Wipe data/cache/dalvik

6) Flash ROM, Gapps, and the 2 GSM ril zips you provided. (I prefer to flash Gapps after the first boot)

7) Reboot and watch it boot up.

8) Calls should work (assuming the correct apn settings are in place)

Agree?
[Verizon Samsung Galaxy S 4] linuxthinker:
Almost!

(2) is optional and can be done later. There's no dependency here.

For (3), you only need the GSM flash package. The cdma package is provided if you want to revert.

For (4), a custom recovery is a given, since CM can't be flashed on the vzw s4 without it :)

For (6), flash only the GSM package.

For (8), calls should work even if APN settings are broken.

The two things to test for is:

1. After you've placed a call and are connected to the other party (i.e. the call timer starts ticking), you can successfully hang up.

2. You can receive an incoming call.

And to answer the carrier specificity question -- I'm testing this with Taiwan Mobile, so it's most definitely not carrier specific. :)
[Verizon Samsung Galaxy S 4] canaanp:
I guess this would have to be re-flashed after each nightly update that is applied?
[Verizon Samsung Galaxy S 4] linuxthinker:
I haven't worked with nightlies, but I suspect the answer is yes since nightlies are full images and not deltas.

Sent from my Nexus 7
[Verizon Samsung Galaxy S 4] canaanp:
I just tested with a fresh install of the 2/5 nightly. I wanna have your baby. Works perfectly, thank you!
[Verizon Samsung Galaxy S 4] mbastats:
It worked!

You have solved a problem that so many people were having. It works!!! Thank you for contributing. Now I'm going to spend time manually packaging a ROM with this and the apps and features I want.

Thank you!!!
[Verizon Samsung Galaxy S 4] Alttwo:
Thank you. I'm using my Verizon s4 on T-Mobile and you saved me the trouble of doing this manually every time
[Verizon Samsung Galaxy S 4] aindfan:
With the latest comment on the linked Jira thread (and a correct APN), I think that I have an AT&T SIM working in my Verizon S4 without this mod. Does anyone else have this experience? (I should note that I flashed the GSM zip from OP three days ago, but I have since wiped, installed Hyperdrive ROM, wiped again, and reinstalled CM11 without flashing the GSM zip.)

To clarify, here's what I did:

1. Wipe data and cache.

2. Install latest CM11 nightly and gapps.

3. Boot and confirm that everything is working.

4. Add the letter "U" to the build.prop line that said "ro.telephony.ril.v3=newDriverCall" by default.

5. Reboot and confirm that Verizon LTE still works.

6. Power off, insert AT&T SIM, power on.

7. Choose LTE/WCDMA/GSM in Mobile Network settings and select a working APN.

8. Get H or H+ icon in signal bars and use speed test to confirm the blazing fast 0.10M down, 0.13M up.

9. Place call to my Verizon number, check voicemail, and hang up normally (I didn't get stuck at "hanging up").

10. Place test call from Skype to AT&T number, pick it up on the S4, and hang up from the S4 normally.

Thanks!
[Verizon Samsung Galaxy S 4] linuxthinker:
Are you running CM11 nightly or the snapshot?

FWIW, I tried "ro.telephony.ril.v3=newDriverCallU,newDialCode" from this post: http://xdaforums.com/showpost.php?p=50036251&postcount=1591 and it caused a segfault loop on bootup.

Given all the issues getting CM11 working well, I'm probably going back to stock MDK 4.2.2; it's still less bug-prone than CM11 is :(
[Verizon Samsung Galaxy S 4] aindfan:
I'm using the CM11 nightly. I didn't add the part after the comma to the build.prop line.
[Verizon Samsung Galaxy S 4] arlissnd:
I am very grateful for this! I searched and searched for days for a way to fix my dialer not letting me hang up a call after switching to Straight Talk AT&T. Now if I could only figure out how to get 4g LTE instead of just H+, I would do backflips! I appreciate your post immensely!
[Verizon Samsung Galaxy S 4] linuxthinker:
Are you using the latest (MK2) radios? Those should get you LTE if AT&T has refarmed AWS LTE in your area.
[Verizon Samsung Galaxy S 4] arlissnd:
I will try flash mk2 right now. Thanks. I'll report back ASAP.
[Verizon Samsung Galaxy S 4] linuxthinker:
FWIW, I flashed the non-hlos + modem.
[Verizon Samsung Galaxy S 4] arlissnd:
Did you use the vruemk2 or the other one? I just did that one, but it was not the non-hlos. I read that you should only flash the non-hlos modem that matches your boot loader. I'm on mdk boot loader.
[Verizon Samsung Galaxy S 4] linuxthinker:
My understanding (according to the main CM11 thread) is that rule only applies for stock. I used the MK2 non-hlos+modem.
[Verizon Samsung Galaxy S 4] arlissnd:
Did you get it from here http://xdaforums.com/showthread.php?t=2487298

---------- Post added at 06:46 AM ---------- Previous post was at 06:44 AM ----------

Are you on mdk boot loader? Would you possibly have a link to where you got it? I appreciate your help!
[Verizon Samsung Galaxy S 4] linuxthinker:
Yeah, I got it from that thread. I'm using the MK2 non-hlos + modem from there.
[Verizon Samsung Galaxy S 4] arlissnd:
OK. Just to be clear... You are on mdk boot loader and you flashed mk2 non-hlos zip and also the mk2 modem? One after the other ?
[Verizon Samsung Galaxy S 4] linuxthinker:
If you get your modem from that thread, the non-hlos and modem are available as a single flashable package. Yes, I am on MDK bootloader.
[Verizon Samsung Galaxy S 4] arlissnd:
Thanks again. It was a little confusing to me as I was reading the posts. In going to try it now.

I just flashed it and got an improvement on speed test. Still no 4g LTE. But I will try messing with settings again in the morning. AT&T must not have AWS here yet.
[Verizon Samsung Galaxy S 4] jay876:
I tried the latest universal galaxy s4 nightly (feb 24 build) and still have my dialer hanging and being unable to receive calls when running cm 11. I'm just wondering do I need to flash the gsm zip for that build? I'm just being cautious.

Verizon Galaxy S4 (MDK + cwm recovery) on a GSM network.
[Verizon Samsung Galaxy S 4] arlissnd:
I flashed the gsm zip and it fixed my problem.
[Verizon Samsung Galaxy S 4] jay876:
Yea I decided to try that this morning with the latest build and it worked :}. Thanks for this solution.
[Verizon Samsung Galaxy S 4] arlissnd:
I've seen in a lot of other forums that many, many people are having exact problem. I searched for like 3 hours the other day before I found this. I am very thankful for this thread!
[Verizon Samsung Galaxy S 4] arlissnd:
Do you get the 4g LTE icons on the status bar? I just get H+, but I get decent speed, almost 8mbps down.
[Verizon Samsung Galaxy S 4] linuxthinker:
I was using it in a country without LTE, so the best I got was H+.

Unless you're using AT&T in an area with AWS expansion or T-Mobile, the best you're going to get in the US is H+. The VZW S4 only does LTE on 750/AWS. AT&T operates on 700/AWS and T-Mobile is all-AWS.
[Verizon Samsung Galaxy S 4] arlissnd:
Good to know.
[Verizon Samsung Galaxy S 4] 65vdub:
I can send texts but not receive them, any ideas? I just switched to T-Mobile like an hour ago. I added the U to the ro.telephony.ril.v3 line and also flashed the gsm zip in the op. And rebooted, LTE and calling work as well as sending SMS. I just can't receive SMS.
[Verizon Samsung Galaxy S 4] Mystique:
Hello all,

Has anyone used this recently?

I have the exact problems using 'more up to date' M7.

Since they have moved to a unified build I would have thought this to be a non-issue; but that is not the case.

Any idea on what should be done for a M7 or modern unified build?
[Verizon Samsung Galaxy S 4] linuxthinker:
I haven't tried doing this since the switch to the unified build. I'm pretty busy this week, but I'll see if I can figure out how they're switching radios between the AT&T and Verizon versions and see if we can trigger that manually. Probably won't be able to look at this until this weekend.
[Verizon Samsung Galaxy S 4] Mystique:
I've been running the GPE (Google Play Edition) of 4.4.3 on my S4 since the move to AT&T..

I'll get some time and try the build prop tweak and see what that does.

I opened the M7 zip and one of the libraries is not in there anymore..

So maybe the build prop is what I was missing..
[Verizon Samsung Galaxy S 4] Mystique:
So, post #13 is what the new fix is.

Except, that brings a new problem of all incoming calls are prefixed with a +

So trying to respond via Sms or even a call back, results in a formatting error and an unsuccessful communication attempt.

But, post 13 totally gets incoming calls going and the phone hanging up properly.

Sigh
[Verizon Samsung Galaxy S 4] roboots21:
Use Prefixer from the Play Store to remove the +. Works perfectly once you set it up.
[Verizon Samsung Galaxy S 4] Mystique:
This might be it.

Higher rating, I will try and report back.

https://play.google.com/store/apps/details?id=com.tftbelow.prefixer

Thank you.
[Verizon Samsung Galaxy S 4] roboots21:
Yup .. That's the one! Using on the wife's S4 on cricket and works like a charm! Glad I could help!
[Verizon Samsung Galaxy S 4] slosho:
OMG!!11!!1! This is so what I needed! Loaning out my VZW GS4 (I now have a note 3 and miss the CM11) to my brother for use on Cricket/At&t. Thought I was going to have to undo my CM on the device, I will be second in line to berth ur childeren!
[Verizon Samsung Galaxy S 4] brizey:
If you are running the current CM11, you can pull the current ril files from the gsm folder in the blobs folder in the zip file.

What I do: delete the I545 lines in the updater script, and sub in I545 for M919 to get the gsm files for T-Mobile. Everything worked for me. I'm using the GE ROM now, but I tried LS (a CM11 based ROM) and this worked fine.
[Verizon Samsung Galaxy S 4] justda:
This works with the unified builds if you can grab and hold data that is.

I used this with a few CM based ROM's and had horrible data if any service at all. But it is working fine with danvh's GPE CM based ROM.

Sent from my SCH-I545 - CM 11 base and a T-Mobile Sim.
[Verizon Samsung Galaxy S 4] thorrules:
Has anyone tried this on cm12? Just wanted to know before I try it myself.
[Verizon Samsung Galaxy S 4] bjbinc:
Did it work? If not can we get a similar patch for CM12? Having the exact same issues. Thanks!
[Verizon Samsung Galaxy S 4] thorrules:
No it didn't work. I moved onto nexus 5. But I still have my s4 so I can test it, if a fix is posted here.
[Verizon Samsung Galaxy S 4] linuxthinker:
I'm in the same boat. I've moved on to a Nexus 6, so I haven't been actively trying to fix the S4. The Nexus 6 "just works." Drop in a SIM from any US carrier and it works, CDMA or GSM. It's really what the S4 should have been.
[Verizon Samsung Galaxy S 4] bjbinc:
I'm using GPE 5.0.1 with no problems at all...
[Verizon Samsung Galaxy S 4] skrapmetal:
No fix for using this on Lollipop?
[Verizon Samsung Galaxy S 4] HapaKato:
I played with different combinations of files and modified build props but I just don't know enough about what I'm doing and have had no luck so far. I'm running a S3, but this thread is the closest I can find to the problem.
[Verizon Samsung Galaxy S 4] HapaKato:
I got the t-mobile version of Pac-Rom running on my Verizon S3 and everything works. I piggybacked the conversation here: http://forum.cyanogenmod.org/topic/...l-alerts-and-outgoing-call-is-not-hanging-up/

and modified the updater-script located in, META-INF\com\google\android\ (I assume this is the same for CM12 as that's the base of Pac-Rom) to change all instances of d2tmo to d2vzw. Hope that helps someone.
[Verizon Samsung Galaxy S 4] Drake9897:
Anyway I could get this mod for CM13? Calling just doesn't work for me :/
[HTC One Max] halibil:
hi guys

I rooted my device ,, now fingerprint doesn't work

there are any Solution to get it back ? :angel:
[HTC One Max] jaypeg123:
Have you read anything at all on the htc one max thread? Or you just shout out a question in the air like irl.!
[HTC One Max] halibil:
sorry bro

I can't speek english .. so I come here directly to ask anyone have a solution

sorry again :)
[HTC One Max] jaypeg123:
You don't have to speak just read. But I assume that you can't read English either so there's no point in me giving you the solution.
[HTC One Max] pradeepvizz:
we have a solution already, there is no need for a thread.

[MENTION=2037218]jaypeg123[/MENTION] LOL :D !
[HTC One Max] halibil:
I meant I'm not good enough to read a long article .

I was hope to find goodness person can to show me where is the solution located In this forum

If you don't have a good answer .. You don't have to write shameless reply to someone tired to select a few of word he knows to describe

his problem

If you need to help and you have to

Write in my native language .. I will not taunt from your mistakes ( like you did ) I will be proud & glad to help you ..

Thank you for nothing
[HTC One Max] wase4711:
English is the language that is used on XDA, per the rules.

If you can't read it or write it, then you need to find another place for help.

Its just that simple.
[HTC One Max] neodiver:
Try cutting and pasting this line into the search box at the top of the page: "one max enable fingerprint scanner"

It worked wonders for me! :laugh:
[HTC One Max] luigi97777:
good!
[HTC One Max] wildstang83:
Guys, I know that repeat questions can get old. However, there is no need at all to be rude and unhelpful. All you have to do is answer the OP in a helpful way, or provide a link to some previous discussion on the subject. If you cannot bring yourself to do either of those, click the back button on your browser and go be helpful in another thread.

Now then, since this is a well discussed topic, I will close this thread. For future reference, this nice S-Off Guide explains how to re-enable the fingerprint scanner.

Regards
[8125, K-JAM, P4300, MDA Vario Software Upgrading] roriii:
hello everyone any one know how to write an ipl 1.67.nb with witch programm thanks
[HTC Butterfly] indrawib:
Why s2w+s2s kairi kernel 4.3 did not working well with custom Rom soul-6
[Sony Xperia P, U, Sola, Go] rajput10906725:
whenever i want to update my music library by using download music info.there is always an error (security error).I've tried many solutions but can not resolve this problem.is this a bootloader problem? kindly help me i'm using xperia u stock ics. 54 and rooted and unlocked bootloader
[Sony Xperia P, U, Sola, Go] Wind07:
You cannot download music info on UB.
[Sony Xperia P, U, Sola, Go] rajput10906725:
will it work if i lock the BL
[Sony Xperia P, U, Sola, Go] Wind07:
Did you backup TA before unlocking? Walkman checks for DRM keys which is lost in the Unlocking BL process. If you did backup relock and restore the backup. And you CANNOT RESTORE ANOTHER PERSON'S TA(even if it is Xperia U also) as it will result in hardbrick.
[Sony Xperia P, U, Sola, Go] rajput10906725:
what is TA?
[Sony Xperia P, U, Sola, Go] rajput10906725:
I haven't backup my TA..i didn't know about this at that time...is there any other solution?
[Sony Xperia P, U, Sola, Go] Wind07:
The answer is NO. DRM Keys are checked when downloading music info
[Droid RAZR M Android Development] CarbonROM:
Reserved
[Droid RAZR M Android Development] CarbonROM:
Also Reserved
[Droid RAZR M Android Development] levizx:
Great work! Will try it out once finished modding it for XT905.

PS: Why not add it to DevDB?
[Droid RAZR M Android Development] arrrghhh:
I was told none of these moto's have DevDB. I've never used it myself, might be why haha.
[Droid RAZR M Android Development] levizx:
Yeah, maybe that:D

Quick question: I'm noticing quite apparent banding on my screen, especially on white background. And occational white noise splash while turning screen on, is it normal or just because I'm using it on XT905? Seems to be kernel related. I'm actually testing out both Gummy and Carbon, both have the same problem.
[Droid RAZR M Android Development] arrrghhh:
This is not made for xt905, so I'm not sure... Do you know how that device differs? I'm not aware of any forum for that device...

Edit - just checked, seems CM doesn't support it either? How does CM run?
[Droid RAZR M Android Development] levizx:
Should be almost the same since this is just the GSM version of XT907. By apparent I actually mean noticable by human eyes (on while background). It's has to have something to do with the buffer or refresh rate.

Actually all ROMs with minor modification works fine. Not as smooth as I'd hope ie not smoother than debloated stock 4.1, but all things work, sans the occasional white-noise splash while turning screen on and the annoying band morie pattern.

Another question, do you have any plans ditching the emulated sdcard? It's quite pointless with just about 4GB after a full wipe and you have to share the space with apps.
[Droid RAZR M Android Development] allen_ho:
I can't find out the download package of the xt907, is that true? I love carbon team, the black theme looks really nice
[Droid RAZR M Android Development] arrrghhh:
We are working on migrating to a new download site + mirror... as our infrastructure was not up to the task (downloads were REALLY slow).

Hopefully the new setup can handle the load! I'll upload the last build to a mirror.
[Droid RAZR M Android Development] hecksagon:
The banding issue affects all 4.4 roms. I don't know the technical details but it seems 3D acceleration is about 50% slower than 4.2 roms. Since nearly everything is composted in the GPU now, everything seems to suffer from poor frame rates and other graphical anomalies.