Develop Bugs

[HOWTO] Change PRL on Virgin Mobile LG Optimus V (5/06/2011)

I saw this information posted elsewhere in pieces and thought I'd bring it together. I didn't make this procedure, but I can confirm that it works (and so can many others now). This is absolutely for the LG Optimus V and no other phone. Do not do this unless you understand what a PRL is and why you are doing it. There is some risk in doing this. I'm sure Virgin and Sprint would not be happy to know of this mod. It might even be blocked in the future by changing the way Sprint's towers filters Virgin users. Do this at your own risk! I take no responsibility!
1. Requirements:
Windows
LG Optimus V USB Serial Drivers (updated 3/22/2011)
Read the first few pages of this thread if you have driver issues. You can also try this. Thank you rjones1981.
You don't need to have a rooted phone to do this.
2. Get Your MSL Code:
New Technique (thanks to mmarz)
Log into your Virgin Mobile account.
Click this link
Although you get a 404 error page, search the page for "msl:"
The six numbers after msl: are your MSL code. Write them down.
Old Technique
Download CDMA Workshop 3.6.0 Demo
Turn on USB Debugging, and connect your phone to your PC.
Open Device Manager.
Ports > LGE Android Platform USB Serial Port > Properties > Port Settings > Advanced > COM port number
Change the value to a port number below 10. (demo restriction of CDMA Workshop)
Run CDMA Workshop
Select the proper port from step 4. Hit "Connect."
Under the "Security" tab, find "SPC/User Lock."
Change the drop down menu to "LG method," and click "Read."
Write down the number that appears in the box. This is your MSL code. Now close CDMA Workshop, we won't need it anymore.
3. Update Your PRL:
Connect your phone to your computer using a USB cable.
Open Device Manager.
Ports > LGE Android Platform USB Serial Port > Properties > Port Settings > Advanced > COM port number
Make a note of your COM port number.
Download and install QPST v2.7.
Open "QPST Configuration".
In the "Ports" tab, if your com port isn't listed, select "Add New Port" and write in your com port as "COM#" (# being the number you noted in step 4). Verify that your com port is listed.
Make sure your phone appears in the the "Active Phones" tab.
Click "Start Clients." Choose "SERVICE PROGRAMMING." Select your phone.
Click "Read from Phone."
Enter your MSL code when promoted. (It will not finish reading from your phone. It will stop near the end and report an error. This is normal.)
Hit "Save to File" to backup your phone's settings and PRL to a .qcn file. (Optional but recommended)
Select the "Roaming" tab.
Under "Preferred Roaming Enable" choose "Browse..." and select the 01115.prl or 61677.prl file. (attached below, also see update 6)
Under the "System" tab change "Roam Preference" to "Home only". (Optional but recommended)
Click "Write to Phone," and your phone should immediately reboot. Do not disconnect your phone until it has booted back up.
To confirm that this worked, go into settings > about phone > status. You should have the new PRL and all that it entails. To reverse the process, follow the same steps but use the Virgin 61007 PRL or use your .qcn backup by selecting "Load from File" in the QPST SERVICE PROGRAMMING.
If you try different PRL's and get better service, please post your results here.
Update 1: Even though you can enable roaming using the QPST System tab under Roam Preferences, and you can actually connect to the Verizon towers, your calls will prompt you for a credit card, and your data will not work while roaming. I recommend leaving roaming on "Home Only." Even though you can't roam, an updated PRL will give you better coverage on Sprint's network. There are already reports that this fixes the 3G connectivity issue.
Update 2: I have created a hybrid PRL numbered 61676. I manually picked that number, and it may conflict with the PRL # of one released in the distant future, just fyi. I created the PRL by taking 60676 and removing a few roaming entries to make room. I then compared the entries in 61007 to it, and added all the non-roaming entries that 60676 lacked. It will almost be impossible to figure out if these additional entries help at all, but they can't hurt. I'm attaching 61676 below if you guys want to test it out. I promise nothing, but so far my phone has not complained about using it. Let me know how it works out if you do try it.
Update 3: Added new 60677 and a new hybrid 61677
Update 4: Proof that it is worthwhile to do!
Update 5: Added 01115 PRL. It is the latest from Sprint. Don't know why it is numbered like it is. I'm not going to make another hybrid prl for it because it is too time consuming, and I see no benefits from it.
Update 6: I'll no longer keep this updated for new PRL's. You can find new ones as they are posted here: http://cid-eabe29f3770d8d15.skydriv...Public/PRLs?ppud=4&wa=wsignin1.0&sa=636785150
Update 7: Newest PRL posted here: http://forum.xda-developers.com/showpost.php?p=17690691&postcount=201
Roaming does not work on Virgin Mobile! If you do roam, you will not receive your phone calls or texts, and you won't be able to make calls or send texts! Your data will also not work if roaming. Set your "Roam Preference" to "Home only", and you don't have to worry about roaming.

This was never in pieces, why don't you give proper thanks to the original poster from android central?
http://forum.androidcentral.com/opt...irgin-mobile-prl-61007-needed-enter-help.html

xtravbx said:
This was never in pieces, why don't you give proper thanks to the original poster from android central?
http://forum.androidcentral.com/opt...irgin-mobile-prl-61007-needed-enter-help.html
Click to expand...
Click to collapse
Haha, you should be asking why he doesn't give proper thanks to me. I wrote this, and he copied it. Before I wrote it, it was spread out over a bunch of posts. I don't really care either way. I didn't invent the phone, the programs, or the procedure. I'm just glad the info is out there.
http://forum.androidcentral.com/opt...prl-61007-needed-enter-help-5.html#post715849
I guess he did reference me.

I've installed all of the proper drivers but my phone is not showing up in device manager. i have a rooted V on sublimewulf's stock rom.
my cpu is running 64bit win7. after a little research i believe the sprint prl will help me quite a bit in my hometown.
is there anything thing i can do to set com for my phone?
UPDATE found my phone its not using the lg drivers, its using adb sooner driver but i cant figure out how to get it ti show in ports tab

i shot jfk said:
I've installed all of the proper drivers but my phone is not showing up in device manager. i have a rooted V on sublimewulf's stock rom.
my cpu is running 64bit win7. after a little research i believe the sprint prl will help me quite a bit in my hometown.
is there anything thing i can do to set com for my phone?
UPDATE found my phone its not using the lg drivers, its using adb sooner driver but i cant figure out how to get it ti show in ports tab
Click to expand...
Click to collapse
Uninstall the other drivers and install the correct ones.

Does anyone know how to fix the "Failed..phone does not answer" response I get from CDMA when I try to read the spc using the lg method?
This is something I'd really like to try.
Thank you for taking the time to write the guide!

overthinkingme said:
Does anyone know how to fix the "Failed..phone does not answer" response I get from CDMA when I try to read the spc using the lg method?
This is something I'd really like to try.
Thank you for taking the time to write the guide!
Click to expand...
Click to collapse
Which version of CDMA Workshop are you using? It works fine using the demo linked above. You may want to also try reinstalling the drivers. After you click connect, does pressing the read button next to it return an error?

