Related
Found this German page just off of Google with what appears to have a guide on rooting kitkat without voiding knox...
http://www.mobtivity.com/de/news/galaxy-note-3-update-auf-android-kitkat-mit-root-und-knox-0x0.html
I posted the link in another thread as well, but figure a new thread will give it some more attention.
Not sure if this would even work on the T-Mobile note 3.
I've never personally rooted before, but planning to once a knox friendly method has been confirmed for KitKat!
Interesting. Going to have to look into the original No-Knox Trip thread too.
SUCCESS! 4.4.2 KitKat Rooted with Knox 0x0!
Success! Followed the German guide in the link and now I have 4.4.2 KitKat Rooted with Knox 0x0! Below is the bootloader file that I created and used.
Dreamgun said:
Found this German page just off of Google with what appears to have a guide on rooting kitkat without voiding knox...
http://www.mobtivity.com/de/news/galaxy-note-3-update-auf-android-kitkat-mit-root-und-knox-0x0.html
I posted the link in another thread as well, but figure a new thread will give it some more attention.
Not sure if this would even work on the T-Mobile note 3.
I've never personally rooted before, but planning to once a knox friendly method has been confirmed for KitKat!
Click to expand...
Click to collapse
joetzzz said:
Success! Followed the German guide in the link and now I have 4.4.2 KitKat Rooted with Knox 0x0! Below is the bootloader file that I created and used.
Click to expand...
Click to collapse
Awesome stuff haha. I wonder how this roots without voiding knox
I wonder if there were more successes?
joetzzz said:
Success! Followed the German guide in the link and now I have 4.4.2 KitKat Rooted with Knox 0x0! Below is the bootloader file that I created and used.
Click to expand...
Click to collapse
Could you post us a picture of your phone with the proof....seeing is believing.
joetzzz said:
Success! Followed the German guide in the link and now I have 4.4.2 KitKat Rooted with Knox 0x0! Below is the bootloader file that I created and used.
Click to expand...
Click to collapse
So you followed every step and just used the bootloader file you uploaded instead of theirs and you are now rooted with KNOX 0x0? Not that I dont believe you, but can you show a screen shot of this please?
My words are my proof, my friend. It's too much trouble for me right now to have to take picture of the Download mode screen. Sorry.
Muffycheeks said:
Could you post us a picture
of your phone with the proof....seeing is believing.
Click to expand...
Click to collapse
Dreamgun said:
Found this German page just off of Google with what appears to have a guide on rooting kitkat without voiding knox...
http://www.mobtivity.com/de/news/galaxy-note-3-update-auf-android-kitkat-mit-root-und-knox-0x0.html
I posted the link in another thread as well, but figure a new thread will give it some more attention.
Not sure if this would even work on the T-Mobile note 3.
I've never personally rooted before, but planning to once a knox friendly method has been confirmed for KitKat!
Click to expand...
Click to collapse
THIS IS T-Mobile Note 3 Forum, why are saying: "Not sure if this would even work on the T-Mobile note 3" ???
wrong forum...
Yes. Just follow the steps. The trickiest part is the extracting bootloader. I had to open the command prompt, go to the folder, and run the batch file, instead of running it directly from Windows explorer. That's why I posted the file here for others to benefit.
droidkevlar said:
So you followed every step and just used the bootloader file you uploaded instead of theirs and you are now rooted with KNOX 0x0? Not that I dont believe you, but can you show a screen shot of this please?
Click to expand...
Click to collapse
---------- Post added at 03:48 PM ---------- Previous post was at 03:37 PM ----------
I confirm that it works on my T-Mobile Note 3 SM-N900T.
belozeroff said:
THIS IS T-Mobile Note 3 Forum, why are saying: "Not sure if this would even work on the T-Mobile note 3" ???
wrong forum...
Click to expand...
Click to collapse
Just to clarify
This method has been used for some time here... http://forum.xda-developers.com/showthread.php?t=2522729&page=69
Also, this is not a 4.4 root method, rather it takes advantage of root while on 4.3 (ex. Root de la vega). So if you already installed the 4.4 bootloader, you have to wait for something else to come along.
You use mobile odin pro (which requires you already have root) to flash the 4.4 ROM while injecting root into it, however mobile odin pro never touches the bootloader and so if you stop there, you can't boot back into your phone. It's a soft brick. You need to update to the 4.4 bootloader using Odin on the desktop after using MOP to flash the ROM.
I tried this the day the update came out and got stuck on the booting recovery screen after I flashed my own 4.4 extracted bootloader. I was forced to Odin to the complete 4.4 and I am stuck with no root unless I auto-cf and lose knox.
effortless said:
This method has been used for some time here... http://forum.xda-developers.com/showthread.php?t=2522729&page=69
Also, this is not a 4.4 root method, rather it takes advantage of root while on 4.3 (ex. Root de la vega). So if you already installed the 4.4 bootloader, you have to wait for something else to come along.
You use mobile odin pro (which requires you already have root) to flash the 4.4 ROM while injecting root into it, however mobile odin pro never touches the bootloader and so if you stop there, you can't boot back into your phone. It's a soft brick. You need to update to the 4.4 bootloader using Odin on the desktop after using MOP to flash the ROM.
I tried this the day the update came out and got stuck on the booting recovery screen after I flashed my own 4.4 extracted bootloader. I was forced to Odin to the complete 4.4 and I am stuck with no root unless I auto-cf and lose knox.
Click to expand...
Click to collapse
So what your saying is, this doesnt work like the person before you said, correct?
I think my bootloader file wasn't created right. This should technically work if the bootloader is correct. It's for preserving a rooted 4.3 to 4.4, not rooting 4.4.
Sent from my SM-N900T using Tapatalk
What's the best and easiest way to to create a bootloader file? I need one for different version of note 3. Any issues since using this method? Like spen or force closes or anything?
Sent from my SM-N900R4 using Tapatalk
The tool in the German guide is supposed to be able to create a bootloader from any rom, given you have the md5 file from Sammobile. Use Google translate if you can't read German.
droidhead36 said:
What's the best and easiest way to to create a bootloader file? I need one for different version of note 3. Any issues since using this method? Like spen or force closes or anything?
Sent from my SM-N900R4 using Tapatalk
Click to expand...
Click to collapse
Ok it works. Pretty easy instruction. Knox still 0x0. But I had to spend $4.99 to buy Mobile Odin Pro.
Things are getting a little confusing... I think this needs an english guide with requirements that people can follow and understand. Q_Q
Dreamgun said:
Things are getting a little confusing... I think this needs an english guide with requirements that people can follow and understand. Q_Q
Click to expand...
Click to collapse
Agreed. Someone that has done this, can you make a quick guide on how to do this exactly coming from 4.3?
I followed the guide and got to 4.4 with root access and KNOX is still on 0x0.
1. I got the initial root on 4.3 with root_de_la_vega and used regionaway to unlock the device as I am currently using my N900T with ATT.
2. Followed all the steps to create the bootloader file after getting the stock firmware for 4.4.
3. Followed the instructions as described on the page using google translater via chrome.
4. After applying the firmware using mobile odin pro...the device gets stuck at recovery booting.
5. Took off the battery for a few and then finally made it to download mode.
6. Tried to use the BL option, but the version of ODIN I had didn't provide an option to choose the BL.
7. Download the ODIN from the instruction page and that provided the option to load the BL i created using the method.
8. Finally the device booted, and I still have root access with KNOW 0x0 and running on 4.4 as well.
Let me know if you need the bootloader file I created and I shall upload the same.
Hope this helps.
Confirmed working; did this yesterday following the instructions, step by step like on the website mentioned; started from 4.3 rooted with Root de la Vega 0x0 Knox flag, unpacked tar.md5 file, created bootloader with the script provided, flashed firmware from Mobile Odin (need to be careful to select after flash option to download mode before you click flash now), then flashed the bootloader I've created using the Odin version provided in the link; everything went smooth, no softbricks, got to keep all my apps and settings, now my phone is running 4.4.2 and is rooted with the Knox flag untouched, 0x0. Only issue I've seen so far is that my default email application keeps FC-ing, can't use it.
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 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
Hi, I'm a long time Android enthusiast, owning, rooting and modding a Nexus 4, LG Optimus V, and Honor 5X. However, the HTC 10 is really confusing to me because of its new Nougat update.
I currently have a US Unlocked HTC 10 with a freshly unlocked bootloader, S-On. I was wondering if I should root it with TWRP Recovery, and install an RUU to keep root, or is that not how it works? I'm jut very confused as to how to keep root going into the Nougat update. Thanks
Thats not how it works.
When you use an RUU, it will not keep root. It will wipe your device full factory reset.
I dont really recommend the 7.0 update just yet as there is no TWRP for it.
Since you are S-ON, you wont be able to downgrade back to 6.0.
You CAN root 7.0 using Magisk if you need to.
http://forum.xda-developers.com/htc-10/development/root-magisk-autoroot-magisk-phhs-t3507505
If Still you want to upgrade, then you should S-OFF FIRST.. so you can downgrade if you want. You can NOT S-OFF from 7.0 yet, and you can not downgrade without S-OFF, so it's a one way ticket if you don't S-OFF first. (for now.)
You cant really Keep root (AKAIK), you'll have to re-root after each update. Here is what I usually do (excluding the 7.0 update for now because there is no TWRP Yet)
1) Flash TWRP.
2) Backup System Image / Boot (Clean - before root).
3) Flash the latest SuperSU to root.
4) When there is a new OTA update, boot to TWRP, restore the Last Clean System Image / Boot images.
5) Flash Latest Stock Recovery.img. (You'll need to find it, or extract it from an OTA Zip)
6) Boot to Rom, Install OTA.
7) Repeat Steps 1-3
Check these links
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
x51 said:
If Still you want to upgrade, then you should S-OFF FIRST.. so you can downgrade if you want. You cant S-OFF from 7.0 yet, and you cant downgrade, so it's a one way ticket for now.
Click to expand...
Click to collapse
Is Sunshine still the only way to S-OFF? If so, is it still a paid option?
elguy said:
Is Sunshine still the only way to S-OFF? If so, is it still a paid option?
Click to expand...
Click to collapse
As far as I know, Yes and Yes.
I was getting along fine without it, until I upgraded to 7.0 and wanted to go back... now I'm stuck.
x51 said:
Thats not how it works.
When you use an RUU, it will not keep root. It will wipe your device full factory reset.
I dont really recommend the 7.0 update just yet as there is no TWRP for it.
Since you are S-ON, you wont be able to downgrade back to 6.0.
You CAN root 7.0 using Magisk if you need to.
http://forum.xda-developers.com/htc-10/development/root-magisk-autoroot-magisk-phhs-t3507505
If Still you want to upgrade, then you should S-OFF FIRST.. so you can downgrade if you want. You can NOT S-OFF from 7.0 yet, and you can not downgrade without S-OFF, so it's a one way ticket if you don't S-OFF first. (for now.)
You cant really Keep root (AKAIK), you'll have to re-root after each update. Here is what I usually do (excluding the 7.0 update for now because there is no TWRP Yet)
1) Flash TWRP.
2) Backup System Image / Boot (Clean - before root).
3) Flash the latest SuperSU to root.
4) When there is a new OTA update, boot to TWRP, restore the Last Clean System Image / Boot images.
5) Flash Latest Stock Recovery.img. (You'll need to find it, or extract it from an OTA Zip)
6) Boot to Rom, Install OTA.
7) Repeat Steps 1-3
Check these links
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Click to expand...
Click to collapse
I see. Seems as it it'd be better to wait for a confirmed root / twrp method for 7.0 first for a guranated method. Thank you, some of these terms are new to me....
x51 said:
As far as I know, Yes and Yes.
I was getting along fine without it, until I upgraded to 7.0 and wanted to go back... now I'm stuck.
Click to expand...
Click to collapse
Unlock bootloader, custom rom to 6.0. Then sunshine or contact me to s-off
ArtOfSnaila said:
I see. Seems as it it'd be better to wait for a confirmed root / twrp method for 7.0 first for a guranated method. Thank you, some of these terms are new to me....
Click to expand...
Click to collapse
I think there are many of us that are in this situation, I will be waiting patiently for a fix to the TWRP issue with 7.0 and then will enjoy the ride...
Sent from my HTC 10 using Tapatalk
Yep, same here. The best option is to wait for Captain Throwback to get TWRP spruced up for Nougat. Flash Nougat then flash TWRP.
stifilz said:
Unlock bootloader, custom rom to 6.0. Then sunshine or contact me to s-off
Click to expand...
Click to collapse
How would I custom Rom to 6.0 without TWRP?
x51 said:
How would I custom Rom to 6.0 without TWRP?
Click to expand...
Click to collapse
Oh yeah, good point lol. Would need to flash an older boot combination I guess. Way to dangerous for most, this is why I s-off first and mess around after. I imagine TWRP won't be long anyway
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.