Develop Bugs

Broke My Sprint Touch

Hello,
I saw on the htc site that an update for the Sprint HTC touch was available so i downloaded it and tried to load it on my phone.
It took a few tries to get it to connect and when it finally did it said there was an invalid command.
I thought it was because i upgraded my phone earlier to the titan rom and radio to get gps and rev a so i put it back to the factory settings.
Everything was normal.
I then tried the official htc software update again and it worked until it got to 10% and it said invalid command again and exited.
It is now stuck on the boot load screen and remains that way after numerous soft/hard resets.

To "unbrick" your phone, follow the steps in this thread:
http://forum.ppcgeeks.com/showthread.php?t=24906
In a nutshell:
You'll have to revert back to your carrier's ROM (by carrier, I mean a genuine, signed ROM) by extracting the ROM's exe file and renaming the .nbh file inside the archive to VOGUIMG.nbh.
Then, remove your Micro SD card and use a card reader** to put that file into the root - ensure that the card is formatted as FAT32 and that the card is not an SDHC (meaning any card that is 4GB+().
**card reader or any other device that has a microSD slot that operates as a USB mass storage device - I did the same procedure with an MP3 player... **
Insert the card and reboot the phone, it should go into the bootloader and update automatically.
Good luck

If you can get to the boot screen, chances are it is not bricked
Just download the original ROM and flash to that. Make sure to NOT use a virtual machine! You can only run the .EXE file in Windows XP natively, not in software such as Parallels or VM Ware.

TGHI said:
To "unbrick" your phone, follow the steps in this thread:
http://forum.ppcgeeks.com/showthread.php?t=24906
In a nutshell:
You'll have to revert back to your carrier's ROM (by carrier, I mean a genuine, signed ROM) by extracting the ROM's exe file and renaming the .nbh file inside the archive to VOGUIMG.nbh.
Then, remove your Micro SD card and use a card reader** to put that file into the root - ensure that the card is formatted as FAT32 and that the card is not an SDHC (meaning any card that is 4GB+().
**card reader or any other device that has a microSD slot that operates as a USB mass storage device - I did the same procedure with an MP3 player... **
Insert the card and reboot the phone, it should go into the bootloader and update automatically.
Good luck
Click to expand...
Click to collapse
I tried this maybe 5 times and i keep getting a communication error!

bpack428 said:
I tried this maybe 5 times and i keep getting a communication error!
Click to expand...
Click to collapse
If you are getting a communication error while trying to flash from the sd card, you've got some very serious problems. More than likely, if you are flashing from sd and get an error, it is probably not a communications error.
What letters are on the three-color boot-loader screen?
Best regards,
-boggsie

boggsie said:
If you are getting a communication error while trying to flash from the sd card, you've got some very serious problems. More than likely, if you are flashing from sd and get an error, it is probably not a communications error.
What letters are on the three-color boot-loader screen?
Best regards,
-boggsie
Click to expand...
Click to collapse
VOGU100 MFG
SPL-2.01.1000
CPLD-3
in the top right corner it says RUUNBH
bottom it says serial

I think im going to play dumb and get a new phone from sprint.

bpack428 said:
I think im going to play dumb and get a new phone from sprint.
Click to expand...
Click to collapse
This is a pretty simple fix. You need to stick your MicroSD card into your PC via card reader. Format the card to fat32. Re-Formating is important because even if your card is already fat 32 sometimes it still won't work until your re-format it. Then copy "any" compatible Vogue RUU file over to your card. Rename the file "VOGUIMG" without the quotes and stick it back into your phone in the root directory.. Hold down the power and camera button and reset the phone with the stylus. Once inside the bootloader follow the instructions on your screen. Reset when you are done and you should be good. THIS IS ASSUMING YOUR PHONE IS ALREADY UNLOCKED. If you go back to Sprint and they see why your phone isn't booting they may not honor your warranty.
GOOD LUCK....

ptfdmedic said:
This is a pretty simple fix. You need to stick your MicroSD card into your PC via card reader. Format the card to fat32. The copy "any" compatible Vogue RUU file over to yourt card. Rename the file "VOGUIMG" without the quotes and stick it back into your phone. Hold down the power and camera button and rested the phone with the stylus. Once inside the bootloader follow the instructions on your screen. Reset when you are done and you should be good. THIS IS ASSUMING YOUR PHONE IS ALREADY UNLOCKED. If you go back to Sprint and they see why your phone isn't booting they may not honor your warranty.
GOOD LUCK....
Click to expand...
Click to collapse
I have done this. It says loading... on my phone and then i try to load RUU_Vogue_SPRINT_WWE_1.12.651.1_2.13.00_SPC_NV133_Ship on my phone from my pc and i get a communication error

bpack428 said:
I have done this. It says loading... on my phone and then i try to load RUU_Vogue_SPRINT_WWE_1.12.651.1_2.13.00_SPC_NV133_Ship on my phone from my pc and i get a communication error
Click to expand...
Click to collapse
Let me clarify. Use any "Compatible" "Custom" Rom. I don't believe the Sprint Release off the HTC site will work with what you are doing. You need a Custom Rom.
I would suggest you visit: http://forum.ppcgeeks.com/forumdisplay.php?f=59
and just pick one and follow the instructions I gave eariler. I don't believe you can do this type of upgrade with the Sprint ROM you need to try with a custom ROM....
MAKE SURE YOUR PHONE IS UNLOCKED....

ptfdmedic said:
Let me clarify. Use any "Compatible" "Custom" Rom. I don't believe the Sprint Release off the HTC site will work with what you are doing. You need a Custom Rom.
I would suggest you visit: http://forum.ppcgeeks.com/forumdisplay.php?f=59
and just pick one and follow the instructions I gave eariler. I don't believe you can do this type of upgrade with the Sprint ROM you need to try with a custom ROM....
MAKE SURE YOUR PHONE IS UNLOCKED....
Click to expand...
Click to collapse
How do i know if my phone is unlocked?
All that i want to do it update it to the official htc rom

bpack428 said:
How do i know if my phone is unlocked?
All that i want to do it update it to the official htc rom
Click to expand...
Click to collapse
Have you ever loaded a custom ROM?... You said you loaded a Titan ROM? I believe you had to have your phone unlocked for that and that was just for the Radio and it was not a full OS flash. So if you did that then hopefully your phone is unlocked.
If your phone is unlocked you will see the following on you bootloader:
VOGU100 MFG
SPL-2.31.Coke
CPLD-3
What do you have listed.
Let me know and maybe I can help.

He posted the information earlier in the thread:
VOGU100 MFG
SPL-2.01.1000
CPLD-3
Click to expand...
Click to collapse
His phone is not unlocked and he cannot get back into Windows Mobile so he cannot unlock it at this point.
His only option is to load the RUU/WWE from Sprint (presuming that is his carrier) as I don't think (I'm probably wrong) that the stock boot loader will flash from sd card.
Best regards,
-boggsie

boggsie said:
He posted the information earlier in the thread:
His phone is not unlocked and he cannot get back into Windows Mobile so he cannot unlock it at this point.
His only option is to load the RUU/WWE from Sprint (presuming that is his carrier) as I don't think (I'm probably wrong) that the stock boot loader will flash from sd card.
Best regards,
-boggsie
Click to expand...
Click to collapse
I have no idea if i can or cannot do that.

