Database Develop

[Q] unable to root following the exact guide here

was trying to root my Galaxy Note following this link:
http://forum.xda-developers.com/showthread.php?t=1312859
but all i got is this, i 100% sure i did every steps right. driver debug etc etc
{
"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"
}
is that because my one is a LA2 version?
just bought my phone from Hong Kong
thanks

maximilianyuen said:
was trying to root my Galaxy Note following this link:
http://forum.xda-developers.com/showthread.php?t=1312859
but all i got is this, i 100% sure i did every steps right. driver debug etc etc
Click to expand...
Click to collapse
Why would you try to root Note with Sony Ericsson Xperia Play rooting method? You are lucky not to have bricked your phone.
Anyway, zegrush method does not work with LA+ builds.
What you want to do is visit DrKetan's Note Rooting thread, read carefully, follow the instructions, and you'll get there.

maximilianyuen said:
was trying to root my Galaxy Note following this link:
http://forum.xda-developers.com/showthread.php?t=1312859
but all i got is this, i 100% sure i did every steps right. driver debug etc etc
is that because my one is a LA2 version?
just bought my phone from Hong Kong
thanks
Click to expand...
Click to collapse
Answer is given by yourself. chasmodo advised you correctly
LA2 is nonrootable. download guide from last link of my signature n follow it, it will lead you step by step to your destination.

maximilianyuen said:
was trying to root my Galaxy Note following this link:
http://forum.xda-developers.com/showthread.php?t=1312859
but all i got is this, i 100% sure i did every steps right. driver debug etc etc
is that because my one is a LA2 version?
just bought my phone from Hong Kong
thanks
Click to expand...
Click to collapse
There is one simple way to root any Note rom by flashing FM Kernel at website following:
http://forum.xda-developers.com/showthread.php?t=1342807
Enjoy,

minhsu said:
There is one simple way to root any Note rom by flashing FM Kernel at website following:
http://forum.xda-developers.com/showthread.php?t=1342807
Enjoy,
Click to expand...
Click to collapse
Can you describe here, How to flash FM kernel without having Root + CWM ?

dr.ketan said:
Can you describe here, How to flash FM kernel without having Root + CWM ?
Click to expand...
Click to collapse
Yeah I'd like to know that too...

To root with FM Kernel, you need:
- FM Kernel 2.0 actually.
- Odin 1.83 on laptop or PC.
- SS USB driver installed on PC.
Then
1. Open Odin 1.83
2. Select PDA and choose FM Kernel.tar
3. Connect Note to PC.
4. Click START on Odin screen, about 20" procedure will finish.
5. Disconnect Note with PC.
6. Now you have rooted Note,
7. Continue to install Superuser 3.0 and CWM to able to use a lots of softwares and to install any firmwares or Kernels that you want.
Enjoy,

minhsu said:
To root with FM Kernel, you need:
- FM Kernel 2.0 actually.
- Odin 1.83 on laptop or PC.
- SS USB driver installed on PC.
Then
1. Open Odin 1.83
2. Select PDA and choose FM Kernel.tar
3. Connect Note to PC.
4. Click START on Odin screen, about 20" procedure will finish.
5. Disconnect Note with PC.
6. Now you have rooted Note,
7. Continue to install Superuser 3.0 and CWM to able to use a lots of softwares and to install any firmwares or Kernels that you want.
Enjoy,
Click to expand...
Click to collapse
If you have updated like this, just check your binary counter.
Custom ROM/Kernel flashing with ODin, raise flash counter.
Have you read this lines? which is there on link you have mentioned
The configuration is more or less Samsung Stock (except debugging, logging and the governor). Maybe I will optimize it in the future. The CWM App from Chainfire is not included, but should work on this kernel. I suggest to first flash a CF Kernel in order to root your phone and get the CWM App. After that you can flash this kernel. I recommend the CWM Manager App for flashing activities.
Click to expand...
Click to collapse

dr.ketan said:
If you have updated like this, just check your binary counter.
Custom ROM/Kernel flashing with ODin, raise flash counter.
Click to expand...
Click to collapse
This is slightly off-topic, but I am new to Samsung devices -- getting my Note today or tomorrow -- and I would like to know what is this flash counter and are there some negative effects to it rising?

WereCatf said:
This is slightly off-topic, but I am new to Samsung devices -- getting my Note today or tomorrow -- and I would like to know what is this flash counter and are there some negative effects to it rising?
Click to expand...
Click to collapse
Flash counter is number, that shows how many time you have flash your device with custom ROM(non samsung), it has negative effect is, when your counter is raised, you can't claim warranty.
Still there is no losing hope, if counter raised, You can reset it to zero, but that requires 'Zig' Hardware Tool.
Keep one golden rule in mind - NEVER flash any custom ROM/Kernel with PC odin.
To get Root n Update ROM, you can get guide from last link on my signature.

