Related
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
I'm looking to move to the latest software but non ota so I can keep root and unlock boot loader. I can't seem to find any roms.
jagri44451 said:
I'm looking to move to the latest software but non ota so I can keep root and unlock boot loader. I can't seem to find any roms.
Click to expand...
Click to collapse
how did you unlock your bootloader may i ask?
I did it before the update then used one on here that didn't lock it
All that is available are AOSP ROMs or CM11. No one has been able to get the new kitkat kernel to boot with our old firmware. :crying:
At this point, I'm happy with DU weekly builds. Don't really miss Touchwiz, I do flash MOAR sometimes. However, I still things run much better on vanilla android.
sjpritch25 said:
All that is available are AOSP ROMs or CM11. No one has been able to get the new kitkat kernel to boot with our old firmware. :crying:
At this point, I'm happy with DU weekly builds. Don't really miss Touchwiz, I do flash MOAR sometimes. However, I still things run much better on vanilla android.
Click to expand...
Click to collapse
While that is correct there are several decent versions of aosp and other variations. I would seriously look around for what's available but stay away from anything that says BL LOCKED or any variation of that
From my S3 on Wicked 4.3
ShapesBlue said:
While that is correct there are several decent versions of aosp and other variations. I would seriously look around for what's available but stay away from anything that says BL LOCKED or any variation of that
From my S3 on Wicked 4.3
Click to expand...
Click to collapse
I've been having recurring camera reboots on my stock, rooted, BL-unlocked ROM and really want to get away from that. Does either CM or any of the crop of AOSP ROMs of 4.4 for similarly unlocked devices manage to work well w/ phone hardware (e.g., cameras work properly, mic works properly, bluetooth works properly) without being too "1337 g4m3r XT3M3!!!"? I'd like a fairly simple layout, to be honest, without a bunch of crufty, automatic extra features. Just a plain, 4.4.4 ROM that actually lets me take more than one picture before rebooting
Armando Penblade said:
I've been having recurring camera reboots on my stock, rooted, BL-unlocked ROM and really want to get away from that. Does either CM or any of the crop of AOSP ROMs of 4.4 for similarly unlocked devices manage to work well w/ phone hardware (e.g., cameras work properly, mic works properly, bluetooth works properly) without being too "1337 g4m3r XT3M3!!!"? I'd like a fairly simple layout, to be honest, without a bunch of crufty, automatic extra features. Just a plain, 4.4.4 ROM that actually lets me take more than one picture before rebooting
Click to expand...
Click to collapse
Nope. I believe you have to pay $50 to jtag your device back to an unlocked bootloader. I maybe wrong, but i believe that is the only hope. For the time being, the only unlockable devices seem to be HTC.
sjpritch25 said:
Nope. I believe you have to pay $50 to jtag your device back to an unlocked bootloader. I maybe wrong, but i believe that is the only hope. For the time being, the only unlockable devices seem to be HTC.
Click to expand...
Click to collapse
No, my phone's currently on the unlocked 4.3 build floating around the forums; i was wondering which of the unlocked 4.4 builds (e.g., AOSP, Cyanogenmod) was most stable, since there isn't a TW build compatible with my unlocked bootloader.
Armando Penblade said:
No, my phone's currently on the unlocked 4.3 build floating around the forums; i was wondering which of the unlocked 4.4 builds (e.g., AOSP, Cyanogenmod) was most stable, since there isn't a TW build compatible with my unlocked bootloader.
Click to expand...
Click to collapse
I like the Dirty Unicorn
https://plus.google.com/107557684350196595860/posts/Hk5z6BCnX1m
Questions and Help issues belong in Q&A, Help and Troubleshooting...not Original Development
All the development sections are only for developers to post work
As for looking for the "best" or "most stable" ROMs it is strongly advised that you read the development threads yourself
Find out what bugs and fixes are offered in the thread and if that appeals to you, or has a bug YOU can live with
No one can pick your ROM for you nor should they...in the end only YOU know what it is best for YOU.
As a general tip, stay away from Nightlies if you want stability as new fixes and bugs are presented often in those.
Hi there,
I know this May be a silly question but my iPhone 5s is getting on my last nerves and this is the only thing holding me back from ordering a Z3 today. Does anyone have any idea when the first custom roms will be out for the z3? I can't stand skinned androids (although I've never owned a Sony handset before).. I just wouldn't want to buy one and having to wait a few months for CM/PA.
Thanks for anyone who replies!
gazzaman2k said:
got my SimpleTech 256 sd card and i must say its f00king fast i can tell you that made in Japan, 10mb/s read/write speed and works flawlessly with tomtom and is even faster then my dads ipaq 3870 using 66x CF lol
only £37 from ebay might have to order another soon
no data erase yet and its on FAT16 named again to storage
Click to expand...
Click to collapse
Mate what's wrong wid or iPhone by the way. One of the best phones on the market. Anyways about custom ROMs or PA/CM ROMs might come by end of Oct or Nov. No one knows but they are surely in the pipeline although I love the xperia UI which is close to stock android and the best among other OEM skins. I have come on an xperia from an iPhone. Trust me xperia is the only one phone where u would enjoy the touch sensitivity like the iPhone.
dj_richard05 said:
Mate what's wrong wid or iPhone by the way. One of the best phones on the market. Anyways about custom ROMs or PA/CM ROMs might come by end of Oct or Nov. No one knows but they are surely in the pipeline although I love the xperia UI which is close to stock android and the best among other OEM skins. I have come on an xperia from an iPhone. Trust me xperia is the only one phone where u would enjoy the touch sensitivity like the iPhone.
Click to expand...
Click to collapse
I love the iphones when they are jailbreakable but for the next forseeable months I can't see an ios 8 JB being released... I love the freedom on Android and constantly find myself going back to iPhone due to the lack of a decent camera found on any Android handsets (I've owned HTC One, S5, Note 3, S4, Nexus 5)..
You can't find a decent camera on any Android phone?
And you go to an iPhone for their cameras? Rly? Hahahaha hahaha you're funny.
Why are there almost no custom roms for this phone. The Android development section has 11 posts?
Other phones have thousands. Why is that.
I was thinking to buy one of these, but this sets me off.
Is there a root , that doen´t void warranty ?
thx
nearlygod said:
Why are there almost no custom roms for this phone. The Android development section has 11 posts?
Other phones have thousands. Why is that.
I was thinking to buy one of these, but this sets me off.
Is there a root , that doen´t void warranty ?
thx
Click to expand...
Click to collapse
No there is no Lock Bootloader with root atm. I would guess once that is solved there will be more custom roms.
nearlygod said:
Is there a root , that doen´t void warranty ?
thx
Click to expand...
Click to collapse
buda81 said:
No there is no Lock Bootloader with root atm. I would guess once that is solved there will be more custom roms.
Click to expand...
Click to collapse
Most custom roms (CM MIUM AOKP AOSP PAC) etc require an unlocked bootloader as well as root. Unlocking the boot voids warrenty, hence the disclaimer in the OP of all their ROMS.
Root with a locked bootloader will only lead to custom roms based on stock firmware. they have more customisation than stock, but not as much as true custom roms based on another kernel.
gregbradley said:
Most custom roms (CM MIUM AOKP AOSP PAC) etc require an unlocked bootloader as well as root. Unlocking the boot voids warrenty, hence the disclaimer in the OP of all their ROMS.
Root with a locked bootloader will only lead to custom roms based on stock firmware. they have more customisation than stock, but not as much as true custom roms based on another kernel.
Click to expand...
Click to collapse
Ok, thanks. Still , although the warranty is lost. There is still so little activity. Why is that. I just read the news, that Sony release AOSP Versions for all phones and allows the bootloaders to be unlocked. I thought that this would be a developers dream, for CM for example.
So, whats wrong with the phone. I still dont get it.
Was considering z3 went with g3 as there seems like way more dev support for LG phone and tons of LP roms in alpha beta stage.
Whats up with sony?
No one want to root because of loss of DRM keys..
And what does that mean?
thx
I'm not sure if it's a good idea to resurrect a old thread (zombies!)
but i see there are almost no custom roms for Z3 (either stock based or AOSP or something else)
the stock based are still on Kitkat.. (1 Rom)
AOSP i see only Cyanogen but with very little development (of course a pair of roms based on CM).
The freexperia project is almost non functional.
I'm not demoting the devs / modders... just not finding the root cause of this.
The Very old Samsung S3 is still getting too much love than our new phone, that has qualcomm SOC and thus, unlimited (sort of) open source development
Something is wrong with this phone or i'm missing something?
Im waiting too..
smala said:
I'm not sure if it's a good idea to resurrect a old thread (zombies!)
but i see there are almost no custom roms for Z3 (either stock based or AOSP or something else)
the stock based are still on Kitkat.. (1 Rom)
AOSP i see only Cyanogen but with very little development (of course a pair of roms based on CM).
The freexperia project is almost non functional.
I'm not demoting the devs / modders... just not finding the root cause of this.
The Very old Samsung S3 is still getting too much love than our new phone, that has qualcomm SOC and thus, unlimited (sort of) open source development
Something is wrong with this phone or i'm missing something?
Click to expand...
Click to collapse
Stock is good enough.
I know stock is great. Just wonder if a modified custom ROM could squeeze the battery further. I doubt it but u never know.
Sindroid said:
I know stock is great. Just wonder if a modified custom ROM could squeeze the battery further. I doubt it but u never know.
Click to expand...
Click to collapse
It could happen, that is true, I'm sure soon Z3 will have some custom ROM's for users to play with, on it.
hello all, I just bought this device for around $630 in AUD brand new with a spigen case included thought it was time for a upgrade came from a nexus 5 running AICP 6.0.1 HammerheadCAF with racer caf kernel also has the latest twrp so when it comes to flashing stuff I know what I'm doing.... anyway I noticed there is very little for the s6 compared to other devices ive bought from google so can you guys point me out to the most stable, most recent custom rom, looking for little to no bloatware As it takes up in size.... as far as the device goes I have not received it yet just getting prepared for when it does arrive. need directions to rooting and custom recovery as well not sure if the bootloader needs to be unlocked? I'm aware that this device is 64 bit so is that the reason for very little mods or just lack of devs?
I also noticed that there is such a thing called alliance framework which helps with customizing the rom as well as theming am I right?
all these things are considered so with that being said I would like to know what you guys are running and whats the best out there in your opinion at this point it time :angel:
Hi,
First regarding the most stable or best ROM, I suggest you to, as you probably did with the Nexus 5, look the threads and check for complaints of bugs and features, so that you can know what's the best for you. There are lots of debloated ROMs, and most say so already in the thread title.
About the lack of development, it's due to Samsung processor Exynos. Since Samsung takes too long or doesn't even release the processor documentation and development sources, it is very hard to develop anything that is not based on TouchWiz, which is Sammy's framework on the stock ROM. Recently the CyanogenMod Team took the Galaxy S6 as an official branch, so I believe that we will have a CM based ROM soon and I hope it will bring more development to our device!
I don't know about that framework, although if it's something that is used on the S6, then you will probably find it in any development or general section.
Rooting is as simple as flashing TWRP and SuperSU, although it'll trip your Knox, which is a flag in the bootloader that shows that something was modified in your device, there is no way to reverse and on most countries it results in void warranty. If your device ships with Android 5.0.2, then you can try using Ping Pong Root (again, just check the development threads for it), which is a root method that doesn't trip Knox.
I'm still running stock since I'm waiting to try out Samsung Pay, which requires untouched Knox. So yeah, welcome to the S6 family! Hope you enjoy your device . If I forgot to answer anything let me know.
All the best,
~Lord
Sent from my SM-G920I using Tapatalk
Advice : Keep your knox working update to MM setback and relax the best and fast rom is Marshmallow
In my understanding (correct me if I am wrong) sgs7 us version with SD820 have locked bootloader and anything custom is really hard to do. People need to hack phone to do anything. With International Exynos version on other hand it's not as bad. We had custom recovery on first day and I do see ROM out there but it's slimmed down version of stock.
So it is possible to install custom Roms, but why there is none available. For years I've been using cm and I would very much to start using it again.
Thank you.
russiandivxclub said:
In my understanding (correct me if I am wrong) sgs7 us version with SD820 have locked bootloader and anything custom is really hard to do. People need to hack phone to do anything. With International Exynos version on other hand it's not as bad. We had custom recovery on first day and I do see ROM out there but it's slimmed down version of stock.
So it is possible to install custom Roms, but why there is none available. For years I've been using cm and I would very much to start using it again.
Thank you.
Click to expand...
Click to collapse
First of all, there are a few roms already available for the exynos variant, but they are all TW based. The reason why there are no other roms, is that the Qualcomm s7's bootloader is locked and it will stay that until samsung decides to unlock it. As for the exynos variant, the source code is not open which makes it very difficult for developers to build a rom. So before buying this phone, you should have done more research, because even if developers are able to build a cool rom like Cyanogenmod, then there is a very little change you will be able to use it as your daily driver. So this means that samsung is not developer friendly and it won't change until samsung decides otherwise.
This is the Development forum, not your own personal Q&A. Put threads in correct sections. Reported.
Lol it is q&a section buddy.
Thank you for your answer. I've gotten new Exynos Variant from work and I was thinking putting some custom ROM on it. Thank you for explaining this to me.
Cheers
russiandivxclub said:
Lol it is q&a section buddy.
Thank you for your answer. I've gotten new Exynos Variant from work and I was thinking putting some custom ROM on it. Thank you for explaining this to me.
Cheers
Click to expand...
Click to collapse
enjoy
http://forum.xda-developers.com/s7-edge/development/vr-560-tekxnesis-hybrid-s7e-urv1-00-00-t3357561