boggsie said:
He posted the information earlier in the thread:
His phone is not unlocked and he cannot get back into Windows Mobile so he cannot unlock it at this point.
His only option is to load the RUU/WWE from Sprint (presuming that is his carrier) as I don't think (I'm probably wrong) that the stock boot loader will flash from sd card.
Best regards,
-boggsie
Click to expand...
Click to collapse
Hye Boggsie,
Didn't COKE release a version of his unlocker that was flashable via SD card. I know that I flashed extracted the .nbh from the .exe and renamed it and flashed. It worked but I only did this because I running Vista 64 and couldn't get it to work from Vista. I will look and see if I can remember how I did it. The op said he flashed a titan rom to get the radio or something. I would guess that might play a part in this.
I agree that the Sprint.exe would be his only option but I will see if I can locate what I did. That may also work........
Thanks for the reply...

Here is the link to the 2.31 unlocker: ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker_MFG_2.31.exe
Here is the link to the thread over on PPCGEEKS:
http://forum.ppcgeeks.com/showthread.php?t=20370
What I did was to extract the .nbh and rename it to VOGUIMG. I flashed that from my SD card and unlocked my phone. I don't believe this is a supported method. I don't know how good of an idea it is. But it seems that you have tried everything else already. I would READ the thread VERY CAREFULLY before deciding to try this. I Must be VERY CLEAR. DO THIS AT YOUR OWN RISK. AGAIN READ THE INSTRUCTIONS IN THE THREAD FIRST. I only did this because when I was newer I made a mistake and found myself in a similar position as you. I knew my phone was dead and figured I had nothing left to lose. I take no responsibility for this as I am sharing information that I have from my own experience. I don't think that this is really suppossed to work but it did for me. It has been a while since I fixed mine, and I have flashed to many times to remember. So I am reasonably sure this is what I did.
Good Luck......
Update:
Read this thread:
http://forum.ppcgeeks.com/showthread.php?t=24906
This should help you fix this.
UPDATE 2:
Rename the .nbh to VOGUIMG not VOGUIMG.nbh the .nbh is the file extension and not part of the renaming process. If you include .nbh in the name it will not work.....
OK. GOOD LUCK

ptfdmedic said:
Hye Boggsie,
Didn't COKE release a version of his unlocker that was flashable via SD card. I know that I flashed extracted the .nbh from the .exe and renamed it and flashed. It worked but I only did this because I running Vista 64 and couldn't get it to work from Vista. I will look and see if I can remember how I did it. The op said he flashed a titan rom to get the radio or something. I would guess that might play a part in this.
I agree that the Sprint.exe would be his only option but I will see if I can locate what I did. That may also work........
Thanks for the reply...
Click to expand...
Click to collapse
He did, but only for the Titan or Kaiser ... probably the Titan.
AFAIK, he doesn't have a replacement Vogue, yet.
Best regards,
-boggsie

boggsie said:
He did, but only for the Titan or Kaiser ... probably the Titan.
AFAIK, he doesn't have a replacement Vogue, yet.
Best regards,
-boggsie
Click to expand...
Click to collapse
Hey I took the plunge.
I relocked and and then unlocked right from my sd card. It does work. Only recommended if there is no other way. But it does work. It is just like flashing a custom rom from your sd card but it only takes a few seconds.....

