Related
as title.
prefer twrp if possible.
thank you very much
I haven't actually done this, but here are the steps as I understand them:
1) perform an adb backup -all ( in case you want to go back to stock. Easier than flashing and re-installing all your apps)
2) back up your TA partition
3) Unlock your bootloader
4) Install a kernel that contains your chosen recovery mode, twrp in this case
5) Reboot into recovery mode and install your CM ROM
There are lots of tutorials and guides here on xda. Search for your device model with twrp and kernel/cm10.2.
You can also search the CyanogenMod site, they also have guides for some devices.
Good luck.
http://wiki.cyanogenmod.org/w/Install_CM_for_pollux
I've found that link but it doesn't talk about installing recovery. After installing the kernel (in my experience with HTC One X, boot.img = kernel only), the device somehow has magically received CWM as well?
mrjayviper said:
http://wiki.cyanogenmod.org/w/Install_CM_for_pollux
I've found that link but it doesn't talk about installing recovery. After installing the kernel (in my experience with HTC One X, boot.img = kernel only), the device somehow has magically received CWM as well?
Click to expand...
Click to collapse
You have a lot of reading to do before you're ready to potentially wreck your new tablet. One mistake or flashing the wrong ROM version and you could brick it but good. You will also lose some functionality in the proprietary apps and the OS.
On Xperia devices I believe there is no recovery partition so the recovery mod is integrated into the kernel that you need to install. Pollux_windy is the Cyanogen ROM for the wifi only version of Tab Z and the other pollux_[whatever] is for the Tab z with cell service. The kernel is a separate install that you need to do before flashing the new ROM so that you have a recovery mode to flash from.
I'm quite happy with the stock firmware so I don't plan on installing a ROM just yet. I did toy with the idea of flashing a kernel with a recovery mod but then learned that the Bravia engine and a few other features get disabled when your crypto keys get erased by unlocking the bootloader. Having a recovery mod without the need to install a ROM lost its appeal to me at that point.
This is not exactly what you are looking for but it's a place to start: http://wiki.cyanogenmod.org/w/Install_for_pollux_windy
Be careful and don't rush into this until you are 100% sure you know exactly what you are doing and what you need to accomplish your goal. Eg. If you don't back up your DRM keys before unlocking the bootloader, they are gone for good and you can never get them back. It goes without saying, if you flash a ROM and your Tab develops a problem and you can't get it back to a factory state, you'll lose warranty service.
Does the cyanogenMod kernel work with the stock rom (pollux/LTE)
(Root/Unlcked)
THX
mrjayviper said:
http://wiki.cyanogenmod.org/w/Install_CM_for_pollux
I've found that link but it doesn't talk about installing recovery. After installing the kernel (in my experience with HTC One X, boot.img = kernel only), the device somehow has magically received CWM as well?
Click to expand...
Click to collapse
I've been flashing Samsung (android) & Nexus phones over the last 3 years - but flashing the Tablet Z is quite different.
The replies here from dph3055 give very good advice - I wish I'd read something like it before I began messing with the SXTZ. I messed up straight away by unlocking my bootloader before backing up my TA partition - lost all the DRM keys :crying:
I used to flash new ROM's on my old Galaxy S2 and there was never a issue of bootloader thing and same goes for old Xiaomi phones like redmi 1s.
But recently When xiaomi started locking bootloader , even after unlocking bootloader ,In most of ROM threads there is warning to delete the bootloader file from MIUI recovery ROM and then flash the ROM through recovery as it'll relock the bootloader.
Why does this happen so ?
1) What is the difference between official and unofficial unlocked bootloader ?
2) How much difference does one make if we want to flash all type of ROM's including MIUI , CM ,RR etc ?
3) Is there any way in which bootloader once unlocked , we don't have to worry about getting it relocked by flashing other ROM's like exactly what happens in most other android smartphones after unlocking their bootloader ?
Please clear the above doubts as it's becoming very confusing and irritating on flashing the ROM and what points needed to be kept in mind to avoid bricking the RN3.
Read this thread, my phone was officially unlocked the bootloader and used alka twrp to flash official rom with the ease. No need to do anything, just flashed it, superSU and exposed. Rebooted my phone, done. Only failed on incremental ota update, rebooted phone and received a second ota full rom and always success.
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Sent from my Redmi Note 3 using Tapatalk
lack of good/complete tutorials
I believe flashing has always been a tricky job, more or less. The fact of the matter is that (for our device) I see very little complete tutorials in ROM threads, they all focus on the last bit of flashing. Some hazards are being mentioned and in the best case scenario you get a link to a vague solution (cross other forums and boards), never a full tutorial in the starting topic or the second post however. Back in the days you would see full explanations in every ROM thread, first posts were even being reserved for that. Nowadays users are being supposed to know it al which most do not.
Besides from the complete guides I also noticed that whenever something is explained, the explanations themselves are poor in terms of language (grammar as well as vocabulary) causing even more problems for newbies to fully understand what they are up to.
I am ne to the Xiaomi community but I am absolutely not new to flashing, cooking etc. (started back in the days with iPAQ's and so on) but I also had a though time to end up where I am now with a official unlocked phone that is rooted, has a custom recovery and a Xiaomi.eu ROM. MY journey was a long one but I must conclude that none of the steps were a real hazard, but combining everything in a workflow in correct order was a pain in the back.
First thing that came to me was the idea of writing down my experiences in the form of a FULL tutorial, which I might do when I find the time. I am pretty sure this will help many fellow flashers, newbies and pro's, to establish what most of us did.
These were just my two cents.
P.S. One more thing I noticed is that there are a lot of unfinished projects, they do the job that they were needed for, but they do nothing else.
e.g. Why are there so many custom recoveries, are there no developers anymore that can combine them all to one-fits-all ?
timberwolf60 said:
Read this thread, my phone was officially unlocked the bootloader and used alka twrp to flash official rom with the ease. No need to do anything, just flashed it, superSU and exposed. Rebooted my phone, done. Only failed on incremental ota update, rebooted phone and received a second ota full rom and always success.
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
That is a lot of If else there
Why we can't just flash any rom after unlocking bootloader officially and always have to fear about bootloader relock again?
If i am not mistaken this situation is in Xiaomi phones right ?
Dust2Dust said:
I believe flashing has always been a tricky job, more or less. The fact of the matter is that (for our device) I see very little complete tutorials in ROM threads, they all focus on the last bit of flashing. Some hazards are being mentioned and in the best case scenario you get a link to a vague solution (cross other forums and boards), never a full tutorial in the starting topic or the second post however. Back in the days you would see full explanations in every ROM thread, first posts were even being reserved for that. Nowadays users are being supposed to know it al which most do not.
Besides from the complete guides I also noticed that whenever something is explained, the explanations themselves are poor in terms of language (grammar as well as vocabulary) causing even more problems for newbies to fully understand what they are up to.
I am ne to the Xiaomi community but I am absolutely not new to flashing, cooking etc. (started back in the days with iPAQ's and so on) but I also had a though time to end up where I am now with a official unlocked phone that is rooted, has a custom recovery and a Xiaomi.eu ROM. MY journey was a long one but I must conclude that none of the steps were a real hazard, but combining everything in a workflow in correct order was a pain in the back.
First thing that came to me was the idea of writing down my experiences in the form of a FULL tutorial, which I might do when I find the time. I am pretty sure this will help many fellow flashers, newbies and pro's, to establish what most of us did.
These were just my two cents.
P.S. One more thing I noticed is that there are a lot of unfinished projects, they do the job that they were needed for, but they do nothing else.
e.g. Why are there so many custom recoveries, are there no developers anymore that can combine them all to one-fits-all ?
Click to expand...
Click to collapse
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
akhil17kr said:
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
Click to expand...
Click to collapse
Xiaomi.eu weekly rom was cooked from cn dev rom, removed Chinese apps and put in Google apps and more European languages. Those who wish to flash it must officially unlocked bootloader.
Sent from my Redmi Note 2 using Tapatalk
timberwolf60 said:
Xiaomi.eu weekly rom was cooked from cn dev rom, removed Chinese apps and put in Google apps and more European languages. Those who wish to flash it must officially unlocked bootloader.
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
and What's the difference between officially and unofficially unlocked bootloader ? i have unofficially now , should i officially unlock it ? if it makes flashing procedure easy ?
akhil17kr said:
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
Click to expand...
Click to collapse
Couple of examples: Xiaomi.eu gives me different locales and languages. It also sets default GPS location to Europe instead of Asia which provides a faster GPS fix. It is however behind in development so it doesn't have MIUI 8 yet.
As for the bootloader unlock: I have not looked into that since there is no need. If you follow all the steps in correct order and with correct ROM's official unlocking cannot go wrong. The culprit however is the complete chaos (now I said it) in instructions and tutorials. So I have not looked into the unofficial bootloader unlocking.
Dust2Dust said:
Couple of examples: Xiaomi.eu gives me different locales and languages. It also sets default GPS location to Europe instead of Asia which provides a faster GPS fix. It is however behind in development so it doesn't have MIUI 8 yet.
As for the bootloader unlock: I have not looked into that since there is no need. If you follow all the steps in correct order and with correct ROM's official unlocking cannot go wrong. The culprit however is the complete chaos (now I said it) in instructions and tutorials. So I have not looked into the unofficial bootloader unlocking.
Click to expand...
Click to collapse
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
akhil17kr said:
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
Click to expand...
Click to collapse
I did the same steps above after flashing resurrection remix with cm13 radio,after restoration of miui from twrp Alka backup my fingerprint sensor stopped working bcos the firmware didn't restore and I unchecked that partition so what i did was again.
1) go back to twrp Alka
2) flash the full MIUI 8 rom .zip and rebooted
3) then the fingerprint started working .
So Alka twrp has a bug in Restoration of firmware partition .so be careful and have a full twrp Alka backup and then flash cm13 and firmware
akhil17kr said:
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
Click to expand...
Click to collapse
They look more or less correct, I choose not to go the CM way (yet) since there are still some flaws that I can't live with.
I would try to go to official unlock, whatever it takes. It just looks more solid & safe from what I have been reading so far.
Also I would choose to use an other Recovery:
Official TWRP with F2FS Support
• Based on official TWRP 3.0.2-2 & updated CyanogenMod source
• Adds Support For F2FS based file systems.
• Used for flashing official CyanogenMod 13 based ROMs.
• Users with official unlocked bootloader will have to flash Universal Boot Img Patcher (UBP) after flashing MIUI Recovery ROM Zip.
• Users with unofficial unlocked bootloader should strictly not use this TWRP for flashing MIUI Recovery ROM Zip.
That seems optimized for CM the most.
II should tell you that I received the phone two days ago and I am also still catching up on reading.
Add on, taken from the above link:
In case of unofficial unlock:
4. Flashing Official CM13 ROM
• Flash F2FS TWRP & Backup Current ROM.
• Select /data & /cache Partitions & Select Change File System
• Select F2FS & Swipe To Change
• Reboot to Recovery & Factory Reset
• Reboot to Recovery & Flash CM13 Firmware
• Reboot to Recovery & Flash CM13 Zip
• Flash Appropriate GApps Version Zip & Reboot to System
• To Return Back To Any ROM After Flashing CM13, Flash Safe TWRP v2 & Proceed.
Good evening at all,
I'm Mark99_19. With my LG-P710, two years ago (I had at that time Jellybean version, 4.1.2), I flashed TWRP recovery with this method. And it worked so good.
Now, I've an another phone (Nexus 5 ), and I've given my LG-P710 to my brother.
The phone, with Kitkat version - V20A -, have had an update.
But suddenly, when the phone rebooted to recovery to complete the update, TWRP recovery wasn't able to mount any partition (/data, /system, /sdcard ...) because of Kitkat restrictions - I suppose -, and the version of recovery (v 2.8.1.0)
So, all that I can do is
ADB
Terminal command
Any other function is useless because of no-one partition mounted.
In my opinion, a solution should be to flash a new recovery, for example the last TWRP, or at least, the original recovery. But this one, it seems unable to find..
Anyone can help me?
If you have any questions, please write me
Have a good day,
Mark99_19
First, try flashing a .kdz from here - they have twrp 2.8.1.0.
Now, since we're talking about a P710, I suggest you just flash CM 10.2(JB 4.3.1) (there is a fix for video recording somewhere around here) or CM 11(KK 4.4.4).
If you want, you could also flash the latest TWRP 3.0.2-0.
Hello,
first of all i want to mention that i have a special skill when it comes to choosing smartphones to buy. I like em small and cheap so i always had trouble installing custom roms when buying new phones. Just like this time, when i decidied that replacing my Galaxy S5 Mini screen for the fourth time is just not worth it anymore. I ran to the next store, checked the offers, found the Galaxy A20e, did a quick google "A20e lineage" saw there were a few install threads and decided to buy the phone.
That was on Thursday i have since then continuously tried to either root the stock firmware or flash TWRP to install Lineage GSI.
Whatever i try, when rooting with Magisk and afterwards booting the rooted OS using the recovery key combo, the touchscreen won´t work.
I can boot to the unrooted OS and use the touchscreen.
When installing TWRP using XDADEV guide, i can boot to TWRP right after install, wipe and flash required zip file but after the next reboot i can only boot into stock recovery.
Here´s what i did so far:
Software Used:
- Odin 3.14
- Magisk Manager App 7.5.1
- SamFirm 0.3.6
- downloaded the newest Stock firmware "A202FXXU3BTD1"
- unlocked bootloader / SamsungVault
- Flashed newest Firmware "A202FXXU3BTD1" using Odin.
- Installed Magisk Manager
- Patched extracted file "AP_A202....tar" from "A202FXXU3BTD1"
- Moved the patched AP file back to computer
- Flashed modified AP + stock BL, CP and Home_CSC again
- Wipe/Factory reset
- Start Phone with Power+Volume Up until Logo flashes, then release for rooted OS
- Touchscreen not working
- Boot Phone without root (just press Power Button)
- Touchscreen works fine
II then repeated the complete procedure with an Andoid 9 based FW "A202FXXU3ASL4" which ended with the same result.
Then i wanted to move on, since i always thought that Installing TWRP normally does not require root permissions.
I found several guides, some required root, some not. So i decided to try that. I Found two different testing versions, one from xda and flashed them regarding to the HowTo.
With the Android 10 stock firmware, odin was not able to install them at all.
The Android 9 Stock firmware was able to install TWRP and i was able to wipe and flash additional required zip file but after the next boot, i was only able to boot to stock recovery.
I will continue trying different Firmware versions, for now i want to go back to the newest stock FW since i have tried this one in the beginning of my research, maybe now, 15 hours of work later, i will manage to get it running =D
I am willing to provide further details, just let me know. Hope someone has an idea.
best regards,
Hannes
correcting
after frther testing, there is no way to boot into unrooted OS with working touch once magisk patched firmware is installed
GG
looks like reading and testing for 2 days built the right knowledge so after flashing the most recent firmware and only flashing the modified boot.img again (this was one of my first steps ever) this time it seemed to work.
Magisk is officially installed and the system is rooted. on to the next step, i´ll keep reporting.
on to the next one
I was finally able to get TWRP running after flashing Pie based Stock FW.
Now i am stuck installing Q based GSI, they just wont boot.
Pie based GSI work fine, is flashing Q based Stock FW required to install Q based GSI using TWRP?
SOLVED
hannes22 said:
looks like reading and testing for 2 days built the right knowledge so after flashing the most recent firmware and only flashing the modified boot.img again (this was one of my first steps ever) this time it seemed to work.
Magisk is officially installed and the system is rooted. on to the next step, i´ll keep reporting.
Click to expand...
Click to collapse
Could you be more specific on how you managed to root your A20e SM-202F? I've got the exact same issue with an unresponsive touch screen. My bootloader is unlocked, no problem there. I've tried three different firmwares (one of them being the exact same as stock, and the others are newer versions), and several different (but similar) methods. I've tried patching the firmware with both latest Magisk Manager and the canary version. I use latest Odin. I've also tried to patch both the full AP-file and the only the boot.img (boot.tar). But every time that I reboot into android after I've done the rooting I get a touch screen that's not working. I just can't get past that point...
The phone I'm trying to root has Android 10 and U3 bootloader, NEE version.
EDIT - The solution was to first download and flash the newest firmware _without_ using a patched Boot.img or AP.tar-file. I.e, patching the same firmware the phone had out of the box did NOT work. After the firmware update I could successfully flash the patched Boot.img file and root the phone.
Loaded twrp with odin, then loaded aicp custom rom.
A year later loaded pixel pie custom rom
On power off the fone wouldn't restart in pixel, or twrp
I tried taking the Battery out and waiting 5 mis, 1hr, 3 hrs the fone still wont start.
BUT if the fone is left with the battery out for 3days it starts in both pixel and twrp no problem !!!
I also tried cleaning all partitions on twrp except sd card and loading my image of aicp which used to work, .. no change.
Anyone have an idea what this might be?
The phone is a samsung note 4 snapdragon originally on marshmallow android.
Im thinking of asking samsung to put marshmallow on again then reloading twrp and aicp
What happens when, instead of ACPI power off, you go to TWRP, reload TWRP, and then turn off the phone with TWRP?
If enabling works fine, the ACPI kernel may be to blame.
Be specific about which version of TWRP and ACPI you are using.
ze7zez said:
What happens when, instead of ACPI power off, you go to TWRP, reload TWRP, and then turn off the phone with TWRP?
If enabling works fine, the ACPI kernel may be to blame.
Be specific about which version of TWRP and ACPI you are using.
Click to expand...
Click to collapse
Sorry for delay, each restart takes 3 days!
Thankyou very much for your reply, appreciated,
Yes if close with twrp it opens without problem. If then close with power button have to wait 3 days before it restarts.
Note 4 snapdragon trite official Samsung phone bought uk originally marshmallow
Aicp _trite_q_15_unofficial 202 00 409 april 2020
previously used pexelrom, i dont know vesrion,it was pie though for note4 trite
Twrp 3 6 1 9.0 trite tar From https://eu.dl.twrp.me/trlte/
(the files were .img.tar I assumed this is ok for odin, battery removed and boot first into recovery)
Pleeas can you give me overview of kernal problem,
.........................
The aicp rom worked except battery ran down on pwer off (known fault) Image taken.
Tried pixel rom with incuded gapps pie version and couldnt get twrp (to make image)
Used odin to rload twrp 3 6 1 9.0 trite tar .img.tar file
reloaded my image of aicp
......................
limit of my knowledge here!
Could piexel rom have locked something for future custom roms using twrp
Could the later version of twrp be worse
I assume version of odin twrp are for the original phone (samy note4 snapdragon) not the last custom rom
.... Is twrp in a separate partition that isnt wiped by loading custom rom with twrp? Isit this that is the problem, or someting in the custom rom,. Ive got this far without rooting the phone,has pixel altered this.
......................
If you are installing a new/different custom rom, it's best to do a full wipe with internal memory included.
For many phone models, twrp 3.6.x performs worse than 3.5.2.x.
Since the twrp kernel is good for shutting down the phone, change the ROM to one that also shuts down the phone well.
Read the first post of the thread very carefully and understandingly:
[ROM][UNOFFICIAL][11] LineageOS 18.1 [tblte][trlte][trlteduos]
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS...
forum.xda-developers.com
and install LineageOS 18.1 by @ripee.
gwm121 said:
Sorry for delay, each restart takes 3 days!
Thankyou very much for your reply, appreciated,
Yes if close with twrp it opens without problem. If then close with power button have to wait 3 days before it restarts.
Note 4 snapdragon trite official Samsung phone bought uk originally marshmallow
Aicp _trite_q_15_unofficial 202 00 409 april 2020
previously used pexelrom, i dont know vesrion,it was pie though for note4 trite
Twrp 3 6 1 9.0 trite tar From https://eu.dl.twrp.me/trlte/
(the files were .img.tar I assumed this is ok for odin, battery removed and boot first into recovery)
Pleeas can you give me overview of kernal problem,
.........................
The aicp rom worked except battery ran down on pwer off (known fault) Image taken.
Tried pixel rom with incuded gapps pie version and couldnt get twrp (to make image)
Used odin to rload twrp 3 6 1 9.0 trite tar .img.tar file
reloaded my image of aicp
......................
limit of my knowledge here!
Could piexel rom have locked something for future custom roms using twrp
Could the later version of twrp be worse
I assume version of odin twrp are for the original phone (samy note4 snapdragon) not the last custom rom
.... Is twrp in a separate partition that isnt wiped by loading custom rom with twrp? Isit this that is the problem, or someting in the custom rom,. Ive got this far without rooting the phone,has pixel altered this.
......................
Click to expand...
Click to collapse
Thankyou ze for succinct helpful info.
I am reading very carefully as you suggest
In this section im unsure about ..........."type fastboot reboot" ...
Recovery is to get to twrp right? vol up pwr home with note 4, that would bring up menus on twrp, .there is a menu box for reboot.. Have I undersood this please?
I can follow ypour suggestion tomload an earlier version of twrp
is it possible a later twrp has anything to do with the loading kernal of the rom
"""Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."""