Related
Ok just recently unbricked my phone and started flashing once again. First I did the HARD SPL change from 2.03 to 2.10 Olipro. I flashed the current vp3G a few times but I was getting no phone service. I flashed the schaps and it did the same. My was getting no service and when I clicked on settings it said this.
Unknown SIM status.
Only emergency calls can be made without a PIN.
Click to expand...
Click to collapse
Did some googling and found some sources where it said my default PIN was either 1111 or 2222. I went ahead and called ATT and explained to them I was getting no service but of course never mentioned I had a cooked ROM. They said the same that the default was 1111. Of course for some reason when I was talking to them I could not get to the settings to enter it. I told them I would call them back.
Finally got to enter it in and nothing. It is still not working. I'm in some desperate need of suggestions. Thank You.
- Monty
Flash the OEM ROM from your provider. This should get your service back if your using a legit SIM
i see you have unbricked your phone, try loading up a new radio
http://rapidshare.com/files/60589318/radio1.54.07.00.rar
oh yea, thats the radio im using for my 8525, its the updated version 1.54 it works pretty well, hope that fixes your problem
I have that same problem but it seems that changing the radio does not work, although I havent tried every single radio. Some radios will give say i have no service even when i don't have the sim card in (it should be saying no sim)
This might help
If you are in USA and if you have a CINULAR sim card in your phone go to a AT&T store for a FREE AT&T sim card. It might resolve the issue as AT&T just changed some settings in some towers.
Read about in VP's 3.62
here: http://forum.xda-developers.com/showpost.php?p=1637422&postcount=445:)
fuzzvirus said:
If you are in USA and if you have a CINULAR sim card in your phone go to a AT&T store for a FREE AT&T sim card. It might resolve the issue as AT&T just changed some settings in some towers.
Read about in VP's 3.62
here: http://forum.xda-developers.com/showpost.php?p=1637422&postcount=445:)[/QUOTE
I have a new AT&T sim card and I still have the problem
Click to expand...
Click to collapse
Monty, have you found a solution?
ihavetinyballs said:
Flash the OEM ROM from your provider. This should get your service back if your using a legit SIM
Click to expand...
Click to collapse
That is how I bricked my phone in the first place. Could not flash OEM either 2.15 or the most recent 3.62 WM6 upgrade.
asianr0cker said:
oh yea, thats the radio im using for my 8525, its the updated version 1.54 it works pretty well, hope that fixes your problem
Click to expand...
Click to collapse
When I got unbricked I updated my SPL like you mentioned and now I'm running 2.10. I did try to update the radio but that also got locked up and had to hard reset to get it back. I was trying 1.54 also.
cjchriscj said:
Monty, have you found a solution?
Click to expand...
Click to collapse
No I have not.
More reading and more reading. Ok I realize I have no GSM and no Radio. When I try to install radio it gets stuck on 0% then locks me out. Then I'm stuck in the Tri-Color mode and am forced to reflash ROM. I'm thinking "Problem 5" is the problem I'm having but can anyone confirm or help me out please.
My ATT flash screen says:
R None
G None
D 3.62
Click to expand...
Click to collapse
That means I have no Radio and GSM correct? What do I do?
warranty?
How far into your warranty are you, assuming you're still under warranty? Same thing happened to me. I played stupid with AT&T tech support (then Cingular), had no distinguishable drop marks or water damage, and they replaced it under warranty I even had it stuck on the bootloader screen If you're still under warranty, try to load an oem rom back on it and see if you can get them to replace it.
kalrykh said:
How far into your warranty are you, assuming you're still under warranty? Same thing happened to me. I played stupid with AT&T tech support (then Cingular), had no distinguishable drop marks or water damage, and they replaced it under warranty I even had it stuck on the bootloader screen If you're still under warranty, try to load an oem rom back on it and see if you can get them to replace it.
Click to expand...
Click to collapse
Unfortunatley im out of warranty
Is there anyway to completely erase everything that is on the hermes at once? except for the stuff on the eeprom, i already had to deal with that
can no one help us?
i heard from my friend who works at an att non corp store that just recently non corp stores were given the ability to give the new contract discounts. that he just has to make a 5 min call and it gets approved and they can offer you the 2yr discount although it might extend your contract.
reason im saying this is even if your not up for an update, any att store should be able to (if the guy chooses to be helpful) hook you up with the discount regardless of how long or how little you've been in contract.
just food for thought in case you cant find a solution.
when I reset my device i see no GSM ocassionaly, well since an hour ago, its been saying nothing but No GSM, I have tried to fix it using the unbrick direction in the wiki, but to no avail.
Hey guys, I have an Excalibur that gets stuck on the TMobile splash screen when you try to turn the device on.
I've tried doing a hard reset, but I still end up with the same problem. I can get the phone into the bootloader mode (green, blue red) but everything I've searched around (read the wiki, tried google, youtube, etc.) says that I need to be connected to ActiveSync in order to flash a rom onto it.
Is there any way to flash this thing while in bootloader mode or am I screwed?
Thanks!!
Stickys, official roms & hard-reset bootloader.
Thanks for the quick response, Stylez!
I've read the "hard reset and bootloader" post, which is how I learned to put the device in bootloader mode (thanks to you!)
I've also downloaded the necessary ROM file and loader from the other sticky you mentioned. (I did read and search on my own before asking)
But when I try to run the ROMUpdateUtility.exe it tells me to connect the device to activesync which I can't really do because it's in Bootloader mode and WindowsMobile Device Center says it's not connected.
Try this.
Did you SDA and Surreal unlocked your cell prior to flashing?
If not, do so. You can find both files in the Wiki or in one of the stickies I am sure.
SDA Unlock it from desktop, reboot, Surreal, drag it in the device, install it, once installed... go to the ROM you chose and run the AUTO file, not RUU... you should follow the instructions of when to click on and the center button on the device, now, (this might occur) I know it does make the sound of restarting and when you load the ROM say v1.7a Ricky and Styles RoseROM, it won't go over 3% saying it can't find the device... just click on the RUU this time, and I bet you that this time it will find the device and load it. Try it and let me know.
When I run the SDA Unlock, the button remains greyed out because it doesn't recognize the device is connected to the computer. Is it supposed to even though it's on the bootloader screen?
The white bootloader screen is only needed when you flash a new ROM into it. You need to connect the device NOT in bootloader but just as is when turned on normally so that the ActiveSync will recognize it.
Same thing for Surreal, you just drag it in the phone and install it as you would install any .cab.
Inimical said:
Hey guys, I have an Excalibur that gets stuck on the TMobile splash screen when you try to turn the device on.
Is there any way to flash this thing while in bootloader mode or am I screwed?
Click to expand...
Click to collapse
Thanks, but unfortunately I can't get this thing to boot past the T-Mobile splash screen. Is there no way to flash it without Activesync?
Also, I'm in the Red/Green/Blue bootloader (hold the camera button and attach USB cable) not the White one.
So, you are running the T-Mobile flash, yet you can't go past the initial screen? Did you just get it like this or did you flash it before... ???
Did you try to run USPL CID BYPASS? It might get it into white bootloader mode, just assuming. If not, then do as I suggested, when it says it doesn't find the device, re-run the RUU. As posted above.
I got the phone like this from a friend. So, who knows what could be wrong with it.
The bootloader screen says it's running 1.22.0000 and as far as I know, it's the default TMobile rom.
It won't get passed the T-Mobile initial screen. It will just turn back off after a few minutes. I can get it into the Bootloader mode as mentioned before, so I assumed I'd be able to flash it to fix whatever is preventing it from booting fully.
It seems, however, that something more severe may be wrong with the phone if the computer can't register that it's connected which prevents me from running any kind of CID BYPASS programs or SDA Unlock utilities.
Any other suggestions?
I am gonna think about it, but hopefully the more expert in here will help you sooner. I personally think your buddy messed up while flashing or something. Because if he did not, then he can just send it back and get another one from T-Mo. Plus, not being there to see makes things a bit more complicated this once.
Are you even connected to ActiveSync when in bootloader mode? I don't mean you, I mean in general.
And btw, did you try to do what I suggested you?
Connect the phone, get it in bootloader, try to flash the T-Mo ROM and clickon AUTO.bat, an image is on the guide with pics sticky thread in here... that should open and ms-dos thing, even if it opens the loader and doesn't go over 3%, this time... click on the RUU icon.. it worked for me last night and for the T-Mo ROM you shouldn't need any sda or surreal stuff. Try it...
You can get the T-Mo ROM from their web-site or here too.
I know you can go on youtube and look up upgrade to kavana, there is a guy who has it for download. Thing is T-Mo asks you for a cell number to verify you are the owner of the phone so you might have to insert your friend's number.
Capitan Totti said:
Are you even connected to ActiveSync when in bootloader mode? I don't mean you, I mean in general.
Click to expand...
Click to collapse
No, while in bootloader and connected via USB, ActiveSync (WindowsMobile Device Center in Vista) says that there is no device connected.
Capitan Totti said:
And btw, did you try to do what I suggested you?
Connect the phone, get it in bootloader, try to flash the T-Mo ROM and clickon AUTO.bat
Click to expand...
Click to collapse
I tried this step, however, when the DOS box opens, it tells me it cannot find the phone and asks to try again. I do this repeatedly and get nothing. I also tried clicking NO on the retry, but nothing.
Capitan Totti said:
You can get the T-Mo ROM from their web-site or here too.
I know you can go on youtube and look up upgrade to kavana, there is a guy who has it for download. Thing is T-Mo asks you for a cell number to verify you are the owner of the phone so you might have to insert your friend's number.
Click to expand...
Click to collapse
Tried that too, I actually have T-Mobile so I put in my own number. I ended up with the same error message about not finding a phone. Is it supposed to find the phone when connected in Bootloader mode?
Thanks for your help, btw
Thanks for explaining that. I think you might have yourself a bit of a problem.
I'll ponder on it and let you know. Can't you return it in exchange for another Dash?
What ROM are you trying to flash? I would recommend that you go to T-Mobile.com/wmupgrade and download the current Officially Dash ROM and recover the device that way. If you do not have a T-Mobile phone number, I can get you one that you may use to access the download page.
Once you reflash the official rom I recommend you do the CID unlock and flash a 6.1
stellarvelocity said:
What ROM are you trying to flash? I would recommend that you go to T-Mobile.com/wmupgrade and download the current Officially Dash ROM and recover the device that way. If you do not have a T-Mobile phone number, I can get you one that you may use to access the download page.
Once you reflash the official rom I recommend you do the CID unlock and flash a 6.1
Click to expand...
Click to collapse
I recommend reading the thread before posting. All you proposed I already mentioned and he answered. Look above...
I was trying to install the sprint shipped rom (6.1 from htc.com), but, for some reason it went to recovery mode after it was already running about 10% on the loading page.
Now, all Im getting is the three color screen with this info:
VOGU100 MFG RUUNBH
SPL- 2.01.1000
CPLD-3
The PC still recognizes the phone when I used the USB cord.
Any suggestion will be appreciated since I already try doing the rom update a couple of times and it keeps failing.
My Phone: Sprint pcs HTC Touch.
Perhaps you tried flashing the GSM ROM? Just download this one and run it. You'll be fine.
EDIT: Apparently you can't directly link from HTC's website. Just be sure to choose the Sprint version.
chulopapi said:
I was trying to install the sprint shipped rom (6.1 from htc.com), but, for some reason it went to recovery mode after it was already running about 10% on the loading page.
Now, all Im getting is the three color screen with this info:
VOGU100 MFG RUUNBH
SPL- 2.01.1000
CPLD-3
The PC still recognizes the phone when I used the USB cord.
Any suggestion will be appreciated since I already try doing the rom update a couple of times and it keeps failing.
My Phone: Sprint pcs HTC Touch.
Click to expand...
Click to collapse
It may be that your device ran out of battery. Try charging your device and use the rom that you were trying to use before (Sprint shipped rom). Good luck.
TaurusBullba said:
Perhaps you tried flashing the GSM ROM? Just download this one and run it. You'll be fine.
EDIT: Apparently you can't directly link from HTC's website. Just be sure to choose the Sprint version.
Click to expand...
Click to collapse
I download the Rom from that website, the only version that they have for the htc touch from sprint, thats the one I tried to flash before
I'm going to try the GSM ROM and I will get you back tomorrow to see if it worked.
egzthunder1 said:
It may be that your device ran out of battery. Try charging your device and use the rom that you were trying to use before (Sprint shipped rom). Good luck.
Click to expand...
Click to collapse
I will try to leave it charging, and then, try to run the ROM thanks...I will reply back with results
chulopapi said:
I download the Rom from that website, the only version that they have for the htc touch from sprint, thats the one I tried to flash before
I'm going to try the GSM ROM and I will get you back tomorrow to see if it worked.
Click to expand...
Click to collapse
NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.
If you have a Sprint branded phone, that is a CDMA phone. NEVER install a GSM rom on a CDMA phone.
egzthunder1 said:
NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.
If you have a Sprint branded phone, that is a CDMA phone. NEVER install a GSM rom on a CDMA phone.
Click to expand...
Click to collapse
I'm guessing you were too late Egz, probably bricked the phone.
WnG88 said:
I'm guessing you were too late Egz, probably bricked the phone.
Click to expand...
Click to collapse
Which is why I always say "read, read, read, and then read some more"....
WnG88 said:
I'm guessing you were too late Egz, probably bricked the phone.
Click to expand...
Click to collapse
No actually I haven't done anything yet. so, I'm still where I began...which stills no good
just flash a sprint rom. go to here... just download the shipped exe sprint rom. either that or you can flash it via sd card.
If flashing the full versions keep failing, try and just flash the un-locker.
You still have a locked phone, but you should be able to try and flash
the un-locker from Coke since you're at the tri-color screen.
forum.xda-developers.com/showthread.php?t=592964
Read down that thread to get the download link for file below
Vogue_unlocker_MFG_2.31.zip
That should flash, then you can try and load a rom from the MicroSD card.
Alright people I have solve my problem. After downloading many ROMs, finally one of them worked. When to a ppcgeek page where they have all kinds of sprint roms.
Here's the page:
//up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker.exe[/url]
special thanks to everyone that help.
Hi. Can a T-mobile HTC TOUCH PRO2 (US version) which was stupidly flashed with a SPRINT CDMA ROM be brought back to GSM by reflashing it with a GSM flash ROM file using a PC running Windows? If so, where can I obtain the flash ROM file from, as well as the utility to flashing it back with.
PS: HTC Techs wouldn't help me except telling me to send it in so they can charge me more than I already paid for this phone already. Thanks in advance for helping or trying to help.
Did you brick you device?
Kevinik said:
Did you brick you device?
Click to expand...
Click to collapse
Well, my "know-it-all" buddy who's had great success with tinkering & flashing my other phones, B-R-I-C-K-E-D this one. Now he and I have been through the gamut on trying to reset this TP2 with the problems listed in another thread here using forum members' suggestions as well as the resetting tips for this model found on HTC.com with no success. So I had a thought in my sleep. Maybe, just maybe, I can reflash it?
Symptoms: There is no screen on this phone now. My PC tries to recognize it for about 1 minute or two, after it displays it's hardware signature in Device Manager 2-3 minutes showing up as "Qualcomm CDMA Technologies MSM" with an exclamation point under "Other Devices", then, the phone's hardware signature disappears from my hardware list in Windows 7's Device Manager listing. It didn't do that before.
"My Other thread" referring to all I did in trying to revive this phone with the help of other members here.
suzukii said:
Hi. Can a T-mobile HTC TOUCH PRO2 (US version) which was stupidly flashed with a SPRINT CDMA ROM be brought back to GSM by reflashing it with a GSM flash ROM file using a PC running Windows? If so, where can I obtain the flash ROM file from, as well as the utility to flashing it back with.
PS: HTC Techs wouldn't help me except telling me to send it in so they can charge me more than I already paid for this phone already. Thanks in advance for helping or trying to help.
Click to expand...
Click to collapse
You should be able to connect the USB, go into bootloader mode, and then run update the ROM. You should probably run task29 first to clear the memory. If you can't get the USB to work, you can flash from your SD card. Check the first several posts of the ROM forum, rather than this GENERAL forum.
find an official T-mobile HTC TOUCH PRO2 rom and flash it.
and if your device has hard-spl then you can flash any full gsm rom.
some roms here
faria said:
find an official T-mobile HTC TOUCH PRO2 rom and flash it.
and if your device has hard-spl then you can flash any full gsm rom.
some roms here
Click to expand...
Click to collapse
Yep it all started with the Hard-SPL from the Rhodium.htc-unlocks.com guys.
PS: your link above doesn't seem to work.
suzukii said:
Yep it all started with the Hard-SPL from the Rhodium.htc-unlocks.com guys.
PS: your link above doesn't seem to work.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=544538
and here you shoul find a t-mobile rom
http://www.xda-roms.com/
faria said:
http://forum.xda-developers.com/showthread.php?t=544538
and here you shoul find a t-mobile rom
http://www.xda-roms.com/
Click to expand...
Click to collapse
Will do. Thanks.
faria said:
http://forum.xda-developers.com/showthread.php?t=544538
and here you shoul find a t-mobile rom
http://www.xda-roms.com/
Click to expand...
Click to collapse
Nope no good. These tips all expect some sort of interactivity between the use & the phone present like being able to go into bootloader mode or expecting something visual on the screen. My TP2 doesn't do anything after flashing it with the CDMA process (provided by the Rhodium.htc-unlocks.com website), except turn on the little orange LED ever couple of minutes until the battery just dies out.
You now have a nice paper weight or brick. Flashing a cdma radio and/or bootloader/unlocker is NOT reversible. If you had only flashed a cdma rom then that could have been reversed.
suzukii said:
Nope no good. These tips all expect some sort of interactivity between the use & the phone present like being able to go into bootloader mode or expecting something visual on the screen. My TP2 doesn't do anything after flashing it with the CDMA process (provided by the Rhodium.htc-unlocks.com website), except turn on the little orange LED ever couple of minutes until the battery just dies out.
Click to expand...
Click to collapse
If you cant get into bootloader I'm almost certain that means the phone's bricked. I realize that's likely not the information you want to here but you need at least a FEW things working on the thing to be able to flash it to a different rom. Bootloader being one of them.
If you cant get into bootloader mode,then i dont currently know any other way of reviving the device at home.sorry.
edit
to the poster above....
it seems we posted at the same time
drewcam888 said:
You now have a nice paper weight or brick. Flashing a cdma radio and/or bootloader/unlocker is NOT reversible. If you had only flashed a cdma rom then that could have been reversed.
Click to expand...
Click to collapse
YEP. Thanks. I just got a RMA from HTC to send it in for repairs. They'll probably rape my credit card. Oh well.
suzukii said:
YEP. Thanks. I just got a RMA from HTC to send it in for repairs. They'll probably rape my credit card. Oh well.
Click to expand...
Click to collapse
you rigth there!problably cheaper to buy a new one
Aaron McCarthy said:
If you cant get into bootloader I'm almost certain that means the phone's bricked. I realize that's likely not the information you want to here but you need at least a FEW things working on the thing to be able to flash it to a different rom. Bootloader being one of them.
Click to expand...
Click to collapse
I'll keep that in mind next time. For now the phone is on it's way back to Oz. What sux about this is that I could've had the pleasure of bricking my own phone, instead my pal got to enjoy this phones' trial & tribulations. thanks anyhow guys.
Now lets see what happens with my T-mobile HD2-Leo, eh,eh
suzukii said:
YEP. Thanks. I just got a RMA from HTC to send it in for repairs. They'll probably rape my credit card. Oh well.
Click to expand...
Click to collapse
RMA usually it's totally free you only have to pay to send in the phone. I know cause I did the same thing kind of... I flashed a GSM rom on a CDMA phone and totally bricked it. My phone connection led didn't light up when connected. Then I call HTC, they sent me to call another company that handles US Cellular and got it RMA paid only shipping.
If your led connection lights up there might be a possibility you can flash your stock rom with a clean Micro SD Card. Just search for this method on the forums, it has been a working life saver to many.
suzukii said:
Nope no good. These tips all expect some sort of interactivity between the use & the phone present like being able to go into bootloader mode or expecting something visual on the screen. My TP2 doesn't do anything after flashing it with the CDMA process (provided by the Rhodium.htc-unlocks.com website), except turn on the little orange LED ever couple of minutes until the battery just dies out.
Click to expand...
Click to collapse
The only thing that might work is to go back over the the CDMA forum and find out how the CDMA version invokes the bootloader. Maybe it is different than the GSM version? If you can't get to bootloader you are in trouble.
Kevinik said:
RMA usually it's totally free you only have to pay to send in the phone. I know cause I did the same thing kind of... I flashed a GSM rom on a CDMA phone and totally bricked it. My phone connection led didn't light up when connected. Then I call HTC, they sent me to call another company that handles US Cellular and got it RMA paid only shipping.
Click to expand...
Click to collapse
Bear in mind that (I believe) the OP said he Hard-SPL'd the device. I've seen numerous tales on here, of HTC declining to repair under warranty in those cases, citing 'Illegal software'. They usually then quote a couple of hundred dollars to change the motherboard, or a fee to return the phone unrepaired (the fee is their charge for the diagnostics).
I have the same error. Any new guess? In my country there aren't HTC repair stores
hi all:
anyone here know how to reboot the tmobile tp2 after I think I brick it? probably flash with wrong rom. now the phone will not turn off. stuck at "stick together".
Thanks
De
When I first got my HTC LTE was working fine then it suddenly stopped. I called T-Mobile who was clueless, so I popped the sim back into my S7 Edge and Nexus 6P age LTE worked perfectly. I decided to try unlocking s-off etc to flash a more current firmware since mine was on a really old one. I flagged 1.30xx stock then LeeDroid rom being sure to not decrypt data during the process. LTE still won't won't, I'm only getting HSPA+ which sucks. I have another sim card I could activate, but I want to know if there's another way to fix this? My APN seems fine, as does the preferred radio mode. Any suggestions/additional troubleshooting that I can do before sending the phone back
Update:
Here are some videos I made showing the issue:
Part 1
Part 2
I will add another one using the stock ROM to further prove the issue exists on both the unlocked firmware, and T-Mobile one.
You root your phone, mess it up and then send it back? Kinda messed up.
Did you try flashing the latest modem?
iamtimmah said:
You root your phone, mess it up and then send it back? Kinda messed up.
Click to expand...
Click to collapse
He said this happened before, and he tried rooted and flashing a ROM to see if it made a difference.
iamtimmah said:
You root your phone, mess it up and then send it back? Kinda messed up.
Click to expand...
Click to collapse
No, I stated the issue was there before then. I only unlocked it and flashed updated firmware in an attempt to fix the issue which it didn't. Clearly we all need to read thoroughly before responding to an OP so we don't look arrogant in the end.
Now, on another note I mentioned this issue was already present from the moment I started using the phone 100% stock. It will sometimes still get LTE, but it only sticks for 10-30 seconds then drops to H/H+ immediately. My S7 Edge and Nexus 6P do not have this issue whatsoever therefore I'm certain something with the firmware is not right.
geoff5093 said:
Did you try flashing the latest modem?
He said this happened before, and he tried rooted and flashing a ROM to see if it made a difference.
Click to expand...
Click to collapse
Thank you, for reading the OP , and no I don't have just the modem files, although I do have the RUU so I know it's in there
Pilz said:
When I first got my HTC LTE was working fine then it suddenly stopped. I called T-Mobile who was clueless, so I popped the sim back into my S7 Edge and Nexus 6P age LTE worked perfectly. I decided to try unlocking s-off etc to flash a more current firmware since mine was on a really old one. I flagged 1.30xx stock then LeeDroid rom being sure to not decrypt data during the process. LTE still won't won't, I'm only getting HSPA+ which sucks. I have another sim card I could activate, but I want to know if there's another way to fix this? My APN seems fine, as does the preferred radio mode. Any suggestions/additional troubleshooting that I can do before sending the phone back
Click to expand...
Click to collapse
Did you try 1.53 us unlocked ruu that's worth a try
bbell101584 said:
Did you try 1.53 us unlocked ruu that's worth a try
Click to expand...
Click to collapse
No, I can't get it to flash, but I'm going to try another method for updating it to that version
Mine has been extremely inconsistent in sticking to LTE. Sometimes I have to force it to LTE only and then when I switch back to GSM/WCDMA/LTE auto, it ****s the bed for a few minutes before correcting itself.
Pilz said:
No, I can't get it to flash, but I'm going to try another method for updating it to that version
Click to expand...
Click to collapse
Did you try downloading the ruu.exe on the computer and then running it as administrator also make sure you have either changed your cid to the US unlocked one or to supercid I used the exe version of the ruu it went fine on my end I hope you get your situation worked out
I don't know your phone model, but since you are in the US. I would suggest you run US unlocked RUU for eliminating any software issues.
If you have an unlocked device, then you can simply download from @Behold's thread about us unlocked RUU.
If you have a T-mobile device, I would suggest you to get s-off and then run RUU.
Send back your modified phone is likely the least preferred option to do/recommend.
bbell101584 said:
Did you try downloading the ruu.exe on the computer and then running it as administrator also make sure you have either changed your cid to the US unlocked one or to supercid I used the exe version of the ruu it went fine on my end I hope you get your situation worked out
Click to expand...
Click to collapse
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
frankcck said:
I don't know your phone model, but since you are in the US. I would suggest you run US unlocked RUU for eliminating any software issues.
If you have an unlocked device, then you can simply download from @Behold's thread about us unlocked RUU.
If you have a T-mobile device, I would suggest you to get s-off and then run RUU.
Send back your modified phone is likely the least preferred option to do/recommend.
Click to expand...
Click to collapse
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Pilz said:
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Click to expand...
Click to collapse
Boot into download mode and run RUU again.
frankcck said:
Boot into download mode and run RUU again.
Click to expand...
Click to collapse
That's exactly what I did, and I just confirmed the error code was "155 unknown error"
Pilz said:
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Click to expand...
Click to collapse
Did you right click the ruu.exe and choose to run as administrative that's the only thing else I can say maybe a more experienced person can help you further sorry
---------- Post added at 02:10 PM ---------- Previous post was at 02:09 PM ----------
Redownload the ruu or just try from a whole different computer if you have access to one
bbell101584 said:
Did you right click the ruu.exe and choose to run as administrative that's the only thing else I can say maybe a more experienced person can help you further sorry
Click to expand...
Click to collapse
Yep, following the instructions to the t (so to speak), it ran fine, booted into whatever that weird screen is with the % on it then after about 15 seconds gave me the error
I just gave the extSD method again, now it is saying
Code:
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 22 RU_HEADER_ERROR
Pilz said:
That's exactly what I did, and I just confirmed the error code was "155 unknown error"
Click to expand...
Click to collapse
I did not boot into download mode. Left it on the home screen, Just made sure USB debugging was on. The RUU handled everything after that.
Quick update:
I changed my CID to 111111 and it flashed via the RUU .exe file (surprisingly). I still cannot get LTE other than a ran moment where it might connect for a second before dropping back to H+. I even made a new APN (copied from my S7 Edge) and it still won't get LTE. Could this be some bizarre sim issue despite it working on every other phone I own (4 other phones work fine with LTE and my sim)?
Pilz said:
Quick update:
I changed my CID to 111111 and it flashed via the RUU .exe file (surprisingly). I still cannot get LTE other than a ran moment where it might connect for a second before dropping back to H+. I even made a new APN (copied from my S7 Edge) and it still won't get LTE. Could this be some bizarre sim issue despite it working on every other phone I own (4 other phones work fine with LTE and my sim)?
Click to expand...
Click to collapse
Have them re register the device on the network? The US unlocked base should work fine on TMOUS, I know as I have used it and both LTE, VoLTE, and WiFi calling fully work.
Mikee4fun said:
Looks like a sim issue. Try re seating the sim and if that does not work have TMO give you another sim from the store.
Click to expand...
Click to collapse
I have another sim, and I've reinserted it s few times now without success. I might call them and activate the other sim. It's just odd how it works flawlessly with LTE on every phone but this one.