Hi
I've tried 3 different twrp images, all supposedly bumped (take this one for example), but when I try to boot to recovery with any of them I still get the boot certification verify error and can't get into recovery
running rooted 5.0 stock wiped, installed by instructions in linked threads
Thanks
update: used autorec, can now access recovery... but it's twrp 2.8.6... can I install fulmics on this version, or how do I update it?
update 2: TIL that you can update twrp from inside twrp and it still works, but that still leaves me confused with the above problems
Related
Hi,
I've just tried and failed to install the "cm-12-20150218-NIGHTLY-nicki" ROM on my phone. Specs are:
Official Android 4.3 Firmware
Model: C1904
Timeline:
Unlocked bootloader according to instructions at http://forum.xda-developers.com/showthread.php?t=2484428
Phone then got stuck in official boot animation (the colourful one)
Didn't bother flashing the "Elixer" kernel as suggested in above thread
Used fastboot to flash the boot.img from the CM zip file
Booted to recovery
Wiped data & cache
Flashed CM & GApps from external SD card
Restarted phone
Phone showed big Android robot animation and then went back to CyanogenMod Recovery
Looking at logs showed "Cannot load volume /misc" error
Found a forum post saying this thread helped with the above error: http://forum.xda-developers.com/xperia-m/development/cwm-twrp-recoveries-cm12-lollipop-t2979752
Tried flashing TWRP recovery (http://forum.xda-developers.com/xpe...very-cwm-twrp-recoveries-custom-roms-t3016507) within CyanogenMod Recovery, but it said the file integrity was bad or something
Used "fastboot flash boot FOTAKernel.img" to flash the above, which worked
Tried to wipe data from within TWRP, but got "failed to mount /data" errors
So the phone is now in a state where:
I can only boot into TWRP
I can't use ADB since the program on the computer won't detect the phone
Fastboot still works
I can't boot into Android
Something seems wrong with "/data"
Any ideas about where to go from here?
I was able to use Flashtool to flash the official firmware back on and boot into it as normal. After doing that and restarting the procedure to install CM12 2015-02-19, this time it installed just fine.
Although I still got errors about "Cannot load volume /misc". Hopefully they don't matter...
Now you have CM12 installed and it is working?
Had the same errors when I tried to flash CM12. Flashing CM11 worked fine but I could not get CM12 to boot...
xa.fr said:
Now you have CM12 installed and it is working?
Had the same errors when I tried to flash CM12. Flashing CM11 worked fine but I could not get CM12 to boot...
Click to expand...
Click to collapse
Yeah; it's installed and working fine. When I flashed the official firmware, (Android 4.3) I told Flashtool to flash everything including the kernel. That seemed to put the phone back into a good state, which allowed me to install CM12.
I'm not sure what caused the problem in my case. Maybe it was unlocking the boot loader.
Hello lads,
I'm having the following problem:
I wanted to install the latest Dirty Unicorns weekly, as I'm using Multirom TWRP, I also reinjected Multirom after install, which places an openscript recovery script for twrp which is run everytime I try to boot into twrp, which doesnt get removed as I'm not able to boot into the rom, because bootloader gives out a "secure boot error" because the rom is not bumped anymore because of that. Can I somehow get into twrp without running that open recovery script?
Edit:
Flashed the usual TWRP via fastboot, now my device is operating again!
I was running an unlocked one plus 3 on OxygenOS 4.0.2 (Android Nougat) and have TWRP installed. As 4.0.3 got released yesterday, i tried installing it today but i accidentally hit install on the OTA update setting which caused my phone to reboot. Now my phone won't boot into the os, i get a black screen after 'powered by Android'. I tried getting into Recovery however i get the same response, a black screen. I do not think it is hardbricked as the Fastboot still works and when i go into fashtboot it states that the OEM is 'unlocked'. I have personal data on this device pls can someone help. I do not know what i should do> How do i boot into recovery without crashing?
Is it possible to install twrp again with the PC? I had once also the same problem, install it again and after that it booted again into recovery.
Just install TWRP from fastboot, then you'll have access to internal storage by TWRP
It's happening because it's trying to send you to recovery which is twrp 3. 0.4-1which is bugged so just go to fastboot and flash twrp 2.0.4-1 and then try booting in.. You can even update the phone by flashing the update zip by oneplus from recovery
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 have a Pixel C, rooted using the Nexus Rootkit, TWRP and SuperSU.
All was fine and was on build N2G48C.
I had an OTA notification for Oreo, so I downloaded the OPR6.170623.010 Oreo OTA file, and used FlashFire to apply this.
Now everytime it reboots it goes past the Google logo, then to the "waiting for fastboot command" screen. I've tried rebooting to Recovery and I get the same thing!
Google didn't seem to help, so please can anyone else help?
I was manually flashing rather then using flashfire, but I was getting the same problem. First, flash just the stock room (no root or TWRP) and check that it boots. Mine would, but every time I tried to flash TWRP, it would bootloop to fastboot.
You may want to download the full rom, not just the ota. You can modify the flash batch file to not wipe the tablet, or just flash the components.
What was finally successful for me was to flash TWRP and NOT let it finalize. It should ask if you want to mount R/W so it can keep the rom from overwriting the recovery. I told it no, then flashed the Magisk zip for root. I haven't tested SuperSU, but just replace it here to try. This got me a proper boot to Oreo, with Magisk working correctly.
If I understand it right, and I haven't booted to recovery to check, the rom will likely have overwritten TWRP. Worst case, I have to reflash recovery whenever I want to do a backup or update my rom, but that isn't something I do often on this tablet.