ptfdmedic said:
Hey I took the plunge.
I relocked and and then unlocked right from my sd card. It does work. Only recommended if there is no other way. But it does work. It is just like flashing a custom rom from your sd card but it only takes a few seconds.....
Click to expand...
Click to collapse
Wow ... a bit of a gutsy move; yours are bigger than mine, my friend.
Although, I wonder why / how it works? I mean, flashing a bootloader from SD is facilitated through the existing bootloader. So the existing bootloader is being overwrittern by the new bootloader, but the existing bootloader is performing the write / update process, so how can it possibly be overwritten?
This is why the bootloader process from the pc needs activesync; so that a temporary bootloader can be run in memory and then used to write the new bootloader over top of the existing one.
Oh well, who cares why I can't understand it ... it works. Good find!
Best regards,
-boggsie

boggsie said:
Wow ... a bit of a gutsy move; yours are bigger than mine, my friend.
Although, I wonder why / how it works? I mean, flashing a bootloader from SD is facilitated through the existing bootloader. So the existing bootloader is being overwrittern by the new bootloader, but the existing bootloader is performing the write / update process, so how can it possibly be overwritten?
This is why the bootloader process from the pc needs activesync; so that a temporary bootloader can be run in memory and then used to write the new bootloader over top of the existing one.
Oh well, who cares why I can't understand it ... it works. Good find!
Best regards,
-boggsie
Click to expand...
Click to collapse
Boggsie,
Check out this thread. It explains it all.
http://forum.ppcgeeks.com/showthread.php?t=24906
I agree it shouldn't work. But it does. Coke says it should be a last resort. But is actually works....

Issue with Unbrick guide(method)