Along the same lines, although slightly OT:
I have gained Root access using the zegrush method. That was very painless. I did read a lot before doing it, and obviously picked the right file & approach.
I then installed CWM. That was quite painless too. I found a blog post that described it (because I was unsure what it even was) here:
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
I am sure these details are here somewhere too, but there is a great deal of information here, and sometimes a lot of knowledge is assumed.
I then gritted my teeth, took my Note in my hands, and flashed the Abyss kernel. Again, I read a lot, and I selected the right file (thanks to dr.ketan once again).
So all is quite rosy, and nothing (touch wood) has gone wrong. It seems I can easily flash kernals any time I want.
My only question is, is it just as simple to flash a ROM in this way with CWM? If so, the whole process is much easier than it seemed when I started!
I do point this out because there is an awful lot of information out there. Some of it is in a 'different language' and can be intimidating. It took me ages to get around to finding CWM for example. I am a techie (C++ / Java / C# developer from way back), but it is still not easy to get started. It appears that when you take the time to learn, follow the right steps (after picking the correct set based on your circumstances) it is actually quite simple.
Many thanks to everyone making it possible, and most importantly the developers giving us these great mods for free!

dr.ketan said:
Flash counter is number, that shows how many time you have flash your device with custom ROM(non samsung), it has negative effect is, when your counter is raised, you can't claim warranty.
Click to expand...
Click to collapse
Here in Finland the laws are slightly different, I don't quite think that applies here. I'll still keep that in mind!
To get Root n Update ROM, you can get guide from last link on my signature.
Click to expand...
Click to collapse
Aye, I have bookmarked it

jeromepearce said:
My only question is, is it just as simple to flash a ROM in this way with CWM? If so, the whole process is much easier than it seemed when I started!
Click to expand...
Click to collapse
dr.ketan said:
To get Root n Update ROM, you can get guide from last link on my signature.
Click to expand...
Click to collapse
OK question answered by your guide. I shall read that, and get on with it once I have stopped playing with kernels. Many thanks.

dr.ketan said:
If you have updated like this, just check your binary counter.
Custom ROM/Kernel flashing with ODin, raise flash counter.
Have you read this lines? which is there on link you have mentioned
Click to expand...
Click to collapse
I knew that, but binary counter increases only one time, after that with CWM, upgading firmware easily.
For me, I had a self made Jig so I can remove yellow triangle and binary counter always returns zero.

minhsu said:
I knew that, but binary counter increases only one time, after that with CWM, upgading firmware easily.
For me, I had a self made Jig so I can remove yellow triangle and binary counter always returns zero.
Click to expand...
Click to collapse
So it is better you mention such things in post.

Just want to say thanks for every helpful info
but i will wait and hold after I try out the official ICS upgrade before I and flashing anything...
coz i was hoping this can be done with just 1 click...

[HOWTO][P3113] Revert to Stock Android 4.0.4 ICS build UEBLH2

From Android Authority
{
"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"
}
The official firmware can be used to restore your tablet to its factory state, which means that it can be used as an escape route if you ever need to revert to stock firmware. For instance, this can be very handy if you stumble upon an bad or misbehaving custom ROM that makes your tablet malfunction.
This guide shows you how to revert the Galaxy Tab 2 7.0 P3113 to Android 4.0.4 ICS build UEBLH2 (stock official firmware).
Warning​
The instructions in this guide are intended for use with the Samsung Galaxy Tab 2 7.0, model number GT-P3113. Applying these instructions on another device or model may produce undesired outcomes.
The information in this guide is provided for instructional and educational purposes only. There is no guarantee that these instructions will work under your specific and unique circumstances.
Use these instructions at your own risk. We shall not hold any responsibility or liability for whatever happens to you or your device arising from your use of the info in this guide.
Read and understand the whole guide first before actually performing the instructions.
Requirements​
Samsung Galaxy Tab 2 7.0 GT-P3113
A Windows PC
Install your handset’s USB drivers on the PC. You may install the drivers by installing Samsung Kies.
Enable USB debugging on your handset.
Disable antivirus, firewall, and other security software. Also disable Samsung Kies and other software that accesses your phone. Such software can interfere with the procedure in this guide.
Download the following files to your computer:
UEBLH2 firmware update package for Galaxy Tab 2 7.0 GT-P3113 (P3113UEBLH2_P3113XARBLH2_XAR.zip, 785 MB)
Odin 3.04 (Odin3_v3.04.zip, 456.59 kB) (Attatched)
Make sure your device’s battery still has at least 70% power. You don’t want the device to shut down in the middle of the procedure.
Backup all personal data on your phone to make sure you have a copy of your personal data (e.g., contacts, SMS, MMS, Internet settings, Wi-Fi passwords, and the like) in case the procedure in this guide erases such data.
Instructions​
Using ZIP extraction software, extract the *.tar.md5 file contained in the UEBLH2 firmware update package.
Extract the contents of Odin3_v3.04.zip to your computer.
Turn off your tablet. Make sure it is not hooked up to your PC.
Run Odin on your computer by double-clicking Odin3 v3.04.exe.
Click the PDA button in Odin and load the *.tar.md5 file contained in the UEBLH2 firmware update package that you unzipped.
Do not change any other setting in Odin. Make sure that the checkbox for “Re-partition” is not ticked.
Reboot the tablet into Download Mode by holding down the Volume Down and Power buttons until you see the warning screen. Press the Volume Up key to continue to Download Mode.
Connect the tablet to your PC via USB cable. You should see an “Added!” message on the Odin window.
Click the Start button in Odin to begin flashing the firmware to your tablet. When installation completes and succeeds, Odin will display a “PASSED” message in one of its boxes. The tablet will also automatically reboot.
If, on rebooting, the screen gets stuck at the Samsung logo, try resolving it by doing the following:
Turn off the tablet.
Boot into Recovery Mode by holding down Power and Volume Up buttons together until the screen turns on. When the Samsung logo appears, let go of the Power button but keep holding down the Volume Up button until the device boots into recovery.
In Recovery Mode, select Wipe data/Factory reset and select Yes on next screen.
Select Reboot system now to reboot the tablet
Congratulations! You’ve successfully reverted your Samsung Galaxy Tab 2 7.0 to Android 4.0.4 Ice Cream Sandwich build UEBLH2.

"Disable my AV/security" before I download from unknown links ?
Cool story bro. :laugh: General tip for PC users , scan everything you download onto your desktop no matter the source with your AV. Especially an ".exe "
Nice guide apart from that.

thank you.. I didnt think of wipe data/factory. I was stuck on samsung logo. i wanted to return to stock since I'm giving the tablet to my nephew and don't want him doing crazy stuff. :victory:

Sean_Seany said:
"Disable my AV/security" before I download from unknown links ?
Cool story bro. :laugh: General tip for PC users , scan everything you download onto your desktop no matter the source with your AV. Especially an ".exe "
Nice guide apart from that.
Click to expand...
Click to collapse
NO, not disable before downloading, disable your AV before using Odin to flash, as IT IS A WELL KNOWN FACT that some AV programs can cause issues with flashing ROM's.

daniel644 said:
NO, not disable before downloading, disable your AV before using Odin to flash, as IT IS A WELL KNOWN FACT that some AV programs can cause issues with flashing ROM's.
Click to expand...
Click to collapse
Did you actually read what the OP posted ? Nah didnt think so . So why exactly do you need to disable AV/Secuirty for a USB file transfer ? Please enlighten me with your facts.....

Sean_Seany said:
Did you actually read what the OP posted ? Nah didnt think so . So why exactly do you need to disable AV/Secuirty for a USB file transfer ? Please enlighten me with your facts.....
Click to expand...
Click to collapse
If you are having issues disabling your antivirus software, then don't disable it. I never disable mine. The only reason I added it to the post is because in rare cases the AV can cause issues for some reason or another.

Sean_Seany said:
Did you actually read what the OP posted ? Nah didnt think so . So why exactly do you need to disable AV/Secuirty for a USB file transfer ? Please enlighten me with your facts.....
Click to expand...
Click to collapse
I think you misunderstand, when flashing files VIA ODIN certain antiviruses have been known to cause issues, personally I never have but it is a standard disclaimer on ANY Device to computer connection, when doing debugging or flashing not file transfers, I see the same disclaimer on all the Droid Razr Utility builds, and most ROM's being flashed via ODIN, it's rare but it could happen.

I think the reason for disabling your AV,is because it and your pc dont know the difference. When you run a program that flashes 'firmware' like Odin,it can be detected as malicious and blocked.HTC recommends the same thing for flashing with their exe files,and thats the same reason why its recommended during most rooting process'.

dude I thank you for this... I bought a gt 3113 3 days ago and it came with jb out of the box, dont get me wrong jb is awesome i run it on my sgs2 only thing is id like to use my tablet for streaming online content and most of the sites i view still use flash which jb no longer supports so i been looking for ways to revert it back to stock ics cause i love the ir function of the stock rom and most custom roms bork the ir blaster as per my research. anyway anymore details i should know before attempting this?? thanks in advance
Edit: do you have another linky for the FW? hotfile keeps erroring out on me thanks again

aj9507 said:
dude I thank you for this... I bought a gt 3113 3 days ago and it came with jb out of the box, dont get me wrong jb is awesome i run it on my sgs2 only thing is id like to use my tablet for streaming online content and most of the sites i view still use flash which jb no longer supports so i been looking for ways to revert it back to stock ics cause i love the ir function of the stock rom and most custom roms bork the ir blaster as per my research. anyway anymore details i should know before attempting this?? thanks in advance
Edit: do you have another linky for the FW? hotfile keeps erroring out on me thanks again
Click to expand...
Click to collapse
Yours came with JB??? Just curious what country are you in? The 3113 is US only no?? Maybe were finally getting our official release any day now...
Sent from my crack smoking SGH-i777

Slavestate said:
Yours came with JB??? Just curious what country are you in? The 3113 is US only no?? Maybe were finally getting our official release any day now...
Sent from my crack smoking SGH-i777
Click to expand...
Click to collapse
Yup usa version. 4.1 android love jb but hate that I can't stream from most sites due to lack of flash and most root methods I can't get to work
Sent from my GT-P3113 using Tapatalk HD

Flash works perfect on every jelly bean rom I have tried just simply sideload it but I suppose thats of topic.

yup sideloaded it and even running the older version of the browser to ensure flash support and its laggy and stutters lovin the tablet though

Yes.... some of these are preloaded with 4.1.1.
I bought 2 of these for my daughters. 1 was defective. When I took it back, the store didn't have anymore so they sent me to a store in another city.
I ended up with one running 4.0.4 and one running 4.1.1.

BuLLitz said:
Yes.... some of these are preloaded with 4.1.1.
I bought 2 of these for my daughters. 1 was defective. When I took it back, the store didn't have anymore so they sent me to a store in another city.
I ended up with one running 4.0.4 and one running 4.1.1.
Click to expand...
Click to collapse
PS:The 4.1.1 that came preloaded is UECLK7.
It can be found here...
http://androidjinn.com/how-to-install-ueclk7-android-4-1-1-jelly-bean-on-p3113-galaxy-tab-2.html/2
---------- Post added at 02:14 AM ---------- Previous post was at 01:54 AM ----------
BuLLitz said:
PS:The 4.1.1 that came preloaded is UECLK7.
It can be found here...
http://androidjinn.com/how-to-install-ueclk7-android-4-1-1-jelly-bean-on-p3113-galaxy-tab-2.html/2
Click to expand...
Click to collapse
Following the instructions there, I can confirm that the versions are the same now. Both of my tablets are 4.1.1. In addition, KIES recognizes it as a valid version.

BuLLitz said:
PS:The 4.1.1 that came preloaded is UECLK7.
Following the instructions there, I can confirm that the versions are the same now. Both of my tablets are 4.1.1. In addition, KIES recognizes it as a valid version.
Click to expand...
Click to collapse
The update was officially pushed out today through Kies.
Sent from my crack smoking SGH-i777

well now
I used this and it worked quite well, but now the drivers won't install right when I plug it into my computer.
any suggestions?
thanks.

Re-enable debugging.

ROCK ON! Nice guide!!! I was on JB4.1.1, but, IMO, not good. i rolled back to 4.0.4

ugh
Thepooch said:
Re-enable debugging.
Click to expand...
Click to collapse
Not only can I not install drivers, I can't find the debugging either.
I'm not totally retarded, but I'm starting to feel like it

Wanting to Unroot M8, don't have original image (1.12.651.17)

Hey everyone.
I've spent the better of the last three hours scouring the inter webs, Google, and these forums trying to find the answers to my questions - but to no avail (I've found partial answers, but I am afraid a partial answer could lead to a total brick). So anyway I apologize ahead of time if this has already been addressed somewhere else.
Here we go:
I bought one of the first Sprint HTC One M8's through Amazon. Here are the details:
Model: 831C
Android Version 4.4.2
Software Version 1.12.651.17
Unlocked but S-On (Using TWRP)
Naturally, right out of the box I rooted it. However, I did not save the original recovery image (ROM?).
--> I want to restore the phone to its original state so I can accept the OTA update and hopefully address the god-awful cell signal.
I've found a lot of stock recoveries online, but none that match 1.12.651.17.
Do I need to find that specific recovery (1.12.651.17) to flash to my phone? Will another one work (e.g. 1.54.654.13)? Or, is the recovery image specific to each phone's firmware?
I've never worried about saving my stock recovery in the past (been rooting since the HTC Evo days) but it looks like not doing so finally caught up with me.
Thanks in advance.
PS I did find something 1.12.651.17 related in the link below, but how to flash this to my phone (or whether or not it will brick) is beyond me. I've downloaded all 6 files and am waiting to figure out how the heck to get them to my phone.
http://forum.xda-developers.com/showthread.php?t=2736048

