Related
I feel there is a lack of information on exactly how to go about doing this, so here is what worked for me:
1. Determine your build version, I started from NCE. You have to be on 4.4.4 to update to 5.0. You can find the OTA files for this in this thread. Install them in order if needed. (Steps 4-8).
2. Get the 5.0 update zip from this thread
3. Ensure you have the latest platform tools. Use the SDK Manager.
4. Reboot into recovery (Hold power, volume up, and home button).
5. Select install from adb in recovery
6. open a terminal in the directory where the OTA zip is located.
7. enter adb sideload <file name here>
8. let it complete, then reboot.
If you get an adb cannot read error, ensure you've followed step 3.
**NOTE** This is for stock devices only, and I've only tested this from STOCK recovery. I have NO idea what effect this has on root, but general intuition says you'll lose it.
Does this wipe everything?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Unhived__Mind said:
Does this wipe everything?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Click to expand...
Click to collapse
Did not wipe apps data but wipe some personal data.
Notes from Note 4
What about Odin?
Is there I way I can flash the update with Odin? I'd rather not lose any data. I'm on 4.4.4 Rooted.
I am curretnly on NG3 (4.4.2), it seems I cannot get any OTA. Keeps saying its interrupted. Do I need to update to 4.4.4 then use this method to get lollipop on the device?
Ryan6700 said:
Is there I way I can flash the update with Odin? I'd rather not lose any data. I'm on 4.4.4 Rooted.
Click to expand...
Click to collapse
Read this : http://forum.xda-developers.com/showthread.php?p=59994426
Notes from Note 4
---------- Post added at 04:10 PM ---------- Previous post was at 04:09 PM ----------
ThuGzta said:
I am curretnly on NG3 (4.4.2), it seems I cannot get any OTA. Keeps saying its interrupted. Do I need to update to 4.4.4 then use this method to get lollipop on the device?
Click to expand...
Click to collapse
Yes you need to be on 4.4.4 before updating to 5.0
Notes from Note 4
This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Thank you once again for root, do you finally get to enjoy your new Pixel?
Woooooooooooooo! I am so fricken excited for this.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Here is everything you need.
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
http://www.xda-developers.com/root-is-now-available-for-the-google-pixel-and-pixel-xl/
Here is everything you need.
Once again you're the man Chainfire, thanks for all your hard work
- An unnamed tester needed to do the whole thing twice for the root to stick. While I assume this was Jeff's own fault, we can never be sure. -lol
---------- Post added at 09:17 PM ---------- Previous post was at 09:14 PM ----------
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
According to the post..
The images for the Pixels need to be 'fastboot boot'ed, not flashed. After a few minutes (have patience) and a couple of (automatic) reboots, Android should boot fully rooted. Read the README in the ZIP.
clockcycle said:
Once again you're the man Chainfire, thanks for all your hard work
---------- Post added at 09:17 PM ---------- Previous post was at 09:14 PM ----------
According to the post..
The images for the Pixels need to be 'fastboot boot'ed, not flashed. After a few minutes (have patience) and a couple of (automatic) reboots, Android should boot fully rooted. Read the README in the ZIP.
Click to expand...
Click to collapse
needed to set everything up and enable usb debugging - thennnn boot into bootloader and flash boot-to-root.img.
all is well!
Running just fine, thank you Chainfire!
Sent from my Pixel using Tapatalk
Worked like a charm! Thanks @Chainfire. I had just posted my pixel up for sale. Guess I'll keep it a while longer.
root issues
Pixel 32gig bought from google store unlocked bootloader and did as tutorial said, i have superSU icon but not asking for root privilage, apps saying no root?
You are the best Chainfire I've met today.
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
mrnovanova said:
Worked like a charm! Thanks @Chainfire. I had just posted my pixel up for sale. Guess I'll keep it a while longer.
Click to expand...
Click to collapse
And I was eyeing a 5X... maybe not now!
So far when I flash EX kernel root stops working and when I reboot the phone to root it again kernel reverts back to stock. Lol! Guess I can't have both.
mrnovanova said:
So far when I flash EX kernel root stops working and when I reboot the phone to root it again kernel reverts back to stock. Lol! Guess I can't have both.
Click to expand...
Click to collapse
You're doing something wrong, it all works fine.
fastboot flash ElementalX and then fastboot boot Chainfire's boot-to-root.img
flar2 said:
You're doing something wrong, it all works fine.
fastboot flash ElementalX and then fastboot boot Chainfire's boot-to-root.img
Click to expand...
Click to collapse
Yup. It seems I was just booting the kernel image without flashing it. All good now followed directions on your last post where you say fastboot flash boot and not fastboot boot. I think that made all the difference.
Sent from my Pixel using XDA-Developers mobile app
More donations to come, after I return from Cruise
Will Xposed framework work? Or do we need to wait for twrp?
maflin18 said:
Will Xposed framework work? Or do we need to wait for twrp?
Click to expand...
Click to collapse
I'm wondering the same thing, but I'm pretty certain we need twrp. From what I understand there's a working version out there for the pixels, so it shouldn't be long before it's released.
Sent from my Pixel using XDA Labs
do i have to use fastboot boot boot-to-root.img or do i have to put it in slot a?
varun.gid said:
do i have to use fastboot boot boot-to-root.img or do i have to put it in slot a?
Click to expand...
Click to collapse
Slot a for kernel and fastboot boot boot-to-root for root worked for me.
Sent from my Pixel using XDA-Developers mobile app
maflin18 said:
Will Xposed framework work? Or do we need to wait for twrp?
Click to expand...
Click to collapse
Why ask the same question in more than one thread ?
Have you even read anything in the xposed thread ?
Your answer is in the xposed thread, not here
Sent from my Pixel using XDA-Developers mobile app
Hi everybody,
I have a probleme with my OP3T.
I have upgraded the OS from 3.5.4 to 4, but I don't succed to root the phone, mainly because of the TWRP (flash with 3.0.3.0) that doesn't access to the SD card (twrp asks a password I don't have, so that stay encrypted).
When I try to follow this guide, I always have an error with the recovery stock (recovery downloaded from the oneplus support) during the sideload step (I also try to dowload the rom with twrp, but no success...)
So my question:
Does someone can help me to come back to 3.5.4 until twrp is supported by 4.0 ?
Thank you very much
I'm in the same boat. When sideloading 3.5.3 ota it fails after approximately 45%.
I had the same problem. Steps I did in order to make phone functional:
If you don't have TWRP, you have to install it.
Then, you should wipe your phone entirely from TWRP (Factory Reset, Format Data, Advanced Wipe->Dalvik/ART;System;Data;Internal Storage).
Reset the phone and enter TWRP once again.
Copy the official ZIP with OOS 3.5.x ROM into phone's memory, then flash it.
Flash SuperSU, otherwise your phone won't boot.
I don't take any responsibility, in case you mess something up with your phone.
Okay, my solution was to: 1. boot up in fastboot mode 2. Disable encryption by opening a command prompt in administrater mode and type fastboot format userdata. 3. Install 3.5.3 from Twrp.
Not ideal to disable encryption but now I got a working phone
---------- Post added at 04:59 PM ---------- Previous post was at 04:54 PM ----------
djseban2 said:
I had the same problem. Steps I did in order to make phone functional:
If you don't have TWRP, you have to install it.
Then, you should wipe your phone entirely from TWRP (Factory Reset, Format Data, Advanced Wipe->Dalvik/ART;System;Data;Internal Storage).
Reset the phone and enter TWRP once again.
Copy the official ZIP with OOS 3.5.x ROM into phone's memory, then flash it.
Flash SuperSU, otherwise your phone won't boot.
I don't take any responsibility, in case you mess something up with your phone.
Click to expand...
Click to collapse
Thx. I might have forgotten to reset the phone after wipe, before installing 3.5.4 which is why it wouldn't install even from twrp. My solution worked though - encrypting it again will be for another day. Sick of geeking
So once you have working 3.5.3/4 can you return it to stock - I mean by relocking bootloader and reflashing stock recovery? So then to receive 4.0 via OTA?
Thanks
white43 said:
So once you have working 3.5.3/4 can you return it to stock - I mean by relocking bootloader and reflashing stock recovery? So then to receive 4.0 via OTA?
Thanks
Click to expand...
Click to collapse
Yes, it's entirely possible, but what's the point? You can flash stock recovery->lock bootloader->sideload OOS 4.0, and you are stock . From what I've read, not everyone got 4.0 through OTA yet.
Do you have to be on a specific version of twrp to do this? I cant flash 3.5.4 back using the latest twrp (3031)
EDIT
Never mind all OK, was just begin inpatient
white43 said:
So once you have working 3.5.3/4 can you return it to stock - I mean by relocking bootloader and reflashing stock recovery? So then to receive 4.0 via OTA?
Thanks
Click to expand...
Click to collapse
Do you have a link for the stock 3.5.X recovery? Link from O+ download section won't work..
They provide the so-called Oxygen Stock REC for OP3T here: downloads.oneplus.net/
But I always got different MD5 after downloading the img they provided.
spida_singh said:
Do you have to be on a specific version of twrp to do this? I cant flash 3.5.4 back using the latest twrp (3031)
EDIT
Never mind all OK, was just begin inpatient
Click to expand...
Click to collapse
Hey I am in same boat, does TWRP version matters to return from 4.0.2 to 3.5.3.
I have TWRP(3031) and SU 2.79. I want to revert for battery as well xposed.
uttam.ace said:
Hey I am in same boat, does TWRP version matters to return from 4.0.2 to 3.5.3.
I have TWRP(3031) and SU 2.79. I want to revert for battery as well xposed.
Click to expand...
Click to collapse
It will work with 3.0.3-1 TWRP but you have to flash the ROM twice because of filesystem and put the files twice on the internal memory. Reboot recovery twice forced.
I think TWRP 3.0.4.0 should work better but I do not used it on my phone to restore from 4.0.2 to 3.5.4 so you could try and let us know
---------- Post added at 06:35 PM ---------- Previous post was at 06:32 PM ----------
https://forums.oneplus.net/threads/how-to-restore-to-3-5-4-from-4-0-2-on-op3t.493963/
I made this but you can flash it at your own risk.
To me it worked.
And another tutorial I found but not tried is here https://forum.xda-developers.com/showpost.php?p=70310185&postcount=308
Oneplus 3T downgrade bootloader locked
Hello everyone!
I have a OP3T locked by frp and android nougat oxygen 4.0.3. Is there any solution to downgrade the android to oxygen 3.x??
Thank you guys,
Cheers!
spida_singh said:
Do you have to be on a specific version of twrp to do this? I cant flash 3.5.4 back using the latest twrp (3031)
EDIT
Never mind all OK, was just begin inpatient
Click to expand...
Click to collapse
I tried using TWRP 3.0.4.1,
I was able to flash. thing is, while flashing zip in twrp, it won't show any progress for 2-10 minutes.
then it will show finished flashing
---------- Post added at 07:12 PM ---------- Previous post was at 07:07 PM ----------
I want to share my experience,
Latest TWRP 3.0.4.1 made all difficulty easy,
I was in oxyzen os 4.1.6.
then tried sideload, it fails,
then installed TWRp and flash 3.5.4 via TWRP, (have to flash data,system,cache,internal storage) before flashing,
then it just booted, no issue
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
chanh2018 said:
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Won't root for me.
you mean magisk not working with this build?
mcdull said:
you mean magisk not working with this build?
Click to expand...
Click to collapse
No, it's not working for ME.
Sent from my PH-1 using XDA Labs
avd said:
Won't root for me.
Click to expand...
Click to collapse
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
kt-Froggy said:
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
Click to expand...
Click to collapse
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
JimmyCash030 said:
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
Click to expand...
Click to collapse
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
kt-Froggy said:
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
Click to expand...
Click to collapse
yeah worked for me as well with the latest canary MM !!
Magisk 19.4 works just fine on latest 148 build if need be I can upload magisk rooted boot. Img
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
allenjthomsen said:
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
Click to expand...
Click to collapse
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
avd said:
getting back to the topic at hand, i flashed this, then twrp on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now i got to plug this in and swap slots to reinstall twrp.
Is possible that magisk and twrp are back to not playing nice to each other again?
(i'll test this out if i get a chance to swap slots)
Click to expand...
Click to collapse
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
allenjthomsen said:
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
Click to expand...
Click to collapse
pretty much everything for this phone resides in t.me/ESSENTIALPH1DEV
avd said:
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Click to expand...
Click to collapse
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
Flashing the patched image provided just sits there looking at the boot animation.
I'll play with it tonight.
It's a Sprint phone. Could that be the issue?
Sent from my PH-1 using XDA Labs
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
I'm no expert but did this ans it worked:
1. In TWRP recovery (created nandroid and wiped cache)
2. Flashed full update zip from official download link, then TWRP, then wipe cache
3. Reboot system and let it settle
4. Reboot into TRWP and flashed Canary Channel zip file
5. Wipe cache
6. Reboot system
Hope this helps.
jionny said:
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
Click to expand...
Click to collapse
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
? I always have trouble remembering, not anymore it seems
gavinfernandes2012 said:
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
I always have trouble remembering, not anymore it seems
Click to expand...
Click to collapse
Are you able to give more precise instructions on fastboot instructions?
jionny said:
Are you able to give more precise instructions on fastboot instructions?
Click to expand...
Click to collapse
Nevermind, got the instructions from essentials site. flashed via fastboot which erased everything had to do a complete setup again
I need stock firmware for my Moto G6 XT1925-5 OPSS27.82-87-6
And compatible working and tested TWRP.
I want to reflash this Phone, and get rid bootloader unlock warning.
Any help with that?
Morricorne said:
I need stock firmware for my Moto G6 XT1925-5 OPSS27.82-87-6
And compatible working and tested TWRP.
I want to reflash this Phone, and get rid bootloader unlock warning.
Any help with that?
Click to expand...
Click to collapse
This is the signed firmware you are looking for:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Official TWRP is available on https://eu.dl.twrp.me/ali/.
You should start with version 3.2.3-0 for your old Oreo build.
---------- Post added at 10:29 PM ---------- Previous post was at 10:22 PM ----------
Morricorne said:
I want to reflash this Phone, and get rid bootloader unlock warning.
Any help with that?
Click to expand...
Click to collapse
Try this tool for Windows
https://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667/
In case of any problems with the tool I could repack a logo.bin with the images that you prefer.
WoKoschekk said:
This is the signed firmware you are looking for:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Official TWRP is available on https://eu.dl.twrp.me/ali/.
You should start with version 3.2.3-0 for your old Oreo build.
Click to expand...
Click to collapse
Thanks for answear. I test this fw in next week.
Now im on official newest 9.0 for moto g6.
I find place with stock moto g6 firmware. Tried flash oldest 8.0 rom. But fastboot give me cannot downgrade message. Thats why i decided flash newest avaible fw.
I flashed official TWRP recovery for g6 too.
And try flash zip file. But i cant decrypt storage. And i have error with format data. I Just give up with remove Bootloader warning. And use stock 9.0
I dont have enough data package to download this fw. But i try this fw in future. Thanks for helpi just wanted only remove this Bootloader warning. Cause im buy this moto with already unlocked Bootloader. I have moto g5 too. With unlocked Bootloader. I replaced this warning with black moto logo. And its work. But i cant do the same thing with moto g6
Morricorne said:
Thanks for answear. I test this fw in next week.
Now im on official newest 9.0 for moto g6.
I find place with stock moto g6 firmware. Tried flash oldest 8.0 rom. But fastboot give me cannot downgrade message. Thats why i decided flash newest avaible fw.
I flashed official TWRP recovery for g6 too.
And try flash zip file. But i cant decrypt storage. And i have error with format data. I Just give up with remove Bootloader warning. And use stock 9.0
I dont have enough data package to download this fw. But i try this fw in future. Thanks for help
Click to expand...
Click to collapse
Do not downgrade from Pie to Oreo! Once Pie is installed there is no way back to Oreo.
TWRP can't decrypt /data on Moto G6. Start TWRP, don't enter a password and hit cancel. Go to "Wipe > Format Data (do not use 'Advanced'!!) > type 'yes' and swipe to confirm".
Next reboot to recovery twice!
Now /data is unencrypted and you must flash the no-verity/disable_forceencrypt.zip in order to stay unencrypted. A reboot to system without that .zip will encrypt your /data again.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
Flashing newest Magisk v20.4 will cause a bootloop. Use v19.3 instead and update Magisk through Magisk Manager when v19.3 is installed without any issues.
WoKoschekk said:
Do not downgrade from Pie to Oreo! Once Pie is installed there is no way back to Oreo.
TWRP can't decrypt /data on Moto G6. Start TWRP, don't enter a password and hit cancel. Go to "Wipe > Format Data (do not use 'Advanced'!!) > type 'yes' and swipe to confirm".
Next reboot to recovery twice!
Now /data is unencrypted and you must flash the no-verity/disable_forceencrypt.zip in order to stay unencrypted. A reboot to system without that .zip will encrypt your /data again.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
Flashing newest Magisk v20.4 will cause a bootloop. Use v19.3 instead and update Magisk through Magisk Manager when v19.3 is installed without any issues.
Click to expand...
Click to collapse
OK thanks i try this in next week
WoKoschekk said:
Do not downgrade from Pie to Oreo! Once Pie is installed there is no way back to Oreo.
TWRP can't decrypt /data on Moto G6. Start TWRP, don't enter a password and hit cancel. Go to "Wipe > Format Data (do not use 'Advanced'!!) > type 'yes' and swipe to confirm".
Next reboot to recovery twice!
Now /data is unencrypted and you must flash the no-verity/disable_forceencrypt.zip in order to stay unencrypted. A reboot to system without that .zip will encrypt your /data again.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
Flashing newest Magisk v20.4 will cause a bootloop. Use v19.3 instead and update Magisk through Magisk Manager when v19.3 is installed without any issues.
Click to expand...
Click to collapse
Where i can find this disable forceencrypt zip?
Morricorne said:
Where i can find this disable forceencrypt zip?
Click to expand...
Click to collapse
https://github.com/Zackptg5/Disable...Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
WoKoschekk said:
Do not downgrade from Pie to Oreo! Once Pie is installed there is no way back to Oreo.
TWRP can't decrypt /data on Moto G6. Start TWRP, don't enter a password and hit cancel. Go to "Wipe > Format Data (do not use 'Advanced'!!) > type 'yes' and swipe to confirm".
Next reboot to recovery twice!
Now /data is unencrypted and you must flash the no-verity/disable_forceencrypt.zip in order to stay unencrypted. A reboot to system without that .zip will encrypt your /data again.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
Flashing newest Magisk v20.4 will cause a bootloop. Use v19.3 instead and update Magisk through Magisk Manager when v19.3 is installed without any issues.
Click to expand...
Click to collapse
Cant format data TWRP 3.3.1-0
Flashed decryption zip, magisk system start.
Can enter TWRP again.
Imei work but no Service.
Wtf?
Morricorne said:
Flashed decryption zip, magisk system start.
Can enter TWRP again.
Imei work but no Service.
Wtf?
Click to expand...
Click to collapse
It's not a decryption.zip, it's a forceencryption-disabler.
---------- Post added at 08:27 AM ---------- Previous post was at 08:20 AM ----------
I guess you don't reboot to system after flashing the stock ROM, do you?
One of the last fastboot commands was "fastboot erase userdata". The missing reboot command is the reason for your problem!
WoKoschekk said:
It's not a decryption.zip, it's a forceencryption-disabler.
---------- Post added at 08:27 AM ---------- Previous post was at 08:20 AM ----------
I guess you don't reboot to system after flashing the stock ROM, do you?
One of the last fastboot commands was "fastboot erase userdata". The missing reboot command is the reason for your problem!
Click to expand...
Click to collapse
Nope its a not compatible with android 9 version. I found this on xda
https://forum.xda-developers.com/moto-g6/help/service-root-t4004467
**** that. I reflash everything to Stock cause i dont need magisk and root. I only need get rid Bootloader Unlock warning. What i almost finished. Now i look for modified logo.bin
Morricorne said:
Nope its a not compatible with android 9 version. I found this on xda
https://forum.xda-developers.com/moto-g6/help/service-root-t4004467
**** that. I reflash everything to Stock cause i dont need magisk and root. I only need get rid Bootloader Unlock warning. What i almost finished. Now i look for modified logo.bin
Click to expand...
Click to collapse
Post a picture and I will convert it for you to a logo.bin
WoKoschekk said:
Post a picture and I will convert it for you to a logo.bin
Click to expand...
Click to collapse
I may send you original logo bin
I have this now
A resolution of 1080x2160 would be perfect.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
Morricorne said:
I may send you original logo bin
I have this now
Click to expand...
Click to collapse
Send it
WoKoschekk said:
A resolution of 1080x2160 would be perfect.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
Send it
Click to expand...
Click to collapse
Finished everything flashed. Bootlogo too. And i get ride unknown password when Phone boot too. I dont use any password. Then i dont know whats wrong. Phone ask me everytime when i reboot my device. Now this is gone. No more modding moto g6. Better is stay on stable working stock. Then cant use phone. Man what a day. Time to relax i almost throw this damn phone on the floor.