Related
i have done research and i basically nail down the problem. i did search around and found options to resolve this.
one of it is using RUU options, i tried several times, but due to slow booting, the operation fail.
i try to use OTA, to update to 2.50.707.4, however, when it reboot, it stuck in the HTC black screen instead of white.
My problem problem is same as the one is found:
" powering up takes about 30 minutes - 20 minutes just black screen(so I thought phone completely broken), then HTC logo with approx 10 mins vibro, approx 5 mins silent, boot to android and then - working fast as usual. USB connection not recognizes, reboot to bootloader takes eternity and locks up in menu(maybe its just makes a move onse an hour, I dont tested so long)
Any advises?"
my problem came when i did the "one click eng s-off" as i wanna flash a new radio. after i have done the "one click eng s-ff", my device reboot and i am having the above super slow boot. i assume the hboot screw up or conflict with what i have done.
please please advice...
edit: however, i am able to go into bootloader and recovery using adb command (which take ages). my recovery is 4ext or something like that. i have a backup of my previous downgrade version before i flash the smartdroid. what should i do?
my backup after downgrade version is 2.37.707.3. what else i need to do?
edit: SOLVED
i revert back my hboot and everything done, very risky to have eng s-off.
from what i read, you probably have a device shipped with 3.x, and downgrading hboot causes that super slow booting. its a known problem...
actually, the problem is not caused by downgrading. this is what is did : http://forum.xda-developers.com/showthread.php?t=855403 "one click ENG S-OFF"
i just revert back hboot settings using the terminal and code provided from the thread, and problem gone. yet, i don't know what's go wrong. i think this problem is very rare as it is NOT due to downgrading process, as before i do the ENG S-OFF thing, i already downgrade the device and even flash smartdroid ROM in it with no issues.
actually i am helping my friend to root his phone. well, i own a samsung galaxy s2. i don't have to go through all the pain to root.
The issue happened when you flash the older Eng bootloader on a device that came with gingerbread.
Since the Eng bootloader is older(from froyo) it is as above hosted. Downgrading your bootloader. Its not as rare as might think. A lot of people have been in this spot
marsdta said:
The issue happened when you flash the older Eng bootloader on a device that came with gingerbread.
Since the Eng bootloader is older(from froyo) it is as above hosted. Downgrading your bootloader. Its not as rare as might think. A lot of people have been in this spot
Click to expand...
Click to collapse
there might be a lot, but trying to search for this solution is as rare as i can describe. or should i say, i couldn't even search for it? i have to click one by one to search for it.
can you enlighten me with a link or steps to get eng s-off? coz all the search topic i found is actually quite technical, as i am sgs2 users, it is actually very hard to understand the term used in htc.
i might as well quit helping my friends with more rooting/hacking on htc as it is too risky and almost different from sgs2, and i don't wanna pay for any damages.
mattcfk said:
there might be a lot, but trying to search for this solution is as rare as i can describe. or should i say, i couldn't even search for it? i have to click one by one to search for it.
can you enlighten me with a link or steps to get eng s-off? coz all the search topic i found is actually quite technical, as i am sgs2 users, it is actually very hard to understand the term used in htc.
i might as well quit helping my friends with more rooting/hacking on htc as it is too risky and almost different from sgs2, and i don't wanna pay for any damages.
Click to expand...
Click to collapse
Their is no need to have Eng soff. It only causes issues for newer devices. Regualr soff is more than enough to flash a custom recovery,custom roms,radios,bootsplashes.
For example with engineering bootloader many people will use.the fastboot command to flash a radio(you guys might use modem). With soff to flash a radio it needs to be packed in a flashable BOOTLOADER zip file. We call them PD98IMG.zip. that's essentially the difference. Eng one can use a PC and fastboot to flash radios, while regular soff we pack it in a zip and flash in bootloader
marsdta said:
Their is no need to have Eng soff. It only causes issues for newer devices. Regualr soff is more than enough to flash a custom recovery,custom roms,radios,bootsplashes.
For example with engineering bootloader many people will use.the fastboot command to flash a radio(you guys might use modem). With soff to flash a radio it needs to be packed in a flashable BOOTLOADER zip file. We call them PD98IMG.zip. that's essentially the difference. Eng one can use a PC and fastboot to flash radios, while regular soff we pack it in a zip and flash in bootloader
Click to expand...
Click to collapse
so confusing >.<" anyway, my fren came back to me, he sent his phone for warranty. seems like the bootloader is giving him trouble again (back to very long boot up thing). i don't think i wanna touch HTC device ever.
hi
on friday I got a desire which belonged to a friend of mine and now through me becomes the phone of another friend. the phone was already rooted (I was the one who did it initially too) but that was a long time ago and there was no custom recovery (I think we used some kind of tethered-recovery) or anything like that on the phone. so I decided to correct that. my target was custom recovery, root, new rom, s-off preferably data++
unrevoked and revolutionary did of course not work for me so I decided to just flash the GB RUU basically like described here: http://forum.xda-developers.com/showthread.php?t=1626405
and that worked pretty good but now the phone is stuck in a bootloop which resets the phone right after starting the rom. I already tried reflashing the ruu (via goldcard just to be safe, though I am pretty sure I have the correct one (tmobile DE branded, t-mob101), that however did not change anything.
so now I don't really know what to do, please help me
thanks in advance
what's the hboot info?
thaaanks a lot. in the german forum so far noone has been repyling at all since yesterday.
fastboot and recovery (though stock) works btw.
fastboot / hboot info:
Bravo PVT1 Ship s-on
hboot-1.02.0001
Microp-031d
touch panel-synth101
radio-5.17.05.23
Jul 22 2011, 16:19:16
yeah recovery isn't gonna help..
Think you can only try the 2.3 RUU again.. otherwise you can't do much more.
------
If that doesn't work (after a couple of tries).. then the process is to:
- find an XTC Clip (they're expensive, not worth buying, look into whether some phone repair shops have them)
- S-OFF the phone with the xtc clip
- Download an alpharev stock bootloader pb99img (rename it to pb99img), put it on your sd-card and update it from hboot
- Do a full wipe in fastboot
- flash recovery
- flash a rom
then I have a serious problem. apart from trying over and over again I have no choice? because I as mentioned I already tried it twice.
could the radio be a problem because the point where the phone reboots should be the moment when it normally asks for the sim pin?
can you please point me to the absolut right RUU file? I just want to be cautious.
starting the ruu installer, getting the rom.zip file (which seems to contain nothing if I open it on the computer?), renaming it to PB99IMG.zip putting it onto the goldcard and starting into fastboot is the right way?
fleity said:
then I have a serious problem. apart from trying over and over again I have no choice? because I as mentioned I already tried it twice.
could the radio be a problem because the point where the phone reboots should be the moment when it normally asks for the sim pin?
can you please point me to the absolut right RUU file? I just want to be cautious.
starting the ruu installer, getting the rom.zip file (which seems to contain nothing if I open it on the computer?), renaming it to PB99IMG.zip putting it onto the goldcard and starting into fastboot is the right way?
Click to expand...
Click to collapse
Ohh so it boots? If it does, boot it without inserting the sim, enable USB debugging, run revolutionary to S-OFF, flash recovery, backup the ROM, do a full wipe and flash a custom ROM.. see what happens then.
sorry if it was that easy I would have done that a long time ago ^^°
the phone also reboots if there is no sim inserted.
can I maybe flash some other RUU? another GB version, WWE instead of tmob UK/DE or even Froyo?) even newer stuff? I read something about a 1.03 hboot somewhere? as long as I get this running again I am pretty much willing to do anything. however I still wonder why this is happening.
I am dieing a little bit here, I'm so stupid
is it possible that I really messed up badly here:
http://www.your-android.de/htc-desire-gingerbread-upgrade-steht-zum-download-bereit
"Hey guys, we’re happy to announce that Gingerbread for Desire is here! Please visit our Developer website to access the download. http://developer.htc.com
Please note that the following regional variants are not compatible with this upgrade: Germany (Telekom Deutschland), North America, South Korea and Japan."
so still.. why is exactly is not working and how can I fix it...
no there is only 1 GB RUU.. try installing it from the .exe (boot into fastboot, plug it in, run RUU.exe).. see what happens then
i didnt know you could install RUUs from fastboot.
update worked perfectly like before but still reboots after 1 second in the rom.
fleity said:
i didnt know you could install RUUs from fastboot.
update worked perfectly like before but still reboots after 1 second in the rom.
Click to expand...
Click to collapse
Does the phone get really hot by any chance?
öhm how exactly should I test that? keep it runing in fastboot or repeat the bootcycle?
fleity said:
öhm how exactly should I test that? keep it runing in fastboot or repeat the bootcycle?
Click to expand...
Click to collapse
Umm nah, just when it boots, is it really hot? i.e. hotter than you would expect it to be...
Try sticking it in the freezer for 15 minutes in a plastic bag, then try turning it on again..
what the f? oookay one quick question before however: if I can flash the ruu from fastboot can I use revolutionary from fastboot too? (cause if revolutionary works all problems are solved, I did not dare to try that since the new hboot came with the weird gb update)
I would not say it gets any hotter than usual however freezer it is
fleity said:
what the f? oookay one quick question before however: if I can flash the ruu from fastboot can I use revolutionary from fastboot too? (cause if revolutionary works all problems are solved, I did not dare to try that since the new hboot came with the weird gb update)
I would not say it gets any hotter than usual however freezer it is
Click to expand...
Click to collapse
no, can only use revolutionary when booted into the ROM unfortunately
If you got hold of an XTC clip as mentioned before however...
The freezer thing? some Deisre's have faced hardware faults before causing them to overheat, reboot all the time etc. if you tried to use a RUU it would always fail.. sticking it in the freezer helped.. for a few minutes.. so trying to see whether this is the problem.
you sir are my hero of the day
it booted! awesome, incredible, how could you even think of that. I am absolutly speechless and impressed.
I just rebooted it manually again and it sill works. thaaaaaaaaank you so much
can you pm your paypal adress I like to buy you a beer or sth similar?
so the next steps would be run revolutionary and flash a custom right?
fleity said:
you sir are my hero of the day
it booted! awesome, incredible, how could you even think of that. I am absolutly speechless and impressed.
I just rebooted it manually again and it sill works. thaaaaaaaaank you so much
can you pm your paypal adress I like to buy you a beer or sth similar?
so the next steps would be run revolutionary and flash a custom right?
Click to expand...
Click to collapse
Haha don't worry about it.. and don't get too happy.. once it heats up again you may just have the same problem...
But for now yes, S-OFF the phone with revolutionary and flash a custom recovery, then backup, do a full wipe (boot, system, data, cache, dalvik) and flash a custom ROM. Cyanogenmod is a good place to start (need to flash google apps after flashing CM though)
I was able to Unlocked my Bootloaders but still no S-OFF
1.29 software lastest.
any help. ^_^
1The_Rock said:
I was able to Unlocked my Bootloaders but still no S-OFF
1.29 software lastest.
any help. ^_^
Click to expand...
Click to collapse
You cant get S-OFF yet ... just unlock bootloader ans thats all you need to flash custom ROMs (just flash a custom recoery like this one)
1The_Rock said:
I was able to Unlocked my Bootloaders but still no S-OFF
1.29 software lastest.
any help. ^_^
Click to expand...
Click to collapse
S off is unavailable, if your bootloader is unlocked, you can still root or flash custom roms
muamers said:
You cant get S-OFF yet ... just unlock bootloader ans thats all you need to flash custom ROMs (just flash a custom recoery like this one)
Click to expand...
Click to collapse
Gracious , Well gonna give it a try... As i am having problem with my HOX. i.e
when i play games / listen music / watch gallery movie.. my HOX keeps getting restarted :crying: . I hope we got a good tutorial....
xl VipeR lx said:
S off is unavailable, if your bootloader is unlocked, you can still root or flash custom roms
Click to expand...
Click to collapse
Thx pal. :victory:
editing... Now how do i get started... onces i download the Clockworkmod Touch Recovery img.
after 2 hours of intensive reading and searching.. i was able to install custom rom.. with fastboot. Cheers
editing... i thought custom rom could fix my issue.
HOW COME my HOX keeps getting restarted while i play music / movie / games ???
Someone had s-of, but still is private
I can not link because not writing posts for 10 posts
not helping much...
My HOX have been wiped out... i can only access to custom recovery.
How DO i enable USB Toggle so i can move custom rom on the SD CARD ?
As my HOX have been complete DEAD... ( As per me )
1The_Rock said:
editing... i thought custom rom could fix my issue.
HOW COME my HOX keeps getting restarted while i play music / movie / games ???
Click to expand...
Click to collapse
I think you just screwed yourself. Its a manufacturing defect and you need to get your phone repaired at HTC. But since you unlocked it, HTC would most possibly blame it on your custom rom and make you pay for the repairs (A new mainboard of course would be part of the repair, and that isn't cheap).
Here's a few tips for you:
1) If the phone has problems, look for HTC first (Or if your phone is still less than 1 week old from when you purchased it, get the phone exchanged for a new phone at where you purchased it)
2) If HTC is unable to repair/fix the problem, get the phone returned to where you purchased it (Make sure you get back your money!) and buy a different phone
3) DO NOT flash custom roms if you already know your phone has problems - that will just void your warranty and you'll be screwing yourself.
4) Before you attempt a unlock at htcdev.com , make sure your phone is 100% operational, no broken stuff, errors, etc as once your phone is unlocked/has a custom rom, your warranty is as good as void.
5) S-OFF is yet to be available for the HTC One X (International Tegra 3 version - Quad Core processor), however, the U.S (Snapdragon S4 version - Dual COre processor) has S-OFF available. DO NOT attempt to use the S-OFF method for the Snapdragon version on the Tegra 3 version as it will not work, and possibly damage your phone.
6) Unlocking your phone at htcdev.com is not S-OFF, but it allows your phone to use custom roms but would also void your warranty on all software-related problems.
http://forum.xda-developers.com/showthread.php?t=1592355
that should get you started, it did it for me!
However...seems you don't have a ROM.zip on your SD card, right?
Which CWM did you flash on your HOX? How much battery have you left?
With the latest CWM touch it is possible to mount the SD card, also, the HOX is charging while in CWM.
In case of the latest CWM you should be fine, then.
Follow the steps in the thread up there first, to create your FASTBOOT folder on c: just to make sure you have all stuff at the right place.
Can you still go into your bootloader? (Press and hold VOL - and then press POWER shortly...while holding VOL - until booatlader pops up)
cccy said:
I think you just screwed yourself. Its a manufacturing defect and you need to get your phone repaired at HTC. But since you unlocked it, HTC would most possibly blame it on your custom rom and make you pay for the repairs (A new mainboard of course would be part of the repair, and that isn't cheap).
Here's a few tips for you:
1) If the phone has problems, look for HTC first (Or if your phone is still less than 1 week old from when you purchased it, get the phone exchanged for a new phone at where you purchased it)
2) If HTC is unable to repair/fix the problem, get the phone returned to where you purchased it (Make sure you get back your money!) and buy a different phone
3) DO NOT flash custom roms if you already know your phone has problems - that will just void your warranty and you'll be screwing yourself.
4) Before you attempt a unlock at htcdev.com , make sure your phone is 100% operational, no broken stuff, errors, etc as once your phone is unlocked/has a custom rom, your warranty is as good as void.
5) S-OFF is yet to be available for the HTC One X (International Tegra 3 version - Quad Core processor), however, the U.S (Snapdragon S4 version - Dual COre processor) has S-OFF available. DO NOT attempt to use the S-OFF method for the Snapdragon version on the Tegra 3 version as it will not work, and possibly damage your phone.
6) Unlocking your phone at htcdev.com is not S-OFF, but it allows your phone to use custom roms but would also void your warranty on all software-related problems.
Click to expand...
Click to collapse
Even i thought so, perhaps after sleeping for 3 hours. I tried again and very calmly .....
As i got to know i did not used the lastest recovery img.
everything is good now with custom rom.
Phew ! my head and heart was nearly out , As i just bought this HOX yesterday.
hardstuffmuc said:
http://forum.xda-developers.com/showthread.php?t=1592355
that should get you started, it did it for me!
However...seems you don't have a ROM.zip on your SD card, right?
Which CWM did you flash on your HOX? How much battery have you left?
With the latest CWM touch it is possible to mount the SD card, also, the HOX is charging while in CWM.
In case of the latest CWM you should be fine, then.
Follow the steps in the thread up there first, to create your FASTBOOT folder on c: just to make sure you have all stuff at the right place.
Can you still go into your bootloader? (Press and hold VOL - and then press POWER shortly...while holding VOL - until booatlader pops up)
Click to expand...
Click to collapse
Yeah, I learnt this lesson after sleeping and gently reading all the pages and finally my HOX is UP ^_^
You people ROX :fingers-crossed:
thx a lot .
Hi all,
First of all, I can imagine that this problem has already been encountered a million times, but I tried searching the forum and didn't see the exact same problem as mine with the same setup. I'm happy to read more if someone points me to another thread with the solution.
Long story short, I tried flashing JellyTime_42 on this phone and even though everything seemed to work well, it's not booting and I'm stuck with the HTC logo.
unlocked the bootloader with HTC dev
flashed CWM recovery 5.8.1.5-ace
uploaded cm-JellyTime_42 and gapps.
wiped data, cache and dalvik cache using CWM
installed JellyTime
rebooted... and that's where I am now.
Some info about the phone itself. It's an Desire HD on ATT. cid: CWS__001
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0030
MICROP-0438
RADIO-26.17.14.11_M
eMMC-boot
As I said, I can fastboot, and although I'm not sure how to push other stuff to the phone, that part seems functional.
Thanks a lot for your help!!
Nick
You need to fastboot flash the boot.img from the ROM zip.
bananagranola said:
You need to fastboot flash the boot.img from the ROM zip.
Click to expand...
Click to collapse
Thanks so much bananagranola, that worked and I can now boot and use the phone!
(for some reason I never saw that step mentioned in any tutorial)
Thanks again
Most tutorials are for S-Off.
Yes, the preferred unlock method for the DHD/I4G is to get S-OFF using the Advanced Ace Hack Kit (AAHK). You can still do that, you just need to relock your bootloader and run the AAHK. The command to relock was given in the last step of HTCdev unlock.
You better do that soon though, if you want. - http://forum.xda-developers.com/showthread.php?p=38157931
There are 2-3 tutorials in the Ace Think Tank thread for both the AAHK and HTCdev methods of unlock. I've made one for flashing a ROM after HTCdev unlock too. You'll find all the information you'll need about this phone in the Ace Think Tank thread. Look through it.
Also, I suggest you use either 4ext or TWRP recovery rather than CWM. CWM is very dated and causes problems while installing some ROMs (like the recent ViperDHD updates).
For 4ext - Download and install 4ext Recovery Updater from www.4ext.net and flash the latest touch recovery.
For TWRP - Install Goo Manager from Play Store->Menu->Install OpenRecoveryScript
Sent from my Desire HD using xda premium
Hi sashank,
Thanks for your input.
Why is AAHK the preferred method? It seems way complicated compared to what I've done, but probably I'm missing something. That said, the phone works like a charm now after flashing boot.img.
Because if you have S-OFF, you won't need to flash boot.img every time you flash a ROM/kernel/ROM update. You don't need to have a PC with you just to flash a ROM. Also, you can directly restore a backup with no hassle. With HTCdev unlock, you need to flash the boot.img in the backup folder separately to complete the process. I do this for my friend's One X because it doesn't have an S-OFF method unfortunately, and it's quite a hassle. If you're okay with flashing boot.img every time, then stick with HTCdev unlock, no problem.
AAHK is actually quite simple to use. It does everything for you. You just need to follow the instructions to the letter, select a few options correctly and it does the rest. Don't be intimidated by it.
Sent from my Desire HD using xda premium
Nico7578 said:
Hi sashank,
Thanks for your input.
Why is AAHK the preferred method? It seems way complicated compared to what I've done, but probably I'm missing something. That said, the phone works like a charm now after flashing boot.img.
Click to expand...
Click to collapse
Nico, HTCDEV just allows you to have a limited control over your device. You will still be linked to your carrier or sales code (CID) and will not be able to flash RUU from other carriers/geographical areas. That might sound useless now, but belive me that when you get stuck and can not find a RUU for your device you will remember it!
Besides, HTCDEV will not allow you to flash radios and some other stuff. Not to metion that your bootloader says *UNLOCKED* in a beautiful pink color at the top...LOL
S-OFF disables all kinda of security in the phone (nand security off) and that allows you to flash anything at all. From RUU's to radios without facing issues. Besides, that is completely reversible and will leave no traces of being S-OFF if you need to get to a service centre.
Nico7578 said:
Hi sashank,
Thanks for your input.
Why is AAHK the preferred method? It seems way complicated compared to what I've done, but probably I'm missing something.
Click to expand...
Click to collapse
Because AAHK gives you full control on your device. It basically gives you permanent root privileges, S-OFFs your phone and with SuperCID (if needed) you actually unbrand your phone...that is that you can install every ROM you want on it.
It's not so difficult, to be honest, you just need to carefully read the guide and you'll soon unleash the real power of your device
NeoLocutus said:
Because AAHK gives you full control on your device. It basically gives you permanent root privileges, S-OFFs your phone and with SuperCID (if needed) you actually unbrand your phone...that is that you can install every ROM you want on it.
It's not so difficult, to be honest, you just need to carefully read the guide and you'll soon unleash the real power of your device
Click to expand...
Click to collapse
I think that something is wrong there. The root access is only to rom level. If you flash a RUU you will lose root privileges until SU is flashed again. What the Hack Kit gives you is S-OFF permanently, which is reversible anyway.
Please Help
Hello
I need help. Please
I recently brought a friend's phone (Desire HD) to flash custom ROM on. I flashed boot.img via fastboot but when I select recovery, A white screen with HTC shows and after a few seconds, black screen occurs. I know screen is on however. I dont know what to do. The bootloader says unlocked but it says
S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
The steps that I did was.
1. I unlocked the bootloader via HTCDev. It gave me error so I updated via RUU manually through fastboot.
2. After that, I was able to unlock the bootloader via HTCDev.
3. I followed this (http://www.teamandroid.com/2013/04/...android-422-jellytime-jelly-bean-rom-guide/2/) to flash method to Jelly-time on DHD. But when I flashed boot.img via fastboot cmd, it does not go to Recovery, it only shows phone with exclamation mark. If I reboot the phone, it shows white HTC screen and then black black screen. Please help me what to do. After unlocking via HTCDev, I didn't intall CWM, I though flashing boot.img is actually installing CWN :'|
Thanks a LOT in advance
I worked it successfully. I fastboot flashed CWM and it worked. Case closed
Hi all -
Had this HTC One M9 stock for about a month now. I've been reading and reading and reading, and have the big itch to root, but also have some questions I'm hoping folks can answer that I'm a bit confused about. So I'll just get right to my questions.
I've had android phones for years, and I get the general concept of this stuff, but is this clip method so different, in that if I haven't done it before I pose a significant risk of bricking my phone or struggling to figure out the process if I've never done this method?
Does the clip method just get me S Off, or can it unlock the bootloader too?
Should I just use clip to S Off and follow instructions in this thread to unlock bootloader (http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036)?
Can I return this phone to 100% stock if I need warranty service? From what I can gather from the unlock bootloader thread above, I can lock and unlock, and I assume with clip I can S on. Is there a way to flash image to OEM stock, and is there any other Knox-like things I need to worry about that I can't trip back?
I believe I read I can install TWRP recovery, but how do I do that once I have S Off and unlocked bootloader?
My goal is really just to flash a custom rom. I don't know I want to change all the in depth things that I think I'm reading I can do with S off. Is it possible, or does it make sense, to S off, unlock bootloader (which I think is all I need for TWRP and to load ROM), then S on again?
I know obv people are sending their phones to folks to S off, but there's a few reasons I'm thinking about the clip method (please correct any misunderstanding):
I can get clip for just under $100. Comparatively if I send it off, I'd probably do a $30 donation plus fast shipping both ways...I'm already over half the cost of the clip.
If I need the clip to return phone to true stock, I'd like that have that ability myself.
I know there's a few highly recommended people on here, but I'm still uneasy about sending a $600 phone to someone I don't know.
If the process is easy enough, I could try and recoup the money by doing a few phones in my area.
I'm mysteriously not seeing many website recommendations for the clip.
Sorry for the 1001 questions, but thank you SO much in advance for anyone that can offer advice!!!
crackface said:
Hi all -
Had this HTC One M9 stock for about a month now. I've been reading and reading and reading, and have the big itch to root, but also have some questions I'm hoping folks can answer that I'm a bit confused about. So I'll just get right to my questions.
I've had android phones for years, and I get the general concept of this stuff, but is this clip method so different, in that if I haven't done it before I pose a significant risk of bricking my phone or struggling to figure out the process if I've never done this method?
Does the clip method just get me S Off, or can it unlock the bootloader too?
Should I just use clip to S Off and follow instructions in this thread to unlock bootloader (http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036)?
Can I return this phone to 100% stock if I need warranty service? From what I can gather from the unlock bootloader thread above, I can lock and unlock, and I assume with clip I can S on. Is there a way to flash image to OEM stock, and is there any other Knox-like things I need to worry about that I can't trip back?
I believe I read I can install TWRP recovery, but how do I do that once I have S Off and unlocked bootloader?
My goal is really just to flash a custom rom. I don't know I want to change all the in depth things that I think I'm reading I can do with S off. Is it possible, or does it make sense, to S off, unlock bootloader (which I think is all I need for TWRP and to load ROM), then S on again?
I know obv people are sending their phones to folks to S off, but there's a few reasons I'm thinking about the clip method (please correct any misunderstanding):
I can get clip for just under $100. Comparatively if I send it off, I'd probably do a $30 donation plus fast shipping both ways...I'm already over half the cost of the clip.
If I need the clip to return phone to true stock, I'd like that have that ability myself.
I know there's a few highly recommended people on here, but I'm still uneasy about sending a $600 phone to someone I don't know.
If the process is easy enough, I could try and recoup the money by doing a few phones in my area.
I'm mysteriously not seeing many website recommendations for the clip.
Sorry for the 1001 questions, but thank you SO much in advance for anyone that can offer advice!!!
Click to expand...
Click to collapse
OK...so when you s-off it's completely reversible and does not require a clip or card to revert. Just some simple commands. If you have a clip the best bet is to s-off and then use the adb command to unlock. The clip can unlock but it uses the HTC Dev method which let's HTC know what you've done.
Once s-off you leave it s-off. You definitely do not want to turn it on while on a custom rom. Some system write protection is turned on/off by the s flag and boot loader lock status. There's no such thing as Knox on HTC. Using already posted commands you can simply lock the boot loader, flash an ruu (like Odin image) and turn s back on.
What I normally do is s-off, then unlock via the adb command. Flash twrp. Flash supersu. Flash rom.
If you don't understand all of this and why it works this way you probably should NOT be meeting local folks to work on their phones. Sometimes things go wrong and you would be stuck in a really bad situation.
Sent from my Nexus 6 using Tapatalk
dottat said:
OK...so when you s-off it's completely reversible and does not require a clip or card to revert. Just some simple commands. If you have a clip the best bet is to s-off and then use the adb command to unlock. The clip can unlock but it uses the HTC Dev method which let's HTC know what you've done.
Once s-off you leave it s-off. You definitely do not want to turn it on while on a custom rom. Some system write protection is turned on/off by the s flag and boot loader lock status. There's no such thing as Knox on HTC. Using already posted commands you can simply lock the boot loader, flash an ruu (like Odin image) and turn s back on.
What I normally do is s-off, then unlock via the adb command. Flash twrp. Flash supersu. Flash rom.
If you don't understand all of this and why it works this way you probably should NOT be meeting local folks to work on their phones. Sometimes things go wrong and you would be stuck in a really bad situation.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Makes sense, and loud and clear on the advice on doing others' phones. Thank you so much....
Keep in mind that any clip/javacard will mark the device, so HTC will know that you had S-OFF anyway (if you ever return it for warranty).
Sent from my Nexus 5 using Tapatalk
efrant said:
Keep in mind that any clip/javacard will mark the device, so HTC will know that you had S-OFF anyway (if you ever return it for warranty).
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Says who? Was never a problem for me. You actually have a harder time on a non-vzw HTC since you have to go through HTC Dev which registers in their system anytime you call in that you have strayed from stock.
I have warrantied many phones that were Java card s-offed. Properly returned to stock they will pass everytime.
Sent from my Nexus 6 using Tapatalk
dottat said:
Says who? Was never a problem for me. You actually have a harder time on a non-vzw HTC since you have to go through HTC Dev which registers in their system anytime you call in that you have strayed from stock.
I have warrantied many phones that were Java card s-offed. Properly returned to stock they will pass everytime.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Says someone who reverse-engineered the process, and who I believe.
I'm not saying it will be a problem, only that it could, if HTC decides to get picky. (I have never RMA'd anything ever so I certainly can't speak from experience. )
Yes, I agree that if you use HTC Dev to unlock, it makes it more of a problem than using a javacard (although there's nothing preventing a non-Verizon device from using a javacard - - your comment sort of implies non-Verizon HTCs need to go the HTC Dev route).
Sent from my Nexus 5 using Tapatalk
efrant said:
Says someone who reverse-engineered the process, and who I believe.
I'm not saying it will be a problem, only that it could, if HTC decides to get picky. (I have never RMA'd anything ever so I certainly can't speak from experience. )
Yes, I agree that if you use HTC Dev to unlock, it makes it more of a problem than using a javacard (although there's nothing preventing a non-Verizon device from using a javacard - - your comment sort of implies non-Verizon HTCs need to go the HTC Dev route).
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yep...second part of my comment pertains to the unlocking of a boot loader. It's probable that a higher number of non-vzw HTC phones use software methods to s-off. Of all of the phones I have s-offed using a card, 90% were vzw. I unlock all boot loaders using adb. Most of the folks out there who do card s-offs use supercid and dev unlock afterwards. I never really understood why when you can do it without letting HTC know. The built in boot loader unlock method on the clip also uses HTC Dev. Since all vzw HTC phones are banned from dev we have to s-off first.
Sent from my Nexus 6 using Tapatalk
dottat said:
Says who? Was never a problem for me. You actually have a harder time on a non-vzw HTC since you have to go through HTC Dev which registers in their system anytime you call in that you have strayed from stock.
I have warrantied many phones that were Java card s-offed. Properly returned to stock they will pass everytime.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
True dat - I am one helped by @dottat to return to s-on, locked, and stock for a warrantee replacement. No problem.
dottat said:
I unlock all boot loaders using adb. Most of the folks out there who do card s-offs use supercid and dev unlock afterwards. I never really understood why when you can do it without letting HTC know.
Click to expand...
Click to collapse
Out of curiosity, once you have S-OFF using your javacard, how do you unlock the bootloader using dd when you don't have root? Or how do you get root?
Sent from my Nexus 5 using Tapatalk
efrant said:
Out of curiosity, once you have S-OFF using your javacard, how do you unlock the bootloader using dd when you don't have root? Or how do you get root?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Depends on the device. On m9 you simply flash twrp (don't need to be unlocked on m9 to do so) and then use adb shell in twrp. On the m8, I have twrp packaged up that it will flash in ruu mode with a locked bootloader. Then same as above.
In twrp, adb shell is root already....no need to su.
Sent from my Nexus 6 using Tapatalk
dottat said:
Depends on the device. On m9 you simply flash twrp (don't need to be unlocked on m9 to do so) and then use adb shell in twrp.
Click to expand...
Click to collapse
Thanks! I had no idea you didn't need to be unlocked to flash the recovery partition. Is it only recovery, or do you have fastboot access to other partitions as well while locked?
efrant said:
Thanks! I had no idea you didn't need to be unlocked to flash the recovery partition. Is it only recovery, or do you have fastboot access to other partitions as well while locked?
Click to expand...
Click to collapse
If I am not mistaken, you won't have fastboot access to \system or \sp1 (splash screen) without bootloader unlock, but you CAN have access to \system within a ROM if you are rooted, even if the bootloader is locked.
hgoldner said:
If I am not mistaken, you won't have fastboot access to \system or \sp1 (splash screen) without bootloader unlock, but you CAN have access to \system within a ROM if you are rooted, even if the bootloader is locked.
Click to expand...
Click to collapse
Thanks. So to confirm, with S-OFF and a locked bootloader on an M9, you have fastboot access to all partitions other than system and sp1??
efrant said:
Thanks. So to confirm, with S-OFF and a locked bootloader on an M9, you have fastboot access to all partitions other than system and sp1??
Click to expand...
Click to collapse
Why don't you want to bootloader unlock? if you're already S-OFF you can do it in adb shell. Don't hold me to what partitions are fastboot accessible with bootloader locked. I've always had an S-OFF unit with bootloader unlocked. Some partitions aren't writable in fastboot even with bootloader unlocked, although they can be flashed by aboot with an appropriate zip file. For instance, I have a custom splash screen on both my test M9 and my own M9. I keep my test M9 system partition unwritable to ease taking OTA's on the device, but my own M9 runs Fluent.
hgoldner said:
Why don't you want to bootloader unlock? if you're already S-OFF you can do it in adb shell. Don't hold me to what partitions are fastboot accessible with bootloader locked. I've always had an S-OFF unit with bootloader unlocked. Some partitions aren't writable in fastboot even with bootloader unlocked, although they can be flashed by aboot with an appropriate zip file. For instance, I have a custom splash screen on both my test M9 and my own M9. I keep my test M9 system partition unwritable to ease taking OTA's on the device, but my own M9 runs Fluent.
Click to expand...
Click to collapse
It's not that I don't want to unlock. I'm just insatiably curious as to how things now work with HTCs. (Last HTC I owned was 5 years ago.)
Sent from my Nexus 5 using Tapatalk
efrant said:
It's not that I don't want to unlock. I'm just insatiably curious as to how things now work with HTCs. (Last HTC I owned was 5 years ago.)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The M9 is very different from any prior HTC handset. Instead of an hboot which contains fastboot access, it uses an aboot which is very limited in what it can do, that leads to either a "download" mode or a "recovery mode." Only download mode supports fastboot, and only for some partitions. Some things, like splash screens, can only be flashed in aboot from a properly compiled zip file. Some things can only be flashed in download mode via fastboot. I don't believe \system can ever be flashed on an M9, only altered in recovery or via a rooted system (actually, it can if you are installing a fresh custom ROM). And I believe more changes are afoot in HTC handsets in that regard.
With my M8, Rezound and Incredible, you unlocked bootloader and you got S-OFF. Okay, it was a little more complicated on the Rezound because of that infernal "wire trick," but still, you could fastboot write to any partition once you unlocked bootloader and were S-OFF. That is decidedly different on the M9, and the Verizon variant is locked down even tighter.
hgoldner said:
If I am not mistaken, you won't have fastboot access to \system or \sp1 (splash screen) without bootloader unlock, but you CAN have access to \system within a ROM if you are rooted, even if the bootloader is locked.
Click to expand...
Click to collapse
System part is the other way around while locked on this phone.
Write protected in os ....accessible via twrp.
Boot loader lock flag controls system rw on this phone. On the m8 it was the s flag.
Sent from my Nexus 6 using Tapatalk