Database Develop

HTC Salsa Bootloader Unlocked!!

HTC has provided official tool to unlock Salsa bootloader, available at http://www.htcdev.com/bootloader/
Go to the website, sign up (if you havent done so), select Your device, Follow the instructions, and enjoy
Note : HBOOT update is required.

mate, let me know what is your RUU before doing the unlock. which part of download section did you take. Because mine, i got none. But i just continued to the fastboot oec, and simply send the code, and voila, its ***unlocked***
so i just wonder, why hboot updated is required since first, i dont get the update even i check it again and again, and second, it still can be unlocked without updating the firmware.

kanded said:
mate, let me know what is your RUU before doing the unlock. which part of download section did you take. Because mine, i got none. But i just continued to the fastboot oec, and simply send the code, and voila, its ***unlocked***
so i just wonder, why hboot updated is required since first, i dont get the update even i check it again and again, and second, it still can be unlocked without updating the firmware.
Click to expand...
Click to collapse
i didnt try it, i just posted the news...
but now i tried and couldnt update the hboot because i am on 1.12.720.3 and it says i need 1.12.720.5, i cant find the update anywhere.. so i just went on and tried the 'fastboot oem get_identifier_token' but i got a command error... i tried 'fastboot oem ?' but the command list didnt include 'get_identifier_token'
how did you do it?? which RUU are you on??

tried this, failed to update hboot, rom image error. basically im unable to update this hboot version.
this is the problem im having all round, i cannot update or revert from this chinese rom im using.
as for the fastboot, no point as i cannot get past stage one lol

why dont you try fastboot?? you might get lucky, kanded said he did it without updating... or is it that HTC is just bullsh**ing everyone bye saying it can be unlocked, but not providing the necessary updates for unlocking??

pachuau86 said:
why dont you try fastboot?? you might get lucky, kanded said he did it without updating... or is it that HTC is just bullsh**ing everyone bye saying it can be unlocked, but not providing the necessary updates for unlocking??
Click to expand...
Click to collapse
tried, i've actually just said, f*** it to it. stay with what we got till someone develops a way around it all.
it requires updating all round just to access the first part!

ic... so whats with kanded ?? how did he do it??? Seems i have to wait some more as i cant get my hands on a clip either.... bummer

pachuau86 said:
ic... so whats with kanded ?? how did he do it??? Seems i have to wait some more as i cant get my hands on a clip either.... bummer
Click to expand...
Click to collapse
don't know,
i do know u have to have all sdk parts installed as im unsure what it needs to run with, that took 2 hrs getting it all.
ive tried again, even skipping to fastboot, still nothing.
but ive already tampered with mine, already has cwm installed, s-off and rooted, with chinese uk o2 rom installed......so i wonder if he's using standard issue rom from scratch, but either way, it may not work on all salsa handsets.
but keep trying if you want. the option to send it us is still there!

man, i want to clarify.
the first time i bought this salsa, it is hTC Asia WWE, with S-ON of course.
there is no English language. fu** with it, so i tried to change into RUU O2 UK, by making my sdcard as a goldcard, and put the RUU files onto it.
Here i tell you the way, the RUU files is exe, right ? You can directly flash it as long as you got goldcard (its not hard to make it, everybody knows that)
Or, if that fail, there is still a way updating the stock rom with RUU. Install the exe, while its popping up in ur windows, open task manager, and you see RUU instalshield wizard is running, right ? now go to process, and see Aruwizard.exe
properties that aruwizard.exe, and open file location. you will see there is a zip "rom.zim"
rename that rom zip into PH11IMG.zip and put it into your sdcard that has been as a goldcard. now do the hboot, it will do the recovery itself. let me know if it works.
after that, go to htcdev, and then next step, no need to download for upgrading, bla bla bla, i got my bin_unlock by emails twice. hahaha.
get helped ? say thanks
---------- Post added at 07:18 AM ---------- Previous post was at 07:08 AM ----------
its for you bigbear, i read in any thread that you got problem with your rom right now, that you wanna go back to your stock from that chinese one rom, confirm me if im right.
you may try the way i've said above.
you know of course i also flash that custom rom you post, but i can get back to my before rom.
this is that we must be carefull. if you wanna get back to the last rom you have, you gotta do backup via recovery. there is a backup and restore section. do the backup, and save your backup (it is in clockwordmod folder) in the safest place.
lets say you wanna get back, just do the restore, and voila, you are in your home sweet home. no problemo at all altough you got big headache because of flashing the wrong rom
this is the way :
1) Format SD card as Fat32
2) Install HTC Sync Drivers. (available at htc.com)
3)Connect Your phone to PC. USB Debugging must on and usb connection type: Only Charging.)
4) Open SimpleGoldCard Tool as a admin
and follow procedure step by step at SimpleGoldcard tool.