Yeah, i must be missing something here, I installed what should be the right drivers I'd thought but when I plug the phone in there's nothing in device manager under ports... There's an "ADB Interface" now with "Android Sooner Single ADB" under it. There's a Google mass Storage USB Device under Disk Drives, and a new USB Mass storage device under Universal Serial Bus...
So what am I doing wrong and how do I fix it?
Thanks for any help!

danwil77 said:
Yeah, i must be missing something here, I installed what should be the right drivers I'd thought but when I plug the phone in there's nothing in device manager under ports... There's an "ADB Interface" now with "Android Sooner Single ADB" under it. There's a Google mass Storage USB Device under Disk Drives, and a new USB Mass storage device under Universal Serial Bus...
So what am I doing wrong and how do I fix it?
Thanks for any help!
Click to expand...
Click to collapse
Same issue here. If I install the phone's USB drivers from the LG website (http://www.lg.com/us/mobile-phones/LG-VM670.jsp, under "Resources" tab) I get an "ADB Interface" section in the device manager with "Android Sooner Single ADB" under it, exactly as the previous poster described.
If I uninstall those and install the drivers linked to in the OP, I then get told that no driver was found for my device when I plug in my phone. It should be noted that the page linked to by the original poster identifies the drivers there as being for the LG-LS670, which would be the Optimus S... The Sprint version of the phone. The Optimus V is technically the LG-VM670. (See http://en.wikipedia.org/wiki/LG_Optimus_One#LG_Optimus_S_-_LS670_-_Sprint).
Could this be why my system is refusing to use those drivers?
Are those of you who've connected to your Optimus V with the drivers linked to in the OP all running hacked ROMs?

Kate6 said:
Same issue here. If I install the phone's USB drivers from the LG website (http://www.lg.com/us/mobile-phones/LG-VM670.jsp, under "Resources" tab) I get an "ADB Interface" section in the device manager with "Android Sooner Single ADB" under it, exactly as the previous poster described.
If I uninstall those and install the drivers linked to in the OP, I then get told that no driver was found for my device when I plug in my phone. It should be noted that the page linked to by the original poster identifies the drivers there as being for the LG-LS670, which would be the Optimus S... The Sprint version of the phone. The Optimus V is technically the LG-VM670. (See http://en.wikipedia.org/wiki/LG_Optimus_One#LG_Optimus_S_-_LS670_-_Sprint).
Could this be why my system is refusing to use those drivers?
Are those of you who've connected to your Optimus V with the drivers linked to in the OP all running hacked ROMs?
Click to expand...
Click to collapse
I uploaded the drivers myself and fixed the link in the original post. Uninstall and delete (using device manager) the "Android Sooner Single ADB" driver and try unplugging and reinserting the USB cable.. If the device shows up as unrecognized, Right click on it in the device manager window> Update Driver Software> Browse my Computer> Let me pick from a list> All> (wait for the list to be populated)> LG Electronics> LGE Android Platform USB Serial.

freddysam said:
Which version of CDMA Workshop are you using? It works fine using the demo linked above. You may want to also try reinstalling the drivers. After you click connect, does pressing the read button next to it return an error?
Click to expand...
Click to collapse
CDMA 2.7, I am going to try the demo and see if that helps.
Read also returns the same error. It connects fine though.
EDIT:
Figured it out!
Don't connect to the modem port.
I should have read the directions more slowly.

freddysam said:
I uploaded the drivers myself and fixed the link in the original post. Uninstall the other drivers you are using and install these. If the device shows up as unrecognized, Right click on it in the device manager window> Update Driver Software> Browse my Computer> Let me pick from a list> All> (wait for the list to be populated)> LG Electronics> LGE Android Platform USB Serial
Click to expand...
Click to collapse
Okay... I've uninstalled any LG drivers I previously had installed, installed the drivers you uploaded.
{
"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"
}
Turned on USB Debugging on my phone and plugged it in. Device Manager shows this:
I right click, "Update Driver Software" => "Browse my computer for driver software" => "Let me pick from a list of device drivers on my computer"... This brings me here:
Unchecking "Show compatible hardware" gives me a lot more options, including a couple of references to the "HTC Dream" (which I believe is another name for the T-Mobile G1, the first widely available Android phone)... But nothing about USB Serial.
The only thing I have showing up under ports is a "Printer Port (LPT1)." What am I doing wrong? Any clue?

Same exact results here as above, can't get the USB Serial drivers to show up anywhere after uninstalling and installing the new drivers that were uploaded...
I've tried it on Windows 7 Home 32bit and also Windows 7 Ultimate 64bit with the same results (of course i'd already tried the install with the other drivers on both machines... Should I dig out an XP machine to try this on?
Has anyone with an un-rooted Optimus V gotten this to work?
I hope after all this trouble (assuming i get it to work) it actually does help with all the 3g data outages like i've been promised

Kate6 said:
Okay... I've uninstalled any LG drivers I previously had installed, installed the drivers you uploaded.
http://www.kate6.org/Screen0.png
Turned on USB Debugging on my phone and plugged it in. Device Manager shows this:
http://www.kate6.org/Screen1.png
I right click, "Update Driver Software" => "Browse my computer for driver software" => "Let me pick from a list of device drivers on my computer"... This brings me here:
http://www.kate6.org/Screen2.png
Unchecking "Show compatible hardware" gives me a lot more options, including a couple of references to the "HTC Dream" (which I believe is another name for the T-Mobile G1, the first widely available Android phone)... But nothing about USB Serial.
http://www.kate6.org/Screen3.png
The only thing I have showing up under ports is a "Printer Port (LPT1)." What am I doing wrong? Any clue?
Click to expand...
Click to collapse
You didn't uninstall the Android Sooner Single ADB Interface Driver. Right click on it and select Uninstall. When it asks you to confirm, check the box to delete the drivers. Then follow the directions I posted to manually add the correct driver.

freddysam said:
Haha, you should be asking why he doesn't give proper thanks to me. I wrote this, and he copied it. Before I wrote it, it was spread out over a bunch of posts. I don't really care either way. I didn't invent the phone, the programs, or the procedure. I'm just glad the info is out there.
http://forum.androidcentral.com/opt...prl-61007-needed-enter-help-5.html#post715849
I guess he did reference me.
Click to expand...
Click to collapse
Hmmmm, really? OK... Yes, it was spread out (in one thread, not multiple). But you gave no mention where you obtained the info from. But thanks for cleaning it up, cause it did help a few people get going.

freddysam said:
You didn't uninstall the Android Sooner Single ADB Interface Driver. Right click on it and select Uninstall. When it asks you to confirm, check the box to delete the drivers. Then follow the directions I posted to manually add the correct driver.
Click to expand...
Click to collapse
God, I hate Windows. There's no Mac-native or Linux-native programs that can do this, are there?
At this point there was nothing to right click on, which I assume means that when I uninstalled the drivers through the "Uninstall Programs" control panel it left some files behind that were mucking up the process. So I went ahead and reinstalled the driver's from LG's, website, reconnected my phone to get the "Sooner Single" to show up, then right clicked on it, chose uninstall and make sure Delete was selected.
Then I went in the Uninstall control panel to make sure everything was deleted. Then I deleted anything that looked like it was owned by LG under C:\Program Files, C:\ProgramData and C:\Windows\System32\Drivers.
Then I installed your drivers, as linked in the first post and plugged my phone back in. And it showed back up as the "Sooner Single" interface, but had a "Device Cannot Start" error on it... Which I'm guessing means that driver was actually in your package. Right clicked, uninstall, make sure I check Delete... Unplug and replug my phone back in. This time I get an "Android USB Device" that the system was unable to find a driver for.
So I followed your directions.... Update Driver, Search my computer, etc. There appears to be both an "LG Electronics, Inc" entry and an "LG Electronics Inc" (without the comma) entry. One of them has two Serial Port drivers, and two NMEA GPS Port drivers, the other has three of each. I've at this point tried all five of the Serial Port drivers.
The ones from the group of three (I can't remember if that's the one with the comma or without) required me to reboot my computer when I installed them and then, after the reboot, had a "Device cannot start" on them. The other two managed to start, but when I hit the "Connect" button in the CDMA Workshop it says "Failed to open COMx"... I tried switching around between COM1, COM3, COM5 (making sure to always have the same port selected in both the device manager and the CDMA Workshop)... I tried messing with the baud rate setting, again matching them in both locations.
No go.
I'm doing all of this on two machines, btw... An installation of Windows 7 64 bit running under Parallels Desktop on my Mac, and an install of Windows 7 32 bit running on a friend's computer with no virtualization. Getting identical results on both. Well, I did discover that my friend's computer freezes up mid-POST if my phone is plugged into its USB port while it's rebooting, which was just a little bit of extra frustration to deal with.
Any more hints?
I'd really like to get this working... I've had data outages of several hours almost every day for 2-3 weeks now, usually during prime time usage hours (i.e. around noon, and around 4pm to 7-8pm.) Would love anything that would make the stop or even lessen it.

Wow Kate, ok. Install one of the drivers that is labeled "LGE Android Platform USB Serial Port", I don't think it matters which one. Then make sure no other com ports conflict with the com port you choose. To make sure, restart your computer after changing the port and verify it didn't change. You obviously have debugging enabled on your phone, otherwise the driver wouldn't even appear....Hmmm. I agree that windows makes all of this so much harder than it has to be. The problem with the drivers is a perfect example of how something so simple requires a full days worth of trial and error to fix.
Takenover83 said:
Hmmmm, really? OK... Yes, it was spread out (in one thread, not multiple). But you gave no mention where you obtained the info from. But thanks for cleaning it up, cause it did help a few people get going.
Click to expand...
Click to collapse
Actually, the only part I got from your thread was the procedure to use the Demo version of CDMA workshop to get the MSL code. The rest a pieced together from XDA posts and forums:
http://forum.xda-developers.com/showthread.php?t=940612
http://mark.cdmaforums.com/QPSTSetup.htm
http://www.evanvaughan.com/default.aspx?pageid=56EED25AA49D4B1C
I also didn't use pirated software to get the VM PRL. When you read from the phone using QPST, even though it gives an error, it does download the phone's PRL. You can then save that to a QCN file with the rest of the phone settings. You can then extract the PRL using QPST's Roaming List editor. You should know that the pirated copy of CDMA workshop that is floating around online has been flagged as containing a virus multiple times.
Again, you copied and pasted my entire post and gave no reference to me. I did not complain because this isn't anything besides a walk through.
I'm going to be posting a new PRL soon just for VM users that has all of the roaming features of 60676 removed and adds in the difference from 61007. Feel free to post it in your thread too.

Again, you copied and pasted my entire post and gave no reference to me. I did not complain because this isn't anything besides a walk through.
Click to expand...
Click to collapse
I didn't? Maybe you should go read your post #3 again. You admit to me referencing you. I did mention it and went as far to call it "nice". That is more then you did for me.

Takenover83 said:
I didn't? Maybe you should go read your post #3 again. You admit to me referencing you. I did mention it and went as far to call it "nice". That is more then you did for me.
Click to expand...
Click to collapse
Haha, I'm really not looking for a pissing match, and we both have links to each others threads. So I'm just going to leave it at that.
I posted the new PRL if you want to try it out.

followed your steps and got the same results as kate.
getting extremely frusterated with the process.

HTC One M8 Rooting and S-Off Guide for Newbies (US/International)

Welcome to the HTC One M8 S-Off GUIDE FOR NEWBIES!​
Disclaimer:​I am not responsible for any damage to your phone, in part, or in whole; including bad SD cards, broken reception, bad wifi, Windows 8 being installed, or anything else that could go wrong: Bricking, Bootloops, blips, beeps, boops, or sweeps. You chose to follow these instructions on your own accord and if you do so, agree that I am not liable in anyway, shape or form.
What Models/Carries Should this Work for?
USA: ATT, TMobile
European: Tmobile, VodaFone
I'm unsure if all of this works for Verizon/Sprint versions. You'll have to check the Toolkit's thread and the Firewater thread or official site for confirmation. The above models are just what I've read on the forums)
Credits:
Hansoon2000 for the HTC One Toolkit
Shrimp208 for Minimal ADB and Fastoot
Beups and Fuses for Firewater​.
Ok, so, you want to achieve Root/S-Off and its many benefits. I'm going to walk you through what I did to make this process fairly simple.
Requirements:
HTC One M8
Windows 7, 8, 8.1
No Lockscreen on your phone.
Developer Options Enabled with the following:
1. USB Debugging Enabled
2. Allow Mock Locations (this may not be necessary, but I always do it just in case)
Hint: Don't know how to enable developer options? Go to Settings>About>Software Information>More and tap on "Build Number" 7 times. This will open Developer Options in the Settings menu.
Let's Root!​Use the All-In-One toolkit here:
http://forum.xda-developers.com/showthread.php?t=2699065
Process:
When you open the ToolKit, you'll notice lots of little boxes with text inside. We're going to focus on the box at the very top left that says "To root the phone, follow in order." Fairly simple, right?
First, Download and install HTC Sync Manager and make sure it sees your One M8. Do not use the Install Drivers option from the toolkit, they're outdated/don't work for most people. HTC Sync will install the latest driver for the M8. You can then uninstall the HTC Sync Manager program itself. Link: http://www.htc.com/www/software/htc-sync-manager/
Register at HTCDev. This is needed for this process to gain permaroot at the time I write this. If it doesn't allow you to register, either use a different email address, or ask a friend to do this.
Once logged in, go to "Unlock Bootloader" and Select HTC One (M8) from the drop down list. Follow the steps/prompts and directions on the site.
Get Token ID. Plug your phone in to a USB 2.0 port on your PC (not a hub, not USB3.0, USB 2.0). You should be notified that the HTC One M8 has been plugged in. If so, Proceed. If not, you'll have to figure out the issues you're having with the drivers first.
Two windows will Pop Up. Hit close on the First Window.
The second window should pop up with text. Your token ID is a long series of alpha-numeric text. This is an example of everything you should copy:
{
"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"
}
Note: Copy ALL off that text. From the <<<<Identifier Token Start down to Identifier Token End>>>>
Now, Take that copied text and submit it at HTCDev where it asks you to. If it's successful and you've copied what you need to, an Unlock_Code file will be emailed to you. Download and Place this file in the HTC One Toolkit's Data folder.
Unlcok Bootloader: Again, two windows will pop up, close the first. Your Phone should reboot and the token ID Applied. Your phone will ask you if you want to proceed. Hit Volume Up for "Yes" and Power Button to confirm. This might take a minute, don't freak out.
Flash a Recovery. Once your phone is booted back to the Home screen, go to the far right top window and Select TWRP as the recovery. Select Flash Recovery. Your phone will again pop up with two windows, close the first, and let it do it's thing. Reboot back into the Recovery after this is all done.
Flash Supersu. Go into "Install" in TWRP and select "SuperSu" from the list, swype to begin process.
Congratulations, you should now be rooted!
Time to S-Off!​
WARNING: Not all devices are supported by Firewater. There's really no way to tell until you start running the process to S-Off. If Firewater tells you that your device is not compatible, then it's not compatible. You'll have to wait until Firewater does support your device and is updated.
REQUIRMENTS:
ROOTED HTC ONE M8
ADB and HTC Drivers (htc drivers should be installed from Rooting)
Developer Options Enabled with the following:
1. USB Debugging Enabled
2. Allow Mock Locations (this may not be necessary, but I always do it just in case)
Hint: Don't know how to enable developer options? Go to Settings>About>Software Information>More and tap on "Build Number" 7 times. This will open Developer Options in the Settings menu.
Don't have ADB and don't know where to start? Then download and install MINIMAL ADB AND FASTBOOT:
http://forum.xda-developers.com/showthread.php?t=2317790
Once Downloaded and installed, go to your Start window on the PC and search "ADB". Minimal ADB and Fastboot (here on referred to as ADB) will show up, click on it to bring up a Command Prompt. Using Admin Rights isn't a bad idea either when using ADB.
Go to http://firewater-soff.com/instructions/ And make sure you Follow the Prerequisits to the letter! Read the Instructions for "Rooted, Normal Device Method"
Now that you have the Firewater file, go to Start and Search for ADB, RIGHT CLICK and choose SHOW FILE LOCATION. Drop your Firewater file here. Now we can begin!
Process:
Connect your phone to a USB 2.0 Port if you already haven't and make sure your phone is on the Home screen with NO LOCKSCREEN OF ANY SORT
In the Command Terminal, Type:
adb device (this should show you that your phone is connected. If it says that the phone is inactive/offline, then unplug your phone and replug it. Try again. It should now show up).
Type:
adb Reboot (this will reboot your phone)
After your device has rebooted, there's a 99.9999% chance that it will ":go offline" and not connect to adb (we can confirm this with "adb device" command. Unplug, Replug your phone and ensure it's online and ADB can see it).
Type:
adb wait-for-device push firewater /data/local/tmp
Type:
adb shell
Type:
su
Type:
chmod 755 /data/local/tmp/firewater
Type:
/data/local/tmp/firewater
If you're successful up to this point, Firewater will ask you if you're sure. Type:
Yes
At this point, the Command Prompt will start Chugging bottles of Firewater. Some Command Prompts only Chug One, others, 5,6, up to 12. If you reach 13 Bottles, Abort and try the steps again. This may take a while and several resteps, just be patient. The command prompt, when successful, will notify you that you are now S-Off!
To check this, boot in to Bootloader to confirm (it will say S-Off, not S-On).
The Why:
I believe the reason you need an internet connection is that the Firewater file connects to a server and the voodoo is all done by the server. Why would they do this? Probably to ensure that HTC doesn't screw us out of S-Offing our device like they're known to do by downloading and decompiling files used to S-Off or reverse engineering steps taken to S-Off If anything, this slows them down (and possibly makes it impossible for them to stop us from doing so.)
Special Thanks:
Beups, Fuses, Hasoon2000, and all Developers that are supporting our device with lots of goodies. Don't forget to donate to them to encourage them to spend time on our device, or, just buy them a beverage for all of the hard work and time they spend doing this for us.
If I have forgotten anything or forgot to give credit to someone, please let me know and I'll be sure to add it.

