First thing: before using this How-to guide. *I am not responsible for any data lost,bricked phones,or anything related to your Honor 8*
I am writing this from my own experience updating. Your mileage may vary.
Notes: I've heard reports that flashing stock recovery and stock boot.img from fastboot(instead of twrp) help to have a higher chance of getting past erecovery. Let me know if it helps.
To follow this guide you should be rooted,TWRP installed and using the B360 version while having the OTA available for B385 for FRD-L04.
Ok, lets get started.
Code:
Step 1:
Make backups. I made backups with HiSuite and within TWRP. Just in case.
Code:
Step 2:
Reboot into Recovery. I used TWRP v3.1.0-3 for steps outlined.
[URL="https://drive.google.com/open?id=0B0uzUjmZ9bI6eVBlWm1ZSE56Yzg"]Download for TWRP IMG[/URL]
Code:
Step 3:
You will need to [I]Unroot[/I]. Whatever method you want to use, do it,
but, I used the UnSU zip by Osmosis
[URL="https://drive.google.com/open?id=0B0uzUjmZ9bI6SXlmenpVM3Z4b0E"]Link for .zip[/URL]
Flash this .zip. Do not Reboot.
Code:
Step 4:
We need to flash the stock boot.img and the stock recovery.img. (This likely needs to be done in
Fastboot versus recovery)
[URL="https://drive.google.com/open?id=0B0zE1Kk8sIB6MDF6SmEyaXYzVTg"]Stock Recovery.img[/URL]
[URL="https://drive.google.com/open?id=0B0zE1Kk8sIB6NlIzOWJkQ1Z1OHc"]Stock Boot.img[/URL]
Now, Move these somewhere on your
phone (internal storage/SDcard) and go to Install from TWRP. (Many people
report success doing this step in Fastboot)
Locate files, Probably have to switch to Images.
Flash boot.img to [I]Boot[/I] and recovery.img to [I]Recovery[/I]
Code:
Step 5:
Shutdown phone from TWRP. Make sure when you turn your phone
back on, don't have it connected to USB.
Code:
Step 6:
Power up phone
Code:
Step 7:
You should be able to boot like normal to your previous phone configuration,
except now you have stock boot and stock recovery
and should be able to receive/install OTA.
NOTE: If you have issues with booting and it will only boot to
eRecovery, try hitting[I][B]Shutdown[/B][/I] and performing
a cold boot. If that still doesn't workthen you will have to run
through the prompts and recovery B360.That's why we have
backups as step 1
Code:
Step 8:
Once phone is booted, go to Settings-> System Update ->
Perform the update to OTA B385 like normal
Code:
Step 9:
We just need to get into fastboot mode now and flash TWRP
like we have done on B360 and previous.
Connect phone with USB debugging enabled and open cmd prompt.
to make sure device is connected
Code:
[I]adb devices[/I]
open directory you need
Code:
[I]cd c:\whatever the path you saved the TWRP.img[/I]
Reboot phone to bootloader
Code:
[I]adb reboot bootloader[/I]
Flash TWRP
Code:
[I]fastboot flash recovery twrp-3.1.0-3-frd.img[/I]
Code:
[I]fastboot reboot[/I]
Code:
Step 10:
After phone reboots. We need to get into the TWRP recovery we just flashed.
Whatever method you want to use. I just shutdown and used
power up+power button.
Code:
Step 11:
we need to flash Magisk to get root.[URL="https://drive.google.com/open?id=0B0uzUjmZ9bI6WFMwTUIwd21rX2s"]Magisk[/URL]
Place .zip on phone Sdcard or internal
in TWRP -> install -> locate Magisk flashable zip
[I]flash and reboot[/I]
I think that covers it. You should be updated to the latest B385 OTA and have Magisk root.
Sorry if this was long.
A ton of credit to @Telperion for helping and access to the correct files to get this completed
Thanks I followed your procedure and everything worked as described!
However in TWRP now if I try to remove certain system apps (e.g., Health) I get "Cannot remove system app. Failed to locate the app". Am I the only one with this issue?
Thanks, is it working with B380 too ?
cococchio said:
Thanks I followed your procedure and everything worked as described!
However in TWRP now if I try to remove certain system apps (e.g., Health) I get "Cannot remove system app. Failed to locate the app". Am I the only one with this issue?
Click to expand...
Click to collapse
I haven't tried to remove apps from twrp. I just freeze them with titanium backup. Or just uninsall within system if possible.
Sent from my FRD-L04 using Tapatalk
volginster said:
Thanks, is it working with B380 too ?
Click to expand...
Click to collapse
Which model of honor 8?
Sent from my FRD-L04 using Tapatalk
Wesley32 said:
I haven't tried to remove apps from twrp. I just freeze them with titanium backup. Or just uninsall within system if possible.
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
Silly me! yes I was able to remove the health app directly from system
Sent from my FRD-L04 using Tapatalk
I told myself that I would not do any modding on my phone until a fully stable custom ROM comes up. But right now I felt the urge to do this because of Magisk and the new OTA. Thanks OP. I'll try it.
---------- Post added at 06:19 PM ---------- Previous post was at 05:34 PM ----------
Oh man. Phone only boots to erecovery.
adriansticoid said:
I told myself that I would not do any modding on my phone until a fully stable custom ROM comes up. But right now I felt the urge to do this because of Magisk and the new OTA. Thanks OP. I'll try it.
---------- Post added at 06:19 PM ---------- Previous post was at 05:34 PM ----------
Oh man. Phone only boots to erecovery.
Click to expand...
Click to collapse
Try shutdown and cold booting. Otherwise, finish steps in erecovery and then just restore apps. Internal data should still be intact. Only system is wiped.
Sent from my FRD-L04 using Tapatalk
Wesley32 said:
Try shutdown and cold booting. Otherwise, finish steps in erecovery and then just restore apps. Internal data should still be intact. Only system is wiped.
Click to expand...
Click to collapse
Got it sorted now and downloading B385.
I know u can't successfully install ota update while rooted/custom recovery, but will the update still arrive via ota if rooted, or will it not even show up till phone is unrooted? Reason I ask is because the vast majority seems to have already received this update, where as I have been waiting and waiting... Wondered if maybe it wasn't showing up yet because I wasn't unrooted and/or not running stock recovery/boot
Sent from my HUAWEI FRD-L04 using XDA Labs
BigBrad75 said:
I know u can't successfully install ota update while rooted/custom recovery, but will the update still arrive via ota if rooted, or will it not even show up till phone is unrooted? Reason I ask is because the vast majority seems to have already received this update, where as I have been waiting and waiting... Wondered if maybe it wasn't showing up yet because I wasn't unrooted and/or not running stock recovery/boot
Click to expand...
Click to collapse
Yes. 3 days ago I was still with B360 and SuperSU and my phone was notifying me of a B385 update. Until I came along to this guide. Now I'm in B385 and Magisk.
Sent from my Honor 8 using XDA Labs
Is there any way to force the update ? I'm on Att go plan is South Dakota and I'm impatient lol...
adriansticoid said:
Yes. 3 days ago I was still with B360 and SuperSU and my phone was notifying me of a B385 update. Until I came along to this guide. Now I'm in B385 and Magisk.
Click to expand...
Click to collapse
Thanks that's what I needed to know!
apocrasy said:
Is there any way to force the update ? I'm on Att go plan is South Dakota and I'm impatient lol...
Click to expand...
Click to collapse
Haha I misread that the first time, I thought you had said that u were in South Dakota and you were important!! =D
Sent from my HUAWEI FRD-L04 using XDA Labs
I just put my location in there because I'm not sure how they decide how they update . Is it by region or carrier or both ? I know some MN people got there updates...
My phone won't boot past the boot screen after flashing the stock boot and recovery.
*Edit* I had to do a factory reset via the stock recovery and it booted up.
Same procedure for the FRD-L19?
BonezMontana said:
My phone won't boot past the boot screen after flashing the stock boot and recovery.
*Edit* I had to do a factory reset via the stock recovery and it booted up.
Click to expand...
Click to collapse
This happened to me as well, but, thankfully the recovery only wipes the system. Doesn't wipe actual data partition.
Sent from my FRD-L04 using Tapatalk
Psy87 said:
Same procedure for the FRD-L19?
Click to expand...
Click to collapse
Is this the same phone just the 64gb?
Sent from my FRD-L04 using Tapatalk
So when I tried flashing it it kept giving me an error and won't download. Tried both sideloading it from my PC and downloading it straight to my device. Both gave me the error and didn't install magic
natethegreat1487 said:
So when I tried flashing it it kept giving me an error and won't download. Tried both sideloading it from my PC and downloading it straight to my device. Both gave me the error and didn't install magic
Click to expand...
Click to collapse
What did you do before that?
Sent from my Honor 8 using XDA Labs
Related
https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app
Jexx11 said:
What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it
alex94kumar said:
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it
Click to expand...
Click to collapse
That's odd, I used the TWRP version in Hashcodes thread, flashed with the Motorola Fastboot. When I went to restart from TWRP it asked me if I wanted to root and I let it. Now I'm rooted.
Sent from my XT1060 using Tapatalk
Stranger things have happened, I guess. Regardless of which method you use, you'll end up with root either way
This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.
chaoslimits said:
This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.
Click to expand...
Click to collapse
same here but i have 85% battery
so i guess we will have to re-flash and push the supersu
The only advice I can give to either of you is to try reflashing TWRP again
Actually i did it again and it worked, guess we can't just skip steps.
Sent from my Nexus 7 using Tapatalk 4
Well im glad it worked out for you in the end
It worked after I charged the phone.
Thanks
Sent from my XT1060 using Tapatalk 2
How do I return my phone to default in order to install OTA
I have already flashed the stock recovery but my phone is still rooted. Do I need to unroot? I tried installing the OTA and it said it failed.
This method should work on any version with with an unlocked bootloader such as Sprint and T-Mobile - not just the dev editions.
alex94kumar said:
https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
Click to expand...
Click to collapse
Anyone knows how to do UNROOT if I used this method to get root?
I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.
1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.
s0nic69 said:
1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.
Click to expand...
Click to collapse
If we're already on 4.4, how do we know if we have the first OTA?
Thanks
chillmeow said:
I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.
Click to expand...
Click to collapse
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
---------- Post added at 03:45 PM ---------- Previous post was at 03:28 PM ----------
doctor_evil said:
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
Click to expand...
Click to collapse
OK I feel like an idiot. I just noticed that in the fastboot screen it shows that it's locked. I thought developer phones were unlocked by default?
ok after unlocking it I was able to install twrp recovery with no problems
Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?
pphi said:
Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?
Click to expand...
Click to collapse
Are you selecting recovery with the power button or the volume up button? Volume up selects. If you use the power button, the phone just boots normally.
I just received a notification on my 6P saying that the january security update is available. The thing is that I'm rooted with systemless root, xposed, EX Kernel and TWRP. Can I update using the update button?
With systemless I believe you should be able to.
I just posted about this too....no one got back to me. I got the same message and have more or less the same setup as you. I'm scared to reboot and update lol
Pain-N-Panic said:
I just posted about this too....no one got back to me. I got the same message and have more or less the same setup as you. I'm scared to reboot and update lol
Click to expand...
Click to collapse
No.
If you have TWRP installed you will not be able to take an OTA.
Why bother?
Just flash what you want.
Ok, so if I reboot and my phone tries to install the OTA, what happens?
I have exact the same setup and tried to let the OTA install but in TWRP it aborted because of the mismatching kernel I think (at least it said it expected the generic device name Google angler etc and in stead it found Huawei nexus 6P Dees-troy etc)
So no harm is done when you try to update other than it doesn't work
But as far as I know when using xposed there's no use for systemless root because xposed is changing system partition
This update message won't go away. Can I flash it myself through TWRP with Xposed installed?
You cannot use twrp with an OTA. You need stock recovery. Also I believe that Xposed modifies /system and that in itself would prevent the OTA with stock recovery.
dratsablive said:
You cannot use twrp with an OTA. You need stock recovery. Also I believe that Xposed modifies /system and that in itself would prevent the OTA with stock recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I used step 10 from this guide then re-flashed TWRP, Super Su, ElementalX and everything seems to be fine, no data loss.
Pain-N-Panic said:
Ok, so if I reboot and my phone tries to install the OTA, what happens?
Click to expand...
Click to collapse
Nothing happens. it'll just fail to flash the update. It'll reboot to twrp, attempt to flash the update, and it'll fail the flash. So it just won't flash. Then you'll just reboot the system and nothing will be changed. I think you can flash these minor changes, but if you try to flash a major update through OTA it won't work with out stock recovery because that's part of the flash I think
---------- Post added at 03:40 PM ---------- Previous post was at 03:38 PM ----------
regenwurm16 said:
I have exact the same setup and tried to let the OTA install but in TWRP it aborted because of the mismatching kernel I think (at least it said it expected the generic device name Google angler etc and in stead it found Huawei nexus 6P Dees-troy etc)
So no harm is done when you try to update other than it doesn't work
But as far as I know when using xposed there's no use for systemless root because xposed is changing system partition
Click to expand...
Click to collapse
It does not bored because of mismatched kernel. Because I tried flashing the stock kernel and then OTA and it still did not work
kirkgbolton said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I used step 10 from this guide then re-flashed TWRP, Super Su, ElementalX and everything seems to be fine, no data loss.
Click to expand...
Click to collapse
This. At this time it's the only fix. I did it as well. Never flashed a factory image via fastboot before so I was a little intimidated but Heisenberg's guide is so smooth and easy to follow I did it in about 5 minutes lol. Plus it was a great learning experience for me.
Is it likely that eventually TWRP flashable zips will make this process easier? Or is there some sort of restriction with these updates for Nexus phones that will always require fastboot?
Not sure. I do know that the above method only took me about 10 minutes. Yeah it sucks you have to utilize a PC to do it but its really not that bad. Maybe in the future someone will figure out how to implement the updates via flashable zip in recovery.
I struggle with this too. I really hope that someone will find a solution to flash it via .zip (sadly I'm more a programmer than an Android-hacker, otherwise I would try my very best right now ).
Just to point it out, it looks like the article you are referring to has been updated since it was linked. I wouldn't want to wipe userdata, so I think 11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact) is what you were referring to at the time. Apologies for the resurrection.
I just used the FlashFire app to update my Nexus 6p with the February update and it worked like a charm.
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
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.
Hi!
I'm looking for a way to either root/twrp v1.2.0b02 (coming from stock files), or a way to apply the ota on a twrp'd/rooted v1.2.0b01.
I have tried this guide without luck starting from the point where the tool tries to flash twrp. when the phone tried to reboot into bootloader it just rebooted to the system.
With this guide i can't apply B02 as i get a mismatch error (forgot what the actual message was called).
any ideas?
thanks in advance!
edit: further information: i am currently on 7.1.1 b01 with unlocked-BL/twrp/root thanks to this guide, BUUUT i can not update from that to b02.
when i flash stock recovery and try to update via ota i get a "package mismatch" error during the update installation process while in the (stock-) recovery.
1. Which version are you running?
2. are you already unlocked and
rooted?
If yes, just flash stock recovery with axon7tool and update your system in the usual way. If done, flash back TWRP and supersu. Done.
Gesendet von meinem ZTE A2017U mit Tapatalk
Its a good question. For e.g. I'm on b10 G version rooted. How to come to A2017GV1.2.0B02 rooted?
Just the same. Install stock recovery and follow the update process as described everywhere in this forum.
marcus.linkenbach said:
1. Which version are you running?
2. are you already unlocked and
rooted?
If yes, just flash stock recovery with axon7tool and update your system in the usual way. If done, flash back TWRP and supersu. Done.
Gesendet von meinem ZTE A2017U mit Tapatalk
Click to expand...
Click to collapse
1.
[...]or a way to apply the ota on a twrp'd/rooted v1.2.0b01.
Click to expand...
Click to collapse
2. trying it right now.
edit: results in a package mismatch.
Flaîm said:
1.
2. trying it right now.
edit: results in a package mismatch.
Click to expand...
Click to collapse
What ended in a package mismatch? Flashing the recovery or updating? (Sorry, didn't see your first quote)
Sent from my ZTE A2017U using XDA Labs
marcus.linkenbach said:
What ended in a package mismatch? Flashing the recovery or updating? (Sorry, didn't see your first quote)
Sent from my ZTE A2017U using XDA Labs
Click to expand...
Click to collapse
the update itself.
Hello,
I'm on A2017GV1.2.0B02, and I'd like to root it.
I have installed adb and axon7toolkit, but it seems there's no stock recovery anymore since 7.x firmware. So when I issue adb edl reboot, the phone is just rebooting the OS. :/
Which steps must I follow for rooting my stock A2017GV1.2.0B02 ?
Thanks.
Jeremy-X said:
Hello,
I'm on A2017GV1.2.0B02, and I'd like to root it.
I have installed adb and axon7toolkit, but it seems there's no stock recovery anymore since 7.x firmware. So when I issue adb edl reboot, the phone is just rebooting the OS. :/
Which steps must I follow for rooting my stock A2017GV1.2.0B02 ?
Thanks.
Click to expand...
Click to collapse
the command to edl is: adb reboot edl.
To boot into recovery it's just power + vol+ button.
But since nougat you cannot boot into bootloader anymore. This would be necessary to unlock the bootloader. Therefore you would have to follow the steps I already mentioned in this thread.
Sent from my ZTE A2017U using XDA Labs
---------- Post added at 01:49 PM ---------- Previous post was at 01:41 PM ----------
Flaîm said:
the update itself.
Click to expand...
Click to collapse
B01 is what? Android 7.0 or 7.1.1? If you are already on 7.1.1 you don't have to flash anything. You will receive the update to B02 OTA. Otherwise you have to follow the official steps to get where you want to be. Described a lot on xda.
Sent from my ZTE A2017U using XDA Labs
Thanks for the answer, but there's no recovery for the B02 7.1.1.
Jeremy-X said:
Thanks for the answer, but there's no recovery for the B02 7.1.1.
Click to expand...
Click to collapse
You are triyng to update your sistem with twrp and the stock update.
you need to go back to stock recovery, aply update from system, wait for process and then, reboot edl, and reflash recovery.
then from recovery root
Flaîm said:
I have tried this guide without luck starting from the point where the tool tries to flash twrp. when the phone tried to reboot into bootloader it just rebooted to the system.
Click to expand...
Click to collapse
My stuff was for reinstalling TWRP on an unlocked phone after Nougat deleted it.
You should try axon7toolkit and see if that does the stuff. Another way around would be to downgrade your phone to B10 (Marshmallow) via MiFavor's update by sd thingy, (i'm not 100% sure if it lets you get to mm from nougat, but it's definitely worth a shot) then trying the BL unlock thread (NOT mine!)
Choose an username... said:
My stuff was for reinstalling TWRP on an unlocked phone after Nougat deleted it.
Click to expand...
Click to collapse
ooooh! guess i misinterpreted the guide then. i never had the problem to begin with as i already unlocked my bootloader on 6.0b10.
ayways, i am currently on 7.1.1 b01 with twrp/root thanks to this guide, BUUUT i can not update from that to b02.
when i flash stock recovery and try to update via ota i get a "package mismatch" error during the update installation process inside the (stock-) recovery.
Flaîm said:
ooooh! guess i misinterpreted the guide then. i never had the problem to begin with as i already unlocked my bootloader on 6.0b10.
ayways, i am currently on 7.1.1 b01 with twrp/root thanks to this guide, BUUUT i can not update from that to b02.
when i flash stock recovery and try to update via ota i get a "package mismatch" error during the update installation process inside the (stock-) recovery.
Click to expand...
Click to collapse
Okay that happened to me. By "this guide" you mean what I posted close to the end right? the xda app just shows me the last post lol
Try to download the full B02 package. Some guy mirrored the full package on one of the B02 posts. Then try to use MiFavor's own updater. It worked for me, can't see why you couldn't use that
Choose an username... said:
Okay that happened to me. By "this guide" you mean what I posted close to the end right? the xda app just shows me the last post lol
Click to expand...
Click to collapse
here's the non-bb coded link https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
Choose an username... said:
Try to download the full B02 package. Some guy mirrored the full package on one of the B02 posts. Then try to use MiFavor's own updater. It worked for me, can't see why you couldn't use that
Click to expand...
Click to collapse
didn't see a b02 fota, sorry. mind linking it?
Flaîm said:
ooooh! guess i misinterpreted the guide then. i never had the problem to begin with as i already unlocked my bootloader on 6.0b10.
ayways, i am currently on 7.1.1 b01 with twrp/root thanks to this guide, BUUUT i can not update from that to b02.
when i flash stock recovery and try to update via ota i get a "package mismatch" error during the update installation process inside the (stock-) recovery.
Click to expand...
Click to collapse
enable bootloader unlock in developer settings...
pelelademadera said:
enable bootloader unlock in developer settings...
Click to expand...
Click to collapse
hmm...
(attachment)
Flaîm said:
ooooh! guess i misinterpreted the guide then. i never had the problem to begin with as i already unlocked my bootloader on 6.0b10.
ayways, i am currently on 7.1.1 b01 with twrp/root thanks to this guide, BUUUT i can not update from that to b02.
when i flash stock recovery and try to update via ota i get a "package mismatch" error during the update installation process inside the (stock-) recovery.
Click to expand...
Click to collapse
You'll always get that mismatch regarding what you do or try. You'll need a custom made twrp flashable zip. Tron1 and I have tried to make one but no success. We will try to make a full flashable zip based on the full image.
Even if you flash your stock recovery back and do the OTA, you'll always get a mismatch regardless what others might say.
raystef66 said:
You'll always get that mismatch regarding what you do or try. You'll need a custom made twrp flashable zip. Tron1 and I have tried to make one but no success. We will try to make a full flashable zip based on the full image.
Even if you flash your stock recovery back and do the OTA, you'll always get a mismatch regardless what others might say.
Click to expand...
Click to collapse
that's what i was afraid of.
guess the zips again will be split into bootstack and system like his other flashable images, right?
Flaîm said:
that's what i was afraid of.
guess the zips again will be split into bootstack and system like his other flashable images, right?
Click to expand...
Click to collapse
Most likely.
This is my first oneplus and non-carrier device and I'm unsure of whether to accept this OTA update. I'm pretty sure I would lose root, maybe twrp but stay unlocked? My concern is having to wipe device again. Without an SD card I'd have to transfer a lot of stuff back and forth.
I read that I could just flash magisk from TWRP after installing an OTA update. I took the update and now my phone thinks I just installed the OS for the first time and TWRP is gone. So.... don't do that.
I am SO frustrated. I should have read more posts.
Bubba Fett said:
This is my first oneplus and non-carrier device and I'm unsure of whether to accept this OTA update. I'm pretty sure I would lose root, maybe twrp but stay unlocked? My concern is having to wipe device again. Without an SD card I'd have to transfer a lot of stuff back and forth.
Click to expand...
Click to collapse
My method:
Download the TWRP 3.2.3-22 installer zip to your device https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Download the full 1.6 GB ZIP to your device - OnePlus6TOxygen_34_OTA_018_all_1812260723_29c01e732b714cfa.zip
https://forum.xda-developers.com/on...os-9-0-4-ota-oneplus-6t-t3860953/post78026655
Boot into recovery and install TWRP 3.2.3-22 zip
Reboot Recovery
Backup (see next post)
Install the full 1.6 GB download
Install TWRP 3.2.3-22 zip again
Reboot Recovery
Flash Magisk-v18.0.zip
Reboot System
Sent from my crosshatch using XDA Labs
Follow the guide here: Link
If you have TWRP, and are rooted:
- Download the full package from above.
- Boot to TWRP, flash that full ROM package you downloaded.
- Flash the TWRP installer.
- Reboot to recovery. (The ROM installs to the opposite slot, so rebooting to recovery again switches to that slot that you just installed that update to)
- Now that you are in TWRP again install Magisk.
- Reboot to System.
- No data or Apps lost. You will be good to go.
I get it now. Little different than I'm used to. Thanks!
Edit.. Just saw the answer to my question farther into the link. I thought it was for devs. Thanks for not beating me up! ?
valzi said:
I read that I could just flash magisk from TWRP after installing an OTA update. I took the update and now my phone thinks I just installed the OS for the first time and TWRP is gone. So.... don't do that.
I am SO frustrated. I should have read more posts.
Click to expand...
Click to collapse
I did something similar, but just flashed twrp using adb again, like you did the first time. Then flash the twrp installer after. It made twrp stick when you reboot to recovery. Don't forget to flash Magisk again. The link in post 4 is great. wish I would have read it before asking.
It was so much easier on my Oneplus One. I just took OTA updates without doing anything unusual at all. No flashing. I was using a custom rom though. Maybe that's the answer now?
Or maybe I should just unroot and deal with the inconveniences of an unrooted phone.
Well, first of all you want lose your data when you do upgrade through OTA.
If you use magisk, tap uninstall and restore images. Then do OTA update but do not reboot. Clear recent apps and go back to magisk: install it to inactive slot. Then reboot.
You will lose customer recovery though, so if you want it, sideload it again with PC.
geminium said:
Well, first of all you want lose your data when you do upgrade through OTA.
If you use magisk, tap uninstall and restore images. Then do OTA update but do not reboot. Clear recent apps and go back to magisk: install it to inactive slot. Then reboot.
You will lose customer recovery though, so if you want it, sideload it again with PC.
Click to expand...
Click to collapse
What is the advantage to this method?
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
OhioYJ said:
Follow the guide here: Link
If you have TWRP, and are rooted:
- Download the full package from above.
- Boot to TWRP, flash that full ROM package you downloaded.
- Flash the TWRP installer.
- Reboot to recovery. (The ROM installs to the opposite slot, so rebooting to recovery again switches to that slot that you just installed that update to)
- Now that you are in TWRP again install Magisk.
- Reboot to System.
- No data or Apps lost. You will be good to go.
Click to expand...
Click to collapse
If I have TWRP, do I still need to uninstall Magisk, or can I just follow the TWRP guide and skip the Magisk guide?
@valzi I don't remove Magisk when doing the updates. I just reinstall. I always use the TWRP method.
valzi said:
What is the advantage to this method?
Click to expand...
Click to collapse
I've only used this method, the only thing I can think of is, it's just easier. Go into Magisk, click Uninstall, click restore images, don't reboot, do your OTA update, don't reboot after it's done, go back into Magisk, click install, then click install to slot (Or something like that. It'll say after OTA next to it.) All of those steps are done within Android and not recovery. Do note though, I haven't tried it with custom recovery INSTALLED on my device. YMMV
OMGWTFISTHIS said:
I've only used this method, the only thing I can think of is, it's just easier. Go into Magisk, click Uninstall, click restore images, don't reboot, do your OTA update, don't reboot after it's done, go back into Magisk, click install, then click install to slot (Or something like that. It'll say after OTA next to it.) All of those steps are done within Android and not recovery. Do note though, I haven't tried it with custom recovery INSTALLED on my device. YMMV
Click to expand...
Click to collapse
Hmm. That seems a lot more complicated to me if you have to lose your data though.
---------- Post added at 03:04 AM ---------- Previous post was at 02:57 AM ----------
OhioYJ said:
@valzi I don't remove Magisk when doing the updates. I just reinstall. I always use the TWRP method.
Click to expand...
Click to collapse
Thanks for the help!