Develop Bugs

Could someone please provide me with SX56 unlock code?

I am sure this bit of the question has been asked before so perhaps someone could cut and paste the procedure but I need to unlock this SX56 AT&T phone because I use T-Mobile AND travel abroad quite a lot.
The IMEI number is 350314000995655
(I couldn't find the SX56 model number or the correct ROM code or the Radio number in your pop-down menu so I entered it on the next line)

Unlock procedure
Sorry for last postingjavascript:emoticon('')
Embarassed: Siemens told me that I need an IMEI Number and that AT&T would provide me with an unlock code for this unit with that IMEI number (which obviously they won't)javascript:emoticon(':evil:')
Evil or Very Mad
Is the procedure (for my unit) to ask for an unlock code and then enter it or is it to download
* SD Card Reader
* 1x64Mb+ SD card
* XDATools
* XDA-Developers Special Edition ROM 1.2
1. Backup the existing bootloader and operating system using card reader
2. Extract the XDA-Developers Special Edition ROM 1.2 using Winzip
3. Write the NK.nbf-file (in the directory English) to your Device
4. Running the Programs -> Phone -> XDAUnlock file will remove the SIMlock...
5. after this time, the original ROM could be restored as desired.
And if I need to, can I do all this with Infra Red and sync or with the cradle which connects it to the computer? I cant find any reference to my ROM or Radio numbers in the pull down menu here and am a bit confused by this.javascript:emoticon(':?')
Confused

No, flashing the ROM will not unlock your device. Search for the wallaby unlocker, or check the wiki, as it is there, sticky and has been mentioned before.

Completing unlock process and flashing
I was directed to the flash upgrade program to unlock the device at the XDA-Wallaby Home Page and did flash but nowhere was I given the option to unlock: However the flashing process failed in an unusual and probably not important way: It completed successfully but I have lost the stylus and couldnt figure out how to stop the battery by pushing a fine screwdriver into the hole shown on the host computer screen. All that now shows on the screen is COMPLETED and a number of close-together vertical lines at the far right quarter inch of the screen.
Is there some trick to turning the battery off with some special tool or have I in fact completed the procedure and simply don't know that I have or what to do next? (get to a screen where I can run the XDAUnlock program which I transferred over to the SX56 before flashing the ROM?)
I wonder if I should or need to take the battery off if I Have lost that tool which does this by pushing into the hole on the lower quarter of the unit?

A bit of self-help going on here
So I DO appear to have flashed the ROM and the XDA ROM now appears on the screen although with no real backlight: The DO YOU WANT TO UNLOCK also appears but when YES is pressed, nothing happens. In fact one can see the unit taking the command but nothing further happens and the question just hangs on the screen.
Is this unlocking a command which takes a long time to execute? Or should I cancel out of it and carry on with bringing up the screen and can I execute it later on? Or have I done something major wrong and is there any way of rectifying? Sometimes if I press YES hard enough, the backlight appears for a half second (and the YES command pulsates once) and then goes off. But the question about unlocking still hangs on the screen.
Is this something to do with the program not being able to unlock an AT&T lock? Or has the screen lost sensitivity in some way and if so, (last resource here, improbably necessary) is there a source for Wallaby screens?

FOr the benefit of anyone trying this
NOTE:
After a night of the YES command taking and then not doing anything, I tried MOVING the over-screen by trying to drag it to another position
This didnt work. BUT tapping on the blue bar resulted in a message telling me that the unit was now unlocked. And the 7-8 black vertical lines to the right of the screen now have reduced to one, a quarter of an inch in
(Mind you, tapping on the ok button on THAT screen still mysteriously does nothing. This is a ROM which works in a VERY interesting, unusual and unexpected way!!)

new problem - report of invalid sim
now i am having another problem and am not sure i shoudn't start another thread
'
I did repalce the screen and the unit now starts up and reports invalid sim.
Is there any solution or should I re-flash the rom again and see if that works, hope for the best?

hello i bought a 6315 on ebay, i want to use it in latin america, gsm 1900, i need to unlcok it, room version is A.20.10 i wanted to download the special rom, but the link doesnt work and room folder on ftp is emty, i know is an old phone,can someone help me please unlock it? [email protected]

licensedtoquill said:
now i am having another problem and am not sure i shoudn't start another thread
'
I did repalce the screen and the unit now starts up and reports invalid sim.
Is there any solution or should I re-flash the rom again and see if that works, hope for the best?
Click to expand...
Click to collapse
I found the same happened to me first time and a soft reset did the trick. It may also be that the "Hard Reset" will be needed. I seem to recall that this was what I had to do with a couple of them. If your stylus is missing, a push pin and a bit of control will do. Just shove it in the micro hole at the bottom left of the device and hold it for a few seconds then let it go. If it does not restart on its own, follow that with a "soft reset" by pressing the point of the stylus (or a ball point pen) into the larger hole at the bottom left of the unit.
For the upgrade/unlock rom . . . the best one to which I have access is at:
http://www.landjtech.com/Secure/OutSetting/SX56/xdaunlock2.zip
Hope it helps

[n00b Guide] Your USA T-Mobile Defy: Rooting, Roms, and fixing 3G

Disclaimer: I make no warranties expressed or implied. This information is provided for research and educational purposes only. By reading this post, you agree not to hold me, my estate, my heirs, or my dog responsible for anything ever and waive all of your rights to legal action against said parties forever in perpetuity. Amen.
Note: this guide covers Android 2.1 (Eclair). Various builds of Android 2.2 (Froyo) are available in the forum. You should NOT use my guide if you are installing a build of Android 2.2 (Froyo). Currently I am running the Jboogie Froyo Rom, Orange DeBlur v4, which is great and (in my opinion) the best Froyo Rom out there for USA T-Mobile. Froyo is not much faster than Eclair in terms of benchmarks, but the apps are better, especially if you need the Android email app for connecting to an exchange server.
Now, on to the guide:
Goal: starting with a fresh-out-of-the-box Defy from T-Mobile USA, root the phone, install a non-US (or other) Rom, and recover your 3G capabilities.
Why: non-US Roms have much less bloatware from T-mo and Motorola, and allow you to install JIT/Deodex if you want
0) Oh noes! You've got to sign up for a Motoblur account just to use your phone! Create a throwaway email address at any of the webmail providers (gmail, yahoo etc.) and then go through the motions on the phone to set it up and get to the main home screen. Editorial note: wtf!!!
1) Get root access to your phone. Following Sorensiim's excellent guide, download the Z4Root app, which allows you to root (and unroot) your Defy. (thanks to Sorensiim for hosting!)
>> n00b notes:
First, go to Settings -> Applications and check "Unknown Sources" so you can run the Z4Root app.
Also go to Settings -> Applications -> Development and check "USB Debugging" so you can connect to your phone from your computer later.
Then open your phone's browser, navigate to this page, and download the app directly to your phone.
Install the app from your "Downloads" folder (accessible inside your Browser)
Run the Z4Root app on your phone, hit the "root" button and wait for it to work its magic.
This is what you will see if you run Z4Root after you reboot from rooting:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Install recovery so that you can make a backup of your operating system to your SD card before you do anything else - that way you can go back to the stock T-mobile OS if you need to.
Following Sorensiim's excellent guide, and many thanks to tenfar who put it together for us, just go here to download the Recovery App. (thanks to Sorensiim for hosting!)
>> n00b notes:
Just like before, visit this page on your phone's browser. Click the link to download the recover app, and once it's done, install it.
Allow the app to have root access, and check the box to always allow.
Once you are in the System Recovery program, click "Install Recovery System"; it will let you know when it's successfully installed (see image below):
3) Make a backup by opening the System Recovery app, and then press the "Recovery Boot" button. Back it up! Once again, details here, big thanks to tenfar!
>> n00b notes:
Once you have booted into recovery, you'll see the black/green screen shown below.
Use the volume buttons to navigate the menu and the power button to select an option.
Go to "Backup and Restore", and then "Backup".
If you need to restore later, just do the same thing except hit "Restore" and then select the one you want.
4) Flash a different ROM! Now here's where it get's a little more tricky. First, you'll want to follow Higgsy's Debranding Guide closely. I won't repeat his excellent guide, but here are my comments on the steps in the guide:
>> n00b notes:
Technically this step is optional - you can still weed out the bloatware and overclock while keeping your stock USA ROM. However, you will miss out on being able to install JIT/Deodex and having other features of non-USA roms, such as tethering.
Step 1: I used the consumer drivers package - Motorola 4.8.0 Driver with MotoConnect - since I am using 64 bit Windows 7. You can also use the developer drivers that Higgsy links to in his guide (available here).
Step 2: I used the JRDNEM_U3_2.34.1 firmware from central Europe, since you don't have to deal with Motoblur that way. You don't have to use this Rom of course, there are a bunch of different options, but I wanted to stick with a "real" Rom from Motorola as a starting point. Note that a firmware version is not the same as an Android version - i.e. v2.34.1 is NOT android 2.3, it is still anroid 2.1. Confusing, I know. Other Rom options include custom Roms that people put together and list in the XDA Developers forum. If you want to use one of those, you would follow their instructions for installing that particular custom Rom.
Step 3: In case the RSD Lite download link in the guide doesn't work, you can also get it from Megaupload the password for the site and the rar file is 'alabama'.
Step 7: Before booting the phone into the bootloader, you may want to clear out your data manually (aka "wipe your phone"). Go back into the System Recovery app, go to "Recovery Boot", and then when you're back on the black screen, select "Wipe DATA/Factory reset", "Wipe CACHE Partition" and then also go to "Advanced" and then select "Wipe Dalvik Cache". Then hold down the power button to turn off your phone. You won't be able to boot your phone after this, except by holding down the volume up + power on buttons together to get into the bootloader, so I would make 100% sure you have the drivers and RSD Lite installed and working!
Step 8: I would recommend waiting until it says "PASS" on the right side of the RSD Lite window before closing the program (this is after the "PLEASE START PHONE MANUALLY" phase is completed).
You should now have a working phone, with EDGE connectivity (little "E" in your status bar at the top) but no 3G or H icons. What, no 3G? We'll fix that next.
5) Re-root your phone and reinstall System Recovery following steps 1 and 2 above.
6) Install JIT/Deodexed: Optional step if you flashed either the 2.21 or 2.34 ROM. If you want to make your phone a bit faster, this is for you. Higgsy's guide is here if you want to do this!
>> n00b notes:
Update: on my third time flashing the phone, I was able to get JIT/Deodexed working fine. I think my failure the first time may have been due to my old SIM card, which I replaced because I was having problems reading the card and sending text messages (couldn't update the SMSC number).
Originally, I couldn't get the JIT/Deodexed package to work on my USA phone after installing the 2.34.1 firmware (too many 'untoward things happening' like Higgsy warned about), so I just skipped it the second time I flashed the 2.34.1 firmware.
The process of installing the packages is super easy, although you may want to make a backup before you start just in case. You can never have too many backups, because you can always transfer them to your computer if your SD card gets full. They are stored on your SD card under /goapkrev/backup/
The performance improvements are substantial - see graphs below.
Obviously you must get the package that matches the version of the ROM you installed. If you didn't flash a new ROM and still have the stock USA one, you are out of luck.
7) Make another backup! Now you want to backup your freshly-installed (and possibly JIT/Deodexed) Non-US Rom. Your first backup was the USA T-mobile Rom. You'll want to make this backup in case you eff something up in one of the next couple steps and want to go back to a fresh Non-US install and try-again.
Following the instructions in Step 3 above, load the System Recovery app, Recovery Reboot, and make a backup. Then reboot your phone!
8) Install ADB and/or Android SDK on your computer - there is a great guide on the Cyanogen Mod Wiki here. Just go slow, and follow the instructions. Once you can do "adb devices" and see your phone, you're good to proceed onward.
>> n00b notes:
To open a Command Prompt in Windows, go to "start" -> "run" and type "cmd" in the box or just go to "start" -> "all programs" -> "accessories" -> "command prompt").
Note that if you have 64-bit windows, you'll still need to install the regular 32-bit Java Development Kit (JDK), not the 64-bit version.
When you're editing your "path" environment variables in windows, note that you can't have spaces before or after semicolons. This is what my full path looks like (and iTunes works now - it didn't when I accidentally left a space after QTSystem\;
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\;[B]%SystemRoot%;C:\Program Files (x86)\Android\android-sdk-windows\platform-tools;C:\Program Files (x86)\Android\android-sdk-windows\tools[/B]
9) Fix 3G
*** NOTE: This step only applies to USA phones. If you're not in the USA, your 3G probably works fine.
Download HandlerExploit's 3G fix from the 2.21 UK ROM or my 3G fix from the 6.19 US ROM. Thanks to HandlerExploit for figuring this out for us.
>> n00b notes:
There's not much difference between the two 3G fixes, except that each one will display different info in the "About Phone" section (either v2.21 or v6.19). For example, if you use my fix, "About Phone" will tell you that you have "Build number: JORDN_U3_6.19.0" installed - this is a side affect of the patch. For HandlerExploit's fix, "About Phone" will report v.2.21 GB
You may want to write down what Rom you actually installed if you think you might forget (for example, my phone actually has "JRDNEM_U3_2.34.1" even though it reports 6.19.0 in "About Phone")
If you downloaded HandlerExploit's 3gFix, you can choose to follow his instructions or the ones below, which are basically the same as what is in his, except you enter the commands line-by-line instead of running them through a script. I prefer line by line because I like to know what I'm doing. Both methods should work fine.
If you are unfamiliar with basic command prompt commands (cd dir ls etc.) please see my reply later in this thread
Once you download the zip file, extract it somewhere, like your desktop.
Alright, time to get some ADB skills. Plug your phone in via USB and open a command prompt. First we connect to the phone by typing this, each command followed by the "Enter" key:
Code:
adb shell
Then you want to run some commands as a super user so type:
Code:
su
Quick! Look at your phone, and tell it to always allow superuser access. You only have to do this once.
You should have a "#" command prompt now (instead of a "$" like before) indicating that you are working as a superuser (#=superuser). Now some more commands to enter. (n00b tip: you can copy and paste each line into the command prompt by copying the line from this guide and right clicking "paste" on the command prompt window)
Code:
mount -o remount,rw -t ext3 /dev/block/mmsblk1p21 /system
chmod 0777 /system/etc/motorola/bp_nvm_default
chmod 0777 /system/etc/motorola
chmod 0777 /system/etc
chmod 0777 /system/app
chmod 0777 /system/lib
chmod 0777 /system/lib/modules
chmod 0777 /system
exit
exit
So now we have set CHMOD Permissions for some folders on your phone, and then quit the adb shell. Now we've got to push some files to the phone:
Navigate to the folder where you extracted the files from the 3g fix you downloaded above, for example, type:
Code:
cd c:\users\administrator\desktop\3gfix\
then enter:
Code:
adb push system /system
This will copy all the files in the subfolder "system" to your phone's "/system" folder, overwriting them (which is why we made a backup earlier). Then enter:
Code:
adb reboot
to reboot your phone. You should have 3G connectivity now - note that it may take up to a minute or so for it to appear the first time, and you may not see the icon at all if you have WiFi enabled (so disable it in your settings to test it out).
If it still doesn't work, try going to "Settings" -> "Wireless & Networks" -> "Mobile Networks" -> "Access Point Names" -> (settings button of four squares) -> "Reset to default". Also make sure the APN name is highlighted with a green dot. You may also have to go to "Settings" -> "Wireless & Networks" -> "Mobile Networks" -> "Operator Selection" -> "Select Automatically"
This is what the 3G icon looks like of course:
10) The phone is yours. You can:
Install some apps: Titanium Backup & Launcher Pro for example.
Weed out the bloatware, overclock, and scale: see Sorensiim's awesome guide here. I highly recommend doing this, just bumping up to 1000mhz overclock makes the phone's performance much more snappy. If you overclock, you should definitely use Sorensiim's scaling method and his scaling files -- it makes a very noticeable improvement in battery life.
Benchmark your phone: with Quadrant Standard Edition, available in the app market
Play Angry Birds all day: :-D
Here is my phone benchmarked, with no overclocking, no bloatware removal, no JIT/Deodex packages, just the stock JRDNEM_U3_2.34.1 firmware (note that the phone with the US Rom straight out of the box benchmarks a little higher at 987. I'm not sure why this is.):
Here it is after overclocking to 1000mhz and my own customized bloat removal (not as much as most people, i use some of the default apps), also still no JIT/Deodex. Obviously you can get it to go faster if you want to overclock more, install JIT/Deodex, and remove more bloat:
Edit: These are the apps I disabled for the second benchmark (renaming them using Sorensiim's guide )
AdService.apk
ArcPhotoworkshop.apk
ArcVideoEditorLite.apk
esmusica_2_0_0012_embed_Signed_2010-04-13_11-05-17.apk
FBAndroid-1.3.2.apk
Fota.apk
hiphopofficial_2_0_0012_embed_Signed_2010-04-13_11-08-31.apk
Kindle-1.0.2-OEM-SingleSign.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
MagicSmokeWallpapers.apk
MySpace.apk
Protips.apk
Quickoffice_BasicViewer_2.0.52.apk
revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.apk
truecountry_2_0_0012_embed_Signed_2010-04-13_11-06-12.apk
WeatherWidget.apk
Here is what I got to after JIT/Deodexed was installed on 2.34 - same apps removed, same overclock at 1000mhz. Removing VisualizationWallpapers.apk and YouTube.apk got me to 1308.

Wow, great guide! I might try this later.. I do have a question though, if we've already set up our phones on a stock rom, can Titanum Backup or the recovery backup our apps and settings and then restore them to our new deblured ROM?
Sent from my MB525 using XDA App

Passa91 said:
Wow, great guide! I might try this later.. I do have a question though, if we've already set up our phones on a stock rom, can Titanum Backup or the recovery backup our apps and settings and then restore them to our new deblured ROM?
Click to expand...
Click to collapse
Yes, you would do that with Titanium Backup. System Recovery is for making entire images. It's easier to replace things piece-by-piece with Titanium Backup.

Thanks for this...along with handler's tips on SA I got it working.

Although I´m not an US user (hence got working 3G) I´m still on the 2.34.1 ROM, and I still use som of the default apps.
Just wondering though: which ones did you remove? I´m not going to get into ADB, but I was thinking of removing some of ´em with TB.
Slightly OT - can you safely remove Swype? There´s no swedish language support for that, and I´ve gotten used to TouchPal anyway...

heglen said:
Although I´m not an US user (hence got working 3G) I´m still on the 2.34.1 ROM, and I still use som of the default apps.
Just wondering though: which ones did you remove? I´m not going to get into ADB, but I was thinking of removing some of ´em with TB.
Slightly OT - can you safely remove Swype? There´s no swedish language support for that, and I´ve gotten used to TouchPal anyway...
Click to expand...
Click to collapse
Sure you can remove Swype, theres still the standard android keyboard installed as well. Check out scandinavian keyboard from the market too

I had a big problem in step #8, installing ADB. No matter what I tried, the command "adb devices" would not work. But I was able to solve it by following this:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
You have to download the ADB files from
http://www.megaupload.com/?d=RTEY0Q97
and put them into your
Android\android-sdk-windows\tools
directory. Word is, they were taken out by Google for whatever reason in the R08 version, and must be restored in order for ADB to work.
After I extracted the files into the Tools folder, and used the 'adb devices' command, it worked like a charm!

Quick noob question.
If I install a custom ROM on my Defy following this guide and then restore the T-mo US 3G connectivity - will I be able to use the "Web2 go" unlimited plan without being detected and blocked by T-mo? Currently as I have the stock firmware/ROM it does not let me connect to neither 3G nor Edge. I've tried my SIM with Nokia N900 and 3G works fine, since the T-mo network doesn't recognize it as a smart phone. Please let me know if de-bluring/debranding my Defy will solve this problem for me.
Thanks in advance.

nvvass said:
If I install a custom ROM on my Defy following this guide and then restore the T-mo US 3G connectivity - will I be able to use the "Web2 go" unlimited plan without being detected and blocked by T-mo?
Click to expand...
Click to collapse
Why did you buy an android smartphone if you don't have a plan for it? Can't help ya.

rob-t said:
Why did you buy an android smartphone if you don't have a plan for it? Can't help ya.
Click to expand...
Click to collapse
I do have a plan. Many friends' Nexuses work fine with the same plan. I know a guy with a Nokia N900 and it works in 3G even with his grandfathered T-zone for $4.99. Why pay more? You didn't answer my question though - can you give a specific answer? As in "will work" or "won't work".
Thanks.

nvvass said:
You didn't answer my question though - can you give a specific answer? As in "will work" or "won't work".
Click to expand...
Click to collapse
Seeing as how I never had even heard of web2go before your post, I really have no idea. I'm not entirely sure I know what T-zone and web2go even /are/.
If you follow the instructions above and you still can't use your web2go thing, you can always roll back to your first backup and then use Z4root to unroot your phone, effectively returning it to 'stock' condition.

Wifi Calling?
Great tutorial for us noobs! Thanks! How does this affect wifi calling?

rob-t said:
Seeing as how I never had even heard of web2go before your post, I really have no idea. I'm not entirely sure I know what T-zone and web2go even /are/.
If you follow the instructions above and you still can't use your web2go thing, you can always roll back to your first backup and then use Z4root to unroot your phone, effectively returning it to 'stock' condition.
Click to expand...
Click to collapse
I'm sorry I assumed you're familiar with T-mo US, but thanks for responding anyway. Basically, web2go is an unlimited data plan for $10, that T-mo used to provide for "dumb" phones. T-zones was it's previous version (before 3G times) priced at $4.99 and was offered for all phones other than BBs. I remember getting a Dash (T-mo branded HTC Excalibur), witch was one of the first phones T-mo started to call "smart", and was able to get full Inet access with my T-zones just by tweaking some APN settings on the phone. In fact I (and many others) was able to get that without any data plan for awhile, before T-mo caught up with it and started blocking it. Of course it was too slow for browsing (EDGE/GPRS), but you could get your e-mails pretty easily and search stuff when in a pinch. Speaking of that - anybody remember when texting was free? Anywho, at some point in time T-mo started blocking smart phones from accessing data services on a "dumb" data plan - apparently by adding a piece of code to the FW of all T-mo branded phones, that allows their network to recognize the phone as "smart" and then block access if a "dumb" plan is used. Now, if you use a non-T-mo branded phone (even the same model that has a T-mo version) the network is not able to figure the type of phone and lets you access regardless of data plan. So, I hope this long explanation helps you understand where I was coming from with my original question. Obviously, when you flash the Defy with a non-T-mo ROM you get rid of the piece of code that makes the phone identifiable, but then when you copy part of the original ROM to restore 3G functionality, does that part contain the ID code also, I was wondering. At any rate, if you're not familiar/don't use T-mo you wouldn't know, I understand, I guess I'll have to go through the steps and figure it out for myself. Thanks anyway.

bcrawf68 said:
Great tutorial for us noobs! Thanks! How does this affect wifi calling?
Click to expand...
Click to collapse
WiFi calling seems to work fine for me.
nvvass said:
Now, if you use a non-T-mo branded phone (even the same model that has a T-mo version) the network is not able to figure the type of phone and lets you access regardless of data plan.
Click to expand...
Click to collapse
Ah OK thanks for the explanation. I currently use T-mobile but I don't really know much about their offerings. I would try the 2.21 or 2.34 firmware and then apply the UK 3G fix made by HandlerExploit, instead of the USA 3G fix I made from the US firmware.
Only one way to really find out though...

Excellent!
Steps 1-8 of your guide are also very helpful for non-US Defy users!
3G fixing, however, is probably not required on European Defys and I would not recommend following steps 9 et seq for those devices. Please correct me if I'm wrong here.

cloogshizer said:
3G fixing, however, is probably not required on European Defys and I would not recommend following steps 9 et seq for those devices. Please correct me if I'm wrong here.
Click to expand...
Click to collapse
Thanks, yes, I updated the guide accordingly. 3G fixing should only be necessary in the USA.

nvvass said:
I'm sorry I assumed you're familiar with T-mo US, but thanks for responding anyway. Basically, web2go is an unlimited data plan for $10, that T-mo used to provide for "dumb" phones. T-zones was it's previous version (before 3G times) priced at $4.99 and was offered for all phones other than BBs. I remember getting a Dash (T-mo branded HTC Excalibur), witch was one of the first phones T-mo started to call "smart", and was able to get full Inet access with my T-zones just by tweaking some APN settings on the phone. In fact I (and many others) was able to get that without any data plan for awhile, before T-mo caught up with it and started blocking it. Of course it was too slow for browsing (EDGE/GPRS), but you could get your e-mails pretty easily and search stuff when in a pinch. Speaking of that - anybody remember when texting was free? Anywho, at some point in time T-mo started blocking smart phones from accessing data services on a "dumb" data plan - apparently by adding a piece of code to the FW of all T-mo branded phones, that allows their network to recognize the phone as "smart" and then block access if a "dumb" plan is used. Now, if you use a non-T-mo branded phone (even the same model that has a T-mo version) the network is not able to figure the type of phone and lets you access regardless of data plan. So, I hope this long explanation helps you understand where I was coming from with my original question. Obviously, when you flash the Defy with a non-T-mo ROM you get rid of the piece of code that makes the phone identifiable, but then when you copy part of the original ROM to restore 3G functionality, does that part contain the ID code also, I was wondering. At any rate, if you're not familiar/don't use T-mo you wouldn't know, I understand, I guess I'll have to go through the steps and figure it out for myself. Thanks anyway.
Click to expand...
Click to collapse
cloogshizer said:
Steps 1-8 of your guide are also very helpful for non-US Defy users!
3G fixing, however, is probably not required on European Defys and I would not recommend following steps 9 et seq for those devices. Please correct me if I'm wrong here.
Click to expand...
Click to collapse
first of all.. thank's for the great tutorial man..!!
second of all, I got this T-mobile defy from my uncle and I used it in Indonesia.. It's true what nvvass said, that the T-mo firmware constantly tries to connect with the "smart phone" data plan.. which caused me to unable to connect to my local provider data connection.. after I flashed the defy with the central-europe de-blur firmware, Voila..!! I got 3G connection directly..!! without any settings at all..
hope this helps for anyone using US T-mobile defy outsite of US.. cheers mate..

if i have no reception (the signal bars have a red circle with a line through it on top) will this kind of 3g fix but relevant to australia fix the issue?

Jt612 said:
if i have no reception (the signal bars have a red circle with a line through it on top) will this kind of 3g fix but relevant to australia fix the issue?
Click to expand...
Click to collapse
where did you get the phone from? if it from US and still locked with T-mobile, than it would refuse to connect with local provider.. you need unlock code..

i bought it in australia its an australian phone... works fine when i restore my backup of australian software but i would like to use the 2.34.1

[SEMI-FIX/BYPASS] Unlocking Bootloader when HTCdev site is crashing/semi-down

UPDATE: I was on XDA Portal! http://www.xda-developers.com/android/bypass-htc-server-problems-when-unlocking-bootloader/
Hey guys,
So basically I spent two hours checking trying to unlock my HTC One X's bootloader a few days back.
I mean seriously? Two hours to unlock my bootloader? That's utter bull. HTCdev has the worst bootloader unlock servers ever, mostly because server keeps overloading.
I found several fixes if you have this error when you open the website on Google Chrome, but these aren't really fixes that fix the server, these are temporary bypasses if you want to get your bootloader unlocked immediately.
You would want to follow this if you constantly get these errors by using Google Chrome:
1. "The connection to htcdev.com was interrupted."
2. "This webpage is not available"
3. After logging in to the website, you select "All Other Supported Models" and press Begin Unlock, no popup window comes up asking you to verify ToS and verifying that you will void warranty.
4. *without logging into HTCdev* You click Begin Unlock and you get a popup to login, after login you get an error "This webpage is not available"
To bypass most of these problems, follow these steps before proceeding:
1. Login to the website and make sure you get to the page where you can see "Welcome XXXXXXXXX Logout Account" on top of the window.
2. *OPTIONAL TO TEST* Try selecting All Other Supported Models from the dropdown box and click Begin Bootloader Unlock, if this fails and does not show a popup after 2-3 minutes, refresh and do the same except click the button two more times. If this fails, proceed onwards to step 3.
3. Make sure you have Fastboot, HTC Sync and Java installed on your computer.
4. Put your phone in Fastboot mode, do this command in the fastboot cmd to get your code: fastboot oem get_identifier_token
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Right Click > Mark > highlight the block of text > Right click to copy to the code
5. Make sure you are logged in, then proceed to this site: http://htcdev.com/bootloader/unlock-instructions, when navigating through the pages, you get the above Chrome errors, just do one or two refreshes until you see something on your screen and not a Google Chrome error. Navigate to Step 10, http://htcdev.com/bootloader/unlock-instructions/page-3
6. Paste in the code and immediately click Submit, if you get a Google Chrome error, go back and Submit again. Repeat until you see the HTC success screen when you unlock your bootloader, telling you to check your email. If you get an error about your code, recopy your code and paste into the box.
7. Check your email, download the Unlock.bin into your Fastboot folder and open your Fastboot cmd prompt, run this command to unlock your phone: fastboot flash unlocktoken Unlock_code.bin
8. Follow on-screen instructions to unlock your bootloader.
9. Flash CWM recovery by Koush: http://forum.xda-developers.com/showthread.php?t=1594819
Use this command to flash the recovery onto your phone: fastboot flash recovery nameofrecovery.img
For example: fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img.img
10. Smile, you unlocked your phone's bootloader

Huh~ the problems you faced simply cause by the high serverload on HTCDev. Perhaps caused by those who are waiting for Desire and Rhyme RUUs..
"HTCdev has the worst bootloader unlock servers ever." -- can't give any comments on this because there no others available.
Need to clarify HTC is the first to offer official bootloader unlock though not s-off. Currently already made it to available for all their android devices, hardworks. Who you are comparing it with? Motorola's single device unlock site?
and why you need java for bootloader unlocking process.
the unlocked process is already done on step 8 actually.

HebeGuess said:
Huh~ the problems you faced simply cause by the high serverload on HTCDev. Perhaps caused by those who are waiting for Desire and Rhyme RUUs..
"HTCdev has the worst bootloader unlock servers ever." -- can't give any comments on this because there no others available.
Need to clarify HTC is the first to offer official bootloader unlock though not s-off. Currently already made it to available for all their android devices, hardworks. Who you are comparing it with? Motorola's single device unlock site?
and why you need java for bootloader unlocking process.
the unlocked process is already done on step 8 actually.
Click to expand...
Click to collapse
Please read the title. Obviously it is high server load or just crappy server upload speeds. I have waited weeks and weeks for it to load fast, if you try to go on HTCdev again right now, it is extremely slow and would constantly hang.
Think about it logically, HTC is such a big company, and plus we shouldn't have extremely high network ping since the HQ is just an hour flight away from where I live. It's not hardwork if people want to unlock their bootloaders and they purposely lock it down, they're just pissing people off, intentionally wanting to record down who voided their warranty. Look at all the Samsung users, their phones come with a pre-unlocked bootloader and they're doing much better than HTC.
They are in fact the first to do this kind of unlock, no other company is doing it the same way, which means it is the worst way to do it.
If you can be bothered, please take a look at HTCdev's twitter page. There are loads of people complaining about their bootloader unlock page, and HTCdev claiming that they fixed it, but its an ongoing problem and I have never ever had such a hassle when trying to root your phone.
Anyways this is a technique I would follow if you have the problems stated above, just wanting to help people, not start flames.

Actually i was on the site regulary basis recents day for Desire S's RUU..
But bid samsung shipped with pre-unlocked bootloader? No, please dont includes nexus flagship devices and the funny verizon GS3 dev edition that wanting people to paid more..
And I have no intents to pouring flames on this..

We're on the International variant of the HTC One X forum here, and the major population here are from everywhere around the world, not just US.
Samsung releases pre-unlocked versions of their International devices, I never said anything about US carrier released ones.
Nexus flagship devices are controlled by Google, if Google says lock the bootloader, they listen, but if its a Samsung Galaxy S series device, Google can't force them to lock the Galaxy line's bootloader.

oh thank god!!! finally! =) Thank you thank you thank you!!! =) I'd been wrestling with their servers off and on for about FOUR hours lol. This totally worked

