Back 2 Stock Help - Sprint HTC One (M7)

Im taking my silver HTC One back because my camera is jacked up along with some signal issues. So im getting the black version But I need to return it back to stock. I'm guessing i start off by flashing my original nandroid back up. Im guessing next would be relocking the bootloader?

Mr.Muscles said:
Im taking my silver HTC One back because my camera is jacked up along with some signal issues. So im getting the black version But I need to return it back to stock. I'm guessing i start off by flashing my original nandroid back up. Im guessing next would be relocking the bootloader?
Click to expand...
Click to collapse
put it into fastboot, run the command prompt "fastboot oem lock" and then the bootloader should then say "relocked" and will still say "tampered" too, then run the RUU that OMJ has posted in the development thread and then you will be back to stock, your "tampered" flag will be gone but the "relocked" will still be present

make sure you have USB debugging on.
Download the AIO Tool Kit and extract. anywhere
Hasoons AIO Toolkit
Download the Sprint_HTC_One_m7wls_1.29.651.7_encrypted_ROM.zip and rename it to something short such as lol.zip(that's what I used, just rename it lol, not lol.zip, if you rename to lol.zip it will show up as lol.zip.zip.) and place it at the root of your c:/ drive, so c:/lol.zip
Navigate to the AIO toolkit folder you extracted, Open the One.exe. At the bottom, click reboot into bootloader and then do command.
Hold shift and right click then click Open Command Window Here.
when the command line opens up type
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip c:/lol.zip
If you get a message about flushing, then retype the last command, "fastboot flash zip c:/lol.zip"and it should work

Thank you so much guys. At work right now and will do as soon as I get home.

Will you still have the relocked if you do it this way? If you send a phone back that says relocked will sprint charge you or will they even notice.
youkosnake said:
make sure you have USB debugging on.
Download the AIO Tool Kit and extract. anywhere
Hasoons AIO Toolkit
Download the Sprint_HTC_One_m7wls_1.29.651.7_encrypted_ROM.zip and rename it to something short such as lol.zip(that's what I used, just rename it lol, not lol.zip, if you rename to lol.zip it will show up as lol.zip.zip.) and place it at the root of your c:/ drive, so c:/lol.zip
Navigate to the AIO toolkit folder you extracted, Open the One.exe. At the bottom, click reboot into bootloader and then do command.
Hold shift and right click then click Open Command Window Here.
when the command line opens up type
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip c:/lol.zip
If you get a message about flushing, then retype the last command, "fastboot flash zip c:/lol.zip"and it should work
Click to expand...
Click to collapse

toadkiller said:
Will you still have the relocked if you do it this way? If you send a phone back that says relocked will sprint charge you or will they even notice.
Click to expand...
Click to collapse
yes it will still say relocked in the bootloader but most of the time sprint doesnt look unless you are returning it bc its defective, if you are returning it just to return it and will pay the $35 restocking fee then they shouldnt look, i never do and im a tech who deals with the returned phones

Yeah mine is going back because of the speakers, they crackle. The replacement doesnt. Oh well Ill see what happens.
LymeWire said:
yes it will still say relocked in the bootloader but most of the time sprint doesnt look unless you are returning it bc its defective, if you are returning it just to return it and will pay the $35 restocking fee then they shouldnt look, i never do and im a tech who deals with the returned phones
Click to expand...
Click to collapse

LymeWire said:
yes it will still say relocked in the bootloader but most of the time sprint doesnt look unless you are returning it bc its defective, if you are returning it just to return it and will pay the $35 restocking fee then they shouldnt look, i never do and im a tech who deals with the returned phones
Click to expand...
Click to collapse
I couldn't get it to stock so I said f it. I hope they don't look at it. I'm sure I'll be paying for it later though.
Sent from my HTCONE using xda app-developers app

Related

[Q] [UPDATE WITH SOLUTION] RUU 155 Error with HTC ONE Developer Edition

I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Gotta re lock your bootloader
fastboot oem lock
I got relock it even though it came unlocked? How would I unlock it again since I don't have the tokens from HTC development, or is the ruu gonna do that by itself.
Sent from my HTC One using Tapatalk 2
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA Z(1.29.1540.16) to the latest which I cant get an RUU for. The RUU available is 1.29.1540.3 no other available. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
All I can see now is a scren that says:
***TAMPERED***
***RELOCKED***
bunch of numbers and letters in green and
RUU in orange
schn1tt3r said:
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA to the latest which I cant get an RUU for. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
Click to expand...
Click to collapse
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Bosnazmaj said:
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Click to expand...
Click to collapse
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
schn1tt3r said:
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
Click to expand...
Click to collapse
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Bosnazmaj said:
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Click to expand...
Click to collapse
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
I also have same phone de it shouldnt be tamperd relocked it should be only relocked
Sent from my HTC One using xda app-developers app
I find it funny now far Computer OS's have come and yet we always have to go back to good old DOS Command Prompt to fix things.
BTW, my phone now has bootloader RELOCKED due to the fastboot oem lock command, should I send the phone back just like that or unlock bootloader before sending it back?
I guess to Unlock bootloader again, I have to follow same instructions as if it were an AT&T version right? Did you UNLOCK yours again OP?
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yes, that is the reason I was doing all this restoring. I had ROOTed it to install AdAway. Ads is the only major drawback when compared to iOS (this is my first Android). When you see a gray image on my phone, there are 3 sort of water drops. Like between the touch screen and LCD.
Well, I am exchanging it actually. I like the HTC One a lot. It has a tiny gap, but I dont care about that much, the weird discoloration on the sceen, though, I do mind.
That makes sense.
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Click to expand...
Click to collapse
Thank you. This was very helpful.
Glad I could help
Sent from my HTC One using Tapatalk 2
schn1tt3r said:
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
Click to expand...
Click to collapse
THANK YOU MAN!!!!!!!! You just saved me. I had the same problem except I had OTA .17 and trying to flash .16. My device was all jacked up but it's back to original.
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
.........
Click to expand...
Click to collapse
Bosnazmaj - thank you for this wonderful write-up & knowledge. I have a Dev edition myself. Sometime ago, I got into charging issues. Initially, assuming it to be software issues, I thought I'd run the RUU. So, like you, I too figured out that I have to lock my bootloader. Ran the RUU....long story short, found out that I have to give my phone for repairs (turned out to be a hardware issue).
So, the point I am trying to make is that, if we unlock the bootloader, certain apps (like flashlight, sound recorder etc) seems to get deleted. While this, on it's own, might not sound too alarming....the problem is, if these apps are not present, then the OTA does not & will not get applied as the OTA says that these apps have to be present. I am not sure how to unlock the bootloader without losing any apps.
Any knowledge / information on this is MOST appreciated.
Actually I used titanium backup to back those apps that disappear during root before I unlocked anything. Then once I rooted and unlocked I just restored them back with titanium and all was fine. But in reality you don't want to so an ota when you are rooted as you might loose root.
Sent from my HTC One using Tapatalk 2
Can't you re-unlock the phone using following command without going through the HTCDev website mess?
Code:
fastboot oem unlock
Just a heads up. I was able to return to stock using the RUU without locking the bootloader. It took a while to figure it out.
I went from ARHD 31 to A stock rom (m7_stock_dev_1.29.1540.16_signed_052313.zip) found on an old thread, also had to find a stock recovery that would work (i think it was the one liked in the ARHD thread) and used the revone S-off method, then applied the latest RUU from the htc dev site .and it installed and the bootloader remained unlocked.
I had to get this thing ready for someone who bought it. They asked if i could return it to stock with S-off. It was a pain in the but, but got it working

Sending My M8 for Repair, Which option should I choose?

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

How to root the HTC Desire 510

Okay guys and gals,
Today I'm gonna be giving you some directions on how to root the HTC Desire 510.
Steps:
1. What your gonna need is your phone, a usb, and a pc. (I used my xperia z as my pc)
2 Your gonna need to download [THIS]. This is the recovery image your gonna need. Just download that and put the file in a folder on your desktop or somewhere you'll remember.
3. Next your gonna want to reboot your phone into fastboot and connect it to your pc.
4. Next on your pc pull up cmd. (search cmd in the start menu) and type "fastboot devices" without the quotes and hit enter. If it shows your device your ready to move on.
5. Now your going to want to change your directory to where the image you downloaded is with a command similar to this "cd C:\users\xxx\desktop\recovery folder". Next rename the image to something simple like flash.img and type this into cmd "fastboot flash recovery flash.img" after doing that you should be able to boot into twrp from the hboot menu on your device.
6. Next on your computer download the su binary zip here. After downloading it reboot your device and copy it to your internal storage and reboot back to your recovery. Then in your recovery go find the supersu-v2.16.zip and flash it then reboot normally. Your device should now be rooted.
Thanks for all your help
cant unlock bootloader!!!! help!!!! please!!!
i know that to root the htc desire 510 first i need to unlock the bootloader, i followed the htc dev steps but when ever im submitting the unlock code nothing happens i just get the screen where i press yes or know but nothing else happens, my bootloader has been relocked yes i know i made a mistake can anyone help please!!!!
htnexx said:
i know that to root the htc desire 510 first i need to unlock the bootloader, i followed the htc dev steps but when ever im submitting the unlock code nothing happens i just get the screen where i press yes or know but nothing else happens, my bootloader has been relocked yes i know i made a mistake can anyone help please!!!!
Click to expand...
Click to collapse
same thing happened to me. does yours look like mine? http://forum.xda-developers.com/desire-510/help/qa-twrp-a11chl-a11ul-32-bit-t2951146 i have pictures posted of what it does when i try to unlock.
exactly!!!! i couldnt upload pics but is the same error mate, i hope somebody can help us...
I'm having problems with the recovery it won't unload the file I rename it recovery.img but still nothing
htnexx said:
exactly!!!! i couldnt upload pics but is the same error mate, i hope somebody can help us...
Click to expand...
Click to collapse
Did you make any progress? Any change?
LarryBoyG said:
Did you make any progress? Any change?
Click to expand...
Click to collapse
no change, im hoping somebody comes with a solution or ideas
Could anyone tell me why when I try to unlock my boot loader and go to get the token it tells me my token length is inccorrect. Is there any reason why this is happening?
oHaiiSquidd said:
Could anyone tell me why when I try to unlock my boot loader and go to get the token it tells me my token length is inccorrect. Is there any reason why this is happening?
Click to expand...
Click to collapse
make sure youre copying from " <<<TOKEN START>>>" to "<<<TOKEN END>>>" , arrows and all.
01keenan10 said:
make sure youre copying from " <<<TOKEN START>>>" to "<<<TOKEN END>>>" , arrows and all.
Click to expand...
Click to collapse
I did do that I tried multiple times. Also when I try to run the fastboot from HTC site it keeps telling me something about missingadbapi.dll
2858
Worked like a charm. Much appreciated
Many Thanks! Phone Rooted! but i had 1 question whats the difference between this recovery.img(10,594kb) and the one on twrp website which is 10,480kb in size. just wondering? thanks
This worked great for me, thanks! It was my first root ever, and I had some guidance along the way, but this thread as well as the one to unlock the bootloader were very useful. The only snag was HTC took forever to email me the key.
Thanks again!
-jason
is there a way to get s-off yet?
Works for HTC Desire with model # 0PCV1?
CurbThePain said:
Okay guys and gals,
Today I'm gonna be giving you some directions on how to root the HTC Desire 510. Basically what your gonna need is your phone, a usb, and a pc. (I used my xperia z as my pc) Over HERE is the recovery image your gonna need. Just look for the download. So download that file and put it in the root of your hard drive. Next your gonna want to reboot your phone into fastboot and connect it to your pc. Next on your pc pull up cmd. (search cmd in the start menu) and type "fastboot devices" without the quotes and hit enter. If it says its not a command or something like that head (here --> http://forum.xda-developers.com/showthread.php?t=2317790) and follow the directions. After that type fastboot devices again and hit enter. If it shows your device your ready to keep moving on. Your going to want to change your directory to where the image you downloaded is with a command similar to this "cd C:". Next rename the image to something simple like img.img and type this into cmd "fastboot flash recovery img.img" after doing that you should be able to boot into twrp from the hboot menu on your device. Next on your computer download the su binary zip here. After downloading it reboot your device and copy it to your internal storage and reboot back to your recovery. Then in your recovery go find the supersu-v2.16.zip and flash it then reboot normally. Your device should now be rooted.
Click to expand...
Click to collapse
I am reading that this seems to work on HTC Desire 510 devices however I know that Boost Mobile had its own little version of the HTC Desire 510 with the model number 0PCV1 and ive read a lot of threads stating that it was unable to be rooted. So before I started to touch anything I was wondering if this for sure will work with my HTC Desire 510 with model number 0PCV1. Thanks.
Have Boost HTC 510 OPCV1 and I'm unlocked and rooted. Only downside is the unlock threw it to s-on and it says tampered in hboot.
dipspit said:
Have Boost HTC 510 OPCV1 and I'm unlocked and rooted. Only downside is the unlock threw it to s-on and it says tampered in hboot.
Click to expand...
Click to collapse
Okay well its good to know rooting is possible. However the downside sounds iffy to me, I guess since Ive never rooted an android device yet. I have previously jailbreak'd an iPhone 5c on iOS 8.1
Does the s-on effect anything? And what about the hboot flagging as tampered?
The downsides is really nothin. I'm on the 510 right now so hope this explains it pretty well: htcdev.com/bootloader/about_unlock_process
dipspit said:
The downsides is really nothin. I'm on the 510 right now so hope this explains it pretty well: htcdev.com/bootloader/about_unlock_process
Click to expand...
Click to collapse
Okay that explains it pretty well to me. My final questions if your hanging around the thread, did you use this original posting to root your device?

Need help from the pros

I got my warranty phone today from Motorola and need to send mine back. The screen is completely blank on it so I can't see anything in order to unrooted, and relocked BL. Motorola has a 500 dollar hold on my credit card until they get my old one back. I'm afraid that because its BL unlocked and rooted they are going to take my 500 bucks. I was told to use Wugs but you have to be able to see the screen to use it with my limited knowledge. If they get it back I'm sure they will be able to see somehow that it's rooted and BL unlocked and I'll lose the 500 bucks meaning this phone costed 900 bucks. Please guys. Help me with this. I already got ripped off on someone selling me a messed up phone and now I'm afraid I'm gonna lose another 500. I will PayPal a gift to anyone who can walk me through this. Thanks
I really don't think you have to worry about the phone being unrooted and bootloader unlocked. Since the screen is not working they will most likely dismantle and reassemble the phone and flash Android 5.1 without taking stock of what was on the phone when they received it.
That's what I'm praying but I was hoping there was a way to do it. I'm sure they know how. That means y'all definitely know how.
Boot to bootloader. From off, hold volume down and press power.
Connect the usb and run "fastboot devices " to confirm connection
Then extract the correct system.img and boot.img for the stock version you should be on. Then fastboot flash them.
Then do a "fastboot oem lock"
All details about how to use fastboot are in nexus 6 general > sticky roll-up thread > adb and fastboot
danarama said:
Boot to bootloader. From off, hold volume down and press power.
Connect the usb and run "fastboot devices " to confirm connection
Then extract the correct system.img and boot.img for the stock version you should be on. Then fastboot flash them.
Then do a "fastboot oem lock"
All details about how to use fastboot are in nexus 6 general > sticky roll-up thread > adb and fastboot
Click to expand...
Click to collapse
Had no choice but to ship it. Lord be with me
electrojas said:
Had no choice but to ship it. Lord be with me
Click to expand...
Click to collapse
If you shiped to Texas they just throw in a bin and refurbish. Don't look at anything.
Man I hope that's the case. Thanks for the hope brother
electrojas said:
Man I hope that's the case. Thanks for the hope brother
Click to expand...
Click to collapse
We had a guy in the threads that was a supervisor at the refurb plant. He said they don't look at them. Most that get denied told Moto up front that it was rooted.

Stock Recovery help

So I have a custom recovery called TWRP, And I want to get back my original stock recovery, I have an HTC Desire 510 Provider is cricket. And i'm also looking forward to re-locking bootloader. I want to install regular updates for my phone and with that custom recovery that I have can not. I may have created a new post which i'm sorry but I really need the help.
AdorableCFW said:
So I have a custom recovery called TWRP, And I want to get back my original stock recovery, I have an HTC Desire 510 Provider is cricket. And i'm also looking forward to re-locking bootloader. I want to install regular updates for my phone and with that custom recovery that I have can not. I may have created a new post which i'm sorry but I really need the help.
Click to expand...
Click to collapse
Just relock the bootlloader and then run the RUU on your computer and it will reset all of it back to stock...
MrMike2182 said:
Just relock the bootlloader and then run the RUU on your computer and it will reset all of it back to stock...
Click to expand...
Click to collapse
You've helped me before that I notice on my other account because I wanted to get back on my stock rom which I thank you for that. Could you explain how to do that?
AdorableCFW said:
You've helped me before that I notice on my other account because I wanted to get back on my stock rom which I thank you for that. Could you explain how to do that?
Click to expand...
Click to collapse
Go on computer then go into your adb and fastboot then open a command window and type fastboot oem lock Make sure your phone is connected to the computer and iin fastboot mode then after you do this just leave the phone there and run the RUU.
MrMike2182 said:
Go on computer then go into your adb and fastboot then open a command window and type fastboot oem lock Make sure your phone is connected to the computer and iin fastboot mode then after you do this just leave the phone there and run the RUU.
Click to expand...
Click to collapse
When I run the ruu, for image version it's blank.
AdorableCFW said:
When I run the ruu, for image version it's blank.
Click to expand...
Click to collapse
I've looked on other parts on the internet about the blank image version, They said go right on ahead and so I did and now it's fixed. Thank you for your help
AdorableCFW said:
I've looked on other parts on the internet about the blank image version, They said go right on ahead and so I did and now it's fixed. Thank you for your help
Click to expand...
Click to collapse
You're welcome.

Categories

Resources