works now, thanks to kanded and 0x.shivam.x0

BigBearEvo said:
tried this, failed to update hboot, rom image error. basically im unable to update this hboot version.
this is the problem im having all round, i cannot update or revert from this chinese rom im using.
as for the fastboot, no point as i cannot get past stage one lol
Click to expand...
Click to collapse
How did you get a custom rom running on your phone? I can't root my phone because I don't have access to the clip. Is there any other method?

By going to htcdev and getting my bootloader unlocked. From there its plain sailing
Sent from a 3.5 Sensed Salsa

Yeah i know how to do that. Got my incredible s rooted juwt like that. Rather i installed cm7 and then it got rooted. Do you have any link on hiw to proceed after unlocking the boot loader? Oh and could i have a list of roms for the salsa? Thanks in advance.
XDA FTW

jhon101 said:
Yeah i know how to do that. Got my incredible s rooted juwt like that. Rather i installed cm7 and then it got rooted. Do you have any link on hiw to proceed after unlocking the boot loader? Oh and could i have a list of roms for the salsa? Thanks in advance.
XDA FTW
Click to expand...
Click to collapse
www.wix.com/bigbearevo/salsa everything i know of is there

BigBearEvo said:
www.wix.com/bigbearevo/salsa everything i know of is there
Click to expand...
Click to collapse
Alright thanks man. Appreciated. And good stuff with the site. Lastly, would you happen to know what language should i learn to write a kernel and for a rom?
And yes i pressed the thanks button

To learn kernels and Roms its best to use Ubuntu Linux. And I found finding a Dev that could teach u what u need, I'm still learning but my Ubuntu is offline so I've not progressed any further yet.
Sent from a 3.5 Sensed Salsa

Tried it and its working fine. Thanks to BigBearEvo's site. i could easily flash a 3.5 rom

If you are thinking about upgrading to ICS, READ THIS!

There seems to be an influx of posts with users asking for help after bricking/semi-bricking their phone after upgrading using the ph39img method. Upgrading using the PH39IMG.zip is risky if you don't THOROUGHLY understand the steps, it is a bit complex even for those of us who have flashed numerous times when it was the gingerbread. It is hard to know what you are doing even if you are an expert at flashing roms because it completely different and new process.
With that being said, USE THE RUU TO UPGRADE!
Do not use the PH39IMG to upgrade just because it takes too long to download the RUU file, because there is a HIGH chance that you WILL brick your phone if you accidentally miss just one step in the process.
So do yourself a favor, be smart and use the RUU.
Official RUU from AT&T
-make sure to back up your files (that includes internal storage)-

Please forgive me for asking but can you point me to the RUU?
Also, I am unlocked & rooted...can you give me (or point me to) the "dummies simple guide" to flashing with the RUU?
I have flashed my older Captivate many times and many previous WM6 phones but not up on the HTC and Vivid yet... I apologize!
Sent from my HTC Vivid using Tapatalk

We can probably close this thread...lol. Good intentions, bad timing.

mark72501 said:
Please forgive me for asking but can you point me to the RUU?
Also, I am unlocked & rooted...can you give me (or point me to) the "dummies simple guide" to flashing with the RUU?
I have flashed my older Captivate many times and many previous WM6 phones but not up on the HTC and Vivid yet... I apologize!
Sent from my HTC Vivid using Tapatalk
Click to expand...
Click to collapse
No problem, this post was intended to get you to use the RUU if you are not familiar with the HBOOT upgrade process.
http://forum.xda-developers.com/showthread.php?t=1338919
To run the RUU, you must relock your bootloader
anthromatt said:
We can probably close this thread...lol. Good intentions, bad timing.
Click to expand...
Click to collapse
Yeah, it looks like if you are on stock, you can now update through phone AT&T software update in settings. Hopefully it's a much smoother upgrading process.