Hi there guys searched around and relaly dont see a similiar problem I am having and any help would be appreciated. So I flashed the ics leak forthe unrooted v ersion of my att&t nitro that worked fine(its the exact same one as hono's but for unrooted roms) Anyways now that att official is coming out I wish to downgrade back to a stock rom so it will update to official. problem is during the unbrick method as its at some points in broken english(not a dis) just saying can get a bit confusing.
So I get to the step where the lg tool is updating and reboots phone and phone is back on and we are at about 93 percent that the problem occurs. the program(lg tool) says that there is a problem with the usb connection to the phone communicating please pull out usb remove battery and turn phone back on and hit restart ive tried that and still gets to same point to eventually program gives up and say exit.
ive reinstalled teh shttp server and all the tools redownloaded the linked kdz file etc...cant i just flash the official att rom since im not actually bricked. or is it better to dowgrade and redo it how i am trying to do now. Any hlep is appreciated seems as newer phones come out things get more confusing then easier

talrune said:
Hi there guys searched around and relaly dont see a similiar problem I am having and any help would be appreciated. So I flashed the ics leak forthe unrooted v ersion of my att&t nitro that worked fine(its the exact same one as hono's but for unrooted roms) Anyways now that att official is coming out I wish to downgrade back to a stock rom so it will update to official. problem is during the unbrick method as its at some points in broken english(not a dis) just saying can get a bit confusing.
So I get to the step where the lg tool is updating and reboots phone and phone is back on and we are at about 93 percent that the problem occurs. the program(lg tool) says that there is a problem with the usb connection to the phone communicating please pull out usb remove battery and turn phone back on and hit restart ive tried that and still gets to same point to eventually program gives up and say exit.
ive reinstalled teh shttp server and all the tools redownloaded the linked kdz file etc...cant i just flash the official att rom since im not actually bricked. or is it better to dowgrade and redo it how i am trying to do now. Any hlep is appreciated seems as newer phones come out things get more confusing then easier
Click to expand...
Click to collapse
i recommend you to use the original data cable that came alongwith the phone package and the usb ports at the back of the pc !
do this and try again !

yeah I am using the data cable that came with it and using the usb ports on back of pc. also i assume I cannot access the adb commands via the command line if phone isnt rooted correct? because i have t ried but thats a no go but as i said i assume thats because im not rooted.

You shouldn't have any reason to downgrade. You should just be able to use the LG tool to install the new ICS version when it "officially" comes out without any fuss.
If you want to install it right away (but slightly more difficult method), then follow the unbricking guide but use the new AT&T KDZ file instead of the one listed in the guide. And stop after it flashes that because you're done.

ok i assume the new att kdz is on this forum so i will look for it and give it a go i know the link hono had up yesterday for official attv20 was dead link.

oh another question when ya luanch the R&D test tool(UpTestEX_mod2_marwin.exe ) for select type do i leave it at cdma? and for phone mode leave it in diag? or should it be in emergency or cs_emergency that is not listed in the guide

ok got it to work i had to block the 127.0.0.1 lgmobile line in host and rebooted computer and pointed model dll on the R&D tool to the one in kd folder and then used the v20 official att ics and slet it stay on korean as country but chose english as language,thanks for hte help.

SIM no longer recognized as being inserted; IMEI not visible in software

Firstly, my apologies if this issue has been solved before here, but neither a search of the forum nor the automatically found "similar threads" based on the title have revealed such a problem as this.
Last night, I attempted (and eventually succeeded) at reverting my SGH-I747 to the stock 4.1.1 ROM, with the intention of subsequently installing the 4.3 and 4.4 OTAs. However, I was unable to do this because the phone behaved as though no SIM had been inserted, despite the fact that one had. At various points throughout today, I've performed factory resets, re-flashed the 4.1.1 ROM, and gone back to CM11 (under which my cellular connection had been fully functional up until last night), all with no results. My next thought was that the SIM card itself had somehow broken*, so I looked through AT&T's process for ordering a new SIM. However, I am unable to view the phones IMEI (which is required for such ordering) through software. Obviously, I could just pull out the battery and look at the IMEI there, but I worry that the lack of ability to view it in software is indicitave of some sort of problem with the phone.
My main concern is, is this a problem that I can easily solve? Or have I irrevocably screwed up my phone's SIM slot (or some other piece of related hardware) which I need to replace in order to recieve mobile communication?
Any help much appreciated.
*Before anyone asks, I am unable to test the SIM in a different device, as neither I nor anyone I know has a device on AT&T with a micro-SIM slot whose phone I can borrow for that purpose.

dhmmjoph said:
Firstly, my apologies if this issue has been solved before here, but neither a search of the forum nor the automatically found "similar threads" based on the title have revealed such a problem as this.
Last night, I attempted (and eventually succeeded) at reverting my SGH-I747 to the stock 4.1.1 ROM, with the intention of subsequently installing the 4.3 and 4.4 OTAs. However, I was unable to do this because the phone behaved as though no SIM had been inserted, despite the fact that one had. At various points throughout today, I've performed factory resets, re-flashed the 4.1.1 ROM, and gone back to CM11 (under which my cellular connection had been fully functional up until last night), all with no results. My next thought was that the SIM card itself had somehow broken*, so I looked through AT&T's process for ordering a new SIM. However, I am unable to view the phones IMEI (which is required for such ordering) through software. Obviously, I could just pull out the battery and look at the IMEI there, but I worry that the lack of ability to view it in software is indicitave of some sort of problem with the phone.
My main concern is, is this a problem that I can easily solve? Or have I irrevocably screwed up my phone's SIM slot (or some other piece of related hardware) which I need to replace in order to recieve mobile communication?
Any help much appreciated.
*Before anyone asks, I am unable to test the SIM in a different device, as neither I nor anyone I know has a device on AT&T with a micro-SIM slot whose phone I can borrow for that purpose.
Click to expand...
Click to collapse
You're quite lucky you didn't brick your phone downgrading like that.
You're gonna need nv-reader/write to get your IMEI back.. Look here.

BWolf56 said:
You're quite lucky you didn't brick your phone downgrading like that.
You're gonna need nv-reader/write to get your IMEI back.. Look here.
Click to expand...
Click to collapse
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?

dhmmjoph said:
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?
Click to expand...
Click to collapse
No, sorry. And I doubt you'll find one.

dhmmjoph said:
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?
Click to expand...
Click to collapse
Before you try the NV re-write, I would suggest you first check to see your modem hasn't been corrupted. Go to settings and see what is showing under Baseband version. If it reads <Unknown>, then you may be able to fix it by flashing the 4.3 MJB modem. I don't know what procedure you used to downgrade from 4.3 to 4.1.1 without hard-bricking your phone. It is indeed possible to downgrade the ROM only without downgrading the bootloader. However, the 4.3 bootloader and modem are in a tight and unbreakable marriage so if you downgrade the ROM and modem, you would end up losing your modem and consequently all cellular functioning even if you didn't up in a hard brick.
If your baseband version is indeed showing as unknown, then you can go to the link below to download the modem and flash via custom recovery ....
http://www.androidfilehost.com/?fid=23212708291680823

Larry2999 said:
Before you try the NV re-write, I would suggest you first check to see your modem hasn't been corrupted. Go to settings and see what is showing under Baseband version. If it reads <Unknown>, then you may be able to fix it by flashing the 4.3 MJB modem. I don't know what procedure you used to downgrade from 4.3 to 4.1.1 without hard-bricking your phone. It is indeed possible to downgrade the ROM only without downgrading the bootloader. However, the 4.3 bootloader and modem are in a tight and unbreakable marriage so if you downgrade the ROM and modem, you would end up losing your modem and consequently all cellular functioning even if you didn't up in a hard brick.
If your baseband version is indeed showing as unknown, then you can go to the link below to download the modem and flash via custom recovery ....
Click to expand...
Click to collapse
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!

dhmmjoph said:
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!
Click to expand...
Click to collapse
You said you moved it to your sd card? You might have to change TWRP's mounting to it.

BWolf56 said:
You said you moved it to your sd card? You might have to change TWRP's mounting to it.
Click to expand...
Click to collapse
I should clarify. I downloaded the file using my laptop, then connected the phone to the laptop, and moved the file to the root of the external SD. Using a file explorer app on the phone, I can see the file in that location, as well as several flashable ZIPs which I've put there in the past. However, when using TWRP to select a file to flash, I can navigate to the root of the external SD and see (and flash, if I wanted to) the other files, but not the .bin, presumably (though it's possible - or likely - that I'm wrong here) because TWRP expects all flashable files to be .ZIPs, and so doesn't display files that don't end in .zip. So, the question is, in order to flash this file, do I need to change the extension to .zip? or flash a different custom recovery? or use some other method for flashing altogether?

dhmmjoph said:
I should clarify. I downloaded the file using my laptop, then connected the phone to the laptop, and moved the file to the root of the external SD. Using a file explorer app on the phone, I can see the file in that location, as well as several flashable ZIPs which I've put there in the past. However, when using TWRP to select a file to flash, I can navigate to the root of the external SD and see (and flash, if I wanted to) the other files, but not the .bin, presumably (though it's possible - or likely - that I'm wrong here) because TWRP expects all flashable files to be .ZIPs, and so doesn't display files that don't end in .zip. So, the question is, in order to flash this file, do I need to change the extension to .zip? or flash a different custom recovery? or use some other method for flashing altogether?
Click to expand...
Click to collapse
I'm not so sure what file you downloaded but it should be a zip. In order to flash, you need a zip with META-INF folder in it (to put it simply).
Here's what you need: http://forum.xda-developers.com/showthread.php?t=1831898 (The MJB one).

dhmmjoph said:
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!
Click to expand...
Click to collapse
The file should be a zip. Just checked the link I sent you and I'm just seeing it's a*.bin file. You could try the one from the link forwarded by BWolf although this appears to be for CWM.
After this, you may also want to see if you won't be better off going to full stock 4.3. I'm not sure the hybrid firmware (4.1.1 ROM with 4.3 Bootloader/Modem) offers any real benefits.

Larry2999 said:
The file should be a zip. Just checked the link I sent you and I'm just seeing it's a*.bin file. You could try the one from the link forwarded by BWolf although this appears to be for CWM.
After this, you may also want to see if you won't be better off going to full stock 4.3. I'm not sure the hybrid firmware (4.1.1 ROM with 4.3 Bootloader/Modem) offers any real benefits.
Click to expand...
Click to collapse
Here's a TWRP flashable zip for the modem if the CWM doesn't work.

HELP! HTC M9 ROM update help

Ok so in the last thread I started I learned how flashing ROMS works, with the matching firmware, CID's, and other stuff, but now I have another issue... The ROM that I was able to flash was the TeamVenom Viper One ROM for Android L (Lolipop)....The ROM version I used was Viper 3.5.0, but now I would like to upgrade to Viper 6.1.0, but it requires Android M (HTC Firmware 3.x).... I do not have a stock ROM to go back to update, and the HTCDev RUU.exe to update gives error code 132 (similar to error code 12, Thanks for the ReadMe page btw @Flippy498), which is a signature error (which is odd because it is straight from HTCDev) and I cannot find a zip file of 3.xx.502.xx to flash that isn't A) corrupted upon download, or B) has a working link... I don't think I can update Viper because it says "Flashing the new Android M firmware is a must, else your phone won’t boot!!" (trust me it doesn't boot, I've tried)... But I read somewhere that having a Team Venom account will allow you to receive OTA updates, yet when I check for OTA updates through the Venom app in the app drawer it doesn't find any available updates, which I know is incorrect because as I said I'm still on Android L (5.1)... What would I need to do from here, how would I A)fix HTC installer, or B) does anybody have a WORKING flashable stock android zip to update from Lollipop to Marshmallow...
Thanks in advanced!
Forum N00b,
qwsderter

