Related
HI,
I've using my Galaxy Nexus (GSM) for a long time, but i want to get Root access, i've been reading a lot and it seems if i use Galaxy Nexus Toolkit it will delete all my data, there's any way to root it without losing any data?
Thanks a lot! :good: :fingers-crossed:
milerx said:
HI,
I've using my Galaxy Nexus (GSM) for a long time, but i want to get Root access, i've been reading a lot and it seems if i use Galaxy Nexus Toolkit it will delete all my data, there's any way to root it without losing any data?
Thanks a lot! :good: :fingers-crossed:
Click to expand...
Click to collapse
no.
you have to unlock your bootloader (no matter which method you use, also, dont use a toolkit, use the sticky at the top of the forum) which wipes your data. period.
Zepius said:
you have to unlock your bootloader (no matter which method you use, also, dont use a toolkit, use the sticky at the top of the forum) which wipes your data. period.
Click to expand...
Click to collapse
I did a root of my Galaxy Nexus, when I flashed the new 4.1. It did work fine. When the phone did the small update to 4.1.2, can it be true that it rolled back the root? My phone don't seem to be rooted anymore.
Isn't it possible to get root permissions again, without loosing data?
IsonNick said:
I did a root of my Galaxy Nexus, when I flashed the new 4.1. It did work fine. When the phone did the small update to 4.1.2, can it be true that it rolled back the root? My phone don't seem to be rooted anymore.
Isn't it possible to get root permissions again, without loosing data?
Click to expand...
Click to collapse
if your bootloader is unlocked, reflash the supersu.zip
otherwise, you have to unlock the bootloader and it will wipe your device.
Zepius said:
if your bootloader is unlocked, reflash the supersu.zip
Click to expand...
Click to collapse
It should be. Anyway to see that?
(sorry for noob questions)
IsonNick said:
It should be. Anyway to see that?
(sorry for noob questions)
Click to expand...
Click to collapse
if you enter fastboot, it will says "lock status: unlocked"
or you can see if when you first start up your phone if there's a little lock that is unlocked.
Zepius said:
or you can see if when you first start up your phone if there's a little lock that is unlocked.
Click to expand...
Click to collapse
Hep hep! The lock is unlocked. Perfect.
When I receive the 4.2 update (my phone is yakju), I will root again. Thank you for your help, I appreciate it a lot.
Similar thing happened to me. I was messing around with different ROM's for some time but in the end went back to the stock ROM. My phone now shows unlocked and using the stock recovery (as described here http://forums.androidcentral.com/google-samsung-galaxy-nexus/243004-recovery-mode.html).
The stock recovery offers 4 options: reboot, apply update from ADB or USB, wipe.
How do I "reflash the supersu.zip" from here? I want to avoid wiping as everything is set up as I like it now, and because it isn't rooted I can't back it up, catch 22 thing
madsere said:
Similar thing happened to me. I was messing around with different ROM's for some time but in the end went back to the stock ROM. My phone now shows unlocked and using the stock recovery (as described here http://forums.androidcentral.com/google-samsung-galaxy-nexus/243004-recovery-mode.html).
The stock recovery offers 4 options: reboot, apply update from ADB or USB, wipe.
How do I "reflash the supersu.zip" from here? I want to avoid wiping as everything is set up as I like it now, and because it isn't rooted I can't back it up, catch 22 thing
Click to expand...
Click to collapse
Why did you bump a 4 months old thread?
Obviously, you need a custom recovery to flash a non-Google zip...
Sent from my Nexus
bk201doesntexist said:
Why did you bump a 4 months old thread?
Obviously, you need a custom recovery to flash a non-Google zip...
Sent from my Nexus
Click to expand...
Click to collapse
I'm sorry, I didn't know there was a rule against that. I searched Google for the problem and this thread came up closest.
Well sorry if I am not a genius like you who know everything already. I thought that forums like this was for asking questions.
It would be nice if instead of just being mean and nasty you'd offer some constructive suggestions, such as would installing a custom recovery wipe the phone? The distinction between the boot loader and the custom recovery isn't clear to me.
madsere said:
I'm sorry, I didn't know there was a rule against that. I searched Google for the problem and this thread came up closest.
Well sorry if I am not a genius like you who know everything already. I thought that forums like this was for asking questions.
It would be nice if instead of just being mean and nasty you'd offer some constructive suggestions, such as would installing a custom recovery wipe the phone? The distinction between the boot loader and the custom recovery isn't clear to me.
Click to expand...
Click to collapse
Yeah?
Then it would be nice if you read the stickies.
Sent from my Nexus
madsere said:
I'm sorry, I didn't know there was a rule against that. I searched Google for the problem and this thread came up closest.
Well sorry if I am not a genius like you who know everything already. I thought that forums like this was for asking questions.
It would be nice if instead of just being mean and nasty you'd offer some constructive suggestions, such as would installing a custom recovery wipe the phone? The distinction between the boot loader and the custom recovery isn't clear to me.
Click to expand...
Click to collapse
Sarcastic, aren't we? Look, XDA is first and foremost a developer site for developers to develop. Answering and asking questions about that development is only incidental. Members are expected to have read the rules of XDA and to follow them. That includes not bumping old threads, but it also includes an expectation that you will read the information readily available to you. Seeing the same common questions get asked daily, when there are good guides made specifically for this purpose, gets very old very fast. The constructive suggestion is to search and read. Guides abound both in the stickies and elsewhere, and the fact that you haven't found answers to your fairly common questions tells me that you either haven't made an effort to look, or you just don't understand and therefore probably shouldn't be messing with your phone.
I was able to root my gnex without wiping the data!
I dont know how it happened, but it happened, I was surprised too because I was really frustrated couldn't root it even after 10-15 tries ( I am a big time noob) and suddenly I unlocked the boot loader and rooted the phone without any loss of data, actually I was rooting because I had the VM100U something memory issue and my phone was terribly slow! I was surprised becasue i was expecting to copy all my files and crap one by one but now I have no issues
Yea sorry, I know there are tons of threads on rooting this stupid thing but I've been trying out so many different ways today and failed that I'm sick of and tired of this stupid piece of crap.
This is my brother's phone, and it's run out of internal memory (seriously 300 mb?), anyway he has like 10 apps installed on the internal memory, these plus all the updates have filled it up. So now I'm trying to root it so I can swap the SD cards (already got him a 32 gig microSD for that).
And oh boy am I sick of this thing, so far I've tried multiple options and none work, and some are too complicated with poor instructions for me to figure out.
Rooting my Galaxy W was so easy and this thing here just makes me hate everything.
Stuff I've tried:
Sony Xperia Flasher
ERoot
Flash tool
bootloader
I'm at the end of my wits here, completely frustrated and yea, if this where my phone I would have already smashed it with a hammer.
I really don't have time for this sh*t since I have to study for a big test, so I would appreciate something super simple and fast, like with the Galaxy W.
Again, sorry for sounding like a **** and creating yet another thread, but I'm desperate.
Thanks for any help.
dial *#*#7378423#*#* on your phone then go to service info then to configuration & at the bottom what does it say regarding your bootloader ?
Bootloader unlock allowed: Yes
Dead Metal said:
Bootloader unlock allowed: Yes
Click to expand...
Click to collapse
this is good,what version of android do you have ?
It says Android Version 2.3.4
But build number 4.02.A0.69
Dead Metal said:
It says Android Version 2.3.4
But build number 4.02.A0.69
Click to expand...
Click to collapse
ok i used this app to root my phone (google it or search this forum for it,easy to find):
DooMLoRD_v4_ROOT-zergRush-busybox-su
& i used this video to unlock bootloader:
http://www.youtube.com/watch?v=-crbhMFSuaQ
Thanks , I'll try that tomorrow, right now I'm just too tiered.
Dead Metal said:
Thanks , I'll try that tomorrow, right now I'm just too tiered.
Click to expand...
Click to collapse
if you need help send me PM & i will reply back in this thread. take care
If you want you can unlock the bootloader (loosing your warranty, of course), and then install a newer version of android up to 4.2.2, which is much more smoother than 2.3.4 and has much more features...
Madness, if you can't figure it out you're either not reading enough or just being lazy. There's about 4 or 5 links in my guide with how to root, add to that the amount of other threads there is, starting a new one means your lazy, because you've read nothing whilst signing up and just want to be spoon fed. Luck for you, there's some willing to do it.
Sent from Myushi
Rooting Tools
you can root using doomlord root script.
I have rooted several times after flashing few roms and the script works great.
Hope this helps..
http://forum.xda-developers.com/showthread.php?t=1321582
XperienceD said:
Madness, if you can't figure it out you're either not reading enough or just being lazy. There's about 4 or 5 links in my guide with how to root, add to that the amount of other threads there is, starting a new one means your lazy, because you've read nothing whilst signing up and just want to be spoon fed. Luck for you, there's some willing to do it.
Sent from Myushi
Click to expand...
Click to collapse
Had you taken a look at my join date and post count you may have noticed how I did not sign up to be spoon fed to root this device. And had you read my post you may have noticed how I stated that I've already rooted the Galaxy W, which is my phone, which was also real easy and straight forward.
I signed up to be able to hit the thanks button for Sir Arco's CM10 ROM, and give feedback should I notice bugs or other problems with it.
All I wanted was to root it without flashing a new ROM, since all my brother wants is more space on his phone, I don't think he'll want to check the forums constantly to check if there's a new version of a ROM out so he can flash it, so unlocking the bootloader and flashing a new ROM would be pretty pointless.
you can try to use the doomlord process, but you will always install a new rom, in that case will upgrade de phone to 4.0.3 and then you will be able to root the phone with de .bat file inside :good:
Dead Metal said:
Had you taken a look at my join date and post count you may have noticed how I did not sign up to be spoon fed to root this device.
Click to expand...
Click to collapse
But you still clearly hadn't read anything whilst signing up, otherwise you wouldn't have started a new thread on something as common as "how do I root". I assume you will have managed it by now?
XperienceD said:
But you still clearly hadn't read anything whilst signing up, otherwise you wouldn't have started a new thread on something as common as "how do I root". I assume you will have managed it by now?
Click to expand...
Click to collapse
I did, which is why I apologized for posting another thread like it, there where also no I do I root this in this forum, since apparently I'm the only one who had trouble with the options that are posted in the guide threads.
And no, the doom script did not work, it did say it was successful but the phone remained unrooted. So after a couple more tries (and rectifying the "drivers out of date" error message) I unlocked the bootloader, tried again a couple of times still to no effect. So I want ahead and flashed a new ROM and Kernel. At first my brother wasn't too happy about that but he's starting to like the new ROM.
Man, it was easier flashing android onto the bloody HP Touchpad than this phone.
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.
Ok, I start this off with the fact that this is my first phone with the whole slot A&B thing. I've done a ton of reading but it's still very confusing to me. I'm very confused on what exactly to do when it comes to updates. I'm stock rooted with TWRP installed on slot A. I'm also on the December build. I would like to update but I don't know what the easiest way to go about it is to be honest. I feel like an idiot but I guess that's because I'm really old school when it comes to this stuff. My rooting/roming goes back to the Samsung Captivate and countless other phones up until it got to be too much of a hassle to get a phone from a carrier that could be messed with. Now that I have rambled on, I thought it would be different getting a Pixel but this whole slot thing has me all confused. I basically want to stay stock rooted for now and possibly try a kernel down the line but I'm very happy with stock for now. Any advice would be greatly appreciated.
Thanks
pside15 said:
Ok, I start this off with the fact that this is my first phone with the whole slot A&B thing. I've done a ton of reading but it's still very confusing to me. I'm very confused on what exactly to do when it comes to updates. I'm stock rooted with TWRP installed on slot A. I'm also on the December build. I would like to update but I don't know what the easiest way to go about it is to be honest. I feel like an idiot but I guess that's because I'm really old school when it comes to this stuff. My rooting/roming goes back to the Samsung Captivate and countless other phones up until it got to be too much of a hassle to get a phone from a carrier that could be messed with. Now that I have rambled on, I thought it would be different getting a Pixel but this whole slot thing has me all confused. I basically want to stay stock rooted for now and possibly try a kernel down the line but I'm very happy with stock for now. Any advice would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
@Homeboy76 will get you squared away :good:
https://forum.xda-developers.com/pi...-android-9-0-pie-unlock-t3857195/post77944292
Badger50 said:
@Homeboy76 will get you squared away :good:
https://forum.xda-developers.com/pi...-android-9-0-pie-unlock-t3857195/post77944292
Click to expand...
Click to collapse
Thanks for the reply. I've read throughout that thread numerous times and I still can't determine the easiest way to update my phone and the necessary steps to take to get there. I just want to be stock rooted like I am now but don't know what steps to take to get there. Like do I need to unroot first, relock bootloader? I'm sure all those answers are in that thread but I'm probably just too dense to see them. I haven't really had a solid rooted phone in like 3 years so I'm used to things being done way different. Some times I miss my old HTC Inspire/Desire HD. There was so much development for that phone and it was all very straightforward.
pside15 said:
Thanks for the reply. I've read throughout that thread numerous times and I still can't determine the easiest way to update my phone and the necessary steps to take to get there. I just want to be stock rooted like I am now but don't know what steps to take to get there. Like do I need to unroot first, relock bootloader? I'm sure all those answers are in that thread but I'm probably just too dense to see them. I haven't really had a solid rooted phone in like 3 years so I'm used to things being done way different. Some times I miss my old HTC Inspire/Desire HD. There was so much development for that phone and it was all very straightforward.
Click to expand...
Click to collapse
This guide is how I update the monthly security patches. It is predicated on the notion that you have the latest platform-tools (28.0.1) and that your computer and phone are communicating well. It doesn't not require you to switch slots, and it will not wipe your data, and, you do not have to unroot before you begin. Happy flashing, and good luck
And never ever ever relock the bootloader! :crying:
Badger50 said:
This guide is how I update the monthly security patches. It is predicated on the notion that you have the latest platform-tools (28.0.1) and that your computer and phone are communicating well. It doesn't not require you to switch slots, and it will not wipe your data, and, you do not have to unroot before you begin. Happy flashing, and good luck
And never ever ever relock the bootloader! :crying:
Click to expand...
Click to collapse
Awesome, thank you very much for that. Yeah, I figured that about the bootloader. Does it matter if I have TWRP installed? That's the one main confusing thing to me. How you can have TWRP installed or not installed. I'm used to absolutely having to have TWRP or some other kind of custom recovery installed. But like I said it's been quite a while since I was really able to root/ROM a phone. I was basically forced to move to AT&T and opted for the Active line of Galaxy phones since I have little kids plus even the phones that were rootable and such seemed like more of a hassle than it was worth. The last phone I had that had some good development was probably the LG G3 on T-MOBILE. For some reason the T-MOBILE version had an unlocked bootloader or could be unlocked, don't remember exactly. But then a coworker got a Pixel 2XL and I got the itch again, not knowing how much had really changed though. Ok, I think I've rambled on enough now. Thanks again for the help.
pside15 said:
Awesome, thank you very much for that. Yeah, I figured that about the bootloader. Does it matter if I have TWRP installed? That's the one main confusing thing to me. How you can have TWRP installed or not installed. I'm used to absolutely having to have TWRP or some other kind of custom recovery installed. But like I said it's been quite a while since I was really able to root/ROM a phone. I was basically forced to move to AT&T and opted for the Active line of Galaxy phones since I have little kids plus even the phones that were rootable and such seemed like more of a hassle than it was worth. The last phone I had that had some good development was probably the LG G3 on T-MOBILE. For some reason the T-MOBILE version had an unlocked bootloader or could be unlocked, don't remember exactly. But then a coworker got a Pixel 2XL and I got the itch again, not knowing how much had really changed though. Ok, I think I've rambled on enough now. Thanks again for the help.
Click to expand...
Click to collapse
Doesn't matter if you have twrp installed or not. When you fastboot the update, it'll wipe it out anyway :good:
I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.
Download latest factory image. Extract the boot.img from it and save to your phone. Open magisk manager and patch that boot.img. Save /download/magisk_patched.img to your computer. Disable or remove any magisk modules that you might have running. In bootloader run the flash-all.bat, after editing to remove -w, and boot into system. Reboot to bootloader and run "fastboot flash boot --slot all magisk_patched.img" and you should be good to go. Make sure to back everything up before hand just in case something does wrong. I use a mix of titanium backup, sms backup/restore, export contacts, and manually saving files. There are other ways, but this is what I am comfortable with.
pside15 said:
I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.
Click to expand...
Click to collapse
Here ya go... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Google offers their own flashing update tool. You can find it here, https://pixelrepair.withgoogle.com/carrier_selection.
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You will need to wipe data on the upgrade to 10.
You will need to root again after the update. Bootloader will remain unlocked.
Once you have rooted, there is a method to take an OTA, and stay rooted. A description of the procedure is in the forums somewhere.
Again, I would recommend to follow the guide posted by Homeboy76. It will comprehensibly explain all the steps you need to achieve root,update etc. With links to downloads.
Gone are the days of flashing with just your phone. My first rooting experience was with an HTC Amaze. Then an S4 Samsung.
Good luck..
Edit: I stand corrected on data wipe when going to 10. I perhaps was overly cautious, and followed other recommendations.
pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You do not need to wipe data to update to 10. It is perfectly safe, we all did it. And so did all the people with locked bootloaders. You only have to wipe going down. Up is fine.
---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------
And here is the link to take an ota without losing root.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation).
Anyone tried Google's flashing update tool?
Homeboy76 said:
Anyone tried this?
Click to expand...
Click to collapse
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection
sliding_billy said:
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
It's working now
Homeboy76 said:
The link is in spotmark's quote: How can it be my link?
When I click it it works.
Click to expand...
Click to collapse
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.
sliding_billy said:
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.
Click to expand...
Click to collapse
It's working now
Homeboy76 said:
Read the edited post above yours.
Click to expand...
Click to collapse
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.
sliding_billy said:
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.
Click to expand...
Click to collapse
@sliding_billy
It's working now
Homeboy76 said:
@sliding_billy
It's working now
Click to expand...
Click to collapse
Winner, winner. Even better when you can't see the link.