You might want to add that if firewater says your device is not compatible then it means exactly that and you just need to wait for firewater to be updated. There's no pattern to what is and isn't compatible its just luck of the draw and likely down to hardware variances.
Sent from my HTC One_M8 using Tapatalk

stuart0001 said:
You might want to add that if firewater says your device is not compatible then it means exactly that and you just need to wait for firewater to be updated. There's no pattern to what is and isn't compatible its just luck of the draw and likely down to hardware variances.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Ah, yes, you're correct. Thank you!

i'm having a nightmare.
having issues all the way through, seems the htc drivers i get from the toolkit don't install correctly. adb just wouldnt play. i got round that by installing htc sync from phone, that installed correct htc drivers. i then un installed htc sync.
now i've got as far as...
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
3082 KB/s (4519496 bytes in 1.431s)
C:\Program Files (x86)\Minimal ADB and Fastboot>shell
'shell' is not recognized as an internal or external command,
operable program or batch file.
any ideas what i've f'ed up?
---------- Post added at 01:47 AM ---------- Previous post was at 01:39 AM ----------
ok i think it should be adb shell yes?

Yes adb shell
Sent from my HTC One_M8 using xda app-developers app

Learoy1 said:
i'm having a nightmare.
having issues all the way through, seems the htc drivers i get from the toolkit don't install correctly. adb just wouldnt play. i got round that by installing htc sync from phone, that installed correct htc drivers. i then un installed htc sync.
now i've got as far as...
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
3082 KB/s (4519496 bytes in 1.431s)
C:\Program Files (x86)\Minimal ADB and Fastboot>shell
'shell' is not recognized as an internal or external command,
operable program or batch file.
any ideas what i've f'ed up?
---------- Post added at 01:47 AM ---------- Previous post was at 01:39 AM ----------
ok i think it should be adb shell yes?
Click to expand...
Click to collapse
Did you get it all worked out?
Also, I updated the OP to use "adb shell," I apologize, I should have remembered that adb need to be there. As well, I've updated the OP to point to the latest HTC Sync with drivers.