qwsderter said:
but now I would like to upgrade to Viper 6.1.0, but it requires Android M (HTC Firmware 3.x)
Click to expand...
Click to collapse
It's actually recommended to use firmware 4.x for Viper 6.1.0 (although the rom boots on 3.x, as well).
qwsderter said:
I do not have a stock ROM to go back to update, and the HTCDev RUU.exe to update gives error code 132 (similar to error code 12, Thanks for the ReadMe page btw @Flippy498), which is a signature error (which is odd because it is straight from HTCDev)
Click to expand...
Click to collapse
It's not odd at all. Re-read the explanation of the error or the RUU section. Both explain why the flash fails.
qwsderter said:
I cannot find a zip file of 3.xx.502.xx to flash that isn't A) corrupted upon download, or B) has a working link
Click to expand...
Click to collapse
I checked the link in the ReadMe thread. It'sworking fine. If the file gets corrupted during the download then it's due to your setup (e.g. an interruption of your internet connection during the download, etc.).
qwsderter said:
But I read somewhere that having a Team Venom account will allow you to receive OTA updates, yet when I check for OTA updates through the Venom app in the app drawer it doesn't find any available updates, which I know is incorrect because as I said I'm still on Android L (5.1)
Click to expand...
Click to collapse
There is no OTA for updating Venom 3.5.0. Custom roms can't update your firmware. Therefore, you need to update it on your own and to flash a full rom whenever the rom's base get's changed. The OTAs only update the rom (e.g. from 3.0.0 to 3.1.0). That's why there isn't an OTA for 6.0.0 -> 6.1.0, either. 6.1.0 is based on a different firmware than 6.0.0. You might want to read the article that is labeled as "The difference between rom and firmware" in the further reading section of the ReadMe thread.

Flippy498 said:
It's actually recommended to use firmware 4.x for Viper 6.1.0 (although the rom boots on 3.x, as well).
It's not odd at all. Re-read the explanation of the error or the RUU section. Both explain why the flash fails.
I checked the link in the ReadMe thread. It'sworking fine. If the file gets corrupted during the download then it's due to your setup (e.g. an interruption of your internet connection during the download, etc.).
There is no OTA for updating Venom 3.5.0. Custom roms can't update your firmware. Therefore, you need to update it on your own and to flash a full rom whenever the rom's base get's changed. The OTAs only update the rom (e.g. from 3.0.0 to 3.1.0). That's why there isn't an OTA for 6.0.0 -> 6.1.0, either. 6.1.0 is based on a different firmware than 6.0.0. You might want to read the article that is labeled as "The difference between rom and firmware" in the further reading section of the ReadMe thread.
Click to expand...
Click to collapse
Hey thanks Flippy you are the clutch, but I can verify that the files ARE corrupt.... I have downloaded it twice, and I have google fiber so I can guarantee that the connection was consistent. Winrar said the file was corrupted, along with when trying to flash TWRP would flash.... Any other ideas, you are the master at this Flippy, there must be another way...

