Related
Hi everyone,
I have a AT&T HOX, which runs at 2.20. Is there any possibility to downgrade to a lower version and root the device? I really love "hacking" these phones but Im stuck at 2.20...
Thank you for your time reading my topic
No, if there was no one would be complaining about 2.20.
Search some.
http://forum.xda-developers.com/showthread.php?t=1838640
Here's gunnyman thread on the 2.20 think tank. There is also a bounty for 2.20 root in the general discussion.
Sent from my One X using xda premium
Search does not always equal knowledge
OP:
I had the same question. I just picked HOX 2.20 off of Craigslist. I didn't know about the CBlock from AT&T version 2.20. I guess I'll have to try some social engineering at the store to get the to free it up for me. From what I've read, root is required to downgrade but no root is available for 2.20, yet.
BTW: I've been looking for this answer for a while, via search. This is the only thread that clearly states 2.20 is not downgradable.
FynxSyndct said:
OP:
BTW: I've been looking for this answer for a while, via search. This is the only thread that clearly states 2.20 is not downgradable.
Click to expand...
Click to collapse
Don't know where you were looking.
Uh.....? I posted a link to another thread stating that 2.20 is not rootable yet. There are at least three in the general discussion thread that I can think of. If you want I can't paste those here? Happy to help in any way. I feel bad for you folks that are locked out on the 2.20.
Sent from my One X using xda premium
subarudroid said:
Uh.....? I posted a link to another thread stating that 2.20 is not rootable yet. There are at least three in the general discussion thread that I can think of. If you want I can't paste those here? Happy to help in any way. I feel bad for you folks that are locked out on the 2.20.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Not downgradable != not rootable. It's a matter of them not searching with the correct terminology or not understanding what they need to have to downgrade, but obviously they don't know which is why they are asking the question in the first place.
There is now root for 2.20. Check the General forum.
So, I've read several times about how to root non-AT&T phones with the new JB OTA (3.17) already installed...phones like the Rogers HOX I purchased with the OTA pre-installed (3.17.631.2).
However, I also came across a post talking about how this method worked but when he tried to flash a different ROM his phone was bricked. (Of course I can't find this now).
So, for those of you who have tried rooting a 3.17 phone, can you please post:
(1) Whether you were successful -- I admit, I'm a bit scared, because all the phones I've previously rooted have used fancy exploits!
(2) What ROMs you have flashed successfully -- of the very few threads I've found about rooting 3.17, it seems that everyone is choosing Viper and not trying others...
(3) Whether you experienced problems with certain ROMs
(4) Whether you've downgraded the touch firmware, and whether this resolved any issues
(5) Any other advice you can give!
Please please please note that I am NOT talking about the AT&T update and I am NOT referring to the bricks people are encountering when they accept that OTA. This is about 3.17, NOT the AT&T-exclusive 3.18.
I'm hoping this info will be added to 1 of the sticky posts on this forum...because what's there is American-centric...
skittleys said:
So, I've read several times about how to root non-AT&T phones with the new JB OTA (3.17) already installed...phones like the Rogers HOX I purchased with the OTA pre-installed (3.17.631.2).
However, I also came across a post talking about how this method worked but when he tried to flash a different ROM his phone was bricked. (Of course I can't find this now).
So, for those of you who have tried rooting a 3.17 phone, can you please post:
(1) Whether you were successful -- I admit, I'm a bit scared, because all the phones I've previously rooted have used fancy exploits!
(2) What ROMs you have flashed successfully -- of the very few threads I've found about rooting 3.17, it seems that everyone is choosing Viper and not trying others...
(3) Whether you experienced problems with certain ROMs
(4) Whether you've downgraded the touch firmware, and whether this resolved any issues
(5) Any other advice you can give!
Please please please note that I am NOT talking about the AT&T update and I am NOT referring to the bricks people are encountering when they accept that OTA. This is about 3.17, NOT the AT&T-exclusive 3.18.
I'm hoping this info will be added to 1 of the sticky posts on this forum...because what's there is American-centric...
Click to expand...
Click to collapse
You can just unlock the bootloader from HTC Dev. I think, and I could be wrong, that only AT&T isn't allowing bootloader unlock. I know for a fact Rogers and Telus can just unlock through HTC DEV and once bootloader is unlocked you can flash TWRP.
If someone bricked flashing a rom, it was not designed for his/her phone. Probably for the international one X which is oh so common.
Since you have 3.17, you would need to downgrade your Touchscreen Firmware in order to use AOSP roms but sense roms will work fine. To downgrade your touchscreen firmware you would first need S-OFF but as SuperCID works only on AT&T phones with certain firmwares you would need to manually change your CID to 11111111
HTC Dev, supercid, soff, downgrade firmware.
Then flash anything.
I know what the procedure is, I'm just a bit worried about what could happen after because of that 1 post that I read.
exad, I wondered if it that ROM was designed for the wrong phone, but confirmed that it wasn't. I do suspect that it was because of the touch firmware, but again, I've never actually seen anyone say that they've rooted from 3.17 and installed a ROM other than Viper...hence my worry...because I prefer ROMs that aren't based on Sense.
I see that you're both outside the USA. Did you root the 3.17 version, or did you do it earlier and never installed the OTA?
skittleys said:
I know what the procedure is, I'm just a bit worried about what could happen after because of that 1 post that I read.
exad, I wondered if it that ROM was designed for the wrong phone, but confirmed that it wasn't. I do suspect that it was because of the touch firmware, but again, I've never actually seen anyone say that they've rooted from 3.17 and installed a ROM other than Viper...hence my worry...because I prefer ROMs that aren't based on Sense.
I see that you're both outside the USA. Did you root the 3.17 version, or did you do it earlier and never installed the OTA?
Click to expand...
Click to collapse
Outside the USA you don't need super cid you can HTC DEV unlock so it's not the same. We can root any firmware.
You can't brick flashing a rom unless you're flashing a rom for the wrong phone, aosp roms won't work with the touchscreen update you'd need to downgrade it. If you're not an idiot, you won't brick.
I really don't understand your fear.. Viper is just fast, smooth and customizable. you'll be fine running other roms except AOSP until you downgrade the touchscreen firmware.
I feel like this thread is going around in circles.
If you have a rogers HOX, htc dev unlock and flash twrp. It's crazy simple.
I can't read.
Dacra said:
I can't read.
Click to expand...
Click to collapse
You and me both buddy, and I've been here for 4 years. Ugh!
Sent from my HTC One X
exad said:
I feel like this thread is going around in circles.
Click to expand...
Click to collapse
Yes, I feel like it's going around in circles too. Of course, that could be because you aren't addressing the questions I actually asked!
I know the procedure, I know what the limitation is in the US, I know about flashing ROMs and making sure they're for your specific phone before doing so. Like I already said, I'm not at all new to Android hacking. What I don't know is whether anyone has successfully rooted and flashed a ROM starting from a 3.1x OTA and its accompanying changes like the new bootloader. After all, we don't really know what changes HTC's made. For all we know, installing a ROM not based on 3.xx (like an AOSP-based ROM) causes issues beyond the touchscreen problem. These worries are compounded by the fact that the only post I've seen where someone tried to flash an AOSP-based ROM was a failure. I've yet to see someone say they've had success, which is why I started this thread in the first place. Because while I do assume that someone in this large user base has done it, in my line of business, acting on assumptions in the absence of even some weak evidence for that assumption and where there's documentation to suggest otherwise gets you fired, sued, and stripped of your licence.
So, let me ask my main question yet again—in fact, the ONLY question I asked in my last post—and hopefully it's clear this time:
Have you or anyone else rooted your HOX for the first time starting from an official HTC 3.17 ROM with its accompanying changes in the bootloader etc. and been successful? And if so, were you or that person able to successfully flash and use an AOSP-based ROM?
Sent from my HTC One X using xda app-developers app
I did. I have a Telus HOXL that was on the OTA Jellybean.
I SIM unlocked the phone (unnecessary but I wanted to use it on Bell). Then I HTCdev unlocked the bootloader. Flashed TWRP, rooted, SuperCID'd then s-off'ed. Finally I downgraded my touchpanel firmware.
However, I haven't installed an AOSP ROM yet since ViperXL has been working so great.
skittleys said:
Yes, I feel like it's going around in circles too. Of course, that could be because you aren't addressing the questions I actually asked!
I know the procedure, I know what the limitation is in the US, I know about flashing ROMs and making sure they're for your specific phone before doing so. Like I already said, I'm not at all new to Android hacking. What I don't know is whether anyone has successfully rooted and flashed a ROM starting from a 3.1x OTA and its accompanying changes like the new bootloader. After all, we don't really know what changes HTC's made. For all we know, installing a ROM not based on 3.xx (like an AOSP-based ROM) causes issues beyond the touchscreen problem. These worries are compounded by the fact that the only post I've seen where someone tried to flash an AOSP-based ROM was a failure. I've yet to see someone say they've had success, which is why I started this thread in the first place. Because while I do assume that someone in this large user base has done it, in my line of business, acting on assumptions in the absence of even some weak evidence for that assumption and where there's documentation to suggest otherwise gets you fired, sued, and stripped of your licence.
So, let me ask my main question yet again—in fact, the ONLY question I asked in my last post—and hopefully it's clear this time:
Have you or anyone else rooted your HOX for the first time starting from an official HTC 3.17 ROM with its accompanying changes in the bootloader etc. and been successful? And if so, were you or that person able to successfully flash and use an AOSP-based ROM?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
There's no limitations with non-aT&T one x. They allow you to unlock bootlader regardless of software. You need to S-OFF after and then downgrade Touchscreen Firmware to run AOSP, there won't be any issues running AOSP.
These questions could have been easily answered with just a little bit of research on your part.
Okay, installed LiquidSmooth and it's working so AOSP ROM's are fine.
Sent from my HTC One X using xda app-developers app
ChronoReverse said:
I did. I have a Telus HOXL that was on the OTA Jellybean.
I SIM unlocked the phone (unnecessary but I wanted to use it on Bell). Then I HTCdev unlocked the bootloader. Flashed TWRP, rooted, SuperCID'd then s-off'ed. Finally I downgraded my touchpanel firmware.
However, I haven't installed an AOSP ROM yet since ViperXL has been working so great.
.....................
Okay, installed LiquidSmooth and it's working so AOSP ROM's are fine.
Click to expand...
Click to collapse
Thanks, ChronoReverse!
exad said:
There's no limitations with non-aT&T one x. They allow you to unlock bootlader regardless of software. You need to S-OFF after and then downgrade Touchscreen Firmware to run AOSP, there won't be any issues running AOSP.
These questions could have been easily answered with just a little bit of research on your part.
Click to expand...
Click to collapse
Again, you're telling me things I already know and completely ignoring the questions I actually asked and the points I already made.
I know you can unlock the bootloader regardless of the current ROM...that doesn't necessarily mean that you can then go and flash any ROM designed for this phone but developed with different bootloaders and expect it to work. Plus, the bootloader was just one example of the many changes.
As I've said in each and every one of my posts, I already know the procedure, including for downgrading the firmware. Saying "there won't be any issues running AOSP" is a very bold statement, considering that I've yet to find evidence of anyone having actually done that (until this thread, that is). Again, theoretical vs. actual experience is a huge distinction.
And no, the questions I have asked aren't easily answered with a little research, since I did a LOT of research and found nothing. Something I have reiterated numerous times. The non-existent questions you are answering can be found with a tiny bit of research, and I already found them, which is why I didn't ask them in the first place.
How bout you unlock your bootloader and flash whatever rom you want?
skittleys said:
Thanks, ChronoReverse!
Again, you're telling me things I already know and completely ignoring the questions I actually asked and the points I already made.
I know you can unlock the bootloader regardless of the current ROM...that doesn't necessarily mean that you can then go and flash any ROM designed for this phone but developed with different bootloaders and expect it to work. Plus, the bootloader was just one example of the many changes.
As I've said in each and every one of my posts, I already know the procedure, including for downgrading the firmware. Saying "there won't be any issues running AOSP" is a very bold statement, considering that I've yet to find evidence of anyone having actually done that (until this thread, that is). Again, theoretical vs. actual experience is a huge distinction.
And no, the questions I have asked aren't easily answered with a little research, since I did a LOT of research and found nothing. Something I have reiterated numerous times. The non-existent questions you are answering can be found with a tiny bit of research, and I already found them, which is why I didn't ask them in the first place.
Click to expand...
Click to collapse
Don't be a ****. I answered your question. You're just not understanding.
S-OFF UPGRADE TO LATEST SOFTWARE, DOWNGRADE TOUCHSCREEN. RUN WHATEVER ROM YOU WANT WITH NO ISSUES. AOSP, SENSE, SENSE BASED SENSELESS. WHATEVER YOU WANT, NO INCOMPATIBILITIES. FFS.
You're assuming there are meaningful hardware differences in this phone across carriers. In fact, there are not.
People have successfully run 3.17 based roms on 3.18 carrier phones and vice versa. The differences are minor and superficial and pertain entirely to carrier branding. The 2.14 hboot is the same across all carriers.
I understand your concern, but you're trying to create an issue where none exists.
Not trying for a useless post but damn pointless topic...
Sent from my HTC One XL using xda app-developers app
Well that wasted about eight minutes and I am still confused.
Sent from my HTC One X using xda premium
iElvis said:
You're assuming there are meaningful hardware differences in this phone across carriers. In fact, there are not.
People have successfully run 3.17 based roms on 3.18 carrier phones and vice versa. The differences are minor and superficial and pertain entirely to carrier branding. The 2.14 hboot is the same across all carriers.
I understand your concern, but you're trying to create an issue where none exists.
Click to expand...
Click to collapse
I know that. That's not what I was worried about. When I mentioned 3.18 in my first post, it was only to make it clear that I wasn't yet another AT&T user who'd just flashed the OTA. What I was worried about was ROMs that were developed using the older hboots...and I wasn't so much worried about the bootloader being different in the first place, it was just an example of the changes that occurred with the OTA that won't simply be overridden with a factory reset/rooting/flashing a new ROM/whatever.
exad said:
Don't be a ****. I answered your question. You're just not understanding.
S-OFF UPGRADE TO LATEST SOFTWARE, DOWNGRADE TOUCHSCREEN. RUN WHATEVER ROM YOU WANT WITH NO ISSUES. AOSP, SENSE, SENSE BASED SENSELESS. WHATEVER YOU WANT, NO INCOMPATIBILITIES. FFS.
Click to expand...
Click to collapse
31ken31 said:
Not trying for a useless post but damn pointless topic...
Click to expand...
Click to collapse
Venomtester said:
Well that wasted about eight minutes and I am still confused.
Click to expand...
Click to collapse
You know, you guys are being awfully mean to someone who just wanted a straightforward answer to something she couldn't find the answer to. Outside of this thread, I challenge you to search for and find a post wherein someone's even implied that they upgraded to the 3.xx RUU, fully unlocked/rooted their phone, and flashed a non-Sense-based ROM. Don't just go clicking to a post you already know exists. Search for it. You'll find that search is fruitless. In fact, until this thread a couple of weeks ago, there was no such thread even for Sense-based ROMs. And finally, there was the aforementioned post I found from someone who'd successfully rooted and installed ViperXL but bricked his phone when flashing an AOSP-based ROM. With all that in mind, can you understand my lack of confidence? Can you understand why I started this thread instead of just going ahead with it? And then can you maybe stop criticizing someone who actually bothered to research her issue before posting and discovered nothing but a lack of information?
Your question was answered in the first response but you dragged it out saying that it wasn't. I spend day and night on the forum giving free help, by choice, mind you, the least you could do is read and take the advice that is given, instead of wasting everyone's time with sillyness and appreciate the time that people spend answering your questions.
This forum is not intended for people who don't understand what they are doing. Devs are doing this stuff for themselves, not you, they choose to share it with you and if you are not familiar with this kind of thing or are weary of risk. DONT ROOT YOUR PHONE.
Sent from my One X using xda app-developers app
Okay i just got a galaxy s3 because i have practically been on the fascinate my whole life, Flashed the life out of it and to this day its 100%. I want to root, and flash roms to my s3, but i have came across many threads and such and i really cant afford to ruin this phone, its like 3 days old lol. I am used to Odin, but that was the fascinate... I am on 4.1.2 and the Baseband version is I535VRBMF1 (what my phone was shipped with). Someone help me asap! i am very eager to make this phone sweet! its been out for awhile now so i suppose someone will know how to do this.
..P.s i have found bootloader unlock files for other 4.1.2, but i was about to start odin and realized it wasnt the same. Please get back with me asap.
kirkwoodlucas said:
Okay i just got a galaxy s3 because i have practically been on the fascinate my whole life, Flashed the life out of it and to this day its 100%. I want to root, and flash roms to my s3, but i have came across many threads and such and i really cant afford to ruin this phone, its like 3 days old lol. I am used to Odin, but that was the fascinate... I am on 4.1.2 and the Baseband version is I535VRBMF1 (what my phone was shipped with). Someone help me asap! i am very eager to make this phone sweet! its been out for awhile now so i suppose someone will know how to do this.
..P.s i have found bootloader unlock files for other 4.1.2, but i was about to start odin and realized it wasnt the same. Please get back with me asap.
Click to expand...
Click to collapse
Read all the sticky threads in the development section before you do anything. You'll answer all your questions and learn more stuff unique to this phone.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Read all the sticky threads in the development section before you do anything. You'll answer all your questions and learn more stuff unique to this phone.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
i cant seem to find it or what im looking for.
kirkwoodlucas said:
i cant seem to find it or what im looking for.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2079399
Read through imei backing up, casual root method, and how to root your galaxy s3 and more for generalized flashing methods. If you have any questions after reading through those feel free to ask.
Sent from my SCH-I535 using Tapatalk 2
Your best way to root and unlock the bootloader is the Casual method. It roots, unlocks and even installs a recovery like CWM or TWRP. However read up a bit. It's always good to get somewhat knowledgeable before barreling into something.
Make sure to read and understand the "Comprehensive IMEI/EFS Backup" section (on the link that BadUsername provided). I've never had an issue with this but I read sob storied all the time about people who didn't back up and had issues.
have any one with root on latest kitkat with locked bootloader in MOTO DROID RAZR MAXX HD?
sachi9121 said:
have any one with root on latest kitkat with locked bootloader in MOTO DROID RAZR MAXX HD?
Click to expand...
Click to collapse
No, Its currently not possible, and it isn't very likely that a way will be found.
TXKSSnapper said:
No, Its currently not possible, and it isn't very likely that a way will be found.
Click to expand...
Click to collapse
Why is EVERYONE so quick to shoot down the fact this cannot be rooted. Is anyone trying?
Kin Kira said:
Why is EVERYONE so quick to shoot down the fact this cannot be rooted. Is anyone trying?
Click to expand...
Click to collapse
if you were as fast at reading a few post in the General forum on this exact topic, as you are at posting about it here. you would already know, this has been gone over extensively, by people who know what they are doing. you would also know, that every option suggested has been thoroughly explored and tested. you would also know, that as far as anyone is aware, no one is publicly working on a solution, as this phone is past its prime and most if not all of the people capable of finding an exploit are not willing to spend time finding one.
had you read for 5 minutes before posting, you would already know this, #Just-Sayin
TXKSSnapper said:
No, Its currently not possible, and it isn't very likely that a way will be found.
Click to expand...
Click to collapse
bweN diorD said:
if you were as fast at reading a few post in the General forum on this exact topic, as you are at posting about it here. you would already know, this has been gone over extensively, by people who know what they are doing. you would also know, that every option suggested has been thoroughly explored and tested. you would also know, that as far as anyone is aware, no one is publicly working on a solution, as this phone is past its prime and most if not all of the people capable of finding an exploit are not willing to spend time finding one.
had you read for 5 minutes before posting, you would already know this, #Just-Sayin
Click to expand...
Click to collapse
There's phones well over a year and a half old still being played with. I'm simply shocked this isn't.
Kin Kira said:
There's phones well over a year and a half old still being played with. I'm simply shocked this isn't.
Click to expand...
Click to collapse
last i checked the s5 kitkat root bounty was over $17,000, and thats a new phone.
that should tell you something about how hard it is on kk.
bweN diorD said:
last i checked the s5 kitkat root bounty was over $17,000, and thats a new phone.
that should tell you something about how hard it is on kk.
Click to expand...
Click to collapse
Oh damn. It's KitKat that's the issue than? I'm out of the loop it seems. I was under the assumption it was the phone itself people couldn't root. It's KitKat that's causing the issue. Okay. Hmm, I wonder if there's any root methods for 4.4.2 yet....
Kin Kira said:
Why is EVERYONE so quick to shoot down the fact this cannot be rooted. Is anyone trying?
Click to expand...
Click to collapse
Yes, attempts have been made. Alas, without any success. See here. And this is the thread for it.
Kin Kira said:
Oh damn. It's KitKat that's the issue than? I'm out of the loop it seems. I was under the assumption it was the phone itself people couldn't root. It's KitKat that's causing the issue. Okay. Hmm, I wonder if there's any root methods for 4.4.2 yet....
Click to expand...
Click to collapse
Uh, that's what we've been saying. No, there's not except possibly for a few phones and all those methods have been tried with this and they didn't work as Motorola had already fixed those exploits.
The only way to root this phone under KitKat is to have an unlocked bootloader, and there is NO way to do that anymore, period.
The original unlocking exploit took the Dan a long time to find it and a lot of testing. That exploit is long gone and cannot be put back onto the phone as it was patched into a protected zone of the phone that even unlocked bootloaders do not have access to write to. So, there is NO way to flash back to a previous version of JB that had the exploit and have it "patch" the exploit back in. Yes, you'll go back to JB, but not exploit will be there.
And please understand the frustration from some of us - you're is possibly the 200th time this was asked. If you actually searched the forums and read the postings, you would see there are huge threads about this issue. That's the main reason why so many of us are frustrated with this question because it keeps getting asked and it's sitting right here in other threads and so, the forum is getting polluted with the same question being asked, over and over again. If people would just take the time to research for themselves rather than just jumping in and asking the question, it would make this forum lest polluted. What's funny is, the questions all come from people who have just registered on this forum (they all had posts < 10). It's very frustrating.
Are all of the One A9s ordered direct from HTC able to be BL unlocked right from HTC or is there still a process outside of that? Does it wipe the device?
Hoping to get the device and quickly root to maybe use apps like greenify to get some tolerable battery life. All the reviews say battery is terrible.
Sent from my E5823 using Tapatalk
You unlock the boot loader via htc.dev and s-off with sunshine, read the thread about it. Good luck it is not that hard to do, and the 25$ to s-off is well spent money.
You're able to use htc dev program to unlock the bootloader. If you got yours directly from htc and if it's the developer edition then the bootloader comes unlocked with no warranty void. Unlocking the bootloader through htc dev does in fact wipe your device. Once I obtained the device from att I unlocked the bootloader, flashed twrp and installed the latest supersu beta for systemless root. Afterwards I booted up, installed sunshine and purchased s-off. After I gained s-off I converted to the developer edition by changing my cid to BS_US001 (dev edition) and flashing the corresponding firmware. As of now there are flashable zips from @Captain_Throwback that are prerooted. If you're looking to use greenify or amplify than I'd recommend the deodexed version as that makes it more stable for the xposed framework.
Wait you have to pay to get root?
Sent from my E5823 using Tapatalk
Not for root. For S-Off.
Don't you need s-off for root?
Sent from my E5823 using Tapatalk
It seems like you can read , and all your questions are covered in multiple threads already, thre are FAQ sections to. Just try to find them before starting another thread about it.
jaypeg123 said:
It seems like you can read , and all your questions are covered in multiple threads already, thre are FAQ sections to. Just try to find them before starting another thread about it.
Click to expand...
Click to collapse
The purpose of forums is to collaborate and help. Every single phone manufacturer does things differently and every forum is setup differently. I checked the top threads in general and QA and didn't see my answers.
Sent from my E5823 using Tapatalk
I am sorry if I offended you, but this is not a chat app , and the rooting thread is one of the first an biggest in here, the info in a forum like this are intended to be used, and we can't shout out a question in a new thread the second it pops up in our head. Then we will never find anything around here, I often go back and read up on things so that I am sure of things, this xda forum has so much knowledge saved and there must be some kind of structure to get it to work. Try look up how many members we have, you will be surprised..