dizzyraider said:
Yeah, it looks like if you are on stock, you can now update through phone AT&T software update in settings. Hopefully it's a much smoother upgrading process.
Click to expand...
Click to collapse
I am on stock ROM that came on the phone, just unlocked and rooted and most of the bloat gone...I thought I read somewhere a couple of days ago that it wouldn't give it to me OTA unless I re-locked. Is this correct?
I guess I could try it but it's middle of the day, I'm at work...can't mess with it right now so just checking!
Thank you

Correct...

mark72501 said:
I am on stock ROM that came on the phone, just unlocked and rooted and most of the bloat gone...I thought I read somewhere a couple of days ago that it wouldn't give it to me OTA unless I re-locked. Is this correct?
I guess I could try it but it's middle of the day, I'm at work...can't mess with it right now so just checking!
Thank you
Click to expand...
Click to collapse
I believe you will need to Re-Lock. I'm guessing that OTA and just running the EXE will result in the same thing if you are unlocked. No Go.

This probably isn't the proper thread to post this in but it is somewhat related.
Got home tonight and wanted to do this. Ran across the below link and it sounded detailed and easy enough...so...I decided to try it.
Well, I got down to step 15 and after that it automatically rebooted or something and it seems from there I can't do step 16, 17 and on. I can get to HBOOT but it never asked to update the PH39IMG.
What do I need to do now? Now if I try to boot the phone up I get stuck at the HTC splash screen.
Oops...forgot link: http://www.androidauthority.com/vivid-4g-pre-rooted-ics-htc-sense-3-6-63538/
Thanks!

mark72501 said:
This probably isn't the proper thread to post this in but it is somewhat related.
Got home tonight and wanted to do this. Ran across the below link and it sounded detailed and easy enough...so...I decided to try it.
Well, I got down to step 15 and after that it automatically rebooted or something and it seems from there I can't do step 16, 17 and on. I can get to HBOOT but it never asked to update the PH39IMG.
What do I need to do now? Now if I try to boot the phone up I get stuck at the HTC splash screen.
Oops...forgot link: http://www.androidauthority.com/vivid-4g-pre-rooted-ics-htc-sense-3-6-63538/
Thanks!
Click to expand...
Click to collapse
Pull out the battery them put it back in (Before starting up again, make sure the file is downloaded correctly in the sd card) Power up by pressing power and vol down, them you can try to update again.

dizzyraider said:
Pull out the battery them put it back in (Before starting up again, make sure the file is downloaded correctly in the sd card) Power up by pressing power and vol down, them you can try to update again.
Click to expand...
Click to collapse
Do you mean the PH39IMG file? And I'm not sure how to check that since I can't connect the phone to the computer after booted and see it as a drive. All I can get to is fastboot.
I did notice that on the site with the directions it says the PH39IMG file is 35.6MB and I d/l'd it twice and it shows 35.5MB on my computer. Not sure if that means anything or not.
Is there a way to see what's on the SD card without the phone booting?

mark72501 said:
Do you mean the PH39IMG file? And I'm not sure how to check that since I can't connect the phone to the computer after booted and see it as a drive. All I can get to is fastboot.
I did notice that on the site with the directions it says the PH39IMG file is 35.6MB and I d/l'd it twice and it shows 35.5MB on my computer. Not sure if that means anything or not.
Is there a way to see what's on the SD card without the phone booting?
Click to expand...
Click to collapse
Yes, take out the card and use an external sd card reader. That's how i would do it

dizzyraider said:
Yes, take out the card and use an external sd card reader. That's how i would do it
Click to expand...
Click to collapse
Ah...that would be the, or one of the, problem then...I put it on the phone. I'm accustomed to that from the phone I came from where the phone memory was often referred to as the SD card (because it was one it just couldn't be removed). I have no SD card in my phone that is removable. Yeah......

