Ok, so this is basically just a collection of links to forum posts and a loose guide on how to get your E4 Plus (Qualcomm) up and running with TWRP, LineageOS, and root.
UNLOCKING BOOTLOADER:
So, first you need to navigate here to Motorola's website (https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b).
Follow the steps here and setup a Motorola account (I just linked my Google account) so they can send you your unlock code via email. The rest of the steps will be covered in the link sent to your email by Motorola.
FLASHING TWRP:
First, navigate to ReimuHakurei's thread for their build of TWRP and download it (https://forum.xda-developers.com/moto-e4-plus/development/twrp-twrp-moto-e4-plus-qualcomm-t3697154).
Next, navigate to mauronofrio's thread for their AIO Tool (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993).
Download this and either put your phone in bootloader mode or turn on USB Debugging from your Developer Settings and let the AIO Tool do it for you. Then click "Flash TWRP" and then select "MANUAL MODE" and find ReimuHakurei's TWRP file in the file browser. Check the box that says "And boot it" and click "FLASH".
Your phone should boot to TWRP and we are ready for the next step.
FLASHING LINEAGEOS, GAPPS, AND ROOT:
Navigate to SeanStar's thread for their build of LineageOS and download it (https://forum.xda-developers.com/mo...lineageos-14-1-moto-e4-plus-qualcomm-t3734197)
Now we need to wipe the phone completely. Press "Wipe", press "Format Data", type "yes" and the press the check mark. Next, you need to wipe the rest of the phone. From the "Wipe" screen, press "Advanced Wipe" and check all the boxes except "MicroSDCard" and "USB-OTG" the swipe the "Swipe to Wipe" portion of your screen. Now, copy the Lineage ZIP to your phone via OTG, MicroSD, or MTP. From the main TWRP screen, press "Install" and navigate to where your Lineage ZIP is (if it is on your OTG/MicroSD, press "Select Storage" and select the appropriate option). Tap on your Lineage ZIP and swipe on the "Swipe to confirm Flash" portion of your screen. Do the same with the appropriate GApps ZIP (http://opengapps.org/) and Magisk ZIP (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
Now, reboot to system, follow the setup process, and profit :good:
Thanks to:
ReimuHakurei for their build of TWRP.
SeanStar for their of LineageOS.
topjohnwu for Magisk.
mauronofrio for TOOL ALL IN ONE.
Nice guide. well done!
koop1955 said:
Nice guide. well done!
Click to expand...
Click to collapse
Thank you very much
Data is working for boost in this?
xhan145 said:
Data is working for boost in this?
Click to expand...
Click to collapse
You should check on the Lineage thread (https://forum.xda-developers.com/mo...lineageos-14-1-moto-e4-plus-qualcomm-t3734197) but I would say no, not this time. But development is continuing.
Which gaps configuration for this phone? ARM or ARM64?
EDIT: I flashed ARM and it seems to work.
MrIndieJ said:
Now we need to wipe the phone completely. Press "Wipe", press "Format Data", type "yes" and the press the check mark.
Click to expand...
Click to collapse
I had a problem with this. It wouldn't work because the partition was encrypted. I resolved it bye rebooting to recovery and try it again. I rebooted to recovery AFTER this too before I continued with the next step.
- redacted -
Sizzlechest said:
Which gaps configuration for this phone? ARM or ARM64?
EDIT: I flashed ARM and it seems to work.
Click to expand...
Click to collapse
It's technically a 64bit SoC, I can't find my E4+ at the moment, or I'd check which one I used ?
Sizzlechest said:
I had a problem with this. It wouldn't work because the partition was encrypted. I resolved it bye rebooting to recovery and try it again. I rebooted to recovery AFTER this too before I continued with the next step.
Click to expand...
Click to collapse
Hmm... Odd. I'm gonna dig mine out and see if I can reproduce that problem tonight (currently at work).
MrIndieJ said:
It's technically a 64bit SoC, I can't find my E4+ at the moment, or I'd check which one I used
Click to expand...
Click to collapse
Could I just flash the ARM64 over it or would I have to reinstall the rom?
Sizzlechest said:
Could I just flash the ARM64 over it or would I have to reinstall the rom?
Click to expand...
Click to collapse
I personally would backup and reinstall for stability.
64 bit Gapps didn't work for me, kept throwing an error code at me until I installed the regular ones.
imneveral0ne said:
64 bit Gapps didn't work for me, kept throwing an error code at me until I installed the regular ones.
Click to expand...
Click to collapse
Qualcomm's page says it's 64bit though :0 That's weird...
Exactly why I tried them first. Not sure what the problem was there honestly.
imneveral0ne said:
Exactly why I tried them first. Not sure what the problem was there honestly.
Click to expand...
Click to collapse
Even though it's a 64 bit processor it was released as a 32 bit Android OS. Because of driver issues custom roms will be 32 bit as well. For a 400 series snapdragon it wouldn't make much of a difference. If I remember correctly the G5 series was 32 bit as well and that will make a difference on the 600 series.
Did my second Boost phone using this method. Give special attention to the output from TWRP when you wipe the phone.. If it says it cannot wipe the partition, go back to the main menu in TWRP and reboot back into recovery again. You will be able to wipe now.
Sizzlechest said:
Did my second Boost phone using this method. Give special attention to the output from TWRP when you wipe the phone.. If it says it cannot wipe the partition, go back to the main menu in TWRP and reboot back into recovery again. You will be able to wipe now.
Click to expand...
Click to collapse
I'll add this to the guide, thank you for posting your findings! I just recently found my E4+ again, so I'll be adjusting some stuff with the guide ?
MrIndieJ said:
I'll add this to the guide, thank you for posting your findings! I just recently found my E4+ again, so I'll be adjusting some stuff with the guide
Click to expand...
Click to collapse
I hear there's a newer TWRP for Owens, but it's not on XDA. I haven't tested it.
Sizzlechest said:
I hear there's a newer TWRP for Owens, but it's not on XDA. I haven't tested it.
Click to expand...
Click to collapse
I have installed it and BlissROM and am testing it. No fingerprint on BlissROM, but it's good aside from that. The TWRP seems good too. No hiccups on reformat/wipe.
Related
I went to the dark side in April 2016, and haven't flashed anything in about 2 years. Wife's tablet (flo) needs an update, MM is getting laggy though the tablet has always been good to us.
Titanium was getting to be crap around the last time I used it, with problems mostly restoring, does that still hold true? Might just use it to back up a couple apps she uses a lot and just use Play Store to restore the rest. It's not really important, just curious.
Downloading the TWRP app, I know TWRP is installed but willing to bet it needs to be updated and the app can do that.
Tablet is near its EOL, not planning on rooting it if the ROM doesn't come pre-rooted. I have no idea what Magisk is.
So I'm gonna go into TWRP, wipe system, wipe data, wipe cache, wipe dalvik. Flash ROM (going with Lineage 15.1). Now at one point 2-3 years ago the common wisdom was starting to become "flash ROM, boot ROM, reboot to recovery and then flash Gapps." Y'all still doing that? Or can I just flash Gapps right after flashing ROM and reboot then?
Bit nervous as I haven't flashed in a while, but also kind of exciting.
We've got Android 8.1 Oreo now... Working perfectly on our Nexus 7... You should check it out...
Any suggestions for which are the most stable roms to try? I'm in the same boat. I'm on android 6.0.1, stopped flashing things a while ago and it might even be official! But mine's running like a dog so think I wanna try something to jazz it up!
You should try pure Nexus rom based on 7.1.2 for ultimate good battery life. Oreo is Good but battery isn't the greatest.
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
ganggreen777 said:
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
Click to expand...
Click to collapse
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
Thanks so much for responding back!!!!
Tonight I will follow the steps. I trust it will go fine.
Excited to do this. ......yep I waited this long to root this device
k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
I did the 'install lineageOS on flo and installed TWRP latest. Seem like fastboot went into a slew of commands
and finished. I followed the steps to reboot into recovery and twrp is not there. Android dude opened with red triangle.
I have no clue whats up. I leave it sit, and it reboots into android splash screen and bootsup so i can use the tablet. I guess this is why I am soo perplexed. "Am i missing something?"
ganggreen777 said:
....twrp is not there. Android dude opened with red triangle.
...."Am i missing something?"
Click to expand...
Click to collapse
I think you have missed this step.... "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." - https://twrp.me/asus/asusnexus72013wifi.html
k23m said:
I think you have missed this step.... "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." - https://twrp.me/asus/asusnexus72013wifi.html
Click to expand...
Click to collapse
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Kevin_McLaughlin said:
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Click to expand...
Click to collapse
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this ordecr or else TWRP will be gone again.
Click to expand...
Click to collapse
Why u asking???? Have we chatted b4?¿?
I will do as stated above (I swear I am (thinking) I am doing it as above all the other times. (when you say copy output...is that from the fastboot dialogue? ) ...is it as easy as copy paste ...I dont remember how to copy via adb fastboot...
(Makes me wonder if twrp is really being fastbooted into the n7 2013
Thanks for helping.
k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
Click to expand...
Click to collapse
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
beachfl said:
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
Click to expand...
Click to collapse
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
ganggreen777 said:
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
Click to expand...
Click to collapse
BTW
I am great to go.....thanks very much for helping me thru
---------- Post added at 01:06 AM ---------- Previous post was at 01:04 AM ----------
k23m said:
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
Click to expand...
Click to collapse
BTW I am great to go... Thanks for sticking thru with me
Hi all,
We've worked with TeamWin to get an official release of TWRP for daisy released, and here it is! We're sponsoring continued development of TWRP for daisy and other devices, so reach out to me if you have any questions.
I have to thank Dees_Troy & TeamWin for putting in the effort to make this available for us - donate here to support them directly.
So, without further ado, here's the download link. Here's a link to the source.
Please make sure you're on the factory image. If you aren't, the instructions to do that are here. You will lose your data and you'll have to set up your phone again.
1. Enable developer options (your bootloader should still be unlocked)
2. adb reboot bootloader
3. fastboot boot twrp-daisy-3.2.3-0.img
4. Hit "Cancel" if you're prompted for a decrypt password
5. adb push ./twrp-installer-daisy-3.2.3-0.zip /sdcard
6. Run the install in TWRP to permanently install TWRP across both slots
7. Reboot (you can reboot afterwards to TWRP to verify it is there)
Thanks all - and feel free to post your experiences, questions, comments, and concerns.
, Guava.
adb says "adb: usage: push requires an argument" after using first command.
thanks for the effort though!
tutankpusch said:
adb says "adb: usage: push requires an argument" after using first command.
thanks for the effort though!
Click to expand...
Click to collapse
Oops - ad "/sdcard" to the end of that command. Missed that. I'll update the OP.
I can't get past decryption, but I'll wait for a fixed version. Thanks for going to all this trouble!
KezraPlanes said:
I can't get past decryption, but I'll wait for a fixed version. Thanks for going to all this trouble!
Click to expand...
Click to collapse
Decryption is a Xiaomi issue...what do you mean by fixed version?
d1ngh said:
Decryption is a Xiaomi issue...what do you mean by fixed version?
Click to expand...
Click to collapse
So there's no fix? I can't have my phone secure at all? I thought this was a bug lol
TWRP encryption is how I ended up killing my Note 4X
d1ngh said:
Hi all,
We've worked with TeamWin to get an official release of TWRP for daisy released, and here it is! We're sponsoring continued development of TWRP for daisy and other devices, so reach out to me if you have any questions.
I have to thank Dees_Troy & TeamWin for putting in the effort to make this available for us - donate here to support them directly.
So, without further ado, here's the download link. Here's a link to the source.
Please make sure you're on the factory image. If you aren't, download the files here and run flash_all.sh, then go to recovery and factory reset. You will lose your data and you'll have to set yup your phone again.
1. Enable developer options (your bootloader should still be unlocked)
2. adb push ./twrp-installer-daisy-3.2.3-0.zip /sdcard
3. adb reboot bootloader
4. fastboot boot twrp-daisy-3.2.3-0.img
5. Run the install in TWRP to permanently install TWRP across both slots
6. Reboot (you can reboot afterwards to TWRP to verify it is there)
Thanks all - and feel free to post your experiences, questions, comments, and concerns.
Click to expand...
Click to collapse
How to install de TWRP inside TWRP.. im not finding the file.
And I used the command adb push...
KezraPlanes said:
So there's no fix? I can't have my phone secure at all? I thought this was a bug lol
TWRP encryption is how I ended up killing my Note 4X
Click to expand...
Click to collapse
Try adb push while TWRP is booted. It should get you past the pre-load issue.
actually there was an error when installing twrp.zip from twrp:
"E:recv error un uevent
Unable to find partition for path '/cache'"
but it seems everything is working fine
brunoliveh said:
How to install de TWRP inside TWRP.. im not finding the file.
And I used the command adb push...
Click to expand...
Click to collapse
When you're in the TWRP UI tap "Install" and select the twrp file you pushed (if you used the command above it should be in /sdcard)
tutankpusch said:
actually there was an error when installing twrp.zip from twrp:
"E:recv error un uevent
Unable to find partition for path '/cache'"
Click to expand...
Click to collapse
There isn't a cache partition on A/B devices, that error is fine.
d1ngh said:
Hi all,
We've worked with TeamWin to get an official release of TWRP for daisy released, and here it is! We're sponsoring continued development of TWRP for daisy and other devices, so reach out to me if you have any questions.
I have to thank Dees_Troy & TeamWin for putting in the effort to make this available for us - donate here to support them directly.
So, without further ado, here's the download link. Here's a link to the source.
Please make sure you're on the factory image. If you aren't, download the files here and run flash_all.sh, then go to recovery and factory reset. You will lose your data and you'll have to set yup your phone again.
1. Enable developer options (your bootloader should still be unlocked)
2. adb push ./twrp-installer-daisy-3.2.3-0.zip /sdcard
3. adb reboot bootloader
4. fastboot boot twrp-daisy-3.2.3-0.img
5. Run the install in TWRP to permanently install TWRP across both slots
6. Reboot (you can reboot afterwards to TWRP to verify it is there)
Thanks all - and feel free to post your experiences, questions, comments, and concerns.
Click to expand...
Click to collapse
using the updated command
failed to copy './twrp-installer-daisy-3.2.3-0.zip' to '/sdcard': couldn't create file: Is a directory
brunoliveh said:
using the updated command
failed to copy './twrp-installer-daisy-3.2.3-0.zip' to '/sdcard': couldn't create file: Is a directory
Click to expand...
Click to collapse
If there's already stuff there you'll need to specify the filename as well
Great news!
-Is full encryption working?
-I don't want to loose magisk... how can i preserve it?
d1ngh said:
Try adb push while TWRP is booted. It should get you past the pre-load issue.
Click to expand...
Click to collapse
Hey, that worked! And decryption works after a reboot. But now it's boot looping into TWRP? Did I lose all my data or is there a way to make it boot back into what was installed?
If I have to reinstall it's fine, but I'd like to know
KezraPlanes said:
Hey, that worked! And decryption works after a reboot. But now it's boot looping into TWRP? Did I lose all my data or is there a way to make it boot back into what was installed?
If I have to reinstall it's fine, but I'd like to know
Click to expand...
Click to collapse
That doesn't sound good. Did you factory reset after installing twrp? If so you will have lost data but the ROM should still be there.
d1ngh said:
That doesn't sound good. Did you factory reset after installing twrp? If so you will have lost data but the ROM should still be there.
Click to expand...
Click to collapse
I didn't. I was checking the file system and all my files are there. The ROM is the one who's gone lol.
Can I flash a GSI and have it working again?
Edit: Hooking up USB and I can access storage. Copying stuff over just in case.
KezraPlanes said:
I didn't. I was checking the file system and all my files are there. The ROM is the one who's gone lol.
Can I flash a GSI and have it working again?
Click to expand...
Click to collapse
I've been able to install TWRP before a GSI with relative ease but I couldn't get it to boot properly (phh-treble). I've also been able to install TWRP after a GSI and it works just fine. What GSI are you using? I might be able to test it out pretty quickly.
d1ngh said:
I've been able to install TWRP before a GSI with relative ease but I couldn't get it to boot properly (phh-treble). I've also been able to install TWRP after a GSI and it works just fine. What GSI are you using? I might be able to test it out pretty quickly.
Click to expand...
Click to collapse
I was using stock Android, just with Magisk. Didn't factory reset because I wasn't using a GSI and thought it wouldn't be a problem.
I'm asking if now I can just flash a GSI and have the phone up and running again. It seems storage and everything is there and working fine.
KezraPlanes said:
I was using stock Android, just with Magisk. Didn't factory reset because I wasn't using a GSI and thought it wouldn't be a problem.
I'm asking if now I can just flash a GSI and have the phone up and running again. It seems storage and everything is there and working fine.
Click to expand...
Click to collapse
Switch active slot
---------- Post added at 09:23 PM ---------- Previous post was at 09:23 PM ----------
KezraPlanes said:
I was using stock Android, just with Magisk. Didn't factory reset because I wasn't using a GSI and thought it wouldn't be a problem.
I'm asking if now I can just flash a GSI and have the phone up and running again. It seems storage and everything is there and working fine.
Click to expand...
Click to collapse
Try to Switch active slot
Hey guys, so this is my problem:
I've bought a OnePlus 5T some days after its release. When i searched for a tutorial teaching how to root the device (i don't know the root process deeply), there were just a few videos at that time. This was the video i watched to root me device (some people already told me that this isn't the best method, but it was what I had at the moment):
https://www.youtube.com/watch?v=9SsIH6iauYQ
As i told, i'm a layman and doesn't know the root process, and now i need to update urgently my Android (its currently on the Android version it was when i bought it: 7.1.1). I've found some threads with a similar situation, but i got lost in all the details that i don't know, like "you need to unlock the bootloader", "just flash the TWRP and stuff", but i need a more simple language like "click this, click that". I really need it now, so i'm even thinking about searching for someone trustable to do it or transfering some cash to anyone who helps me, because i don't wanna lose anything important in the process. Anyone that can help me, PLEASE?!
Thanks in advance
djmarkybr said:
Hey guys, so this is my problem:
I've bought a OnePlus 5T some days after its release. When i searched for a tutorial teaching how to root the device (i don't know the root process deeply), there were just a few videos at that time. This was the video i watched to root me device (some people already told me that this isn't the best method, but it was what I had at the moment):
https://www.youtube.com/watch?v=9SsIH6iauYQ
As i told, i'm a layman and doesn't know the root process, and now i need to update urgently my Android (its currently on the Android version it was when i bought it: 7.1.1). I've found some threads with a similar situation, but i got lost in all the details that i don't know, like "you need to unlock the bootloader", "just flash the TWRP and stuff", but i need a more simple language like "click this, click that". I really need it now, so i'm even thinking about searching for someone trustable to do it or transfering some cash to anyone who helps me, because i don't wanna lose anything important in the process. Anyone that can help me, PLEASE?!
Thanks in advance
Click to expand...
Click to collapse
I am not sure, if I understood it correctly. You need to update your device that's clear but do you need your device still rooted afterwards?
Because if not just update your device, it should be that simple. If you need to root your device afterwards just follow this thread:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
Gesendet von meinem CLT-L29 mit Tapatalk
CaerCadarn said:
I am not sure, if I understood it correctly. You need to update your device that's clear but do you need your device still rooted afterwards?
Because if not just update your device, it should be that simple. If you need to root your device afterwards just follow this thread:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
Gesendet von meinem CLT-L29 mit Tapatalk
Click to expand...
Click to collapse
Sorry, actually i forgot this detail. I have a root based on SuperSU and i would like to have the Magisk one after i update my Android. What you think is the best way to do it?
Btw, just one question: you said that if i didn't want to keep the root, i could just update my Android, but once i click in the system update option, the update fails, i believe its because of the root right?
djmarkybr said:
Sorry, actually i forgot this detail. I have a root based on SuperSU and i would like to have the Magisk one after i update my Android. What you think is the best way to do it?
Btw, just one question: you said that if i didn't want to keep the root, i could just update my Android, but once i click in the system update option, the update fails, i believe its because of the root right?
Click to expand...
Click to collapse
No, because you have to download the whole update package. Normally the device detects itself if it is rooted/unlocked, so there should be the option to download the whole package. With that the update should not fail.
Gesendet von meinem CLT-L29 mit Tapatalk
CaerCadarn said:
No, because you have to download the whole update package. Normally the device detects itself if it is rooted/unlocked, so there should be the option to download the whole package. With that the update should not fail.
Gesendet von meinem CLT-L29 mit Tapatalk
Click to expand...
Click to collapse
Where i find this whole package option? Can i just download the last version (5.7.1) on OnePlus site?
@ djmarkybr,
follow this self explanatory guide by Funk Wizard, here:https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
for removing super su you can use uninstaller unsu
a0879 said:
@ djmarkybr,
follow this self explanatory guide by Funk Wizard, here:https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
for removing super su you can use uninstaller unsu
Click to expand...
Click to collapse
Ok, i read the guide so i'll try to follow it once i get home since i don't have admin access on my work.
Just 2 questions:
1- how do i remove SuperSU? I'm asking cause i've download the file you attached and there is no .exe file or something on it, do i put the files on my phone and then execute the uninstaller by the phone itself? If so, how i do it? Btw, i was taking a look at the SuperSU app and it has this option : "Exchange superuser app - Cleaning to exchange for another superuser app", it works just the same as your uninstall?
2- Even reading FunkWizard's guide, i'm still confused of which order i should do the things. Because i need to:
- Uninstall SuperSU
- Download full OTA on OnePlus website and install it through TWRP
- Install Magisk
is there a best order to do all this? Am i missing something?
Thanks
The attached unsu file is for removing super su by flashing thru twrp ! its not not for pc i.e. no .exe file.
i assume that your bootloader is unlocked and twrp already installed then just flash the unsu zip in twrp > wipe dalvik/cache > reboot, super su gets removed.
You can also go like this (you may need a pc for this):
Since you are on nougat build download the oreo version first.
first download the full oos rom from here on pc : https://forum.xda-developers.com/showthread.php?t=3728665http://
download latest magisk zip from here :https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445http://
download no verity zip to remain decrypted, here :https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
boot your phone in twrp , wipe everything (first transfer your important data from phone to pc/usb otg), in twrp you can go advanced > format data > yes > done > reboot twrp > now there is nothing in your phone by formatting internal storage (everything). Now while in twrp transfer your already downloaded oos and magisk zips from pc to your phone through the data cable.
Now, flash oos zip > magisk zip > no verity zip > wipe dalvik/cache > reboot > that's it, enjoy your new android version !
a0879 said:
The attached unsu file is for removing super su by flashing thru twrp ! its not not for pc i.e. no .exe file.
i assume that your bootloader is unlocked and twrp already installed then just flash the unsu zip in twrp > wipe dalvik/cache > reboot, super su gets removed.
You can also go like this (you may need a pc for this):
Since you are on nougat build download the oreo version first.
first download the full oos rom from here on pc : https://forum.xda-developers.com/showthread.php?t=3728665http://
download latest magisk zip from here :https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445http://
download no verity zip to remain decrypted, here :https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
boot your phone in twrp , wipe everything (first transfer your important data from phone to pc/usb otg), in twrp you can go advanced > format data > yes > done > reboot twrp > now there is nothing in your phone by formatting internal storage (everything). Now while in twrp transfer your already downloaded oos and magisk zips from pc to your phone through the data cable.
Now, flash oos zip > magisk zip > no verity zip > wipe dalvik/cache > reboot > that's it, enjoy your new android version !
Click to expand...
Click to collapse
Thank you so much for the help, i'll try this once i get home. Just one more thing: you suggest a Beta Oreo Version or a Stable One? Any version specifically?
djmarkybr said:
Thank you so much for the help, i'll try this once i get home. Just one more thing: you suggest a Beta Oreo Version or a Stable One? Any version specifically?
Click to expand...
Click to collapse
After installing Oreo I don't think that you'll remain on it for a long time.. ha, ha..., Pie is already waiting out there.. :laugh:
go for stable :good:
5.1.3 to 5.1.7
a0879 said:
After installing Oreo I don't think that you'll remain on it for a long time.. ha, ha..., Pie is already waiting out there.. :laugh:
go for stable :good:
5.1.3 to 5.1.7
Click to expand...
Click to collapse
Hey buddy, i followed your steps and now the phone isn't starting totally, it stops on the OnePlus start screen with the white balls around the red one. Should i do the process all again? Can i start TWRP in this situation?
edit: nvm, i try it again and now it works normally But Magisk isn't working, when i try to flash it through TWRP it shows "Updater process ended with ERROR: 1
Error instaling zip file '/sdcard/Magisk....' "
And Android version is still 7.1.1 , so i need to update the Android through the phone itself and then i reapply the root?
edit2: sorry for so many edits in this same reply, let me try to explain the status of all the process right now to see if you can give me some tip:
- Android is on 8.1.0 version right now; Do i need to upload it more?
- Bootloader is unlocked (at least when i go "Enable OEM Unlocking" on Developer options, i cant check this option cause it says that bootloader is already unlocked)
- I can't acess TWRP on reboot now, it seems that i enter on some Oneplus Recovery Mode, not TWRP itself
- Root isn't working
If you need any extra information just ask me
djmarkybr said:
Hey buddy, i followed your steps and now the phone isn't starting totally, it stops on the OnePlus start screen with the white balls around the red one. Should i do the process all again? Can i start TWRP in this situation?
edit: nvm, i try it again and now it works normally But Magisk isn't working, when i try to flash it through TWRP it shows "Updater process ended with ERROR: 1
Error instaling zip file '/sdcard/Magisk....' "
And Android version is still 7.1.1 , so i need to update the Android through the phone itself and then i reapply the root?
edit2: sorry for so many edits in this same reply, let me try to explain the status of all the process right now to see if you can give me some tip:
- Android is on 8.1.0 version right now; Do i need to upload it more?
- Bootloader is unlocked (at least when i go "Enable OEM Unlocking" on Developer options, i cant check this option cause it says that bootloader is already unlocked)
- I can't acess TWRP on reboot now, it seems that i enter on some Oneplus Recovery Mode, not TWRP itself
- Root isn't working
If you need any extra information just ask me
Click to expand...
Click to collapse
I acknowledge your PM, Little tied up at the moment. Please allow me time till tonight to study your case and i shall reply with the best way forward. Don't do anything silly till then
Edit: Please confirm the current status of the device
Rom/OS version
TWRP yes/no
Magisk yes/no
Funk Wizard said:
I acknowledge your PM, Little tied up at the moment. Please allow me time till tonight to study your case and i shall reply with the best way forward. Don't do anything silly till then
Edit: Please confirm the current status of the device
Rom/OS version
TWRP yes/no
Magisk yes/no
Click to expand...
Click to collapse
No problem FunkWizard, take your time and answer when possible, i'll hold my fingers to don't get a worst situation. :angel:
Rom/OS version : Custom ROM(i believe)/8.1.0
TWRP: no; after everything i tried, when i try to acess TWRP now, it doesn't enter on TWRP itself, it shows a different recover screen, like a recovery screen of Oneplus system, just like the picture i attached.
Magisk: no; one of my goals in this entire process was to uninstall SuperSU and install Magisk after all, but when TWRP was working and i tried to install Magisk, i got an error and Magisk didn't install correctly, and since i've uninstalled the SuperSU, i'm without root right now, and i can't even try to install it since TWRP is working right now :crying:
djmarkybr said:
No problem FunkWizard, take your time and answer when possible, i'll hold my fingers to don't get a worst situation. :angel:
Rom/OS version : Custom ROM(i believe)/8.1.0
TWRP: no; after everything i tried, when i try to acess TWRP now, it doesn't enter on TWRP itself, it shows a different recover screen, like a recovery screen of Oneplus system, just like the picture i attached.
Magisk: no; one of my goals in this entire process was to uninstall SuperSU and install Magisk after all, but when TWRP was working and i tried to install Magisk, i got an error and Magisk didn't install correctly, and since i've uninstalled the SuperSU, i'm without root right now, and i can't even try to install it since TWRP is working right now :crying:
Click to expand...
Click to collapse
you lost TWRP sometimes happen but not worry you can easly load again :good:
Mervingio said:
you lost TWRP sometimes happen but not worry you can easly load again :good:
Click to expand...
Click to collapse
Thank God o/ i just need to know how lol :laugh:
djmarkybr said:
No problem FunkWizard, take your time and answer when possible, i'll hold my fingers to don't get a worst situation. :angel:
Rom/OS version : Custom ROM(i believe)/8.1.0
TWRP: no; after everything i tried, when i try to acess TWRP now, it doesn't enter on TWRP itself, it shows a different recover screen, like a recovery screen of Oneplus system, just like the picture i attached.
Magisk: no; one of my goals in this entire process was to uninstall SuperSU and install Magisk after all, but when TWRP was working and i tried to install Magisk, i got an error and Magisk didn't install correctly, and since i've uninstalled the SuperSU, i'm without root right now, and i can't even try to install it since TWRP is working right now :crying:
Click to expand...
Click to collapse
djmarkybr said:
Thank God o/ i just need to know how lol :laugh:
Click to expand...
Click to collapse
If you have oneplus recovery instead of twrp then you can't be on custom ROM, it has to be on oxygenos. Unless I know of what version I would not be able to give you the step by step process.
U can flash twrp easily, simply download the latest Bluspark twrp and flash it via fastboot steps on the unlock device thread in the guides section.
There on you can download and flash the full zips from twrp followed by Magisk.
Sent from my OnePlus6T using XDA Labs
Funk Wizard said:
If you have oneplus recovery instead of twrp then you can't be on custom ROM, it has to be on oxygenos. Unless I know of what version I would not be able to give you the step by step process.
U can flash twrp easily, simply download the latest Bluspark twrp and flash it via fastboot steps on the unlock device thread in the guides section.
There on you can download and flash the full zips from twrp followed by Magisk.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Sorry Funk, i confused the information, my OxigenOS is 5.1.4
I'll wait for your step by step just to make sure i don't do something wrong
Hi. I download the official update on My 5t rooted. But do not install correctly. "installation failed", it's a twrp problem? I i flash the stock recovery works fine? Thanks.
bramby said:
Hi. I download the official update on My 5t rooted. But do not install correctly. "installation failed", it's a twrp problem? I i flash the stock recovery works fine? Thanks.
Click to expand...
Click to collapse
I don't know, i'm also lost here. Hope someone can help you too
bramby said:
Hi. I download the official update on My 5t rooted. But do not install correctly. "installation failed", it's a twrp problem? I i flash the stock recovery works fine? Thanks.[/QUOTE @djmarkybr
I flashed back stock recovery and all went fine with Pie!
Gesendet von meinem CLT-L29 mit Tapatalk
Click to expand...
Click to collapse
I have to tell you :This is the first working TWRP I've found. This os not my work. Just sharing it in Redmi7 Recovery section.
It contains English and Chinese only.
Download link: https://mega.nz/#!TpojlSIA!ymMSB9wBHiza9kSAzqO-8idkuv5mRsvMXQ5rno4Z-so
Redmi 7 special edition TWRP Chinese and English modified optimization version
build date: 2019.4.20
modell: red rice 7, redmi 7
developer: wzsx150
team name: LR.Team
Installation:
Unlocked bootloader required
Working ADB and FASTBOOT connection required
The usually way: with fastboot flash recovery redmi7.img command
after successfully process do not restart the device
type fastboot reboot (do not press enter)
press and hold the volume up button
now press enter
press and hold the volume up button until the fresh TWRP starts
Quote from the Chinese website:
pre-brush into the third-party rec, must unlock the phone! ! Again, the brush machine is risky, please be cautious!
1. This rec supports data partition automatic decryption , encrypted data can be used normally under rec. The official system defaults to encrypting data partitions.
2. This rec supports the official full-page card swipe, but it may cover twrp; when upgrading automatically, you can remove the checkbox of the setting > auto-restart option for easy operation.
3. The bootloader must be unlocked to be able to brush into a third-party rec.
4. Built-in advanced > root system / clear root function.
5. Built-in advanced > remove dm checksum and cancel the forced encryption function, through certain operations, you can remove the official data forced encryption (understand people naturally understand how to operate, because avb2.0 exists, this function may not be normal).
6. Prevent the functions covered by the official rec: root system, signature boot, remove dm check, cancel forced encryption, etc. (some functions may cause the system to fail to enter, carefully operate).
刷入第三方rec前,必须解锁手机!!再次提醒,刷机有风险,操作请谨慎!
1.本rec支持data分区自动解密,加密的data不用格式化也能在rec下正常使用。官方系统默认是加密data分区。
2.本rec支持刷入官方原版全量卡刷包,但可能会覆盖twrp;自动升级时,可以去掉设置>自动重启选项的勾选,方便操作。
3.必须解锁bootloader才能刷入第三方rec。
4.内置高级>root系统/清除root功能。
5.内置高级>去除dm校验和取消强制加密功能,通过一定操作,可以去掉官方的data强制加密(懂的人自然懂怎么操作,因为avb2.0的存在,该功能可能不正常)。
6.防止被官方rec覆盖的功能:root系统、签名boot、去除dm校验、取消强制加密等(部分功能可能导致进不去系统,慎重操作)
Source: http://www.miui.com/thread-23429227-1-1.html
Do not forget! And be aware of it! No one has commanded you to change your phone!
No one has forced you to do this. So, you take every step at your own risk! Full responsibility lies with you!
Awesome! Thank you so much! You Rock!
I installed and works!
MalyMikrus said:
I installed and works!
Click to expand...
Click to collapse
Of course it works. If it wasn't working, I wouldn't have shared it.
JulianJenner said:
Of course it works. If it wasn't working, I wouldn't have shared it.
Click to expand...
Click to collapse
have u try rooting the phone with this twrp?
Yepp. My MIUI Stable is rooted now.
But, after Magisk19.zip you need a DmVerityForcedEncrypt.zip too!
https://mega.nz/#!6xpgQazL!RZALbnhhR8xEiri_7ljivVBZd2RhZYbQSmWd-tTgwtc
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
Thanks !, I have to wait 15 days to unlock the bootloader, and try the twrp with miui eu, do you know if any developer is working in any kernel or rom? Regards!
JulianJenner said:
Yepp. My MIUI Stable is rooted now.
But, after Magisk19.zip you need a DmVerityForcedEncrypt.zip too!
https://mega.nz/#!6xpgQazL!RZALbnhhR8xEiri_7ljivVBZd2RhZYbQSmWd-tTgwtc
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
Click to expand...
Click to collapse
This wasn't needed for me.
I just fastboot flashed the twrp.img file, rebooted into recovery mode (aka TWRP), and then flashed the Magisk v19 zip file.
rebooted and magisk was installed properly, twrp is installed properly
Okay. That is good!
I think zip is needing if you flash stock miui rom, with this twrp...
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
Can you post the dt and source please?
Dev.Team is the chinese LR.Team.They never give out information. Neither device tree nor other...they never share it.
I've mentioned source, where I found it (on first thread).
This is not my work, I just shared.
This is Recovery section of Redmi7. ...and this is a Recovery.
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
JulianJenner said:
Dev.Team is the chinese LR.Team.They never give out information. Neither device tree nor other...they never share it.
I've mentioned source, where I found it (on first thread).
This is not my work, I just shared.
This is Recovery section of Redmi7. ...and this is a Recovery.
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
Click to expand...
Click to collapse
yea, but to publish a thread in this 'development' section, you need to follow XDA rules, which means the source code has to be published as well
Ok.
I thought this recovery is an important thing for Redmi7 users...
If not...okay...delete this thread...or move to an indifferent section. No problemo...
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
how can I flash stock recovery?? Where i can find stock recovery?
IczYn said:
how can I flash stock recovery?? Where i can find stock recovery?
Click to expand...
Click to collapse
On every stock ROM zip and on every stock TGZ file...
JulianJenner said:
On every stock ROM zip and on every stock TGZ file...
Click to expand...
Click to collapse
OK but why when i try download stock rom i cant do this?
Thread closed on OP's request.
LTT
I'm currently on Magisk 20.4
Is it safe to update to 21.4?
I heard some updates didn't go well on our phone.
Thanks
kenbo111 said:
I'm currently on Magisk 20.4
Is it safe to update to 21.4?
I heard some updates didn't go well on our phone.
Thanks
Click to expand...
Click to collapse
Yup, did both updates this morning. Working fine on 21.4
Quick question - I was going to do this myself to provide another datapoint, but I'm wondering about the "Preserve AVB 2.0/dm-verity" option. It's unchecked, which I think is correct... but what does this mean, and how should we have this set (ie, if we think for ourselves, what's this about?)
For some reason, the "Direct Install" (or whatever it's called) option in Magisk Manager didn't work. It just said "download complete" and didn't actually install it. Maybe that's why you heard that the update didn't go well. I had to do the "Download zip only" option, instead, reboot into recovery and install it there. It seems to be working fine. It's just the update option in Magisk Manager that didn't.
Osprey00 said:
For some reason, the "Direct Install" (or whatever it's called) option in Magisk Manager didn't work. It just said "download complete" and didn't actually install it. Maybe that's why you heard that the update didn't go well. I had to do the "Download zip only" option, instead, reboot into recovery and install it there. It seems to be working fine. It's just the update option in Magisk Manager that didn't.
Click to expand...
Click to collapse
Weird, direct install has always worked for me. Other devices not so much, but always on the V30.
schwinn8 said:
Quick question - I was going to do this myself to provide another datapoint, but I'm wondering about the "Preserve AVB 2.0/dm-verity" option. It's unchecked, which I think is correct... but what does this mean, and how should we have this set (ie, if we think for ourselves, what's this about?)
Click to expand...
Click to collapse
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
schwinn8 said:
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
Click to expand...
Click to collapse
Anyone would know better than me, but I've done it checked and unchecked without issue. I lean toward checking it when updating, not really sure why.
ldeveraux said:
Weird, direct install has always worked for me. Other devices not so much, but always on the V30.
Click to expand...
Click to collapse
Yeah, it's always worked for me, as well. This was the first time that it didn't, which is why I mentioned that it could be an issue with this particular version.
schwinn8 said:
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
Click to expand...
Click to collapse
I didn't get a "preserve" option (or any options). Maybe that's only if you're coming from certain versions, like 20.x versions, since I believe that I updated from 21.0.
Osprey00 said:
Yeah, it's always worked for me, as well. This was the first time that it didn't, which is why I mentioned that it could be an issue with this particular version.
I didn't get a "preserve" option (or any options). Maybe that's only if you're coming from certain versions, like 20.x versions, since I believe that I updated from 21.0.
Click to expand...
Click to collapse
Nope, it's there on mine when I upgraded from 21.X to 21.X. It's right there when you expand Option when you start the Install process.
ldeveraux said:
Nope, it's there on mine when I upgraded from 21.X to 21.X. It's right there when you expand Option when you start the Install process.
Click to expand...
Click to collapse
I get no such option when I install it from recovery. Maybe it's only if you install it through Magisk Manager.
Well, I went ahead and installed it with the option unchecked. It applied and booted with no issues. Looks like it worked.
I figured leaving it unchecked makes sense, since I believe we disable dm-verity during the WTF process anyway, so we shouldn't need to touch it. I wanted to be sure before I did it myself, but it seems I didn't have to worry. Unchecked worked for me.
Osprey00 said:
I get no such option when I install it from recovery. Maybe it's only if you install it through Magisk Manager.
Click to expand...
Click to collapse
Well yeah, I thought that would have been clear. I said I was able to flash direct install, not through twrp
ldeveraux said:
Well yeah, I thought that would have been clear. I said I was able to flash direct install, not through twrp
Click to expand...
Click to collapse
I know, and I did the opposite. I was just speaking it out loud for the sake of discussion.
Speaking of things that should've been clear earlier, it's occurred to me that that "Preserve AVB 2.0/dm-verity" probably does exactly what it says. Remember that, until about a year ago, it was recommended to flash a "dm-verity" zip in recovery when installing a ROM. I don't remember the order, but it could've been that we were supposed to flash Magisk first and then dm-verity because Magisk erased the latter. That "preserve" option, therefore, likely allows you to flash Magisk without erasing dm-verity and having to go into recovery after to re-flash it. Now, we haven't needed to flash dm-verity for a year, so the option may not matter if you're using a ROM version that's less than a year old, though there's probably no harm in being safe and checking it. Anyways, that's my guess.
My attempt of update Magisk from 21.4 to 22.0 brought me completely forgotten fastboot screen. Phone no longer boots. Just fastboot screen.
Magisk's direct install seemed to do nothing for unknown reason. Later I needed to reboot and was surprised to see fastboot screen.
Which partition should I flash using fastboot to fix this (especially preserving data, root, twrp etc.) ?
boot or boot + system? I do have a TWRP backups of these, but they are in WIN format. Can Ijust flash them with fastboot?
There's more to this -
fastboot devices
list no devices.
Reinstallation of the LG drivers didn't help.
you
przemhb said:
My attempt of update Magisk from 21.4 to 22.0 brought me completely forgotten fastboot screen. Phone no longer boots. Just fastboot screen.
Magisk's direct install seemed to do nothing for unknown reason. Later I needed to reboot and was surprised to see fastboot screen.
Which partition should I flash using fastboot to fix this (especially preserving data, root, twrp etc.) ?
boot or boot + system? I do have a TWRP backups of these, but they are in WIN format. Can Ijust flash them with fastboot?
Click to expand...
Click to collapse
You need to flash the original boot image from your stock or custom ROM via the flash boot using the command "flashboot flash boot <boot_file>
Then reflash TWRP and re-install magisk. Maybe the v21.4. The latest one broke my boot too. Good luck!
You need to flash the original boot image from your stock
Click to expand...
Click to collapse
I've got TWRP flashable TWRP-H93030b_00_OPEN_EU_0704.zip with two files: boot.img, and boot-original.img.
If I recall correctly boot.img is pre-patched? Which of these should I use?
I finally managed to connect over fastboot.
przemhb said:
I've got TWRP flashable TWRP-H93030b_00_OPEN_EU_0704.zip with two files: boot.img, and boot-original.img.
If I recall correctly boot.img is pre-patched? Which of these should I use?
I finally managed to connect over fastboot.
Click to expand...
Click to collapse
boot.img should be good. You can always flash the other boot image if it does not boot up.
Managed to flash "boot.img", TWRP and boot to TWRP, but... got "Mount Decrypt Data Enter Password".
I haven't encrypted purposely any partition.
Furthermore TWRP locked and doesn't unlock when I try to "swipe to unlock"...
Forced reboot. Android started. Phone works, but Magisk isn't installed. Rebooted once again into TWRP and installed Magisk ignoring data decrypt message. TWRP said it failed, but after reboot Magisk Manager sees Magisk installed and so TitaniumBackup
Seems it solved the prolem.