Develop Bugs

Looking for TELUS ROM for Motorola Charm

There appears to have been a TELUS software update for the Charm. Apparently I can't post a link, but if you search Google for "telus charm update" you can go to (what should be) the second result. Does this mean there should also be an SBF out there for it somewhere? Or would this software update have come in the "update.zip" format? Anyone have any information? My TELUS Charm is bricked—the only existing ROM that even slightly works is the T-Mobile one, but I don't get any phone service with it. All of the others give me MEM_MAP errors. Thanks!

I'm also looking for TELUS ROM for Motorola Charm.
Anyone can help me?

cjbi said:
I'm also looking for TELUS ROM for Motorola Charm.
Anyone can help me?
Click to expand...
Click to collapse
Here's the original Charm T-Mobile ROM and another ROM for Charm without Blur - but it didn't boot when I flashed it to my T-Mobile Charm using RSDLite 4.5.3 - I had to flash T-Mobile again.
Haven't found a way to (nan- or clockworkmod-) backup the entire ROM.
Charm ROMs:
http://and-developers.com/sbf:mb502
Also I'm trying to get Cronos (who's android 2.3 for Hero is amazing) to create a Charm port by donating him a Charm:
http://www.cronosproject.org/forum/viewtopic.php?f=39&t=664&p=23467

dvfk said:
Here's the original Charm T-Mobile ROM and another ROM for Charm without Blur - but it didn't boot when I flashed it to my T-Mobile Charm using RSDLite 4.5.3 - I had to flash T-Mobile again.
Click to expand...
Click to collapse
Thanks, but I don't need T-Mobile rom. I need TELUS rom.

Hi,
I have two TELUS charms.
Can anyone tell me how to do a backup of the ROM?
I will post it here once i get it.
Both phones are rooted, but I managed to almost brick one and so would like to clone the ROM over from the working phone .

