Hi,
I have tried many TWRP versions (eg: Official, @TheStrix , ZCX, Alka,...) and all brings the same results - after flashing and booting directly to TWRP (which works) and then rebooting to system I got bootloop.
I have tried most clean way to try:
- flash via fastboot whole system - even with userdata
- turn on usb debugging
- reboot to fastboot
- flash twrp
- boot in to recovery (power+VolUp)
- cancel decription
- reboot to system
- boot loop
So do we have any working TWRP for latest developer global rom?
Btw, I have unlocked bootloader - official way. In the past TWRP was working for me with CM14.1. Now I want have it with official rom.
Try Alka twrp
Wysłane z mojego Elephone P8000 przy użyciu Tapatalka
mar.ur said:
Try Alka twrp
Click to expand...
Click to collapse
This also do not work for me - boot loop.
After this problems, I have to reflash whole system in order to have it bootable.
The latest ZCX-TWRP_REDMI_NOTE3-PRO_Kenzo_20161230.zip works for me. Thread can be closed.
When you start TWRP for the first time, you have to select "Keep Read Only"
Flash twrp without unlock bootloader ?
you need to format all data and reboot once to twrp recovery before flashing custom ROM
i'm on the latesr global rom and zcx works for me. maybe downgrade to an earlier version of global rom then flash zcx then upgrade to miui 8.
Related
While H2OS was loaded, I flashed TWRP. After that I rebooted to recovery, cleared all the essential things, flashed a ROM followed by a Gapps package. After that, when I chose reboot to system, the phone stays stuck at the OnePlus logo screen. I can't access the recovery either. I flashed 3 different versions of TWRP, but still couldn't boot to recovery. P.S.: Bootloader is unlocked
What can I do now?
UPDATE: BluSpark's modded TWRP works, but after flashing the ROM nothing boots
meraj99 said:
While H2OS was loaded, I flashed TWRP. After that I rebooted to recovery, cleared all the essential things, flashed a ROM followed by a Gapps package. After that, when I chose reboot to system, the phone stays stuck at the OnePlus logo screen. I can't access the recovery either. I flashed 3 different versions of TWRP, but still couldn't boot to recovery. P.S.: Bootloader is unlocked
What can I do now?
UPDATE: BluSpark's modded TWRP works, but after flashing the ROM nothing boots
Click to expand...
Click to collapse
You should fastboot flash old OOS 2 stock recovery, then full OOS 2.2.2 Rom.
Then root and install offical TWRP (not BS V41).
Then install what you want (but not Oxygen or hydrogen on MM)
Kéno40 said:
You should fastboot flash old OOS 2 stock recovery, then full OOS 2.2.2 Rom.
Then root and install offical TWRP (not BS V41).
Then install what you want (but not Oxygen or hydrogen on MM)
Click to expand...
Click to collapse
oh, root access is compulsory?
Just tinking about root, because I used it to install TWRP but you're right, fastboot flash could do it
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)
Hi,
After running out of patience i unlocked boot loader on my RN 3 (SD VERSION), and flashed lineage OS, but i did not get VOLTE on it.
To fix that i flashed some files again (and probably forgot to enable developer options), then i rebooted to the phone, and now the bootloader has locked again. I tried booting into EDL mode/TWRP recovery, but the device booted back to lineage OS.
I did not even flash GAPPS just to check if VOLTE is working(basically i booted into the system), now i cannot go to the EDL mode and also not into TWRP recovery. Please guide me on how to get out of this situtaion. I had unlocked bootloader by flashing MIUI 7 through EDL (replaced emmc, and then unlocked it in CMD through unlock-go command)
I am only left with lineage OS with no apps (Tried installing Play store and Play services, that also force closes).
Please help me out with this. I know i messed it up by probably not turning on the developer options before flashing the files.
Please let me know where exactly i messed up so that i do not repeat the mistake. And please guide me on how to unlock bootloader and flash stuff again. Thanks.
Hey just try to find advance restart option in developer options and from their you know what to do
N.G. said:
Hey just try to find advance restart option in developer options and from their you know what to do
Click to expand...
Click to collapse
Yes i found it, I can now boot into the TWRP recovery, but now that the bootloader is locked, i dont think i will be able to wipe or flash any rom. If i wipe i will be in bootloop.
I cant go to EDL. Is it possible to restore MIUI backup with bootloader locked??
Maheshnotani said:
Hi,
After running out of patience i unlocked boot loader on my RN 3 (SD VERSION), and flashed lineage OS, but i did not get VOLTE on it.
To fix that i flashed some files again (and probably forgot to enable developer options), then i rebooted to the phone, and now the bootloader has locked again. I tried booting into EDL mode/TWRP recovery, but the device booted back to lineage OS.
I did not even flash GAPPS just to check if VOLTE is working(basically i booted into the system), now i cannot go to the EDL mode and also not into TWRP recovery. Please guide me on how to get out of this situtaion. I had unlocked bootloader by flashing MIUI 7 through EDL (replaced emmc, and then unlocked it in CMD through unlock-go command)
I am only left with lineage OS with no apps (Tried installing Play store and Play services, that also force closes).
which twrp?
Please help me out with this. I know i messed it up by probably not turning on the developer options before flashing the files.
Please let me know where exactly i messed up so that i do not repeat the mistake. And please guide me on how to unlock bootloader and flash stuff again. Thanks.
Click to expand...
Click to collapse
phone booting or not?...u said gapps force closing...??
which twrp
Maheshnotani said:
Yes i found it, I can now boot into the TWRP recovery, but now that the bootloader is locked, i dont think i will be able to wipe or flash any rom. If i wipe i will be in bootloop.
I cant go to EDL. Is it possible to restore MIUI backup with bootloader locked??
Click to expand...
Click to collapse
What twrp you have have if it is zcx then just flash any rom and if you are wondering check this https://forum.xda-developers.com/re...ide-install-lineage-os-locked-t3546154/page39
And yes don't even try to flash your backup zip from miui backup but if it's twrp backup then you are good to go
ajeshmanu said:
phone booting or not?...u said gapps force closing...??
which twrp
Click to expand...
Click to collapse
Phone is booting. Running lineage 14.1, gapps also flashed now using TWRP.
So basically i can go to TWRP, not to EDL.
N.G. said:
What twrp you have have if it is zcx then just flash any rom and if you are wondering check this https://forum.xda-developers.com/re...ide-install-lineage-os-locked-t3546154/page39
And yes don't even try to flash your backup zip from miui backup but if it's twrp backup then you are good to go
Click to expand...
Click to collapse
I have TWRP 3.1.0.0 and not ZCX. BOOTLOADER IS LOCKED INDEED.
The backup is twrp backup, not MIUI.
So what you are saying is that i should UPDATE THE Current recovery to ZCX through flash image option(IN TWRP) right? And then flash SUPERSU?
And after that CAN I Wipe the currently installed Lineage OS, and then install it again along with CM firmware and VOLTE Patch??? (As mentioned here, https://forum.xda-developers.com/re...t/volte-patches-nougat-based-cm-roms-t3509257)
Please confirm, and if yes, please confirm the order of flashing of above three files.
The main issue is VOLTE.
Also, the backup that i took with 3.1.0.0 can be restored using ZCX Right???
I am not sure but to be on safer side just flash the miui backup first boot in the ROM , set it up ,then try to other stuff and after that try to install zcx twrp if you dont want the unlock your bootloader again
---------- Post added at 02:06 PM ---------- Previous post was at 02:02 PM ----------
Just have a problem that my network goes on and off automatically I am on RR if you face something like this in your ROM
Plz reply
How did u find ur bootloader is locked?
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.
Anyone have any solution for the flash to work with magisk?
If i uninstall and install SU my flash will work?
Replace the kernel with the MK2000, flashing it with TWRP after Magisk, and the flash will be back.
tremalnaik said:
Replace the kernel with the MK2000, flashing it with TWRP after Magisk, and the flash will be back.
Click to expand...
Click to collapse
There is an Oreo mk2000 kernel? I used it for nougat, I'll give it a look.
thunderc8 said:
There is an Oreo mk2000 kernel? I used it for nougat, I'll give it a look.
Click to expand...
Click to collapse
It's still a beta version, but on my phone is working perfectly.
You can find it here, in the same thread of the Nougat version: h850 mk2000 kernel
I installed the kernel and after magisk again but the flash light is not working again.
I get the same error.
I have to wipe everything again?
Never mind i just flashed mk again without flashing magisk again and its working.
thunderc8 said:
I installed the kernel and after magisk again but the flash light is not working again.
Click to expand...
Click to collapse
I get the same problem.
After flashing TWRP I do this:
don't wipe Data, but "format" data (you have to type "yes" to delete encryption)
intall Magisk-v17.1.zip
install xposed-v90-sdk26-arm64-beta3 (optional)
install driver Adreno 530 rev21 non treble (optional)
install as last zip: KERNEL MK2000 v1.0 Beta5 (for OREO)
reboot system
now flashlight works fine.
So installing "no-verity-opt-encrypt" (DM-verify) is not necessary.
P.S.
I was on Fulmics 5.5 (stock 7.x) with unlocked bootloader, the correct twrp flashing for me was this:
with LGUP
flash kdz android 7.x (flag on refurbish) (I tried upgrading directly to 8.x, but the G5 was gone in bootloop)
flash kdz android 8.x (flag on upgrade)
(the bootloader still remain unlocked, so you have not flash unlock partition with unlock.bin file)
Phase 2
Boot, skip all settings, Enable Developer, enable Debug USB and accept request permissions etc...
open ADB and type
reboot bootloader
fastboot flash recovery twrp.img
don't reboot!
remove cable, remove battery, reinsert battery
power on in recovery mode (correctly, or you have to return at Phase 2)
double yes for reset factory (to enter in recovery)
you should enter in TWRP recovery
Is there any way to fix the "flashlight" bug with the stock kernel, still with the stock recovery
and rooting with Magisk by patching the boot image beforehand and flashing it in fastboot ?
I tried using the mk2000 kernel, but no img image is provided for this, only a zip,
but I don't want to root by using TWRP and flashing zips.
Why, I want systemless root, in case OTA updates will appear.
Thank you.
Even though I'd really suggest you to install TWRP permanently (if you accidentally enter in the stock recovery, the whole internal memory gets erased permanently), you may try to install Magisk from TWRP and then flash again the stock recovery.img using fastboot.
By the way, the Magisk zip is systemless: it doesn't flash executables on the system partition; it's just packed as a zip file for convenience to be easily read by TWRP.
On the other hand, if you want both original kernel and Magisk with a working flashlight, you can't. Flashlight with Magisk only works with MK2000 kernel at the moment.
It's new version mk2000 kernel v2.0 stable version from 04 January 2019, for Oreo try it. I want to unlock BL and make root, pls tell us it is flash work ? Sorry for my English.
Wysłane z mojego LG-H850 przy użyciu Tapatalka
I din't try the latest version, but I'm currently using mk2000 with unlocked bootloader and Magisk, and everything (both root and flash) is ok.
Edit: I now have the latest version of mk2000, and I can confirm everything is ok.
My flashlight and camera flashlight are not working too. I have to back read just in case I am not the only one with the same problem. I see there is a lo of suggestion and I tried it and it worked like a charm. I used H850_v1.0-mk2000 to make it work.
BBCAtomic said:
My flashlight and camera flashlight are not working too. I have to back read just in case I am not the only one with the same problem. I see there is a lo of suggestion and I tried it and it worked like a charm. I used H850_v1.0-mk2000 to make it work.
Click to expand...
Click to collapse
read previous massages
https://forum.xda-developers.com/showpost.php?p=77832747&postcount=6