[Q] Changing CID back to original

Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)

stanny2k said:
Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)
Click to expand...
Click to collapse
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers

nkk71 said:
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers
Click to expand...
Click to collapse
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..

stanny2k said:
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..
Click to expand...
Click to collapse
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.

nkk71 said:
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.
Click to expand...
Click to collapse
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"

stanny2k said:
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
Click to expand...
Click to collapse
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Also, please follow the instruction properly, no jumping, skipping or adding steps
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
stanny2k said:
Oh, and have a "thanks"
Click to expand...
Click to collapse
Thanks, I like those

nkk71 said:
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Click to expand...
Click to collapse
Ok, I'll grab this!
nkk71 said:
Also, please follow the instruction properly, no jumping, skipping or adding steps
Click to expand...
Click to collapse
Will do! Don't worry, word for word!
nkk71 said:
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
Click to expand...
Click to collapse
Noted.
nkk71 said:
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
Click to expand...
Click to collapse
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
nkk71 said:
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
Click to expand...
Click to collapse
Appreciate it, thank you

stanny2k said:
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
Click to expand...
Click to collapse
yep, exactly, after the 1st OTA, your phone will be 100% "out-of-the-box"; once the OTA updates successfully it will mean
1- your entire firmware was updated (hboot, recovery, kernel, radio, etc)
2- your ROM will also be updated, proving everything is 100%
otherwise, the OTA would not be able to complete.
Now due to a patch in later hboots (in particular 1.55 as far as i know), going from s-off to s-on, will (after a few reboots) result in "tamper detected - rebooting" and TAMPERED is back.
so in summary, if you really need to go S-On, you do so after first successful OTA (using the command mentioned in my guide), and then you can take any OTAs you like.
hope that makes sense

Perfect sense!
I'll have a bash at this tonight! Thanks a lot

Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan

stanny2k said:
Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
Click to expand...
Click to collapse
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks

nkk71 said:
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
Click to expand...
Click to collapse
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.

stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.

nkk71 said:
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.
Click to expand...
Click to collapse
Yup, I did fastboot erase cache before and after flashing it, both were successful as well. I didnt check the MD5, I just installed it after I downloaded it.. it was midnight by the time I got that far! I was tired!
Yeah and thanks a lot for your help mate. Really appreciate it.
I'll let you know the outcome with HTC Hopefully they find nothing untoward!

stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself

nkk71 said:
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself
Click to expand...
Click to collapse
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!

stanny2k said:
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!
Click to expand...
Click to collapse
finger gymnastics :laugh:

stanny2k said:
Well, that was an eventful evening
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
Click to expand...
Click to collapse
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!

nkk71 said:
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!
Click to expand...
Click to collapse
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it

stanny2k said:
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it
Click to expand...
Click to collapse
problem is with the CWM i recommended, works just fine when flashed, but when using "fastboot boot CWM.img" looks like 6.0.3.2 doesnt work properly with adb, 6.0.4.5 on the other hand works with "fastboot boot"
I'll update my guide with some more "visuals" whenever I get a chance....

Black Screen, Phone On, But No Backlight

Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Ok so Tuesday night I was going to bed (phone still on and working) and plugged my phone in to the charger to charge for the night as I usually do every night. Wake up in the morning and hit the power button to unlock the phone and to my surprise the display doesn't come on. As I said I've never dropped this phone in the entire 9 months I've had it, nor has it ever gotten wet.
This is NOT the first time this has happened either. I've had the phone display flicker on/off and after a couple times it will just stay on. It's also went off and I've fixed it by holding a light to the sensor in the top left and it came on. This time I'm not having any luck.
Please help! It's rooted, with custom ROM, and boot unlocked, therefore I cannot send it in for repair as warranty is voided. I've tried restoring it back to stock the best I can via mirror Android to PC program, but it's very difficult. I've restored it once before, I just don't get why it's not working again with me holding the light to the sensor. Any help and/or suggestions would be greatly aprreciated!! Thank you!

