Related
So guys, what is the latest update, I just got this A500 yesterday and it says no update avil. when I manually check on WiFi.
Right now I am showing
Model: A500
Android ver: 3.0.1
Kernel: 2.6.36.3-00001-g9b3ce2b
Build Number: Acer_A500_1.104.02_COM_GEN1
It seems like I am missing an update, since I can't get Corporate/Activesync mail in E-mail client and I see others saying they received an update last week and it may have been pulled?
Thanks.
xendrome said:
So guys, what is the latest update, I just got this A500 yesterday and it says no update avil. when I manually check on WiFi.
Right now I am showing
Model: A500
Android ver: 3.0.1
Kernel: 2.6.36.3-00001-g9b3ce2b
Build Number: Acer_A500_1.104.02_COM_GEN1
It seems like I am missing an update, since I can't get Corporate/Activesync mail in E-mail client and I see others saying they received an update last week and it may have been pulled?
Thanks.
Click to expand...
Click to collapse
Have you looked at my thread this will fix anybody who has not yet received the 1.141.07_COM_GEN1 update. If it helps give thanks and support good sir. The instructions are pretty straight forward you do need root. Also Euclid's Brother was nice enough to help by making a tool so if you want you can skip the ADB steps.
Crsdr37 said:
Have you looked at my thread this will fix anybody who has not yet received the 1.141.07_COM_GEN1 update. If it helps give thanks and support good sir. The instructions are pretty straight forward you do need root. Also Euclid's Brother was nice enough to help by making a tool so if you want you can skip the ADB steps.
Click to expand...
Click to collapse
What if my current system is never meant to get 1.141.07_COM_GEN1, and then later on I can't update OTA to 3.1 because of the manual upgrade to 1.141.07.
I could see this happening, it happened with the Samsung Epic at one point.
Any way to go back to an old update if need be?
xendrome said:
What if my current system is never meant to get 1.141.07_COM_GEN1, and then later on I can't update OTA to 3.1 because of the manual upgrade to 1.141.07.
I could see this happening, it happened with the Samsung Epic at one point.
Any way to go back to an old update if need be?
Click to expand...
Click to collapse
Yes all you would need is the system.img and the boot.img from your device also acer is updating devices for free that have an update issue. you just have to send it to them. The reason you are not getting the update I would think though is that your kernel is different from the people in the USA since there are 2 different kernel versions. Have you registered with acer through your device?
Crsdr37 said:
Yes all you would need is the system.img and the boot.img from your device also acer is updating devices for free that have an update issue. you just have to send it to them. The reason you are not getting the update I would think though is that your kernel is different from the people in the USA since there are 2 different kernel versions. Have you registered with acer through your device?
Click to expand...
Click to collapse
Yes I have already registered, can I copy the existing system.img and boot.img from the system? If so where are they located? I am already rooted so I should have access to them if they exist.
Thanks.
xendrome said:
Yes I have already registered, can I copy the existing system.img and boot.img from the system? If so where are they located? I am already rooted so I should have access to them if they exist.
Thanks.
Click to expand...
Click to collapse
you can you either need to know how to use adb or get an app called terminal emulator. Either way the steps are the same.
1. Open ADB or Terminal type su hit enter.
2. type dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img (hit enter)
3. type dd if=/dev/block/mmcblk0p2 of=/sdcard/boot.img (hit enter)
4. type dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img (hit enter)
There you go you just backed up your current system
Crsdr37 said:
you can you either need to know how to use adb or get an app called terminal emulator. Either way the steps are the same.
1. Open ADB or Terminal type su hit enter.
2. type dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img (hit enter)
3. type dd if=/dev/block/mmcblk0p2 of=/sdcard/boot.img (hit enter)
4. type dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img (hit enter)
There you go you just backed up your current system
Click to expand...
Click to collapse
Well great.. looks like the SD card slot is damaged..
Put an SD card in, pushed down on it to get it to click and it made a noise like something broke... now it doesn't see the SD card.... lucky me. I bet one of the pins is bent.
Any tutorial's on how to pop the back off?
Look on youtube its not that hard
Sent from my PC36100 using XDA Premium App
Crsdr37 said:
Look on youtube its not that hard
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Well sure enough one of the Micro SD card slot pins was bent all to crap and broken. I took the unit back and did a swap at the store.
Now I am back, I have rooted and backed up those images so I have a good backup.
I guess I am still concerned with flashing the boot/system img files and then running the update.zip for 1.141.07.
I mean, if it was released for the US, why isn't it still being pushed OTA, and if it was pulled for a reason.. then there must be a problem with it?
What is the source for the files in the first post of this thread... - http://forum.xda-developers.com/showthread.php?t=1101859
xendrome said:
Well sure enough one of the Micro SD card slot pins was bent all to crap and broken. I took the unit back and did a swap at the store.
Now I am back, I have rooted and backed up those images so I have a good backup.
I guess I am still concerned with flashing the boot/system img files and then running the update.zip for 1.141.07.
I mean, if it was released for the US, why isn't it still being pushed OTA, and if it was pulled for a reason.. then there must be a problem with it?
What is the source for the files in the first post of this thread... - http://forum.xda-developers.com/showthread.php?t=1101859
Click to expand...
Click to collapse
It has a different kernel if yiu start on step one in my thread it replaces your kernel.so all would be good
Sent from my PC36100 using XDA Premium App
To Crsdr37
Crsdr37 said:
Have you looked at my thread this will fix anybody who has not yet received the 1.141.07_COM_GEN1 update. If it helps give thanks and support good sir. The instructions are pretty straight forward you do need root. Also Euclid's Brother was nice enough to help by making a tool so if you want you can skip the ADB steps.
Click to expand...
Click to collapse
Hi,
I also have the build, 'Acer_A500_1.104.02_com_GEN1', on my Iconia and patiently waited for an update. I guess it will never come?!
I found your thread, but was not able to find the app that would allow me to update without ADB.
Would appreciate any help.
Thanks
Hi,
My Nexus 4 failed to connect to my office wifi (LEAP network). The was due to a known issue on Android v4.2 (code.google.com/p/android/issues/detail?id=40023)
And the workaround is using a working wpa_supplicant from v4.1.2 to replace the current one on v4.2.
However Nexus 4 doesn't have v4.1.x ROM , and I tired v4.1.2 wpa_supplicant from Nexus S/7 but it didn't suit my Nexus 4 (I tried factory ROM and CyanolenMod), it cannot even list all available wifi connections with v4.1.2 wpa_supplicant.
So anyone out there able to connect to LEAP Wifi in your Nexus 4 successfully? If so could you pls share your experience?
And any other suggestions will be much appreciated!
Thanks and Regards!
I have the same problem, Nexus 4 with Android 4.2.1 ROM, LEAP WIFI not working. Also tried replacing wpa_supplicant with 4.1.2 version from Nexus 7 ROM, but it's not compatible with Nexus 4. Can someone provide a link to Nexus 4 ROM 4.1.2 version or correct wpa_supplicant file from that ROM please?
Zoccat said:
I have the same problem, Nexus 4 with Android 4.2.1 ROM, LEAP WIFI not working. Also tried replacing wpa_supplicant with 4.1.2 version from Nexus 7 ROM, but it's not compatible with Nexus 4. Can someone provide a link to Nexus 4 ROM 4.1.2 version or correct wpa_supplicant file from that ROM please?
Click to expand...
Click to collapse
Well, I'm glad to know I'm not the only one have this problem, the thing is there are no 4.1.2 ROMs for Nexus 4 - yet.
Hope v4.2.2 can fix this issue, finger crossed...
I managed to get it work! :laugh:
Here is my steps:
1) Install leap wifi free apk (com.oneguyinabasement.leapwifi.apk) then set up leap wifi connection FIRST.
2) Download wpa_supplicant.4.1.2 =>
http ://snk.to/f-cu3a753u
3) Then follow the steps (post #43) =>
http ://code.google.com/p/android/issues/detail?id=40023
Let me know if it helps.
I have a problem with my university wifi network.
I can connect but the connection isn't right. My speed is slow and spotty.
Anyone else?
Bump
I am having issues with LEAP. I tried the file from #53
3. Install the 4.1 version of wpa_supplicant
(commands assume the new version is in the Download directory - modify as needed)
On your device, open a terminal session, become root
Make the /system directory writeable:
mount -o rw,remount /system
Copy your new file there:
cp -p /sdcard/Download/wpa_supplicant-4.1.2 /system/bin
Make it executable:
chmod 775 /system/bin/wpa_supplicant-4.1.2
Rename the old version:
mv /system/bin/wpa_supplicant /system/bin/wpa_supplicant-4.2
Create a link to the new version (makes it clear which version you're running):
ln -s /system/bin/wpa_supplicant-4.1.2 /system/bin/wpa_supplicant
Verify this all worked:
/system/bin/wpa_supplicant -v
- should return version 4.1.2
Restart your system and LEAP should work as in 4.1.x.
I could not able connect to any network after that but I didnt know that i have to use a app (like LEAP wifi free) prior.I could not even serach for wifi networks. I have reverted what I did now i can able to wifi except LEAP. I am on Motley Kernel and PA ROM.
Now it seems the issue fixed and pushed to AOSP.
Cru,
Can you able to connect to other network after doing the work-round mentioned. Could you pls try connecting to a new network (not LEAP) and let know.
Franklin Bernard said:
Cru,
Can you able to connect to other network after doing the work-round mentioned. Could you pls try connecting to a new network (not LEAP) and let know.
Click to expand...
Click to collapse
Frank, you are right. It lost the ability to find new network connections after doing this work-around. We have to restore to new wpa supplicant file to fine/create the connections then change back to old wpa file to actually get it work. That's the reason I said we need setup leap wifi connection first
Cru_Su said:
Frank, you are right. It lost the ability to find new network connections after doing this work-around. We have to restore to new wpa supplicant file to fine/create the connections then change back to old wpa file to actually get it work. That's the reason I said we need setup leap wifi connection first
Click to expand...
Click to collapse
Thanks,
It seems the Code has been pushed to AOSP.
https://android-review.googlesource.com/#/c/50663/
Im trying to get the wpa_supplicant.conf file which has the fix. but I could not. Let me know if you can able to get it. I will post the file here if I get it .
Thanks
4.2.2 LEAP not working
Its very disappointing.
LEAP is not working in 4.2.2. I tried connecting to LEAP using LEAP Wifi Free app.
LEAP working
Franklin Bernard said:
Its very disappointing.
LEAP is not working in 4.2.2. I tried connecting to LEAP using LEAP Wifi Free app.
Click to expand...
Click to collapse
Finally LEAP is working. Its posted in the http://code.google.com/p/android/issues/detail?id=40023.
1. Backup
2. Please download the attachment from #104
3.Please follow the steps which is mentioned in #43 .
All the best,
Franklin B.
Franklin Bernard said:
Finally LEAP is working. Its posted in the http://code.google.com/p/android/issues/detail?id=40023.
1. Backup
2. Please download the attachment from #104
3.Please follow the steps which is mentioned in #43 .
All the best,
Franklin B.
Click to expand...
Click to collapse
Also worked for me, thanks a bunch to all.
I had this issue on my nexus 7 and was solved relatively easy by using an older version of the wpa_supplicant file for the nexus 7 but for the nexus 4 i guess there isn't a version that works...
Anyway the patched one the guy posted in post 104 works for me, the only difference I had to make was the auth_alg, mine was originally set to "LEAP" where as in his example he set it to OPEN SHARED LEAP, which I also needed to do in order to get it to work
I've been following the progress on official Ubuntu Touch port to Galaxy Tab 10.1 for a while and today they have updated the wiki for a dedicated session and early build install instructions.
This is an early build, some things work, some things are unknown and wifi is work in progress.
Installation
1. Download the ubuntu preinstalled and the p4wifi specific cyanogenmod image from the unlock instruction section below.
2. Put both zip files onto your sdcard
3. Enter recovery mode and do a wipe data/factory reset
4. Flash in this order:
First the cyanogenmod image (e.g. cm-10.1-20130325-UNOFFICIAL-p4wifi.zip)
Then the ubuntu image (this may take a while)
5. reboot
fix screen pixel ratio (this will become obsolete once the config file is included by default):
1. download p4wifi.conf: http://ubuntuone.com/688wubidavYnvfKvBWV7cY
2. copy p4wifi.conf into /etc/ubuntu-session.d/
3. reboot
Unlocking instructions
link to images
1. Ubuntu stuff:
Current: http://cdimage.ubuntu.com/ubuntu-to...urrent/quantal-preinstalled-phablet-armhf.zip
2. CyanogenMod image:
Current: http://ubuntuone.com/6V0ZxZ8cqB2AGcF8nImrDV
*Note: I am not involved with the development and I do not own this project, for more details please go to the link below.
https://wiki.ubuntu.com/Touch/Devices/p4wifi
Thanks, friend! I'm gonna test it soon :good:
AW: Official Ubuntu Touch for Galaxy Tab 10.1 is here!
I tried it. Installation worked fine and the first start (reboot after install) also went fine. Can't test more things than boot up right now - no time so far. I'll have a look this evening.
But why are there already users exsisting an how do i log in?
Sent from my One S using xda app-developers app
They say it's a test-only version and you can only log in to guest account...
and if you read the ubuntu-part file's name it is "quantal-PREINSTALLED", which means it is an installed image of Ubuntu that was tested on some previous devices by Ubuntu devs...
it's my thought, though...
AW: Official Ubuntu Touch for Galaxy Tab 10.1 is here!
Yes. It's a tech demo. But it already looks nice. I hope development goes on quickly.
Sent from my One S using xda app-developers app
customromfan said:
Yes. It's a tech demo. But it already looks nice. I hope development goes on quickly.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I'm testing this now, but I cannot find /etc/ubuntu-session.d/
Wifi not working after returning image back to Cyanogenmod
I followed your instructions and got Ubuntu touch working. After playing around with it for a while I decided to go back to my Cyanogenmod rom. For some reason now I cannot turn on the wifi. It is the same image that was working before. Can you offer some advice or assistance?
Thanks
Can someone make a video of this running? I want to do it myself but can't find the 10.1's charger
GazaIan said:
Can someone make a video of this running?
Click to expand...
Click to collapse
I've installed it with no problems, just followed the instructions in the first post...
I'm now attempting to get screen pixel ratio fixed and wifi running, and then will upload a video to youtube (probably in the next few hours)
Sorry, but I just can't find etc\ubuntu-session.d\ and can't make a persistent local directory in /data/ ...
If anyone can help me with these problems, please tell me...
(I chmodded the userinit.sh file for wifi and tried to fix the screen pixel ratio, but couldn't find or create the directories to put them)...
I'll upload a video anyway...
Dingles666 said:
I followed your instructions and got Ubuntu touch working. After playing around with it for a while I decided to go back to my Cyanogenmod rom. For some reason now I cannot turn on the wifi. It is the same image that was working before. Can you offer some advice or assistance?
Thanks
Click to expand...
Click to collapse
Not sure why you're having this problem. Maybe try format everything before flashing back or use a nand backup if you have one?
I think we must put the p4wifi.conf into ubuntu-session.d folder in the quantal before we install the image, right?
The proof I can provide is that there are folders named ubuntu-session.d and data in the quantal, but they're extracted to somewhere else during installation...
Video coming soon...
arashtarafar said:
Sorry, but I just can't find etc\ubuntu-session.d\ and can't make a persistent local directory in /data/ ...
If anyone can help me with these problems, please tell me...
(I chmodded the userinit.sh file for wifi and tried to fix the screen pixel ratio, but couldn't find or create the directories to put them)...
I'll upload a video anyway...
Click to expand...
Click to collapse
My memory is a bit vague on this, but I think it's in the /ubuntu folder, as well as the rest of the filesystem. It confused the hell out of me when I had it on my Sensation, it seemed like there was an entire filesystem at the root of the storage, then another inside /ubuntu where everything seemed to be.
You could use the search in Nautilus to find it as well, just make sure it's searching all subdirectories
I had a problem adding the p4wifi.conf file to /etc/ubuntu-session.d/ folder. This is how I solved it.
My problem basically was that when using adb shell to access the device I was inside the android system. And you need to get inside the ubuntu-system.
My way to get shell access to the ubuntu-system was the following:
>adb root
>adb shell
You should now see something similar to [email protected]:/ #
Then enter:
>ubuntu_chroot shell
You should now see something similar to [email protected]:/#
You are now in the ubuntu-system.
to get the p4wifi.conf file into /etc/ubuntu-session.d I did the following:
>cd /etc/ubuntu-session.d
>echo -e "GRID_UNIT_PX=10\nQTWEBKIT_DPR=2.0\nFORM_FACTOR=\"tablet\"" | sudo tee p4wifi.conf
For some reason there is a space between " and tablet. This space should be removed! It seems as if the forum adds it when rendering my post.
Now for the changes to take effect you will need to reboot your device. You can do that by writing the following
>reboot
I hope this helped someone that just as me struggled to get the pixel-ratio fix applied to the system.
Thanks, my friend.
I'm gonna try this and then will upload a video...
if we can find the way to fix WiFi according to this post:
http://forum.xda-developers.com/showpost.php?p=38988110&postcount=44
it will be awesome!
thanks again
arashtarafar said:
Thanks, my friend.
I'm gonna try this and then will upload a video...
if we can find the way to fix WiFi according to this post:
http://forum.xda-developers.com/showpost.php?p=38988110&postcount=44
it will be awesome!
thanks again
Click to expand...
Click to collapse
Yeah I read about this post too, I'm a bit busy this week but maybe I'll try it out this weekend.
I finally fixed screen pixel ratio by flashing the .zip package linked in post 15 in this thread ... simply adb push it and flash using CWM (ubuntu won't erase CWM after being flashed)...
I'm now going to fix WiFi to upload a video that's worth seeing ...
arashtarafar said:
Thanks, my friend.
I'm gonna try this and then will upload a video...
if we can find the way to fix WiFi according to this post:
http://forum.xda-developers.com/showpost.php?p=38988110&postcount=44
it will be awesome!
thanks again
Click to expand...
Click to collapse
I have tried this but no success Please share if anyone solves the wifi-issue.
---------- Post added at 03:38 PM ---------- Previous post was at 03:33 PM ----------
Does iwlist work for anyone? For me it dosen't even recognise the command.
does 3G work on this?
3G doesn't work yet, but I'm testing the OS on my galaxy tab 3G
yeah, I too have tried putting userinit.sh file in /data/loca/ with no success... but note that you must put the file using ubuntu_chroot shell... did you try that?
maybe we can put the commands in afterflash-p4.zip and then flash it, like the way we solved the screen pixel ratio issue...
inform us if this method worked for you
Enjoy. Don't forget to thank @beaups too, he discovered the eMMC backdoor and exploited it!
UPDATE: [8/2/16] I have recompiled the binary to fix issues with older ROMs like 4.4. This should fix all the issues with "This is for samsung device only" errors.
THIS WILL NOT WORK ON GALAXY S3/GALAXY S4/GALAXY S6|e/Galaxy S7|e. It will NOT work on AT&T
More info on doing this: here
DON'T UPDATE YOUR BOOTLOADER TO ANYTHING AFTER THE LATEST BUILD AS OF 4/19/16
Disclosure: I do not own a Note 4. The exploit happened to be applicable to the Note 4, and we compiled it for your devices rather than not release it at all. This seems like a reasonable and friendly thing to do for the community. I can't help you root or teach you how to use ADB. It's important you have the ability to do these things or research them a bit before blindly using this. I am very familiar with Samsung however, and time permitting, will do my best to help anyone having issues.
You should not run this if you don't understand it. For those who are capable but need some help go here
ROOT REQUIRED, we aren't responsible for anything you do with this.
You NEED a MicroSD, and it WILL be formatted during this process.
YOU MUST DISABLE REACTIVATION LOCK OR YOU WILL HAVE ISSUES!!!!!!!!!
You can download the eMMC brick bug check app on the Play Store to verify your CID starts with 15. If it does, you are good. If not, it will not work.
UPDATE: Anyone having issues with the "this is for samsung devices only error, please the fix attached to this post
Download
The code below is NOT a script, you must enter the commands manually.
First you must unzip the file.
Code:
adb push unlock_n4 /data/local/tmp/
adb shell
su
cd /data/local/tmp/
chmod 777 unlock_n4
chown root.root unlock_n4
./unlock_n4
Allow device to reboot. After full reboot, power down and pull battery. May need to run it twice if it doesn't work after the battery pull.
Paypal: [email protected] [COMPLETELY VOLUNTARY AND OPTIONAL]
Wow! Awesome. Would like to pay my bounty now.
Sent from my SM-N910V using Tapatalk
I can confirm this works. I tested on my Note 4 with 5.1.1 with temp root for Ryan. Running TWRP and about to install CM
Anyway now we can look into doing this for the AT&T model ? N910A? Since we have the Verizon model taken care of
Sent from my SAMSUNG-SM-N910A using Tapatalk
please post a video on how to do this because I don't know squat about adb. I have the Verizon note 4 with unlimited data. I know ill have to back up all of my data to my pc but I haven't even used the temp root and don't know how to do that either
nemopsp said:
Anyway now we can look into doing this for the AT&T model ? N910A? Since we have the Verizon model taken care of
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
Won't work unfortunately.
Akashp2011 said:
please post a video on how to do this because I don't know squat about adb. I have the Verizon note 4 with unlimited data. I know ill have to back up all of my data to my pc but I haven't even used the temp root and don't know how to do that either
Click to expand...
Click to collapse
That is out of the scope of this thread.
Akashp2011 said:
please post a video on how to do this because I don't know squat about adb. I have the Verizon note 4 with unlimited data. I know ill have to back up all of my data to my pc but I haven't even used the temp root and don't know how to do that either
Click to expand...
Click to collapse
right to learn adb bro ...
http://forum.xda-developers.com/showthread.php?t=2266638
Wow...waiting my device arrived tomorrow...thank it awesome
ryanbg said:
That is out of the scope of this thread.
Click to expand...
Click to collapse
okay then can you please provide step by step instructions on how to do this? I can manage to temp root my device
Great! Can't wait to get home!
Sent from my SM-N910V using XDA-Developers mobile app
munchy_cool said:
right to learn adb bro ...
http://forum.xda-developers.com/showthread.php?t=2266638
Click to expand...
Click to collapse
preciate ya
sixtythreechevy said:
Wow! Awesome. Would like to pay my bounty now.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Updated OP with address
Akashp2011 said:
okay then can you please provide step by step instructions on how to do this? I can manage to temp root my device
Click to expand...
Click to collapse
once you are comfortable with adb, the instructions in OP are a walk in the park. Read the other thread I linked to and try some adb commands like
adb reboot bootloader
it's easy , just give it a try first.
and this works for retail note 4, right? im just making sure because ive waited so d*mn long for this moment.. lol
Akashp2011 said:
and this works for retail note 4, right? im just making sure because ive waited so d*mn long for this moment.. lol
Click to expand...
Click to collapse
yes, make sure your cid is 15. Download brickbug app from Playstore and check cid, it should start with 15.
ryanbg said:
Won't work unfortunately.
Click to expand...
Click to collapse
Well Congrats for Verizon users!! #HAPPYDAY
Now wish someone could at least permanently root N910A model.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Do I just leave the file in my downloads on my pc or will it just transfer it automatically to my phone
HORIZONx720 said:
Do I just leave the file in my downloads on my pc or will it just transfer it automatically to my phone
Click to expand...
Click to collapse
like it says in OP, your card will be wiped so you have to backup card contents manually.
ryanbg said:
Enjoy. Don't forget to thank @beaups too
ROOT REQUIRED, we aren't responsible for anything you do with this.
You NEED a MicroSD, and it WILL be formatted during this process.
Download
Code:
adb push samsung_unlock_n4-2 /data/local/tmp/
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-2
chown root.root samsung_unlock_n4-2
./samsung_unlock_n4-2
Allow device to reboot. After full reboot, power down and pull battery. May need to run it twice if it doesn't work after the battery pull.
Paypal: [email protected] [COMPLETELY VOLUNTARY AND OPTIONAL]
Click to expand...
Click to collapse
How does one obtain root for this though?
I'm trying to diagnose an issue I'm having with my Metro (MetroPCS) SIM card. If anyone is using their X Compact on Metro or T-Mobile, could you please run the following command and let me know what the output is?
adb shell getprop ro.semc.version.cust.active
The output should be 3 digits. Mine is currently blank, so I'm trying to determine if it's because of my SIM card.
Additionally, could you go into the service menu (*#*#7378423#*#*) > Service info > Software info, scroll to the bottom and post the Current Modem Config value (I'll also need to know if you're using T-Mobile or Metro)?
Knowing this information will help me figure out my problem. Thank you.
camdecoster said:
I'm trying to diagnose an issue I'm having with my Metro (MetroPCS) SIM card. If anyone is using their X Compact on Metro or T-Mobile, could you please run the following command and let me know what the output is?
adb shell getprop ro.semc.version.cust.active
The output should be 3 digits. Mine is currently blank, so I'm trying to determine if it's because of my SIM card.
Additionally, could you go into the service menu (*#*#7378423#*#*) > Service info > Software info, scroll to the bottom and post the Current Modem Config value (I'll also need to know if you're using T-Mobile or Metro)?
Knowing this information will help me figure out my problem. Thank you.
Click to expand...
Click to collapse
/system/etc/customization/modem/amss_fsg_kugo_tar.mbn
Im on T-Mobile.
xXxMemerxXx said:
/system/etc/customization/modem/amss_fsg_kugo_tar.mbn
Im on T-Mobile.
Click to expand...
Click to collapse
Thanks. That's surprising because there's a T-Mobile specific modem binary file that should get loaded if the SIM is recognized. The one you mentioned is the default modem binary file. I'm interested to look at what other people are seeing.
camdecoster said:
Thanks. That's surprising because there's a T-Mobile specific modem binary file that should get loaded if the SIM is recognized. The one you mentioned is the default modem binary file. I'm interested to look at what other people are seeing.
Click to expand...
Click to collapse
Would loading the T-Mobile one change anything? Like better service? Because I did not have service when camping when other on T-mobile did. Other than that its been working for over 2 years.
xXxMemerxXx said:
Would loading the T-Mobile one change anything? Like better service? Because I did not have service when camping when other on T-mobile did. Other than that its been working for over 2 years.
Click to expand...
Click to collapse
Probably not, but I don't know for sure. Comparing the two files, the T-Mobile file is smaller and what is shown is not readable by me (encrypted or binary blob). I just thought that it would be loading. If you run the command I mentioned, I might be able figure out why it's not loading. Running the following command would also help me out:
adb shell getprop persist.sys.sim_config_ids
camdecoster said:
Probably not, but I don't know for sure. Comparing the two files, the T-Mobile file is smaller and what is shown is not readable by me (encrypted or binary blob). I just thought that it would be loading. If you run the command I mentioned, I might be able figure out why it's not loading. Running the following command would also help me out:
adb shell getprop persist.sys.sim_config_ids
Click to expand...
Click to collapse
If I'm honest, I have no idea how to do any of that. I just use my phone lol.
xXxMemerxXx said:
If I'm honest, I have no idea how to do any of that. I just use my phone lol.
Click to expand...
Click to collapse
No worries. It would involve downloading the Android debug bridge (adb) and running the commands with USB debugging enabled.