Hi,
A better approach will be this way:
1. with your "My Device Identifier Token" ready (have it in a notepad)
2. use google chrome and launch 5 tabs
3. navigate all to http://www.htcdev.com/bootloader/unlock-instructions/page-3
4. login to each of the 5 tabs
5.scroll all the way down to the part to input your token for all 5 tabs
6. copy your token from the notepad stated earlier.
7. paste and submit into all 5 tabs by using the short cut Ctrl+Tab
8. At least one will be submitted and you will received an email even though all the page shows you login error.

problem with bootloader
after flashing unloctoken from cmd by fastboot flash unlocktoken Unlock_code.bin
i m not able to get any flash screen on my htc evo 3d gsm i m on
hboot 1.48.0005
build no 1.14.0.0 cl95535-keys
i m on ginger bread not able to update to ics.
default ics update is not also coming on my mobile
i m tired of doing it i hv done whole process like 100 times but splash screen dsnt appears on my mobile
i htc driver+java+htcsync+adt-bundle-windows
is their any other method to unlock my htc evo 3d gsm then htcdev pls help me i m trying this from last 1 year not no sucess yet

haroujf said:
Hi,
A better approach will be this way:
1. with your "My Device Identifier Token" ready (have it in a notepad)
2. use google chrome and launch 5 tabs
3. navigate all to http://www.htcdev.com/bootloader/unlock-instructions/page-3
4. login to each of the 5 tabs
5.scroll all the way down to the part to input your token for all 5 tabs
6. copy your token from the notepad stated earlier.
7. paste and submit into all 5 tabs by using the short cut Ctrl+Tab
8. At least one will be submitted and you will received an email even though all the page shows you login error.
Click to expand...
Click to collapse
+1
The guide shown here (OP) is useless, this is what everybody does anyway.
You've just made a massive guide, basically saying just keep refreshing and you'll pass through soon enough.
Using the method you described, it could still take hours...

