think I may have bricked my boot. when installing TWRP, flashing the TWRP.img I flashed it to the boot. now my device won't boot. but goes into recovery. I wasn't able to do a backup TWRP said I didn't have enough space. however i can confirm my TWRP works and decrpyts lol
TWRP Coral [Official]
- Thread starter bigbiff
- Start date
You will need to reflash a stock boot image from google.
I'm not sure if I'm doing something wrong but running FLORAL on the current May update and successfully can boot to TWRP using fastboot but after going to install and installing image to boot partition and choosing both slots I reflashed Magisk as the TWRP website says that flashing TWRP removes root but then phone fails to boot and just loops recovery. Had to reflash root patched stock boot to recover phone. Is TWRP still not flashable and only from boot or did I do something wrong? Otherwise TWRP seems to work as expected when booted to. Just can't make it permanent.
thanks I googled and I found out the same. luckily I kept a copy of the patched_magisk file. and just flashed that. how do I properly install twrp? or as the post above said, "make it permanent" after fastboot boot twrp..
Last edited:
Please find instructions in Post 2. Make sure to install a custom kernel if touch doesn't work when rebooting to recovery mode.
understood that, now... at the install image screen. when flashing twrp.img in the twrp app. do I swipe to confirm the twrp.img to the boot, super or install recovery ram
Install Recovery Ramdisk. I will make the verbiage clearer in post 2.
This is where I was having my problem I was following the installation instructions from the TWRP website and as you see in the screenshot I circled where the confusion is it says something about installing to both boot slots which I think is going to screw other people up as well somebody should fix that verbiage so that it says install to recovery RAM disk
Attachments
The installer repacks the TWRP ramdisk into the current boot ramdisk on both slots. The verbiage is correct as far as I can tell. We use that on all the A/B devices as a template.
This is true but in the instructions it doesn't mention choosing the recovery ramdisk option before installing. What I'm saying is that this should be added so people don't make the mistake I did which is take the mention of flashing to both slots meaning I should choose boot and both slots while installing the image which is what I did the first time before I saw your earlier response said to choose the ramdisk one.
"3. Go to Install
4. Touch Install Image Recovery Ramdisk
5. Select your TWRP boot.img from /sdcard"
Swap #4 and #5: I had to select the TWRP image first, then got the option to "Install Recovery Ramdisk". I was on Sultan Kernel, installed, and I'm able to reboot to recovery (TWRP) without issue so far.
I'll test it out tonight out of curiosity since I didn't try TWRP on this device yet. Been having random issues, so it's time to fresh flash.
I did a backup of data only, successfully. When I checked the TWRP folder once booted into Android, there was nothing. I rebooted into TWRP, went to restore, and there was nothing to restore.
Any device with recovery in boot needs to have recovery reinstalled by using the install ramdisk method when choosing the image to repack recovery from. Please do not flash the boot.img directly to the boot partition.
Can you use adb and use su to use the ls command to list the contents of /data/media/0?
I'm having the same issue as @neejay01 . I did a backup of all partitions (excluding misc). While I am still in TWRP after the backup, I can see the backup when I press restore. But when I reboot the phone I cannot see the folder in any file explorer apps. The ls command does not show the folder either
I tried again and it did the same thing, no files in any file explorer (with root). So I tried for a third time, this time I changed the backup name. Before I rebooted I pull the contents of data/media/0 with adb just to make sure I had the files. I rebooted and the files were there in a file explorer. So I deleted all the files and tried the backup again, this time leaving the name auto generated and it worked fine. Not sure why it didn't work the first few times and now all of a sudden works. I am going to try a new rom and I will see how the restore works
*Forgot to add this is the A11 test version*
*Forgot to add this is the A11 test version*
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
-
77[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [/B]
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
coral Device Config: https://github.com/bigbiff/android_device_google_coral
A11 Testing:
Please test and let me know if anything isn't working.
DOWNLOAD:
Please go to https://twrp.me to download the recovery image.
Old info:
- Credit to @Freak07 https://github.com/freak07/FLORAL - using his kernel as a base for Coral/Flame TWRP
http://twrp.me30
Repacking is still being worked on. Fastboot only is workable. I have mentioned this in the thread.
For people who want to know, I am working on ramdisk issues I am having before repacking.
Please don't leave passive aggressive comments in the future.29Hello, I released a new test image:
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test5-coral.img
- fix restoring of persist partition
- fix restoring of super partition29
There has been a fix posted to our gerrit and merged. I am working on a ramdisk issue and will put a new test build that allows restore of super.24Hello, I was able to get repacking working, however you need to use a kernel with LZMA ramdisk support. I am using Kirisakura-FLORAL_5.2.2.zip for testing.
Also I am now using @Freak07 FLORAL kernel as a base for the fastboot image in order to support the newer DTBO image from R.
Please see the download in the FP.
You can repack TWRP into the boot ramdisk with this version, and reboot to recovery is working. I need to test magisk next.