qwsderter said:
Hey thanks Flippy you are the clutch, but I can verify that the files ARE corrupt.... I have downloaded it twice, and I have google fiber so I can guarantee that the connection was consistent. Winrar said the file was corrupted, along with when trying to flash TWRP would flash....
Click to expand...
Click to collapse
You should re-read the ReadMe thread. They're not corrupt. I thought that with "corrupt" you meant the MD5 checksum wouldn't match after the download. That WinRar error message is expected behaviour.

Flippy498 said:
You should re-read the ReadMe thread. They're not corrupt. I thought that with "corrupt" you meant the MD5 checksum wouldn't match after the download. That WinRar error message is expected behaviour.
Click to expand...
Click to collapse
Ah gotcha... So I used the decryption tool to make a SD flashable zip, and what do you know, TWRP crashes when I swipe to flash... How come I can flash other ROMs but I can't flash stock roms without it crashing (Device turns off)

Please don't tinker around without knowing what you're doing and (as said before) read what got written in the FAQ and the RUU section. Extracting the *.zip wasn't needed at all since there already is a download link for an extracted *.zip. In addition, there are step by step instructions how RUUs can/need to get flashed.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Please don't tinker around without knowing what you're doing and (as said before) read what got written in the FAQ and the RUU section. Extracting the *.zip wasn't needed at all since there already is a download link for an extracted *.zip. In addition, there are step by step instructions how RUUs can/need to get flashed.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ok thank you "again" I have officially read your ENTIRE guide 3 times now, Not trying to offend you or make shame of your work, but the problem is I "THINK" that I am following your work.... I download the RUU for my phone (in this case SKU: 502 - CID: CWS__001 VERSION 2.11.502 (I have also tried 3.38.502.41 to no avail)) and everything is going as planned, I have verified that BOTH the CID and MID are matching that of my phone.... But when I plug SD card into Phone in download mode I get no such asked if I want to flash the file (as your guide says to do).... Ok so if I try to flash through TWRP it crashes, and if I try to Fastboot Flash the file I get what is seen in the picture attachment, and then nothing happens, except the bootloader page says "Under flash" and adds another line saying Under flash everytime I press the power button... My phone is S-OFF, is there another possible way to do this.... I swear to go I have read your ReadMe thread and I'm not just being arrogant, but my phone WILL not flash to ANY STOCK ROM downloaded anywhere from the Internet... @Flippy498 I promise there has to be something I missed in your ReadMe (I HAVE NO IDEA HOW I COULD) or i'm getting damaged ROMs... I'm sorry that you have to put up with me and help me thus far, and let me say the XDA community deserves people like you, and less people like me who think they know what they are doing until something breaks...
EDIT: It seems the phone is missing a located at /dev/fastboot_download_j in the CMD screenshot. Should that be said issue how would I go about fixing that...

Your SD card isn't bigger than 32gb and formatted to fat32? The file is placed in the root directory of the card and renamed to 0PJAIMG.zip (not 0PJAIMG.zip.zip and not OPJAIMG.zip)? The SD card method as it is written there already got used by a lot of users without any issues. The problem in this case must be on your end. What kind of error is stated at the bottom of your download mode? The M9 always tells you what's wrong. Either the SD card isn't mounted correctly (in other words you're using an unsupported format) or the 0PJAIMG.zip file is missing (in other words either non-existent on your sd card, placed in the wrong direction or renamed wrongly).
And of course TWRP crashes. Not every *.zip file can get flashed via TWRP just because it's a *.zip. (Just like not every *.zip can/should get unzipped just because it's a *.zip.) The only methods that can be used for flashing a RUU are mentioned in the ReadMe thread. And that's what I meant with "don't tinker around". You're doing things with files they're not meant to be done with.
The fastboot flash on the other hand can't work with the commands shown in your screenshot. That's a mistake in my guide. :silly: And it's even explained in the text above the instructions. I'm wondering why nobody (including me) noticed that before. I can only assume that it's because fastboot flashing doesn't get used that often for RUUS. The commands need to start with "htc_fastboot" not "fastboot". The normal fastboot isn't able to flash RUUs. I've fixed that part. Thanks for making me aware of that.
And in regard to the "damaged roms": The ReadMe thread explains how to check whether your downloads are fine (key word: md5).

Flippy498 said:
Your SD card isn't bigger than 32gb and formatted to fat32? The file is placed in the root directory of the card and renamed to 0PJAIMG.zip (not 0PJAIMG.zip.zip and not OPJAIMG.zip)? The SD card method as it is written there already got used by a lot of users without any issues. The problem in this case must be on your end. What kind of error is stated at the bottom of your download mode? The M9 always tells you what's wrong. Either the SD card isn't mounted correctly (in other words you're using an unsupported format) or the 0PJAIMG.zip file is missing (in other words either non-existent on your sd card, placed in the wrong direction or renamed wrongly).
And of course TWRP crashes. Not every *.zip file can get flashed via TWRP just because it's a *.zip. (Just like not every *.zip can/should get unzipped just because it's a *.zip.) The only methods that can be used for flashing a RUU are mentioned in the ReadMe thread. And that's what I meant with "don't tinker around". You're doing things with files they're not meant to be done with.
The fastboot flash on the other hand can't work with the commands shown in your screenshot. That's a mistake in my guide. :silly: And it's even explained in the text above the instructions. I'm wondering why nobody (including me) noticed that before. I can only assume that it's because fastboot flashing doesn't get used that often for RUUS. The commands need to start with "htc_fastboot" not "fastboot". The normal fastboot isn't able to flash RUUs. I've fixed that part. Thanks for making me aware of that.
And in regard to the "damaged roms": The ReadMe thread explains how to check whether your downloads are fine (key word: md5).
Click to expand...
Click to collapse
Once again Thank you for helping me out, the htc_flashboot command was what I needed, I was able to flash the stock rom through the command.... May I just say, you sir know what you are doing, and I wish you continue to help other people on this forms just like you've helped me.... I Installed the 2.x rom, but the OTA update didn't work for some reason... so I'm gonna flash the 4.x and then install ViperOne again...
And when I was saying "Damaged Roms" I was not implying that it was corrupted over the internet, but rather that they were never working in the first place...
Oh, that microSD card I had is in the trash now, since the only device that recognizes it is my pc, I assume it is on the brink of death...
Thanks again,
qwsderter