Thank you so much nicolaschum! Your introduction works perfect and I've just unclocked my father's HTC VT328t. It is contract model of a carrier China Mobile, with lot of useless carrier apps and worst part is all google apps and frameworks are removed.
I've been stuck in HTC legal term page for near two hours and unable to get into Unlock Instructions page (step 1 - 4) and was about to give it up. Fortunately I found this thread and with your instruction I've bypassed them and got final Token submitted successful message in only 4 tries within 5 minutes. Now I can get google apps installed on his mobile :laugh:

Thanks!
Thanks for this
Sent from my HTC One X using xda app-developers app

nicholaschum said:
Hey guys,
So basically I spent two hours checking trying to unlock my HTC One X's bootloader a few days back.
I mean seriously? Two hours to unlock my bootloader? That's utter bull****. HTCdev has the worst bootloader unlock servers ever, mostly because server keeps overloading.
I found several fixes if you have this error when you open the website on Google Chrome, but these aren't really fixes that fix the server, these are temporary bypasses if you want to get your bootloader unlocked immediately.
You would want to follow this if you constantly get these errors by using Google Chrome:
1. "The connection to htcdev.com was interrupted."
2. "This webpage is not available"
3. After logging in to the website, you select "All Other Supported Models" and press Begin Unlock, no popup window comes up asking you to verify ToS and verifying that you will void warranty.
4. *without logging into HTCdev* You click Begin Unlock and you get a popup to login, after login you get an error "This webpage is not available"
To bypass most of these problems, follow these steps before proceeding:
1. Login to the website and make sure you get to the page where you can see "Welcome XXXXXXXXX Logout Account" on top of the window.
2. *OPTIONAL TO TEST* Try selecting All Other Supported Models from the dropdown box and click Begin Bootloader Unlock, if this fails and does not show a popup after 2-3 minutes, refresh and do the same except click the button two more times. If this fails, proceed onwards to step 3.
3. Make sure you have Fastboot, HTC Sync and Java installed on your computer.
4. Put your phone in Fastboot mode, do this command in the fastboot cmd to get your code: fastboot oem get_identifier_token
Right Click > Mark > highlight the block of text > Right click to copy to the code
5. Make sure you are logged in, then proceed to this site: http://htcdev.com/bootloader/unlock-instructions, when navigating through the pages, you get the above Chrome errors, just do one or two refreshes until you see something on your screen and not a Google Chrome error. Navigate to Step 10, http://htcdev.com/bootloader/unlock-instructions/page-3
6. Paste in the code and immediately click Submit, if you get a Google Chrome error, go back and Submit again. Repeat until you see the HTC success screen when you unlock your bootloader, telling you to check your email. If you get an error about your code, recopy your code and paste into the box.
7. Check your email, download the Unlock.bin into your Fastboot folder and open your Fastboot cmd prompt, run this command to unlock your phone: fastboot flash unlocktoken Unlock_code.bin
8. Follow on-screen instructions to unlock your bootloader.
9. Flash CWM recovery by Koush: http://forum.xda-developers.com/showthread.php?t=1594819
Use this command to flash the recovery onto your phone: fastboot flash recovery nameofrecovery.img
For example: fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img.img
10. Smile, you unlocked your phone's bootloader
Click to expand...
Click to collapse
Helped me unlock an HTC Eris, thank you. Was annoyed with the long wait and sluggish website.

