Related
Hi all.
I'm not a fan of the rom on my phone so I might end up rooting and going down the custom rom route eventually. For now, I wanted to know if its possible for me to change the stock rom on my handset without too much hassle? I got the One X second hand and it looks like the phones from somewhere in Asia so I've got a bunch of stock apps from out that way so I wanted to know if I could flash the phone with a UK or EU rom without breaking the phone?
.. and if so.. how?
Basically of comes down to this
Unlock the bootloader (this will reset the phone to stock)
Flash a custom recovery and make a NANDROID BACKUP RIGHT AWAY !
Push the superuser.zip from the recovery to the rom to gain root acces or flash a brand new custom rom
But befor you start you need to read up in here, all sorts of guides and also tools. Get to learn adb/fastboot commands. That's very important !
http://forum.xda-developers.com/showthread.php?t=1832891
Yeah I already know how to do all that, I've done a few different models but I generally wanted to know if I could just flash the current stock from with a stock from from the UK?
Im not too bothered for rooting and custom roms at the minute as some apps I use dont work with a rooted phone.
In that case....yes. pretty much all roms are based on the wwe software
Hi!
My Z1C is rooted, has dualrecovery and is running a stock 4.4.2 (14.3.a.0.757)
I also have a lot of customizations via XPosed.
What would be the easiest way to upgrade to a Lollipop version? Someone suggested I can just upgrade and use towelroot afterwards to regain root, but I could not find any verification of that.
Is it safer to flash a pre-rooted zip and if so can anyone point to a decent source?
Also, will XPosed Framework still be functional on Lollipop? I hear there are so many headachy changes to the security layout that I am not sure of that, but right now I'Äd feel safer with a version that has Stagefright fixed...
Let me know what you think!
Thanks
Walter_White said:
Hi!
My Z1C is rooted, has dualrecovery and is running a stock 4.4.2 (14.3.a.0.757)
I also have a lot of customizations via XPosed.
What would be the easiest way to upgrade to a Lollipop version? Someone suggested I can just upgrade and use towelroot afterwards to regain root, but I could not find any verification of that.
Is it safer to flash a pre-rooted zip and if so can anyone point to a decent source?
Also, will XPosed Framework still be functional on Lollipop? I hear there are so many headachy changes to the security layout that I am not sure of that, but right now I'Äd feel safer with a version that has Stagefright fixed...
Let me know what you think!
Thanks
Click to expand...
Click to collapse
AFAIK, there is currently no 'one click' root for 5.1. There is a thread about a Kingroot-to-Supersu method that I can verify works for 5.0.2. You can root 5.1, but either by fastboot, (requiring unlocked bl), or downgrade method, (which you're already on step 1 with KK). There seems to be varied reports about PRFs, but I'm sure you can find a good one by now. I think the main question is if you're hoping to save app data, Xposed settings, etc., to restore afterwards. If so, I would say it's very iffy. You could try Titanium or something, but I wouldn't be surprised if you get some glitches.
As far as Xposed, it works great on 5.0 or 5.1, and there's new developments coming steadily.
Search Z1c 'general', and 'android development' forums for downloads, etc.
Forgot to mention, BL is unlocked with dualrecovery.
Thanks for your advice so far. Root procedure for 5.1 with unlocked BL is already outlined in a thread here?
And yeah, I agree, trying to save app data / settings is bordering on impossible now, I fear TiBackup has outlived its usefulness when it comes to ROM migration. Spent half of today getting my Z1C apps to Z5C and still not nearly half done.
Damn gremlins.
Walter_White said:
Forgot to mention, BL is unlocked with dualrecovery.
Thanks for your advice so far. Root procedure for 5.1 with unlocked BL is already outlined in a thread here?
And yeah, I agree, trying to save app data / settings is bordering on impossible now, I fear TiBackup has outlived its usefulness when it comes to ROM migration. Spent half of today getting my Z1C apps to Z5C and still not nearly half done.
Damn gremlins.
Click to expand...
Click to collapse
To root with unlocked bl, flash stock ROM w/ Flashtool, then flash this with fastboot -http://forum.xda-developers.com/sony-xperia-z1-compact/general/ub-root-init-d-support-recovery-busybox-t3202799 - done. Then you can install Xposed, custom kernel, etc..
Thanks!
Will try this as soon as I managed to migrate my stuff fully to my new Z5C. Migration without TiBackup is a real PITA
Just making sure, when using your route "flash any stock and then follow up with the mentioned file" it means I can jump straigfht from 4.4.2 into the 5 era? Or Do I have to go to 5 for some compatibility reasons. I recall there was something like this sometime back when there was a major new version.
As far my planned procedure for tmw is:
TWRP backup
CWM backup
TiBackup
copying required stuff to the computer
then flash http://forum.xda-developers.com/son...al/stock-14-6-0-368-ce1-dualrecovery-t3216740 as this seems to be the most recent version including updates of the recoveries, pre-rooting already combined. This saves me the step from bone stock to pre-rooted stock as I would have to make in your suggestion.
Also, I want to as well try to use the DRM Feature Fix Mod (http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672), so I will flash the LP version of that one afterwards.
This should work, or am I missing anything significant? I can very well toss the data, the Z5C is now my main phone,, the Z1C has been given a 2nd life with a new backplate and battery I just put in so I'd hate to brick it.
Please confirm that I have a general idea of what I am doing lol... Using flashtool etc. is known to me but selecting the right ROMs remains a mystery unless you follow XDA daily...
Much appreciated
Walter_White said:
Just making sure, when using your route "flash any stock and then follow up with the mentioned file" it means I can jump straigfht from 4.4.2 into the 5 era? Or Do I have to go to 5 for some compatibility reasons. I recall there was something like this sometime back when there was a major new version.
As far my planned procedure for tmw is:
TWRP backup
CWM backup
TiBackup
copying required stuff to the computer
then flash http://forum.xda-developers.com/son...al/stock-14-6-0-368-ce1-dualrecovery-t3216740 as this seems to be the most recent version including updates of the recoveries, pre-rooting already combined. This saves me the step from bone stock to pre-rooted stock as I would have to make in your suggestion.
Also, I want to as well try to use the DRM Feature Fix Mod (http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672), so I will flash the LP version of that one afterwards.
This should work, or am I missing anything significant? I can very well toss the data, the Z5C is now my main phone,, the Z1C has been given a 2nd life with a new backplate and battery I just put in so I'd hate to brick it.
Please confirm that I have a general idea of what I am doing lol... Using flashtool etc. is known to me but selecting the right ROMs remains a mystery unless you follow XDA daily...
Much appreciated
Click to expand...
Click to collapse
Sorry, not sure if you were responding to me... As far as backing up and restoring data, I can't say for sure what's best, going from kk to lp. If you're going from stock to stock, probably built-in Google backup would do the trick. 3rd party stuff is chancy when switching versions in my experience, but Titanium might do OK. I don't think you can backup any kk data in recovery, then restore it on lp. Maybe someone else can tell you otherwise. As far as root in on lp, with unlocked bl, all you need is to flash stock ROM in flash mode with Flashtool, then flash the IMG I linked. - done.
I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)
Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Where are you getting the firmware you're trying to use to downgrade?
douger1957 said:
Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
Click to expand...
Click to collapse
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
douger1957 said:
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Click to expand...
Click to collapse
I actually tried a PC version of kingoroot. It also failed numerous times.
douger1957 said:
Where are you getting the firmware you're trying to use to downgrade?
Click to expand...
Click to collapse
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.
nertskull said:
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
I actually tried a PC version of kingoroot. It also failed numerous times.
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.
Click to expand...
Click to collapse
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.
douger1957 said:
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.
Click to expand...
Click to collapse
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?
nertskull said:
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?
Click to expand...
Click to collapse
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?
douger1957 said:
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?
Click to expand...
Click to collapse
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.
nertskull said:
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.
Click to expand...
Click to collapse
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.
douger1957 said:
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.
Click to expand...
Click to collapse
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks
nertskull said:
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks
Click to expand...
Click to collapse
That's a difficult question to answer and for me would boil down to whether I wanted features available in Marshmallow based ROMs or not.
Wifi calling is a nice to have feature for me but it's not really a dealbreaker. There's a bit more security baked into Marshmallow which is always nice to have.
The development atmosphere is more active over at the generic Note 4 forum. You can now get one of the super ROMs (Note/S7 combo ports) in either flavor. You'll want to stick with ROMs developed for the N910F or G models. They're international phones with fewer integration headaches for our N910V phones. To use those ROMs on our phone, you'll need a data fix most kindly provided by @louforgiveno.
My suggestion in picking a ROM is to zero in on one that seems to have the features you'd like to have and read the entire thread. Look for threads in either the General or Q&A subforums that are dedicated to answering questions about the ROM and read those, too. Some of those threads are upwards to 1,000 posts or more, you say? You'll discover what problems people have had with the ROM and the solutions or workarounds needed to overcome them. You'll also discover just how lazy many posters are either not reading thoroughly or failing to use the search function.
Final suggestions? Do a full nandroid backup before you flash anything. In TWRP, check off all of the boxes. In many of today's ROMs, you'll have a 8 to 10 gig backup file. If you can't keep that on the phone, move it to your PC. There will be far fewer tears if something goes wrong. When you flash a ROM, do a full wipe. I check off Dalvik/ART cache, system, data, and cache. For your first ROM, I would move anything that you have on internal storage off the phone and wipe internal storage too. If you have any Kingroot/Kingoroot cooties, that should clear them off the phone. When you're done flashing a ROM there's an option to wipe the cache. Do it. If you've installed a bunch or apps or deleted them, wipe the Dalvik and cache. It'll help bring the Android stars into alignment as that forces the system to optimize.
Good luck and happy flashing.
You need to go to 5.1.1 use kingOroot and then do it again. Cid will remain that's what I did. Its different for everyone these root methods are pulled from the internet and it will usually take a few time and it will try dufrrent methods of rooting
nertskull said:
I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)
Click to expand...
Click to collapse
For me, I had to run Kingoroot from my laptop, and Kingroot never worked.
I've watched the video guides about Sunshine S-off but I'm still a bit confused. I currently have a non-rooted, S-ON HTC 10 with a locked bootloader (in other words it's factory new). I want to upgrade to Nougat when it becomes available in the EU, but since I want to have an "S-off LOCKED" + rooted phone I was told that doing the Sunshine method while still being on MM is the best thing to do. To do this, as far as I'm concerned I have to follow these steps:
1.) Download, run and purchase Sunshine.
2.) Select the S-off LOCKED option and start the process.
3.) This is where things become confusing. According to the videos I've watched, now my phone should be encrypted. Since I don't have TWRP, should I use the original recovery program's factory reset option?
4.) Flash TWRP, just like you had your bootloader unlocked. (If I flash TWRP on MM, will I still be able to use it on Nougat?)
5.) Wait for the Nougat OTA and install it. (The update should come automatically, right?)
6.) Root it.
After rooting, I would still get the OTA updates, right? (since I have my bootloader locked)
I would be grateful if someone could verify these steps. Thanks in advance!
bence.szij said:
I've watched the video guides about Sunshine S-off but I'm still a bit confused. I currently have a non-rooted, S-ON HTC 10 with a locked bootloader (in other words it's factory new). I want to upgrade to Nougat when it becomes available in the EU, but since I want to have an "S-off LOCKED" + rooted phone I was told that doing the Sunshine method while still being on MM is the best thing to do. To do this, as far as I'm concerned I have to follow these steps:
1.) Download, run and purchase Sunshine.
2.) Select the S-off LOCKED option and start the process.
3.) This is where things become confusing. According to the videos I've watched, now my phone should be encrypted. Since I don't have TWRP, should I use the original recovery program's factory reset option?
4.) Flash TWRP, just like you had your bootloader unlocked. (If I flash TWRP on MM, will I still be able to use it on Nougat?)
5.) Wait for the Nougat OTA and install it. (The update should come automatically, right?)
6.) Root it.
After rooting, I would still get the OTA updates, right? (since I have my bootloader locked)
I would be grateful if someone could verify these steps. Thanks in advance!
Click to expand...
Click to collapse
There is a lot of questions unanswered.
1. Why do you want S-OFF? Most people don't need it.
2. Do you want Nougat 2.28 full firmware, or only Nougat Android?
3. You need stock recovery to flash an OTA.
4. Current TWRP will not work on Nougat 2.28 firmware, and I think it won't work until HTC release official Kernel source.
5. If you want only the Android Nougat OS, while staying on MM 1.95 Firmware in order to be able to flash TWRP...then why not just flash Viper, ICE or LeeDroid custom ROM?
6. If you do flash custom N ROM, I believe that there are bugs due to using MM firmware. Something to do with Camera and Sound. It's all very complicated.
Summary: Describe what you want and we'll be able to tell you exactly what you need to do.
Kyuubi10 said:
There is a lot of questions unanswered.
1. Why do you want S-OFF? Most people don't need it.
2. Do you want Nougat 2.28 full firmware, or only Nougat Android?
3. You need stock recovery to flash an OTA.
4. Current TWRP will not work on Nougat 2.28 firmware, and I think it won't work until HTC release official Kernel source.
5. If you want only the Android Nougat OS, while staying on MM 1.95 Firmware in order to be able to flash TWRP...then why not just flash Viper, ICE or LeeDroid custom ROM?
6. If you do flash custom N ROM, I believe that there are bugs due to using MM firmware. Something to do with Camera and Sound. It's all very complicated.
Summary: Describe what you want and we'll be able to tell you exactly what you need to do.
Click to expand...
Click to collapse
Thanks for the anwser!
I'll try to anwser your questions (and ask new ones) as precisely as I can.
1.) I want S-OFF because that way the bootlocker can stay locked, and as I've heard you can go S-ON again with Sunshine. That way I don't really have to worry about the "relocked" state and warranty loss. Otherwise the HTCDev method would be perfectly fine for me.
2.) I didn't know that you can use the Nougat OS without upgrading your firmware. Could you please explain the differences between "Nougat 2.28 full firmware" and "Nougat Android"? I tried to do a research but I've failed
3.) So basically if I have TWRP the only way to install system updates is to flash them manually? Also if I stay with stock recovery while being S-off LOCKED will I get the OTAs? And what if I unlock the bootloader?
4.) When do you think HTC will release official Kernel source? Weeks? Months?
5.)- 6.) When I bought my phone in July, I decided not to root it immediately. I've planned to root after installing Android N, and since the EU release is near I've started researching on the process. The only reason I want to S-off now, while being on MM, is that Sunshine might not work after installing the Nougat OTA (I need Sunshine to protect my warranty). I'm not in a hurry, my goal is to have a phone with Nougat, TWRP, root and xposed (maybe an N version of Viper). I don't want to have a buggy phone. If running Nougat/Viper on an older firmware would cause bugs, I'd rather wait with the whole process until the OTA arrives, then install it and unlock my bootloader with HTCDev instead of achieving the "S-off LOCKED" state with Sunshine, even if this means warranty loss.
I hope I could explain things better this time.
bence.szij said:
Thanks for the anwser!
I'll try to anwser your questions (and ask new ones) as precisely as I can.
1.) I want S-OFF because that way the bootlocker can stay locked, and as I've heard you can go S-ON again with Sunshine. That way I don't really have to worry about the "relocked" state and warranty loss. Otherwise the HTCDev method would be perfectly fine for me.
2.) I didn't know that you can use the Nougat OS without upgrading your firmware. Could you please explain the differences between "Nougat 2.28 full firmware" and "Nougat Android"? I tried to do a research but I've failed
3.) So basically if I have TWRP the only way to install system updates is to flash them manually? Also if I stay with stock recovery while being S-off LOCKED will I get the OTAs? And what if I unlock the bootloader?
4.) When do you think HTC will release official Kernel source? Weeks? Months?
5.)- 6.) When I bought my phone in July, I decided not to root it immediately. I've planned to root after installing Android N, and since the EU release is near I've started researching on the process. The only reason I want to S-off now, while being on MM, is that Sunshine might not work after installing the Nougat OTA (I need Sunshine to protect my warranty). I'm not in a hurry, my goal is to have a phone with Nougat, TWRP, root and xposed (maybe an N version of Viper). I don't want to have a buggy phone. If running Nougat/Viper on an older firmware would cause bugs, I'd rather wait with the whole process until the OTA arrives, then install it and unlock my bootloader with HTCDev instead of achieving the "S-off LOCKED" state with Sunshine, even if this means warranty loss.
I hope I could explain things better this time.
Click to expand...
Click to collapse
If you're thankful press the thanks button, it would mean much more than saying you're thankful. It is there for a reason.
By seeing your answers my best advise will be, you don't need to S-OFF.
HTC explicitly states in their full T&C that your warranty is not completely void when you unlock bootload.
Your warranty just becomes conditional, which means that if you brick your device your warranty is void.
Or if any damage to the phone comes as a direct effect of you unlocking your bootloader, then warranty is void.
If the damage/fault is unrelated to you unlocking your bootloader then your warranty should still be AND will be valid.
Has been this way since I first joined the HTC bandwagon with the OneX.
Now regarding waiting for N before rooting. I also advise against this.
When the N sources are released you will be jumping into mostly BETA releases.
These tend to have a few bugs early on, I'd advise to root now while on M which is very stable and full of awesome features.
Wait around until N has some stable ROMs and Kernels.
Answering your other questions:
2) The firmware on your phone is your: "Bootloader, Radio, OpenDSP etc..." These are the deepest software on your phone, and for security and to avoid bricks should stay stock, unless you really know what you are doing. Firmware is not made by Google, but instead by the OEM. This is unique to the hardware on your phone. Android is made by google, and it can be divided into Kernel and OS/ROM.
3) S-OFF I don't know, but if you are S-ON with stock system and stock recovery you should always be able to install OTA even if you have unlocked bootloader.
4) I believe January.
Enjoy root and xposed on MM...get familiar with what is possible and learn as much as possible on a stable configuration.
Once you've learned a bit more about what root is capable of then move on to N when N is stable.
I suggest to learn how to use RUU.exe/RUU.zips before moving to N though.
Kyuubi10 said:
If you're thankful press the thanks button, it would mean much more than saying you're thankful. It is there for a reason.
By seeing your answers my best advise will be, you don't need to S-OFF.
HTC explicitly states in their full T&C that your warranty is not completely void when you unlock bootload.
Your warranty just becomes conditional, which means that if you brick your device your warranty is void.
Or if any damage to the phone comes as a direct effect of you unlocking your bootloader, then warranty is void.
If the damage/fault is unrelated to you unlocking your bootloader then your warranty should still be AND will be valid.
Has been this way since I first joined the HTC bandwagon with the OneX.
Now regarding waiting for N before rooting. I also advise against this.
When the N sources are released you will be jumping into mostly BETA releases.
These tend to have a few bugs early on, I'd advise to root now while on M which is very stable and full of awesome features.
Wait around until N has some stable ROMs and Kernels.
Answering your other questions:
2) The firmware on your phone is your: "Bootloader, Radio, OpenDSP etc..." These are the deepest software on your phone, and for security and to avoid bricks should stay stock, unless you really know what you are doing. Firmware is not made by Google, but instead by the OEM. This is unique to the hardware on your phone. Android is made by google, and it can be divided into Kernel and OS/ROM.
3) S-OFF I don't know, but if you are S-ON with stock system and stock recovery you should always be able to install OTA even if you have unlocked bootloader.
4) I believe January.
Enjoy root and xposed on MM...get familiar with what is possible and learn as much as possible on a stable configuration.
Once you've learned a bit more about what root is capable of then move on to N when N is stable.
I suggest to learn how to use RUU.exe/RUU.zips before moving to N though.
Click to expand...
Click to collapse
Thanks again!
I guess I'll do as you said and do it now. I have only one more question left then: let's say I unlock my bootloader with HTCDev, install TWRP, then root my phone and flash xposed. A few months later Nougat becomes stable and I decide to upgrade. In that case, I would be still using my current firmware, so N based roms would contain bugs, which I don't want. How can I upgrade my firmware in a situation like this?
bence.szij said:
Thanks again!
I guess I'll do as you said and do it now. I have only one more question left then: let's say I unlock my bootloader with HTCDev, install TWRP, then root my phone and flash xposed. A few months later Nougat becomes stable and I decide to upgrade. In that case, I would be still using my current firmware, so N based roms would contain bugs, which I don't want. How can I upgrade my firmware in a situation like this?
Click to expand...
Click to collapse
You're welcome, it's a pleasure to help.
An easy way of getting root is by flashing a custom ROM which already comes with root
I believe that quickly by Feb you should already have a stable N release.
Now to upgrade firmware... That's what the RUU part of my previous answer is for.
HTC are really rooting friendly, so much so they gave us a way to easily and quickly going back to stock. That is called an RUU.
You can search that more in detail to learn about it.
But to update firmware you have two ways, the fast way through RUU, or the slow way by flashing stock ROM via TWRP, then fastboot flash stock recovery and then flash the OTAs.
By doing RUU or via OTA method will update your firmware.
Keep in mind if you plan to use Android Pay or Pokemon Go, this may effect some your decision if you want to go s-off locked status or unlocked bootloader. Everything @Kyuubi10 said is good info, that's just something I would factor into consideration. There may be ways around having an unlocked bootloader and using Android Pay, I'm not the expert there because I don't want google having more of my financial information than they already have. But if you do use it or plan too, that might be something you need to take into consideration before you go unlocked and s-on.
I'm not talking you out of unlocking or anything, I just want you to know in case it's something you need to further consider.
CharliesTheMan said:
Keep in mind if you plan to use Android Pay or Pokemon Go, this may effect some your decision if you want to go s-off locked status or unlocked bootloader. Everything @Kyuubi10 said is good info, that's just something I would factor into consideration. There may be ways around having an unlocked bootloader and using Android Pay, I'm not the expert there because I don't want google having more of my financial information than they already have. But if you do use it or plan too, that might be something you need to take into consideration before you go unlocked and s-on.
I'm not talking you out of unlocking or anything, I just want you to know in case it's something you need to further consider.
Click to expand...
Click to collapse
Actually... I believe you can go unlocked and use android pay.
As long as you don't have root.
You can even have customROM and custom Kernel, but as long as you have no root, and no xposed you should be able to use Android Pay and Pokemon Go.
E.g. MultiROM with 1 rom non-rooted should be possible.
But I may be wrong, so don't quote me.
bence.szij said:
Thanks again!
I guess I'll do as you said and do it now. I have only one more question left then: let's say I unlock my bootloader with HTCDev, install TWRP, then root my phone and flash xposed. A few months later Nougat becomes stable and I decide to upgrade. In that case, I would be still using my current firmware, so N based roms would contain bugs, which I don't want. How can I upgrade my firmware in a situation like this?
Click to expand...
Click to collapse
You're lucky!
HTC released N sources yesterday!!
Will probably get a stable release by mid January.
Kyuubi10 said:
You're lucky!
HTC released N sources yesterday!!
Will probably get a stable release by mid January.
Click to expand...
Click to collapse
Thanks for the info! I've unlocked the bootloader yesterday and I'm planning to flash TWRP and SuperSU tonight?
bence.szij said:
Thanks for the info! I've unlocked the bootloader yesterday and I'm planning to flash TWRP and SuperSU tonight?
Click to expand...
Click to collapse
Don't worry about flashing SuperSU, usually it'll be included in the Custom ROM...if you want to use Custom ROM.
Or even TWRP gives you the option to enable SuperSU, if you wish to stay with stock ROM.
Previously posted in incorrect forum.
Hi All,
Just got my hands on a couple devices (some kitkat, some lollipop). They are all currently not rooted.
I see there is a lot of support for this device, so my question is, what should I do to these devices?
1) Downgrade them all, root them, and update them to lineage os? Is this relatively easy?
2) Can I upgrade them all to lollipop somehow, and then root?
3) What other options are out there, and what do you guys thinks is the best way to take this?
Cheers
xxtavexx said:
1) Downgrade them all, root them, and update them to lineage os? Is this relatively easy?
Click to expand...
Click to collapse
Downgrading from lollipop to kitkat is possible, but it sounds like a long and involved process. For returning to stock kitkat all we have a test kdz that introduces a few issues you have to fix. For rooting kitkat PurpleDrake worked. Once you have root, you can flash TWRP then use it to flash any V410 rom you want.
xxtavexx said:
2) Can I upgrade them all to lollipop somehow, and then root?
Click to expand...
Click to collapse
No one has posted any V410 lollipop firmware to update manually. You'll have to take an OTA update. Kingroot has been reported to work on stock lollipop. Attempts to replace Kingroot with SuperSU once root access has been gained have been reported to result in bricked tablets.
Also, you'll be stuck on LG stock with the lollipop bootloader, it can't be unlocked. The kitkat bootloader can't be unlocked either, but it was easy to exploit. TWRP and all the custom roms rely on being on the kitkat bootloader.
xxtavexx said:
3) What other options are out there, and what do you guys thinks is the best way to take this?
Click to expand...
Click to collapse
I never liked the stock LG rom, but that's just a matter of personal preference. I've been on custom roms since they got stable. Currently I'm running an Android 5.1.1 build of Tesla. This tablet just worked best for me on lollipop custom roms. Marshmallow and Nougat get really unresponsive over time, though to be honest I think that has more to do with garbage apps my kid installs than the system itself. It is always nice and responsive after a clean flash.
jason2678 said:
Downgrading from lollipop to kitkat is possible, but it sounds like a long and involved process. For returning to stock kitkat all we have a test kdz that introduces a few issues you have to fix. For rooting kitkat PurpleDrake worked. Once you have root, you can flash TWRP then use it to flash any V410 rom you want.
No one has posted any V410 lollipop firmware to update manually. You'll have to take an OTA update. Kingroot has been reported to work on stock lollipop. Attempts to replace Kingroot with SuperSU once root access has been gained have been reported to result in bricked tablets.
Also, you'll be stuck on LG stock with the lollipop bootloader, it can't be unlocked. The kitkat bootloader can't be unlocked either, but it was easy to exploit. TWRP and all the custom roms rely on being on the kitkat bootloader.
I never liked the stock LG rom, but that's just a matter of personal preference. I've been on custom roms since they got stable. Currently I'm running an Android 5.1.1 build of Tesla. This tablet just worked best for me on lollipop custom roms. Marshmallow and Nougat get really unresponsive over time, though to be honest I think that has more to do with garbage apps my kid installs than the system itself. It is always nice and responsive after a clean flash.
Click to expand...
Click to collapse
Thank you for this extremely informative reply jason2678 ! Thanks for taking time out of your day to provide that detailed reply.
I would love to hear other peoples experiences on which rom to run as well.