Sorry for the question but it's my first HTC device and I'm studying in deep all the aspects of bootloader, s-off and so on.
What about I need to come back the M8 for warranty?
If I am right I can restore stock rom and recovery and relock the bootloader through s-off. At this point, what about s-off? Is there a way to revert it to stock s-on?

This Rooting method works for the International variant as well right?

Just can't seem to get my device online. I've tried just about everything, restarted phone, laptop, server, different port, different cable, etc. I see a notification that says "Media Device [MTP] connected", and I have an inkling that it could be causing issues, but I can't seem to find a way to disable it. Is anyone else having this issue?
(T-Mobile M8, perma-rooted)
*edit* After several attempts, I seem to have gotten the timing right, using the version of ADB that came with the all in one tool. Somehow it just started to work, but only with that version. Other versions of ADB still saw the device offline. Just one of those annoying things. Either way, I'm now S-OFF. That was the last piece I was missing. Thank you.

Not working!
Have htc one m8 (at&t version) and have tried all the steps but always fails at the end. It saids it wil not work with my device? Don't other people use this with at&t and it works for them? Why doesn't it work for me? Is there another method to s-off? Like from twrp recovery?

patstar5 said:
Have htc one m8 (at&t version) and have tried all the steps but always fails at the end. It saids it wil not work with my device? Don't other people use this with at&t and it works for them? Why doesn't it work for me? Is there another method to s-off? Like from twrp recovery?
Click to expand...
Click to collapse
HTC patched the old S-OFF method, it doesn't work anymore unless you're really lucky to get a device that's before the patch and you don't first update it...
You can try Sunshine S-OFF it's $25 but it seems to do the job right. It actually checks your device for compatibility before you even pay for it, at least that way you won't end up paying for something that "might" not work.
[Android][HTC S-OFF] SunShine for modern HTC devices It's from the same developers of firewater. So far those that did it seems quite happy about it.
Your choice though, it's the only alternative method available.

