I am on OOS 3.1.2 flashed with TWRP by Eng.stk v41 works fine , but i want revert do Cyanogenmod 13, if i flash Cyanogenmod via TWRP and do a Reboot, my device Stuck on Oneplus Logo and nothing happens.
Reboot to Recovery and flash OOS 3.1.2 again and boot into OOS works fine, but Cyanogenmod doesnt boot.
If i downgrad twrp version it doesnt boot anymore into Recovery
Some help pls
I am having exactly the same problem, and would also like to know the answer.
Also, the eng.stk TWRP is the only one I can find that works.
TECCC said:
I am on OOS 3.1.2 flashed with TWRP by Eng.stk v41 works fine , but i want revert do Cyanogenmod 13, if i flash Cyanogenmod via TWRP and do a Reboot, my device Stuck on Oneplus Logo and nothing happens.
Reboot to Recovery and flash OOS 3.1.2 again and boot into OOS works fine, but Cyanogenmod doesnt boot.
If i downgrad twrp version it doesnt boot anymore into Recovery
Some help pls
Click to expand...
Click to collapse
nickmcg said:
I am having exactly the same problem, and would also like to know the answer.
Also, the eng.stk TWRP is the only one I can find that works.
Click to expand...
Click to collapse
For future, i advise you to search before posting. I have posted this exact same reply on 3 threads. but anyway.
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, Hence it works as you're on the MM bootloader too.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
- Reboot to fast boot
- Flash Unofficial MM TWRP
- Boot into recovery
- Wipe everything except SD Card
- Flash OOS2 zip
- Boot into it
- Goto settings, unlock dev options, enable advanced reboot
- Then reboot to bootloader
- Install official TWRP, Done
Flash any ROM you want now.
Joshwin Aranha said:
For future, i advise you to search before posting. I have posted this exact same reply on 3 threads. but anyway.
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, Hence it works as you're on the MM bootloader too.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
- Reboot to fast boot
- Flash Unofficial MM TWRP
- Boot into recovery
- Wipe everything except SD Card
- Flash OOS2 zip
- Boot into it
- Goto settings, unlock dev options, enable advanced reboot
- Then reboot to bootloader
- Install official TWRP, Done
Flash any ROM you want now.
Click to expand...
Click to collapse
Many thanks, I'll give it a try
nickmcg said:
Many thanks, I'll give it a try
Click to expand...
Click to collapse
Look at cm13 thread, because now is possible to flash cm13 on new bootloader (from today's nightly I suppose)
Related
Well the title explains itself, is there any easy way to downgrade from OOS3 to flash any custom ROM? Don't know how long it will be till custom Roms update to be compatible with its bootloader. I read I have to go through the unblock method but I really don't want that. So, any easy/safe way to do it?
Thanks a lot!
You can simply flash OOS 2.2.2 if you wanna downgrade
Assuming you're on OOS3 with eng.stks modded TWRP,
- Boot into recovery
- Wipe everything except SD Card
- Flash OOS2 zip
- Boot into it
- Goto settings, unlock dev options, enable advanced reboot
- Then reboot to bootloader
- Install official TWRP, Done
flash any rom you want now.
Joshwin Aranha said:
Assuming you're on OOS3 with eng.stks modded TWRP,
- Boot into recovery
- Wipe everything except SD Card
- Flash OOS2 zip
- Boot into it
- Goto settings, unlock dev options, enable advanced reboot
- Then reboot to bootloader
- Install official TWRP, Done
flash any rom you want now.
Click to expand...
Click to collapse
Worked like a charm, thanks a lot!
feligoni said:
Worked like a charm, thanks a lot!
Click to expand...
Click to collapse
I'm glad
hello !
im a OPX , i updated my phone to Marshm. 6.0.1 and i want to downrgade to android 5.1.1
Really?
Omicron Technics
Hi.
So the latest Cyanogenmod (honestly every update out of the CM update that came out on 9th Oct) builds do not work for my device. Whenever I try to boot up the device, the device just gets stuck on the bootup screen, that is the screen where you see the OnePlus logo and there's text in the lower part that says "Powered by Android", except that there is no "powered by Android" text seen.
What should I do in order to get things working?
Sorry to post this in the general thread, I am not yet high enough that I can post in the Android Development Thread.
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Loureiro said:
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Click to expand...
Click to collapse
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
sundhar88 said:
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
Click to expand...
Click to collapse
Alright thanks! If I face any problems I'll post again!
aamodjoshi23 said:
Alright thanks! If I face any problems I'll post again!
Click to expand...
Click to collapse
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
sundhar88 said:
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
Yup. You need to first flash the OOS recovery and then you need to flash the OOS 3.1.3 and then again the TWRP and then you need to flash whichever ROM you want to... Been there, done that. Real pain...
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Loureiro said:
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
You're a lifesaver dude! Thanks for the link!!
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Adesh15 said:
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Click to expand...
Click to collapse
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Install opx_recovery, flash 3.1.3 from recovery. After installed you can fastboot flash Blu sparks latest or Nichets twrp done.
Cretandus said:
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Click to expand...
Click to collapse
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Cretandus said:
Hi all,
I�¢??m having the exact same problem. I�¢??ve searched several forums, and have seen different solutions, but I�¢??m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don�¢??t want to make any mistakes. I�¢??m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I�¢??m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
What I did was, first of all, I took the backup using Titanium Backup and took a nandroid backup. Then I already had downloaded the files required, that is the BL zip file, the TWRP recovery, and the latest CM 13.0 build. Then I went to recovery > install and then located the BL and flashed it. Then I tried to flash the TWRP recovery but it didn't. Gave an error saying, "Unsuccessful" or something on those lines.
So I took that TWRP img file and copied it on my laptop. Then I went into the bootloader, which at first I thought was a bad idea since I just flashed the BL zip, then I flashed the new TWRP img file and went to recovery mode. And it had worked. So I flashed the CM 13.0 build too and then booted up the device, and it worked!
I guess that should help
aamodjoshi23 said:
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
Click to expand...
Click to collapse
I'm glad it worked for(don't forget to drop a thanks and a vote would be good too)
Also for next time,please search the forums before creating a thread.:angel:
Adesh15 said:
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Click to expand...
Click to collapse
Adesh15, it worked! Thank you very much!
Cretandus said:
Adesh15, it worked! Thank you very much!
Click to expand...
Click to collapse
Great !
I am using TWRP 3.0.2.0 It is giving me problems as shown in images below.
I tried flashing new recovery but it also couldn't get flashed. While flashing new CM 13/CM14.1 ROMs it is giving errors, but it flashes older CM 13 ROMs fine.
dvaibhavd said:
I am using TWRP 3.0.2.0 It is giving me problems as shown in images below.
I tried flashing new recovery but it also couldn't get flashed. While flashing new CM 13/CM14.1 ROMs it is giving errors, but it flashes older CM 13 ROMs fine.
Click to expand...
Click to collapse
Bro wait....!!!
Is this real?
You are using too old recovery(as your ss says 2.8.7)+old boot loader..you need some work on your phone to be able to flash new cm 13/14.1.
Just head over to general thread and find how to upgrade boot loader and install latest twrp.
After that you can flash all latest available ROM.
Boot logo Problem
Hey I have used this method http://forum.xda-developers.com/one...update-bootloader-firmware-to-t3478917/page20 and updated the BL.However after flashing CM14 I am stuck on 1+ logo.
I was able to flash stock Oxygen Rom .I want to flash CM 14 please help
Same
utkhirodka said:
Hey I have used this method http://forum.xda-developers.com/one...update-bootloader-firmware-to-t3478917/page20 and updated the BL.However after flashing CM14 I am stuck on 1+ logo.
I was able to flash stock Oxygen Rom .I want to flash CM 14 please help
Click to expand...
Click to collapse
Same here with the TZ issues. As for the recovery, the TWRP version 3.0.2-0 is the most latest one that I can flash & boot into successfully. If I flash anything newer than 3.0.0-1 my OPX is stuck on OP logo as well.
My phone is stuck at one plus boot logo when i tried to go into recovery mode or tried to start it the oneplus logo popped and goes out again and again and when i tried to flash twrp through fastboot mode it say the device is locked cant change or erase the recovery what should i do please guide me
The only recovery that will flash on mine is 3.0.2-0. I've tried flashing through Fastboot. I've even tried to use the dd command for both 3.0.3-0 official and blu sparkz v41 and it gets stuck at the OnePlus logo.
Phone still boots into OOS just fine and 3.0.2-0 flashes through the old JMZ TWRP app just fine. It's just any other method that doesn't work.
The latest recoverys for new bootloader is 3.0.3, bluesparks 3.0.2-1 V41 or Sultans updated TWRP. 3.0.2 and under us for old bootloader.
Exodusche said:
The latest recoverys for new bootloader is 3.0.3, bluesparks 3.0.2-1 V41 or Sultans updated TWRP. 3.0.2 and under us for old bootloader.
Click to expand...
Click to collapse
Again, I tried flashing 3.0.3 and it wouldn't stick.
blackknightavalon said:
Again, I tried flashing 3.0.3 and it wouldn't stick.
Click to expand...
Click to collapse
After flashing recovery you have to boot right into it with fastboot command then swipe to allow modifications?
Exodusche said:
After flashing recovery you have to boot right into it with fastboot command then swipe to allow modifications?
Click to expand...
Click to collapse
As stated above, all it does is hang at the OnePlus logo.
Also...
fastboot boot drive:\path\to\twrp-3.0.3-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.507s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.540s
Click to expand...
Click to collapse
blackknightavalon said:
As stated above, all it does is hang at the OnePlus logo.
Click to expand...
Click to collapse
Ok sorry what I did was keep it simple. Reflash original stock recovery, flash 2.2.3 then flash 3.1.4 and boot. Just skip everything and reboot back to bootloader mode. Now you can flash latest TWRP and should boot latest ROMs without any issues.
Exodusche said:
Ok sorry what I did was keep it simple. Reflash original stock recovery, flash 2.2.3 then flash 3.1.4 and boot. Just skip everything and reboot back to bootloader mode. Now you can flash latest TWRP and should boot latest ROMs without any issues.
Click to expand...
Click to collapse
2.2.3 flashed successfully. I already know 3.1.4 will work. I'll post again if your plan completely works.
...and I'm still getting the same errors after flashing 3.1.4 through stock recovery. o.0
I'm going to start from the earliest firmware available and flash progressively from there and see if that works.
My phone stucks on oneplus logo after flashing paranoid rom . I do everything like wiping dalvin cache, data , system . TWRP recovery i am using is 3.03 and currently running cm 13. Any solution?
Mandeep Singh 07 said:
My phone stucks on oneplus logo after flashing paranoid rom . I do everything like wiping dalvin cache, data , system . TWRP recovery i am using is 3.03 and currently running cm 13. Any solution?
Click to expand...
Click to collapse
Is ur bootloader updated to latest one ??
[email protected] said:
Is ur bootloader updated to latest one ??
Click to expand...
Click to collapse
yeah its latest one 3.0.3
Mandeep Singh 07 said:
yeah its latest one 3.0.3
Click to expand...
Click to collapse
PA I believe is on the old bootloader still. So you would have to downgrade your bootloader by flashing LL stock recovery and 2.x.x OOS firmware. Not worth the hassle if you ask me.
Mandeep Singh 07 said:
yeah its latest one 3.0.3
Click to expand...
Click to collapse
actually when i root the phone , then it goes into bootloop, i didn`t backup my data so i lost my all data ,
after that i install paranoid then it stucks on boot logo , i tried it several times but none happens,
then i use adb push command ino twrp recovery(3.0.2) to copy cyanogenmod after that i flash it , it fails ,
then i flash cwm recovery then flash is succeded and currently running cm 13 ,
when i installed root checker it said your phone is partially rooted, when i enable root option in developer option then it said root verified.
But when i tried to flash other roms using twrp (3.0.3, 3.0.2) it stucks on boot logo.
Please help me
Exodusche said:
PA I believe is on the old bootloader still. So you would have to downgrade your bootloader by flashing LL stock recovery and 2.x.x OOS firmware. Not worth the hassle if you ask me.
Click to expand...
Click to collapse
lower bootloader can`t flash it fails every time....
Mandeep Singh 07 said:
lower bootloader can`t flash it fails every time....
Click to expand...
Click to collapse
Did you also revert to the old TWRP version 3.0.2? Other then that I'm out of ideas.
Exodusche said:
Did you also revert to the old TWRP version 3.0.2? Other then that I'm out of ideas.
Click to expand...
Click to collapse
At that twrp blu spark 3.0.2 is available and of only that recovery is working lower recoviers cant flash and boot
Mandeep Singh 07 said:
At that twrp blu spark 3.0.2 is available and of only that recovery is working lower recoviers cant flash and boot
Click to expand...
Click to collapse
Right but if your downgrading your bootloader to flash PA you need to use old bootloader TWRP 3.0.2. So that being said easiest way is flash 2.2.3 with blusprk 3.0.2-2 TWRP then immediately after flash TWRP 3.0.2 image. Now re boot back into recovery and flash PA. I prefer flashing 2.2.3 with stock LL recovery less chance of issues. Then just fastboot flash old TWRP 3.0.2 and continue with PA.
Exodusche said:
Right but if your downgrading your bootloader to flash PA you need to use old bootloader TWRP 3.0.2. So that being said easiest way is flash 2.2.3 with blusprk 3.0.2-2 TWRP then immediately after flash TWRP 3.0.2 image. Now re boot back into recovery and flash PA. I prefer flashing 2.2.3 with stock LL recovery less chance of issues. Then just fastboot flash old TWRP 3.0.2 and continue with PA.
Click to expand...
Click to collapse
thanks bro this works fine
This is my version of TWRP built for the 2017 Moto G5S. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, turn off your device, hold PWR and VolDn for 3 seconds, then let go.
Differences between upstream TWRP and my fork:
My original green theme
No SuperSU
No TWRP app
No HTC Dumlock cruft
Updated pigz compressor (slightly faster and more tolerant of corruption)
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is available on the downloads tab.
XDA:DevDB Information
TWRP for Moto G5S, Tool/Utility for the Moto G5S
Contributors
squid2
Source Code: https://github.com/moto8937-twrp
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-17
Created 2017-11-05
Last Updated 2018-08-17
Squid TWRP 3.1.1-r3
Initial build for montana is up. I expect it to be fully functional, including encryption support. Special thanks to @lohanbarth for testing.
thank you for your work :good:
Hi,
i just flashed your TWRP. The flash was successful, after booting to recovery twrp came up just fine. I wiped /data to decrypt, then rebooted the phone... Now it seems either bootlooping or bricked.
(Of course i unlocked the bootloader before flashing)
The phone just shows the bootloader-screen (blue background, red M-Logo, white letters "powered by android") with a small text in the middle "bad key).
Nothing happens. I cant even shut it down. Holding the power button for 10 seconds seems to start a reboot (screen goes black) but the bootloader-screen immediately shows back up and stays. Theres nothing i can do, no adb/fastboot access either...
Any suggestions?
Edit1:
AH! Pressing VolDown + Power gets me to fastboot/recovery... Phew. Guess i flash the stock rom first before proceeding any further.
Edit2:
Succeeded, nice!
Hi,
I flashed this TWRP. After flashing I went to recovery mode. Format Data failed as /data unknown. Flashed stock ROM. Again flashed TWRP. This time it just bootloops into TWRP recovery. When I power off and ON again, it bootloops and goes into TWRP recovery again and again. Any idea what could be wrong? My guess is I screwed up partition table. But not sure.
Thanks
KS
I went through flashing stock ROM, TWRP once again. After flashing TWRP, I went to recovery repeatedly and did 'Format Data' every time. I flashed Magisk. System booted fine. I verified by power off/on several times. Seems to be working fine.
Thanks
KS
Thanks for your hard work at bringing TWRP to the MOTO G5s.
It took me a while to install it on my XT1797, as there was some strange message during boot which said
ID: Bad key
But after many many times bricking and unbricking, I am now finally rooted using Magisk.
Hope that we can see some custom Roms for this great device soon.
I tried it with XT1797, but I can not boot and flash twrp.
Is this twrp compatible with XT1797?
hello, your bootloader and unlock it?
did you enable USB debugging?
that you put the fastboot cmd?
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
FAFAŁ said:
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Click to expand...
Click to collapse
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Root and TWRP. And a great phone.
Just need some Roms, pray that they will come!
Thank you!
janhieber said:
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Click to expand...
Click to collapse
Ok .that's all super go to recovery end fire .Thanks
Hello, I compiled the twrp3.2 with the sources of squid2.
thank @squid2 for sources
twrp-montana-3.2.0-r1 > http://www.mediafire.com/file/4443oy6kwiyvm5g/twrp-montana-3.2.0-r1.img
Squid TWRP 3.2.0-r1
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
squid2 said:
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
Click to expand...
Click to collapse
Dear @squid2 please give some ROMs also
... please i know you are busy with work but it is just a request
Unable to Flash twrp recovery
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
dau999 said:
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
Click to expand...
Click to collapse
after the flash of the twrp you select good recovery in the bootloader?
lohanbarth said:
after the flash of the twrp you select good recovery in the bootloader?
Click to expand...
Click to collapse
Select good recovery in the bootloader??!!
Bootloader gives me a notification that the img is not signed or corrupt (squids one)
you tried to download it again and then try again
lohanbarth said:
you tried to download it again and then try again
Click to expand...
Click to collapse
I did, same error.