I've been using my Sensation XE for almost 9 months now, and on the 2nd month i decided to Root it. I went through the steps: unlock bootloader (Juopunut), s-off and root. For some reason after a week or two from ROOTING the phone, i noticed that the bootloader reverted back to LOCKED. It was still S-offed and rooted, no problem with that. I was just wondering why it went back to LOCKED state.
I didn't mind the bootloader being locked and proceed to flashing a custom rom. I've been shifting from one rom to another and they were really buggy. I checked the forums and read the section about known bugs. Yes, the bugs were existent, but there are tons of bugs happening in my phone that we're not mentioned. I shifted to another custom rom and the same things happened. Some of my bugs and glitches are not on the list of known bugs.
I started to ask if it's the LOCKED BOOTLOADER who's making this issue on my custom roms. END OF STORY
QUESTIONS:
Do issues with custom roms happen if BOOTLOADER is LOCKED?
Is it safe to attempt to unlock the bootloader again even if it's rooted and s-offed?
If it's because of the LOCKED BOOTLOADER, is it permanent? Can it still be undone?
czyre04 said:
I've been using my Sensation XE for almost 9 months now, and on the 2nd month i decided to Root it. I went through the steps: unlock bootloader (Juopunut), s-off and root. For some reason after a week or two from ROOTING the phone, i noticed that the bootloader reverted back to LOCKED. It was still S-offed and rooted, no problem with that. I was just wondering why it went back to LOCKED state.
I didn't mind the bootloader being locked and proceed to flashing a custom rom. I've been shifting from one rom to another and they were really buggy. I checked the forums and read the section about known bugs. Yes, the bugs were existent, but there are tons of bugs happening in my phone that we're not mentioned. I shifted to another custom rom and the same things happened. Some of my bugs and glitches are not on the list of known bugs.
I started to ask if it's the LOCKED BOOTLOADER who's making this issue on my custom roms. END OF STORY
QUESTIONS:
Do issues with custom roms happen if BOOTLOADER is LOCKED?
Is it safe to attempt to unlock the bootloader again even if it's rooted and s-offed?
If it's because of the LOCKED BOOTLOADER, is it permanent? Can it still be undone?
Click to expand...
Click to collapse
Hi,
If you are s-off,DO NOT try to use HTC to lock/unlock your phone.
It will cause problems for you.
Did you flash a version of the 3.33 firmware?
This has been known to lock people's bootloader.
The only thing a locked bootloader will do,is prevent you using all the fastboot commands.
malybru said:
Hi,
If you are s-off,DO NOT try to use HTC to lock/unlock your phone.
It will cause problems for you.
Did you flash a version of the 3.33 firmware?
This has been known to lock people's bootloader.
The only thing a locked bootloader will do,is prevent you using all the fastboot commands.
Click to expand...
Click to collapse
Yeah, I kinda have updated the firmware after the root process.
Have any idea why i get extra bugs from roms?
Thanks for the reply BTW. Appreciated it.
czyre04 said:
Yeah, I kinda have updated the firmware after the root process.
Have any idea why i get extra bugs from roms?
Thanks for the reply BTW. Appreciated it.
Click to expand...
Click to collapse
Hi,
Sorry,I have no idea why your phone is suffering all these bugs.
My suggestion would be to keep searching for a ROM/kernel combination that works for you.
Related
I need to root, unlock, and install CWM right? How exactly do I do this? I tried to locate a how to without any luck.
The dev section is filled with all the info you need to know.
Also, not trying to be a **** but saying you searched when it is obvious that you didn't will get you nowhere.
OK I've read some more and had a couple more questions...
I noticed that the roms I've looked at don't require an unlocked phone. What's the point of unlocking the phone then? Can I just root and install CWM?
Some roms say "needs the 1.85 base." What does this mean and how do I get it before flashing a rom?
Thanks!
johnl199 said:
OK I've read some more and had a couple more questions...
I noticed that the roms I've looked at don't require an unlocked phone. What's the point of unlocking the phone then? Can I just root and install CWM?
Some roms say "needs the 1.85 base." What does this mean and how do I get it before flashing a rom?
Thanks!
Click to expand...
Click to collapse
Some of the roms, prior to the unlock discovery, were executable as an RUU. All the updated versions require recovery which you need the bootloader unlocked to get in to. It's a painless process and there's even a 1-Click script method for those who dont want to take chances.
Will I be able to get the phone back to COMPLETELY stock should I decide to sell it in the future?
From what I know it will say relocked or tampered but maybe I'm wrong
Sent from my HTC One X using xda premium
After unlocking your phone, there will be no way to get back to 100% stock unless we can get S-OFF (which hopefully may be in the near future due to a few devices already being S-OFF).
However, you can root your device and not unlock it (1.82 and prior as of now) and still be able to revert to 100% stock as if it came right out of the box.
Most of the ROMs currently do not require an unlocked bootloader.
However, this will definitely change as we begin to see custom kernels (hopefully soon with the release of the source by HTC Dev) and more complex ROMs (such as those based on AOSP, such as CM9 and AOKP).
So in short, you can still use most of the ROMs in the dev section. Just be aware however that if you do not unlock then you cannot install CWM (limiting the number of ROM options) and also if you update past 1.82.502.3 then you cannot root (at this time, other root exploits are being explored).
Is unlocking your bootloader the same as carrier unlocking your phone?
Does this mean that say, AT&T phones could be used on Tmobile?
lamenramen said:
Is unlocking your bootloader the same as carrier unlocking your phone?
Does this mean that say, AT&T phones could be used on Tmobile?
Click to expand...
Click to collapse
Nope. You are thinking of SIM unlock.
Bootloader unlock lets you load custom ROMs and change recovery, that's all.
Hi XDA-Devvers,
In a topic (http://forum.xda-developers.com/showthread.php?t=1510719) I read about the following:
Nonverbose said:
Root won't stop an ota but an unlocked bootloader will. You can check in your boot screen if its still unlocked or if its relocked.
Click to expand...
Click to collapse
Doesn't that mean that we can root our tablet, lock the bootloader again (fastboot oem lock), install Voodoo OTA RootKeeper and once there's an OTA available, just backup the root with the Voodoo app and install it?
How awesome would that be :laugh:
Since I am not a pro in that kind of stuff: Can anyone confirm this theory might actually work for real?
fastboot oem lock is unavailable once you unlocked the bootloader.
Ah bummer. Can we relock the bootloader yet? IF we were able to relock the bootloader, it would work, wouldn't it?
TomONeill said:
Ah bummer. Can we relock the bootloader yet? IF we were able to relock the bootloader, it would work, wouldn't it?
Click to expand...
Click to collapse
No, as many informations -including bootloader version- are sent to check if a new OTA is available
alx5962 said:
No, as many informations -including bootloader version- are sent to check if a new OTA is available
Click to expand...
Click to collapse
Okay, thank you for replying. This makes the decision to root a little harder since I want to keep getting updates and for that you'll need ClockWork (and the people who are pushing the update to XDA)(Clockwork does have the nandroid backup though, which I want to have when rooting), which doesn't run very stable last time I read (I rooted before, but then I sent my tab back (heat problems) and got a new one. I flashed a beta ROM xd).
I thanked your post
Isn't it enough to have the original Kernel and ROM? Do you really need a locked bootloader to get OTA updates?
Has anyone tested the universal root method? See http://forum.xda-developers.com/showthread.php?t=1886460
As this doesn't effect the Kernel, OTA updates might work if rooting works with this method.
I've not tried it. I've read some people are bricking their tablets with the universal, and since the A700 is basically a brick waiting to happen, I think I'll pass on it for a while.
I have a rogers one x, running 4.0.3 / 1.94.631.3.
I'd like to update to the newer software version so I can have the official version of the 3 dot mod (using the tast button as a menu/task button).
I'd also like to be rooted again.
I really dont want to unlock my bootloader yet though, is there a way to update my phone without having to unlock my bootloader>?
Berserk87 said:
I have a rogers one x, running 4.0.3 / 1.94.631.3.
I'd like to update to the newer software version so I can have the official version of the 3 dot mod (using the tast button as a menu/task button).
I'd also like to be rooted again.
I really dont want to unlock my bootloader yet though, is there a way to update my phone without having to unlock my bootloader>?
Click to expand...
Click to collapse
You can't root these phones without unlocking the bootloader. If you're already rooted, you're already unlocked. Just flash a 4.0.4 rooted stock rom.
Edit: This applies to 2.20 only. If for some reason you're still on a 1.xx firmware, you may not need to unlock.
Technically not true...
Earlier versions of the firmware 1.7 - 1.85 you could root without unlocking keeping the phone true to stock but with root. In the bootloader you get just the tampered flag but still locked.
You might able to keep root with root ota keeper from play store or if you have the pro version of supersu there's an option for it try keep root but I don't think these are 100% guaranteed to work.
Sent from my HTC One XL using xda premium
thejosh86 said:
Earlier versions of the firmware 1.7 - 1.85 you could root without unlocking keeping the phone true to stock but with root. In the bootloader you get just the tampered flag but still locked.
Click to expand...
Click to collapse
You're right; it's been so long I forgot about that. We actually got root on 1.73 first, then unlock about two weeks later.
iElvis said:
You're right; it's been so long I forgot about that. We actually got root on 1.73 first, then unlock about two weeks later.
Click to expand...
Click to collapse
Haha yeahhh I know what you mean - feels like forever ago now.
Sent from my HTC One XL using xda premium
I'm worried that unlocking my bootloader will instantly void my warranty.
But i would love to play with custom roms and have up to date software.
I'm assuming there will most likely never be a way to restore the bootloader flags, so it looks like it has never been unlocked.
Berserk87 said:
I'm worried that unlocking my bootloader will instantly void my warranty.
But i would love to play with custom roms and have up to date software.
I'm assuming there will most likely never be a way to restore the bootloader flags, so it looks like it has never been unlocked.
Click to expand...
Click to collapse
Root/boot loader unlock doesn't necessarily mean you warranty is void. If you have a hardware issue the carrier will usually give you a replacement
The only way we could restore the flags is by getting s-off and that doesn't look to promising at this point
Sent from my One X using Tapatalk 2
I'm on Rogers and my phone has been rooted and the bootloader unlocked since the day I got it.
I did have to send my phone in for a warranty repair for the volume buttons. I left the custom rom I was running at the time on the phone.
Rogers replaced my phone as they could not repair my first one. So I don't think you have to worry to much about it if it is a hardware issue.
josh3794 said:
I'm on Rogers and my phone has been rooted and the bootloader unlocked since the day I got it.
I did have to send my phone in for a warranty repair for the volume buttons. I left the custom rom I was running at the time on the phone.
Rogers replaced my phone as they could not repair my first one. So I don't think you have to worry to much about it if it is a hardware issue.
Click to expand...
Click to collapse
Good to know. That was my biggest concern.
I'll most likely be doing a 'one-time-swap' through rogers since my phone has the worst bluetooth ever, then ill start the root/unlock after.
Thanks for the help. :good:
Hi guys
I am new and never flash firmware on HTC before.
I have go HTC one XL from hongkong unlocked with JB (just recently got the official download) but not happy with the data connection speed and it is very slow for some reason. ICS was better than the Hongkong official JB release unfortunately.
Since I am in Australia I want to flash my firmware with the stock rooted Telstra [ROM] 01/01/13 Stock rooted odexed JB Telstra_WWE_3.17.841.2.
Can some one pls point me to the right direction - I am not sure where to start (previously I own SG2 and flashed firmware no issues).
I am aware that there are more options on how to flash in HTC I am abit worried that I might follow the incorrect steps
Thank you
Unfortunately, some changes were deployed in the official JB update which causes the touch screen to not function if you try changing to any ROM that is not also Sense JB. So currently, if you flash an ICS ROM, the touch screen will not work.
Devs may be working on this. But its more likely that it won't be solved until we have kernel source for JB. Until the issue is fixed, you are stuck with Sense JB ROMs.
If you still want to be able to flash custom ROMs, the proper sequence is:
- Unlock bootloader at HTCDev.com
- Install TWRP recovery
- Download custom ROM, and copy to phone's SD
- Flash ROM in TWRP
- Flash boot.img using fastboot
You can start reading here: http://forum.xda-developers.com/showthread.php?t=1671237
redpoint73 said:
Unfortunately, some changes were deployed in the official JB update which causes the touch screen to not function if you try changing to any ROM that is not also Sense JB. So currently, if you flash an ICS ROM, the touch screen will not work.
Devs may be working on this. But its more likely that it won't be solved until we have kernel source for JB. Until the issue is fixed, you are stuck with Sense JB ROMs.
If you still want to be able to flash custom ROMs, the proper sequence is:
- Unlock bootloader at HTCDev.com
- Install TWRP recovery
- Download custom ROM, and copy to phone's SD
- Flash ROM in TWRP
- Flash boot.img using fastboot
You can start reading here: http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
Cheers for the reply.
Yes i still want to flash the telstra jb available hoping that performance is going to be abit better.
Do I still have to unlock my bootloader? Eventoughmy phone is unlocked? Sorry for the basic questions. I will have a read on the link as well. Thanks guys
Sent from my HTC One XL using Tapatalk 2
Hi guys
Been trying to read the suggested link. I am seriously confused.
Do I need to unlock my bootloader?
Is the any tutorial for complete newbie?
Thanks guys
Sent from my HTC One XL using Tapatalk 2
ardabelati said:
Hi guys
Been trying to read the suggested link. I am seriously confused.
Do I need to unlock my bootloader?
Is the any tutorial for complete newbie?
Click to expand...
Click to collapse
You need to read until it makes sense as a complete newbie will just end up bricking the phone.
You do need to unlock the bootloader. Your phone may be "unlocked" in relation to allowing any SIM from any provider, but that is 100% unrelated to unlocking the bootloader.
The Telstra 3.17 is unlikely to make any difference to the Hong Kong based 3.17. They are almost identical except for the few Telstra apps included.
Have you checked that your APN is set to telstra.wap so that LTE will function? The Hong Kong phones ship with incorrect settings for Telstra.
You could refer to this link for help, but ignore it's advise to set telstra.internet as that is incorrect(it is only for 4g modems, not phones) and will prevent some Telstra apps from working correctly:
https://support.mobicity.com.au/ent...up-the-htc-one-xl-on-telstra-s-4g-lte-network
Also you should check Telstras coverage as LTE is only available in limited areas.
http://www.telstra.com.au/mobile-phones/coverage-networks/our-coverage/mobile-broadband/
Beyond these suggestions you should take up your speed issues with Telstra.
ardabelati said:
Do I need to unlock my bootloader?
Click to expand...
Click to collapse
I already answered this in post #2 above. Don't know why you are asking the same question again.
Twisteddx beat me to answering your other questions, and I agree with all he said.
You're confusing unlocking the SIM versus unlocking the bootloader. SIM unlocked just means you can use SIMs for any carrier. Bootloader unlock removed write protection for certain partitions of the memory, allowing you to install custom recovery, custom ROMs, etc. SIM unlock and BL unlock are not related in any way.
I'm not a huge fan of simple tutorials. They invite you to try mods with a minimum of knowledge, which is really the opposite of what you should do. Read up, and learn as much as you can, as twisted mentioned, you will be performing things that can cause permanent damage to the phone if not done completely properly. You need to have a deep understanding of what you are doing before you start. Even if you follow the steps to the letter, things all-to-often go awry. And being armed with as much knowledge as possible is the best way to prepare for such events.
The amount of information can be daunting, for sure. But once you become more familiar with the terms and basic concepts, you will probably see its actually not that complicated. Maybe start with some of the "Misc Guides" at the bottom of the 1st post of my Index thread, such as the Terminology glossary. Look at other posts by similar users in Q&A, and go from there.
Hello guys.
I'm going to buy used and bootloader unlocked Verizon Pixel tomorrow and I'm interested in couple of things:
1. Can I flash all the ROMs that are available for Pixel on Verizon version too?
2. Can I properly install TWRP, root using Magisk, etc?
3. Can I properly flash (and downgrade if needed) official system images (and are they ever available for Verizon models?)
4. Can I take part in Android Beta program?
5. Is there anything I should be afraid of?
Thanks in advance.
Make sure it is bootloader unlocked, and not just SIM unlocked. There are not many VZ ones around that are bootloader unlocked. You need that to do the items on you list.
TonikJDK said:
Make sure it is bootloader unlocked, and not just SIM unlocked. There are not many VZ ones around that area bootloader unlocked. You need that to do the items on you list.
Click to expand...
Click to collapse
As I already stated, bootloader is already unlocked.
No one has an answer?
If it's bootloader u locked then yeah u can do all those things. Just do not ever for any reason ever relock the bootloader. Also I believe there have been a few cases where ppl have had semibricks or other issues which required locked stock to fix or somehow resulted in locked stock
I got a replacement about a month ago on my small Pixel and that one was unlocked. However, the one I got from Verizon in store did not have an unlocked bootloader. I'm not sure what the deal is, but maybe getting a replacement from an "accidental" break might do the trick. just to clarify, my first Pixels' usb port got completely fried and started to smell bad whenever it charged, and the phone would get really hot. I am now on 8.1 with an unlocked bootloader but have yet to actually root the phone
KittyRgnarok said:
If it's bootloader u locked then yeah u can do all those things. Just do not ever for any reason ever relock the bootloader. Also I believe there have been a few cases where ppl have had semibricks or other issues which required locked stock to fix or somehow resulted in locked stock
Click to expand...
Click to collapse
Thank you!
gb_14 said:
Thank you!
Click to expand...
Click to collapse
Np