Related
Ok, i know this is a question in the dev section but i think it belongs here, if mods think different then please move.
As the title says really - if i choose not to try the S-OFF - will i be left behind later on down the line with regard to custom ROM's??
If i bricked my phone the wife would go bonkers, so i am really wary at the moment with trying it as there is a higher chance of bricking it. Anyhow thats a seperate issue..
So maybe some devs can answer my question??.. Am i at some point gonna have to take the plunge or is it more of a nice thing to have, more than a necessity?
Or is there likely to be a later version that has a lesser chance of bricking if does go wrong??
Cheers all for any replies..
I think that if a custom ROM requires S-OFF it will have a good reason, or the dev is being lazy.
Also HTC is very likely to plug the exploit that gives S-OFF at some point, if it's possible to do so.
Moved to Q&A as not development
You dont need a security unlocked device, there will be no diffrence apart from the fact you wont have any write access to the nand chip while the device is booted
Sent from a stoned haze, using Royal Mail
Kool.. So more of a nice thing to have rather than a must!. Appreciate replies.. I will hold off doing it.
Cheers
wingnutta said:
Kool.. So more of a nice thing to have rather than a must!. Appreciate replies.. I will hold off doing it.
Cheers
Click to expand...
Click to collapse
It really is a simple procedure though, its as easy as booting a live cd, connectiong your device and pressing enter
AndroHero said:
It really is a simple procedure though, its as easy as booting a live cd, connectiong your device and pressing enter
Click to expand...
Click to collapse
I do agree from what i have read, but for me personally the risk at this time is too much.. If anything did go wrong i would be kicking myself.
Maybe at a later date as i said if a more less risky version comes out.
wingnutta said:
I do agree from what i have read, but for me personally the risk at this time is too much.. If anything did go wrong i would be kicking myself.
Maybe at a later date as i said if a more less risky version comes out.
Click to expand...
Click to collapse
No such thing. It's not the application that's risky, it's the procedure in general. You're in essence flashing the lowest level of your phone, if it fails the phone will be useless but the chance of it failing is almost negligible.
one thing i am willing to ask. does that mean that turning security to off, you do not need to pay for unlock codes? you can just turn s-off and flash a rom and it will unlock the phone?
sorry for the dumb question!
S-OFF won't sim unlock the phone.
A lot of people are flashing this without knowing what it does, which is just plain stupid. The risk is minimal, but there is a risk that it will totally brick the phone permanently. Nobody should flash it unless they want to use S-OFF for something. It'll also absolutely guaranteed to void the warranty, there's no way HTC will touch a phone if you return it with the S-OFF bootloader (though it is easy to remove).
At the moment it's most useful for devs, in order to test changes without the need for reboot/recovery/reboot.
teppic74 said:
S-OFF won't sim unlock the phone.
A lot of people are flashing this without knowing what it does, which is just plain stupid. The risk is minimal, but there is a risk that it will totally brick the phone permanently. Nobody should flash it unless they want to use S-OFF for something. It'll also absolutely guaranteed to void the warranty, there's no way HTC will touch a phone if you return it with the S-OFF bootloader (though it is easy to remove).
At the moment it's most useful for devs, in order to test changes without the need for reboot/recovery/reboot.
Click to expand...
Click to collapse
+1
no need for normal usage of the phone ... you can also do all without s-off ... with s-off you dont have to reboot everytime ...
teppic74 said:
S-OFF won't sim unlock the phone.
A lot of people are flashing this without knowing what it does, which is just plain stupid. The risk is minimal, but there is a risk that it will totally brick the phone permanently....
At the moment it's most useful for devs, in order to test changes without the need for reboot/recovery/reboot.
Click to expand...
Click to collapse
That statement will do me nicely! Me not a dev...
Hey everybody,
I'm planning on getting my GN in the next two weeks and wanted to ask a simple question:
first of all - I will want my GN to be a yakju, I will want to root it and I will want to unlock the bootloader.
Now, I believe I have everything understood just wanted to be sure if you could help me..
these are the steps I will take:
1. Check if GN is yakju
1.1 If GN is yakju simply use the gnex toolkit to unlock bootloader and root.
FINISH.
2. If GN is not yakju -
2.1 Use step-by-step (http://forum.xda-developers.com/showthread.php?t=1391881) to change rom to yakju 4.0.4.
2.3 Then use gnex toolkit to root (already unlocked bootloader in 2.1).
FINISH.
Am I good to go?
TNX!
Pretty much thats the way it should be,,, advance congrats for the next awesome purchase u r going to make,,,
deepayanneogi said:
Pretty much thats the way it should be,,, advance congrats for the next awesome purchase u r going to make,,,
Click to expand...
Click to collapse
Thanks mate! can't wait already
More replies are welcome.. I just want to feel certain I'm on the right track here..
Be a big boy and don't use a tool kit =]
My guide makes it super simple...
Stickied above and linked in my sig.
Jubakuba said:
Be a big boy and don't use a tool kit =]
My guide makes it super simple...
Stickied above and linked in my sig.
Click to expand...
Click to collapse
Hey tnx
I do consider myself an open minded guy and also I usually like to know the bits and insides stuff of things I do, I will usually prefer going the longer way (I.E - rooting\unlocking bootloader) then to just use the toolkit and pressing "next, next, next" because I prefer to know what every "next" does, BUT in this case, I think I managed to (obsessively) learn what everything does, so I decided to take the shorter trip to rooting+unlocking BL, do you think the toolkit has any disadvantages over the longer way?
omricn said:
Hey tnx
I do consider myself an open minded guy and also I usually like to know the bits and insides stuff of things I do, I will usually prefer going the longer way (I.E - rooting\unlocking bootloader) then to just use the toolkit and pressing "next, next, next" because I prefer to know what every "next" does, BUT in this case, I think I managed to (obsessively) learn what everything does, so I decided to take the shorter trip to rooting+unlocking BL, do you think the toolkit has any disadvantages over the longer way?
Click to expand...
Click to collapse
If it works it works.
The thing I hate about 'em is...
If a user has a soft-bricked phone.
Comes on here...asks for help.
And I tell him to do some adb/fastboot procedure: he asks "lul wut?"
And we have to help him set that up...and assume he set it up correctly.
He then might complain "oh, ya. It won't recognize my device."
Which is possible in some soft-brick situations...but it also might be user error.
Thus making trouble-shooting/fixing 10x harder.
Just...do yourself a favor and make sure ADB/Fastboot work.
run "adb devices"
and "fastboot devices"
If both of those recognize your phone...I guess the toolkit is fine.
As you said, you know whats going on...so what's the harm?
That seems about right. Just be a little cautious when flashing a radio or bootloader, as any of those two when flashed wrong can **** your device up beyond self-repair.
An incorrectly flashed system or boot is "easily" fixable, though.
Theshawty said:
That seems about right. Just be a little cautious when flashing a radio or bootloader, as any of those two when flashed wrong can **** your device up beyond self-repair.
An incorrectly flashed system or boot is "easily" fixable, though.
Click to expand...
Click to collapse
Tnx Actually I'm not going to flash custom roms\radios\BL's just yet (if ever), just going to flash the official 4.0.4 yakju from Google, including the radio that comes with that bundle
Jubakuba said:
If it works it works.
The thing I hate about 'em is...
If a user has a soft-bricked phone.
Comes on here...asks for help.
And I tell him to do some adb/fastboot procedure: he asks "lul wut?"
And we have to help him set that up...and assume he set it up correctly.
He then might complain "oh, ya. It won't recognize my device."
Which is possible in some soft-brick situations...but it also might be user error.
Thus making trouble-shooting/fixing 10x harder.
Just...do yourself a favor and make sure ADB/Fastboot work.
run "adb devices"
and "fastboot devices"
If both of those recognize your phone...I guess the toolkit is fine.
As you said, you know whats going on...so what's the harm?
Click to expand...
Click to collapse
I catch your drift, and I know exactly what you mean.. I'm an IT guy, and apart from my job, I always learn everything there is to know about anything before I buy\change it in any way, to always be super safe and know what to do in every situation I can encounter.
Before I do something I will triple check what could and can happen so that I'm always 3 steps ahead. Thats the reason I already know almost everything there is to know about this phone, about rooting it, about unlocking it, ADB, fastboot etc. even before I bought it call me crazy..
Not crazy by my standards.
I actually did the same thing...
Even posted a thread "OMG LULZ SO I DO THIS, RIGHT?" as you have...
Because I was excited as hell and wanted to reassure myself.
You'll love 'er.
Best phone I've owned...by far.
While the OS (and a Nexus on Verizon...which we thought we'd NEVER see) is a HUGE part of it...
I was/am actually impressed with the hardware as well.
I could go on and on and on about my Droid X (Got it on release day...didn't fully understand the implications of a locked bootloader...and how it would hinder the experience over that of my Original Droid) and how much I hated having a locked bootloader.
That was MY main push. I was like...Oh. My. God. A Nexus?! That **** is MINE.
</rambling>
This phone STILL gives me the shivers.
Love it.
The 4.0.4 radio and bootloader will do for many more releases, I think. I don't think it's the radio's fault for the signal drops as a simple overclocking counters it.
Jubakuba said:
Not crazy by my standards.
I actually did the same thing...
Even posted a thread "OMG LULZ SO I DO THIS, RIGHT?" as you have...
Because I was excited as hell and wanted to reassure myself.
You'll love 'er.
Best phone I've owned...by far.
While the OS (and a Nexus on Verizon...which we thought we'd NEVER see) is a HUGE part of it...
I was/am actually impressed with the hardware as well.
I could go on and on and on about my Droid X (Got it on release day...didn't fully understand the implications of a locked bootloader...and how it would hinder the experience over that of my Original Droid) and how much I hated having a locked bootloader.
That was MY main push. I was like...Oh. My. God. A Nexus?! That **** is MINE.
</rambling>
This phone STILL gives me the shivers.
Love it.
Click to expand...
Click to collapse
Best. Reply. Ever.
I just managed to get this device from someone the other day. Having been an iphone 5c user for a while, going to a 5c after my last frustrating and horrible android experience with an HTC inspire device, I am back on android for the storage expansion so that I can play emulator games- only to find myself pulling my hair out ONCE AGAIN after all the numerous conflicting advice/ threads/tutorials out here which I have countless wasted hours on already. I don't have time to read through tutorials promising a downgrade from lollipop to kit kat, in hopes of a root so I can pair my ps3 controller wirelessly to my device... constantly stuck on odin failing and what have you, so just give it to me dry and clean. Please help as this is extremely frustrating and annoying.
Can I or can I not root this device? if so How? ( please provide detailed instructions as i don't know what the lingo is around here) If not i'm putting this thing right back on craigslist where I got it from. I am running 5.0.1
All I want to do is pair my ps3 controller wirelessly to my note 4, thought I would be able to do that until sixaxis said it needed 'root access' :silly:
if theres a way to circumvent this, please let me know. I do NOT WANT to use a corded controller with this. Battery life is already kinda sucky on this phone so i'll ened to charge the device as i'm playing
Sunaj1 said:
I just managed to get this device from someone the other day. Having been an iphone 5c user for a while, going to a 5c after my last frustrating and horrible android experience with an HTC inspire device, I am back on android for the storage expansion so that I can play emulator games- only to find myself pulling my hair out ONCE AGAIN after all the numerous conflicting advice/ threads/tutorials out here which I have countless wasted hours on already. I don't have time to read through tutorials promising a downgrade from lollipop to kit kat, in hopes of a root so I can pair my ps3 controller wirelessly to my device... constantly stuck on odin failing and what have you, so just give it to me dry and clean. Please help as this is extremely frustrating and annoying.
Can I or can I not root this device? if so How? ( please provide detailed instructions as i don't know what the lingo is around here) If not i'm putting this thing right back on craigslist where I got it from. I am running 5.0.1
All I want to do is pair my ps3 controller wirelessly to my note 4, thought I would be able to do that until sixaxis said it needed 'root access' :silly:
if theres a way to circumvent this, please let me know. I do NOT WANT to use a corded controller with this. Battery life is already kinda sucky on this phone so i'll ened to charge the device as i'm playing
Click to expand...
Click to collapse
Have not read enough, if you have a Verizon locked bootloader... Recommend to put it right away to Craigslist because no root has been found good luck
If you can deal with root on a temp basis, meaning it is lost every reboot, then go that route. Otherwise as EdrickMg stated, it is not available.
How do I know whether the bootloader is locked or not? I might want to buy an N910V, as its much cheaper than international/Indian version, but I need to make sure whether or not the bootloader is unlocked. Cause I can't even think about not rooting a phone in first one hour of purchase. What could I ask the seller to confirm about the bootloader?
If it's a Verizon Note 4, then the bootloader is locked. There is no permanent rooting method for this phone. People are still hopeful that there might be one coming, but I'm willing to bet that there'll never be a method to root it. This phone has been out since October of 2014, with no root method found. There is a temporary root method that will allow you to root your phone, but the next time you reboot, it's gone and your phone is re-locked. To me, that's a lot of effort for something that you lose whenever you reboot your phone, but that's just my opinion. Also, this temporary root is just root - it doesn't unlock your bootloader.
If you absolutely must have a rootable phone with unlocked bootloader, then look elsewhere.
The only thing that we do have is debloater, which is a method that allows us to turn off and block almost anything we want. For me, that's enough, because the only reason I'd want root is to uninstall all of the crap that comes with this phone. It doesn't get rid of the junk, it just turns it off and keeps it from running.
If you want root to be able to install an ad blocker or to install custom kernels and/or ROMs, you cannot do it on this phone and likely (in my opinion), never will be able to.
Okay, I don't understand all these contract things as we don't have them in our country, but Verizon Note 4 and N910V, they are different? If not, how come there is a custom ROM and kernel for the SM-N910V model? The phone does show a red screen where Verizon is written on it. I am not understanding this!
ithehappy said:
Okay, I don't understand all these contract things as we don't have them in our country, but Verizon Note 4 and N910V, they are different? If not, how come there is a custom ROM and kernel for the SM-N910V model? The phone does show a red screen where Verizon is written on it. I am not understanding this!
Click to expand...
Click to collapse
There is a Verizon Note 4 Developers Edition that comes with an unlocked bootloader and it is rootable. I had to buy it straight from Samsung at full retail price. Totally worth it in my opinion. It is no longer available for sale on the Samsung site though
usmaak said:
If it's a Verizon Note 4, then the bootloader is locked. There is no permanent rooting method for this phone. People are still hopeful that there might be one coming, but I'm willing to bet that there'll never be a method to root it. This phone has been out since October of 2014, with no root method found. There is a temporary root method that will allow you to root your phone, but the next time you reboot, it's gone and your phone is re-locked. To me, that's a lot of effort for something that you lose whenever you reboot your phone, but that's just my opinion. Also, this temporary root is just root - it doesn't unlock your bootloader.
If you absolutely must have a rootable phone with unlocked bootloader, then look elsewhere.
The only thing that we do have is debloater, which is a method that allows us to turn off and block almost anything we want. For me, that's enough, because the only reason I'd want root is to uninstall all of the crap that comes with this phone. It doesn't get rid of the junk, it just turns it off and keeps it from running.
If you want root to be able to install an ad blocker or to install custom kernels and/or ROMs, you cannot do it on this phone and likely (in my opinion), never will be able to.
Click to expand...
Click to collapse
I'm happy with a temp root, itll fit my purposes. Can you point me in that direction? and the debloaters direction?
yes sad, so sad that Permanent root was never fount! I am disappointed with Verizon over this......
DikStarrbuck said:
I'm happy with a temp root, itll fit my purposes. Can you point me in that direction? and the debloaters direction?
Click to expand...
Click to collapse
It's all in topics in the forum. Easy to find if you look.
Sent from my SM-N910V using XDA Free mobile app
RedsonRising said:
It's all in topics in the forum. Easy to find if you look.
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Yea, theres SO much stuff in the forum, I honestly dunno what to look for. I'll keep at it, thanks
So what if u have a bootloader that starts with 15? I got 90% on kingoroot running a crap ton of random apps in the backgroundI thought I had it but bam root failed keep in mind I'm on marshmallow to anyone else get 90% are we really close or is it just a trick lol
custom_roms_epeptic said:
So what if u have a bootloader that starts with 15? I got 90% on kingoroot running a crap ton of random apps in the backgroundI thought I had it but bam root failed keep in mind I'm on marshmallow to anyone else get 90% are we really close or is it just a trick lol
Click to expand...
Click to collapse
So your bootloader is unlocked already, correct? You need to have an unlocked bootloader and be running Lollipop, here's the thread that shows you how/what to do...
https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
I used the instructions in that thread and didn't have any issues.
driguy said:
So your bootloader is unlocked already, correct? You need to have an unlocked bootloader and be running Lollipop, here's the thread that shows you how/what to do...
https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
I used the instructions in that thread and didn't have any issues.
Click to expand...
Click to collapse
Thanks bud I'll try it tonight! I gone like 6 pages into Google trying to find something that works I got a little confused on the baseband version part. This is a silly question but if I have mine on
N910VVRU2CPF3 and use Odin and flash version: N910VVRU1ANJ5 it won't brick my device? And no my bootloader is not unlocked yet
custom_roms_epeptic said:
Thanks bud I'll try it tonight! I gone like 6 pages into Google trying to find something that works I got a little confused on the baseband version part. This is a silly question but if I have mine on
N910VVRU2CPF3 and use Odin and flash version: N910VVRU1ANJ5 it won't brick my device?
Click to expand...
Click to collapse
You'll want to flash the N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar .md5 file in ODIN as that is the firmware that Lollipop expects/works on. I don't know what android version N910VVRU1ANJ5 firmware is for. Flashing N910VVRU1ANJ5 shouldn't brick your phone but you will need to have it on N910VVRU2BPA1 to install Lollipop and root.
Trust me, just follow the instructions in the post I previously linked. It's all laid out for you in what is pretty much the easiest way you can do it. As long as you do it in the order listed, with the files provided, it will work.
driguy said:
You'll want to flash the N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar .md5 file in ODIN as that is the firmware that Lollipop expects/works on. I don't know what android version N910VVRU1ANJ5 firmware is for. Flashing N910VVRU1ANJ5 shouldn't brick your phone but you will need to have it on N910VVRU2BPA1 to install Lollipop and root.
Trust me, just follow the instructions in the post I previously linked. It's all laid out for you in what is pretty much the easiest way you can do it. As long as you do it in the order listed, with the files provided, it will work.
Click to expand...
Click to collapse
Nj5 was kitkat but I will flash the version you said I greatly appreciate it
Wait hold on my bootloader is locked will it still work? Sorry for the annoying questions I'm a little rusty cause I only get a new phone every 2 years so I barely ever root lol
Rooting this phone is pretty tricky and you may have to repeat the process a few times for it to work. Follow the guide custom_roms_epeptic posted, that's the one I used and even though it took me a couple hours to go from stock to Nseven, it did indeed work. I would recommend using the version of kingoroot found in the zip contained in that guide, I tried kingroot and the newest version of kingoroot and both got hung up at 90% or just didn't work at all.
custom_roms_epeptic said:
Wait hold on my bootloader is locked will it still work? Sorry for the annoying questions I'm a little rusty cause I only get a new phone every 2 years so I barely ever root lol
Click to expand...
Click to collapse
Part of the steps you will be doing will be to unlock the bootloader, this is mandatory. If your CID starts with 15, you can change the CID of your device to that of a dev edition device, which can then have its bootloader unlocked. Like I said before, it's all laid out for you in the other thread.
driguy said:
Part of the steps you will be doing will be to unlock the bootloader, this is mandatory. If your CID starts with 15, you can change the CID of your device to that of a dev edition device, which can then have its bootloader unlocked. Like I said before, it's all laid out for you in the other thread.
Click to expand...
Click to collapse
Okay so I FLash the downgrade and then unlock the bootloader
,? Yes?
Just ordered my HTC 10, excited...and nervous as I've not had a new device (like long term) in... like over 1.5 years. :S I'm mainly hoping the microSD card slot likes my 128GB U1 x633 card so I can finally have enough space for all my vinyl rips, and then I hope the DAC is as good as they say.
So anyway, I've been reading all of this stuff about rooting and loosing the radio connection and something about the data encryption breaking everything O.O!!! Holy crap. I just wanna root it, find a good rom and dev to support and enjoy it. This is what I do on my current daily driver, my old OPO. I've been trying to look around, search, and read to make sure that I avoid all of these issues mentioned but so far I've not found a concrete explanation of why said issues happen. Not new to rooting/flashing at all, but HTC devices always seemed to of been touchy when it came to custom stuff, and I don't want to explode this thing. My main problem is that I've been away from HTC for.... well since early 2014.
My current knowledge of android stuffz tells me to:
1) Unlock Bootloader via ADB
2) Flash TWRP/Other Customer Recovery
3) Find sweet rom, flash and spend hours customizing
4) Flash xposed and go crazy with modules until the phone explodes and then scale it back to a realistic level
5) Enjoy Phone
6) Cake
HOWEVER... I remember HTC devices having a bit more complication due to things like... RUU and firmware.. I don't even remember what RUU means lol... But I remember when I had my M8 I was always fighting these dang firmware issues. While I ended up with a fantastic experience, I remember fighting for almost 2 months or so to get it to behave. Battery was out of control, phone was crashing, camera exploding. Oh man it sucked, but finally someone really cool was like... "Yo dude I had these issues, this is what you have to do with HTC stuff" , and after a full hour of flashing shiz I had the phone running smoothly and behaving correctly. Something about... you had to flash each level of the firmware and then reboot and...something. Like you couldn't just skip to the latest firmware? I don't remember exactly.
So anyway, the main question I have is. Could someone either
A.) Point me in the direction of a post or something to study to understand what to do and not do. I've searched but not really found anything solid. Something for folks who've been off the HTC scene for a while.
B.) If there isn't really a single post on this, perhaps if someone doesn't mind explaining this (even pm is fine) to me so I don't explord this expensive mofo and cry.
C.) Give me a hug, because I am nervous about having a new device O.O , it's been so long and I'm so used to Cm13 and xposed and all that jazz. I is be scared.
I would be grateful to any and all help/support.
Anyway, thanks in advanced guys and gals. :3
Locklear308 said:
Just ordered my HTC 10, excited...and nervous as I've not had a new device (like long term) in... like over 1.5 years. :S I'm mainly hoping the microSD card slot likes my 128GB U1 x633 card so I can finally have enough space for all my vinyl rips, and then I hope the DAC is as good as they say.
So anyway, I've been reading all of this stuff about rooting and loosing the radio connection and something about the data encryption breaking everything O.O!!! Holy crap. I just wanna root it, find a good rom and dev to support and enjoy it. This is what I do on my current daily driver, my old OPO. I've been trying to look around, search, and read to make sure that I avoid all of these issues mentioned but so far I've not found a concrete explanation of why said issues happen. Not new to rooting/flashing at all, but HTC devices always seemed to of been touchy when it came to custom stuff, and I don't want to explode this thing. My main problem is that I've been away from HTC for.... well since early 2014.
My current knowledge of android stuffz tells me to:
1) Unlock Bootloader via ADB
2) Flash TWRP/Other Customer Recovery
3) Find sweet rom, flash and spend hours customizing
4) Flash xposed and go crazy with modules until the phone explodes and then scale it back to a realistic level
5) Enjoy Phone
6) Cake
HOWEVER... I remember HTC devices having a bit more complication due to things like... RUU and firmware.. I don't even remember what RUU means lol... But I remember when I had my M8 I was always fighting these dang firmware issues. While I ended up with a fantastic experience, I remember fighting for almost 2 months or so to get it to behave. Battery was out of control, phone was crashing, camera exploding. Oh man it sucked, but finally someone really cool was like... "Yo dude I had these issues, this is what you have to do with HTC stuff" , and after a full hour of flashing shiz I had the phone running smoothly and behaving correctly. Something about... you had to flash each level of the firmware and then reboot and...something. Like you couldn't just skip to the latest firmware? I don't remember exactly.
So anyway, the main question I have is. Could someone either
A.) Point me in the direction of a post or something to study to understand what to do and not do. I've searched but not really found anything solid. Something for folks who've been off the HTC scene for a while.
B.) If there isn't really a single post on this, perhaps if someone doesn't mind explaining this (even pm is fine) to me so I don't explord this expensive mofo and cry.
C.) Give me a hug, because I am nervous about having a new device O.O , it's been so long and I'm so used to Cm13 and xposed and all that jazz. I is be scared.
I would be grateful to any and all help/support.
Anyway, thanks in advanced guys and gals. :3
Click to expand...
Click to collapse
I was in the same boat haven't owed an HTC since the Fuze running Windows lol and have been a loyal Samsung user since the S1 so the whole adb fastboot thing was a little overwhelming. I followed the guide in the forum and had a few hiccups but overall went pretty smooth. Adb is definitely not as user friendly as Odin on a Sammy device but not to difficult. My only tips would be make sure you have all the latest drivers, twrp, and adb installed. It seems pretty hard to permanently brick a device these days from my experience so I wouldn't worry to much. As far as the radio not working, as long as you keep your device encrypted you won't lose your radio. I'm sure the devs will find a fix for this soon enough. Enjoy your new 10!
Edit: I'm using a lexar 128gb 633x U1 micro sd and all is well. Worked with adoptable storage also but felt a little sluggish so I went back to using it as external storage.
AndroiderM said:
I was in the same boat haven't owed an HTC since the Fuze running Windows lol and have been a loyal Samsung user since the S1 so the whole adb fastboot thing was a little overwhelming. I followed the guide in the forum and had a few hiccups but overall went pretty smooth. Adb is definitely not as user friendly as Odin on a Sammy device but not to difficult. My only tips would be make sure you have all the latest drivers, twrp, and adb installed. It seems pretty hard to permanently brick a device these days from my experience so I wouldn't worry to much. As far as the radio not working, as long as you keep your device encrypted you won't lose your radio. I'm sure the devs will find a fix for this soon enough. Enjoy your new 10!
Click to expand...
Click to collapse
Well I am comfortable in adb :3 so that's not a worry. So un-enecrypting it is just an option, and I should just avoid it for now? What is the advantage of un-encrypting it?
What guide did you use? Also, what about all this firmware and ruu stuff?
Sorry for so many questions... Lol this thing wasn't cheap and I am nervous , BTW what setup do you have? Root? ROM?
Thanks for replying :3
Locklear308 said:
Well I am comfortable in adb :3 so that's not a worry. So un-enecrypting it is just an option, and I should just avoid it for now? What is the advantage of un-encrypting it?
What guide did you use? Also, what about all this firmware and ruu stuff?
Sorry for so many questions... Lol this thing wasn't cheap and I am nervous , BTW what setup do you have? Root? ROM?
Thanks for replying :3
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
From what I understand unencrypting breaks the radio. With it unencrypted you would get slightly better performance and boot times I think. I would definitely avoid it for now. I'm currently using twrp with Viper 10 rom. I've also used leedroid and still trying to find which one I prefer. I've only had my 10 for 3 days lol so I haven't found my sweet setup just yet. I left s-on for now as I don't really need it off.
No idea about the firmware and ruu stuff. I made a backup of stock rom before I started flashing. I'm pretty sure there is or will be a repo with factory firmware, radios, etc. I don't know what ruu stands for either lol.
---------- Post added at 06:56 AM ---------- Previous post was at 06:51 AM ----------
Did you get carrier or unlocked version
AndroiderM said:
http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
From what I understand unencrypting breaks the radio. With it unencrypted you would get slightly better performance and boot times I think. I would definitely avoid it for now. I'm currently using twrp with Viper 10 rom. I've also used leedroid and still trying to find which one I prefer. I've only had my 10 for 3 days lol so I haven't found my sweet setup just yet. I left s-on for now as I don't really need it off.
No idea about the firmware and ruu stuff. I made a backup of stock rom before I started flashing. I'm pretty sure there is or will be a repo with factory firmware, radios, etc. I don't know what ruu stands for either lol.
---------- Post added at 06:56 AM ---------- Previous post was at 06:51 AM ----------
Did you get carrier or unlocked version
Click to expand...
Click to collapse
Unlocked, at least that's what the guy on Swappa marked it as. *fingers crossed*
Got it for 510. One scratch on the metal
Alright so I will back things up and avoid the radio breaking stuff. I will check that link, thanks man
Locklear308 said:
Unlocked, at least that's what the guy on Swappa marked it as. *fingers crossed*
Got it for 510. One scratch on the metal
Alright so I will back things up and avoid the radio breaking stuff. I will check that link, thanks man
Click to expand...
Click to collapse
No problem, mine has two scratches on metal too lol but guy gave me $200 and unlocked htc 10 w uh oh protection and original receipt for my s7e at&t branded locked bootloader ?. Was a no brainer for me
Locklear308 said:
Just ordered my HTC 10, excited...and nervous as I've not had a new device (like long term) in... like over 1.5 years. :S I'm mainly hoping the microSD card slot likes my 128GB U1 x633 card so I can finally have enough space for all my vinyl rips, and then I hope the DAC is as good as they say.
So anyway, I've been reading all of this stuff about rooting and loosing the radio connection and something about the data encryption breaking everything O.O!!! Holy crap. I just wanna root it, find a good rom and dev to support and enjoy it. This is what I do on my current daily driver, my old OPO. I've been trying to look around, search, and read to make sure that I avoid all of these issues mentioned but so far I've not found a concrete explanation of why said issues happen. Not new to rooting/flashing at all, but HTC devices always seemed to of been touchy when it came to custom stuff, and I don't want to explode this thing. My main problem is that I've been away from HTC for.... well since early 2014.
My current knowledge of android stuffz tells me to:
1) Unlock Bootloader via ADB
2) Flash TWRP/Other Customer Recovery
3) Find sweet rom, flash and spend hours customizing
4) Flash xposed and go crazy with modules until the phone explodes and then scale it back to a realistic level
5) Enjoy Phone
6) Cake
HOWEVER... I remember HTC devices having a bit more complication due to things like... RUU and firmware.. I don't even remember what RUU means lol... But I remember when I had my M8 I was always fighting these dang firmware issues. While I ended up with a fantastic experience, I remember fighting for almost 2 months or so to get it to behave. Battery was out of control, phone was crashing, camera exploding. Oh man it sucked, but finally someone really cool was like... "Yo dude I had these issues, this is what you have to do with HTC stuff" , and after a full hour of flashing shiz I had the phone running smoothly and behaving correctly. Something about... you had to flash each level of the firmware and then reboot and...something. Like you couldn't just skip to the latest firmware? I don't remember exactly.
So anyway, the main question I have is. Could someone either
A.) Point me in the direction of a post or something to study to understand what to do and not do. I've searched but not really found anything solid. Something for folks who've been off the HTC scene for a while.
B.) If there isn't really a single post on this, perhaps if someone doesn't mind explaining this (even pm is fine) to me so I don't explord this expensive mofo and cry.
C.) Give me a hug, because I am nervous about having a new device O.O , it's been so long and I'm so used to Cm13 and xposed and all that jazz. I is be scared.
I would be grateful to any and all help/support.
Anyway, thanks in advanced guys and gals. :3
Click to expand...
Click to collapse
I'm on my third htc10. Exploded last two after rooting haha. Really not hard mate. Just read the guides provided and ask any questions you need. Most ppl on XDA will be helpful, and some will reply like me lol.
BTW, simple answer, unlock phone via HTC Dev, then flash Viper. Done.
purple patch said:
I'm on my third htc10. Exploded last two after rooting haha. Really not hard mate. Just read the guides provided and ask any questions you need. Most ppl on XDA will be helpful, and some will reply like me lol.
BTW, simple answer, unlock phone via HTC Dev, then flash Viper. Done.
Click to expand...
Click to collapse
Alright neato, so do I need to ensure I let it download any and all OTA's for the firmware before doing anything? Is s-off safe to get as well in regards to the issues I referred to in my OP above?
And his is this viper? Does it allow things like settings similar to cm and also allow for xposed?
Thanks for replying man, I feel more comfortable now as it sounds like there isn't anything crazy required to safely root this thing . Phew!!
Locklear308 said:
Alright neato, so do I need to ensure I let it download any and all OTA's for the firmware before doing anything? Is s-off safe to get as well in regards to the issues I referred to in my OP above?
And his is this viper? Does it allow things like settings similar to cm and also allow for xposed?
Thanks for replying man, I feel more comfortable now as it sounds like there isn't anything crazy required to safely root this thing . Phew!!
Click to expand...
Click to collapse
I got an M9 for my wife not that long ago and just had my 10 show up today and gonna root. Just do like the other dude said. Find a guide that says how to use HTC dev to unlock the bootloader. You can't just enter a command in adb like "unlock bootloader" and have it work. Go to the HTC dev website, make an account, pick your device and it walks you through the steps of unlocking the bootloader. That's really the only semi-difficult part IMO. Then proceed as normal. Download twrp, make a stock nand, download ROM, su binaries, kernel, etc. etc. go to recovery and flash. I'm sure there's a couple other steps in their but that's the basics.
As for Viper, it tends to come with so many mods built in, I'd personally be kind of reluctant to use xposed with it to to much modifying. It's a great ROM, but so is leedroid You can try each and see what you like, but if you want to more safely use xposed I'd personally go with leedroid.
DroidIt! said:
I got an M9 for my wife not that long ago and just had my 10 show up today and gonna root. Just do like the other dude said. Find a guide that says how to use HTC dev to unlock the bootloader. You can't just enter a command in adb like "unlock bootloader" and have it work. Go to the HTC dev website, make an account, pick your device and it walks you through the steps of unlocking the bootloader. That's really the only semi-difficult part IMO. Then proceed as normal. Download twrp, make a stock nand, download ROM, su binaries, kernel, etc. etc. go to recovery and flash. I'm sure there's a couple other steps in their but that's the basics.
As for Viper, it tends to come with so many mods built in, I'd personally be kind of reluctant to use xposed with it to to much modifying. It's a great ROM, but so is leedroid You can try each and see what you like, but if you want to more safely use xposed I'd personally go with leedroid.
Click to expand...
Click to collapse
Oh right, I do remember about the whole HTC dev website thing. I was mainly just concerned with the firmware issues and stuff that I had before.
Is there any kind of limitations for reasons not to upgrade to the highest available firmware? Something like, maybe the highest one can't be rooted yet or something like that. I just want to make sure that I don't shoot myself in the foot haha.
Thank you all for your help
Locklear308 said:
Oh right, I do remember about the whole HTC dev website thing. I was mainly just concerned with the firmware issues and stuff that I had before.
Is there any kind of limitations for reasons not to upgrade to the highest available firmware? Something like, maybe the highest one can't be rooted yet or something like that. I just want to make sure that I don't shoot myself in the foot haha.
Thank you all for your help
Click to expand...
Click to collapse
Hey, I'm not sure about firmware not being able to be rooted but the best way to go about it (what I did anyway) is to unlock the phone via htcdev.com, flash a custom recovery (Latest TWRP which has also worked around the encryption stuff?) and then back up everything other than the data partition. That way, no matter what you do, you always have something to revert back to. The reason for not backing up data is due to the encryption. From my understanding, restoring an encrypted data partition would break things. Once you have the phone unlocked and recovery sorted, you are free to flash viper etc. and root the phone using SuperSU. I'm sure you are aware unlocked devices are quite easy to root so whatever you flash will most likely be on latest firmware, already rooted.
As for installing OTAs etc., you need unmodified system and recovery which is where the backups kick in. Simply back up your data on an SD card (pictures etc. not the actual partition) and restore the system-image and recovery. This should reset the phone although I'm not sure if it'll wipe anything and allow you to do OTA updates. Alternatively, get the latest firmware for your device from htcdev (again, not sure if they have firmware on there) and use that instead.
If any of the information above is incorrect or missing steps, someone feel free to correct me.
I've always had my devices rooted and running a custom rom or at least a custom kernel or something of the sort "But" ever since I got my pixel about a year ago I haven't felt the need to root at all, stock rom is just perfect and so battery life and I don't see a reason to.
However I was just thinking that now with locked bootloader if for any reason my phone gets bricked then I'm probably [email protected]*t out of luck because I won't be able to flash a factory image to bring the phone back to life.
Should I unlock my bootloader just in case the worse does happen or is there another workaround for such a situation?
Getting bricked is the direct result of flashing images.
nabbed said:
Getting bricked is the direct result of flashing images.
Click to expand...
Click to collapse
I could not disagree more. There are countless threads of individuals taking OTAs and running into boot loop. Additionally I have read through multiple threads where individuals were simply using their phone to play a game, text, phone call etc and the phone shuts off and goes into a loop.
The users with an unlocked bootloader were able to salvage the device. Users without a locked bootloader looked for a RMA.
To the OP- I personally will never own an Android device with a constantly locked bootloader. The safety net of being able to factory reset and flash stock images is something I've always cherished and do not wish to get rid of.
There are security risks to having an unlocked BL. If an Android savvy criminal were to steal your device they could do a lot of damage with obtaining personal information. For me, I'm much more worried about my phone going in to boot loop than I am some criminal being able to take my phone from me.
Sab3elbromba said:
Should I unlock my bootloader just in case the worse does happen or is there another workaround for such a situation?
Click to expand...
Click to collapse
if for any reason, something did get corrupted on your phone with a lockedbootloader and it tripped verified boot. you would be locked out, no course of action but to get an RMA... so if u plan on tinkering with your phone or just would like a failsafe, at least with an unlocked phone. you would be able to flash firmware, etc...
just remember, not to relock your bootloader; unless your phone is running stock firmware and is wiped.... otherwise you will trip verified boot and brick it...
nabbed said:
Getting bricked is the direct result of flashing images.
Click to expand...
Click to collapse
no, it's not. getting a bricked phone is pretty much always because the person did something ill advised or dumb... like relocking their bootloader running custom firmware...
so a diect result of user error, nothing to do with flashing images.