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.
Related
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.
Hello,
I always had a HTC, so I'm kind of a new with rooting and unlocking an LG.
I have a LG D855 international and I have been reading a lot in this forum and I think that I've figured it out. But I just wont to be sure.
So if I'm right than I can root my phone by running purpledrake. When I've done that I have to install SU.
But if I understand it correcly the only way to get twrp is with" Bump'ed TWRP" so it's only possible to have TWRP if I use a custom rom?
So it's not possible to have orig Rom an TWRP? Right?
But If I just root my phone with purpledrake, so without installing TWRP and without custom Rom, I would still be able to use EXPOSED? RIght?
bamps said:
Hello,
I always had a HTC, so I'm kind of a new with rooting and unlocking an LG.
I have a LG D855 international and I have been reading a lot in this forum and I think that I've figured it out. But I just wont to be sure.
So if I'm right than I can root my phone by running purpledrake. When I've done that I have to install SU.
But if I understand it correcly the only way to get twrp is with" Bump'ed TWRP" so it's only possible to have TWRP if I use a custom rom?
So it's not possible to have orig Rom an TWRP? Right?
But If I just root my phone with purpledrake, so without installing TWRP and without custom Rom, I would still be able to use EXPOSED? RIght?
Click to expand...
Click to collapse
Yes Purple Drake is currently the most reliable root method, once you have root you need to install the SuperSU app of your choice.
Don't confuse yourself with Bump! Just accept that this is the only recovery that works with the G3 and install it then use it like normal. You will only be able to flash custom kernels (and roms with custom kernels) after they have been bumped, this is something the developer will do for you not anything for you to be concerned with, and fairly soon (when this method is released) all custom roms and kernels you find on xda will be pre-bumped - so basically you can treat the recovery like you always have done.
Xposed is nothing to do with recovery and everything to do with having root access.
Does this recovery back up my stock rom safely? I'm hesitant to use it because I've never heard of bump.
davidstjohn1 said:
Does this recovery back up my stock rom safely? I'm hesitant to use it because I've never heard of bump.
Click to expand...
Click to collapse
Nope, afaik, once on bumped twrp, u can't restore stock recovery. For that you will again have to flash the stock KDZ.
OK so it's only for bumped roms. Thank you
davidstjohn1 said:
OK so it's only for bumped roms. Thank you
Click to expand...
Click to collapse
The user above you is wrong and didnt read your question properly.
You CAN back up your stock ROM, just install bump, head to recovery and do a backup - you will never get stock recovery back though, unless you flash a KDZ with Flashtool.
But yes you can use TWRP to back up your currenty stock ROM.
Okay I get it the only way to restore the rom that I backed up is to add bump to it! ok I got it but in order to get back my stock phone I'm going to have to use the LG flash tool right
Lennyuk said:
Yes Purple Drake is currently the most reliable root method, once you have root you need to install the SuperSU app of your choice.
Don't confuse yourself with Bump! Just accept that this is the only recovery that works with the G3 and install it then use it like normal. You will only be able to flash custom kernels (and roms with custom kernels) after they have been bumped, this is something the developer will do for you not anything for you to be concerned with, and fairly soon (when this method is released) all custom roms and kernels you find on xda will be pre-bumped - so basically you can treat the recovery like you always have done.
Xposed is nothing to do with recovery and everything to do with having root access.
Click to expand...
Click to collapse
Thanx a lot.
I just wanted to make sure that I have everything right.
Thanks again
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
I've done a little bit of digging and haven't been able to find much, or at least haven't found a lot of details that are "newer" But my question is simple, Is the n910v version, stock, 6.0.1 able to be just simply rooted?
I don't want a custom rom or anything, all i'm needing is root access to remove bloatware and freeze some apps.
any help, direction, or keywords to search for would be greatly appreciated.
mrkrowely said:
I've done a little bit of digging and haven't been able to find much, or at least haven't found a lot of details that are "newer" But my question is simple, Is the n910v version, stock, 6.0.1 able to be just simply rooted?
I don't want a custom rom or anything, all i'm needing is root access to remove bloatware and freeze some apps.
any help, direction, or keywords to search for would be greatly appreciated.
Click to expand...
Click to collapse
Yes, I used these instructions. Then after I was unlocked with TWRP installed I flashed this with Odin, rooted in TWRP and then debloated. After all this you will be on the newest update rooted and unlocked.
so I have to flash down to 5.1.1, then unlock bootloader, gain root, then flash back to stock, then update back to 6.0.1, and then It'll still be unlocked and rooted?
mrkrowely said:
so I have to flash down to 5.1.1, then unlock bootloader, gain root, then flash back to stock, then update back to 6.0.1, and then It'll still be unlocked and rooted?
Click to expand...
Click to collapse
Pretty much but after you go back to 5.1.1, unlock, TWRP and root you are safe to go to update to 6.0.1 with this file. After you flash that flash TWRP again and install root again. After you unlock you are going to be unlocked unless you install the retail firmware and overwrite your aboot. The file I linked says stock restore but it is safe to flash when you are unlocked because I removed aboot.
I'm going to use the guide you posted to try unlock booyloader as and root. If successful, I can flash cm and gapps or do I need the deblosted romyou posted first? Thanks for your help
Sent from my Moto X using XDA-Developers mobile app
flyers00 said:
I'm going to use the guide you posted to try unlock booyloader as and root. If successful, I can flash cm and gapps or do I need the deblosted romyou posted first? Thanks for your help
Sent from my Moto X using XDA-Developers mobile app
Click to expand...
Click to collapse
Of you are going to install other rom, you don't need to de bloated. Just debloat the one you're going to use as default rom..
I'm having issue with kingroot ,after it attempts to root,the phone reboots a couple times. Then I have to restart the process
Sent from my Moto X using XDA-Developers mobile app
Finally got it to work. Only thing I did different I did was use Kongo root. Thanks for the info
Sent from my SM-N910V using XDA-Developers mobile app
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.