BerndM14 said:
HTC patched the old S-OFF method, it doesn't work anymore unless you're really lucky to get a device that's before the patch and you don't first update it...
You can try Sunshine S-OFF it's $25 but it seems to do the job right. It actually checks your device for compatibility before you even pay for it, at least that way you won't end up paying for something that "might" not work.
[Android][HTC S-OFF] SunShine for modern HTC devices It's from the same developers of firewater. So far those that did it seems quite happy about it.
Your choice though, it's the only alternative method available.
Click to expand...
Click to collapse
I can't believe I paid $25 but it did work. Wanted to change my software buttons to stock android. Well I guess now I can put other roms on it. If I flash a different custom rom on it, it would be like getting a new phone so I would have to transfer all my data again? Took forever to get apps to restore from helium (carbon) backup and some did not work, really don't want to put custom Rom if it does that again. If I make nandroid backup to internal storage, can I transfer it to my pc for use later on?

patstar5 said:
I can't believe I paid $25 but it did work. Wanted to change my software buttons to stock android. Well I guess now I can put other roms on it. If I flash a different custom rom on it, it would be like getting a new phone so I would have to transfer all my data again? Took forever to get apps to restore from helium (carbon) backup and some did not work, really don't want to put custom Rom if it does that again. If I make nandroid backup to internal storage, can I transfer it to my pc for use later on?
Click to expand...
Click to collapse
Yeah unfortunately if you flash any new ROMs it'll be like a "new" phone like you yourself stated. There will be no apps, nothing. You can back it up and restore with something like Titanium. Even through Google Store it's easy enough if you lock in with the same account again, just reinstall, easy as pie.
Yes if you make a nandroid backup of your device you can store it on your computer for use later on. It's actually advisable to do so, you "might not" find a nandroid backup for your device whilst searching online, so at least if something goes wrong you have a backup on your PC and all is good :good: If only more people would make backups before doing anything though...

BerndM14 said:
Yeah unfortunately if you flash any new ROMs it'll be like a "new" phone like you yourself stated. There will be no apps, nothing. You can back it up and restore with something like Titanium. Even through Google Store it's easy enough if you lock in with the same account again, just reinstall, easy as pie.
Yes if you make a nandroid backup of your device you can store it on your computer for use later on. It's actually advisable to do so, you "might not" find a nandroid backup for your device whilst searching online, so at least if something goes wrong you have a backup on your PC and all is good :good: If only more people would make backups before doing anything though...
Click to expand...
Click to collapse
Titanium backup won't let me backup to sd card, I guess I could backup to internal storage and put it on pc like nandroid or move it to sd card afterwards? I could just download custom rom to my phone, goto twrp and flash it without pc? Is there any dual boot method of roms? I know for m7 there was something that let you switch from sense to stock android with press of button.

