I need some help, I had Derpfest running and decided I wanted to start fresh with Bliss. Using fastboot I wiped the device, the device showed slot-a active I disabled dm-verity, switched slots flashed the boot img of the newest version of TWRP. My device shows the .72 firmware. I cannot get into the boot image of twrp the device gets stuck in a boot loop. Any insights?
I'm having a similar issue with a fresh flash of TWRP, and followed the same steps you did as recommended in the post instructions I was following but it bootlooped for me as well. Did you find a solution?
Smurgledorfcc said:
I'm having a similar issue with a fresh flash of TWRP, and followed the same steps you did as recommended in the post instructions I was following but it bootlooped for me as well. Did you find a solution?
Click to expand...
Click to collapse
Yeah, I ended up flashing an older version of twrp then updating via adb and then going through with the install
Related
Using "CWM-based Recovery v5.0.2.7 FULL".
I can't get my device to boot. I'm running the previous version of Energy's ROM (not most recent). However, I can get into recovery and fastboot easily.
All I have tried is to factory reset, wipe caches, and re-install Energy, but it still will not boot. It's gotten close - can see the splashscreen, but no further.
Battery is at 100.
What do I need to do get this baby going again!
P.S. The original problem is that I let the battery drain too low for it to fully boot.
Always read the OP for the ROM before you flash...
http://forum.xda-developers.com/showthread.php?t=1528024
NRGZ28 said:
...
How to Flash this ROM:
- Root your device
- Install TWRP custom recovery
- Install the downloaded ROM .zip found in post #3
- Make sure to do a Factory Reset / Wipe before installing ROM
Click to expand...
Click to collapse
The 3.0 Kernel discussions also mention the the symptoms you will encounter if you do not follow instructions...
http://forum.xda-developers.com/showthread.php?t=1591869
Hashcode said:
PLEASE use TWRP to flash this ROM. You will probably bootloop if you don't. If you experience a really long boot animation, double check your recovery (change if necessary) and try it again.
Click to expand...
Click to collapse
Oddly enough I used TWRP to flash. Somehow it reverted me back to CWM. I don't have a clue.
It's currently trying very hard to boot. Once I get there what should be my first steps?
If it doesn't boot, should I try and push TWRP through fastboot?
Edit: pushed TWRP (latest). Wiped and reinstalled. Still won't get past boot animation.
Can I transfer a new ROM file using fastboot or will I need to use 'fastboot update' to install a different ROM?
Should I try reverting to stock image?
I unlocked the bootloader following Motorolas steps. I then flashed the latest version of TWRP avaiable on the development forum and then flashed Lineage OS + the root zip they provide and gapps. I couldn't figure out how to get out of the bootloop so I've since gone back to stock. Any idea what I was missing?
TWRP:
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
Lineage:
https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
Did you read the notices and entries on the Linage last pages of the thread that people are having it fail on the install, the latest release? That would be a clue...
I even tried flashing Pure Nexus but that too was stuck on a loop. I left it for about 10 minutes as it was loading. :/
I did the same thing like you on my first attempt, on my second I was able to install Lineage OS successfully. I'll provide the steps I did.
First attempt steps:
1. Unlocking the bootloader using Motorola website
2. Installing TWRP from the same link in your post.
At that point I tried booting the phone, but the phone was booting to TWRP only, tried wiping, format data from TWRP with no luck.
3. From TWRP flashed Lineage OS zip file and GAPPS nano package (the latest version of TWRP is able to see SD card).
At that point I was able to to boot LOS only after executing "fastboot erase user data". Doing the same from within TWRP was not doing the job. The problem was that after each reboot the phone was getting into bootloop again and "fastboot erase userdata" was necessary.
4. At that point I noticed that TWRP thread starts with warning that you have to install a patcher to disable this "verity" feature of the bootloader may be. And I installed the patcher "Verity_FE_patcher.zip"
The patcher didn't fix the issue and went back to stock Nougat using the guide below:
https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
First I tried "flashall.bat" , but it didn't wor.k and I flashed all the files manually using the guide . The phone booted normally and I updated it with one OTA update.
Second attempt steps:
1. I wanted to install the verity patcher before anything else and I boot TWRP 3.1.0.1 without flashing it. It booted normally and I realized that the SD card was formated and the patcher zip file is not there. I reboot the system and the phone got in bootloops again even the TWRP was not installed. I coppied the patcher zip, LOS zip, GAPPS zip on SD card . I tried to boot (without flashing) TWRP again, but for some reason TWRP was not able to boot.
2. I flashed TWRP
3. Booted TWRP and flashed verity patcher.
4. Wiped from TWRP and boot the system
At that point I was able to boot the stock firmware with TWRP installed and I was able to restart the phone normally.
5. Flashed LOS and nano GAPPS
Now everything seems to work properly.
Hope this will help.
Thanks. I'll give this a shot tonight. Our first attempts sound very alike.
I updated TWRP in TWRP via zip flashing and now whenever I try to reboot my phone, it only boots back into TWRP.
Previously, I was unlocked bootloader and rooted on stock.
Would appreciate any help. Thanks
I've never installed TWRP on this phone, but here is one thread Google returns that seems to be similar.
https://forum.xda-developers.com/pixel-xl/how-to/twrp-bootloop-flashing-twrp-t3533765
One relevant thing that has changed since the time of that discussion is that the May and newer bootloaders require a signed boot image. When I installed the May update with SuperSU without signing the boot image my phone simply ended up switching to the other slot, but again I didn't have TWRP installed. There is a zip for signing the boot image and further discussion here.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Thanks for the response. Looks like I have to flash factory image and then the verified boot signer. I'll give it a shot and report back.
Fixed this rather easily using the June factory images. Flashed using flash-all.bat (and removed the -w) and things are updated and back to square one. Interestingly, I didn't need to sign the boot image.
Thanks for the help.
facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse
TonikJDK said:
facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse
Do you need to use the signed boot image file if you are flashing an unrooted custom Rom? I thought you needed to use it when flashing anything that changed the boot image from stock, including flashing TWRP if it's going to be installed on the phone.
Actually now that I thought about it the signed boot image is SuperSu specific, isn't it?
Click to expand...
Click to collapse
My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.
alluringreality said:
My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.
Click to expand...
Click to collapse
yeah i am stock rooted with twrp on june 7.1.2. I had to flash the verifiedbootsigner-v8 when rooting with magisk and twrp. I did NOT have to flash it when flashing elementaX 1.12
We're can I download v8?
Sent from my Pixel XL using Tapatalk
The first post from the following link has the latest version of the Verified Boot Signer attached.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
335Deezl said:
We're can I download v8?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
cognitivedissonance said:
So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is Pixel XL forum.
Slowclap
Phalanx7621 said:
Slowclap
Click to expand...
Click to collapse
Hi, I flashed the FOTA Kernel with TWRP 2.8.7 onto my phone and inside TWRP I flashed the recovery with the 3.0.2 TWRP image (telling me "Successfully flashed")
But after rebooting I still have TWRP 2.8.7
Using windows command line and "fastboot flash recovery "TWRP.....img" I get this "FAILED" message.
What am I doing wrong?
I even flashed the phone back to stock and then followed these instructions but same result.
Is my phone broken or sth?
Hi H4NNE5, the Xperia M does not have a recovery partition. The TWRP recovery is included in the boot partition when flashing the kernel. Try to upgrade with the TWRP-Manager if your phone is rooted.
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
H4NNE5 said:
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
Click to expand...
Click to collapse
Try this command
fastboot flash boot twrp_name.img
So I've been following DavidRocher's tutorial to install a custom rom (the one that's linked around here the most), I've followed it before installing his RR official rom but as the room started showing a lot of issues, I decided to wipe everything and install something a little more stable such as lineage. I didn't care for Gcam or etc so I wouldn't have minded not having those at all.
However, even after following these steps now once again, even flashing the stock rom as asked for a brand new, clean install, twrp (offain) is hitting me with Error 1s on *any* custom rom that I try installing. I can seemingly flash the stock rom without any issues, but anything else and it's a solid no from TWRP.
Am I missing something?
The error itself is Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError) Updater process ended with Error: 1 error installing zip file.
I've been wiping, booting, rebooting, re-installing the custom rom, checking the unlocked bootloader and I have had no progress at all. I do not know why this is happening, could anyone please help me?
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
JumboTSB said:
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
Click to expand...
Click to collapse
Please can you describe exactly the steps that you did from boot to recovery and so?
SubwayChamp said:
Please can you describe exactly the steps that you did from boot to recovery and so?
Click to expand...
Click to collapse
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
JumboTSB said:
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
Click to expand...
Click to collapse
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
SubwayChamp said:
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
Click to expand...
Click to collapse
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
JumboTSB said:
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
Click to expand...
Click to collapse
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
SubwayChamp said:
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
Click to expand...
Click to collapse
I guess I'll try it with orange when I have a little more time then.. Spent the last 10-12 hours trying different procedures with twrp and they were pretty fruitless... It's still so weird, I'm definitely not new to flashing roms, I've done it so many times in the past and this is the very first time I get this sort of behavior. I'll update this once I try out OrangeFox.
hi!
your method has always worked for me, but this time I always get error 1.
I tried to install the pixel experience and lineage and nothing works, can you help me?
:good: