yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II, Galaxy S III Developer Discussion ] madmack:
yea, the rilds do work across the US and the EU variants but I had some glitches here and there with that rild socket so I do recommend you switch to your device's proprietary binaries because the slight differences do matter.

try to place a call. can you hear or be heard?
[Galaxy Note II, Galaxy S III Developer Discussion ] chrisaw:
I did try placing a call and unfortunately cannot hear nor be heard. The only two issues I'm seeing so far, however, are:

- Random rebooting (but the SD card reports as corrupt in CM until it's reformatted, seems to be a common issue with CM builds on this device so far.) I'm thinking that could be causing the reboot - will format the card and see if it behaves after that once I reboot it to recovery.

- When placing a call I cannot hear nor be heard sadly.
[Galaxy Note II, Galaxy S III Developer Discussion ] madmack:
yea.. we don't share the rild files with N7100 and I'm afraid the audio issues will be a pain in the ass to fix. I'll ping imilka and see if he can offer any help at all.

the sdcard. it's not corrupt, it's probably formatted as exFAT which CM roms don't support. format it to fat32 and it'll work. If you have an adapter, plug it into your PC and you'll see your files so they're intact.
[Galaxy Note II, Galaxy S III Developer Discussion ] chrisaw:
Yeah I know about the SD thing - seen it before. Thankfully I don't really store anything vital on the SD card so that's not a problem. Even with that removed, however, it's still rebooting frequently (every 4-5mins.) I will have to try merging the n7105 'rild' and associated libs over in to your build to see if that resolves the reboot issue.

The audio issue, however, is something I'm sure was fought when CM10 on the N7100 so I'm guessing it's possible that the N7100 fixes will also work for the N7105 but I realize despite the numbers associated with these devices - there are a fair few differences between them.
[Galaxy Note II, Galaxy S III Developer Discussion ] madmack:
I'm actually using the exact same N7100 files for audio.. I'm thinking our RILD files have different APIs so these audio files will have to be modified.

I contacted imilka. Let's see if he'll provide us with any help :)
[Galaxy Note II, Galaxy S III Developer Discussion ] chrisaw:
Haven't added the N7105 rild binary yet, will let you know the results once I do. It's not really a fair test until I'm running on a N7105 intended rild. :)

---------- Post added at 07:58 PM ---------- Previous post was at 07:12 PM ----------