Lost & Puzzled Newbie
Hi Guys,
I'm hoping someone can help me out here because I've ben sat in front of my pc for 16 hours straight through the night & I now don't appear to be much nearer than when I started!
So, I picked up my new One M8 & having had some success rooting my ASUS TF700T tablet, I decided that I would root my phone before I got started using it properly & wasted time personalising it. Before I get started, I'm currently on Android 4.4.2, Sense 6.0, & software number 1.54.206.10; if you need anything else, let me know.
I did loads of reading first, hence the night sat in front of my pc, & amongst many others, I was following this thread & the instructions here:
http://forum.xda-developers.com/showthread.php?t=2799796
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I was doing really well to begin with & I managed to unlock the bootloader, flash TWRP, & install SuperSU. Then things started to go wrong. I was undecided whether or not to go for S-Off &/or Super CID but I'd read that S-Off might maximise my battery life even more, so I went for it. I only installed the HTC drivers, absolutely no HTC Sync, my USB Debugging was on, Security was off, & Fastboot was disabled. I downloaded Firewater & after discovering that the ADB folder on my pc wasn't just the folder I'd extracted my ADB zip file to, I found the correct ADB folder on my C: drive, dropped Firewater in & plugged my in M8. It's my own fault because normally, when my phone asks, 'do you want me to do this every time?', I say 'no, just once'......but for some unknown reason, once I'd hooked it up & was using the adb command window (Win 8.1), when the message popped up on the M8 about the phone allowing my pc to connect via adb every time, I, apparently stupidly, said yes.
What happened then was that the adb console, would recognise my phone, so when I typed 'adb device' (or whatever the instruction was), it gave me a page of all sorts of details but then every time I typed 'adb reboot', I got a message saying that the device was offline. If I typed 'adb device' again, I'd get the same page of data & I could see the phone in explorer, so I'm sure the drivers are there, but I also got the same message asking for the reboot.
I've spent hours trying to sort this out & if I'm honest, I got a bit lost (I'm normally quite good at problem solving but I don't suppose it helped not having slept for almost 30 hours now). Anyway, I remembered with my tablet that I just went into TWRP & flashed the 'CHROMi X' ROM from there & by this time, I just wanted to try to get things finished, so because I was most familiar with CyanogenMod, I downloaded it on the pc, transferred it to the phone & tried to flash it I thought I'd read that I neded the ClockworkMod bootloader but I was kind've hoping that TWRP would do the job......it didn't & just failed!
Then my problems really started because the phone went into a boot loop, staying on for only about 10-20 seconds after it booted up. Obviously, by this point I was quite worried that I was about to wreck my shiny new phone but I did some more reading & saw that for someone else, SuperSU had caused this, so I booted back to TWRP, wiped the Dalvik cache & re-flashed SuperSU. Thankfully, that stopped the boot loop
However, I now seem unable to access TWRP? When I hold down the volume down & power buttons, the phone just boots straight through to Android? SuperSU is still installed & it opens up fine (albeit with no apps logged) but it seems like now, the phone might not be unlocked, &/or rooted, or both, though that doesn't seem to make sense to me if SuperSU still runs?
EDIT: I've just tried deleting a folder on the external micro SD card using ES File Explorer & the 'operation failed', so it looks SuperSU, although it asked if I wanted to grant/deny the relevant permissions, isn't working. On 2nd attempt, it worked, so I'm still lost!
EDIT: Fastboot had sneaked back on, so I've switched it back off & I'm back into the bootloader, which says 'Tampered' & 'Unlocked' at the top, & I can boot into TWRP to make the backup of what I've got now that I wanted to make earlier
ANOTHER EDIT: I've now backed up the stock ROM with TWRP & downloaded a root checker app, so I now know that I'm still unlocked & rooted Now I could just do with some help deciding what ROM to install & help on how to go about it.....please
EDIT: After all that, I couldn't sleep, so I didn't try & I stayed up & have managed to sort it. I've got Android Revolution HD on for now but I think I'm correct in thinking that I'll be able to change to another ROM at a later date if I don't like this one? I was going to delete all this, so that people didn't think I was an idiot but it might prove useful to someone else, if only to prove that you probably shouldn't miss a night's sleep because you're trying to root your new phone!!!!
I hope all that makes sense to someone else though? All I wanted to do was get rid of all the O2 bloatware, & most of all, actually be able to write to my external micro SD card, without having to take it out of the phone constantly, so I wanted to install a custom ROM that would be as good as CHROMi X is on my tablet!! but as I said at the beginning, I now feel completely lost & unwilling to start trying again until I know what's happening/has happened.........oh, & I need some sleep!!
If anyone can help get me back on track again, I'd really appreciate it because I really have put the effort in & I don't normally give up but I'm worried that if I keep at it now, I'll end up bricking my phone!! I do want to get this sorted out & enjoy this amazing device for the next couple of years, so any advice on where to start next, which ROM I should use (at this point, I'm easy), or whatever, like I said, I'd really appreciate it
p.s. I didn't mention but once I've sorted my phone out, my girlfriend wants me to sort her HTC One Mini 2 out because she wants to be able to use her external micro SD card too!!

delete

Help rooting G3

Recently got a G3 with Verizon. Running Lollipop 5.0.1. I've done quite a bit of reading about rooting, and understand the concept. Decided to try rooting my phone. I followed the guide here:
http://forum.xda-developers.com/log...de-root-lg-firmwares-kitkat-lollipop-t3056951
I attempted to root my phone several times, on three different PC's each running Windows 7. The farthest I ever get is a 90% complete status where the GUI says "Rooting phone" and the phone says "downloading firmware." I've left it in this state for upwards of 10 minutes and I always end up having to pull the usb and remove the battery in my phone in order to restart it. Upon pulling the USB the GUI will immediately show it had completed the root but when I test for super user status (with Terminal Emulator "su" entry) it says "not found."
USB debugging is enabled. I have tried switching between MTP and PTP connections. I have tried several different USB ports on each machine I attempted this. I tried it by first manually installing the LG drivers on the computer as well as by letting Windows automatically install them. I have tried with the box that says to always allow connections from the computer checked as well as unchecked. I tried versions 1.3 and 1.2 of the script. With version 1.2 it seemed like it finished and it prompted me to push control+c followed by N and enter or something and then the command window closed, but the phone was not rooted.
What am I missing?
I'd really like to get this phone rooted as I am excited to create a recovery and experiment with custom ROM's.
Any ideas are appreciated. Thanks!

The link you provided is to the XDA Forums homepage. The correct link is...
[Guide]LG One Click Root - root LG firmwares (KitKat / Lollipop)
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
The method you'll want to use for LP is located here...
[GUIDE][ROOT] Newest Root Method for LG devices
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
If the 1st method (one-click script) doesn't work for, the 2nd method using the classic way will. Download and extract the "New_LG_Root_v0.1_by_dig.zip" file from the OP, then open an elevated command prompt from within the directory you extracted the files to.

Thanks
I thought I fixed that link. Oh well. Glad to see there's a new method. I will try this. Thanks!

This worked by the way. Thanks again!

{GUIDE} {MSL/SPC UNLOCK} -->>Diag Mode: Use QPST - QXDM to Backup & Restore NV Memory

{GUIDE} {MSL/SPC UNLOCK} -->>Diag Mode: Use QPST - QXDM to Backup & Restore NV Memory
I know everyone is eager to unlock the Verizon Boot-Loader.
We are not quite there yet however this is another step in the right direction.
We are getting deeper and deeper into this so be FOR-WARNED.
If you decide to play around with these tools you do so at your own risk :crying:
I will help anyone who kills there device But I TAKE NO RESPONSIBILITY.
------------------------------------------------------------------------------------------------------------------------------
Follow my instructions exactly and everything will be ok
------------------------------------------------------------------------------------------------------------------------------
Lets Get Started Shall We :highfive:
PREREQUISITES
The ability to follow each step in order :good:
ADB installed ( Android Studio )
Install HTC Sync from the link below. Then uninstall it. This will load and leave the drivers.
Make sure you uninstall it. HTC Sync will interfere.
http://www.htc.com/us/support/software/htc-sync-manager.aspx
STEP 1)
Set Windows 7 or 8 or 10 into TEST MODE ! ( I Am Running Windows 10 )
You can read up on this process here if you have trouble with my instructions.
http://www.drivethelife.com/windows...e-enforcement-on-windows-10-8-7-xp-vista.html
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
You’ll need to run a command from an Administrator Command Prompt to do this. To launch one, right-click the Start button or press Windows+X and select “Command Prompt (Admin)”.
Execute This Command
Code:
bcdedit /set testsigning on
If you did it correct you should see the following.
{
"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"
}
Reboot your computer.
If you did it correct you should see the following.
STEP 2) Install the Diag Driver in Windows.
Download the DIAG.zip here. It contains all of the files we need to work with at this point.
Code:
http://www.mediafire.com/file/3ta2ua4tkibn3lb/DIAG%282%29.zip
Unzip the file and install the drivers.
There are 2 drivers. 1 for diagnostic mode and one for Emergency Download Mode.
HTC CDMA LTE DIAG Modem Driver v3.0.2.0 (Diagnostic Driver)
Qualcomm_Diag_QD_Loader_2016_driver (Emergency Download Driver)
When you install the Qualcomm_Diag_QD_Loader_2016_driver you will want your screen to look like this.
The Diagnostic Driver install is pretty self explanatory.
I,m going to leave this section for setup details. More could be added later.
In the next post we will install the tools we need and get the phone connected in diagnostic mode.
Also please see here
https://forum.xda-developers.com/desire-626/general/programming-modem-qpst-qxdm-boost-t3488993 @anthonykb deserves the credit for originally leading me to this idea.
We are using the process for different purpose but it all stems from the same idea.
REMEMBER THE DESIRE 526 AND THE DESIRE 626S AND THE DESIRE 530 ALL HAVE THE SAME CHIPSET.
What works for one of these devices should theoretically work on the others.

