Related
My nephew took his U.S.A. AT&T locked Atrix HD to the the Philippines and bought a sim locally over there. He entered a wrong unlock code too many times and now the phone says subsidy locked. please contact service provider. It is hard locked with no place to enter an unlock code.
Only work around I've been able to find has something to do with flashing brazil radios however that only seems to work on Atrix 2 and older phones and not the Atrix HD. Is there any custom rom/radios flash that would get the phone working again?
I've contacted AT&T and they said there's nothing they can do and suggested I contact Motorola.
Motorola said they can fix it for $109 service fee. Phone is not worth that kinda money,
How would Motorola fix it? If they can flash it back to factory fresh you would think there would be someway that I could do similar.
I hear that there may be unlock services that can also unlock hard locked phones. anyone know of one that has worked for them?
thanks for any help
If you phone is saying contact service provider with nowhere to put in a code, if you leave it there for awhile it should change to enter subsidy password.
Sent from my MB886 using Tapatalk
I have tried leaving it on that screen for 3 days straight and it never changed.
I cant be the only one with this problem..You would think there would be a workaround by now. I wonder if there's a way to flash a different radio like the brazil radios for th atrix 2, but ones that would work on the Atrix HD?
thanks
kingatmos said:
If you phone is saying contact service provider with nowhere to put in a code, if you leave it there for awhile it should change to enter subsidy password.
Sent from my MB886 using Tapatalk
Click to expand...
Click to collapse
You can flash different radios via fastboot. You just need to download the factory firmware, extract the radio bin file, and flash it.
1) install the adb/fastboot files to a single directory on my computer (I use the files from Myth Tools);
2) download the firmware (http://sbf.droid-developers.org/phone.php?device=7);
3) extract the NON-HLOS.bin file to your computer in the adb/fastboot directory from step 1;
4) open a command prompt window as an administrator;
5) install the Motorola USB drivers and connect my booted phone with USB debugging enabled;
6) from the command line, type "adb reboot bootloader" and press the enter key to get my phone into AP Fastboot Flash mode;
7) from the command line, type "fastboot flash modem NON-HLOS.bin" and press enter; and
8) reboot the phone and check to make sure the new baseband is shown.
I downloaded Android 4.1.1 from that site to flash back to the stock rom after trying out CM 11. That should of flashed the NON-HLOS.bin too right?
If so it didn't help..phone is still stuck at the subsidy lock screen.
Do you know of any specific radio that would fix the subsidy lock issue?
thanks
audit13 said:
You can flash different radios via fastboot. You just need to download the factory firmware, extract the radio bin file, and flash it.
Click to expand...
Click to collapse
Gorrillasnot said:
I downloaded Android 4.1.1 from that site to flash back to the stock rom after trying out CM 11. That should of flashed the NON-HLOS.bin too right?
If so it didn't help..phone is still stuck at the subsidy lock screen.
Do you know of any specific radio that would fix the subsidy lock issue?
thanks
Click to expand...
Click to collapse
Where were you advised to flash back to stock? All i see is radio/non-HLOS.bin being discussed.
Sent from my MB886 using xda app-developers app
I never said I was advised to flash back to stock...all I was saying is that I had been trying a modded rom previously and had already flashed the stock ATT rom and was just asking if that had flashed my NON-HLOS.bin as well.
palmbeach05 said:
Where were you advised to flash back to stock? All i see is radio/non-HLOS.bin being discussed.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Gorrillasnot said:
I downloaded Android 4.1.1 from that site to flash back to the stock rom after trying out CM 11. That should of flashed the NON-HLOS.bin too right?
If so it didn't help..phone is still stuck at the subsidy lock screen.
Do you know of any specific radio that would fix the subsidy lock issue?
thanks
Click to expand...
Click to collapse
To be sure the radio was flashed, check under settings --> About Phone.
audit13 said:
To be sure the radio was flashed, check under settings --> About Phone.
Click to expand...
Click to collapse
it sounds like he can't get into his phone due to the subsidy lock?
All AHD sbf/zip files have a xml file in it. its even stated in other threads that this file exists in the zips. RSD Lite flashes according to what the xml file says, thats why they say in the guides to delete certain lines, that way you don't flash something to brick/damage your phone.
you could have easily booted into fastboot and flashed the file, this is what was you were being advised to do.
palmbeach05 said:
it sounds like he can't get into his phone due to the subsidy lock?
All AHD sbf/zip files have a xml file in it. its even stated in other threads that this file exists in the zips. RSD Lite flashes according to what the xml file says, thats why they say in the guides to delete certain lines, that way you don't flash something to brick/damage your phone.
you could have easily booted into fastboot and flashed the file, this is what was you were being advised to do.
Click to expand...
Click to collapse
I can get into the phone and all functions work except making calls. When I put in a sim I get an error message saying subsidy locked. contact service provider. Only emergency calls can be made. and there's a button that says dismiss, but there is no where to put in a code.
When I flashed the stock firmware the only 2 lines I removed were the 2 "getvar" lines because rsd lite will not flash with those lines left in, so I am assuming that everything got flashed including the NON-HLOS.bin, but just to make sure I flashed just the NON-HLOS.bin as sugested by audit13 and it still says the subsidy lock message.
I have searched the web for several days now and it appears this is some kind of permanent lock. Older Atrix, Atrix 2 phones I read you could flash Brazil radios and it would work but I have found no mention of any success on the Atrix HD.
For a somewhat aging, but still very useful phone you would think there would be some kind of work around for this by now. ugh!
thanks
Hi Guys,
I am new in Xposed Modules.I read about the Xposed framework in xda and other websites.some websites have really good tutorials about it.
So what I understand is that we can modify a function and its return values using the Xposed Framework.So My Question is that
We can get the IMEI of a device using this code
Code:
TelephonyManager telephonyManager = (TelephonyManager)getSystemService(Context.TELEPHONY_SERVICE);
telephonyManager.getDeviceId();
It means that the TelephonyManager class has a function called getDeviceId() which returns the IMEI No right ?
so after further checking I found a class which has the function
Code:
com.android.internal.telephony.PhoneSubInfo
and
com.android.internal.telephony.gsm.GSMPhone
So modifying that function to return a custom value is possible right ?
if it is possible then the function
Code:
TelephonyManager telephonyManager = (TelephonyManager)getSystemService(Context.TELEPHONY_SERVICE);
telephonyManager.getDeviceId();
will be returning the new Values right ?
I have tried to create a sample application and it sort of worked in emulator.
Code:
findAndHookMethod("com.android.internal.telephony.PhoneSubInfo", lpparam.classLoader, "getDeviceId",new XC_MethodHook()
{
@Override
protected void afterHookedMethod(MethodHookParam param)
throws Throwable {
// TODO Auto-generated method stub
super.afterHookedMethod(param);
param.setResult("99999999999");
}
});
The Modified value is shown on the Settings -> About Phone - > Status
and also when we take dialer and type *#06#
So have anyone tried this method ?
Correct on all counts. You may want to use XC_MethodReplacement, though (and the shortcut XC_MethodReplacement.returnConstant(...) method).
GermainZ said:
Correct on all counts. You may want to use XC_MethodReplacement, though (and the shortcut XC_MethodReplacement.returnConstant(...) method).
Click to expand...
Click to collapse
My question is will it be sending the original IMEI or this modified IMEI if checked with Network Provider ?
vivekkalady said:
My question is will it be sending the original IMEI or this modified IMEI if checked with Network Provider ?
Click to expand...
Click to collapse
If you replace the method, it will be replaced. Similarly, if you set the result, the result you set will be returned. If only that method is used to get the IMEI, then only the modified IMEI will be sent to whoever requests it.
GermainZ said:
If you replace the method, it will be replaced. Similarly, if you set the result, the result you set will be returned. If only that method is used to get the IMEI, then only the modified IMEI will be sent to whoever requests it.
Click to expand...
Click to collapse
is it legal to post such an application ?
also is there any other method to get the IMEI no ?
when I searched,I only got this method to get IMEI from phone.
vivekkalady said:
is it legal to post such an application ?
Click to expand...
Click to collapse
I don't see why not, since it's not actually changing the IMEI for your phone (only what apps see as the IMEI).
vivekkalady said:
also is there any other method to get the IMEI no ?
when I searched,I only got this method to get IMEI from phone.
Click to expand...
Click to collapse
I don't know.
You can get the number from /system/bin/dumpsys, but that's not something an app would normally do.
Please kindly post!
Many will need your app, including me to test recovering lost IMEI, xD
The legality depends on your local authority.
Thank you for giving me, a noober, hope
xperia_loser said:
Many will need your app, including me to test recovering lost IMEI, xD
The legality depends on your local authority.
Thank you for giving me, a noober, hope
Click to expand...
Click to collapse
It won't help you, actually, and methods of changing your real IMEI aren't allowed on XDA for legal reasons.
Appology for missing out the regulations
GermainZ said:
It won't help you, actually, and methods of changing your real IMEI aren't allowed on XDA for legal reasons.
Click to expand...
Click to collapse
Then, it's restricted. I did not notice the regulations; however, to be honest, I only need to change the 'unknown IMEI' back to my real IMEI which was lost due to careless ROM flashing with no back-up.
It seems that changing IMEI is illegal regardless of intention as nobody can guarantee others' intentions.
Thank you for your information.
xperia_loser said:
Then, it's restricted. I did not notice the regulations; however, to be honest, I only need to change the 'unknown IMEI' back to my real IMEI which was lost due to careless ROM flashing with no back-up.
It seems that changing IMEI is illegal regardless of intention as nobody can guarantee others' intentions.
Thank you for your information.
Click to expand...
Click to collapse
I lost my imei # the same way you did and I sure would like to find a way to put my imei# back in My phone. All I want to do is get my phone working again. I don't think I will get any support from customer service. Any help would be greatly appreciated.
[quote name="xperia_loser" post=54890103]Then, it's restricted. I did not notice the regulations; however, to be honest, I only need to change the 'unknown IMEI' back to my real IMEI which was lost due to careless ROM flashing with no back-up.<br />
<br />
It seems that changing IMEI is illegal regardless of intention as nobody can guarantee others' intentions.<br />
<br />
Thank you for your information.[/QUOTE]<br />
I lost my imei # the same way you did and I sure would like to find a way to put my imei# back in My phone. All I want to do is get my phone working again. I don't think I will get any support from customer service. Any help would be greatly appreciated.<br/>
Given that there are legal uses of this, I see it falling under the area that the VCR fell under during it's rise and speculation that it would contribute to illegal activity (piracy). Just because people CAN use something for illegal purposes, does not make the tool/item itself illegal. ****, how many of us have broken the law in the past by rooting our phones in violation of certain US laws? But it went on here, totally fine.
This module is fine because it doesn't actually change your IMEI, only spoof it for apps.
Changing your IMEI is illegal (this isn't up for discussion - it just is in the US, and that's where XDA is), which makes it forbidden on XDA as per the forum rules.
You can read some more about this here: http://forum.xda-developers.com/showthread.php?t=2249666
@vivekkalady Hi , I am trying on bluestacks latest with xposed installed, but its not working there , is there any chance to make it work ? i want to change to specific imei.
I have an m7_ul, rooted and soff, currently running latest firmware from vomer, hboot 1.57, twrp 2.8.0.1, viperone 7.0.1, on TMOUS.
The text in Settings/About/Phone Identity/Model Number is "HTC One_m8". Where is this text? It's not in build.prop..
Ideas?
Thanks in advance.
psipro_1989 said:
I have an m7_ul, rooted and soff, currently running latest firmware from vomer, hboot 1.57, twrp 2.8.0.1, viperone 7.0.1, on TMOUS.
The text in Settings/About/Phone Identity is "HTC One_m8". Where is this text? It's not in build.prop..
Ideas?
Thanks in advance.
Click to expand...
Click to collapse
Check in System/Customize/ACC/default.xml
Doesn't seem to be there. Is this text aggregated from different files? It doesn't seem likely.
Reviewing the android (java) methods for identifying devices programatically I think it should be a text field in a property bag xml file somewhere. Its not in /default.prop /system/build.prop /system/default.prop or /data/local.prop
Is this a part of the ROM?
psipro_1989 said:
Doesn't seem to be there. Is this text aggregated from different files? It doesn't seem likely.
Reviewing the android (java) methods for identifying devices programatically I think it should be a text field in a property bag xml file somewhere. Its not in /default.prop /system/build.prop /system/default.prop or /data/local.prop
Is this a part of the ROM?
Click to expand...
Click to collapse
Sorry .. I'm not sure where it's located then
maybe @Wonders_Never_Cease or @nkk71 or @alray can give you the answer
clsA said:
Sorry .. I'm not sure where it's located then
maybe @Wonders_Never_Cease or @nkk71 or @alray can give you the answer
Click to expand...
Click to collapse
should be /system/build.prop afaik
Code:
...
ro.product.model=HTC One
...
obviously, if someone changed that (or by flashing some mod changed it), then it would say different.
This would be something the dev missed when porting things I would think. And usually it is in the build.prop.
psipro_1989 said:
I have an m7_ul, rooted and soff, currently running latest firmware from vomer, hboot 1.57, twrp 2.8.0.1, viperone 7.0.1, on TMOUS.
The text in Settings/About/Phone Identity/Model Number is "HTC One_m8". Where is this text? It's not in build.prop..
Ideas?
Thanks in advance.
Click to expand...
Click to collapse
Ok, I've reviewed build.prop and nairy an "m8" can be found. ro.product.model=HTC One. So... Hi ho, hi ho, it's dumpster diving I go!
Most irritating as the rest of the phone is [email protected] near perfect. I don't even know for certain when it happened. I went from stock to ARHD back in January and then went to Venom in early October. Had battery issues almost immediately; battery expiring at 30%... Went SOFF to get the most recent firmware (fixed the battery issue BTW) and of course that's when I noticed IT! And now my OCD won't let me ignore it.. AAAAaaAaaagggggghhhhhh!
Thanks for the vent opportunity..
psipro_1989 said:
Ok, I've reviewed build.prop and nairy an "m8" can be found. ro.product.model=HTC One. So... Hi ho, hi ho, it's dumpster diving I go!
Most irritating as the rest of the phone is [email protected] near perfect. I don't even know for certain when it happened. I went from stock to ARHD back in January and then went to Venom in early October. Had battery issues almost immediately; battery expiring at 30%... Went SOFF to get the most recent firmware (fixed the battery issue BTW) and of course that's when I noticed IT! And now my OCD won't let me ignore it.. AAAAaaAaaagggggghhhhhh!
Thanks for the vent opportunity..
Click to expand...
Click to collapse
Aha found it, it's cause you're on t-mo
it's located in /system/customize/CID/default.xml
and because of t-mo during installation it gets used from
ViperOne_7.0.1.zip\additions\carriers\tmous\system\customize\CID\default.xml
Code:
<module name="deviceData">
<function>
<set name="single">
<item name="device_name">[B]HTC One_M8[/B]</item>
</set>
</function>
</module>
whereas the standard one (non T-Mo) has:
Code:
<module name="deviceData">
<function>
<set name="single">
<item name="device_name">HTC One</item>
</set>
</function>
</module>
not sure if that's an oversight, or if it's on purpose/needed to support T-Mo Wifi calling... i'll ask later
Cool. I'll backup and see if a quick text edit will fix it. You're right. Viperone backported WiFi calling from m8 and this may be required to get it working; though it seems a silly requirement on the part of HTC or t-mobile devs if so...
Thank You
nkk71 said:
Aha found it, it's cause you're on t-mo
it's located in /system/customize/CID/default.xml
and because of t-mo during installation it gets used from
ViperOne_7.0.1.zip\additions\carriers\tmous\system\customize\CID\default.xml
Code:
<module name="deviceData">
<function>
<set name="single">
<item name="device_name">[B]HTC One_M8[/B]</item>
</set>
</function>
</module>
whereas the standard one (non T-Mo) has:
Code:
<module name="deviceData">
<function>
<set name="single">
<item name="device_name">HTC One</item>
</set>
</function>
</module>
not sure if that's an oversight, or if it's on purpose/needed to support T-Mo Wifi calling... i'll ask later
Click to expand...
Click to collapse
I was close I said /system/customize/ACC/default.xml
Curiouser and curiouser! Yup, sure enough the text was present in that file, but it must be propagated throughout the ROM. I changed it, flushed cache and dalvik and, though the file remains modified, the offending text remains in settings etc...
Do I need to edit that file in the ROM and ... Perhaps at this point I need to open a ticket with the venom team.
Thanks and hopefully someone else will see this if they're seeing the artifact.
FYI, when I changed the HTC One_m8 to HTC One the boot splash and shutdown splash reverted to default android... Must be used as a switch somewhere.
psipro_1989 said:
Curiouser and curiouser! Yup, sure enough the text was present in that file, but it must be propagated throughout the ROM. I changed it, flushed cache and dalvik and, though the file remains modified, the offending text remains in settings etc...
Do I need to edit that file in the ROM and ... Perhaps at this point I need to open a ticket with the venom team.
Thanks and hopefully someone else will see this if they're seeing the artifact.
Click to expand...
Click to collapse
i guess you could edit the file in the ROM.zip and dirty flash it.
if you want to make 100% sure, you could do a nandroid backup of your current setup, clean flash the rom, and see how it turns out.
I'll ask later if that is on purpose or an oversight....
Hello guys! After 2 days reading and trying all the methods, i will try to demonstrate the problem here.
My wife Moto X (5.1 Lollipop) start to appear the Camera Problem. Please, reset the camera. Well, after formatting, erasing, etc etc., i found a tutorial in internet to downgrade the Moto X to 4.4.4. Everything ok, procedures ok, deleting this lines from XML.
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="d2a411c57c3f37832702bda0c23484b4" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="2b664024c8a421245b814e3b7c4c5077" />
Moto X start ok, but the camera problem persist. Ok, give back to my wife and she start to use. After 1 day, the OTA 5.1 appear on status bar. And she Accept the OTA. Ok, my bad. I forgot to say to not update.
After the update, phone stuck up on boot failed. And the bootloader locked again.
I tried to unlock bootloader again, no way. Try to flash via RSD 4.2, 4.4, 5.1, no success.
When i try to use RSD, during GPT, error.
Im running out of options.
P.S.: sorry for my bad english, brazilian here.
Solved. Used this file: h t t p s : / / mega.nz/#!7ksR3aaR!Eou63oRpNqFKKUqOdGniAmImPEI22cIvMaX-JRQSkjQ and after "Repair Boot", smart comes alive.
Thanks admin.
I have twrp installed on this phone. My question? Is there a command prompt that i can type to make this happen? Just looking for some Assistance on this because holding down buttons during the boot process with twrp installed kills the process.
Thanks in advance.
Please have a look at
http://zukfans.eu/community/index.php?threads/57/
In the last reply I described how to do that.
schupfer said:
Please have a look at
http://zukfans.eu/community/index.php?threads/57/
In the last reply I described how to do that.
Click to expand...
Click to collapse
Thanks, I was able to figure it out, but now I have a new problem... When I try to update using the sdfuse "SD method" I get
ERROR: product is Z2 Pro? Why is it stating that? What is the fix? Thanks again
Maybe you have changed your model in build.prop, try to check it or maybe flash any other ROM via TWRP and after that try to use the sdfuse method. Let's know.
You have to remove check version lines in update package.
then twrp will install it
Sorry i dont have any in my phone, but it is in,
META-INF/com/google/android/updater-script
Sent from my ZUK Z2121 using Tapatalk
I've been given a friends phone that does the same, link above is dead so was a bit stuck..
He was told that it is impossible for him to get the error he was getting so I've got the phone now, I was getting the same error...
However, if I left the phone on the error, and then tried the QFIL way of doing thing, it worked, weird as QFIL on its own originally was giving an error as well..