i got a note 4 and i know i cant downgrade from lollipop to kitkat without bricking it, but what if i were to root it and do a custom recovery, can i load a kitkat custom rom onto it?
eric303 said:
i got a note 4 and i know i cant downgrade from lollipop to kitkat without bricking it, but what if i were to root it and do a custom recovery, can i load a kitkat custom rom onto it?
Click to expand...
Click to collapse
No, the partitions are completely different. KK is gone for good after your on lolly.
Kit-Kat+Lollipop
http://http://forum.xda-developers.com/note-4/orig-development/tw-kernel-emotroid-team-t2990557
eric303 said:
i got a note 4 and i know i cant downgrade from lollipop to kitkat without bricking it, but what if i were to root it and do a custom recovery, can i load a kitkat custom rom onto it?
Click to expand...
Click to collapse
*delete
hmm... since i got 2 different answers i'm not sure which to do. my purpose is to do the domestic sim unlock on this phone, any other advice?
?
eric303 said:
hmm... since i got 2 different answers i'm not sure which to do. my purpose is to do the domestic sim unlock on this phone, any other advice?
Click to expand...
Click to collapse
*delete
Iceburn1 said:
I told you my steps and that I have done it my self, doesnt matter if the partitions are different, it works, trick is to flash the rooted kernel after. As far as a domestic unlock sure fire way and only way on lollipop is paying...idoneapps...http://idoneapps.com/.
Click to expand...
Click to collapse
really??? r u sure???
// anyone comfirm this work??? running KK rom on L Kernel????
Iceburn1 said:
I told you my steps and that I have done it my self, doesnt matter if the partitions are different, it works, trick is to flash the rooted kernel after. As far as a domestic unlock sure fire way and only way on lollipop is paying...idoneapps...http://idoneapps.com/.
Click to expand...
Click to collapse
fantasylovevn said:
really??? r u sure???
// anyone comfirm this work??? running KK rom on L Kernel????
Click to expand...
Click to collapse
No I can't. But I see no reason to doubt what he says he's done himself. I do know the method he mentions was verified for several lollipop ROMs by multiple users.
OTH. Until I read the post above, IIRC, that's the first I've heard of it working on KitKat. TBH, I've not attempted this- "works on any ROM" concept but stayed close or with my bootloader. OB7 bootloader running OG5 being the biggest exception. But I've also made exceptions for kernels and modems but stayed close to revision of bootloader. I feel max compatibility is where they all match. When possible, that's what I run with.
KitKat may boot with your lollipop bootloader and lollipop 5.1.1 custom rooted kernel but how stable and compatible is it? For me, KitKat WiFi Calling was never stable. Not saying it's a total waste of time; use at your own risk.
I can't affirm with absolute certainty that Odin won't allow you to downgrade once your bootloader is greater than OB7 (because I never tried it, myself) but I can say MANY reported and posted failed Odin logs to confirm that. (That is confirmation). AND some had to use Philz CWM touch recovery for Note 4 to factory reset and flash in recovery after TWRP failed to flash afterwards and for a time; there were a few to confirm this. Don't try to "downgrade to KitKat with Odin" unless your bootloader is OB7 or less. If bootloader is greater than OB7, use recovery only plus the kernel mentioned for downgrade. It's a risk vs reward to consider yourself.
Sent from my SM-N910P using Tapatalk
Related
Is there a need to switch recoveries when switching back and forth between kitkat to JB ?
Do you mean from cwm and twrp and contrariwise? No, you don't need to.
Sent from my LG-E986 using xda app-developers app
tomi001 said:
Do you mean from cwm and twrp and contrariwise? No, you don't need to.
Sent from my LG-E986 using xda app-developers app
Click to expand...
Click to collapse
I meant like are higher/newer recoveries for g pro able to install JB roms such as stock based
optimusv45 said:
I meant like are higher/newer recoveries for g pro able to install JB roms such as stock based
Click to expand...
Click to collapse
No for JB you don't need but for KK you must have cwm 6.0.4.4 and about twrp i m not sure.
tomi001 said:
No for JB you don't need but for KK you must have cwm 6.0.4.4 and about twrp i m not sure.
Click to expand...
Click to collapse
So basically need to switch to older recoveries every time switching from kitkat to JB ?
optimusv45 said:
So basically need to switch to older recoveries every time switching from kitkat to JB ?
Click to expand...
Click to collapse
No for downgrade you don' have to flash another recovery.
tomi001 said:
No for downgrade you don' have to flash another recovery.
Click to expand...
Click to collapse
Ic, so newer recoveries for this phone are backward compatible
optimusv45 said:
Ic, so newer recoveries for this phone are backward compatible
Click to expand...
Click to collapse
Yes.
What is the difference between loki-fied and not loki-fied recovery ? .. when do I need which ? Shellnuts freegee and cubes cwm and twrp threads don't say if their recoveries are lokified or not. Phlis touch cwm thread makes a mention of it, but was very confusing, "lokified during flash" , what's that supposed to mean ? He also speak of lokified if bootloader is locked ? So if bootloader is unlocked through freegee you don't need a lokified recovery ? ... I'm super confused ..
I have flashed every KK ROM for the e980 with CWM 6.0.3.7 without fail, fwiw
e980 - I'd tell you which ROM, but I'd have to update my signature thrice daily
thathamiam said:
I have flashed every KK ROM for the e980 with CWM 6.0.3.7 without fail, fwiw
e980 - I'd tell you which ROM, but I'd have to update my signature thrice daily
Click to expand...
Click to collapse
Thats good to know. Did you get the recovery through freegee ? Do you ever switch back to JB ? Switching back and forth without issues too ?
optimusv45 said:
Thats good to know. Did you get the recovery through freegee ? Do you ever switch back to JB ? Switching back and forth without issues too ?
Click to expand...
Click to collapse
Yes, I got this recovery from Freegee. First and only recovery I installed. Have never updated it, because if it ain't broke...
When KK first came to the OGP, I switched back and forth between that and Vanir 4.3 and BS Harmony 4.3 with no problems, back or forth. YMMV, but for me there has never been a problem. One thing to note is that I haven't flashed any of the stock based roms. I am a custom ROM guy through and through.
e980 - I'd tell you which ROM, but I'd have to update my signature thrice daily
thathamiam said:
Yes, I got this recovery from Freegee. First and only recovery I installed. Have never updated it, because if it ain't broke...
When KK first came to the OGP, I switched back and forth between that and Vanir 4.3 and BS Harmony 4.3 with no problems, back or forth. YMMV, but for me there has never been a problem. One thing to note is that I haven't flashed any of the stock based roms. I am a custom ROM guy through and through.
e980 - I'd tell you which ROM, but I'd have to update my signature thrice daily
Click to expand...
Click to collapse
Sounds good. Thanks man
optimusv45 said:
Sounds good. Thanks man
Click to expand...
Click to collapse
[emoji106]no sweat
Sent from my LG-E980 using Tapatalk
The OGP has a locked bootloader. We use Loki as a way to bypass this so we have the full functionality of an unlocked bootloader. The recoveries included in freegee have the loki bypass just as every recovery here on XDA, for our device, has it (I think).
Stock-based ROMs don't require loki as they can run on the stock kernel included with the phone while loki is needed for AOSP-based ROMs due to the change of kernel. Without an unlocked bootloader (or Loki in our case) we'd be stuck on stock-based ROMs which is exactly what happened to the Atrix HD.
Sent from my ColorOS LG-E980
Neroga said:
The OGP has a locked bootloader. We use Loki as a way to bypass this so we have the full functionality of an unlocked bootloader. The recoveries included in freegee have the loki bypass just as every recovery here on XDA, for our device, has it (I think).
Stock-based ROMs don't require loki as they can run on the stock kernel included with the phone while loki is needed for AOSP-based ROMs due to the change of kernel. Without an unlocked bootloader (or Loki in our case) we'd be stuck on stock-based ROMs which is exactly what happened to the Atrix HD.
Sent from my ColorOS LG-E980
Click to expand...
Click to collapse
Thanks man. Sounds like HTC s-on/off
I guess the next obvious question is why wouldn't people just unlock through freegee ? Is it not reliable ?
I rooted mine with 10p and 10k, used a flashable 10k and used lg flash tools. As of right now I still have this error message coming up in freegee telling me "com. lg.hidden menu has stopped working. I thought maybe there was something wrong, that's why I did all these flashes and recoveries. But I still get this error in freegee. I have also NEVER to date seen the "unlock" or "security off" option in freegee.
The last recovery I did was because I flashed a security app, Cerberus, to my phone and it caused it to get stuck on the LG logo. When I flashed Cerberus I got some error message at the end about there being a Loki error. It was a long name and I don't remember it off hand. You guys have to forgive my ignorance as this phone is new to me and I'm just learning all this stuff for it. Am I doing something wrong here? Is there a way to unlock the bootloader now without using freegee? I don't plan to flash a custom rom on here so is freegee and an unlocked bootloader even needed?
Help me out here guys. A really good in-depth sticky on all this stuff would be great but there isn't one, that I found anyway.
That's interesting. I unlocked my optimus g with freegee. I thought one couldnt even have a custom recovery with bootloader locked .. Maybe this is where the Loki thing comes in play
Don't blame yourself man, it is very confusing here with all variants of the phone in one forum. Also I don't think you'll need freegee at all since you aren't planning on using a custom rom.
Freegee is what I used as well. Yes, it's pretty much like S-Off for HTC which is why you see the Secure Boot Error message on boot. :3
For the OGP, instead of freegee unlocking the bootloader it applies Loki. On my old LGOG (E970) freegee actually unlocks the bootloader. But having a locked bootloader has saved me quite a bit of trouble. Just now got my 4th replacement phone (Middle of the screen was waaaaay too bright compared to the rest) for free by using LGFlashTool and putting it back to stock before sending it in. Otherwise I would've ended up owing AT&T around $1,200 lol.
Sent from my ColorOS LG-E980
Helppp!
Hi, I have a samsung galaxy note 8 LTE, which i just updated to 4.4.2.
How do I get this rooted?
-Do i follow this thread? http://forum.xda-developers.com/showthread.php?t=2291839
Seems like that's only confirmed for 4.2.2..
What else should I take note of? I've read things about 'Recovery' and unlocking bootloader.
-Should I do a recovery? How do I do that?
-Do I have to worry about the bootloader?
-Will I be able to get further ota updates after rooting?
Should I wait for 4.4.4 before rooting?
Thank you in advance. I've done alot of reading but I'm still paranoid and confused...
pandabamboo said:
Helppp!
Hi, I have a samsung galaxy note 8 LTE, which i just updated to 4.4.2.
How do I get this rooted?
-Do i follow this thread? http://forum.xda-developers.com/showthread.php?t=2291839
Seems like that's only confirmed for 4.2.2..
What else should I take note of? I've read things about 'Recovery' and unlocking bootloader.
-Should I do a recovery? How do I do that?
-Do I have to worry about the bootloader?
-Will I be able to get further ota updates after rooting?
Should I wait for 4.4.4 before rooting?
Thank you in advance. I've done alot of reading but I'm still paranoid and confused...
Click to expand...
Click to collapse
I have all of these questions!
There's so much information in these forums, and it's very confusing.
I simply can't find a guide for how to get from Kit-kat on the Note 8 to rooted and with civato's ROM (would love some increased pen accuracy).
Any help would really be appreciated!
pandabamboo said:
Helppp!
Hi, I have a samsung galaxy note 8 LTE, which i just updated to 4.4.2.
How do I get this rooted?
-Do i follow this thread? http://forum.xda-developers.com/showthread.php?t=2291839
Seems like that's only confirmed for 4.2.2..
What else should I take note of? I've read things about 'Recovery' and unlocking bootloader.
-Should I do a recovery? How do I do that?
-Do I have to worry about the bootloader?
-Will I be able to get further ota updates after rooting?
Should I wait for 4.4.4 before rooting?
Thank you in advance. I've done alot of reading but I'm still paranoid and confused...
Click to expand...
Click to collapse
I don't have a 5120 but everything I have read confirms that CF Autoroot works without issue on that device. Just make sure after boot up you install SuperSU, update binary, and set it to apply upon system boot. If it doesn't work the first time keep trying. As a warning....this root method will trip Knox and void your warranty. Can follow the steps HERE to root.
You will want to install a custom recovery to flash roms (PhilZ or TWRP). However, changing the recovery, bootloader, etc. will prevent you from taking OTA updates. This is not such a bad thing because you never know if a new OTA will destroy root and lock the device. It is better to let the devs modify it first and then flash it safely. Usually only takes a day or so for devs to do this.
As for changing the bootloader, it depends on the rom you flash. Some will be fine running from older bootloader and some require the KK bootloader. Just check the first post of the rom and it should give you the requirements.
---------- Post added at 09:07 AM ---------- Previous post was at 08:53 AM ----------
jwdink said:
I have all of these questions!
There's so much information in these forums, and it's very confusing.
I simply can't find a guide for how to get from Kit-kat on the Note 8 to rooted and with civato's ROM (would love some increased pen accuracy).
Any help would really be appreciated!
Click to expand...
Click to collapse
You can use CF Autoroot to obtain root and then install custom recovery via Odin as well. Then you can flash whatever rom you want.
7014
As a warning....this root method will trip Knox and void your warranty. Can follow the steps HERE to root.
Click to expand...
Click to collapse
Thanks CCallahan. Do you know of any method that will not trip Knox?
You can use CF Autoroot to obtain root and then install custom recovery via Odin as well. Then you can flash whatever rom you want.
Click to expand...
Click to collapse
I just wasn't sure on the details of these steps, and wasn't sure where to find more detail. I think I've figured it out now.
First I'd follow these steps: http://www.theandroidsoul.com/samsu...n5100-wifi-philz-touch-advanced-cwm-recovery/
Then, I'd use philz to install the custom kernel (edit: and ROM). I haven't been able to find any step-by-step instructions, however. But these seem close enough: https://www.youtube.com/watch?v=aDOY3Oi1VX8
Does this all sound correct?
jwdink said:
Thanks CCallahan. Do you know of any method that will not trip Knox?
I just wasn't sure on the details of these steps, and wasn't sure where to find more detail. I think I've figured it out now.
First I'd follow these steps: http://www.theandroidsoul.com/samsu...n5100-wifi-philz-touch-advanced-cwm-recovery/
Then, I'd use philz to install the custom kernel. I haven't been able to find any step-by-step instructions, however. But these seem close enough: https://www.youtube.com/watch?v=aDOY3Oi1VX8
Does this all sound correct?
Click to expand...
Click to collapse
I do not know of any root method compatible with the N8 that will not trip Knox. Towelroot is not compatible otherwise it would be an obvious choice.
Yes...looks like that walkthrough will work fine for installing PhilZ.
Why are you installing a custom kernel? Are you sticking with the stock rom or flashing a custom one? A lot of roms already come with the kernel packaged.
CCallahan said:
I do not know of any root method compatible with the N8 that will not trip Knox. Towelroot is not compatible otherwise it would be an obvious choice.
Yes...looks like that walkthrough will work fine for installing PhilZ.
Why are you installing a custom kernel? Are you sticking with the stock rom or flashing a custom one? A lot of roms already come with the kernel packaged.
Click to expand...
Click to collapse
I'm installing a custom ROM & Kernel because the accuracy of the pen is not very good on my device, and I primarily brought it for note taking. My understanding is that civato's ROM/kernel will fix this (hopefully!).
But I didn't mean to imply that I'm only installing a custom kernel but keeping the stock ROM. I was planning on doing both, as described in civato's kernel+ROM release thread.
jwdink said:
I'm installing a custom ROM & Kernel because the accuracy of the pen is not very good on my device, and I primarily brought it for note taking. My understanding is that civato's ROM/kernel will fix this (hopefully!).
But I didn't mean to imply that I'm only installing a custom kernel but keeping the stock ROM. I was planning on doing both, as described in civato's kernel+ROM release thread.
Click to expand...
Click to collapse
Ah ok....after you get PhilZ on there just flash civato's rom and you will be good to go.
1928
CCallahan said:
I don't have a 5120 but everything I have read confirms that CF Autoroot works without issue on that device. Just make sure after boot up you install SuperSU, update binary, and set it to apply upon system boot. If it doesn't work the first time keep trying. As a warning....this root method will trip Knox and void your warranty. Can follow the steps HERE to root.
Click to expand...
Click to collapse
Hi CCallahan,
Would you please confirm whether the method described in the link you mentioned to root Galaxy note 8.0 GT-N5120 running android 4.4.2 would work on note 8.0 i467m (LTE canadian version) running on 4.4.2?
beniboy86 said:
Hi CCallahan,
Would you please confirm whether the method described in the link you mentioned to root Galaxy note 8.0 GT-N5120 running android 4.4.2 would work on note 8.0 i467m (LTE canadian version) running on 4.4.2?
Click to expand...
Click to collapse
The procedure is the same but you want to go and download the CF AutoRoot for your device here: http://autoroot.chainfire.eu/
Your device is on the list so is compatible. There are also some basic instructions listed for how to root.
CCallahan said:
The procedure is the same but you want to go and download the CF AutoRoot for your device here:
Your device is on the list so is compatible. There are also some basic instructions listed for how to root.
Click to expand...
Click to collapse
Thanks for your response. I have only one corcern left. In the link you posted, on top of the table of CF-Auto-root, it mentions that if the bootloader is locked this might brick the device! How can I make sure that my bootloader is unlocked prior to start rooting.
Previuosly, I had my note 8 rooted with CF auto root via odine when it was on jelly bean 4.1.2. Does this mean that it is safe to root it again with new CF auto root for 4.4.2?
It's just a warning pal I rooted fine from 4.4.2 with chainfire autorotate it's just a precaution before proceeding as with any flashing procedure it contains a risk of bricking
Sent from my GT-I9505
beniboy86 said:
Thanks for your response. I have only one corcern left. In the link you posted, on top of the table of CF-Auto-root, it mentions that if the bootloader is locked this might brick the device! How can I make sure that my bootloader is unlocked prior to start rooting.
Previuosly, I had my note 8 rooted with CF auto root via odine when it was on jelly bean 4.1.2. Does this mean that it is safe to root it again with new CF auto root for 4.4.2?
Click to expand...
Click to collapse
How did you update to 4.4.2? Rom flash or OTA? Did you manually update the bootloader?
As far as I know Samsung doesn't usually lock bootloaders unless it is carrier dictated. It is usually common on HTC and Moto devices.
Better to be safe than sorry though.
Sent from my SM-G900P using Tapatalk
CCallahan said:
How did you update to 4.4.2? Rom flash or OTA? Did you manually update the bootloader?
As far as I know Samsung doesn't usually lock bootloaders unless it is carrier dictated. It is usually common on HTC and Moto devices.
Better to be safe than sorry though.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
I updated to 4.4.2 via Kies with samsung's released firmware. I havent done any other flashing apart from this. So, I suppose rooting must be fine, right?
beniboy86 said:
I updated to 4.4.2 via Kies with samsung's released firmware. I havent done any other flashing apart from this. So, I suppose rooting must be fine, right?
Click to expand...
Click to collapse
Sorry but I can't/won't confirm whether or not that particular model is safe to root after 4.4.2 upgrade. Maybe someone with more knowledge on that version can chime in. I wouldn't think it would be an issue but don't want to steer you wrong. The bootloader could be locked.
Sent from my GT-N5110 using Tapatalk
CCallahan said:
Sorry but I can't/won't confirm whether or not that particular model is safe to root after 4.4.2 upgrade. Maybe someone with more knowledge on that version can chime in. I wouldn't think it would be an issue but don't want to steer you wrong. The bootloader could be locked.
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
thanks, I will dig in more on this and will post here if I find something useful.
I have a note 4 which I froze at 5.0.1 BOAF version using the debloater utility.
I would like to do the conversion to the DE unlock and flash CM13.
I keep seeing people needing to flash a 5.1.1 kernel in order to avoid bootloops. As I am not on 5.1.1, am I free to do the unlock, flash TWRP and then flash CM13/Gapps?
I really don't want to update to 5.1.1 and would like some input from those with BOAF who have done this. Any issues you had and solutions?
My fear is getting to the point of flashing TWRP and then not being able to flash SU and CM13 because of the TWRP SD card issue.
I am familiar with ADB and have been flashing roms since the DroidX.
Place all the files you need on your internal storage. Then root with Kingroot and unlock the BL. Then go into DL mode and flash recovery. Then you can access you internal SD to flash the Emotion kernel or you will get kernel panic and bootloop. Then flash Super SU 2.67. If you install Xposed you can remedy the TWRP ext SD issue with Wanam Xpose module. I know because I've done been down this road and figured it out today lol. Hope this helps shed a lil light on it for ya.
?If someone helps you, plz thank them?
Sent from my Tab S SM-T700
stajam said:
Place all the files you need on your internal storage. Then root with Kingroot and unlock the BL. Then go into DL mode and flash recovery. Then you can access you internal SD to flash the Emotion kernel or you will get kernel panic and bootloop. Then flash Super SU 2.67. If you install Xposed you can remedy the TWRP ext SD issue with Wanam Xpose module. I know because I've done been down this road and figured it out today lol. Hope this helps shed a lil light on it for ya.
?If someone helps you, plz thank them?
Sent from my Tab S SM-T700
Click to expand...
Click to collapse
So you say to flash a 5.1.1 kernel on a 5.0.1 system? Sounds weird...
Sent from my SM-N910V using Tapatalk
gcodori said:
So you say to flash a 5.1.1 kernel on a 5.0.1 system? Sounds weird...
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Well I understand what you are saying but if you're going to unlock the bootloader anyways and flash a 6.0 ROM what does it really matter. If you're worried about being able to downgrade, there is a safe upgrade method to do that so you can be able to downgrade if you want.
?If someone helps you, plz thank them?
stajam said:
Well I understand what you are saying but if you're going to unlock the bootloader anyways and flash a 6.0 ROM what does it really matter. If you're worried about being able to downgrade, there is a safe upgrade method to do that so you can be able to downgrade if you want.
?If someone helps you, plz thank them?
Click to expand...
Click to collapse
I'm concerned with soft bricking by flashing the wrong version kernel.
And I was asking how to NOT soft brick.
Has anyone done this with 5.0.1 (as the title states) without issue?
Sent from my SM-N910V using Tapatalk
gcodori said:
I'm concerned with soft bricking by flashing the wrong version kernel.
And I was asking how to NOT soft brick.
Has anyone done this with 5.0.1 (as the title states) without issue?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
If you are on 5.0.1, you can do the DE conversion. You don't need to flash a kernel. Once you're done, you can flash the 5.1.1 through odin, install TWRP, and then flash the kernel and superSU again. Don't use the evolution kernel. Use the one from here: http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
https://www.androidfilehost.com/?fid=24415232478676428
gcodori said:
I'm concerned with soft bricking by flashing the wrong version kernel.
And I was asking how to NOT soft brick.
Has anyone done this with 5.0.1 (as the title states) without issue?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
No, you do not have to flash a 5.1.1 kernel if you intend to stay on 5.0.1. However, if you decide to flash anything 5.1.1+, AND WANT ROOT, a 5.1.1+ permissive kernel is required to prevent boot loop.
livinxtreme2114 said:
No, you do not have to flash a 5.1.1 kernel if you intend to stay on 5.0.1. However, if you decide to flash anything 5.1.1+, AND WANT ROOT, a 5.1.1+ permissive kernel is required to prevent boot loop.
Click to expand...
Click to collapse
My confusion was that I had thought that roms included a kernel already, and you only needed to flash a kernel if you wanted a custom one other than what is included with the rom. In the past I have flashed roms that had tweaked kernels included, no need to flash a separate kernel.
So it sounds like if I want to go to CM13 I have to unlock, update to 5.1.1 then do all of the other steps listed.
I was just hoping to skip right over 5.1.1 and go right to CM13 with TWRP using the included CM13 kernel. That is what I was asking, if those of us on 5.0.1 could skip over updating to 5.1.1.
Another question...If I unlock the BL and then update to 5.1.1 as sizzle suggested, won't that lock the BL again?
gcodori said:
Another question...If I unlock the BL and then update to 5.1.1 as sizzle suggested, won't that lock the BL again?
Click to expand...
Click to collapse
This. Glad I found this thread, this question has been hauting me..
I did the bootloader unlock exploit recently and saw I was on 5.0.1. I know that if I want to flash to a 5.1.1 rom I need to update to 5.1.1 prior to get the kernel and modem and what not. My only worry about doing so is whether or not it will re-lock my bootloader in the process. I'm not worried about downgrading, just about losing my bootloader unlock and root.
Here is what I did from stock 5.1.1 on a rooted verizon Note 4 (Using PaulPizz MMB29M.N910VVRS2CQB2):
Using Oden I installed:
VRS2CQB2_modems.tar.md5
VRS2CQB2_Bootloaders_NoAboot.tar.md5 and
VRS2CQB2_NoAboot.tar.md5
The phone boots into 6.0.1 (Kernel 3.10.40) and I have access to TWRP, ADB, ODIN, and root.
Paul suggested "You need to update your aboot partition to 6.0.1. the wifi driver is in the new aboot"
I am a noob and I don't understand what this means. Can anybody give me a list of steps to follow? I think I might be in over my head and returning to stock 6.0.1 might be acceptable.
Old Dude said:
Here is what I did from stock 5.1.1 on a rooted verizon Note 4 (Using PaulPizz MMB29M.N910VVRS2CQB2):
Using Oden I installed:
VRS2CQB2_modems.tar.md5
VRS2CQB2_Bootloaders_NoAboot.tar.md5 and
VRS2CQB2_NoAboot.tar.md5
The phone boots into 6.0.1 (Kernel 3.10.40) and I have access to TWRP, ADB, ODIN, and root.
Paul suggested "You need to update your aboot partition to 6.0.1. the wifi driver is in the new aboot"
I am a noob and I don't understand what this means. Can anybody give me a list of steps to follow? I think I might be in over my head and returning to stock 6.0.1 might be acceptable.
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
dhplap, I appreciate the link to a different process but there seems to be too much assumed knowledge for me to try again (like what am I supposed to do with a .7z file). I am afraid I'm gonna brick the phone. I have flashed back to stock 5.1.1 (BPA1), verified the WiFi was working again and then flashed the stock CQC1 ROM from SamMobile. I really just wanted to get the latest security patches and have found a way to do that. My CID is still 150100523231384d4100657e54fc1200 which may be helpful in the future.
I am done for now with custom ROMs. I may take another swing at it when I have more time to educate myself. You may close this thread. My sincere thanks for your help.
Old Dude said:
dhplap, I appreciate the link to a different process but there seems to be too much assumed knowledge for me to try again (like what am I supposed to do with a .7z file). I am afraid I'm gonna brick the phone. I have flashed back to stock 5.1.1 (BPA1), verified the WiFi was working again and then flashed the stock CQC1 ROM from SamMobile. I really just wanted to get the latest security patches and have found a way to do that. My CID is still 150100523231384d4100657e54fc1200 which may be helpful in the future.
I am done for now with custom ROMs. I may take another swing at it when I have more time to educate myself. You may close this thread. My sincere thanks for your help.
Click to expand...
Click to collapse
You need to either flash the stock mm or lp rom you lost your WiFi do to the fact that your device while I'm certain it says 6.0.1 is in all reality 5.1.1 with the toolchain updated to mm . If you want a stock system with working radio Odin the stock firmware either api works
mojoswagger1980 said:
You need to either flash the stock mm or lp rom you lost your WiFi do to the fact that your device while I'm certain it says 6.0.1 is in all reality 5.1.1 with the toolchain updated to mm . If you want a stock system with working radio Odin the stock firmware either api works
Click to expand...
Click to collapse
He did flash stock mm. It was the last thing he flashed according to his list. He needs to upgrade his bootloader to mm.
dhplap said:
He did flash stock mm. It was the last thing he flashed according to his list. He needs to upgrade his bootloader to mm.
Click to expand...
Click to collapse
What ? Your High champ he said he flashed w/o aboot. That's the safe upgrade if he had flashed stock the bl would have updated itself
mojoswagger1980 said:
What ? Your High champ he said he flashed w/o aboot. That's the safe upgrade if he had flashed stock the bl would have updated itself
Click to expand...
Click to collapse
First of all your wasted. If he flashes stock mm he will lose root and lock his bootloader again and have to go back to bpa1 and start all over. Hence upgrade bootloader. Or he could stay on lollipop.
dhplap said:
First of all your wasted. If he flashes stock mm he will lose root and lock his bootloader again and have to go back to bpa1 and start all over. Hence upgrade bootloader. Or he could stay on lollipop.
Click to expand...
Click to collapse
He did lose root bud he wants to. If u followed the thread to this point u would know that. You read the first and last post and your responses show that .
mojoswagger1980 said:
He did lose root bud he wants to. If u followed the thread to this point u would know that. You read the first and last post and your responses show that .
Click to expand...
Click to collapse
I guess we both missed that he already flashed the stock bpa1 already. I just went off of you telling him to flash stock after he said he already did it. Have a good day bud!
dhplap said:
I guess we both missed that he already flashed the stock bpa1 already. I just went off of you telling him to flash stock after he said he already did it. Have a good day bud!
Click to expand...
Click to collapse
No u missed it . I was telling him the radio is in the bl he didn't flash . IDK what u we're suggest but at least don't actlike this is mutual in any way . We Aren't disagreeing on Minor details.
mojoswagger1980 said:
No u missed it . I was telling him the radio is in the bl he didn't flash . IDK what u we're suggest but at least don't actlike this is mutual in any way . We Aren't disagreeing on Minor details.
Click to expand...
Click to collapse
That's for sure. Read the second post buddy. That's what he needed to do to update his bootloader and keep root if he wanted too, or he could have just flashed a lollipop rom. Understand or no? Sorry, can't play with you anymore right now, gotta go to work. I'll be back later though if you have any questions.
Hi everyone, I have a bit of experience with flashing roms to android phones from the past and I'm coming from an LG G3 that has Lineage OS installed on it.
What I'm looking to do is to get Lineage installed on my HTC 10, I picked it up the other day and it came shipped with Android 7.0 Nougat installed. I haven't got a clue what to do first just in case anything goes wrong.
So my questions are:
How do I unlock the bootloader and is there anything I need to do first? (What is S-Off?)
Can I flash TWRP without rooting the device to just nandroid backup?
How do I go from Stock rom to LineageOS via flashing? Is it just as simple as wiping system etc and flashing in twrp?
I'd urge you to read a lot more before jumping into this because your questions suggest you're really not aware of what you're doing. It helps to comprehend what each of these terms and actions means before you pull the trigger.
Check the 'development' section for how to unlock
S-Off enables you to update firmware separate from ROMs
No, you need to unlock the bootloader to be able to flash TWRP
Once you have unlocked the bootloader and flashed TWRP then yes, flashing a ROM is as easy, but referring to S-Off, you'll need to be sure that your firmware is compatible with the ROM of your choice; if not, you'll have to flash that separately.
Really. Read up. Check these guides first.
https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
https://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
BillTheCat said:
I'd urge you to read a lot more before jumping into this because your questions suggest you're really not aware of what you're doing. It helps to comprehend what each of these terms and actions means before you pull the trigger.
Check the 'development' section for how to unlock
S-Off enables you to update firmware separate from ROMs
No, you need to unlock the bootloader to be able to flash TWRP
Once you have unlocked the bootloader and flashed TWRP then yes, flashing a ROM is as easy, but referring to S-Off, you'll need to be sure that your firmware is compatible with the ROM of your choice; if not, you'll have to flash that separately.
Really. Read up. Check these guides first.
https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
https://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
Click to expand...
Click to collapse
I know my fair share of android modifications and have done so in the past. It's just this is the most ive ever spent on a phone and I dont want to mess it up firstly. I've even compiled roms of my own in the past as you can see from my signature.
johnnzey said:
I know my fair share of android modifications and have done so in the past. It's just this is the most ive ever spent on a phone and I dont want to mess it up firstly. I've even compiled roms of my own in the past as you can see from my signature.
Click to expand...
Click to collapse
Then you have nothing to worry about... flash away!
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Then you have nothing to worry about... flash away!
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
So, it's oem unlock, twrp, backup, and flash away? Reading up on S-off, it only seems useful for those that are doing really specific modding. I just want the ability to either root or flash custom roms so the bootloader unlock should do me fine right?
johnnzey said:
So, it's oem unlock, twrp, backup, and flash away? Reading up on S-off, it only seems useful for those that are doing really specific modding. I just want the ability to either root or flash custom roms so the bootloader unlock should do me fine right?
Click to expand...
Click to collapse
Backup your files (pictures, music etc) first, bootloader unlocking wipes your device
johnnzey said:
So, it's oem unlock, twrp, backup, and flash away? Reading up on S-off, it only seems useful for those that are doing really specific modding. I just want the ability to either root or flash custom roms so the bootloader unlock should do me fine right?
Click to expand...
Click to collapse
Yes, but if you want to flash a custom ROM not supported by your current firmware version, S-off will be necessary.
Sent from my HTC 10 using Tapatalk
How do I know if a rom doesn't support my firmware version? Is that like flashing a CDMA ROM to a GSM phone (that level of difference) ?
Or is it like converting carrier firmware to stock HTC firmware?
johnnzey said:
How do I know if a rom doesn't support my firmware version? Is that like flashing a CDMA ROM to a GSM phone (that level of difference) ?
Or is it like converting carrier firmware to stock HTC firmware?
Click to expand...
Click to collapse
Just check in the thread for the rom you want, installation requirements are usually listed there.