Checking Drivers + Setup Tools
I think it's time for us to set up some tools and see if our drivers are installed correctly.
There are 3 tools included in the zip.
QPST.2.7.438 ( Just install it. There is nothing special to do )
QXDM Pro 3.14.594 ( Read IMPORTANT text in the patch folder and follow the instructions )
RevSkills V 2.08.6 Pro Edition (Read the readme file)
Install all 3 and proceed to the next step
Set The device into DIAGNOSTIC MODE
My device is already s-off and unlocked. So this might take an extra step for you.
First try this.
Open up the phone dial-er on the phone.
Dial ##3424# and hit send.
I tested this on a fully locked 526 so you will get the DIAG Screen.
You should see this screen.
IF ##3424# isn't giving you that screen you will need the extra step
This might not be 100% necessary BUT I RECOMMEND IT
First you will have to get temp root.
Follow here. It will give you root in the shell only. Not root for apps.
https://forum.xda-developers.com/desire-526/general/temp-root100-how-to-temp-root-desire-t3498969
*********************************************************************************************************
ONCE YOU HAVE ROOT ACCESS
Open up a administrator command window.
Execute these commands in the shell.
Code:
adb devices
adb shell
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
*********************************************************************************************************
IF YOU CAN'T GET ROOT THIS SHOULD STILL WORK !!
*********************************************************************************************************
Verify the Diagnostic Port is Available (ALL DRIVERS WORKING)
Open up the phone dial-er on the phone.
Dial ##3424# and hit send.
Connect the device to the computer.
Open up windows device manager.
With all nessessary drivers installed this is what you should see. :highfive:
If you didn't install and uninstall HTC Sync it will look like this
Some things work but this isn't right. DONT DO IT
The HTC Drivers and Diag Drivers are missing. REALLY DONT DO THIS

Time to do some Work
Lets fire up some tools and get down to business.
Go to QPST and open QPST Configuration
If you are greeted with this screen you are good to go.
Now minimize QPST Configuration
Open RevSkills ( Run as Administrator )
Click on Hardware then Port-Utils then click QC + AT-Cmd
You should see the same port you saw in QPST Config
Now Click On HTC : Unlock SPC
Then Click Change SPC
Then Click Send SPC
Then Click Send SP
You Should be good to go. If you got no errors in revskills.
You will notice there are a lot of READ buttons in Revskills.
You can Explore these if you want. It's a way to read the device.
DO NOT EVER HIT A WRITE BUTTON.
Unless you know why your doing it.
You could kill your device beyond repair.
Anyway if you followed this correctly you now know what you MSL/SPC is.
SPC=000000
Since we know that we can now use the QPST Tools.
more to come.......to be continued..........:crying:

Backup the entire nv ram
Ok lets get too it. Here we will backup the entire NV Ram.
After it is dumped to a file I believe the file can be edited.
It is easy to restore the backup to the device.
Lets get started.
#1) Dial ##3424# then send to get to diagnostic mode.
#2) Open QPST Configuration
#3) You Should See This Screen
#4) In QPST Configuration Click START CLIENTS ( EFS EXPLORER)
Select your device under phone selection
#5)EFS EXPLORER Reads the device
#6)The NV Items Look Like This
Notice the red circle ( We cant access those )
But we can fix NVM to get access using open sesame door
#7)Click File Then NEW then Directory
#7)Add open sesame door
Now reboot the device.
Dial ##3424# again.
Then open QPST Configuration and EFS Explorer again.
Make sure you have the open sesame door folder
Notice NVM is no longe a red circle. ITS UNLOCKED.
After reboot and restart qpst it should look like this.
OK were all done with that part. ( OPEN SESAME DOOR )
Lets dump our Embedded File System now.
Close the EFS File Explorer.
Go to the QPST Configuration and Start Clients -->>> Software Download.
Notice the MPSS Version ---->>>> This tells us what version of Source to USE.
#8)Click The BackupTab
On the backup tab where it says xQCNFile select a a location and name for the file.
#9)Click Start To make the backup.
Pay attention to all the files it creates.
Look at the images below.
TO FLASH A BACKUP EFS FILE
#9)Now Go To the Restore Tab
Select the backup file you want to restore.
Make sure Allow phone/file ESN mismatch is NOT Checked.
The backup you flash has to be from the device you created it from.
Or the backup file will need the ESN Edited to match your device. (DANGEROUS)
I need to find a way to use the ESN mismatch but right now it gives error.
Anyway lets flash our backup.
Select the file.
Click Start.
Restoring NV Memory
Restoring NV ITEM FILES
Restoring BREW FILES
Restoring COMPLETE
So there you have it. We can indeed use the QPST / QXDM tools to communicate and flash the device.
THIS BACKUP IS IMPORTANT.
IF YOU BRICK YOUR PHONE. YOU COULD NEED THIS BACKUP TO RESTORE IT COMPLETELY.
WE CAN EDIT THE BACKUP FILE USING A HEX EDITOR OR THE TOOL I WILL TALK ABOUT NEXT.
In light of all this Someone Who Knows What to Changecould help reduce the device security and help us to further customize the device.
Unfortunately this is fairly new to me so I DONT Know the best things to change.
Best I can think of is to compare the backup from my fully unlocked device. ( S-Off / Super CID )
Against the backup from a factory LOCKED State.
Make any necessary changes to the Locked NV Backup.
Know that the wrong mistake here will brick your device for sure.
Feel free to explore the tools and things that can be accomplished with them.
I recommend highly....DONT CHANGE ANYTHING UNLESS YOU KNOW WHAT YOUR DOING.
Hitting some of the buttons in the tools can be dangerous.
Have Fun. The best thing is this device cost only $34.
So it's perfect for learning these tools and testing.
Then when you do this on your expensive device.
You won't brick it.

GREAT!!
Please make a rom to global GSMcard for connection data,

Wow, I am a newbie and when I seen all these instructions I almost gave up before I started. I can proudly say I successfully completed this tutorial. Does this mean my bootloader is now unlocked? What do I need to do next to root this thing. Once again, please forgive my ignorance, like I said this is all new to me.
I just went in to recovery mode and it still says locked. ???

@blahforme
I'm glad everything worked for you.
I try to write my guides so everyone can follow and get good results.
Unfortunately this is not a boot loader unlock.
So you can't root yet.
But you do have a backup of your NV Memory and you learned something.
Plus you have the drivers and whatnot installed.
So it was worth the effort.
I have build a device image that if it can be flashed will allow you to unlock the boot loader.
I'm working on the flashing part.
The rom build is here and you can learn a whole lot about htc devices in this thread.
Really it's not for a new bee so don't be surprised when you see the complexity of things.
https://forum.xda-developers.com/de...-rom-msm8909-service-rom-source-qpst-t3544178
As soon as i have a way to unlock the boot loader you will all know. Hopefully soon.

