Related
Quick question.
I flashed the radio in my 6p.
Can I install the latest OTA Android update over that or do I need to go back to stock?
Also my phone is unlocked, does it need to be locked?
The radio flash didn't solve my problems.
Anyone?
Which radio did you flash?
2.50
Crakinarse said:
2.50
Click to expand...
Click to collapse
There's a lot about your config you haven't told us. Since you're staying your phone is "unlocked", I can only assume you mean the bootloader is unlocked, and you've got a custom recovery (TWRP) installed. If this is indeed the case, then no you should not take any "OTA" as any changes to "stock" (like a custom recovery) will cause it to fail.
You can, however, wipe and flash new Roms through twrp, or with an unlocked bootloader you can download the latest image from Google's sure for our device and flash that through fastboot (Google search to find tutorials on this there's a million of them). Be aware this will wipe EVERYTHING out on the device and reset it back to defaults (your data, recovery, etc.)
ohlin5 said:
There's a lot about your config you haven't told us. Since you're staying your phone is "unlocked", I can only assume you mean the bootloader is unlocked, and you've got a custom recovery (TWRP) installed. If this is indeed the case, then no you should not take any "OTA" as any changes to "stock" (like a custom recovery) will cause it to fail.
You can, however, wipe and flash new Roms through twrp, or with an unlocked bootloader you can download the latest image from Google's sure for our device and flash that through fastboot (Google search to find tutorials on this there's a million of them). Be aware this will wipe EVERYTHING out on the device and reset it back to defaults (your data, recovery, etc.)
Click to expand...
Click to collapse
All I did was unlock the bootloader and
fastboot flash radio image.
That is it.
I did not install a custom recovery.
Crakinarse said:
All I did was unlock the bootloader and
fastboot flash radio image.
That is it.
I did not install a custom recovery.
Click to expand...
Click to collapse
If you didn't flash a custom recovery you can download the ota without any issues. This is assuming that everything is still completely stock about your device. You can upgrade and downgrade your radio as you wish. I would advise to keep your bootloader unlocked so you can fix any problems if you ever have any.
Hello,
after I've unlocked the bootloader can I still get OTA updates?
I'll just be on stock ROM with root. I also make a backup with nothing on except TWRP.
Lets hope so
LanceM said:
Lets hope so
Click to expand...
Click to collapse
have you tried it?
Yes you'll be able to get new updates with unlock bootloader.
DrakenFX said:
Yes you'll be able to get new updates with unlock bootloader.
Click to expand...
Click to collapse
Can you elaborate on this? The last I heard unlocking the bootloader (using the official procedure) stops OTA. Has this changed ?
mh127 said:
Can you elaborate on this? The last I heard unlocking the bootloader (using the official procedure) stops OTA. Has this changed ?
Click to expand...
Click to collapse
I never said Official getting OTA's , but i believe this is going to change staring with the new Unlock Bootloader procedure.
DrakenFX said:
I never said Official getting OTA's , but i believe this is going to change staring with the new Unlock Bootloader procedure.
Click to expand...
Click to collapse
OK, but AFAIK even with the unofficial unlock (with TWRP and root) the OTA will fail - unless you unroot and go back to locked stock bootloader. Correct me if I am wrong.
mh127 said:
OK, but AFAIK even with the unofficial unlock (with TWRP and root) the OTA will fail - unless you unroot and go back to locked stock bootloader. Correct me if I am wrong.
Click to expand...
Click to collapse
In my experience, what makes the difference - so far - is the recovery. Official ZTE updates and ROMS only flash through the stock recovery.
Unlocked bootloader has made no difference to me.
mh127 said:
OK, but AFAIK even with the unofficial unlock (with TWRP and root) the OTA will fail - unless you unroot and go back to locked stock bootloader. Correct me if I am wrong.
Click to expand...
Click to collapse
If you try to flash Official OTA yes will fail, cuz isn't modded to skip partitions check.
DrakenFX said:
If you try to flash Official OTA yes will fail, cuz isn't modded to skip partitions check.
Click to expand...
Click to collapse
This is getting confusing. "Getting OTA updates" (as OP asks) usually means that the update installs "on its own" by tapping notification rather than flashing via recovery, which is a bit more complicated process.
So back to the OP question: With root and TWRP can one get over-the-air official updates from ZTE without going to the recovery manually? I believe the answer to that is NO.
That said, there is probably a work around in getting the update, probably by manually flashing partitions that have changed in the update.
Is this right?
mh127 said:
This is getting confusing. "Getting OTA updates" (as OP asks) usually means that the update installs "on its own" by tapping notification rather than flashing via recovery, which is a bit more complicated process.
So back to the OP question: With root and TWRP can one get over-the-air official updates from ZTE without going to the recovery manually? I believe the answer to that is NO.
That said, there is probably a work around in getting the update, probably by manually flashing partitions that have changed in the update.
Is this right?
Click to expand...
Click to collapse
Well OPs Question actually was if OTA Updates are possible with unlocked boot-loader...
Root and TWRP is a whole different scenario and won't work with OTA for sure as OTA needs stock recovery and will check for unmodified system (not rooted)...
But if you are on stock with unlocked bootloader you should get notified about OTAs (as until now it did not check for bootloader lock status, but that could change in future) although I don't know if it will install correctly
Gachmuret said:
Well OPs Question actually was if OTA Updates are possible with unlocked boot-loader...
Root and TWRP is a whole different scenario and won't work with OTA for sure as OTA needs stock recovery and will check for unmodified system (not rooted)...
But if you are on stock with unlocked bootloader you should get notified about OTAs (as until now it did not check for bootloader lock status, but that could change in future) although I don't know if it will install correctly
Click to expand...
Click to collapse
OP mentioned that he used TWRP to make a backup, I assumed he has replaced stock recovery with TWRP, but that may not necessarily be the case.
If your device has an bootloader that was unlocked "unofficially" (either via sideloading the official unlock method or DrakenFX & Unjustifieddev's method), but is still completely stock (stock System, stock Boot, stock Recovery, stock everything besides the unlocked bootloader), you can still receive and apply OTAs. However, if you changed any of the partitions, like boot.img (root), recovery.img (TWRP), system.img (changes to system), you will still receive the OTA, but you won't be able to apply it, the update will fail. If you went through the official bootloader unlocking process, which involved you submitting a form to ZTE with your device's IMEI, you would no longer be able to receive OTAs.
What I did was sideload the official B20_Boot on by B20 device, unlocked my bootloader, flashed TWRP, flashed the TWRP Stock B20 dumps that were posted here on XDA, and reflashed stock recovery. This made my device completely stock B20 besides the unlocked bootloader. I then applied the official B27 OTA update, and it installed fine. I then reflashed TWRP (since my bootloader was still unlocked) and re-rooted my device.
If a new update comes out, I can just reflash the stock B27 TWRP dump posted here on XDA, reflash stock recovery, (if needed, reflash stock fastboot), and apply OTA.
xtermmin said:
...
What I did was sideload the official B20_Boot on by B20 device, unlocked my bootloader, flashed TWRP, flashed the TWRP Stock B20 dumps that were posted here on XDA, and reflashed stock recovery. This made my device completely stock B20 besides the unlocked bootloader. I then applied the official B27 OTA update, and it installed fine. I then reflashed TWRP (since my bootloader was still unlocked) and re-rooted my device.
If a new update comes out, I can just reflash the stock B27 TWRP dump posted here on XDA, reflash stock recovery, (if needed, reflash stock fastboot), and apply OTA.
Click to expand...
Click to collapse
So, with this procedure, do you lose all the app installations/other customizations? I believe that all of the application data is on a non-system partition (/data?) but did you need to go through all of the setting up of the phone after you did the upgrade this way?
rayman2k1 said:
So, with this procedure, do you lose all the app installations/other customizations? I believe that all of the application data is on a non-system partition (/data?) but did you need to go through all of the setting up of the phone after you did the upgrade this way?
Click to expand...
Click to collapse
Yes. Unlocking the bootloader does a factory reset, and doing a TWRP restore of a stock image (which overwrites your current partitions) overwrites what you had before.
EDIT: Actually, I think Internal Storage gets erased as well, but your microSD card will be fine.
xtermmin said:
Yes. Unlocking the bootloader does a factory reset, and doing a TWRP restore of a stock image (which overwrites your current partitions) overwrites what you had before.
EDIT: Actually, I think Internal Storage gets erased as well, but your microSD card will be fine.
Click to expand...
Click to collapse
Hmm, had guessed as much. I knew the bootloader unlocking did a wipe, but was hoping that recovery-flashing would do a backup/restore, as if the update had been applied through the in-ROM update procedure. Unless the OTA process only gets deltas and flashes them, leaving fs intact.
rayman2k1 said:
Hmm, had guessed as much. I knew the bootloader unlocking did a wipe, but was hoping that recovery-flashing would do a backup/restore, as if the update had been applied through the in-ROM update procedure. Unless the OTA process only gets deltas and flashes them, leaving fs intact.
Click to expand...
Click to collapse
Yeah, the OTA doesn't straight-up replace partitions, it checks and patches the existing partitions, so if a partition has been changed, the OTA install will fail.
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. Reflash TWRP and SuperSU if needed
Step 10. Enjoy!
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Skwerl23 said:
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. enjoy!
Click to expand...
Click to collapse
Can TWRP be installed afterwards or will it come back when TWRP is installed?
Michalko5896 said:
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Click to expand...
Click to collapse
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Skwerl23 said:
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Click to expand...
Click to collapse
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
I feel your frustration. There is this forum
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
I used the hard brick fix to go back to 3.5.1? I let the system update to 3.5.4. Go into developer settings and check allow oem unlock. Went into bootloader and oem unlocked. It will erase everything. Downloaded and put the OTA patch(940gb~not full) and supersu 2.79 on the device somewhere and did a local update with the patch through stock recovery. Went into bootloader and flashed TWRP 3.0.2.0(not 3.0.3.0). Do not exit bootloader. In bootloader I fastboot BOOT the 3.0.2.0 TWRP(3.0.3.0 would not boot up and screwed the dm-verity). If it(3.0.2.0) doesn't want to boot then quickly hold the power button in and wait till it starts rebooting and go into recovery menu option). Swipe to allow modifications and flash the supersu 2.79 that was placed on the device somewhere. This worked for me and no dm-verity error with f2fs.
Long process but it worked.
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
PaKii94 said:
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
What causes the dm-verity issue in the first place?
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
saberzaid said:
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
Click to expand...
Click to collapse
Yes to first. No to second, It will try but will fail.
Sent from my ONEPLUS A3000 using Tapatalk
Mine is unlocked and rooted. The update failed. Then it redownloaded the full 1.4gb. That's how I found the URL. Then it flashed fine but brought recovery to stock and wiped root. Had to use the toolkit to get TWRP and root back.
So yes, even rooted gets the update
noahvt said:
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Click to expand...
Click to collapse
I did a system restore previously and it set system to ext4. Maybe that's why I didn't have issues.
This dm-verity issue could be showing the instability of f2fs. Hmmm
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
jejemc said:
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
Click to expand...
Click to collapse
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
lanbingxuanyi said:
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
Click to expand...
Click to collapse
Hello, I am going under the beta with the message in red dm-verity for the removed I returned under original rom then I handed twrp then rom custom
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
PaKii94 said:
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
Click to expand...
Click to collapse
I'm running 7.0 stable, unlocked bootloader and dm-verity warning. Android Pay still functions with the workaround.
I want to make a clean Install of factory image (Android 8.0 Oct) on my Nexus 6P with TWRP.
Should wipe Dalvik, Data, System and Internal storage, then move the stock zip file (That I downloaded from google's web) from my computer to my phone and just install in TWRP? Will it work?
Device is unrooted, only has an open boot loader, I just want to make a clean install of Android 8.0
If you wipe your internal all your downloads and your factory image are gone.
Sure you can flash the unpacked *.img with twrp, but don't try to flash the bootloader or radio with twrp.
If you really want a clean start and wipe everything, then you should flash the factory image with fastboot. This will update your bootloader and radio too.
coremania said:
If you wipe your internal all your downloads and your factory image are gone.
Sure you can flash the unpacked *.img with twrp, but don't try to flash the bootloader or radio with twrp.
If you really want a clean start and wipe everything, then you should flash the factory image with fastboot. This will update your bootloader and radio too.
Click to expand...
Click to collapse
Hi coremania, I have a few questions towards this method.
1. If the stock image is stored in either external SD card OR USB OTG, even then will there be any problem installing the the stock rom back using TWRP?
2. If the boot loader is unlocked, should one has to re-lock it first before reinstalling the stock rom either thru' TWRP or thru' Fasboot commands?. and finally,
3. Is it not advisable to flash the stock rom from the full factory image using TWRP rather than Fastboot?
(As I think it is easier to flash thru TWRP than typing those ADB commands in Fastboot).
Thank you for your inputs.
AndroMani said:
Hi coremania, I have a few questions towards this method.
1. If the stock image is stored in either external SD card OR USB OTG, even then will there be any problem installing the the stock rom back using TWRP?
2. If the boot loader is unlocked, should one has to re-lock it first before reinstalling the stock rom either thru' TWRP or thru' Fasboot commands?. and finally,
3. Is it not advisable to flash the stock rom from the full factory image using TWRP rather than Fastboot?
(As I think it is easier to flash thru TWRP than typing those ADB commands in Fastboot).
Thank you for your inputs.
Click to expand...
Click to collapse
If you decide to flash and test some stuff the bootloader should be always unlocked. If anything will went wrong and your bootloader is locked you're mostly f***ed. Never relock your bootloader until you want to sell your device.
I mostly use flashfire to flash stock and custom roms, TWRP is ok too, but it's easier to keep root and TWRP with flashfire by flashing stock images. Do not flash bootloader and radio with flashfire, never ever !!! There are TWRP flashable zips for bootloader and radio here on XDA, you only should use these with TWRP, but the safe way for bootloader and radio is fastboot for sure. Fastboot is the safest way for flashing stock,
but not absolutely necessary, you have to decide this for yourself.
Edit: to your first question, I never flashed with USB otg on the n6p, but I think yes it should be fine.
I hope someone here can help answer this question. I also want to flash factory image version 8.1.0 on my nexus 6P. But somehow my phone is not recognized by any computers I tried to plug it in. When I plug in the usb cable to the phone, it doesn't pop up the usb notification to choose MTP for file transfer. Then I try with Developer tab in Settings to choose it manually (USB debugging is enable) but it still doesn't work. My laptop has been updated with android usb drivers and other stuffs. I have a second phone (Oneplus 1) and it's recognized by my laptop the moment I plug it in. Please suggest any solutions to fix this. Thanks everyone.
sinjok said:
I hope someone here can help answer this question. I also want to flash factory image version 8.1.0 on my nexus 6P. But somehow my phone is not recognized by any computers I tried to plug it in. When I plug in the usb cable to the phone, it doesn't pop up the usb notification to choose MTP for file transfer. Then I try with Developer tab in Settings to choose it manually (USB debugging is enable) but it still doesn't work. My laptop has been updated with android usb drivers and other stuffs. I have a second phone (Oneplus 1) and it's recognized by my laptop the moment I plug it in. Please suggest any solutions to fix this. Thanks everyone.
Click to expand...
Click to collapse
Check your cable, or try a different with different port.
In the Dev options you can reset the debugging options, i guess a reboot is necessary afterwards.
coremania said:
If you decide to flash and test some stuff the bootloader should be always unlocked. If anything will went wrong and your bootloader is locked you're mostly f***ed. Never relock your bootloader until you want to sell your device.
I mostly use flashfire to flash stock and custom roms, TWRP is ok too, but it's easier to keep root and TWRP with flashfire by flashing stock images. Do not flash bootloader and radio with flashfire, never ever !!! There are TWRP flashable zips for bootloader and radio here on XDA, you only should use these with TWRP, but the safe way for bootloader and radio is fastboot for sure. Fastboot is the safest way for flashing stock,
but not absolutely necessary, you have to decide this for yourself.
Edit: to your first question, I never flashed with USB otg on the n6p, but I think yes it should be fine.
Click to expand...
Click to collapse
Thank you for the clarification. So, far I have not faced a situation to flash my custom recovery either thru' TWRP or thru Fastboot. Instead, I am using my Nandroid backups taken from TWRP and using it to restore my system after I try a custom rom OR upgrade my system with the latest Magisk version for a systemless root. So far there are no issues. But, I wanted to be aware of the methods to go back to stock (without any user installed apps/data) if need be. I read in some forums that we need to re-lock the unlocked bootloader if we want to go back to stock rom using fastboot. Otherwise, the system will not be installed alright and might cause a bootloop.
That's why I wanted to clarify.
Thanks again for your inputs.
AndroMani said:
Thank you for the clarification. So, far I have not faced a situation to flash my custom recovery either thru' TWRP or thru Fastboot. Instead, I am using my Nandroid backups taken from TWRP and using it to restore my system after I try a custom rom OR upgrade my system with the latest Magisk version for a systemless root. So far there are no issues. But, I wanted to be aware of the methods to go back to stock (without any user installed apps/data) if need be. I read in some forums that we need to re-lock the unlocked bootloader if we want to go back to stock rom using fastboot. Otherwise, the system will not be installed alright and might cause a bootloop.
That's why I wanted to clarify.
Thanks again for your inputs.
Click to expand...
Click to collapse
You don't need to ever relock your bootloader. If you want to try stock and use TWRP try SuperXe 8.1. It's just flaahable stock with some extras you can opt out of your not intereseted.
AndroMani said:
Thank you for the clarification. So, far I have not faced a situation to flash my custom recovery either thru' TWRP or thru Fastboot. Instead, I am using my Nandroid backups taken from TWRP and using it to restore my system after I try a custom rom OR upgrade my system with the latest Magisk version for a systemless root. So far there are no issues. But, I wanted to be aware of the methods to go back to stock (without any user installed apps/data) if need be. I read in some forums that we need to re-lock the unlocked bootloader if we want to go back to stock rom using fastboot. Otherwise, the system will not be installed alright and might cause a bootloop.
That's why I wanted to clarify.
Thanks again for your inputs.
Click to expand...
Click to collapse
I can't confirm the relock and unlock method to go back to stock. Senseless to me.
I really just want to root stock. I have the Boost Mobile Perry.
guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
Yes. Install twrp, flash no verity, format data (to remove encryption) flash magisk. Some people have said if you took the last security update, you may have to patch the boot.img with magisk manager then flash the patched boot.img in fastboot or twrp to root. And will likely need the latest magisk beta (16.4).
I really don't care about encryption.
guitardoc64 said:
I really don't care about encryption.
Click to expand...
Click to collapse
You have to remove encryption.
Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.
guitardoc64 said:
Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.
Click to expand...
Click to collapse
Don't neglect to backup EVERYTHING in TWRP before doing ANYTHING (and store those images off-device!). Strongly suggest booting a TWRP image to perform this task vs. installing/flashing to the recovery partition, especially if interested in preserving/restoring OTA capability at a future time.
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.
guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
Welcome to the 5% club which is probably generous based on the number of noobs (and veterans) who neglect to image their device before messing with core components. Of course that figure may be skewed as those that do take proper precautions rarely write posts that begin with "help!" and have no path back to the prior working state.
Also, resist the temptation to flash a custom recovery (twrp) vs booting from fastboot if you want to accept accept future OTA updates or roll back to pure stock. While restoring stock recovery is possible it certainly complicates the process. Can always revisit the decision at later time.
guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
Don't have a definitive answer on the latest firmware. Suggest going through the above steps first. If no joy it's a simple matter to patch/flash boot.img .
You are wise to boot a twrp image vs flashing over stock recovery. Simplifies fallback should the need arise. Don't neglect to backup stock and store off device (or at least on a SD card).
davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
For .3, format data to remove encryption.
But the rest should work. If not, you have to download the current firmware ( the version you're on) if you can find it. Extract the boot.img from it. Then use magisk manager to patch it. And use fastboot to flash the patched boot.img
i have the moto e4 mkt which no verity version do i have to flash ?
Rafasama said:
i have the moto e4 mkt which no verity version do i have to flash ?
Click to expand...
Click to collapse
You shouldn't need a no-verity any longer. Newer versions of magisk should take care of it. Just TWRP, and magisk.
madbat99 said:
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.
Click to expand...
Click to collapse
Hello, I am running a Samsung Galaxy J5 Prime at the moment, a friend told me I must flash no verity.zip after flashing TWRP because of the verification and I tried making a backup if the entire rom but it failed so I need to confirm, do I factory reset my device then flash the no verity file or I flash the no verity file and then factory reset the device??
I know it's an old thread but a quick reply would be awesome