Related
More details in the Verizon Note 4 forum here.
XDA:DevDB Information
EFIDroid, Kernel for the T-Mobile Samsung Galaxy Note 4
Contributors
abraha2d, m11kkaa
Source Code: https://github.com/efidroid
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
Beta Release Date: 2017-03-18
Created 2017-03-20
Last Updated 2017-03-31
THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!
vegoja said:
THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!
Click to expand...
Click to collapse
Believe me, I didn't do much work. You can donate to @m11kkaa, though. He's the developer of EFIDroid (if you didn't already know that...). I believe he has a donation link in his profile...
Sent from my Samsung Galaxy Note 4 using XDA Labs
This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?
tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?
Mtotallywired said:
tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?
Click to expand...
Click to collapse
EFIDroid is what you would call a "second-stage bootloader". The main advantage over Dual Boot Patcher (at least for me) is that you no longer have to patch zip files before installing. Also, EFIDroid is more than just a multi-boot solution. Quoting @m11kkaa:
efidroid tries to focus on simplicity, and doesn't require any kernel modifications etc.
in general: well having such a powerful bootloader in your boot stage gives you lots of possibilities, like multiboot, replacements/additions for kernels/ramdisk/cmdline.
This project has a lot more potential than what's currently implemented. i.e. you can give samsung devices fastboot and sony devices a standalone recovery. Also you can natively boot GNU GRUB if you're into booting linux kernel's the desktop way.
Click to expand...
Click to collapse
The two solutions are similar enough that you can migrate your setup from Dual Boot Patcher to EFIDroid without losing any data. I'll try to post a guide later this week.
I was I under the impression dual boot required multiple ROMs running the same kernel... If that is the case a huge advantage efi has is each ROM having their own boot img. I'm currently running 3 ROMs a lollipop a marshmallow and of course a nougat. I really just wanted to see all 3 latest android os running flawlessly on 1 device. And I did just that hats off to the developer for this.
baharvey7817 said:
This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?
Click to expand...
Click to collapse
There's an uninstall button in the app. Or, you could just flash the original boot.img via TWRP (basically what the uninstall button does).
I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol
mlock420 said:
I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol
Click to expand...
Click to collapse
you can look at their website, and then decide if you want this level of control over your phone.
http://efidroid.org/
Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.
1freedude said:
Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.
Click to expand...
Click to collapse
There's no way to have two different bootloaders. EFIDroid comes between the bootloader and the boot.img, so it has no control over the bootloader.
EDIT: EFIDroid may be able to emulate the behavior of another bootloader... you would have to ask @m11kkaa for details...
Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk
CousinMikeyP said:
Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk
Click to expand...
Click to collapse
Here is the LINK. You can see more info HERE
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse
I will have to look into it... The EFIDroid app error messages are not exactly the most helpful kind. (Good thing the app is being phased out soon). That particular error message could mean many things, but most likely it's a connection issue. We will continue this in Slack.
Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..
Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse
RaySCLA said:
Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
Click to expand...
Click to collapse
Tried what you suggested but it didn't work either. So, I chose the 'nuclear option': I wiped the phone completely then reinstalled the stock Marshmallow ROM. using Odin. After that i installed TWRP v3.0.2 (trltetmo) and Supersu v2.79 as well as Busybox v1.26. Only then was I able to install EFIDroid successfully. Now, I'm able to boot the stock rom as well as Resurrection Remix.
It seems that if your going to install EFIDroid you must have the phone rooted using SuperSU. Using Magisk to root your phone instead of SuperSu won't work (at least it didn't work in my case).
lowkeyst4tus said:
Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..
Click to expand...
Click to collapse
This should work anywhere, regardless of ROM... But btw, it's a stretch to say TW is just a skin on top of AOSP. In fact, TW is probably the farthest you can get from AOSP... There's a lot of significant differences that make AOSP kernels incompatible with TW ROMs...
Will putting Magisk on My ZTE A2017G with unofficial Lineage 14.1 get passed Safety net and allow me to use apps like Android Pay?
Sent from my ZTE A2017U using Tapatalk
The latest stable version of Magisk (14.0) works fine for me on LineageOS 14.1 and also passes SafetyNet, so the answer is YES. (But I don't know for certain about Android Pay because I don't use it!)
P650SE said:
The latest stable version of Magisk (14.0) works fine for me on LineageOS 14.1 and also passes SafetyNet, so the answer is YES. (But I don't know for certain about Android Pay because I don't use it!)
Click to expand...
Click to collapse
Great thanks for the info I'm just looking at the guide to install it and I don't understand how to do the bit with stock boot image?
Supersilver-Haze said:
Great thanks for the info I'm just looking at the guide to install it and I don't understand how to do the bit with stock boot image?
Click to expand...
Click to collapse
I am not sure what you mean to be honest, where did you see about this? I know when you install LineageOS you have to flash the B15 Universal Bootloader first in TWRP, and you should also flash the Android N modem; both of which are supplied in the Official LineageOS discussion thread. You can then proceed with flashing the ROM and OpenGApps, followed by Magisk 14.0 and anything else you'd like to install before rebooting.
P650SE said:
I am not sure what you mean to be honest, where did you see about this? I know when you install LineageOS you have to flash the B15 Universal Bootloader first in TWRP, and you should also flash the Android N modem; both of which are supplied in the Official LineageOS discussion thread. You can then proceed with flashing the ROM and OpenGapps, followed by Magisk.
Click to expand...
Click to collapse
Yea I've actually done all that and got it working with a bit of stress involved it's just this part in the guide for Magisk "However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN" if you know how to do that bit would be great haha but if not thanks for your help P650E
Supersilver-Haze said:
Yea I've actually done all that and got it working with a bit of stress involved it's just this part in the guide for Magisk "However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN" if you know how to do that bit would be great haha but if not thanks for your help P650E
Click to expand...
Click to collapse
No worries. I don't think you need to worry about anything like that. The usual procedure is just to download Magisk from the link in the official thread on XDA, copy it to the internal storage on the Axon 7 and then flash it in TWRP. It isn't necessary to do anything else, like the stuff you copied above.
P650SE said:
No worries. I don't think you need to worry about anything like that. The usual procedure is just to download Magisk from the link in the official thread on XDA, copy it to the internal storage on the Axon 7 and then flash it in TWRP. It isn't necessary to do anything else, like the stuff you copied above.
Click to expand...
Click to collapse
Oh well that's embarrassing :laugh: just got the zip and flashed like you said everything working perfectly including Android Pay I can't thank you enough :highfive: hope you enjoy the rest of your day and thanks again
Supersilver-Haze said:
Oh well that's embarrassing :laugh: just got the zip and flashed like you said everything working perfectly including Android Pay I can't thank you enough :highfive: hope you enjoy the rest of your day and thanks again
Click to expand...
Click to collapse
Haha, that's quite alright. Feel free to let me know should you have any further problems with the Axon 7. I'm a new owner but have a lot of experience with previous Android devices such as the LG G4 and OnePlus One.
P650SE said:
Haha, that's quite alright. Feel free to let me know should you have any further problems.
Click to expand...
Click to collapse
Ah I know this is a bit fast to be asking about another problem but I just literally found out that I can't make or receive calls on Lineage I can send and receive texts and use data but no calls
Edit: disregard the I figured it out I had it permanently on LTE so I wasn't able to make or receive calls on LTE it seems
Sent from my ZTE A2017U using Tapatalk
Supersilver-Haze said:
Ah I know this is a bit fast to be asking about another problem but I just literally found out that I can't make or receive calls on Lineage I can send and receive texts and use data but no calls
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Hmm, i'm not sure about that one because I didn't use the phone for making calls when I was running LineageOS on my Axon 7. If you installed the Android N modem before flashing the ROM it should work fine in theory. Maybe you can find someone else in the LineageOS thread who's having the same issue.
Does viper4android through magisk work for you. I keep getting error and then magisk force closes
FuzzyDunlop9 said:
Does viper4android through magisk work for you. I keep getting error and then magisk force closes
Click to expand...
Click to collapse
I also had problems getting Viper4Android to work on this device. For me it would install fine, but the audio effects made no difference in apps like Spotify and YouTube, despite having the deep-buffer fix enabled. Try using this version by ahrion instead, it works for me! (Just make sure you remove anything relating to previous installations of V4A beforehand!)
Hello again, I put the question on the forum but doesn't seem like anyone is answering, do you know the process of going from unofficial lineage to official and should I?
Sent from my ZTE A2017U using Tapatalk
Supersilver-Haze said:
Hello again, I put the question on the forum but doesn't seem like anyone is answering, do you know the process of going from unofficial lineage to official and should I?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I don't know how much difference it would make, but installing the Official build of LineageOS is probably slightly better. The method of switching from Unofficial to Official is basically the same as what I posted previously in your other discussion thread:
1. Make sure your apps and files from Unofficial LOS are backed-up.
2. Download the Official LOS ROM and copy it to either the internal or expandable SD card storage on the Axon 7.
3. Download the latest GApps arm64 ZIP for Android 7.1 from OpenGapps and copy it to either the internal or expandable SD card storage on the Axon 7.
4. Reboot the phone into TWRP custom recovery.
5. Enter the 'Wipe' menu and wipe the partitions /data, /system, /dalvik and /cache. (It might not be 100% necessary to wipe /data since you're just switching to an official build of the same ROM, but it is still advisable. You could try installing the ROM without wiping /data, but you may encounter some issues!)
6. Switch the the 'Install' menu and flash Official LOS, followed by the OpenGApps ZIP.
7. Reboot the device.
I have the habit of always asking on a new device no matter how much I think I know!
I have an xt1635-02 (I am US ATT Prepaid)(nano SIM) supposedly here tomorrow so I've been reading tons here.
However, it seems that a lot of the threads are aimed at rooting stock, which I never do.
As a rule, it's trivial:
[!] In this case it seems best to OTA update stock to 7.1.1 if it isn't already. I believe bootloader must be 7.x.x for doing custom Oreo ROMs . Since mine was 6.0 it took about 8 updates OTA and maybe 2 hours(wifi) .
[!]I go to moto site and do the unlock bootloader dance (already carrier unlocked supposedly).
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
[!]Then flash twrp-3.2.1-0-addison.img (Alberto97) using fastboot on my PC. (Ubuntu 17.10 dev 18.04 with adb and fastboot)(dual boot win7)
I do this twice in a row as I have experienced it not working the first time (dead android LOL).(OCD much??? )
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
- - -
[!] -->then flash Alberto's verity patch mentioned at the top of his TWRP thread
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
This modifies stock. Else your backups of stock won't boot. Learned this the hard way!
- - -
[!]Then use TWRP to backup (default settings) stock a couple of times and put copies of both on PC (via USB on stock).(or if for some reason my USB-C doesn't work, via wifi to my router using filezilla FTP and phone app: "wifi file transfer" by "DNL Media UG"(needs permission storage=on..) - I had to redo this twice - redo this twice - kept dropping back to stock recovery.
[!]Then flash the boot logo using fastboot on PC - I usually use TWRP for this but these that I found here are not set up to be TWRP flash compat so will just remove bin from zip and flash using PC. I think I have about 4 possibilities that I found on these threads. Nice! Easy.
[!]Then boot to TWRP and flash Alberto97's AOSP 8.1 arm64 ROM. Why that ROM you may ask. Been using mainly that Alberto97 ROM on my Moto G3 (32bit version of course), and love it. There's plenty of time to try all the others!!!
I usually consider 2 root options; SuperSU 2.82-SR5, or majisk 1520. (for future readers, these are the latest at this time.)(besides I'm very used to them.)
With SuperSU I have had no probs wiping all 4(Dalvik/ART, system, data, cache), flash ROM, flash 8.1 gapps, flash SUperSU, and boot to install.
With majisk I have sometimes had troubles during install if I flash majisk in the first batch so I tend to wipe all 4, flash ROM and gapps, and boot to install. Then when I finally hit desktop, boot back to TWRP and flash 1520 and reboot.
I need root to use TBPro - no restoring on first time with this 64bit ROM- got to do it the hard way!
SO I believe that's it, but if anyone sees a flaw or problem in there, I would appreciate your help.
Thanks!!!
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
fablebreton said:
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
Click to expand...
Click to collapse
Merci! Many thanks for looking in!!!
Yes, forgot to add that - did much xda search on the efs thing and best I found seemed to be a twrp-3.1.1-0-EFS-addison.img which I may very well flash first and do that since no other TWRP that I looked at offers backup efs. Official and squid2 derived (G3) don't. I assume Alberto's doesn't. Seems like I did it very manually on the G3. If you have it it's a pretty good guarantee that you'll never need it! (Murphy axiom)
As to unofficial gapps, I've been testing about 5 different 8.1 ROMs on the Moto G3 over the past couple months and if the gapps aren't built in to the ROM(some pixelexperience roms), all you can get is an unofficial gapps, or do a minor simple hack to an 8.0 so it will accept it. Usually devs will include it. Bless Alberto97 for not including it so I can select my own!!! But I've had no prob with gapps. Open gapps project has 8.0, but of course they won't work on a true 8.1 unless minor hack. I was planning on using open_gapps-arm64-8.1-aroma-20180109-UNOFFICIAL.zip (from https://cloud.kenzoroms.club/?dir=opengapps) unless you have a better idea. I wanted to grab camera from aroma(somebody's idea), but I also have about 5 other cameras and gcams waiting on the Sdcard that I want to test, simply because there seemed to be disagreement on what works on Alberto's new 8.1 build, so wanted to be able to report.
Thanks again!
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
fablebreton said:
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
Click to expand...
Click to collapse
Thanks for great link! yeah I think I used adb as well as an app last time. I'll add recovery this time so that's 3 backups on internal storage (and copied to PC) should be enough! (yes dear readers I am serious about this - 3 times! They are so tiny! And that pretty much guarantees I'll never need it, but if I do, it's childs play to get it back.)
Thanks!!!
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
KrisM22 said:
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
Click to expand...
Click to collapse
Good plan on sending it back. You would have been SOL trying to root the -01
dandrumheller said:
Good plan on sending it back. You would have been SOL trying to root the -01
Click to expand...
Click to collapse
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
KrisM22 said:
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
Click to expand...
Click to collapse
Okay, refund for that and order another from somebody else! Next week...!
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
punkerEVO said:
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
Click to expand...
Click to collapse
yes. stock 8.x is a no-no. This one that is coming is 6.0.1 So I will let it ota update to 7.1.1 after giving it a thorough check-out, then try unlocking it, etc. Sound right? I have no interest in any of the hardware-type addons, just the plain phone 3/32 octacore etc. Why this one? - I love the reception (radio) strength of Motos, plus a ton of other things. I stick with them. Plus it's all Albeto97's fault for deving on AOSP 8.1
Lol Alberto97's roms are buttery smooth!
punkerEVO said:
Lol Alberto97's roms are buttery smooth!
Click to expand...
Click to collapse
I think they are. He recently came out with an 8.1 AOSP version for the Moto G3 and I love it. I test others, but that's my daily driver. Sure not perfect, but quite good enough for me!!! So I figure when I get it (Tues?) that's what I'll put on it. There's always plenty of time to test others!
Okay, since I am waiting for phone (Tues) , obviously I am worried about "what-if"s and so researching on what to do, "if".
I succeeded in finding a nice zip for 7.1.1 with the Nov security patch
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
(I am US)(there are many others at that nice site!!!)
That took a lot of time.
Then I needed to be sure that I could get RSD lite to run, and tried and tried to no avail to get it to recognize my phone (even on my laptop) (I was testing with an old Moto G3 stock zip and my G3 phone) before some post gave me a version number much higher than at the RSD site. google gave me:
http://rsdlite.en.lo4d.com/
version 6.2.4, which worked perfectly.
I really need to write a short guide on this stuff - feels like I'm re-inventing the wheel, even though many folks have written much before I came along!
The reason for the above two is that for a while the last few days I kept running into folks who had taken 7 OTA and wound up with a bricked phone. So, yes, I just did a search for "brick" on xda in moto z play and will start reading them! LOL
Quick EDIT: I think I am wrong in that brick assumption - the first 3 I looked at involved encryption and 2 downgrades to MM (which is a no-no). I will read further.
edit2 - nevermind - most are downgrading to MM. Wish folks would just ask before doing that. That is a no-no of most (all?) phones. -
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
YES! Will do. I have about 5 cameras that I want to try though I will stop at the first one that works. Phone should be here today.
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
I have no problem with various cameras getting good image, but sometimes on still first pic doesn't save. ( tried camera MX and Professional camera hd. I'm sure lots work about the same.)
Forgot to flash Alberto's verity patch right after flashing TWRP. So I had to RSD lite 7.1.1 Nov 1 and start over - no big deal! OP corrected.
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
jeprox said:
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
Click to expand...
Click to collapse
link to 6.2.4 is in the first post of
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194
Can anyone help on how to modify current TWRP to support encryption?
Nothing as of now. The support is dead.
Yesterday I tried rooting my phone by using almost every instance of magisk available on the web, but I either end up with a bootloop or Error 255.
There is no point installing twrp, you will only break your phone.
Only solution is never trust honor again in terms of development support.
SAME Issues.
shailendra1993 said:
Nothing as of now. The support is dead.
Yesterday I tried rooting my phone by using almost every instance of magisk available on the web, but I either end up with a bootloop or Error 255.
There is no point installing twrp, you will only break your phone.
Only solution is never trust honor again in terms of development support.
Click to expand...
Click to collapse
Unfortunately, i'm regretting getting the H8P instead of the OP5. Kinda had a feeling this would happen but took a shot anyway.
Tried many versions of Magisk but all ends up in bootloop. Spent over 30 hours on the device, tinkering.
Best bet would be to flash Stock, lock bootloader and forget about SU . The only choice given how expensive the phone was to a common man when it released.
No more Honor or Huawei every again. For me or anyone who askes for suggestions.
I'm not that into android that i can jump in to help devs aswell. But i will try to stay active and support those who brick their device.
@anirudh & @shailendra1993
Sorry, but you seem both out of topic.
It seems to me latest official magisk is working on your device by flashing a patched ramdisk via fastboot.
Coming back to OP, the latest public TWRP available for your device seem to be there https://forum.xda-developers.com/honor-8-pro/how-to/restoring-dukfullotaromflasher-t3741223But they may not support encryption...
Anirudh A said:
Unfortunately, i'm regretting getting the H8P instead of the OP5. Kinda had a feeling this would happen but took a shot anyway.
Tried many versions of Magisk but all ends up in bootloop. Spent over 30 hours on the device, tinkering.
Best bet would be to flash Stock, lock bootloader and forget about SU . The only choice given how expensive the phone was to a common man when it released.
No more Honor or Huawei every again. For me or anyone who askes for suggestions.
I'm not that into android that i can jump in to help devs aswell. But i will try to stay active and support those who brick their device.
Click to expand...
Click to collapse
Are you looking to have Magisk with Safety net pass ? Let me know i can help. I am on latest Oreo with Magisk and all seems ok.
psbhullar said:
Are you looking to have Magisk with Safety net pass ? Let me know i can help. I am on latest Oreo with Magisk and all seems ok.
Click to expand...
Click to collapse
Thanks ! I get constant bootloops when I flash almost all versions of magisk on stock Oreo 8.0.0.323 . I'm now using AOSP from open krin . 8.1 . Not the most stable rom, but I love stock Android. Definably miss a few stock rom features though. It would help if you tell us the version of magisk flashed and also stock rom version.
And the installation method you followed for magisk was patching boot using magisk manager and flashing the image via fastboot right?
Anirudh A said:
Thanks ! I get constant bootloops when I flash almost all versions of magisk on stock Oreo 8.0.0.323 . I'm now using AOSP from open krin . 8.1 . Not the most stable rom, but I love stock Android. Definably miss a few stock rom features though. It would help if you tell us the version of magisk flashed and also stock rom version.
And the installation method you followed for magisk was patching boot using magisk manager and flashing the image via fastboot right?
Click to expand...
Click to collapse
Follow each step as mentioned and and it works perfect.
https://www.google.co.in/amp/s/foru...de-magisk-root-honor-8-pro-oreo-t3743587/amp/
I am using this past few weeks on Oreo 8 with no bootloops. Yes with Xposed i too had boot loop issues.
Thanks! Works.
psbhullar said:
Follow each step as mentioned and and it works perfect.
https://www.google.co.in/amp/s/foru...de-magisk-root-honor-8-pro-oreo-t3743587/amp/
I am using this past few weeks on Oreo 8 with no bootloops. Yes with Xposed i too had boot loop issues.
Click to expand...
Click to collapse
Hey,
I followed those same instructions before.
From v 15.4, we can directly extract our boot.img , patch it using magisk manager and flash it using fastboot.
And it works like a charm. With data encrypted.
Thanks for your inputs
psbhullar said:
Are you looking to have Magisk with Safety net pass ? Let me know i can help. I am on latest Oreo with Magisk and all seems ok.
Click to expand...
Click to collapse
wait wait... so you have root and adblock /titanium backup working on latest oreo? please let me know.. I want to get to oreo update but I can't lose titanium and adblock (and keep decrypted my sdcard?!?)
Sent from my DUK-L09 using Tapatalk
I come from an Honor 8 completely turned inside out (root,twrp,xposed,gravity,substratum,v4a,titanium backup,kali linux and so so so on).
Can I hope to get almost half of them on my new Honor 8 Pro? I would stay on latest stock B189, but If I well understand there are problems with TWRP and TB because of encryption. What is the state of the art we can get on Nougat? Thanks a lot.
gianmaxfactor said:
I come from an Honor 8 completely turned inside out (root,twrp,xposed,gravity,substratum,v4a,titanium backup,kali linux and so so so on).
Can I hope to get almost half of them on my new Honor 8 Pro? I would stay on latest stock B189, but If I well understand there are problems with TWRP and TB because of encryption. What is the state of the art we can get on Nougat? Thanks a lot.
Click to expand...
Click to collapse
https://consumer-tkb.huawei.com/tkbapp/downloadWebsiteService?websiteId=768024
Hello again all!
So I've recently discovered the glory of GSI / Treble roms! Good stuff! But after much banter with Ressurection remix's 9.0 GSI rom, I have still yet to get it working, and wasn't sure if I'm just missing something.
So far, what I've tried is:
- Wiping everything (caches, system, data) as well as formatting my data partition
- then installing the rom. after a couple of routine-looking reboots, the system boots without gapps functioning great.
- quick settings states 'No SIM card', which is false
- reinstalled rom countless times
- restored to functioning rom, backed up EFS, reinstalled RRemix in the same fashion, restored EFS backup. No solve there.
And with that, I'm out of ideas and without much knowledge of GSI / Treble processes, I'm not even sure how to word searches for help. Any advice ya'll?
Hey man, let me know if you still haven’t gotten this resolved and are still looking to do so. After days of research and experimentation I finally created a process to reliably flash a fully functional RR 7.X rom. I can provide my boot.img and instructions if you need them.
Derbyy said:
Hey man, let me know if you still haven’t gotten this resolved and are still looking to do so. After days of research and experimentation I finally created a process to reliably flash a fully functional RR 7.X rom. I can provide my boot.img and instructions if you need them.
Click to expand...
Click to collapse
I'm interested in this for sure. I'm curious, are you guys using the A only IMG of treble ROMs?
jal3223 said:
I'm interested in this for sure. I'm curious, are you guys using the A only IMG of treble ROMs?
Click to expand...
Click to collapse
It’s funny you should reply to me on today of all days. This morning, after a month of testing, I finally succeeded in getting my RP2 to A/B boot RR 7, TWRP, AND have it rooted with Magisk. I couldn’t believe I finally got it. AMA
Are any of you on Verizon? I've tried multiple GSIs and have never gotten LTE to work properly.
Reznor7 said:
Are any of you on Verizon? I've tried multiple GSIs and have never gotten LTE to work properly.
Click to expand...
Click to collapse
Did you try an A only image? It should work as it doesn't touch the vendor image or CSC. At first I was trying AB images on my Note 9 and could never get signal. I found out that we are only supposed to use the A only images on that device and my problems were solved. I haven't tried anything on my Razer Phone 2 though as the stock ROM is pretty much exactly what I want. It's worth a try.
Need RR help.
Derbyy said:
Hey man, let me know if you still haven’t gotten this resolved and are still looking to do so. After days of research and experimentation I finally created a process to reliably flash a fully functional RR 7.X rom. I can provide my boot.img and instructions if you need them.
Click to expand...
Click to collapse
Hey, can I get that boot.img and instructions if you can still provide them? I want to install r.r 7.x please. Sorry for messaging you 4 months later.
jal3223 said:
Did you try an A only image? It should work as it doesn't touch the vendor image or CSC. At first I was trying AB images on my Note 9 and could never get signal. I found out that we are only supposed to use the A only images on that device and my problems were solved. I haven't tried anything on my Razer Phone 2 though as the stock ROM is pretty much exactly what I want. It's worth a try.
Click to expand...
Click to collapse
sorry to disturb you years later,but why not try to flash another gsi like crdroid,boot into it and flash you rr rom back?
this strange method worked on my redmi 10a