BigCountry907 said:
Lets fire up some tools and get down to business.
Go to QPST and open QPST Configuration
If you are greeted with this screen you are good to go.
Now minimize QPST Configuration
Open RevSkills ( Run as Administrator )
Click on Hardware then Port-Utils then click QC + AT-Cmd
You should see the same port you saw in QPST Config
Now Click On HTC : Unlock SPC
Then Click Change SPC
Then Click Send SPC
Then Click Send SP
You Should be good to go. If you got no errors in revskills.
You will notice there are a lot of READ buttons in Revskills.
You can Explore these if you want. It's a way to read the device.
DO NOT EVER HIT A WRITE BUTTON.
Unless you know why your doing it.
You could kill your device beyond repair.
Anyway if you followed this correctly you now know what you MSL/SPC is.
SPC=000000
Since we know that we can now use the QPST Tools.
more to come.......to be continued..........:crying:
Click to expand...
Click to collapse
Hi @BigCountry907,
First and foremost, thank you for all of your hard work on the MSM8909 chipset. I've found your many posts to be extremely enlightening! I plan to attempt building your AOSP kernel at some point soon on my Desire 626s; I just need to setup my Linux dev box. I realize this is now an older device, but I'm enjoying learning & getting close to the metal on this one.
Pertaining to these instructions, I am encountering an issue and wanted to see if you might have any ideas.
Have QXDM drivers properly installed; diag port enabled via adb; QPST recognizes the phone (although ESN is blank). As I attempt RevSkills, HTC Unlock SPC = success "Done sending SuperSPC." As I click "Change SPC", I receive "Error writing NV value". However, after several attempts at it, I finally get success. Send SPC = I get a return "41 01 ¶ A" and after "Send SP" get a return of "46 01 ¶ F". I'm going to assume these are successful.
The issue presents itself when I enter ##3424# (DM Command- after writing SPC). It prompts me to enter the MSL. I attempt 000000 and the phone will either: reboot or will say incorrect MSL (and will not allow me into the menu). I'm unable to access DM Command.
While I've already enabled the diag port, I am interested in sending AT commands and going further into using qcdiag to monitor gsm/3g/lte packets. As I understand it, I need to enable serial com in order to send AT commands to the modem. I'd like to get my KC and use rtl-sdr to sniff and decrypt my own traffic to better understand... Currently, as I attempt Putty on COM3 (valid diag port) unable to connect.
To give some supporting information, I am using a Cricket Wireless Desire 626s device unlocked on Marshmallow 2.27.651.6 T-Mobile network (Sprint debloated ROM as Cricket did not update to MM). However, I've attempted this after using the Cricket RUU as well as a few other custom ROMs w/o success.
I've also looked into QXDM - NV Browser - Item 0085 after a supposedly successful SPC write, and get the return "No DIAG Response Received". I've tried to pack as much pertinent info into these screenshots as possible.
Ultimately, I'm interested in getting to packet level data using qxdm, and am hoping you might help steer me a bit. Osmo-qcdiag has some really cool stuff they are working towards and I'd like to use this device. Also, if you happen to have an idea of the NV values to open up additional 3g & LTE bands- that would be super helpful! (I'm on T-Mobile network currently).
Thank you so very much for all of your hard work on this device.
FYI, unfortunately unable to post my image as I"m a "new" member. However,
imgur . com /a / ZiuXP

Running console over adblink

I'm totally new to this, and I'm having trouble finding the info I need, sorry for the basic questions here.
I got my Toshiba Edition Fire TV connected via abdlink via the IP address.
Once it connects, the 'Enable USB Debugging' window pops up on the TV, which I authorize. adblink tells me it's unauthorized and to click 'refresh adb', so I do.
It seems to be functioning and the TV is listed under connected devices, but when I try to open the console, it pops up and immediately closes. If I try to run the abd shell, the console pops up but I can't type anything into it. All of the other functions seem to be working.
I'm trying to disable the banner ads using the command lines found on the forum here in one of the threads. I don't have Kodi installed yet, is that necessary to use the command console? I haven't downloaded anything else, all I have is abdlink, do I need the developer sdk installed or anything else aside from adblink?
Thanks, any help is very much appreciated, I know this is basic stuff. Even more basic, do I install the 32bit apk or the 64bit kodi apk?

I would try a reboot of PC and TV since initial connection. If you store the IP in adblink and make that first connection, allowed on TV it should store that and not have to again (that's how it is on my ftv box). Then try running adblink as admin before connecting.
As for Kodi, install 64bit. If it successfully installs than you have 64bit chip/OS. If it gets parsing error it means you don't... Install 32bit.
Sent from my Mi A1 using Tapatalk

pontiffholychurch said:
I'm totally new to this, and I'm having trouble finding the info I need, sorry for the basic questions here.
I got my Toshiba Edition Fire TV connected via abdlink via the IP address.
Once it connects, the 'Enable USB Debugging' window pops up on the TV, which I authorize. adblink tells me it's unauthorized and to click 'refresh adb', so I do.
It seems to be functioning and the TV is listed under connected devices, but when I try to open the console, it pops up and immediately closes. If I try to run the abd shell, the console pops up but I can't type anything into it. All of the other functions seem to be working.
I'm trying to disable the banner ads using the command lines found on the forum here in one of the threads. I don't have Kodi installed yet, is that necessary to use the command console? I haven't downloaded anything else, all I have is abdlink, do I need the developer sdk installed or anything else aside from adblink?
Click to expand...
Click to collapse
It's a bug.
https://forum.xda-developers.com/showpost.php?p=78279023&postcount=289
Use adblink 3.6 instead.
jocala does great work, but sometimes it's hard to catch everything.

2WhlWzrd said:
It's a bug.
https://forum.xda-developers.com/showpost.php?p=78279023&postcount=289
Use adblink 3.6 instead.
jocala does great work, but sometimes it's hard to catch everything.
Click to expand...
Click to collapse
Well dang. ADB3.6 doesn't seem to be able to identify my TV like 3.7 did unless I'm doing something wrong now.
Even after a system restore it just tells me it can't connect

pontiffholychurch said:
Well dang. ADB3.6 doesn't seem to be able to identify my TV like 3.7 did unless I'm doing something wrong now.
Even after a system restore it just tells me it can't connect
Click to expand...
Click to collapse
adbLink 3.9 has just been released, and the previous bugs have been fixed.

2WhlWzrd said:
has just been released, and the previous bugs have been fixed.
Click to expand...
Click to collapse
Could I ask you, is Fire TV able to access my Windows 7 shares? I have it set up on Windows, but no Fire TV apps find the shares, I can't find any way to do it... Thanks.
Also when I try to use remote manager from ES Explorer, Windows tells me it cannot access the files and to make sure I have permissions.

Edit nevermind ADB works now.