Ok, now added the rild binary as well as all of the /system/lib/*ril*.so files from an N7105 ROM and this appears (early yet) to resolve the reboot issue. The remaining issue is the audio issue which sadly this did not fix but I may be missing some times. Do you think it's worth copying all of the files from your forum post over here?

http://xdaforums.com/showthread.php?p=34750886
[Galaxy Note II, Galaxy S III Developer Discussion ] madmack:
copy the files you see in here:

https://github.com/madmack/proprietary_vendor_samsung/tree/jellybean/t0att/proprietary

from the n7105.

but that wont' fix the audio. the audio issue is a deeper problem and might take a while to get resolved. i'm taking a break from that for now. might come back and have a look in a few days.
[Galaxy Note II, Galaxy S III Developer Discussion ] DarthPiggie:
Foe the audio issues, strangely enough this was not a problem in some of my earlier builds. Right now I see in logcat : error to create audio stream or something like that. I'll take a look through the defconfig and also through the Board Vendor nakefiles to see what could be causing it.
[Galaxy Note II, Galaxy S III Developer Discussion ] chrisaw:
Sounds great Darth!

It's strangely only when on a call that I experience that issue. I hear the standard DTMF dialing sounds perfectly so audio does work - it just doesn't work during a call (don't even get the ringing) sadly.

Will create an updated ZIP with all N7105 proprietary files to see if I can fix this constant reboot issue though - that's the most annoying bug at the moment! :)
[Galaxy Note II, Galaxy S III Developer Discussion ] chrisaw:
Unfortunately no matter what I tried I wasn't able to get rid of the reboot issue - the device just seems to completely reboot every 5mins or so. I did replace all of the files in the ZIP with the N7105 files which were mentioned in the previous post but unfortunately this still didn't resolve the crash. I also found a file named libaudio-ril.so which the build above didn't have, added that but still no difference. When I fiddled with the build.prop (to replace it to the N7105 values for product, etc.) audio stopped working entirely.

Not really much progress sadly! :(

Edit: Ran out of time working on this last night but unfortunately I have still not made any progress. At this point the remaining issues are:

- Rebooting every 5mins (roughly)

- No audio on calls (TX nor RX)

I suspect both of these are radio related and that one will hopefully solve the other. This is, however, a slightly optimistic view and may not be the case. For now, however, I'd be happy if I could just get the reboot issue resolved. The audio issue I can work around by forwarding all calls to my work blackberry for now. What I can't live with is my phone rebooting every few minutes. I did notice, however, that the reboot only seems to occur where the radio is actually being used. If I simply connect it via WiFi it will sit there for an hour or so. As soon as it is forced to use mobile data that's when the reboots are more likely and placing a call almost always triggers this after a minute or two so it does appear to be modem/RILD related.
[Galaxy Note II, Galaxy S III Developer Discussion ] chrisaw:
Quick update on this:

Still working on getting a valid build environment to build this ROM - once I get a successful ROM built, I will then work on patching the audio and hopefully that in turn *may* fix the reboot issue.

We'll see.

Edited: Rebuilding my dev environment based on the sources from http://xdaforums.com/showthread.php?t=2024495 since this allows the radio to work properly. Then we just have audio and the reboot issue to fix. I say *just* but actually those two may require code to be written which would be a bit of a blocker but with the combination of time and money (my own) I'm sure I'll be able to get this working!

Edit 2: Completed my dev environment rebuild and built off a test image but unfortunately the kernel didn't boot properly. Will get back to this tonight and hopefully get a working build environment using the new sources (now completely modified for our N7105.) Once I get this working I'll post a working image in the dev section. It will very likely have broken in-call audio and a reboot issue, however, but let's get what we have working so far posted publicly and see if we can get some people interested in helping on this! :)

Edit 3: Right, my two objectives for tonight are get a working build and eat pizza! Added a potential fix to my build environment to get the first objective done and planning to order pizza while this is re-compiling. Will keep this post updated of any progress I make. I appreciate all the thanks I've been getting and hope I can deliver a semi-functional build tonight, then we can work out the remaining issues after that!

Edit 4: Had my pizza so I achieved one of my two tasks I guess! I'm taking a 20-30min break from this to tweak my VMWare Fusion config in the hopes of being able to build these faster (rebuilding my disk image as SCSI, assigning more cores and throwing 12GB of RAM at this so hopefully we'll get faster builds! I am working with a few devs from around the scene to get the various parts working and DarthPiggie has been kindly helping me with the dev environment issues so all being well we'll have a build tonight - though it will likely be published tomorrow now. :) As I said though, still has the audio and reboot bugs sadly. Those are next on my list to look at and are being looked at by other devs too.

Edit 5: Still unable to get this to build properly yet - facing a new error now, Christ this stuff is poorly documented CM - sort it out! >_>

Edit 6: Got a lot further this time, getting an adb connection to the kernel - looks like I'm missing a few binaries which I now have a fix for thanks to DarthPiggie so we're once again moving with this! Here's hoping I get a successfully booting build this time!

Edit 7: Looks like we may be making progress here - will update shortly depending on the results of the build I'm running now.
[Galaxy Note II, Galaxy S III Developer Discussion ] chrisaw:
Hi folks,

Two updates - firstly I did manage to get a working dev environment which I am now experimenting with but I have based my new environment on the following:

http://xdaforums.com/showthread.php?t=2024495

For now, I will not be posting updates to this thread since I feel that the development news on this really belongs in madmack's thread since he is the one really doing all of the work here! :) Just FYI - you can actually use the madmack build on our N7105s. Your build.prop values will, obviously, switch from N7105 to the AT&T version but from what I can tell this is purely network branding and there does not appear to be any negative effects to running macmack's build on our N7105s - we can always revert back to TW at the drop of a hat.

Warning: I *highly* recommend making a backup of your EFS partition and uploading it to dropbox. The dropbox part is a little paranoid I admit but it will give you a great 'disaster recovery' method just in case and this is all experiemental stuff we're doing here, doubtful it will ever harm your efs partition but if it did and you don't have a backup then good luck explaining how it happened to Samsung.
[Galaxy Note II, Galaxy S III Developer Discussion ] chrisaw:
N7105 instructions:

http://xdaforums.com/showthread.php?t=2072882
[Galaxy Note II, Galaxy S III Developer Discussion ] mithun46:
for audio problems and other hardware releated issues

u can download a custom rom for N7105

copy all lib files to your cm10 lib directory.

and flash and check

i dont have a n7105 but this is my suggestion as a developer
[Galaxy Note II, Galaxy S III Developer Discussion ] chrisaw:
We don't have audio problems on the N7105 - ROM works great. The in-call audio is just very quiet - AT&T users were complaining about exactly the same issue. A patch has now been provided and merged and we're all good. The reason we use separate 'radio's is because by default the AT&T radio works great! It just doesn't provide us with LTE capability. We can enable this in the 'hidden menu' but this has to be done every boot. If we install the modem and the CSC, then clear dalvik and cache we get things setup how it should be: LTE, 3G, 2G rather than 3G preferred. :)

Really though I just wrote that for two reasons:

1.) To keep things simple for new people trying out CM10 on their N7105 for the first time

2.) To keep a record of where to find all the bits and pieces needed to get this running smoothly for myself. :)

We don't actually need any specific 'tweaking' - the AT&T build works just fine for us.
[Galaxy Note II, Galaxy S III Developer Discussion ] frostmore:
If i am reading this right,we an flash the ATnT rom into the international Note2 lte and then flash the correct radio for the international note2 to align with the correct radio frequency to get 4g speeds.

Am i right to assume this?

What i understand is ATnT has different radio frequency compared to the rest of asia and some parts of europe.in fact,ATnT's radio frequency is what i consider to be very unique as it seems they are the only ones using these frequencies.
[Verizon Samsung Galaxy S III] aarond123:
I just installed jelly beans build 5 [http://xdaforums.com/showthread.php?t=1973982] onto my verizon galaxy s III and i rebooted and its stuck on the Jelly beans boot up screen. I plugged it into my PC and it wont recognize the phone. any solutions or do i have to get rid of it and how?
[Verizon Samsung Galaxy S III] Chuckleb0ne:
Boot into recovery and wipe cache.

How to boot into recovery: power off device and hold volume down+ Home button + power button.
[Verizon Samsung Galaxy S III] aarond123:
how do you wipe the cache?
[Verizon Samsung Galaxy S III] kintwofan:
Well in recovery it will say wipe cache. Then go to advanced and wipe dalvik cache, but i bet when you flashed you didn't factory reset. You are going to have to do that once wiping cache didn't work

Sent from my SGS3 running Eclipse 2.1
[Samsung Galaxy Nexus] Rxu:
Some brief history:

Rooted on stock ROM from factory everything working fine.

I was prompted for 4.2.1 OTA update, I accepted phone restarted with no errors.

I cannot get 3G or 4G around my house the signal is full and and i see the little up/down arrow as if some activity is happening.

Any app that requires data Facebook/Netflix/Speedtest tells me network is unavailable. I can still make and receive call and txt

Data does work once I leave my area and phone connects to a different tower I imagine.

I have spoken to tmobile support and a ticket was placed to check the status of the tower and they are reporting "no outage" .

Things I have tried for troubleshooting so far:

1. reset and re-enter apn details

2. tested my sim card in a CM7 rooted HTC Nexus same issue

3. Tried my sim in a stock tmobile blackberry curve , data worked (3G limited device)

4. My phone gets data when i force 2G network only

I would hate to flashback as I have everything setup perfectly and even my tether is working but any help is appreciated.
[Samsung Galaxy Nexus] kyokeun1234:
Try using a different radio
[Samsung Galaxy Nexus] Rxu:
Wouldnt the 4.2.1 OTA push out a new radio if needed? I'm not using a custom ROM all stock since day1 except for root w/gnex toolkit. Also the phone gets great 4G speeds when not in that problem area (that happens to be my house)
[Samsung Galaxy Nexus] gsxrmike04:
OP, have you found out what your problem was as I'm having the same problem with my phone
[Samsung Galaxy Nexus] gsxrmike04:
Update went to t mobile replaced my Sim now have data
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] .G33K:
Guys,

will it be possible to come back to the stock ROM by anychance if I update my phone with a custom by rooting it?? that's my major question. please advise? :)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] sheel9654:
Yes, it can be done download the original firmware of your phone and flash it as flashing some custom rom.....

Don't forget to hit thanks
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] MoonBlade:
yes just find the original firmware .ftf file and flash via flashtool.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] r7r8:
Flash Stock Rom .ftf file or restore from Nandroid Backup if u have created one..

But After flashing to stock.. Root will go..

If u restore from Nandroid backup.. U will retain your root
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] predatOr:
http://xdaforums.com/showthread.php?p=27376024

Download the .ftf file for your particular device from above thread... And then just flash the downloaded file by flashtool...

You will loose your root (bootloader will remain unlocked if you unlocked it previously)

:D press thanks if I helped you :D

Sent via 'rooted' BEETEL landline
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] m.syahril.niezam:
do you has lock or unlock bootloader.. just wanted to know..
[Motorola Droid RAZR] 85gallon:
What file are they located in? framework-res.apk??

The icon for my vibrate symbol when I set it to silent is very dim. It is not as bright as the other icons and is hard to see against the black background. I want to make it brighter.

I am running a variation of CM10.

Thanks for any help.
[Motorola Droid RAZR] hoitzi.flo:
I think they are located in the SystemUI. apk, but not for sure.... Try Romtoolbox, with it you can change the Status Bar Icons very easy (:

GeRAZR't mit meinem XT910

I
[Samsung Captivate Glide] dbrannon79:
***WARNING TO ALL***​

FLASHING ANY FIRMWARE CAN POTENTIALLY BRICK YOUR DEVICE ​

With that said, PLEASE use some precautionary measures to keep your device alive!​

There are many threads out there about making a backup copy of the "/efs" folder. that folder contains all of your IMEI information that is NOT replaceable! There are several cases all over the web, about people who have lost that information causing them not to have service, leaving them with "generic" IMEI's and some with all "0's"

I am posting this to help prevent thoes who are unaware of the consequences that happen when the EFS information is lost!

Here I will post a few guides and informational threads here in XDA to help with this.

EFS Tool for Windows

Guide for the Galaxy S II

A Story From the Vibrant

From the Galaxy Note​

I would also emphasize on making a nandroid backup of your complete system in recovery before starting to venture off onto any custom rom!

Here the folks at XDA have built a great community with a outstanding reputation to help one another advancing to the next level, also unlocking the extreme potential of our devices.

Be sure to "hit" the thanks button and when possible post a personal "Thanks" to the great devs and contributers we have here in XDA!

Feel free to add to this thread, any useful tips and such...

Thanks and God bless. :)
[Samsung Captivate Glide] dbrannon79:
I have not yet confirmed this, but here are three links to what may be a way for those who have lost their EFS to repair it!

there are other guides on how to recreate the efs folder but these tools may enable us to insert the correct information!

http://forum.gsmhosting.com/vbb/f611/android-language-editor-android-language-project-1543222/

http://xdaforums.com/showthread.php?t=1570342

[YOUTUBE]JqLK_2I-SBM[/YOUTUBE]

Thanks to Pierreone, he has provided this link providing a individual from Poland that can repair your IMEI through TeamViewer for a small donation. This may be out only hope!!

http://forum.samdroid.net/f70/repair-imei-s2-5729/

Please if anyone tries these methods, report here to confirm success or failed!

Thanks.
[Samsung Captivate Glide] lorddavid:
I just copy and paste in my pc the EFS folder, thats enough? and how you can identify if there is a problem in the EFS?
[Samsung Captivate Glide] dbrannon79:
That should be enough, but I would make backups in at least to other ways just to be safe, it's better to be safe than sorry. a single file can get corrupt without your knowledge! find a on-line file host like Google drive and that way if your pc was ever to go down it will always be there. Just don't loose your password!!!

to know that there is a problem, check the about phone section in status, the device will show your phone info, look for the IMEI! if it reads all 0's or a generic number starting with "04" and ending like "40000" you have problems! that is a unique serial number that identifies your individual phone!

I'm also not sure that if you were to use it to call an emergency hot line like "911" they would be able to locate you in time! that may not be true tho!
[Samsung Captivate Glide] lorddavid:
mines is ok, has al ot of different numbers. Just a question, what ab out the serial number? mines has only 00000000000
[Samsung Captivate Glide] dbrannon79:
the serial number so far is not a problem! it's the IMEI that you need to worry about! some refurbished phones and others that have flashed a custom rom will display an all "0's" serial no.

this is simply a helpful warning to make a backup before doing any modding! and finding ways for others to repair what is lost! if your phone is ok, just make a backup and your good! :D

One day we will figure out how to completely restore a lost efs and edit what is needed to get back to the norm!
[Samsung Captivate Glide] dbrannon79:
Thanks to Pierreone, I added a link to a thread that looks promising and has success reports!! :D
[Samsung Captivate Glide] roothorick:
Whew, I got lucky. I don't have an EFS backup and have flashed several custom ROMs, but I referenced About Phone against the label under the battery and my IMEI is still intact!

Could someone post what the Generic IMEI is so people can know whether their device is intact?

This is a a bigger problem than it sounds, because in some countries, changing the IMEI may be crime and land you jail time! If the IMEI under About Phone doesn't match the under-battery label, you could be in deep ****.
[Samsung Captivate Glide] braintweaker:
It is 004999010640000.

Have it, because the unlock made my network disconnect every 10 seconds.
[Samsung Captivate Glide] dmw0215:
About the efs folder ?

First of all Thank You for the heads up... I'm finding out a lot about backing up the efs folder but not a lot of detail about what exactly is contained in it other than imei and serial... probably because it shouldn't be fooled with but I like to know how things work in detail... is there any detailed post or site where I can get a complete explanation about it ? Complete file list/tree? What else does it control ? Can it be edited ?
[Samsung Captivate Glide] ninthsense:
This utility works fine. Just wanted to mention 2 things that you need to set before running this successfully:

Settings -> developer options -> android debugging enabled

Settings ->Developer options-> Root access -> set to 'apps and adb'
[Samsung Captivate Glide] gtmaster303:
I followed the guide from the Galaxy S2 forum, and after the first command:

busybox cp -a /efs /sdcard/efs/

Every line says "can't preserve ownership of..." and "operation not permitted"

Am I doing this right?

I did get an efs folder on my internal storage which is about 5mb in size after that command anyway

The rest of the guide, all of the other commands went through ok.
[Samsung Captivate Glide] SillyB:
Holy crap, I wish I had listened to this warning! After flashing a great new rom and getting it 98% set up the way I like it I was deleting some junk apps the marketplace had auto installed, one of them (for wi-fi hotspots I think) was to blame and must have toasted my IMEI.

I thought, oh I'll just restore my CWM backup from an older setup - md5 error can't restore. DOH! After spending most of two days hunting for solutions (none of them linked in this thread worked, except I did get to where I could place calls with a generic IMEI but no data or text). I finally was able to recalculate the md5 manually and restore my old backup, which then got stuck at boot logo, then I flashed a new ROM and the IMEI still isn't back! After much reading I have come to understand NANDROID BACKUPS DO NOT TOUCH THE EFS. That is one thing that that I didn't understand, and the reason I thought I was safe. Please update the OP to state that so more people like me will listen to your advice.

Backup your EFS! Thanks for the warning ;)