OK so I managed to mostly fix my dead Telus Charm by flashing the ROM posted by toto221 at modmymobile (google Charm firmwares superthread, sorry I'm not allowed to post links yet).
However, this ROM, in addition to having BLUR, comes with Google search and Google Talk removed, and Spanish Yahoo as the default search provider.
On the plus side, it does come with Flash 9.1.
EDIT:
So by some weird chance, it seems that first flashing the spanish/portuguese ROM, then rebooting and reflashing the BASEM de-BLUR ROM, I now have a fully working BLUR-free Charm.

ergosteur said:
EDIT:
So by some weird chance, it seems that first flashing the spanish/portuguese ROM, then rebooting and reflashing the BASEM de-BLUR ROM, I now have a fully working BLUR-free Charm.
Click to expand...
Click to collapse
Fully working with Telus HSPA? I'm curious!

cjbi said:
Fully working with Telus HSPA? I'm curious!
Click to expand...
Click to collapse
Well, fully working with Bell HSPA. But I believe they're the same network and frequencies, so, theoretically, yes.
All the files I used are on my Mediafire account:
http://www.mediafire.com/?94z9t52nvd17d
Flash first: BASLA_U3... .sbf (Spanish ROM)
Flash second: BASEM_U3... .sbf (De-BLUR ROM)
I have never flashed the T-Mobile ROM though, so YMMV.

ergosteur said:
Well, fully working with Bell HSPA. But I believe they're the same network and frequencies, so, theoretically, yes.
All the files I used are on my Mediafire account:
http://www.mediafire.com/?94z9t52nvd17d
Flash first: BASLA_U3... .sbf (Spanish ROM)
Flash second: BASEM_U3... .sbf (De-BLUR ROM)
I have never flashed the T-Mobile ROM though, so YMMV.
Click to expand...
Click to collapse
Not working here. Unable to boot. Stuck in the bootloader.
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Click to expand...
Click to collapse
I have flashed the T-Mobile rom recently.

cjbi said:
Not working here. Unable to boot. Stuck in the bootloader.
I have flashed the T-Mobile rom recently.
Click to expand...
Click to collapse
Hmm strange. I did also flash with a messed-up "frankenstein" combination ROM with pieces of both in between, so that may have done something.
I'll post that up on mediafire too. (http://www.mediafire.com/?izn2srs2k2zbrg0)
When I get home I'll try flashing my other Charm that's still running stock Telus.
Also, by the way, is your phone unlocked? Because I bought both of mine unlocked, not sure what difference that makes.

ergosteur said:
Also, by the way, is your phone unlocked? Because I bought both of mine unlocked, not sure what difference that makes.
Click to expand...
Click to collapse
My phone is unlocked.
I will try tomorrow.
Thanks!

OK, so as I thought, the T-Mobile ROM is what causes problems. It has either a different locked bootloader or a newer version, so any of the other, older ROMS (Telus, deblur, etc.) cannot be flashed anymore.
Same problem as a bunch of VZW Droid owners have. http://www.droidforums.net/forum/dr...34-stuck-bootloader-err-a5-70-39-00-27-a.html
Now the only solution would be to flash the phone with an sbf that the phone would accept. Not sure if one of these is available, or if there's any way to hack one together from the T-Mobile and deblur ones.

Interesting developments! How did you create your "frankenstein" ROM? Perhaps such a ROM could be made with the T-Mobile firmware as a base, with the radio components of the Latin American ROM then added?

kgbd1 said:
Interesting developments! How did you create your "frankenstein" ROM? Perhaps such a ROM could be made with the T-Mobile firmware as a base, with the radio components of the Latin American ROM then added?
Click to expand...
Click to collapse
Well, all I did was extract the .sbf using MotoAndroidDepacker. Then I swapped the Code group .smg files around and rebuilt it.
Problem is, I have no idea what I'm doing or what CG31, CG37 and so on mean. I can try to guess based on the file size but... We probably need someone with some Motorola expertise.

ergosteur, I have flashed your "frankenstein" combination ROM today. Still unable to boot.

ergosteur said:
OK, so as I thought, the T-Mobile ROM is what causes problems. It has either a different locked bootloader or a newer version, so any of the other, older ROMS (Telus, deblur, etc.) cannot be flashed anymore.
Click to expand...
Click to collapse
So your phone can now ONLY flash the T-Mobile ROM?? - unable to "update" to the DEBLUR ROM??

dvfk said:
So your phone can now ONLY flash the T-Mobile ROM?? - unable to "update" to the DEBLUR ROM??
Click to expand...
Click to collapse
That's right. Because the DEBLUR ROM has an older bootloader or something, and Motorola doesn't allow downgrades.
Notice the T-Mobile ROM has a white Motorola logo on black background while booting, and some fancy colours behind it, while the other ROMs have a solid white background and black Motorola logo.

ergosteur said:
...the DEBLUR ROM has an older bootloader or something, and Motorola doesn't allow downgrades.
Click to expand...
Click to collapse
I had hoped it was simply because the T-Mobile ROM was SIM locked but the DEBLUR (or any other) ROM still doesn't boot even after I've bought and appiled unlock codes to two T-Mobile Charms.
I think you're right - it seem the bootloader (for USB flashing) is blocking it somehow - it stops booting and shows the bootloader with some error msg.
So the conclusion is: NEVER buy the T-Mobile Charm - go for Telus' only (until a new open community bootloader arrives).

Hi,
Can anyone confirm that an unlocked TELUS CHARM would be de-blured if:
From stock Telus rom and without ever flashing T-Mobile rom I flash:
BASLA_U3_00.32.203_R02_SIGNED_USABASCLALALA02C.0R_PDS000_GCXBASLCLALALA_P051_A021_M009_HWp3_1FF.sbf (spanish rom)
And then flashing:
BASEM_U3_01.12.4_DEBLUR_SIGNED_USABASIL01RINT150AI013.0R_PDS000_UC1SOMPBASLRTINT_P025_A016_HWp3_1FF.sbf (deblured rom)
I will get a WORKING 2G and 3G 850/1900 de-blured TELUS CHARM.
Is this possible?
Best Regards.

UPDATES:
I bricked my CHARM flashing DE BLURED firmware!!!
My TELUS CHARM boots to bootloader, and gives error:
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Never flashed T-Mobile firmware.

[ROM][03/10/11] Vision Sense 1.85.861.3 Untouched (from AUS RUU): Rooted/Deodexed

This is a flashable ROM from generated from Football's RUU_Vision_Hutch_AUS_1.85.861.3 release. It includes all applications and original vendor configuration. In other words, it is untouched with the exception of the following:
Rooted with my customized version of Superuser (required until ChainsDD releases a version with my patches).
Deodexed with moderate compression throughout.
Busybox installed in /system/xbin.
Added large APNS list to /system/etc.
WWE-equivalent language support.
There are no other changes. Just to be blindingly clear, this is NOT Virtuous; although a future version of Virtuous may be based on this ROM. Anyone building ROMs is welcome to use this as a base. Thanks again to Football for continuing to provide us with the latest RUUs.
Disclaimer: This is a one-time release. Unless a problem can be identified with the changes mentioned above (rooting, deodexing, etc), it will not be updated or supported. Use this as-is or find a ROM which uses this release as its' base if you would like support and/or expect to see changes.
Remember to hit the "Thanks" button if my work ends up being useful to you.
Download ROM
​(MD5:a764d0e09975209ab4268cfa3cef3167)​

Please do not ask me how this is different than the 1.85 orange release, as HTC does not exactly provide us change logs.

Orange, it is a name of telecom provider, right? If yes is it possible for you to get similar stock ROM but for Era polish provider and a little older, like 1.7...?
I am asking because as a newbe I didn't make any backup for my stock ROM delivered with my phone and I would like have a possibilty to back to the original stock for Era when for example I will have to give my phone back to service.
Or maybe You can suggest other way to back to Era stock, please indicate any thread if you know.
Thanks a lot for helping

Just flashed this ROM. It has a slow desktop draw issue. When I go to the main screen all icons appear very slowly. I do not understand if this ROM is untoched why it has the same issue as Virtuous?

denich said:
Just flashed this ROM. It has a slow desktop draw issue. When I go to the main screen all icons appear very slowly. I do not understand if this ROM is untoched why it has the same issue as Virtuous?
Click to expand...
Click to collapse
It's clearly a bug this version of Sense and has nothing to do with Virtuous. This is actually the case with many of the bugs in the ROM, we inherit them from HTC.

Just wondering, What did you use to Deodexed the apks/jars?

rmk40 said:
It's clearly a bug this version of Sense and has nothing to do with Virtuous. This is actually the case with many of the bugs in the ROM, we inherit them from HTC.
Click to expand...
Click to collapse
Seems like a bug only with froyo sense...

bigmoew said:
Seems like a bug only with froyo sense...
Click to expand...
Click to collapse
Push Rosie.apk from 1.82 or 1.72 to fix the problem.

rmk40 said:
Push Rosie.apk from 1.82 or 1.72 to fix the problem.
Click to expand...
Click to collapse
I applied the patch which returns rosie to 1.72 (the patch from virtuous thread). it do no help the problem remains

[ROM][29July2013] mROM v4.0 JSS15J - stock 4.3 + GAPPS, MOD(s), etc.

Here is a 4.3 ROM built from AOSP source designed to emulate what a Verizon 4.3 ROM would be like. The changes from AOSP include the addition of GAPPS, addition of Verizon apps, appropriate binaries so everything works, addition of busybox, correct eri.xml, home screen layout to mimic a stock ROM, and the removal of the tethering restriction. The ROM is not pre-rooted, so flash Chainfire's SuperSU if you want root.
As usual, flash at your own risk and post any successes or problems.
Download Link(s) for v4.0: MD5: be4377ab16432112f09d18ae37c91041
DOWNLOAD via Goo.im
Cubby.com MIRROR
SuperSU v1.51 - you may want to check for a more recent version if this link becomes outdated. Flash after you flash the ROM.
Bugs - text-to-speech may not work correctly. Please flash fix attached to this post after flashing the ROM. Thanks AndroJak!
MODS:
Extended Power Menu - CM style
- Ability to reboot, hot reboot, reboot recovery, & reboot bootloader.
- Replaces /system/framework/android.policy.jar
- Thanks to Cyanogenmod and xIC-MACIx
- DOWLOAD
- MIRROR
Thanks to mmuzzy for help building from aosp (fixing t-cdma64 in eri.xml and cell broadcasts menu, plus other stuff I'm probably forgetting), adrynalyne, and djp952 for help building from AOSP.

mwalt2 said:
Here is a stock, rooted, busybox, etc. ROM built from the 4.1.1 AOSP source for Verizon. It has GAPPS included from the GSM developer preview and the Verizon apps as well (MyVerizon and the backup one). My attempt was to make a stock rooted ROM for Verizon based off of the 4.1.1 source on AOSP. Some things are still added to this rom from 4.0.4 IMM76K Verizon ROM, but I did include the new binaries for toro. I haven't fully tested everything, but camera, google now, gps, and wifi all work as expected. I'll try to get some add-on's / mods before too long and have them posted as flashable .zips.
As usual, flash at your own risk and post any successes or problems.
Download Link(s):
about 5 min or so....
Click to expand...
Click to collapse
first cant wait!!! ^.^

Here we go!!!!!

Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.

Download for 1 server is ready now. I'll get a mirror up as well.
BrandT90 said:
Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.
Click to expand...
Click to collapse
Yes, it's working. I asked it how long a bridge was and it read the answer back to me. I haven't done much more than that though yet.

Downloading. Looking forward to this. Thanks Mwalt for sharing!!!
Quick DL as well. 2 minutes has got to be a new record for a JB rom

BrandT90 said:
Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.
Click to expand...
Click to collapse
OP says Google Now is working. I'm downloading now.

excellent. you're a regular johnny on the spot!

downloading now, hope its all good! i'm looking for a "stock jb" style rom of the newest update. ill post my outcome shortly. going to test the basics that are supposed to work.

Is a flash to the JB bootloader recommended? Finally, a build that seems to have all/most components working! No issues with the 4G's or the LTE's?? Lol.
Galaxy Nexus - Slim ICS 4.2

Downloading now. Any thoughts on current JB kernel compatibility?

i wiped data, cache and dalvik cache 2x each, installed and installed trinity kernel on top and hit reboot. (i like trinity for the colors and such, and good battery life ).
first boot took a minute.
updating some apps and gonna test some things.
still getting t-cdma 64 as a carrier

mwalt2 said:
Here is a stock, rooted, busybox, etc. ROM built from the 4.1.1 AOSP source for Verizon. It has GAPPS included from the GSM developer preview and the Verizon apps as well (MyVerizon and the backup one). My attempt was to make a stock rooted ROM for Verizon based off of the 4.1.1 source on AOSP. Some things are still added to this rom from 4.0.4 IMM76K Verizon ROM, but I did include the new binaries for toro. I haven't fully tested everything, but camera, google now, gps, and wifi all work as expected. I'll try to get some add-on's / mods before too long and have them posted as flashable .zips.
As usual, flash at your own risk and post any successes or problems.
Download Link(s):
DOWNLOAD from Dev-Host
MD5: 8383b87cc2f9e5b510807c3034052ffe
Click to expand...
Click to collapse
Any issues in this build? Also, what are the install instructions?

when going to sounds to set ringtones i have a lot of doubles of default ringtones, wonder where i can remove them?

^System/media/ringtones maybe?
Galaxy Nexus - Slim ICS 4.2

works well so far. thanks!

xweaponx said:
Downloading now. Any thoughts on current JB kernel compatibility?
Click to expand...
Click to collapse
I've always used stock, so I can't really comment. Now that source is out, I'd expect the JB kernels to work better.
imablackhat said:
still getting t-cdma 64 as a carrier
Click to expand...
Click to collapse
No sure what causes this, but I've never seen it with this build or the previous developer preview build. Did it happen on first boot before you installed anything else?
tycoon177 said:
Any issues in this build? Also, what are the install instructions?
Click to expand...
Click to collapse
I'd recommend a full factory reset, but people can try what they feel comfortable with. Personally, I did a factory reset, wiped both caches, and then flashed the ROM (with TWRP).
imablackhat said:
when going to sounds to set ringtones i have a lot of doubles of default ringtones, wonder where i can remove them?
Click to expand...
Click to collapse
Do you have any on your sdcard partition in the Ringtones folder? If not, I'd check \system\media\audio path (subfolders for ringtones, alarms, etc). Delete any duplicates you find in there. I don't have any duplicates and there aren't any in the rom.zip I uploaded.

just overwrote mms.apk in system/apps to get the custom pink mms, and got a quick reboot to my boot screen, this never happened on 4.1 roms that weren't source, don't know if this is normal because i replaced the app and it was a one time thing (i hope). as far as going to system/media/ringtones, i see them but there arent any doubles, however theres doubles when i go to select a ringtone from the menu, for everything system related, ringtones and notifications.

What issues have people had? Any boot issues?

I replaced the "stock" keypress ogg files from ics/jelly bean that sound better with this 4.1.1 release, the new key click sounds are horrible. works fine. i used to have t-cdma 64 with any build from 4.1.1 there is a fix that works that ill just apply. its a xml file or something.

Wifi Region code Connectivity problems: A Solution

Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
March 19,2014
Added new Version for newer CM11 nightlies
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
March 25 Note: Added zip for new versions of Commotio Rom
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk

arifqur said:
Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk
Click to expand...
Click to collapse
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later

atifsh said:
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later
Click to expand...
Click to collapse
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.

arifqur said:
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.
Click to expand...
Click to collapse
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.

atifsh said:
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.
Click to expand...
Click to collapse
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.

arifqur said:
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.
Click to expand...
Click to collapse
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.

atifsh said:
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.
Click to expand...
Click to collapse
Yup it is pretty simple. Glad this problem has been sorted out, kind-of

arifqur said:
Yup it is pretty simple. Glad this problem has been sorted out, kind-of
Click to expand...
Click to collapse
yeah flashing every time you update is a mess

atifsh said:
yeah flashing every time you update is a mess
Click to expand...
Click to collapse
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL

arifqur said:
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL
Click to expand...
Click to collapse
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone

atifsh said:
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone
Click to expand...
Click to collapse
Not all phones have this problem and also a lot of custom rom devs apply this patch directly in their roms.
I have an S3, S4, HTC One, Note 2, S2 Skyrocket, Nexus4 and none of them have this problem. Even on OGP this problem started from CM11 Jan 22, 2014 build. The Jan 21st build flashes without this issue.

Flashable zip added for new Commotio Rom Nightlies

Any chance to apply the patch to a stock rooted rom?
Thanks

Region Code
Hi can someone fix this file for region code?

nagi_007pk said:
Hi can someone fix this file for region code?
Click to expand...
Click to collapse
Sorry man.
Tried to patch it but seems to be way different in code from the rest of the roms that I have seen.

Can someone post the patch for latest cm nightlies?

nagi_007pk said:
Can someone post the patch for latest cm nightlies?
Click to expand...
Click to collapse
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.

arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based

nagi_007pk said:
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based
Click to expand...
Click to collapse
Here you go.
Hope it works

arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
just tried it latest nightly, still the same.

Where the best rom out there???? Need help

Guys I try a few rom out there and I end in issues that really bothers like no WiFi calls drops no Bluetooth etc. I really want a cool customizable rom out there that is 100% stable thanks in advance has to be 4.4.2
Sent from my SM-N900T using XDA Free mobile app

Best rom is the original one just root and flash custom recovery you're good to go.

ZzB3B0zZ said:
Guys I try a few rom out there and I end in issues that really bothers like no WiFi calls drops no Bluetooth etc. I really want a cool customizable rom out there that is 100% stable thanks in advance has to be 4.4.2
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
The best ROM is the one you like. I know you said 4.4.2, but you might want to consider going to a Lollipop ROM. I've been using AryaMod from over in the international Note 3 forum, and it is awesome. Best ROM i've used for the Note 3. It's a Note 4 port, very stable, and is very customizable. Plus, the development is very fast with that ROM. Take a look for yourself.
http://forum.xda-developers.com/galaxy-note-3/development/rom-aryamod-v1-tw-lollipop-t2990920

Techngro said:
The best ROM is the one you like. I know you said 4.4.2, but you might want to consider going to a Lollipop ROM. I've been using AryaMod from over in the international Note 3 forum, and it is awesome. Best ROM i've used for the Note 3. It's a Note 4 port, very stable, and is very customizable. Plus, the development is very fast with that ROM. Take a look for yourself.
http://forum.xda-developers.com/galaxy-note-3/development/rom-aryamod-v1-tw-lollipop-t2990920
Click to expand...
Click to collapse
How do you get this to work with out Tmobile SM-N900T?

10507 said:
How do you get this to work with out Tmobile SM-N900T?
Click to expand...
Click to collapse
Yes, it was a little confusing at first. Here's what I did to get it working.
1. I used this thread to upgrade to NK3 baseband and then root it via Odin.
http://forum.xda-developers.com/not...-to-root-nf4-knox-0x0-effortless-nf4-t2846142
2. Then I downloaded TWRP Manager from the Play store and installed TWRP 2.8.4.0
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
3. Next, I did a full wipe/data factory reset, then flashed AryaMod
forum.xda-developers.com/showpost.php?p=58582992&postcount=2034
4. Finally, I rebooted and flashed v2 of the wifi fix here:
http://forum.xda-developers.com/galaxy-note-3/themes-apps/wifi-bluetooth-fix-s5-ported-roms-t2938607
That should get you up and running. Enjoy.

Techngro said:
Yes, it was a little confusing at first. Here's what I did to get it working.
1. I used this thread to upgrade to NK3 baseband and then root it via Odin.
http://forum.xda-developers.com/not...-to-root-nf4-knox-0x0-effortless-nf4-t2846142
2. Then I downloaded TWRP Manager from the Play store and installed TWRP 2.8.4.0
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
3. Next, I did a full wipe/data factory reset, then flashed AryaMod
forum.xda-developers.com/showpost.php?p=58582992&postcount=2034
4. Finally, I rebooted and flashed v2 of the wifi fix here:
http://forum.xda-developers.com/galaxy-note-3/themes-apps/wifi-bluetooth-fix-s5-ported-roms-t2938607
That should get you up and running. Enjoy.
Click to expand...
Click to collapse
Any special kernel you have to flash after flashing the main ROM?

Nope. Just flash and go.

Techngro said:
Nope. Just flash and go.
Click to expand...
Click to collapse
From your usage, can you tell us what is working and what is not beside the NFC?

Well...from my experience everything is working. Wifi, bluetooth, gps, etc. I haven't had any fc on anything, and all of the s-pen features work as they should. I haven't dug down and played with all of the settings yet though. There are some advanced settings that I'd like to play with. My speeds on T-Mobile are fantastic, but I don't think that is the ROM.

How is the rom working? Any issues
Techngro said:
Well...from my experience everything is working. Wifi, bluetooth, gps, etc. I haven't had any fc on anything, and all of the s-pen features work as they should. I haven't dug down and played with all of the settings yet though. There are some advanced settings that I'd like to play with. My speeds on T-Mobile are fantastic, but I don't think that is the ROM.
Click to expand...
Click to collapse
Hi Techngro,
I think you are on the lollipop rom for couple of days. I am planning to install the AryaMod V2.0 on my stock rom, are there any issues you encountered or any FC. The latest AryaModV3.1 has been released, is it better to install the V2.0 or go with V3.1. Any suggestions.
Regards,
Say2009

say2009 said:
Hi Techngro,
I think you are on the lollipop rom for couple of days. I am planning to install the AryaMod V2.0 on my stock rom, are there any issues you encountered or any FC. The latest AryaModV3.1 has been released, is it better to install the V2.0 or go with V3.1. Any suggestions.
Regards,
Say2009
Click to expand...
Click to collapse
I haven't flashed the 3.1 ROM yet because I like to wait a while and see if there are any issues with new updates. There have been some reports of some problems, but you can never know whether that is actually the ROM, or just user error (didn't wipe properly, dirty flash, etc.).
My suggestion to you is, since you're going to flash anyway, flash the latest update first (3.1), and see if it works for you. If you have any problems then you can flash 2.0.

ZzB3B0zZ said:
Guys I try a few rom out there and I end in issues that really bothers like no WiFi calls drops no Bluetooth etc. I really want a cool customizable rom out there that is 100% stable thanks in advance has to be 4.4.2
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
Dude, you are using a T-Mobile Note 3 (based on your signature)...
There is simply no ROM that compares to Tweaked ROM. 100% fully functional and tons of customization options.
Some have recommended you move to a Lollipop ROM... Since your statement is avoiding bugs, issues, etc, I would avoid following that bad advice, since every single one of them will be a port, and none of them will have working NFC, and you are bound to not be satisfied. I can't for the life of me understand why people pay 700 bucks for a handheld computer, then ruin it's functionality and strip the cool software and features from it that they paid tons of money for... but to each his own I guess.
Like I said, based on your post, you are best off with Tweaked ROM by dwitherell. I don't know the guy but dang he seems to know his stuff, and does all of his work solo. I've been using his ROMs since I got my Note 2. Won't touch anything else.

Techngro said:
I haven't flashed the 3.1 ROM yet because I like to wait a while and see if there are any issues with new updates. There have been some reports of some problems, but you can never know whether that is actually the ROM, or just user error (didn't wipe properly, dirty flash, etc.).
My suggestion to you is, since you're going to flash anyway, flash the latest update first (3.1), and see if it works for you. If you have any problems then you can flash 2.0.
Click to expand...
Click to collapse
Thank You for quick reply, I will go with 2.0 and wait for the stable release as I see lot of issues with 3.1.
Regards

say2009 said:
Thank You for quick reply, I will go with 2.0 and wait for the stable release as I see lot of issues with 3.1.
Regards
Click to expand...
Click to collapse
can confirm 3.1 works. I tried it out since i like to see what each rom offers and so far havent encountered no bugs and the battery life is amazing. Glad i read into this.

Best ROM out there is the ROM that doesn't mess up your phone, everything works, get and receive all your calls and messages, take great pics, with super battery life. No f/c's ,no freeze, no black unresponsive screen, no incompatible apps.
It's called .................... Stock/rooted/debloated ROM.
Pp.

Thank You
ciner01 said:
can confirm 3.1 works. I tried it out since i like to see what each rom offers and so far havent encountered no bugs and the battery life is amazing. Glad i read into this.[/QUOTE
Thank You
Click to expand...
Click to collapse