qwsderter said:
I Installed the 2.x rom, but the OTA update didn't work for some reason
Click to expand...
Click to collapse
That's probably like that due to AT&T denying OTAs to phones that currently aren't using an AT&T sim card. You wouldn't be the first user that isn't able to receive AT&T updates for the M9. Don't ask me why they're allowed to do so. Something like that wouldn't be possible in the EU.
qwsderter said:
so I'm gonna flash the 4.x and then install ViperOne again
Click to expand...
Click to collapse
Don't forget that you need to flash one of Sneakyghost's firmware packs if you want to be able to flash 4.x RUUs. (Keyword: encryption keys)
qwsderter said:
And when I was saying "Damaged Roms" I was not implying that it was corrupted over the internet, but rather that they were never working in the first place
Click to expand...
Click to collapse
That's actually the difference between my ReadMe thread and most of the RUU collections on other websites. The files only get linked if they're known to be working whereas other sites link every RUU they can find. There are a lot more RUUs for the M9 out there than the ones I listed. However, these RUUs either aren't able to get flashed successfully or their roms aren't able to receive any OTAs - e.g. there's a second RUU for firmware 1.32.401.15 than the one that is linked in my thread and if you flash that other RUU you're stuck on its firmware version until you flash a different RUU.
qwsderter said:
Oh, that microSD card I had is in the trash now, since the only device that recognizes it is my pc, I assume it is on the brink of death
Click to expand...
Click to collapse
If it's really broken you should thank whichever god you believe in that your phone wasn't able to recognize the card. Since your phone is S-OFF all security checks on your phone are disabled. That means if a file gets corrputed on the SD card due to its partition being messed up your phone would still accept the broken RUU, nonetheless. This would most likely lead to unrecoverable damages. In other words, chances are high in such situations that you create a fancy but expensive paperweigth.

Flippy498 said:
That's probably like that due to AT&T denying OTAs to phones that currently aren't using an AT&T sim card. You wouldn't be the first user that isn't able to receive AT&T updates for the M9. Don't ask me why they're allowed to do so. Something like that wouldn't be possible in the EU.
Click to expand...
Click to collapse
Funny, I thought the same thing, until I realized it was ATT who I am paying every month to rip my girlfriend and I off. Well oh well, I know you are in Germany (From your profile) but if you ever come to the United States, I will say from my personal experience (my opinion, not facts) ATT has seemed to have the broadest coverage, but also is the (2nd) most constrictive (Verizon seems very constraining), to me ATT feels premium but they are also (in my opinion) the most likely to royally screw up... Oh well, no OTA time to flash!!!
Flippy498 said:
If it's really broken you should thank whichever god you believe in that your phone wasn't able to recognize the card. Since your phone is S-OFF all security checks on your phone are disabled. That means if a file gets corrputed on the SD card due to its partition being messed up your phone would still accept the broken RUU, nonetheless. This would most likely lead to unrecoverable damages. In other words, chances are high in such situations that you create a fancy but expensive paperweigth.
Click to expand...
Click to collapse
Trust me, when I tried the SD card in the phone I thought, "That is a little odd", then both of my ASUS MemoPads didn't detect it either EVEN THOUGH THEY WERE RUNNING, I just assumed that they didn't work because MemoPads are the most budget friendly tablets ever and something broke, so I go to my Nexus 7 and realize it doesn't have an SD card slot so I couldn't test, so I popped the card in our Camera... Low and behold it doesnt detect.... Now the true question, why did my desktop detect it, eh whatever not worth my time.... The gods were looking down on me, they broke my $10 microSD and not my more than 10$ phone.....
Once again thank you for the help Flippy, you have no idea how much it hurt using my iPhone 5 for 2 days, I felt so inferior

Swapping simcards

I have an unlocked Samsung Galaxy Note 8 that was a Verizon Wireless variant. I went to swap the SIM cards from the Total Wireless SIM to active AT&T SIM card just to see if it would work and it did but I went to put the Total Wireless SIM card back in and I'm left with all of this AT&T bloat ware that won't let me uninstall along with the AT&T globe as boot logo... Any ideas?

Liftkit said:
I have an unlocked Samsung Galaxy Note 8 that was a Verizon Wireless variant. I went to swap the SIM cards from the Total Wireless SIM to active AT&T SIM card just to see if it would work and it did but I went to put the Total Wireless SIM card back in and I'm left with all of this AT&T bloat ware that won't let me uninstall along with the AT&T globe as boot logo... Any ideas?
Click to expand...
Click to collapse
You have to flash the unlocked firmware that's N950U1 because that doesn't have the bloatware like that.

I'm confused. The phone is not rooted it's just been carrier unlocked. It acts like bloatware and it wasn't there before I don't understand how a SIM card inserting it and replacing it with a different carriers what causes it to leave behind un-installable applications and a boot logo