Thanks for the help, but I'm stuck at submitting token..

Now its getting bad..i dont know why htc seem doesnt care about this.

Really really bad
http://www.isitdownrightnow.com/htcdev.com.html

Re: [FIX] Unlocking Bootloader when HTCdev site is crashing/semi-down [SERVER OVERLOA
Everyone, I had to use a browser other than Chrome. Safari had much more success, even better than IE. Still took a couple of reloads o finish.
Sent from my SGH-T959 using xda app-developers app

2 day trying.....htc sucks

3 day trying...same..sometimes its past till last but at the end ..error 173...

Wilks3y said:
+1
The guide shown here (OP) is useless, this is what everybody does anyway.
You've just made a massive guide, basically saying just keep refreshing and you'll pass through soon enough.
Using the method you described, it could still take hours...
Click to expand...
Click to collapse
Yes if everyone does this then why would anyone have any errors? I have done this on more than 15 HTC One X devices, so I'm pretty sure my guide is useful for me at least. I could even say it's failproof if done correctly.
I even tried his guide you +1'd, but all my tabs did not load, however that is just a smaller condensed method of what I did, that method would still work and is identical to the process of my guide, as it still loads multiple pages anyways, but you can't say a Samsung Galaxy S II is useless compared to the Samsung Galaxy S III because the S II has outdated or a different architecture compared to the S III. Without an S II invented you won't get an S III, so without a guide like this, there would still be people running around yelling how HTC servers should be fixed and never actually getting a fix, and there would not be a compressed version of this guide.

day 3 for me..ihve had multiple tabs open, no dice

Unlock LTE Bands

Hi,
I ordered the HTC 10 off eBay thinking that all models were the same. Turns out I have the M10h model which does not support North American LTE bands. I was wondering if the bands can be unlocked (if the HW supports it). I know it was done for the M9 and some Galaxy devices. Any insight would be great!

I would probably start by trying to flash the USA radio. if you can get the actual radio that is.
Sent from my HTC 10 using XDA-Developers mobile app

Well I'm sure we'll have the radios up soon. Do you think the new encryption will interfere getting the radios from RUUs? If not, then flashing them shouldn't be a problem.

Cakeor314 said:
Hi,
I ordered the HTC 10 off eBay thinking that all models were the same. Turns out I have the M10h model which does not support North American LTE bands. I was wondering if the bands can be unlocked (if the HW supports it). I know it was done for the M9 and some Galaxy devices. Any insight would be great!
Click to expand...
Click to collapse
Well, I have had some fun playing with LTE band changing on my M8 and M9. I went to www dot cdmatool dot com.
Using their DFS Tool, part of the DFS Studio of tools. It's for Qualcomm processors like our HTC's have. Some HTC products use MediaTek processors and DFS won't work for them. If your HTC 10 will accept the ##3424# command to enter diag mode, I would bet a quarter
that you can change your LTE bands with DFS Tool. Be sure you can also adjust the phone's APN to match the carrier's bands you want to work with. Without correct APN, even with correct bands, you will not get connections.

Does this actually work though?

Tried the following adb shell commands to put the phone in Diag mode but didn't work:
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
Was trying the steps from the M9 forum:
http://forum.xda-developers.com/one-m9/general/how-to-change-network-bands-gsm-devices-t3135401

sbong said:
Tried the following adb shell commands to put the phone in Diag mode but didn't work:
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
Was trying the steps from the M9 forum:
http://forum.xda-developers.com/one-m9/general/how-to-change-network-bands-gsm-devices-t3135401
Click to expand...
Click to collapse
Did you get something about this finally? Sorry of being a lazy douchebag, but I don't want to root my phone for now, unless someone can confirm this. I also have the problem with LTE currently with some bands (specially 1700/2100 due non-US phone)

sbong said:
Tried the following adb shell commands to put the phone in Diag mode but didn't work:
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
Was trying the steps from the M9 forum:
http://forum.xda-developers.com/one-m9/general/how-to-change-network-bands-gsm-devices-t3135401
Click to expand...
Click to collapse
dude, it is very sad that this method does not work on htc 10. i was trying this several days ago. neither this command nor ##3424# works on htc 10. it seems like htc 10 blocked this diagnostic mode I AM waiting for someone to find a new hacking method!!

jackzhouyongxiao said:
dude, it is very sad that this method does not work on htc 10. i was trying this several days ago. neither this command nor ##3424# works on htc 10. it seems like htc 10 blocked this diagnostic mode I AM waiting for someone to find a new hacking method!!
Click to expand...
Click to collapse
"*#*#3424#*#*"

jackzhouyongxiao said:
dude, it is very sad that this method does not work on htc 10. i was trying this several days ago. neither this command nor ##3424# works on htc 10. it seems like htc 10 blocked this diagnostic mode I AM waiting for someone to find a new hacking method!!
Click to expand...
Click to collapse
Hooray!, something changed with Verizon's last OTA. I'm on US unlocked version, S-0ff, unlocked, converted to Verizon.
##3424# didn't work on original OTA, but the 1.19.605.22 update now allows ##3424# to get into diagnostic mode and CHANGE YOUR BANDS with DFS Tool.
Now on 2-4-13 like I want to be.

michaelbsheldon said:
Hooray!, something changed with Verizon's last OTA. I'm on US unlocked version, S-0ff, unlocked, converted to Verizon.
##3424# didn't work on original OTA, but the 1.19.605.22 update now allows ##3424# to get into diagnostic mode and CHANGE YOUR BANDS with DFS Tool.
Now on 2-4-13 like I want to be.
Click to expand...
Click to collapse
Were you using Verizon on CDMA while on US Unlocked before converting? (I assume that´s the case when you converted to Verizon).

No, it's the US Unlocked version that needs to be converted with Verizon's current OTA before it will connect.

michaelbsheldon said:
No, it's the US Unlocked version that needs to be converted with Verizon's current OTA before it will connect.
Click to expand...
Click to collapse
Thanks, that´s what I imagined.
I found a way of activating DIAG mode on HTC 10 but every time and method I tried (I`ll detail it on the next post) to change the LTE bands, the changes were lost after rebooting the phone. More on that in a minute.

kainanmaki said:
Thanks, that´s what I imagined.
I found a way of activating DIAG mode on HTC 10 but every time and method I tried (I`ll detail it on the next post) to change the LTE bands, the changes were lost after rebooting the phone. More on that in a minute.
Click to expand...
Click to collapse
What Method?? Please help me with the tutorial
Enviado desde mi iPhone utilizando Tapatalk

So...like I said before, I found a way of activating DIAG mode.
I had the very same problem of ##4232# not getting the job done (I suppose the code only works on CDMA).
We knew that using ADB Shell, opening the DIAG was possible on the M8 and M9.
But those commands didn't work on the 10, and I didn't find any clue on the F_DIAG folder (it changed on the 10).
Googling outside XDA, found that inputting "setprop sys.usb.config diag,adb" should open the DIAG on Android. But it didn't work too. But, also found that checking the /init.htc.usb.rc file on the phone could help devising the correct command.
Opening the file I discovered that these commands are like presets for choosing mtp, ums, and the ones you do find every time you plug the usb and the 10 ask you which method do you prefer for (just charging, transfer files, etc).
After some hit and miss, I found that opening ADB Shell with su and the following line did the job:
"setprop sys.usb.config adb,diag,acm"
That activated Diag Mode, I didn't even need to install the drivers (W10), looking at device manager I found the COM devices needed to perform band changes.
I have yet to get results, I'll detail more on the next post.

Interested to see if this goes anywhere.

mnguyen127 said:
Interested to see if this goes anywhere.
Click to expand...
Click to collapse
Before starting, let me note that a custom kernel is needed for this procedure.
On the guide I'm following (link a few lines below), explains that stock kernels include some lines from Qualcomm to avoid tampering, that's technically the reason why the modifications are lost on every reboot.
Link to the guide:
http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
The guide doesn't help us too much with the DIAG stuff, we are on our own there.
The most complicated part of the guide ask us to "Change USB from AP to CP. And USB settings from MTP + ADB to RNDIS + DM + Modem mode"
I think I almost clinched the RNDIS+DM+Modem part. It is related to the adb shell line I commented on other posts. I'm no coder at all (never wrote a single line) so if you see something ridiculous in my comments you are free to freak out and single it.
To achieve RNDIS+DM+Modem we have to enter on ADB:
Code:
adb shell
su
setprop sys.usb.config rndis,diag,modem
I have yet to find the AP to CP part for USB (Application Processor to Cellular Processor).
Any ideas are welcome.

kainanmaki said:
Thanks, that´s what I imagined.
I found a way of activating DIAG mode on HTC 10 but every time and method I tried (I`ll detail it on the next post) to change the LTE bands, the changes were lost after rebooting the phone. More on that in a minute.
Click to expand...
Click to collapse
I think someone in the M9 Thread mentioned that changes on GSM (not CDMA) Phones are lost on Boot if you use DSF Tools, if you use the Qualcomm tool it will stay.
P.S
The phone can only be Connected to one LTE Band at a time.
The App Signal Check Lite Shows the current Band.
Is there any way to show all Frequencies currently available? There might also be a 2100mhz Band close by or not?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
P.S anyone tried to change stuff in *#*#4636#*#* Mode?

Haldi4803 said:
I think someone in the M9 Thread mentioned that changes on GSM (not CDMA) Phones are lost on Boot if you use DSF Tools, if you use the Qualcomm tool it will stay.
Click to expand...
Click to collapse
So far I tried 4 methods:
1) QXDM Method - Doesn't resist reboot.
2) DFS Tools - Same as 1)
3) NV Items Reader - Same as 1)
4) QSPT - It could work with GSM/3G but not with LTE
I still have tons of doubt regarding to the correct way of doing this for several reason:
1) Do we have a kernel for HTC 10 that's really built from scratch? Because if we don't, we're screwed.
I tried with ElementalX and Cleanslate.
2) The other part I'm not entirely sure is if we have to conect to the COM of the HTC Modem or to the COM of Diag Mode (you can check both numbers on device manager in windows).
3) With Diag COM you can read the NV values and try to make changes (even if they don't stay) but I couldn't while connecting to the Modem COM. Maybe to get this to work we need that "AP to CP" change in USB settings that we`re lacking.
Another interesting point is that if I use NV Items Reader or DFS Tools, when I choose the write the NV value, the signal is lost that exact moment. Which means that something is really happen over there. All guides explain that the signal loss is normal and after reboot everything should work as expected. But no, is resets. I hope it is the kernel, cause' I'm running out of ideas.
Haldi4803 said:
P.S anyone tried to change stuff in *#*#4636#*#* Mode?
Click to expand...
Click to collapse
It's absolutely safe to use it.
You can choose with radio preset to apply, I use it to force the phone in LTE only.
Since I can't make the phone to connect to LTE 4, I'm getting no signal.
It takes 20-30 seconds sometimes to take the change so be patient.

michaelbsheldon said:
Hooray!, something changed with Verizon's last OTA. I'm on US unlocked version, S-0ff, unlocked, converted to Verizon.
##3424# didn't work on original OTA, but the 1.19.605.22 update now allows ##3424# to get into diagnostic mode and CHANGE YOUR BANDS with DFS Tool.
Now on 2-4-13 like I want to be.
Click to expand...
Click to collapse
I have considered converting the firmware to Verizon (even if it´s CDMA) so I could try same process (which worked for you).
Problem is, I can't get pass the Setup Wizard after flashing the Verizon RUU. And of course I don't have a Verizon SIM. I can boot normally but it starts with that fricking Wizard just activating the phone and doin' nothing.
Do you know any way to get past that? I'd to try appling the changes over there and afterwards flashing the GSM radio from the international version.
I read that GSM users could change the LTE NV value for CDMA (because it's useless) and the same for CDMA users while changing LTE NV value for GSM. Maybe I could use that in our favor and then flash the radio afterwards .
I have another ace up my sleeve but depends on another user´s collabotarion.

Unlock Bootloader & Root Moto Z2 Force

To unlock Bootloader:
On Phone:
Open Developer Mode: Settings>System>About Phone>Click "Build Number" Seven Times
Go back to System>Developer Options>Turn on: OEM Unlocking & USB Debugging
On PC:
Do Google Search for Downloads:
Download: adb and fastboot
Download: appropriate phone drivers
Connect Phone to PC
Open: adb & fastboot Folder>open Command Prompt/PowerShell
Type:
adb devices (Pop-up will appear on phone to allow USB debugging)
re-type adb devices (you should see your device)
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data (this data is used in the Motorola Website: https://motorola-global-portal.custh...-your-device-a)
Once logged in, put in above unlock data in to see if phone is able to be unlocked...click unlock.
You'll receive a unique unlock code via email....copy unlock code.
Go back to Command Prompt/PowerShell
Type:
fastboot oem unlock (unique unlock code) (type in twice to confirm unlocking)
(NOTE: ALL DATA WILL GET DELETED-BACK IT UP!)
If this isn't working, what hiccups are you running into?
To Root your device:
On Phone:
Make sure: Developer Options on>OEM Unlocking & USB Debugging turned on (steps above)
Connect (turned on) Device to PC
On PC:
download (TWRP file specific to phone: https://twrp.me/Devices/): EXAMPLE: twrp-3.2.3-0-nash.img
Open/Create new/clean adb/fastboot folder
place TWRP img file INTO the above folder
Download: Magisk-V18.0.zip (https://forum.xda-developers.com/app...mless-t3473445)
Place Magisk-V18.0 Zip file into adb/fastboot folder
Once all files within adb/fastboot folder, open Command Prompt/PowerShell
adb devices
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.2.3-2-nash ((add: .img)) Phone should open Team Win Recovery
ON PHONE: Swipe to "Allow Modification"
adb devices (should show "recovery")
adb push Magisk-V18.0.zip /sdcard
adb shell twrp install /sdcard/Magisk-V18.0.zip (phone should show installation)
adb reboot
On Phone:
Open: Magisk Manager
select lines in upper left hand corner>Settings>Automatic Response>Grant
Open "Root Checker App" to verify root (i.e., Root Checker Pro, Root Checker Advanced)

JTC Intl said:
To unlock Bootloader:
[NOTE: device with root access no longer receives official update notifications from the manufacturer)
Click to expand...
Click to collapse
Mine did until I went into Developer Setting and un ticked automatic software updates..

I thought I had found the perfect Z2 for me. Ordered on eBay for $130 with no scratches and very slight screen burn-in. I don't worry about light burn-in as I always use Substratum and turn all my screens amoled black with light text, I never notice the burn-in anyway.
Only problem was it being a T-Mo version but I couldn't unlock the bootloader. I did all that was required to receive the Unlock Code, however, when I input it the second time, it states "code verification failure." Verifed correct code multiple times and upon checking the Motorola unlock help thread, there is a list at the beginning with CID #s of bootloaders that can be unlocked and those that can not. Any CID not listed as "can be unlocked" are unable to be unlocked even if the # does not appear under "cannot be unlocked" list. My CID of 0x0015 was not on either list, therefore deemed unlockable.
I saw someone else inquire about his 0x0015 CID and was told pretty much that same thing, so I didn't add to the thread and just returned the phone. Now I am looking to purchase another T-Mo phone from a different seller with hopes of receiving a compatible CID, but I'm kinda concerned about running into the same issue. Are you aware if there are large group of these T-Mobile phone who's bootloaders can't be unlocked or did I just get a one off CID#. Or should I be looking at rooting a Sprint version and trying to change it to a GSM Unlocked or are there Sprint version with unlockable bootloaders as well? Any advice as how you think I should proceed would be most helpful as I would like to order the replacement phone today or tomorrow. TIA

MrBrazil1911 said:
I saw someone else inquire about his 0x0015 CID and was told pretty much that same thing, so I didn't add to the thread and just returned the phone. Now I am looking to purchase another T-Mo phone from a different seller with hopes of receiving a compatible CID, but I'm kinda concerned about running into the same issue. Are you aware if there are large group of these T-Mobile phone who's bootloaders can't be unlocked or did I just get a one off CID#. Or should I be looking at rooting a Sprint version and trying to change it to a GSM Unlocked or are there Sprint version with unlockable bootloaders as well? Any advice as how you think I should proceed would be most helpful as I would like to order the replacement phone today or tomorrow. TIA
Click to expand...
Click to collapse
If you're a T-Mobile/Metro user the TMO model is ideal. It packs every Magenta band aside from B71. The Sprint version will affect your experience on T-Mobile, as it only possesses 2, 4, and 12. So no LAA, 66, nor LTE-U. B46, aka LAA is stupid fast. I've heard U is good too, but availability is limited.
Now, if you use ATT, VZ, or Sprint you won't miss out on anything by buying the Sprint version.
All things considered, I'd gamble with the former. Playing the TMO lottery is definitely worth it. In fact, I bought a 2nd one and will see what happens in a few days.

Ace42 said:
If you're a T-Mobile/Metro user the TMO model is ideal. It packs every Magenta band aside from B71. The Sprint version will affect your experience on T-Mobile, as it only possesses 2, 4, and 12. So no LAA, 66, nor LTE-U. B46, aka LAA is stupid fast. I've heard U is good too, but availability is limited.
Now, if you use ATT, VZ, or Sprint you won't miss out on anything by buying the Sprint version.
All things considered, I'd gamble with the former. Playing the TMO lottery is definitely worth it. In fact, I bought a 2nd one and will see what happens in a few days.
Click to expand...
Click to collapse
Thanks for the feedback. I am primarily a T-Mo network user. I use Google Voice and just grab cheap MVNO sims from eBay and will occasionally use an AT&T sim card. So if I manual unlock it myself from instructions I've seen here, will I still retain the above bands you mentioned?

MrBrazil1911 said:
Thanks for the feedback. I am primarily a T-Mo network user. I use Google Voice and just grab cheap MVNO sims from eBay and will occasionally use an AT&T sim card. So if I manual unlock it myself from instructions I've seen here, will I still retain the above bands you mentioned?
Click to expand...
Click to collapse
Bands stay following SIM and Bootloader unlocks. But, when the modem of another model is flashed access to LTE is lost.

Trying to do this and can't get unlock code. When I type in command i just get . . . in the cmd prompt

mike2246 said:
Trying to do this and can't get unlock code. When I type in command i just get . . . in the cmd prompt
Click to expand...
Click to collapse
Make sure you're using up to date adb/fastboot files and a 2.0 usb port. If no 2.0 ports try using a hub to bring the 3.0+ ports down.

41rw4lk said:
Make sure you're using up to date adb/fastboot files and a 2.0 usb port. If no 2.0 ports try using a hub to bring the 3.0+ ports down.
Click to expand...
Click to collapse
I have used usb 3.0 all the time. Was never be a problem. But I would try, too :good: Wish the person luck

allrightlite said:
I have used usb 3.0 all the time. Was never be a problem. But I would try, too :good: Wish the person luck
Click to expand...
Click to collapse
3.0 ports won't be a problem for everyone, but for some it is. Some have only been able to use one port on their pc for flashing, some have had to use hubs to dumb their ports down. That's why it is generally recommended to use 2.0 port. Saves having to repeat the same info 100x in every other post.

This worked perfectly until the last step for my Sprint version of Z2 Force. Kudos to JTC Intl for crystal clear instructions.
When I launch the Magisk Manager , it asks me if I want to "Upgrade to full Magisk to finish set up. Download and install?" I respond OK, then after sometime, it says "There was a problem parsing the package".
Instead of v18 of Magisk, I downloaded v22 that too not as a ZIP, but it was only available as an APK from their GITHub. (https://github.com/topjohnwu/Magisk/releases/tag/v22.1)
EDIT - I tried the troubleshooting suggestions for this problem in their wiki ( clearing cache, clearing data, reinstalling etc). Did not help.
Please help. I'm almost there.
Thank you.

hi i need help is there any other way i can unlock the boot loader because when i enter my code it says device not eligible....

JTC Intl said:
To unlock Bootloader:
On Phone:
Open Developer Mode: Settings>System>About Phone>Click "Build Number" Seven Times
Go back to System>Developer Options>Turn on: OEM Unlocking & USB Debugging
On PC:
Do Google Search for Downloads:
Download: adb and fastboot
Download: appropriate phone drivers
Connect Phone to PC
Open: adb & fastboot Folder>open Command Prompt/PowerShell
Type:
adb devices (Pop-up will appear on phone to allow USB debugging)
re-type adb devices (you should see your device)
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data (this data is used in the Motorola Website: https://motorola-global-portal.custh...-your-device-a)
Once logged in, put in above unlock data in to see if phone is able to be unlocked...click unlock.
You'll receive a unique unlock code via email....copy unlock code.
Go back to Command Prompt/PowerShell
Type:
fastboot oem unlock (unique unlock code) (type in twice to confirm unlocking)
(NOTE: ALL DATA WILL GET DELETED-BACK IT UP!)
If this isn't working, what hiccups are you running into?
To Root your device:
On Phone:
Make sure: Developer Options on>OEM Unlocking & USB Debugging turned on (steps above)
Connect (turned on) Device to PC
On PC:
download (TWRP file specific to phone: https://twrp.me/Devices/): EXAMPLE: twrp-3.2.3-0-nash.img
Open/Create new/clean adb/fastboot folder
place TWRP img file INTO the above folder
Download: Magisk-V18.0.zip (https://forum.xda-developers.com/app...mless-t3473445)
Place Magisk-V18.0 Zip file into adb/fastboot folder
Once all files within adb/fastboot folder, open Command Prompt/PowerShell
adb devices
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.2.3-2-nash ((add: .img)) Phone should open Team Win Recovery
ON PHONE: Swipe to "Allow Modification"
adb devices (should show "recovery")
adb push Magisk-V18.0.zip /sdcard
adb shell twrp install /sdcard/Magisk-V18.0.zip (phone should show installation)
adb reboot
On Phone:
Open: Magisk Manager
select lines in upper left hand corner>Settings>Automatic Response>Grant
Open "Root Checker App" to verify root (i.e., Root Checker Pro, Root Checker Advanced)
Click to expand...
Click to collapse
Does rooting the phone work for an AT&T Moto Z2 force phone?