Kev_McCall said:
Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Ok so Tuesday night I was going to bed (phone still on and working) and plugged my phone in to the charger to charge for the night as I usually do every night. Wake up in the morning and hit the power button to unlock the phone and to my surprise the display doesn't come on. As I said I've never dropped this phone in the entire 9 months I've had it, nor has it ever gotten wet.
This is NOT the first time this has happened either. I've had the phone display flicker on/off and after a couple times it will just stay on. It's also went off and I've fixed it by holding a light to the sensor in the top left and it came on. This time I'm not having any luck.
Please help! It's rooted, with custom ROM, and boot unlocked, therefore I cannot send it in for repair as warranty is voided. I've tried restoring it back to stock the best I can via mirror Android to PC program, but it's very difficult. I've restored it once before, I just don't get why it's not working again with me holding the light to the sensor. Any help and/or suggestions would be greatly aprreciated!! Thank you!
Click to expand...
Click to collapse
Well issues like this are common with custom roms. You would need to pull a log cat or DSM message and send it to the developers.

Kev_McCall said:
Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Click to expand...
Click to collapse
If you are not S-OFF, then you will have to relock your bootloader with this command: fastboot oem lock
Then run this RUU 5.14.531.11 That will put you back at stock and if you want to put a custom rom or root you can try it again.

zelendel said:
Well issues like this are common with custom roms. You would need to pull a log cat or DSM message and send it to the developers.
Click to expand...
Click to collapse
Thanks for the reply, so how would I go about pulling log cat and DSM?

majmoz said:
If you are not S-OFF, then you will have to relock your bootloader with this command: fastboot oem lock
Then run this RUU 5.14.531.11 That will put you back at stock and if you want to put a custom rom or root you can try it again.
Click to expand...
Click to collapse
Thanks man! I've tried other RUU's with no luck. So just to be certain, in order to flash an RUU, you need S-Off wit Bootloader locked? Is it not possible to flash RUU with S-On? Going to do this now. I'll let you know. I'll keep you guys updated. Feeling good about this.

Kev_McCall said:
Thanks man! I've tried other RUU's with no luck. So just to be certain, in order to flash an RUU, you need S-Off wit Bootloader locked? No, if you S-OFF you can leave it unlocked.
Is it not possible to flash RUU with S-On? No, if S-ON you can only flash it if your bootloader is locked and the same OS version or higher.
Going to do this now. I'll let you know. I'll keep you guys updated. Feeling good about this.
Click to expand...
Click to collapse
See comments above.

majmoz said:
See comments above.
Click to expand...
Click to collapse
Ok so I succesfully Installed the RUU and back to stock rom, but upon rebooting, my screen did not turn back on. I've read of dozens of other users who have experienced this same thing. I guess the next step would be to fully return it to stock, turning S-On, removing tampered, unrooting, etc, and just returning it for another phone. @majmoz

Kev_McCall said:
Ok so I succesfully Installed the RUU and back to stock rom, but upon rebooting, my screen did not turn back on. I've read of dozens of other users who have experienced this same thing. I guess the next step would be to fully return it to stock, turning S-On, removing tampered, unrooting, etc, and just returning it for another phone. @majmoz
Click to expand...
Click to collapse
If you successfully ran the RUU, then you are stock with a relocked bootloader. The downside is you have to be S-OFF to remove the tampered and to change the "relocked" to "locked".
If you are S-OFF, then you would have to put TWRP 2.6.3.3 or 2.7.1.2 and install this Bootloader Reset Tool. Then flash a stock recovery. You are now completely back to stock.

majmoz said:
If you successfully ran the RUU, then you are stock with a relocked bootloader. The downside is you have to be S-OFF to remove the tampered and to change the "relocked" to "locked".
If you are S-OFF, then you would have to put TWRP 2.6.3.3 or 2.7.1.2 and install this Bootloader Reset Tool. Then flash a stock recovery. You are now completely back to stock.
Click to expand...
Click to collapse
Yea. I turned S-Off before I even ran the RUU. So there's one thing I'm confused about. If I'm trying to return to complete stock state, why would I install Twrp or CWM if those don't come with it? Is there any other way to do this? As I have no back-light and it's been very hard to do all that I've done so far. Screen hasn't come on, so I'm working blind here. Lucky for me I remember where most of the buttons are at and with the help of ADB, I've gotten this far. @majmoz