Liftkit said:
I'm confused. The phone is not rooted it's just been carrier unlocked. It acts like bloatware and it wasn't there before I don't understand how a SIM card inserting it and replacing it with a different carriers what causes it to leave behind un-installable applications and a boot logo
Click to expand...
Click to collapse
Because it caused your CSC to change and the carriers love putting all their crappy bloatware in the phone because they want you to use their products.. Root has nothing to do with it. If you flash the unlocked firmware N950U1 you won't have to deal with that again!

MrMike2182 said:
Because it caused your CSC to change and the carriers love putting all their crappy bloatware in the phone because they want you to use their products.. Root has nothing to do with it. If you flash the unlocked firmware N950U1 you won't have to deal with that again!
Click to expand...
Click to collapse
Yeah bloatware is such a nuisance. Could you provide a link to some instructions on how to flash firmware? thanks

Liftkit said:
Yeah bloatware is such a nuisance. Could you provide a link to some instructions on how to flash firmware? thanks
Click to expand...
Click to collapse
It's pretty easy actually.. You just download odin that's the application you flash with then you download the firmware you want to flash then unzip the downloaded firmware so you can see all the files in it.. Make sure the computer already has the cellphones drivers already installed or it won't see the phone connected then open odin and put each file in their respective places AP to AP BL to BL etc... Then flash. If you end up with an error just ask us.

MrMike2182 said:
It's pretty easy actually.. You just download odin that's the application you flash with then you download the firmware you want to flash then unzip the downloaded firmware so you can see all the files in it.. Make sure the computer already has the cellphones drivers already installed or it won't see the phone connected then open odin and put each file in their respective places AP to AP BL to BL etc... Then flash. If you end up with an error just ask us.
Click to expand...
Click to collapse
Ok ive got all of it downloaded and unzipped and files added to all the corresponding boxes, my phone is recognized and in download mode.. Yet it still fails to start the process. Ive got the latest odin and im assuming it must be the firmware version?

Just out of curiosity, did you try doing a cache wipe and factory reset in recovery mode with the Total Wireless SIM card installed. Honestly dont know if that would work but might be worth a try.
Also with Odin, did you try to run as administrator? And assuming you are using a Windows based computer, what version of Windows are you using? And I believe there are also 2 versions of the latest Odin, 1 regular and 1 that is modded. Maybe try the other version as well. I dont have a link but I'm sure someone may come along and provide it.

I was trying to keep all of my info so I didn't do a wipe. In the odin version that I have on been using is the one on the Samsung firmware website.

I'm pretty sure this is the patched one here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Also if you use Samsung Smart Switch, that is an easy way to save pretty much all your data, customizations, and most of your programs right to your SD card. It will restore pretty much everything for you. It makes things a lot easier to restore when playing with different ROMs or versions of Android. When you use Smart Switch to restore, it will basically look and feel like it was before you wiped.

Liftkit said:
Ok ive got all of it downloaded and unzipped and files added to all the corresponding boxes, my phone is recognized and in download mode.. Yet it still fails to start the process. Ive got the latest odin and im assuming it must be the firmware version?
Click to expand...
Click to collapse
You're using the wrong odin you need to use the patched version or it will continue to fail.. I've attached the patched version of odin here.

MrMike2182 said:
You're using the wrong odin you need to use the patched version or it will continue to fail.. I've attached the patched version of odin here.
Click to expand...
Click to collapse
I tried the version in the link provided and now it doesnt even recognize the phone when connected where as the the one on sammobile recognized it and started but failed

Liftkit said:
I tried the version in the link provided and now it doesnt even recognize the phone when connected where as the the one on sammobile recognized it and started but failed
Click to expand...
Click to collapse
Something isn't right.. Try a different USB port and a different wire!! Also make sure you right click on odin and run it as administrator.. Go through the firmware files that you extracted and delete just the .md5 part off of all of the files you're going to flash.

MrMike2182 said:
Something isn't right.. Try a different USB port and a different wire!! Also make sure you right click on odin and run it as administrator.. Go through the firmware files that you extracted and delete just the .md5 part off of all of the files you're going to flash.
Click to expand...
Click to collapse
Okay I got it to download it was a USB drivers not installed properly although know that I have completed the firmware update now my SIM card doesn't even register in my phone, what happened?i have attached screen shots. to addit was a Verzon firm not sprint

Liftkit said:
Okay I got it to download it was a USB drivers not installed properly although know that I have completed the firmware update now my SIM card doesn't even register in my phone, what happened?i have attached screen shots. to addit was a Verzon firm not sprint
Click to expand...
Click to collapse
Pop the sim card tray out and then push it back in with the phone on and see if it sees it and asks to restart.. If it doesn't then I'm not sure and someone else will need to chime in.

MrMike2182 said:
Pop the sim card tray out and then push it back in with the phone on and see if it sees it and asks to restart.. If it doesn't then I'm not sure and someone else will need to chime in.
Click to expand...
Click to collapse
Yeah i tried that and nothin still restarted it but nothing, still. no. service

I couldn't get my phone to work if I tried right now anyting I'm screwed with any SIM card

Liftkit said:
I couldn't get my phone to work if I tried right now anyting I'm screwed with any SIM card
Click to expand...
Click to collapse
Where did you get the phone from?

MrMike2182 said:
Where did you get the phone from?
Click to expand...
Click to collapse
A third-party seller on eBay but it was brand new never been opened or activated.

But I think that would be irrelevant since it was working just fine with the exception of some bloatware.