I don't know if this will help at all, but here is a link to the "Nandroid" backup downloads, courtesy of Rydah805 (thank you).
https://
drive.google.com/folderview?id=0B-_A25cR0bQFc1NxdHJkVTJsb0U&usp=sharing
(sorry can't post outside links yet)
I've downloaded all six but am not 100% how to proceed as far as flashing them to the phone via TWRP goes.
Also, not 100% if this will allow me to get back to "stock" so that I can accept the latest OTA update and (hopefully) fix my horrible connection issues.
I am usually one to do my research and then dive in, damn the torpedoes. However in this case I am thinking doing that could turn my phone into a coaster.

all you need is a stock recovery installed and you can do an ota

i was in the same boat as the OP last week. check this thread starting at my post #126 for some assistance from some members:
http://forum.xda-developers.com/showthread.php?t=2759908&page=13
instead of going back to stock to accept OTA, i went S-Off using firewater and then flashed the modified firmware located in post #18 in the same thread:
http://forum.xda-developers.com/showthread.php?t=2759908&page=2
cell signal is 100% improved, it uses 3g more than the LTE spark but it doesnt drop calls or go roaming at random now.
hope that helps.

Tbaggington said:
i was in the same boat as the OP last week. check this thread starting at my post #126 for some assistance from some members:
http://forum.xda-developers.com/showthread.php?t=2759908&page=13
instead of going back to stock to accept OTA, i went S-Off using firewater and then flashed the modified firmware located in post #18 in the same thread:
http://forum.xda-developers.com/showthread.php?t=2759908&page=2
cell signal is 100% improved, it uses 3g more than the LTE spark but it doesnt drop calls or go roaming at random now.
hope that helps.
Click to expand...
Click to collapse
Hot damn that sure does help. I've been having the same issues as you: dropped calls, roaming out of nowhere, failed call origination, etc etc. I may just go the S-Off route instead. Thank you very much for those two links … I have about 24 tabs open in my browser with different possible steps in different possible fixes.
{ParanoiA} said:
all you need is a stock recovery installed and you can do an ota
Click to expand...
Click to collapse
Right on … so any Sprint M8 stock recovery will work? I don't have to specifically get one that matches my phone's current firmware 1.12.651.17?

ecvorst said:
Hot damn that sure does help. I've been having the same issues as you: dropped calls, roaming out of nowhere, failed call origination, etc etc. I may just go the S-Off route instead. Thank you very much for those two links … I have about 24 tabs open in my browser with different possible steps in different possible fixes.
Right on … so any Sprint M8 stock recovery will work? I don't have to specifically get one that matches my phone's current firmware 1.12.651.17?
Click to expand...
Click to collapse
in one of the posts, Magnum Enforcer directed me to a link in his sig. that was key in getting me across the finish line. his post cleared away so much fog in my brain so big thanks to him.
cant help on the stock recovery question, it was too confusing to me so i went the other direction!

He's referring to the second link in my sig. There is a section in the guide regarding firmware updates. Towards the bottom of the first post is also a link to Captain Throwback's firmware thread. No need to go through the hassle of returning to stock to take the OTA if all you want to do is update your firmware. You have to be S-off to update your firmware.

Tbaggington said:
in one of the posts, Magnum Enforcer directed me to a link in his sig. that was key in getting me across the finish line. his post cleared away so much fog in my brain so big thanks to him.
cant help on the stock recovery question, it was too confusing to me so i went the other direction!
Click to expand...
Click to collapse
Magnum_Enforcer said:
He's referring to the second link in my sig. There is a section in the guide regarding firmware updates. Towards the bottom of the first post is also a link to Captain Throwback's firmware thread. No need to go through the hassle of returning to stock to take the OTA if all you want to do is update your firmware. You have to be S-off to update your firmware.
Click to expand...
Click to collapse
Outstanding!
So basically to get my phone "up to date" (and equivalent to taking the most recent OTA update), I simply flash the firmware of my choice to my phone. The trick is to be S-off first.
Then, instead of worrying about OTAs I can just flash the latest firmware whenever it becomes available?
Thanks for bearing with me and for all the great info!

ecvorst said:
Outstanding!
So basically to get my phone "up to date" (and equivalent to taking the most recent OTA update), I simply flash the firmware of my choice to my phone. The trick is to be S-off first.
Then, instead of worrying about OTAs I can just flash the latest firmware whenever it becomes available?
Thanks for bearing with me and for all the great info!
Click to expand...
Click to collapse
That's correct:thumbup:
Sent from my HTC device

Magnum_Enforcer said:
That's correct:thumbup:
Sent from my HTC device
Click to expand...
Click to collapse
Sweet. Thanks man.
Well I'm installing firewater as we speak and I am on the last step after having accepting the terms (including not to taunt firewater). It's hanging up at the "……." part. Not sure if I should hold the power button, start all over, or just panic.
{
"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"
}

Magnum_Enforcer said:
That's correct:thumbup:
Sent from my HTC device
Click to expand...
Click to collapse
By the way, I'm reading your guide right now (http://forum.xda-developers.com/showthread.php?p=51516247#post51516247)… awesome work and very helpful, thank you!

Well just an update:
I have tried the firewater method 6 times now and I keep getting stuck at the same screen I attached on the last page of this thread. I've let this sit for as little as 5 minutes and as long as 30 minutes. Holding the power button for 60 seconds doesn't do anything (unless this prompt means I am supposed to restart the phone).
I'm wondering if the fact that I'm stuck at "………" instead of even getting to the "opening bottles" part means one of the following:
I have a conflict somewhere on the phone or my computer.
or
firewater doesn't work with my Sprint HTC M8
I'll keep digging around to see what I can find.
That notwithstanding, I may have to go back to Plan A and see if I can't get this thing unrooted so I can at least get the OTA and fix the #1 issue: horrible cell reception.
Thanks again for all the helpful input!

Another update … I used #firewater on andirc and the response from beaups was el-quicko. It turns out I was trying to install a version of firewater that wasn't the most recent.
So anyway I guess that's good information for anyone who runs into a similar problem in the future:
Make sure you're trying to install the most recent version of firewater! lol

Interesting developments …
Firewater was a success and I also was successful in downloading the latest firmware to my Mac. I had to select all the files in the folder (it didn't download as a zip) and create a zip file while also naming it the correct name.
Everything went fine as far as sending it to my SD card and using HBOOT method to install. The install went perfectly and I rebooted the phone, but when checking under the About>Software Version on my phone it is still showing Software Version 1.12.651.17 …
Any thoughts?
Thanks.

Software & firmware are different from one another. Flash a different ROM to change the software version.
Sent from my HTC device

I just read a helpful FAQ http://themikmik.com/showthread.php...1-54-651-8-OTA&p=299474&viewfull=1#post299474
Looks like the firmware updates but not the software version.
I'm guessing the same happens whenever someone takes an OTA?

ecvorst said:
I just read a helpful FAQ http://themikmik.com/showthread.php...1-54-651-8-OTA&p=299474&viewfull=1#post299474
Looks like the firmware updates but not the software version.
I'm guessing the same happens whenever someone takes an OTA?
Click to expand...
Click to collapse
If you take a OTA both software & firmware get updated.
Sent from my HTC device

Magnum_Enforcer said:
Software & firmware are different from one another. Flash a different ROM to change the software version.
Sent from my HTC device
Click to expand...
Click to collapse
Thank you Magnum! I just came across the FAQ right after your post. So I guess I should go ahead and flash a new ROM just to make the process complete.
Thanks again for the help - I'm sure I've already mentioned this, but your guide was extremely useful. In the past (original Evo 4g) I've always simply rooted my device and that was it; however, now I'm finally dabbling in the S-Off territory. Sounds like you can do a lot more that way.

ecvorst said:
Thank you Magnum! I just came across the FAQ right after your post. So I guess I should go ahead and flash a new ROM just to make the process complete.
Thanks again for the help - I'm sure I've already mentioned this, but your guide was extremely useful. In the past (original Evo 4g) I've always simply rooted my device and that was it; however, now I'm finally dabbling in the S-Off territory. Sounds like you can do a lot more that way.
Click to expand...
Click to collapse
Glad to help:thumbup:
S-off is definitely the way to go. I've had S-off on every HTC device I've ever owned and it's worth the extra effort to obtain it.
Sent from my HTC device

Magnum_Enforcer said:
Glad to help:thumbup:
S-off is definitely the way to go. I've had S-off on every HTC device I've ever owned and it's worth the extra effort to obtain it.
Sent from my HTC device
Click to expand...
Click to collapse
For sure!
I'm guessing there is really no reason to update my software (that's the RUU stuff, right?) As long as the firmware has been updated, I should hopefully see some improvements to my radio/cell signal.

Got totally Screwed updating my rooted X with 4.4.4

I am not a pro like you guys, but when I bought my unlocked "X Developers Edition 1053" from USA, I could not resist unlocking its bootloader and rooting it.
However I never tried to change the stock ROM, and used my rooted phone for some great apps
But Two days ago, my Phone which was on 4.4.3 got an update to 4.4.4 And I thought why not its just 15 MB update, lets do it.
Wish I would'nt have done that, coz I read somewhere that a rooted phone should not be updated, and now it just shows me the Moto startup Animation for a few seconds and shutdown.
I STFW but got too many ways and I got confused, thought It would be best not to **** my phone with any wild solutions and make problem worse.
I tried starting the phone in fastboot/recovery mode it does go into that mode, when I press Lock and Power Up/Down keys together, and I tried all options in it except "Factory" option, but nothing happens.
So this is it guys, am I really screwed in a big way, or is there any hope for me :crying:
Please help me, even a direction to proper way would also mean a lot.

patel21 said:
I am not a pro like you guys, but when I bought my unlocked "X Developers Edition 1053" from USA, I could not resist unlocking its bootloader and rooting it.
However I never tried to change the stock ROM, and used my rooted phone for some great apps
But Two days ago, my Phone which was on 4.4.3 got an update to 4.4.4 And I thought why not its just 15 MB update, lets do it.
Wish I would'nt have done that, coz I read somewhere that a rooted phone should not be updated, and now it just shows me the Moto startup Animation for a few seconds and shutdown.
I STFW but got too many ways and I got confused, thought It would be best not to **** my phone with any wild solutions and make problem worse.
I tried starting the phone in fastboot/recovery mode it does go into that mode, when I press Lock and Power Up/Down keys together, and I tried all options in it except "Factory" option, but nothing happens.
So this is it guys, am I really screwed in a big way, or is there any hope for me :crying:
Please help me, even a direction to proper way would also mean a lot.
Click to expand...
Click to collapse
You have a custom recovery i assume?
You can try clearing just cache and dalvik. If that doesn't work, May have to clear data too....all your apps and data will be gone though. Not your pics and internal SD stuff though, that will be untouched.
---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------
Next step is see what bootloader version it shows now. If it's still 4.4.3....You can flash the 4.4.3 factory image to get back and running.
Don't downgrade though....that could brick you.

Removed Cache but now: Fastboot Reason Sticky bit factory _fastboot
After applying the following command:
fastboot erase cache
It now gives me error:
Fastboot Reason Sticky bit factory _fastboot
and nothing happens.
I checked moto's website for my framework 4.4.3, but it isn't listed there Firmware till 4.4.2 is only listed there, is it ok to flash this version ?

No, it's not. If you downgrade you can/will likely brick. Now or later.

patel21 said:
I checked moto's website for my framework 4.4.3, but it isn't listed there Firmware till 4.4.2 is only listed there, is it ok to flash this version ?
Click to expand...
Click to collapse
If you're giving up trying to save your data and just want your phone back, and if you're sure you have the xt1053, and you're sure 4.4.3 is what you want, then follow the guide here: http://www.theandroidsoul.com/back-...to-x-xt1053-to-android-4-4-3-kitkat-firmware/
if you wanna save data you might hold off in case anyone else has any ideas.
in the future always make a nandroid backup of your android device asap and after each ota update. you do that from the custom recovery that you installed, and save a copy off your device, on a computer or hd. speaking of the custom recovery, after you make the nandroid and flash superSU, if you're not using it regularly then it's probably better to flash back stock recovery. from what I understand it is not having root that's causing problems with OTA updates, it's the custom recovery. So if you keep it stock you don't have to remember to flash back for OTA, while still enjoying the benefits of root. the OTA will break your root, but since you're unlocked anyway you just have to go through it after each ota and you're golden.

My phone isn't T-Mobile. Will T-Mobile ROM work ?
Thanks for the reply man :good:
My XT1053 is a retail GSM Developer Edition, bought from Motorola Site directly, without any contract with T Mobile, but the guide in the Link uses T-Mobile ROM, is it safe to use it in my phone ?
Update: The Link for Downloading T-Mobile ROm doesn't work.

patel21 said:
Thanks for the reply man :good:
My XT1053 is a retail GSM Developer Edition, bought from Motorola Site directly, without any contract with T Mobile, but the guide in the Link uses T-Mobile ROM, is it safe to use it in my phone ?
Update: The Link for Downloading T-Mobile ROm doesn't work.
Click to expand...
Click to collapse
According to gsmarena moto x is
Available as:
Motorola Moto X XT1058 for AT&T
Motorola Moto X XT1053 for T-Mobile
Motorola Moto X XT1052 for Europe
Motorola Moto X XT1056 for Sprint
Motorola Moto X XT1060 for Verizon
Motorola Moto X XT1055 for U.S. Cellular
To my mind XT1053 should be the same whatever it's called T-Mobile or developer, only difference being in the fine print where one voids your warranty for unlocking and the other doesn't. but you might wanna confirm that.
As for the link, guess it's down. but the main thing is the firmware exists online.

patel21 said:
Thanks for the reply man :good:
My XT1053 is a retail GSM Developer Edition, bought from Motorola Site directly, without any contract with T Mobile, but the guide in the Link uses T-Mobile ROM, is it safe to use it in my phone ?
Update: The Link for Downloading T-Mobile ROm doesn't work.
Click to expand...
Click to collapse
The unlocked GSM Moto X dev ed is the exact same phone as the TMobile Moto X - they are both XT1053 - so you use the TMobile SBF for the unlocked GSM dev ed.
Right now the SBF firmware site is down so you are going to have to wait until they get it back up. The site is not working for anyone right now.
Also keep in mind that since you bought directly from Motorola, you have a 1 year warranty on the device and since it is a dev ed, the warranty was not voided when you unlocked it. So if worse comes to worse, you can return for a warranty replacement as long as you are still within 1 year of purchase.

patel21 said:
T
Update: The Link for Downloading T-Mobile ROm doesn't work.
Click to expand...
Click to collapse
The site is back up now.

Any chances for getting my data back
The T-Mobile Link is working now
But Until it gets Downloaded, is there a method to just backup my phone's data.
Steps I can follow to copy data from phone to my pc, before I go dtg7's route.

patel21 said:
The T-Mobile Link is working now
But Until it gets Downloaded, is there a method to just backup my phone's data.
Steps I can follow to copy data from phone to my pc, before I go dtg7's route.
Click to expand...
Click to collapse
Do you have a custom recovery like TWRP installed?

Yes I have !
When I go to "Recovery" option it takes me to a grey backgorund and blue fonts page, with different options.
And there is a logo of a Man with a Hat.

patel21 said:
When I go to "Recovery" option it takes me to a grey backgorund and blue fonts page, with different options.
And there is a logo of a Man with a Hat.
Click to expand...
Click to collapse
Like this?
{
"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"
}
Did you install the clockworkmod recovery? If so you need to make a nandroid.

Yes its that CWM
Wansanta said:
Like this?
Did you install the clockworkmod recovery? If so you need to make a nandroid.
Click to expand...
Click to collapse
So how do I make nandroid and copy it to my PC

patel21 said:
So how do I make nandroid and copy it to my PC
Click to expand...
Click to collapse
I don't use CWM so I would have to look it up myself. I use TWRP. You can probably find out how to do it through CWM's website.
Once you figure it out, make a nandroid and keep a copy on your PC. Then flash the 4.4.4 sbf. Then install a custom recovery, root 4.4.4 and install Titanium back up. Then extract your data from the nandroid using TiBU.

At this point, you should do some reading. It's obvious you have no idea what you're doing. Stop now before you screw your phone up any further.

Thanks nhizzat and wansanta, Will do some search on nandroid for sure.
Ok, So as you guys have given me a ray of hope. I am checking the ways by which I can save my data.
Wouldn't do anything that I don't know what it does.

patel21 said:
Ok, So as you guys have given me a ray of hope. I am checking the ways by which I can save my data.
Wouldn't do anything that I don't know what it does.
Click to expand...
Click to collapse
If you can get into CWMR, you can make a nandroid. And if you can make a nandroid, you can extract your data using TiBU.

Wansanta said:
If you can get into CWMR, you can make a nandroid. And if you can make a nandroid, you can extract your data using TiBU.
Click to expand...
Click to collapse
I created a backup from CWM, but it will be placed in Phone's internal memory right ? So when I flash my phone with TMobile ROM, wouldn't it erase the backup file too?
Is there a way to extract the backup file to my PC directly before flashing ?

patel21 said:
Is there a way to extract the backup file to my PC directly before flashing ?
Click to expand...
Click to collapse
Again I don't use CWMR so I can't tell you how that works. With TWRP, the backups are in a folder labeled TWRP. You just connect your phone to your PC and copy that folder to your PC.

How To Change CSC

I'm in Australia and want to change the CSC from OPS to TEL. I'm aware that the phone has a multi CSC and it seems the only way to change the CSC is with root. I've tried other methods and none seem to work.
With root, is it a simple matter to change the CSC? Is there a guide for changing it somewhere?

I'm curious about this myself. The store I got mine from sold me the wrong version (which I didn't know until I opened it since there was no way for me to tell on the outside, so they won't let me return it), and I really hate the boot screen from a carrier that isn't mine. More importantly, I can't use tethering, which I assume is because of the CSC, though despite my SIM card, the CSC is still set to the original carrier.
I read something about a different carrier's SIM card switching the CSC upon reboot, or using a USSD code to choose which carrier you're on for the multi-CSC, but those didn't work. I also tried flashing my carrier's CSC (though I used Home_CSC so my data wasn't deleted), even though I knew it would likely be fruitless because of the multi-CSC... and it was.
I'm really puzzled because I just want to change over to my carrier, and since the store won't let me exchange it, I'm not sure what to do. I saw a recommendation to ask Samsung. Maybe they could help. I don't know. I just want a solution for this too.

TankedThomas said:
I'm curious about this myself. The store I got mine from sold me the wrong version (which I didn't know until I opened it since there was no way for me to tell on the outside, so they won't let me return it), and I really hate the boot screen from a carrier that isn't mine. More importantly, I can't use tethering, which I assume is because of the CSC, though despite my SIM card, the CSC is still set to the original carrier.
I read something about a different carrier's SIM card switching the CSC upon reboot, or using a USSD code to choose which carrier you're on for the multi-CSC, but those didn't work. I also tried flashing my carrier's CSC (though I used Home_CSC so my data wasn't deleted), even though I knew it would likely be fruitless because of the multi-CSC... and it was.
I'm really puzzled because I just want to change over to my carrier, and since the store won't let me exchange it, I'm not sure what to do. I saw a recommendation to ask Samsung. Maybe they could help. I don't know. I just want a solution for this too.
Click to expand...
Click to collapse
I'm on the same boat. Wondering if you've figured out a way. ?
Sent from my HUAWEI LYA-L0C using XDA Labs

I've changed the CSC on my S7 without needing to root the device. I think the process should be the same for the Note 9, though I'm not really familiar with multi-CSC. You'll need a Windows computer.
Get the firmware with the CSC you want from SamMobile or Updato (TEL, XSA etc.)
Get the latest ODIN version from XDA
Unzip your firmware so you've got the various files (AP, BL, CSC etc.)
Put the phone into download mode (https://www.youtube.com/watch?v=DkdEcMGFvzY) Don't worry if it takes a couple of tries
Start ODIN and make sure the phone is connected and appearing in ODIN
Add the various firmware files to the corresponding boxes in ODIN. When you come to the CSC one, add that file that starts CSC. NOT the HOME_CSC one.
Run the flash in ODIN
Wait for the flash to complete and the phone to reboot. Both the flash and the reboot will take several minutes, go get yourself a coffee.
Process now complete, you can delete the firmware files from your PC.
This worked on my S7 and the phone was able to take an OTA afterwards.
A couple of notes though.
I have not tried this on a Note 9, but I believe the process should be the same.
This will wipe your phone, so backup first.
You must flash a firmware from the same model. You cannot flash a N960F firmware onto a N9600. They have different hardware.
While you'll only need to do this process once, think carefully about if you need to and what you'll get out of it (Samsung Pay, VoLTE, RCS). If these are features you don't use it's probably not worth the hassle.
Done correctly this won't trip Knox as you're using Samsung signed firmware.
If you give this a go, report back with your experiences.

Thanks but that won't work on the Note 9 now that Samsung has started using a "multi" CSC. I tried lots of methods including the one you have posted. The only method that works on Samsung phones using the multi CSC is this one:
https://forum.xda-developers.com/ga...de-how-to-change-s9-s9-csc-model-csc-t3870836
I used this method on my Note 9 yesterday and it worked. Finally after 2 months I've been able to change the CSC.
I think that they started using the multi CSC from the S8 forward.

Dang. Looks like I have some reading to do to get my head around these multi CSC devices.

Sea-Wolf said:
Dang. Looks like I have some reading to do to get my head around these multi CSC devices.
Click to expand...
Click to collapse
It's a heavy handed approach by Samsung. I even tried to get an authorised Samsung service center to do it for me. I was willing to pay them. They told me that Samsung won't allow them to change the CSC. So if you want to switch service providers, in my case from Optus to Telstra, you can't change the CSC. Without the correct CSC VoLTE and VoWifi won't work.
Thankfully I found the method that I've linked and it works.

appro77 said:
Thankfully I found the method that I've linked and it works.
Click to expand...
Click to collapse
When you followed that method, did you need to do the first step? I'm not sure what he means there but I think he's saying to flash the multi CSC with ODIN first.

Sea-Wolf said:
When you followed that method, did you need to do the first step? I'm not sure what he means there but I think he's saying to flash the multi CSC with ODIN first.
Click to expand...
Click to collapse
The first step is referring to the "Combination Rom". It's a special rom that is used by engineers ( I suppose) to do high level work on the phone. It's not a normal rom. You can't install apps on it etc. It opens to a screen with lots of settings that you don't have to touch. Once the Combination Rom file is flashed with Odin, the phone will reboot into the rom.
Then you do the steps using RealTerm, and then you flash the rom for your phone after rebooting into download mode again and use Odin.
Obviously the CSC file of the rom you flash must contain the CSC that you have nominated when you change the CSC using Realterm in the previous step.

Ah ok, thanks for the info.

mrnovanova said:
I'm on the same boat. Wondering if you've figured out a way.
Sent from my HUAWEI LYA-L0C using XDA Labs
Click to expand...
Click to collapse
Short of rooting or getting it exchanged, not yet. Samsung has been telling me for a month that they'll get it sorted for me but their customer service sucks assssssss.
More info below, if you're interested.
Sea-Wolf said:
I've changed the CSC on my S7 without needing to root the device. I think the process should be the same for the Note 9, though I'm not really familiar with multi-CSC. You'll need a Windows computer.
Get the firmware with the CSC you want from SamMobile or Updato (TEL, XSA etc.)
Get the latest ODIN version from XDA
Unzip your firmware so you've got the various files (AP, BL, CSC etc.)
Put the phone into download mode (https://www.youtube.com/watch?v=DkdEcMGFvzY) Don't worry if it takes a couple of tries
Start ODIN and make sure the phone is connected and appearing in ODIN
Add the various firmware files to the corresponding boxes in ODIN. When you come to the CSC one, add that file that starts CSC. NOT the HOME_CSC one.
Run the flash in ODIN
Wait for the flash to complete and the phone to reboot. Both the flash and the reboot will take several minutes, go get yourself a coffee.
Process now complete, you can delete the firmware files from your PC.
This worked on my S7 and the phone was able to take an OTA afterwards.
A couple of notes though.
I have not tried this on a Note 9, but I believe the process should be the same.
This will wipe your phone, so backup first.
You must flash a firmware from the same model. You cannot flash a N960F firmware onto a N9600. They have different hardware.
While you'll only need to do this process once, think carefully about if you need to and what you'll get out of it (Samsung Pay, VoLTE, RCS). If these are features you don't use it's probably not worth the hassle.
Done correctly this won't trip Knox as you're using Samsung signed firmware.
If you give this a go, report back with your experiences.
Click to expand...
Click to collapse
That doesn't work, unfortunately. I've changed the CSC on an S7 with no issue, but the Note 9 is a whole other beast. No matter how many times you do a complete flash and deep format/NAND erase etc., it won't work. Not really sure how or why. What's annoying is that it seems the N960F models (or, at least, some of them) won't switch CSCs depending on the installed SIM card. If they did, I wouldn't have an issue.
I will add that you definitely need Windows though. Odin on Mac just never seems to work for me. Odin in Windows via Parallels works okay (i.e. sometimes it works, sometimes it doesn't, but it should work more often than not - if it doesn't, set it up via BootCamp first and then it should run fine in Parallels).
appro77 said:
Thanks but that won't work on the Note 9 now that Samsung has started using a "multi" CSC. I tried lots of methods including the one you have posted. The only method that works on Samsung phones using the multi CSC is this one:
https://forum.xda-developers.com/ga...de-how-to-change-s9-s9-csc-model-csc-t3870836
I used this method on my Note 9 yesterday and it worked. Finally after 2 months I've been able to change the CSC.
I think that they started using the multi CSC from the S8 forward.
Click to expand...
Click to collapse
I believe it got more egregious with the S9 and Note 9 though, but I could be wrong. Thanks for the link though, I'm going to give it a try tonight. Here's hoping...
appro77 said:
It's a heavy handed approach by Samsung. I even tried to get an authorised Samsung service center to do it for me. I was willing to pay them. They told me that Samsung won't allow them to change the CSC. So if you want to switch service providers, in my case from Optus to Telstra, you can't change the CSC. Without the correct CSC VoLTE and VoWifi won't work.
Thankfully I found the method that I've linked and it works.
Click to expand...
Click to collapse
Yeah, I can't stand it personally.
As I mentioned earlier, Samsung actually said they'll sort it out for me and replace it, but that's because the retailer I bought it from misled me and sold me the wrong version of the Note 9 (different carrier to what I asked for; they said they were all the same, and I had my father pick it up for me because I was busy so I didn't have the chance to tell them how wrong that is unless it's carrier-unbranded, which wasn't what they were advertising anyway).
I suppose you could always try weaving a tall tale or exaggerating the issue to get Samsung to cooperate with you. It's worth a shot. Just be aware that they're slow as balls to do anything.
I talked to them on their live chat about a month ago and went through a whole process which amounted to nothing, then emailed them about it and they said they would sort it out and they escalated it... and now a month later, I got back on their live chat (Wednesday this week, in fact), and they apologised for not getting it sorted sooner and that they'd sort it out that day and email me back etc. It's Friday night here and still nothing so I'll get in touch with them again if I haven't heard from them by Wednesday next week (and if the above method doesn't work for me).
appro77 said:
The first step is referring to the "Combination Rom". It's a special rom that is used by engineers ( I suppose) to do high level work on the phone. It's not a normal rom. You can't install apps on it etc. It opens to a screen with lots of settings that you don't have to touch. Once the Combination Rom file is flashed with Odin, the phone will reboot into the rom.
Then you do the steps using RealTerm, and then you flash the rom for your phone after rebooting into download mode again and use Odin.
Obviously the CSC file of the rom you flash must contain the CSC that you have nominated when you change the CSC using Realterm in the previous step.
Click to expand...
Click to collapse
The issue with this is getting a combination file compatible with your boot loader. The free ones that are available without paying dodgy Chinese websites didn't work for me (I got ONE of them to run but it wasn't happy about it, and it still wouldn't work, but I could try that process you mentioned with it and see for sure). And as for getting the right combination file even if you're willing to pay for it (which I'd be okay with since the price is low, but I'm not sure if I trust those sites enough to go ahead with it), figuring out which version one needs is a bit confusing, especially for an Android novice like myself.

TankedThomas said:
Short of rooting or getting it exchanged, not yet. Samsung has been telling me for a month that they'll get it sorted for me but their customer service sucks assssssss.
More info below, if you're interested.
Click to expand...
Click to collapse
Oh. Thanks for replying. I was able to change. My CSC using the *#272 trick without issues. Worked like a charm. ?
Sent from my Samsung SM-N960W using XDA Labs

mrnovanova said:
Oh. Thanks for replying. I was able to change. My CSC using the *#272 trick without issues. Worked like a charm.
Sent from my Samsung SM-N960W using XDA Labs
Click to expand...
Click to collapse
Really? On a N960F? Were you running the latest update? That's never worked for me. Just tells me the USSD code is invalid...
And unfortunately, so far, the other method doesn't work for me either: https://forum.xda-developers.com/showpost.php?p=78425738&postcount=38
If only I could get my phone to connected properly to RealTerm, it should work fine... but it won't connect. Dammit...
EDIT: Seems the solution is to keep retrying (and restarting) your PC and phone until it works. Or something like that. I posted an update in the aforementioned thread, and now it works for me. Now I have XNZ/XNZ/TNZ (not super-happy about it remembering it was originally TNZ but it's not like I can change that without getting an entirely new device, or rooting it, anyway, and it doesn't affect anything negatively). The USSD code solution still doesn't work for me though, so there's that.