Kev_McCall said:
Yea. I turned S-Off before I even ran the RUU. So there's one thing I'm confused about. If I'm trying to return to complete stock state, why would I install Twrp or CWM if those don't come with it? Is there any other way to do this? As I have no back-light and it's been very hard to do all that I've done so far. Screen hasn't come on, so I'm working blind here. Lucky for me I remember where most of the buttons are at and with the help of ADB, I've gotten this far. @majmoz
Click to expand...
Click to collapse
Yes, look at nkk71 guide in my signature he has the steps in post 3 or 4. I'm away from the house so I can't post the link.

majmoz said:
Yes, look at nkk71 guide in my signature he has the steps in post 3 or 4. I'm away from the house so I can't post the link.
Click to expand...
Click to collapse
@majmoz
Hey bro thank you so much for the help so far, I really appreciate it. I just have one last problem. I've already talked with HTC and they're going to be sending me a replacement and I have to send my phone back in within 10 days but they said they would be checking for root.
So question 1. When you restore phone to stock ROM via RUU it unroots the phone correct?
Second problem. Now that I've restored the stock rom, usb debugging isn't enabled and I can re-enable it due to not being able to see the screen. So because USB Debugging is not enabled ADB is no longer recognizing it when I run "adb devices"
Because of this I can't turn bootloader, tampered, and lock stats back on. I'm really nervous sending my phone back in like this. I hate to keep bothering you, but you seem to know your stuff a lot more than I, and I'd hate to start a new thread. Thanks again bro.

Kev_McCall said:
@majmoz
So question 1. When you restore phone to stock ROM via RUU it unroots the phone correct?
Second problem. Now that I've restored the stock rom, usb debugging isn't enabled and I can re-enable it due to not being able to see the screen. So because USB Debugging is not enabled ADB is no longer recognizing it when I run "adb devices"
Because of this I can't turn bootloader, tampered, and lock stats back on. I'm really nervous sending my phone back in like this. I hate to keep bothering you, but you seem to know your stuff a lot more than I, and I'd hate to start a new thread. Thanks again bro.
Click to expand...
Click to collapse
1. RUU unroots the phone.
2. Yes, you need USB Debugging enabled and a custom recovery (nkk71 uses CWM).
I have been racking my brain all night. This is a long shot, but if HTC is sending you a replacement before you have to ship yours back then here is an idea. With the replacement phone side by side; memic the commands to open Settings on both phones doing the replacement phone first, then the old phone. The location of the items should be in the same place on both screens. It may take a couple of tries but you seem adapt at reading blank screens. I'm still researching a way to turn it on remotely, but this is the only solution I could come up with presently.
When you get USB Debugging enabled, use nkk71's guide to install CWM on your phone. Then complete the manual steps to remove "Tampered" and to "Locked" the phone. Reboot the phone into bootloader per the instructions. Now we need to put the stock recovery back on the phone. You can get the stock recovery out of the last OTA. Download it to your PC, then open the zip file. Within the zip is the firmware.zip, open it and you will see recovery.img file this is the stock recovery. Just extract it and flash it like you did the custom recovery earlier. Going back to nkk71's guide, complete the fastboot command to return to S-ON. Now you are completely stock with no hint of root.

@majmoz
I'm beast! lol Ok so quick update to my problem. So I got the bright idea to use the Power+Volume Down to take screenshots of my display as I blindly tapped and used that as a guide and moved forward to unlocking developer options, then enabling USB debugging. I can now see my device in ADB once again. Should be pretty cake from here. Thank you so much bro! And also, HTC has agreed to send me a new phone, but I must first send mine in. They would have sent me one first and then I send mine in later, but they wanted to place a $600 credit hold on my card. **** THAT. The rep told me they would be checking for other damages as well as if it rooted.

