A while ago I bought a M7 second hand, and the phone worked nicely while my m8 was being repaired. When the m8 returned I left the M7 unused for some months. Earlier this week I once again needed the M7 as a backup phone. I updated with Lollipop. But quite shortly after the phone started to reboot and couldn't find network/ recognize SIM. As thought I would be warranty left I tried to look up IMEI and didn't find any.
After briefly searching the net it seems like all other phones with this issue have been rooted. As long as I've owned the phone I haven't rooted the phone, but the previous owner might have done it. So I wonder if the imei could have been wiped if the phone never have been rooted. If that's unlikely the previous owner probaly have rooted the phone and that would surely void the warranty.
Where do I start to fix the phone, there seem to be a fix for the issue.
Unrooted using latest stock Android 5.0.2 and Sense 6.0.
eramik said:
A while ago I bought a M7 second hand, and the phone worked nicely while my m8 was being repaired. When the m8 returned I left the M7 unused for some months. Earlier this week I once again needed the M7 as a backup phone. I updated with Lollipop. But quite shortly after the phone started to reboot and couldn't find network/ recognize SIM. As thought I would be warranty left I tried to look up IMEI and didn't find any.
After briefly searching the net it seems like all other phones with this issue have been rooted. As long as I've owned the phone I haven't rooted the phone, but the previous owner might have done it. So I wonder if the imei could have been wiped if the phone never have been rooted. If that's unlikely the previous owner probaly have rooted the phone and that would surely void the warranty.
Where do I start to fix the phone, there seem to be a fix for the issue.
Unrooted using latest stock Android 5.0.2 and Sense 6.0.
Click to expand...
Click to collapse
Restore the phone back to stock using the ruu that match your version, if not solved by this then its probably an hardware fault.
alray said:
Restore the phone back to stock using the ruu that match your version, if not solved by this then its probably an hardware fault.
Click to expand...
Click to collapse
Thanks, I've been searching.
And it seems like htc1guru's guide to return to stock would be able to help me (can't link due to being restricted cause of to few posts).
How do I find the correct RUU, I've not been able to find out?
A couple of other questions.
Currently the phone is UNROOTED, I'm I able to check if has been rooted previously and have S-Off?
eramik said:
Thanks, I've been searching.
And it seems like htc1guru's guide to return to stock would be able to help me (can't link due to being restricted cause of to few posts).
How do I find the correct RUU, I've not been able to find out?
A couple of other questions.
Currently the phone is UNROOTED, I'm I able to check if has been rooted previously and have S-Off?
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" so we can know the relevant info about your phone. Remove imei and s/n before posting
alray said:
Post the output of "fastboot getvar all" so we can know the relevant info about your phone. Remove imei and s/n before posting
Click to expand...
Click to collapse
Took some time, but here we go.
Soemthing strange happend doing the fastboot thing.
After I've finished, the phone asked for a SIM card. And the IMEI restored. But overnight the phone restarted and IMEI disappeared once again.
eramik said:
Soemthing strange happend doing the fastboot thing.
After I've finished, the phone asked for a SIM card. And the IMEI restored. But overnight the phone restarted and IMEI disappeared once again.
Click to expand...
Click to collapse
It might be a defective sim card or sim tray, check with your operator for a new sim card.
alray said:
It might be a defective sim card or sim tray, check with your operator for a new sim card.
Click to expand...
Click to collapse
Definitivly not SIM card related. I've crosschecked SIM card in another phone. I doubt it's the SIM tray, as the problem is only active when the IMEI number falls out. I think I'll try to restore back to stock. Are you able to identify the correct RUU?
Do I need to root the phone to install a clean stock?
eramik said:
Definitivly not SIM card related. I've crosschecked SIM card in another phone. I doubt it's the SIM tray, as the problem is only active when the IMEI number falls out. I think I'll try to restore back to stock. Are you able to identify the correct RUU?
Do I need to root the phone to install a clean stock?
Click to expand...
Click to collapse
Yep you'll need the 7.19.401.22 ruu.zip and you are lucky because I uploaded it earlier this week, it was not available anywhere before
As your phone is S-ON make sure to relock your bootloader before flashing the ruu (if not already locked or re-locked):
Code:
fastboot oem lock
then using htc_fastboot.exe (normal fastboot.exe from the android sdk won't flash new 7.xx.xxx.x RUUs):
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
htc_fastboot reboot
alray said:
Yep you'll need the 7.19.401.22 ruu.zip and you are lucky because I uploaded it earlier this week, it was not available anywhere before
As your phone is S-ON make sure to relock your bootloader before flashing the ruu (if not already locked or re-locked):
Code:
fastboot oem lock
then using htc_fastboot.exe (normal fastboot.exe from the android sdk won't flash new 7.xx.xxx.x RUUs):
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
htc_fastboot reboot
Click to expand...
Click to collapse
Thanks, I'm finished flashing. During the process there was a line which said failed. Don't know which as the fastboot command window don't have the full history. In the end it says OKAY, and the phone reboots. It currently setting up. Should I be worried.
Btw if this works I'll buy you a beer :good:
EDIT: it looks like IMEI still is missing
eramik said:
Thanks, I'm finished flashing. During the process there was a line which said failed. Don't know which as the fastboot command window don't have the full history. In the end it says OKAY, and the phone reboots. It currently setting up. Should I be worried.
Btw if this works I'll buy you a beer :good:
EDIT: it looks like IMEI still is missing
Click to expand...
Click to collapse
Its normal that some lines says failed when flashing a ruu (for example the secondary bootloader) as long as the final result is successful. If your imei is still missing after a ruu, its probably an hardware problem...
Related
So, I bought a second hand Sprint HTC One from Craigslist about a week ago.. First think I did was followed QBKing77's guide on how to unlock bootloader and root. Did that fairly easily, then went through this thread ( http://forum.xda-developers.com/showthread.php?t=2386703 ) to unlock it, had to do the steps in this thread ( http://forum.xda-developers.com/showthread.php?t=2491840 ) to get it to work since I had Android 4.3 and was unsure on how to go backwards to Android 4.2.2. After I got my phone unlocked, I went and got a Net10 SIM card and a month card, activated it, threw it in my One, and.. Nothing. No signal what so ever on GSM. It does recognize my SIM, though. So, I flashed to the original Radio from Sprint ( 1.00.20.0315 ), but still couldn't connect to GSM networks. I called Sprint, and they said my phone was still active on a plan, so I went hunting for a way around that.. I saw some things about flashing to Cricket, but I didn't want that. After relocking my bootloader and trying to RUU a few times, and none of them working, I thought I should update the Firmware. So, I downloaded some UL update for 3.62.401.1 without thinking, flashed it onto my device, and when I booted it up, it started a boot loop. I could navigate the phone for a while, but after about 5 minutes of it being turned on, it would reboot. So, I went into TWRP>wipe>advanced wipe> selected Dalvik Cache, Cache, and System. After that, my system now hangs on the HTC boot screen. I can still get into Bootloader, Fastboot, and Recovery. I tried flashing to TWRP 2.5.0.0, but my touch screen stopped working in TWRP when I did that. I just flashed back to 2.6.3.0, and my touch works again in TWRP. I can't get ADB Sideloader to work.. Currently, my Bootloader is Unlocked, S-Off, superCID, HBoot 1.55.0000, Radio 4A.21.3262.04, OpenDSP v32.120.274.0909, OS 1.29.651.10. That's about all the info I can get from Bootloader. It still says Tampered as well.
What should I do? My first step is to hopefully get back to where I can actually see the homescreen.. After that, I'd like to be able to get my phone to work on GSM.. I don't know if that is possible, though. I haven't found anything about someone having a phone that is still on a Sprint plan and being able to use GSM in the US.
Use this guide
[Complete guide] to SIM unlock your HTC One Sprint for free
BD619 said:
Use this guide
[Complete guide] to SIM unlock your HTC One Sprint for free
Click to expand...
Click to collapse
I already have my phone unlocked. I have the same RUU downloaded from that thread as well, and tried it one more time, and I got Error 155, basically telling me I have the wrong RUU for my device..
Mondragoonest said:
I already have my phone unlocked. I have the same RUU downloaded from that thread as well, and tried it one more time, and I got Error 155, basically telling me I have the wrong RUU for my device..
Click to expand...
Click to collapse
Are you 100% sure you are s-off?
Try a different USB Port
USB 2 if possible.
BD619 said:
Are you 100% sure you are s-off?
Try a different USB Port
USB 2 if possible.
Click to expand...
Click to collapse
I only have two ports on my laptop, and I've tried both. I even tried a usb hub, but that gave me the same error. In my bootloader, it says I'm s-off, I used rumrunner to do it a couple days ago.
Looking to unlock an AT&T version of the HTC One to T-Mobile. I do have an unlock code but it's not working. The phone is rooted and running ARHD 51. I just flashed a different stock rom, tried the code once again but still no luck.
Any suggestions?
WreakerofHavoc said:
Any suggestions?
Click to expand...
Click to collapse
I heard you need to be stock to use a sim-unlock code so you might want to try back to 100% stock then use the code. If it still don't work then maybe you could purchase a new code.
WreakerofHavoc said:
Looking to unlock an AT&T version of the HTC One to T-Mobile. I do have an unlock code but it's not working. The phone is rooted and running ARHD 51. I just flashed a different stock rom, tried the code once again but still no luck.
Click to expand...
Click to collapse
Check your IMEI number and cross reference it with your original to make sure they match. My phone is doing the same thing and it came back from mobile tech videos jtag repair and my numbers are all wrong. Looking for a solution now but my serial number and IMEI numbers are different.
Just a thought, Shot in the dark
alray said:
I heard you need to be stock to use a sim-unlock code so you might want to try back to 100% stock then use the code. If it still don't work then maybe you could purchase a new code.
Click to expand...
Click to collapse
I thought the Rom I used was stock, will try again. Thanks.
cannonofcourse said:
Check your IMEI number and cross reference it with your original to make sure they match. My phone is doing the same thing and it came back from mobile tech videos jtag repair and my numbers are all wrong. Looking for a solution now but my serial number and IMEI numbers are different.
Just a thought, Shot in the dark
Click to expand...
Click to collapse
Will check it out, Thanks.
WreakerofHavoc said:
I thought the Rom I used was stock, will try again. Thanks.
Click to expand...
Click to collapse
Do some searching here (in the Q&A) section, there were quite a few SIM Unlock threads solved (quite a while ago), I can't exactly remember, but it used to be a combo of
1- stock rom (or very close) but matching to firmware version
2- possibly stock recovery
3- possibly locked/relocked bootloader
4- s-off / s-on doesn't matter
I believe number 1 was the most important, can't say/remember about 2 and 3, and quite sure S-Off won't matter.
nkk71 said:
Do some searching here (in the Q&A) section, there were quite a few SIM Unlock threads solved (quite a while ago), I can't exactly remember, but it used to be a combo of
1- stock rom (or very close) but matching to firmware version
2- possibly stock recovery
3- possibly locked/relocked bootloader
4- s-off / s-on doesn't matter
I believe number 1 was the most important, can't say/remember about 2 and 3, and quite sure S-Off won't matter.
Click to expand...
Click to collapse
Ok. Thanks.
restored the original rom, still no luck.
Any suggestions?
Returned to stock rom and recovery, still no luck.
WreakerofHavoc said:
Returned to stock rom and recovery, still no luck.
Click to expand...
Click to collapse
Are you RUU'ing back to stock ?
if your 4.3 try this
http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
if your 4.4 try this
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
clsA said:
Are you RUU'ing back to stock ?
if your 4.3 try this
http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
if your 4.4 try this
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
Haven't RUU'ed to stock yet. S-Off is need for RUU right? Going to S-Off and then try this. Thanks.
WreakerofHavoc said:
Haven't RUU'ed to stock yet. S-Off is need for RUU right? Going to S-Off and then try this. Thanks.
Click to expand...
Click to collapse
you don't need s-off, you just need to relock the bootloader
Hmmm still no luck. Been working at this for a while now, not sure what the problem is. Selling it is the only solution I can think of right now, but there must be a way to unlock this for my carrier.
Hello. I have a similar issue, so I don't think I should create another topic.
I just purchased a 64gb HTC One and purchased the unlock code from the same vendor as always. I was always able to unlock other devices (One XL, One X+, Windows phone 8X) easily, and even other Ones, since this is my fouth (first one I gave to my brother, second slipped off my pocket while in a tunnel riding my motorcycle and the third is 32gb, so I decided to sell it and buy a 64gb).
This one is used like new, everything stock, s-on, nothing unusual. Well, except the led seems to be smaller (very hard to see the red dot while charging) and the system may be newer, since it doens't find any update available.
But the code doesn't work. I tried twice thinking I could be misspelling the numbers, but returned wrong anyway.
So...
1-What happens if I try again and it returns wrong, since it's showing it's my last try?
2-Any clue?
Thanks in advance.
Does your phone work on any network? What carrier is it branded?
Best thing is to email (carrier) support and get a code from them.
This thread is for devices that have a security cross reference back end problems.
Does your phone say it accepts the code then restarts then asks for the code again?
Sent from my unknown using xda app-developers app
mefxes said:
Hello. I have a similar issue, so I don't think I should create another topic.
I just purchased a 64gb HTC One and purchased the unlock code from the same vendor as always. I was always able to unlock other devices (One XL, One X+, Windows phone 8X) easily, and even other Ones, since this is my fouth (first one I gave to my brother, second slipped off my pocket while in a tunnel riding my motorcycle and the third is 32gb, so I decided to sell it and buy a 64gb).
This one is used like new, everything stock, s-on, nothing unusual. Well, except the led seems to be smaller (very hard to see the red dot while charging) and the system may be newer, since it doens't find any update available.
But the code doesn't work. I tried twice thinking I could be misspelling the numbers, but returned wrong anyway.
So...
1-What happens if I try again and it returns wrong, since it's showing it's my last try?
2-Any clue?
Thanks in advance.
Click to expand...
Click to collapse
In my experience, I'm not getting anything showing my number of attempts or last attempt. I've tried the unlock code about 8-10 times on different roms stock and non stock and stock recovery. I really have no idea.
WreakerofHavoc said:
In my experience, I'm not getting anything showing my number of attempts or last attempt. I've tried the unlock code about 8-10 times on different roms stock and non stock and stock recovery. I really have no idea.
Click to expand...
Click to collapse
Thanks for your answer.
All my HTCs always shown a counter.
Today, after restoring the phone to stock ruu, it wasn't showing any counter anymore, so I decided to try again the code I purchased (and other code sellers confirmed) and it worked.
Very strange... but now it's unlocked.
mefxes said:
Thanks for your answer.
All my HTCs always shown a counter.
Today, after restoring the phone to stock ruu, it wasn't showing any counter anymore, so I decided to try again the code I purchased (and other code sellers confirmed) and it worked.
Very strange... but now it's unlocked.
Click to expand...
Click to collapse
You have the at&t version too? Can you link me to the ruu you used?
nkk71 said:
Do some searching here (in the Q&A) section, there were quite a few SIM Unlock threads solved (quite a while ago), I can't exactly remember, but it used to be a combo of
1- stock rom (or very close) but matching to firmware version
2- possibly stock recovery
3- possibly locked/relocked bootloader
4- s-off / s-on doesn't matter
I believe number 1 was the most important, can't say/remember about 2 and 3, and quite sure S-Off won't matter.
Click to expand...
Click to collapse
After a lot of painstaking effort, I managed to flash a stock RUU, got back to a stock recovery, and locked the bootloader. Got the same unlock code from two separate vendors. No dice. Incredibly frustrating, don't know what's wrong with my phone but now I have to sell it.
850csi said:
After a lot of painstaking effort, I managed to flash a stock RUU, got back to a stock recovery, and locked the bootloader. Got the same unlock code from two separate vendors. No dice. Incredibly frustrating, don't know what's wrong with my phone but now I have to sell it.
Click to expand...
Click to collapse
well you can sim-unlock using the sieempi method instead of the unlock code, like many others successfully did
http://forum.xda-developers.com/showpost.php?p=53043418&postcount=601
Hi so basically my One M8 for Sprint is COMPLETELY BRICKED! The phone cannot be repaired as far as I know because it is not S-Off and I can only boot into boot loader.
Alright so here's the situation, I am going to setup a repair and my options are:
1. I send the phone in and they repair the phone.
2. I pay $20, ship my phone and after DIAGNOSTICS they send me a replacement phone NOT the original one.
3. I pay $30 BUT they ship me the phone first and can charge me full price if they reject my claim without my approval.
What do you guys think would be the best option? and what should I say is the reason I need the repair? Should I just say something like the speakers are not clear or the headphone jack doesn't work?
When I spoke with the rep it sounded like they are more concerned about any hardware defects rather than software but she did say any unauthorized software usage will result in denied repair.
Also, keep in mind the phone will only boot into BOOTLOADER and has the "Tampered" "Relocked" and "Security Warning" banner.
Thankyou.
YungMoola15 said:
Hi so basically my One M8 for Sprint is COMPLETELY BRICKED! The phone cannot be repaired as far as I know because it is not S-Off and I can only boot into boot loader.
Alright so here's the situation, I am going to setup a repair and my options are:
1. I send the phone in and they repair the phone.
2. I pay $20, ship my phone and after DIAGNOSTICS they send me a replacement phone NOT the original one.
3. I pay $30 BUT they ship me the phone first and can charge me full price if they reject my claim without my approval.
What do you guys think would be the best option? and what should I say is the reason I need the repair? Should I just say something like the speakers are not clear or the headphone jack doesn't work?
When I spoke with the rep it sounded like they are more concerned about any hardware defects rather than software but she did say any unauthorized software usage will result in denied repair.
Also, keep in mind the phone will only boot into BOOTLOADER and has the "Tampered" "Relocked" and "Security Warning" banner.
Thankyou.
Click to expand...
Click to collapse
If you can boot into the bootloader your m8 is NOT COMPLETELY BRICKED !..... you can try unlocking the bootloader again, reflashing a custom recovery and a rom.
He will need to pull the boot.img from the Rom since he is not s off.
Your phone is not bricked. By any chance did you do a backup before flashing a new Rom??
Sent from my HTC6525LVW using XDA Premium HD app
rider5512 said:
If you can boot into the bootloader your m8 is NOT COMPLETELY BRICKED !..... you can try unlocking the bootloader again, reflashing a custom recovery and a rom.
Click to expand...
Click to collapse
lucky_strike33 said:
He will need to pull the boot.img from the Rom since he is not s off.
Your phone is not bricked. By any chance did you do a backup before flashing a new Rom??
Sent from my HTC6525LVW using XDA Premium HD app
Click to expand...
Click to collapse
OMG You guys just gave me so much hope. If you one of you guys could please me I am willing to compensate for your time. I was an iPhone user previous to this so I am not too knowledgeable but I can definitely follow directions. I had a M7 a year ago and similar thing happened to it but I was able to fix it with the RUU but not this time.
If you guys could just look over my previous thread to give you an idea of whats going on i would much appreciate it.
http://forum.xda-developers.com/htc...-isnt-sprint-m8-factory-t2819981/post54300608
lucky_strike33 said:
He will need to pull the boot.img from the Rom since he is not s off.
Your phone is not bricked. By any chance did you do a backup before flashing a new Rom??
Sent from my HTC6525LVW using XDA Premium HD app
Click to expand...
Click to collapse
There are no backup. Please help me
YungMoola15 said:
There are no backup. Please help me
Click to expand...
Click to collapse
I believe there is a backup for you to use here : http://forum.xda-developers.com/showthread.php?t=2736048
The problem is you relocked the bootloader (as mentioned in your other post).
Have you try to get unlock_code from HTC ? I don't remember whether you can re-unlock the phone without a proper OS but worth a try.
What's your CID as I can't find it in other post.
YungMoola15 said:
There are no backup. Please help me
Click to expand...
Click to collapse
Go to this link here and find the link to the 1.54.651.10 RUU (do not do this if you updated to the most recent update that added WiFi calling or if you have a Harman/Kardon version. There are links to the HK RUU's at this same link). Follow the instructions listed at that link to run the RUU. Afterwards your phone should be working fine.
This thread here may also be useful to you.
ckpv5 said:
I believe there is a backup for you to use here : http://forum.xda-developers.com/showthread.php?t=2736048
The problem is you relocked the bootloader (as mentioned in your other post).
Have you try to get unlock_code from HTC ? I don't remember whether you can re-unlock the phone without a proper OS but worth a try.
What's your CID as I can't find it in other post.
Click to expand...
Click to collapse
Damn F, the bootloader was unlocked before and also had TWRP recovery. My dumbass unrooted it. Here is the info:
YungMoola15 said:
Damn F, the bootloader was unlocked before and also had TWRP recovery. My dumbass unrooted it. Here is the info:
Click to expand...
Click to collapse
Nothing showing
Magnum_Enforcer said:
Nothing showing
Click to expand...
Click to collapse
Magnum_Enforcer said:
Go to this link here and find the link to the 1.54.651.10 RUU (do not do this if you updated to the most recent update that added WiFi calling or if you have a Harman/Kardon version. There are links to the HK RUU's at this same link). Follow the instructions listed at that link to run the RUU. Afterwards your phone should be working fine.
This thread here may also be useful to you.
Click to expand...
Click to collapse
I am really sorry but I can't post right away because XDA hasn't approved me so I only post 5 minutes between.
Don't I have to S-off for the SD card method?
Here's the pic
YungMoola15 said:
I am really sorry but I can't post right away because XDA hasn't approved me so I only post 5 minutes between.
Don't I have to S-off for the SD card method?
Here's the pic
Click to expand...
Click to collapse
You shouldn't, no. But you can also run it from your PC. Hit the second link in my sig and scroll down to the RUU section. I have instructions posted there on how to run the RUU from your PC.
Magnum_Enforcer said:
You shouldn't, no. But you can also run it from your PC. Hit the second link in my sig and scroll down to the RUU section. I have instructions posted there on how to run the RUU from your PC.
Click to expand...
Click to collapse
Hi i am probably an idiot but is there a RUU for my phone? From the pic I uploaded do you know which ruu version I need? Since I am not S-off it has to be the exact version and the instruction you gave said:
"To run a RUU, simply download the RUU you wish to install to your PC, then connect your phone and PC via USB cable. Once connected, simply double-click the RUU file on your computer to start the installer, then follow the on-screen instructions. Normally, a RUU is run while the phone is booted to the OS but alternatively, can be run while the phone is connected to the computer via Fastboot USB mode. If your device is S-on you will need to relock your bootloader to run a RUU. Use the command "fastboot oem lock" to relock your bootloader (without quotation marks)."
But even after relocking my bootloader and using the 1.54.654.9 RUU .exe I get the error 131 on stage 1/7 Sending Signature. Please see the attached pics. BTW you don't know how much I appreciate your help and you will be compensated.
YungMoola15 said:
Hi i am probably an idiot but is there a RUU for my phone? From the pic I uploaded do you know which ruu version I need? Since I am not S-off it has to be the exact version and the instruction you gave said:
"To run a RUU, simply download the RUU you wish to install to your PC, then connect your phone and PC via USB cable. Once connected, simply double-click the RUU file on your computer to start the installer, then follow the on-screen instructions. Normally, a RUU is run while the phone is booted to the OS but alternatively, can be run while the phone is connected to the computer via Fastboot USB mode. If your device is S-on you will need to relock your bootloader to run a RUU. Use the command "fastboot oem lock" to relock your bootloader (without quotation marks)."
But even after relocking my bootloader and using the 1.54.654.9 RUU .exe I get the error 131 on stage 1/7 Sending Signature. Please see the attached pics. BTW you don't know how much I appreciate your help and you will be compensated.
Click to expand...
Click to collapse
Use the RUU for the 1.54.651.10 update as I previously mentioned. This update is newer than the current software version you have. You can upgrade while S-on, you just can't go backwards (unless you're S-off). The RUU can be found in this post along with installation instructions. Try the install method that's mentioned in the post and then if that doesn't work try the PC method. If using the PC method make sure you see "Fastboot USB" hightlighted in red above the bootloader menu screen prior to running the RUU. This means that your phone and PC are properly connected.
You may also find this guide useful.
Magnum_Enforcer said:
Use the RUU for the 1.54.651.10 update as I previously mentioned. This update is newer than the current software version you have. You can upgrade while S-on, you just can't go backwards (unless you're S-off). The RUU can be found in this post along with installation instructions. Try the install method that's mentioned in the post and then if that doesn't work try the PC method. If using the PC method make sure you see "Fastboot USB" hightlighted in red above the bootloader menu screen prior to running the RUU. This means that your phone and PC are properly connected.
You may also find this guide useful.
Click to expand...
Click to collapse
I am in the process of doing the SD Card method (Transferring the file) I will update you. Thank you so much for helping me I really appreciate it brother.
YungMoola15 said:
I am in the process of doing the SD Card method (Transferring the file) I will update you. Thank you so much for helping me I really appreciate it brother.
Click to expand...
Click to collapse
Glad to help. Use that method and disregard my instructions for using the PC method and you should be good to go.
I had to get some clarification from OMJ regarding that RUU. Just follow his instructions in his thread.
Magnum_Enforcer said:
Glad to help. Use that method and disregard my instructions for using the PC method and you should be good to go.
I had to get some clarification from OMJ regarding that RUU. Just follow his instructions in his thread.
Click to expand...
Click to collapse
DUDE YOU ARE A F$#KING LEGEND! I've had the phone for a week and finally today when I was ready to send it for warranty and list it on eBay you came to the rescue.
YungMoola15 said:
DUDE YOU ARE A F$#KING LEGEND! I've had the phone for a week and finally today when I was ready to send it for warranty and list it on eBay you came to the rescue.
Click to expand...
Click to collapse
Glad to help:good:
YungMoola15 said:
DUDE YOU ARE A F$#KING LEGEND! I've had the phone for a week and finally today when I was ready to send it for warranty and list it on eBay you came to the rescue.
Click to expand...
Click to collapse
You should have solved your problem earlier should you post this in correct device forum :silly:
Get the latest firmware RUU unlock bootloader fastboot reboot RUU make sure rename zip file to firmware.zip put in platform tools folder in sdk......once in bootloader type command fastboot oem rebootRUU .......phone will reboot with black screen and HTC logo.......type fastboot flash firmware firmware.zip let it's do it's thing....once done fastboot reboot should fix temp brick
Sent from my 831C using XDA Premium 4 mobile app
i need your help, just got an htc one sprint for 90 bucks, i live abroad the US so i was thinking that i can use this phone without any problems as i have been doing with the verizon's phones with the global roaming. But with this when i put the sim card i got the invalid sim card etc, and i was looking the way to unlock it but spent almost all day and it seems that the version running kitkat and with hboot 1.57 can't get downgraded in order tu unlock the sim for use in my country, tired i can't remember what i did wrong that i just have now a bricked phone that can't get the internal storage, can't flash a zip even on sideload cuz i got errors, couldn't get the s off even using the firewater method with a custom rum.
I remember that i used an CM11 Nightless if i am not wrong but when i tried to restore it i got the 0 storage storage. Reading on different pages i just see the restore to the jelly bean version but kitkat i coulnd't get nothing. I am not so noob i had rooted even a Pantech Burst but this is a pain in the ass for me.
So i want to know if i have a brick or if this phone can be saved.
At least i can get to recovery when i unlock the bootloader but of course i can't get storage, tried with cwm and the other one
What i am worried about is that thing of security warning when i relocked the bootloader
Please help :crying:
tonochito said:
i need your help, just got an htc one sprint for 90 bucks, i live abroad the US so i was thinking that i can use this phone without any problems as i have been doing with the verizon's phones with the global roaming. But with this when i put the sim card i got the invalid sim card etc, and i was looking the way to unlock it but spent almost all day and it seems that the version running kitkat and with hboot 1.57 can't get downgraded in order tu unlock the sim for use in my country, tired i can't remember what i did wrong that i just have now a bricked phone that can't get the internal storage, can't flash a zip even on sideload cuz i got errors, couldn't get the s off even using the firewater method with a custom rum.
I remember that i used an CM11 Nightless if i am not wrong but when i tried to restore it i got the 0 storage storage. Reading on different pages i just see the restore to the jelly bean version but kitkat i coulnd't get nothing. I am not so noob i had rooted even a Pantech Burst but this is a pain in the ass for me.
So i want to know if i have a brick or if this phone can be saved.
At least i can get to recovery when i unlock the bootloader but of course i can't get storage, tried with cwm and the other one
What i am worried about is that thing of security warning when i relocked the bootloader
Please help :crying:
Click to expand...
Click to collapse
You probably need to run a RUU to reset your phone. Here is 5.03.651.3 you can use this if your OS is the same or lower since you are still S-ON. On your sim unlock issue, depending if the imei is clear you can contact Sprint for the unlock code via their support site.
majmoz said:
You probably need to run a RUU to reset your phone. Here is 5.03.651.3 you can use this if your OS is the same or lower since you are still S-ON. On your sim unlock issue, depending if the imei is clear you can contact Sprint for the unlock code via their support site.
Click to expand...
Click to collapse
I have already tried that but i had the application has failed to start because its side-by-side configuration is incorrect, i downloaded the first one not the decrypted. Using both versions of windows 7 and 8 32-64 bits, happens the same problem
and for call Sprint i am in Panama, central america and i don't think that they will provide me the unlock code if the phone even is not mine at all it still with the name of the girl who sold me the one
tonochito said:
I have already tried that but i had the application has failed to start because its side-by-side configuration is incorrect, i downloaded the first one not the decrypted. Using both versions of windows 7 and 8 32-64 bits, happens the same problem
and for call Sprint i am in Panama, central america and i don't think that they will provide me the unlock code if the phone even is not mine at all it still with the name of the girl who sold me the one
Click to expand...
Click to collapse
Try to run the firmware 5.03.651.3 just download it, rename to firmware.zip and place in your adb/fastboot folder. Here are the steps for flashing firmware. Since you are S-ON make sure your bootloader is locked/relocked.
In bootloader/FASTBOOT USB type in the command window:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Then:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
If the firmware flashes successfully, then I would try the RUU again.
Finally i made it came back but i still with the problem of the sim card, reading around the web it seems that with the hboot 1.57 is not yet possible the roaming as was possible with others like 1.56 or less, and i don't wanna have that pain again of what happens this weekend
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
mlw4428 said:
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
Click to expand...
Click to collapse
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
According to jcase relocking the bootloader it still shows a modified status code. Your warranty is permanently voided.
Are you on an Edge plan? Otherwise I don't know why you would be returning the phone to upgrade. Also not sure what their rules are on permanently modifying the software of one of these essentially "lease-to-own" devices, so might want to check the terms and conditions if this applies to you. If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Sent from my XT1254 using Tapatalk
SpyderPride said:
If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Click to expand...
Click to collapse
A bootloader unlocked, rooted XT1254 would be more valuable to a buyer than one locked down. You've already done all the hard work.
TheSt33v said:
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
Click to expand...
Click to collapse
Heya so I'm in a serious bind.
I skipped your step 1 and locked my bootloader. I have an unlocked bootloader. I recently upgraded through the normal verizon pushed update the marshmallow update. Anyhow. I now want to return the phone for an upgrade and well... I locked the bootloader. Then turn the phone off and turned it back on and it now says locked, but it says failed to validate system image. I then got freaked out and downloaded all the step 1 files and tried to flash the stock rom (which i already had installed!) and that doesn't seem to work. Did I brick my phone? Is there any way to get it working now that it is locked with any kind of android at all?
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
TheSt33v said:
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
droidfun1 said:
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
Click to expand...
Click to collapse
Strange. As far as I understand it, RSDlite just automates fastboot, so even if you're using RSDlite, you're actually using fastboot. Whatever works though.
As for the unlocked bootloader message, see my response to that post you made.