Related
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable
I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.
SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553
Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .
I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse
bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.
After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818
1.) You must have a full ZIP from ZTE
2.) Flash back the Original Recovery from the Original ZIP e.g. B08 B10 with ADB Fastboot command ( You must ticked OEM unlock on and USB debugging on in Developer Setting ) in Lineage.
2.1) push Power and tick restart in Bootloader.
2.2) go to Minimal ADB and Fastboot and type fastboot flash recovery recovery.img.
2.3) After this push with the Volume down recovery ,tick power.
OK! You can see the ORIGINALRecovery from ZTE.
3.) You must put a SD Card in Phone with the Original Update.zip
4.) Go in recovery and tick Update from SD card. Search the Update.zip and press Power.
5.) Wait until the Flash Process is finished.
6.) Tick Factory reset with Volume up/down push Power wait.
7.) Tick format Cache with Volume up / down push Power wait.
8.) Push Power to start your Phone with the Original Stock.
9.) After this you go to Settings / Build Number and Tick that seven Times to activate Developer Options, go back to setting and tick Developer Options ,here you must tick the OEM unlocking and USB debugging.
10.) Open Command window on PC and type "fastboot reboot bootloader" the phone shut down and restart in bootloader mode.
11.) in the Comand window you type" Fastboot oem lock" the Phone reboot and the bootloaer is locked. All your Data is lost in this Process!!![COLOR="Red"][/COLOR]
Voila all is done!! Original AXON 7 with Stock Rom .
I have test this with my Axon 7 Model A2017G and i have no Problem.
Sorry for my bad English.
Thanks for writing this out. Will be useful in case I need to switch back in the future
Where do you get the stock rom zip file though? zteusa.com somewhere?
spacemanvt said:
Thanks for writing this out. Will be useful in case I need to switch back in the future
Where do you get the stock rom zip file though? zteusa.com somewhere?
Click to expand...
Click to collapse
There is a global site where you can get the file. http://www.ztedevice.com/support/detail?id=C3BAC27838C4497C80C05EE008527885
Sent from my ZTE A2017G using XDA-Developers Legacy app
Hello,
I recovered my old stock recovery and when trying to apply update from sd card, it gives me this error: "Couldn´t mount /sdcard. installation aborted"
What can I do?
Edit: Solved by formatting the SD card
What is the ADB fastboot command to flash stock recovery?
JP_93 said:
What is the ADB fastboot command to flash stock recovery?
Click to expand...
Click to collapse
fastboot flash recovery "stock Recovery"
Flash the Original recovery.img from your Update.zip!!
JP_93 said:
What is the ADB fastboot command to flash stock recovery?
Click to expand...
Click to collapse
open Update.zip with e.g Winrar and unpacking recovery.img to the ADB directory. OK?!
Then open a Command Window and Type : fatboot flash recovery recovery.img . Wait.
Shutdown your Phone . Restart Phone wit push Power and Volume up.
tick with the Volume down botem update from SD card.
julk13 said:
fastboot flash recovery "stock Recovery"
Click to expand...
Click to collapse
Thanks!
tester2017 said:
open Update.zip with e.g Winrar and unpacking recovery.img to the ADB directory. OK?!
Then open a Command Window and Type : fatboot flash recovery recovery.img . Wait.
Shutdown your Phone . Restart Phone wit push Power and Volume up.
tick with the Volume down botem update from SD card.
Click to expand...
Click to collapse
Thanks for the help, I will try now
10.) Open Command window on PC and type "fastboot reboot bootloader" the phone shut down and restart in bootloader mode.
Click to expand...
Click to collapse
You made a mistake there as you have to enter "adb reboot bootloader" instead of fastboot. Other than that, it works perfectly. Thank you.
I can't get my bootloader locked. Under dev options, "OEM Unlocking" it grayed out.
idigg said:
I can't get my bootloader locked. Under dev options, "OEM Unlocking" it grayed out.
Click to expand...
Click to collapse
Did you find a solution to this? I'm running into the same problem with OEM unlocking being grayed out. I returned to stock just fine, but my problem is booting into the bootloader. Every time I try, it just goes to the "your device cannot be checked for corruption and will reboot in 5 seconds" screen. During this screen and during the screen that comes up you press the volume keys for the options menu, the fastboot oem lock command does not seem to work. Fastboot devices doesn't show any devices listed either
spearman792 said:
Did you find a solution to this? I'm running into the same problem with OEM unlocking being grayed out. I returned to stock just fine, but my problem is booting into the bootloader. Every time I try, it just goes to the "your device cannot be checked for corruption and will reboot in 5 seconds" screen. During this screen and during the screen that comes up you press the volume keys for the options menu, the fastboot oem lock command does not seem to work. Fastboot devices doesn't show any devices listed either
Click to expand...
Click to collapse
Seconded, I'm having the very same problem. Strange thing is, I cannot boot into booloader. I can boot into recovery, I can boot to system but whan I try to boot into bootloader via adb reboot bootloader, the phone just boots into system. If I try Power/Vol-Down, I will eventually land in FTM mode.
Anybody any clue?
SOLVED: After using the Windows based Axon7Toolkit which used Miflash to restore fastboot, I was able to boot into bootloader and also re-lock it.
robertaramar said:
Seconded, I'm having the very same problem. Strange thing is, I cannot boot into booloader. I can boot into recovery, I can boot to system but whan I try to boot into bootloader via adb reboot bootloader, the phone just boots into system. If I try Power/Vol-Down, I will eventually land in FTM mode.
Anybody any clue?
SOLVED: After using the Windows based Axon7Toolkit which used Miflash to restore fastboot, I was able to boot into bootloader and also re-lock it.
Click to expand...
Click to collapse
You couldn't boot into bootloader because there was no bootloader mode. As soon as you update to a recent Nougat build (or an upcoming one) via official zips, your aboot.img will be changed and you won't have bootloader mode anymore. Axon7toolkit relies on fastboot, so it flashes a package through MiFlash that gets you fastboot support.
Jus sayin
Thanks for the clarification.
Is there an aboot.img I can flash e.g. via axon7tool so I can enable fastboot again?
Would that be counted as a warranty void by ZTE?
robertaramar said:
Thanks for the clarification.
Is there an aboot.img I can flash e.g. via axon7tool so I can enable fastboot again?
Would that be counted as a warranty void by ZTE?
Click to expand...
Click to collapse
You can use the A2017U_FASTBOOT_UNLOCK_EDL from 4pda guys with MiFlash. Doesn't matter if you have a G, use this one
Actually axon7toolkit seems to flash that every time it does something related to fastboot. And after you lock it, you can install an official update zip (the latest one for example) and you'll get your phone totally stock, bootloader mode will be blocked.
Now that LG has released the bootloader unlock for the RS988 it can now be rooted.
------------------------------------------------------------------------Disclaimer---------------------------------------------------------------------------------------
This post is meant to be educational and I am not responsible for any lost data or damaged devices resulting from the following instructions
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-----Instructions on Unlocking your bootloader can be found here---------
WARNING THIS WILL FORMAT YOUR DEVICE
https://forum.xda-developers.com/lg-g5/development/official-european-lg-g5-h850-bootloader-t3363040
The only difference is selecting RS988 when selecting your device
---------------------------------------------------------------------------------------
Requierments:
ADB
fastboot
An RS988 LGG5
The working (though not entirely tested!) TWRP image is found here https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-rs988.img (Thank you jeffsga88 for finding this link)
The Latest SuperSu Binary
Step 1:
Make sure your RS988 is fully updated, the rebooting into the bootloader is only unlocked in the most recent updates.
Step 2:
Enable Developer options and USB Debugging
Step 3:
Enter Command
Code:
adb reboot bootloder
Step 4:
Once in bootloader run
Code:
fastboot flash recovery [path to twrp image on your pc]
Step 5:
Turn off the device DO NOT let it boot back into android!!
If you do boot back into android, you will need to re-flash TWRP (Steps 1-4)
Step 6:
With your device unplugged, hold power and volume down, releasing the power button for a moment when you see the LG logo, then
re-pressing the button to enter recovery, on the following screen select yes both times
Step 7:
(The Following Text other than step numbers is written by and entirely created by jcadduono, and can be also found at his post at https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047)
At this point, you will see the TWRP splash and reach a screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 8 you will be unable to boot!
If you are going to root your device or follow the rest of these steps, then it is safe to swipe right and enable modifications.
Step 8:
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
Step 9:
Please consider backing up your stock boot partition in TWRP before proceeding to the next steps!
Step 10:
If you want to be rooted with SuperSU:
Download the latest SuperSU stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
-or-
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Step 11:
Go to [Reboot] -> [System].
---------End of jcadduono post clip-------------
Now upon reboot, the phone may loop a few times and take up to 5 minutes to complete the process.
When you get into the device, run through setup as normal and you will have SuperSu installed and you will be rooted.
I can not verify Magisk Root Yet but will be attempting to do so soon.
You guys that have the rs988 you may want to ask one of the devs to add support for LOS and custom ROMs. But don't bug them either.
Maybe @King_lilrowrow could help if he has time, although I know he's been busy lately with other things. Hopefully someone will help you guys out. I have no idea how to, otherwise I would try and help. Nice you guys have rootr and twrp finally though.
I am using latest version: RS98810d
Step 4: flash recovery finished without error but cannot Power Off when press "Power" for 10 seconds so I unplug batterry then plugin again and press "Power+Volume down" but it cannot so I tried run command "fastboot boot twrp-3.0.2-1-rs988.img" after re-flash recovery but system shows:
=======================================
D:\adb>fastboot boot twrp-3.0.2-1-rs988.img
downloading 'boot.img'...
OKAY [ 0.554s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.585s
==========================================
AriesTruong said:
I am using latest version: RS98810d
Step 4: flash recovery finished without error but cannot Power Off when press "Power" for 10 seconds so I unplug batterry then plugin again and press "Power+Volume down" but it cannot so I tried run command "fastboot boot twrp-3.0.2-1-rs988.img" after re-flash recovery but system shows:
=======================================
D:\adb>fastboot boot twrp-3.0.2-1-rs988.img
downloading 'boot.img'...
OKAY [ 0.554s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.585s
==========================================
Click to expand...
Click to collapse
After flashing recovery, unplug USB cable and pull battery. Put battery back in, then press and hold volume down (hold volume down entire time) and press and hold the power button, when you see the lg logo, let go of power button for 1 second and then press and hold power button again until it reaches factory reset screen. One at factory reset screen select yes both times and you'll enter TWRP. When using the buttons remember to never let go of the volume down button only the power button for 1 second at lg logo.
You can also try after flashing it:
adb reboot recovery
Note: you must reflash TWRP if you allowed it to boot into os without flashing SuperSU or magisk.
AriesTruong said:
I am using latest version: RS98810d
Step 4: flash recovery finished without error but cannot Power Off when press "Power" for 10 seconds so I unplug batterry then plugin again and press "Power+Volume down" but it cannot so I tried run command "fastboot boot twrp-3.0.2-1-rs988.img" after re-flash recovery but system shows:
=======================================
D:\adb>fastboot boot twrp-3.0.2-1-rs988.img
downloading 'boot.img'...
OKAY [ 0.554s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.585s
==========================================
Click to expand...
Click to collapse
It is stated instead of doing that you turn off the phone and boot into the recovery with power+voldown
jeffsga88 said:
After flashing recovery, unplug USB cable and pull battery. Put battery back in, then press and hold volume down (hold volume down entire time) and press and hold the power button, when you see the lg logo, let go of power button for 1 second and then press and hold power button again until it reaches factory reset screen. One at factory reset screen select yes both times and you'll enter TWRP. When using the buttons remember to never let go of the volume down button only the power button for 1 second at lg logo.
You can also try after flashing it:
adb reboot recovery
Note: you must reflash TWRP if you allowed it to boot into os without flashing SuperSU or magisk.
Click to expand...
Click to collapse
I've followed your steps and I can root successful. Thanks alot
AriesTruong said:
I've followed your steps and I can root successful. Thanks alot
Click to expand...
Click to collapse
No problem! Glad we finally have it on RS988
I've held off on unlocking the bootloader and rooting, since it seems there currently are no ROMs available for the RS988 to flash. Basically you just end up with rooted stock?
FAUguy said:
I've held off on unlocking the bootloader and rooting, since it seems there currently are no ROMs available for the RS988 to flash. Basically you just end up with rooted stock?
Click to expand...
Click to collapse
Yes, currently all you can do is install TWRP and root stock. You can also install some audio mods like viper, but no custom ROMs yet for this version of the device.
Is there a touch TWRP recovery available? Granted I'm not sure if I will be able to flash it, since my power button is broken.
maRioHD said:
Is there a touch TWRP recovery available? Granted I'm not sure if I will be able to flash it, since my power button is broken.
Click to expand...
Click to collapse
Yes it's touch TWRP, can't even remember last time I saw a non-touch based one, been at least 3 years or so. Anyways it's located in the op. As far as flashing it, I believe you can do it without the power button. The issue will be rebooting to recovery after flashing it to flash SuperSU or magisk (if you don't do that or at least get into TWRP before first bit after flashing and delete the recovery from boot.p file, TWRP will be overwritten by default recovery and you have to flash again). While in fastboot mode, after flashing you could try and use:
Code:
adb reboot recovery
Not sure if that will get work or not while in fastboot mode, but something to try since your power button is broke.
Is it work on h860?
Sent from my LG-H860 using Tapatalk
Thank you for the advice. I'll try to give it a go tomorrow and report my success. And ya it's been a while since i have been able to do anything to my phone.
memi_pt said:
Is it work on h860?
Sent from my LG-H860 using Tapatalk
Click to expand...
Click to collapse
No. This is for RS988 only.
maRioHD said:
Is there a touch TWRP recovery available? Granted I'm not sure if I will be able to flash it, since my power button is broken.
Click to expand...
Click to collapse
Yes the twrp in the article is touch
Is the latest build RS98811d? Please confirm..
cheers!
wasabitobiko said:
Is the latest build RS98811d? Please confirm..
cheers!
Click to expand...
Click to collapse
You can always check using LG bridge and use update feature. If just wanting to know because your wanting to root and get TWRP, try and follow the guide. If you're not on latest version you'll know because you won't be able to unlock the bootloader using fastboot. If you can unlock your bootloader, you're good to go.
Here's the link and info for LG bridge and using it to check for updates:
http://www.lg.com/us/support-mobile/lg-LGRS988
jeffsga88 said:
Yes it's touch TWRP, can't even remember last time I saw a non-touch based one, been at least 3 years or so. Anyways it's located in the op. As far as flashing it, I believe you can do it without the power button. The issue will be rebooting to recovery after flashing it to flash SuperSU or magisk (if you don't do that or at least get into TWRP before first bit after flashing and delete the recovery from boot.p file, TWRP will be overwritten by default recovery and you have to flash again). While in fastboot mode, after flashing you could try and use:
Not sure if that will get work or not while in fastboot mode, but something to try since your power button is broke.
Click to expand...
Click to collapse
Adb reboot recovery sadly does not work, i encountered this myself , a replacement power button is quite cheap though
xaviex said:
Adb reboot recovery sadly does not work, i encountered this myself , a replacement power button is quite cheap though
Click to expand...
Click to collapse
Yeah didn't think it would but was worth trying Yeah, looks like a $10-15 fix
Thanks for the reply..
Gonna wait until there's some development happening for this device..
Cheers!
jeffsga88 said:
You can always check using LG bridge and use update feature. If just wanting to know because your wanting to root and get TWRP, try and follow the guide. If you're not on latest version you'll know because you won't be able to unlock the bootloader using fastboot. If you can unlock your bootloader, you're good to go.
Here's the link and info for LG bridge and using it to check for updates:
http://www.lg.com/us/support-mobile/lg-LGRS988
Click to expand...
Click to collapse
I installed Android O DP2 update via OTA yesterday. The phone updated, rebooted to the new build and restarted abruptly and since then has been stuck in a boot loop. The Google logo shows up, goes to the android animation step and then Google logo appears again.
I don't have bootloader unlocked, don't have TWRP and have done OTA updates. I am able to get into the stock recovery mode.
How do I fix this, i.e. make it work in any way without erasing the user data? I don't mind extreme steps (without erasing user data) because I was planning to reflash 7 with unlocking & rooting today.
Try to wipe cache from recovery - in recovery hold volume-down and select "Wipe cache partition". Should do the trick
I tried, didn't work. Had to factory reset in the end. Also opted out of beta
I just read that some people that took the update from certain builds had boot loops due to the update only replacing part of the OS but leaving the 7.x.x system in place causing it to boot loop. I think it was like on android authority or something like that.
Sent from my Nexus 6P using XDA-Developers Legacy app
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
POWER BUTTON + VOLUME DOWN BUTTON
Click to expand...
Click to collapse
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Mavelos said:
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.
citifone said:
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.
Click to expand...
Click to collapse
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.
FAILED (remote: OEM unlock is not allowed)
Mavelos said:
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.
Click to expand...
Click to collapse
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?
citifone said:
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?
Click to expand...
Click to collapse
To unlock you first need to have ticked the allow OEM unlock from developer menu within the OS. It won't work otherwise.
Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here [="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?
Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.
scorneil said:
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.
Click to expand...
Click to collapse
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
Lord Aguacate said:
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?
Click to expand...
Click to collapse
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.
i have the same problem with this, and i cannot unlock it too, is there anyway to unlock this phone?
OTG works Perfect! But.....
Mavelos said:
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.
Click to expand...
Click to collapse
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards
Lord Aguacate said:
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards
Click to expand...
Click to collapse
You're welcome. Get your phone fixed and return to the flashing community.
last night i my phone inside my freezer hehehe and this morning i tried to turn it on, and it pass the google logo boot normally but it only lasted for a few minute and then turn off and bootloop again. so i guess my 6p has a hardware faulty
First of all at the time there is no official way to root redmi note 6 pro
This guide is suitable for the global version and mybe Indian version need to check because in India redmi note 6 pro not available
I'm not responsible if anything happens to your device. If you execute this procedure properly then you shouldn't face any problems. I tried this procedure on Redmi Note 6 pro and it worked flawlessly. I used a computer with Windows 10 insider .
Before you proceed please back up all your important data and make sure that your phone battery is charged >60%
A .Prerequisites
1. Disable driver signature enforcement in Windows
How to do this pls read here: http://en.miui.com/thread-237673-1-1.html
2. Install ADB and Fastboot tools with drivers on Windows
How to do this pls read here: https://forum.xda-developers.com/sho....php?t=2588979
3. Enable "OEM unlocking" and "USB debugging" in your device
a. Enable Developer Options in: Settings/About Phone/MIUI version. Click on MIUI version seven times
b. Now go to: Settings/Additional Settings/Developer Options and check "OEM unlocking" and "USB debugging"
4. Check if your bootloader is locked
a. After successful installation of "ADB and Fastboot" enter the fastboot mode by holding together "Volume Down + Power" and connect your device to your computer via USB cable (best would be the original cable).
b. Go to the folder where you have put the "ADB and Fastboot" and open a command window inside that folder. To do that hold together "Shift + Right Click" on any empty white space inside the folder and then select "Open PowerShell Window Here" or "Open Command Window Here"
c. Enter the terminal command in command line: >>fastboot devices<<
If you don't see your device it means that the drivers weren't installed properly or the device wasn't connected properly. If this happens please reinstall your drivers from Point A. 2. or try these drivers here:
http://xiaomiadvices.com/download-xiaomi-usb-drivers/
d. If you see your device then enter the terminal command in command line: >>fastboot oem device-info<<
If your bootloader is locked, you'll get the following status (or something similar):
…………………………………………………………………….
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.058s]
finished. total time: 0.063s
………………………………………………………………………
If your bootloader is unlocked, you'll get following status (or something similar):
…………………………………………………………………….
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.053s]
finished. total time: 0.055s
………………………………………………………………………
5. Request Permission from Xiaomi to Unlock the Bootloader
a. Create a Mi Account: https://global.account.xiaomi.com/pass/register
b. Sign to Xiaomi and apply for unlocking http://en.miui.com/unlock
You have to give a reason for requesting to unlock the bootloader.
c. Wait for permission. however very few users are reporting a waiting time of up to 7 days . If your request is approved then you should receive a message with following content:
"You've been granted the permission to unlock your device (Mi Account xxxx). Donload Mi Unlock Tool At http://en.miui.com/unlock"
6. Connect your Mi Account to your Device
Go to: Settings/Additional Settings/Developer Options/Mi Unlock status and check "Add account and device"
B . UNLOCKING BOOTLOADER
Attention: Unlocking the bootloader will erase all your data! So please back up your data before you unlock the bootloader
1. You must enable "OEM unlocking" and "USB debugging" as per point A. 3.
2. You must connect your Mi Account with your device as per point A. 6.
3. Download Mi Unlock Tool here: http://en.miui.com/unlock
4. Enter the fastboot mode by holding together "Volume Down + Power" and connect your device to your computer via USB cable (best would be the original cable)
5. Start the Mi Unlock Tool
6. Enter your eMail and your password of your Mi Account
7. Connect you device to your computer and start the unlock procedure
8. Follow the unlock tool instructions until the unlock procedure is finished
9. Reboot your device
In case you get the message, that the unlocking can be done after 360h or 720h then you have to wait for that time to pass
C . INSTALL THE TWRP RECOVERY
your boot loader must be unlocked
1. Download the file https://drive.google.com/file/d/1pgcTalz8rAFWYwP8xYNmNB8uTk-OlAn4/view?usp=drivesdk
2. Extract to your computer desktop or adb folder
View attachment 4651279
3. Reboot your phone to fastboot
4. Go to your computer and connect the phone with computer
5. Open a command prompt and type
6. Fastboot devices if you phone detected in command prompt window it will show numbers of device like in picture
View attachment 4651278
7. now type [ fastboot flash recovery recovery.img] or you can do like this ( fastboot flash recovery and drag recovery file to command prompt) and hit enter
View attachment 4651277
8. now press volume+ and power at the same time until your device boot to TWRP
9. After successfully booted TWRP now flash View attachment 4651280 and wipe data
10. Enjoy your flashing
D . ROOT YOUR PHONE
1 .Donwload latest Magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Put Magisk into external sd card because decryption is not for now
2 .Flash Magisk
3 .Restart your smartpphone
4 .Now set up you phone
5 .Done enjoy
telegram :- https://t.me/tulipofficial
I have read about some problems with ported (from whyred ?) twrp and MIUI 10 on RN6 pro,
but I could not remember where
so there are no problems ??
Perfect
perfect with MIUI 10 ?
phonepete said:
perfect with MIUI 10 ?
Click to expand...
Click to collapse
Yes
...
Great wanna try it..?
twrp is ok now
are there any possibility to re-lock?
hi! I was trying to unlock my bootloader but I have an error at 99% with a message in chinese that it says something like: "The phone has not been used for the specified time and cannot be unlock"
Someone has the same problem or knows the solution?
Very thanks
I have problems with this twrp.
When i enter in recovery it ask for a password to decrypt the data storage. I tried everything but i don't know how to decrypt, So i can't mount Internal and SD Partition and neither root my phone
I tried to wipe data, but even in this case i can't navigate into internal storage.
Should i wait for an official TWRP?
raexan said:
hi! I was trying to unlock my bootloader but I have an error at 99% with a message in chinese that it says something like: "The phone has not been used for the specified time and cannot be unlock"
Someone has the same problem or knows the solution?
Very thanks
Click to expand...
Click to collapse
You have to apply for unlock and then wait for 14 days.
Has anyone successfully unlock other LTE bands after root? I have the global version but it does not have LTE band 12 & 17 which are critical for AT&T
Can you please tell me if this TWRP edition can see the SD card ?
Thanks
Password required in mount operation
Just after entered TWRP is asking for a password to Decrypt Data.
Tried all password for my account with no success.
I am not able to actively root my phone.
Any suggestion?
Many thanks
toni.pace said:
Just after entered TWRP is asking for a password to Decrypt Data.
Tried all password for my account with no success.
I am not able to actively root my phone.
Any suggestion?
Many thanks
Click to expand...
Click to collapse
in that menu I think that you can press cancel and enter in the menu of recovery
Enviado desde mi Redmi Note 6 Pro mediante Tapatalk
same thing happened to me .. as I enter to the TWRP, I have being asked for the pin unlock password, which is not the one I have previously set on the miui. I rebooted to system, removed the pin protection and yet again it didn't helped with the TWRP asking the pass .. if I hit the cancel, I enter to the TWRP yet no any storage is mounted and can't do nothing further. So for a lot of us this guide is not 100% good.
clemenza011 said:
same thing happened to me .. …..
Click to expand...
Click to collapse
I was finally able to root the phone, but i don't know exacly how.
BTW
My TWRP is V.3.2.3 v3 Special Edition mod by Mr-r00t
In TWRP just click "Cancel" to password request, then you should be able to see the content of the Sdcard.
From there i flashed "Disable_Dm-Verity_ForceEncrypt_09.02.2018.zip" and "Magisk-v18.0(18000).zip"
Rebooted in system and did some setup in Magisk app
I did install also "Root checker basic"," Root Browser" , "Titanium Backup" from PlayStore.
In "Root checker basic" installed BusyBox too.
Finally root is working, and i was able to copy a new "Hosts" file in \system\etc, just to get rid of annoying ads .
Good luck
Right, I managed the same last eve *with the other recovery to be honest) .. root after magisk works, and tapatalk is clean after adaway was installed .. yet my data is encrypted and I cannot for instance do the full backup from the twrp. I am concerning format data, as I understood that it should remove the encryption, yet I am not sure would I have to flash something (ROM?) after I format the data, or I could just reboot to the system, as is?
magisk manager shows ticked 'preserve force encryption' and unticked 'preserve avb2.0/dm-verify', I suppose that such situation corresponds to the fact that I am encrypted, and I have flashed disable_dm_verity, just like being said.
also, our (RN6PRO) devices have activated anti-roll-back (mine arb index is 4) so there should be no much space for mistakes.
clemenza011 said:
Right, I managed the same last eve *with the other recovery to be honest) .. .
Click to expand...
Click to collapse
Sorry i cannot help with that question about format DATA , my skills are limited.
My Magix manager shows the same " ticked 'preserve force encryption' and unticked 'preserve avb2.0/dm-verify', "
I am ok with my phone now, and don't want the risk to loose everything or to be forced reinstall all.
I hope someone else could answer this question.
Have a nice day.