Kev_McCall said:
@majmoz
I'm beast! lol Ok so quick update to my problem. So I got the bright idea to use the Power+Volume Down to take screenshots of my display as I blindly tapped and used that as a guide and moved forward to unlocking developer options, then enabling USB debugging. I can now see my device in ADB once again. Should be pretty cake from here. Thank you so much bro! And also, HTC has agreed to send me a new phone, but I must first send mine in. They would have sent me one first and then I send mine in later, but they wanted to place a $600 credit hold on my card. **** THAT. The rep told me they would be checking for other damages as well as if it rooted.
Click to expand...
Click to collapse
You are a genius!!! I will have to remember that if this type of situation arises again.

@majmoz
Ok so I've been reading those sites and I know I'm so close to being back to 100% stock, but now I'm stuck. I'm confused as to what order to things.
I restore stock recovery, then lock bootloader, turn S-ON,and remove tampered and return to Locked status?
Here are my fastboot getvar details. Just trying to get this done as soon as possible as I'm also in the process of moving and wont have net here much longer. So as soon as I get this done I can send my phone back in and get the replacement. Really hate being without a phone.

Kev_McCall said:
@majmoz
Ok so I've been reading those sites and I know I'm so close to being back to 100% stock, but now I'm stuck. I'm confused as to what order to things.
I restore stock recovery, then lock bootloader, turn S-ON,and remove tampered and return to Locked status?
Here are my fastboot getvar details. Just trying to get this done as soon as possible as I'm also in the process of moving and wont have net here much longer. So as soon as I get this done I can send my phone back in and get the replacement. Really hate being without a phone.
Click to expand...
Click to collapse
Here I put them in your new post.

Alright cool thanks! I really shouldn't have created a new thread, but I wasn't sure if you would be on for much longer. Reading it now.

Kev_McCall said:
Alright cool thanks! I really shouldn't have created a new thread, but I wasn't sure if you would be on for much longer. Reading it now.
Click to expand...
Click to collapse
it doesn't take 5 threads to fix one problem does it ?

clsA said:
it doesn't take 5 threads to fix one problem does it ?
Click to expand...
Click to collapse
Probably not, you're right. But when other people don't respond to my initial thread it's kind of hard. I'm still stuck And just trying to get this finished up. Would you care to help? It's not much.

Kev_McCall said:
Probably not, you're right. But when other people don't respond to my initial thread it's kind of hard. I'm still stuck And just trying to get this finished up. Would you care to help? It's not much.
Click to expand...
Click to collapse
we all have other lives besides XDA .. you have to be patient
I have a few min where are you now in the recovery process ?

Won't boot into recovery

Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you

belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.

MrMike2182 said:
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
Click to expand...
Click to collapse
Thanks for the reply! I just now gave that a shot but it had no effect.

belowHeights00 said:
Thanks for the reply! I just now gave that a shot but it had no effect.
Click to expand...
Click to collapse
Are you actually holding both buttons down at the same time until the screen turns on? Don't let them go hold them both down until your screen lights up. Then select recovery but if it doesn't work then try below.
Try flashing this version of twrp https://twrp.me/devices/htcdesire510usa32bit.html ... If you're not in the USA I need to know.

Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..

belowHeights00 said:
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
Click to expand...
Click to collapse
What service provider are you using?
Don't toss the unlock code you got from HTC you're gonna need the very first one you got keep it forever.

I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?

belowHeights00 said:
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
Click to expand...
Click to collapse
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..

MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?

belowHeights00 said:
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
Click to expand...
Click to collapse
For extended personalizing other than developer options, I'd use Xposed.

MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)

Zubagy said:
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Click to expand...
Click to collapse
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..

MrMike2182 said:
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
Click to expand...
Click to collapse
Not really, But perhaps it time to learn

Zubagy said:
Not really, But perhaps it time to learn
Click to expand...
Click to collapse
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...

MrMike2182 said:
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
Click to expand...
Click to collapse
I guess then am good to go, are those the only requirements....... i dont have any source code though

Zubagy said:
I guess then am good to go, are those the only requirements....... i dont have any source code though
Click to expand...
Click to collapse
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.

Hey, I also faced this problem but I find the solution and successfully flash twrp
Hey, I also faced this problem but I find the solution and successfully flash tarp recovery.
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse

MrMike2182 said:
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Click to expand...
Click to collapse
Sorry for the delay, yes.... i am using vm ware... my net is not that fast... but it can get things done.