Database Info

No fastboot in recovery after TWRP installed failure

Ok.... So i unlocked my bootloader on a verizon pixel and installed magisk with a patch boot image. no problem
I just tried to install TWRP (3.2.2). I booted the image first, the flashed the TWRP zip in the booted image. Then TWRP would boot, but only TWRP would boot. it would never progress to booting up the rom.
So i found a thread that suggested flashing the magisk patched boot image.... that just made it worse. It would only boot to recovery... and NO FASTBOOT. I was able to get to the menu and use adb to side load the latest OTA. Now i can boot into the ROM and use the phone as usual
However, I still don't have fastboot in recovery mode. I don't think its drivers. I must have mucked up recovery. It gotta be related to the TWRP snafu. I can boot into the stock boot loader and my PC beeps and recognizes the phone, when i use the arrows to go to recovery, my pc loses the device. My PC just can't see the pixel in recovery mode.
Not sure how to proceed
Can I side load the factory image after removing the wipe tag (-w)? Do i need to factory reset?

Am an idiot.... fastboot works in bootloader.... please delete

[Recovery Release] Working TWRP for Sony L1 (G3311 Single SIM others to be confirmed)

Requirements:
1. Bootloader Must Be Unlocked.
2. Have a backup of your working Magisk Patched boot.img saved to your External SDcard.​A little INFO:
The Sony L1 recovery seems to be disabled by SONY for some unknown and Probably stupid reason.
I have tried all ways to get the TWRP and Stock recovery to boot up from the fotakernel partition (recovery) but TWRP and even the stock recovery refuse to boot.
Anyway to cut a very long story short I am releasing this TWRP which is 95% functional and needs to be flashed to the boot partition
Working Method/flow:
Make sure you have a Back up of your working Boot.img "You know the one you used to root the device in the first place".
For ease of use You can use this app by XDA dev @wanam (Thread here) app on playstore Here You can also use this app to flash the v5-twrp-l1.img to your "boot" partition or you can go old skool and use dd (Via adb shell) or use the Magisk patched_boot.img you first rooted with..
Make SURE to Copy this working boot.img to your External SDcard.
When you require TWRP flash the downloaded TWRP to your boot partition using Fastboot (cmd's below) or the above app then reboot
You will now boot to TWRP.
Do what you need to do in TWRP.
IMPORTANT:
Remember Just before you leave TWRP go to INSTALL choose your external SDCard choose "image" from the install screen find your boot.img and select "boot" with the little radio button.
Once flashed choose reboot system.
Now when you boot you will be back to normal :good:
Things Not Working:
1. You will not be able to mount encrypted data therefore you would need to FORMAT your data and then leave it unencrypted.
SuperSU and Magisk will disable forceencrypt for you.
2. Does not Charge or show battery % so I don't know if it's actually charging. (Probably Qnovo battery module used by sony)
It will probably work on all variants but I am not able to test that.
It's use is for backups and restores wipes and installs for which it seems fully functional. :good:
Install Instructios.
Boot to the bootloader then
Code:
fastboot flash boot v5-twrp-l1.img
Then
Code:
fastboot reboot
Download HERE v5-twrp-l1.img

Hi @bigrammy!! I have it booting ok, obviously encryption is not working! I was able to do a backup but couldn't boot back into system, just keeps going back to twrp! I had to flashi the patched 3313 boot image from another post to get back into system! Good work though! Tested on g3311

Chronic2k13 said:
Hi @bigrammy!! I have it booting ok, obviously encryption is not working! I was able to do a backup but couldn't boot back into system, just keeps going back to twrp! I had to flashi the patched 3313 boot image from another post to get back into system! Good work though! Tested on g3311
Click to expand...
Click to collapse
:laugh:
Ok maybe I should update the OP as it seems it's not really clear enough that obviously the boot is replaced by the recovery.
Method would be make sure you have a Back up your working Boot.img You know the one you used to root the device in the first place.
You can also use dd (Via adb shell) or a app from the playstore or better still use the Magisk patched_boot.img .
Copy this working boot.img to your External SDcard.
When required flash the recovery to your boot partition using Fastboot then reboot
You will now boot to TWRP.
Do what you need to do in TWRP.
Then just before you leave TWRP go to INSTALL choose your external SDCard choose "image" from the install screen find your boot.img and select "boot" with the little radio button.
Once flashed choose reboot system.
Now when you boot you will be back to normal :good:
OP Updated let me know if it's clearer to understand now.
Thanks for reporting back. :good:

I'll give it a go! Many thanks! Just one question though. How do I enter recovery mode from then on? Is it still power down, power and volume down yeah?

Chronic2k13 said:
I'll give it a go! Many thanks! Just one question though. How do I enter recovery mode from then on? Is it still power down, power and volume down yeah?
Click to expand...
Click to collapse
I don't think you have really read or understood the OP
You are only ever flashing the "boot partition".
When you need to use TWRP you flash the TWRP.img to the boot partition and when your done you flash back your boot.img again to the boot partition as in the OP.
BTW Have you ever been able to enter the STOCK recovery using Power and Volume Down or using any commands
My phone could not enter the STOCK recovery at all let alone a custom one and since no one ever replied to my question about this I assumed this was the case for everyone as many sony devices from 7.0 had the recovery disabled?

I'm unable to get into stock recovery too!

So,
If we don't have a Recovery partition maybe we can
Create one...
Tutorial in here
https://iwf1.com/how-to-re-partitio...-all-options-included-change-size-fs-type-etc
I'll try it if i have time.

I tested twrp 2 times
Worked every time.
I've tried to install superSu.zip via twrp, looked all right, rebooted the phone and now it's in bootloop for over 2 hours...
It's getting hotter... i ca't turn it off
The only thing that works is keeping Power and Volume Up pressed and it looks restarting...
What can i do to revive it safely?

alegatorul said:
I tested twrp 2 times
Worked every time.
I've tried to install superSu.zip via twrp, looked all right, rebooted the phone and now it's in bootloop for over 2 hours...
It's getting hotter... i ca't turn it off
The only thing that works is keeping Power and Volume Up pressed and it looks restarting...
What can i do to revive it safely?
Click to expand...
Click to collapse
Mate you really need to be careful unless you really know what your doing
You will likely brick the phone if you continue to blindly mess with re-partitioning and the like.
If you were in TWRP which was flashed to the boot partition as directed in the OP then flashing the supersu.zip will simply modify your TWRP.img not your boot.img since TWRP is living in the boot partition at the time you run the .zip hence your looping.
This device has bootloader issues since it will not allow the booting of another partition except "boot" recovery, fotakernel, rdimage, all tested all failed to boot the TWRP recovery and stock recovery.
There is another method used by some sony devices but this will need to be heavily modified for this MediaTek SoC and will require a lot of study and script re-writes.
Spending all this time on a device that's pretty much obsolete before it was launched since it's not planned to receive oreo and Sony 90% locked down the bootloader is kinda futile so use the phone for what it is then throw it in the bin when done in a year or two.

Mate, you are right

Hi, please make recovery for L1 G3312 i hope you can do it.

tweak8 said:
Hi, please make recovery for L1 G3312 i hope you can do it.
Click to expand...
Click to collapse
I think this one may very well work for the dual SIM also so please try it and then report back with some actual details.
eg: bootloader status, firmware version, your region, etc etc.
Thanks.

Works great on the G3113 model, thank you for developing this! Now hoping to find a custom rom to install via .zip.

This "HERE v5-twrp-l1.img" is working in my Xperia L1 G3312.
But, after installing TWRP, phone does not get into boot normally. Everytime it boots into recovery mode. I think that it needs separate twrp partition. This twrp is overwriting the main boot. If anyone can make separate partition for TWRP recovery. This problem will be solved.

Hello. I ignored all your post like a retard and basically just went to the last step to flash the image. The twrp works but it wouldn't boot into normal mode but just boot to twrp everytime so I downloaded some random boot image I saw online and installed it. Now it's just stuck in the sony logo and won't even turn off. Is there anything I can do or is it rip for good?

dumb person said:
Hello. I ignored all your post like a retard and basically just went to the last step to flash the image. The twrp works but it wouldn't boot into normal mode but just boot to twrp everytime so I downloaded some random boot image I saw online and installed it. Now it's just stuck in the sony logo and won't even turn off. Is there anything I can do or is it rip for good?
Click to expand...
Click to collapse
No it's only the boot.img Flash the boot.img in this thread https://forum.xda-developers.com/xperia-l1/how-to/root-l1-g3313-magisk-t3693350 if you can get into fastboot that is.
If not then use FlashTool to flash the stock boot.sin and system.sin only. That should get you working again.

This "HERE v5-twrp-l1.img" is working in my Xperia L1 G3312.
But, after installing TWRP, phone does not get into boot normally. Everytime it boots into recovery mode. I think that it needs separate twrp partition. This twrp is overwriting the main boot. If anyone can make separate partition for TWRP recovery. This problem will be solved.
In twrp mode, I can do everything smoothly..... but phone does not get into boot normally..... After installing stock boot again, phone boot into normally, but twrp has gone completely..... So, it is clear that boot & twrp partition overwrites each other due to no separate partition.... So, we need separate partition for boot & twrp.... then everything will be solved...

bigrammy said:
No it's only the boot.img Flash the boot.img in this thread https://forum.xda-developers.com/xperia-l1/how-to/root-l1-g3313-magisk-t3693350 if you can get into fastboot that is.
If not then use FlashTool to flash the stock boot.sin and system.sin only. That should get you working again.
Click to expand...
Click to collapse
I downloaded the boot from the link you posted and flashed it. Now it phone works again. Many thanks!!

riadjblicd said:
This "HERE v5-twrp-l1.img" is working in my Xperia L1 G3312.
But, after installing TWRP, phone does not get into boot normally. Everytime it boots into recovery mode. I think that it needs separate twrp partition. This twrp is overwriting the main boot. If anyone can make separate partition for TWRP recovery. This problem will be solved.
In twrp mode, I can do everything smoothly..... but phone does not get into boot normally..... After installing stock boot again, phone boot into normally, but twrp has gone completely..... So, it is clear that boot & twrp partition overwrites each other due to no separate partition.... So, we need separate partition for boot & twrp.... then everything will be solved...
Click to expand...
Click to collapse
Yes but Sony Disabled the recovery partition (fotakernel) by design so you can not boot from it.
The OP is clear about the need to flash the TWRP to your boot partition and the reason I also give full instruction in the workflow/method but people simply don't read anymore it seems. :crying:
TWRP can be injected into the boot.img so you can boot normally or boot TWRP using the volume keys at boot time but I can't be bothered working on this since Sony are not going to update the Android Version.
While the phone is OK I have far better phones to spend my time on at the moment.

how to backup boot.img without root? if its impossible then how do i root this phone?

Bootloop after flashing TWRP

Recently I decided to try flashing a custom rom onto my old phone, a Gionee F103 Pro. Since it is quite obscure it isn't officially supported by twrp, but I managed to find an unofficial build. I unlocked the bootloader and flashed twrp using fastboot, and according to the console it was successful. When I booted my phone twrp began to load, but then there were multiple 'unable to mount' and 'failed to mount' errors and it rebooted. This has been repeating for almost an hour now. It's unresponsive to any button presses, and it won't show up on the device manager either. The only way I've got it to stop was by removing the battery. I've tried fastboot mode, recovery mode and regular boot but they all end up the same. I'd be grateful if anyone could could help me fix this.
Thanks!

fibonazi said:
Recently I decided to try flashing a custom rom onto my old phone, a Gionee F103 Pro. Since it is quite obscure it isn't officially supported by twrp, but I managed to find an unofficial build. I unlocked the bootloader and flashed twrp using fastboot, and according to the console it was successful. When I booted my phone twrp began to load, but then there were multiple 'unable to mount' and 'failed to mount' errors and it rebooted. This has been repeating for almost an hour now. It's unresponsive to any button presses, and it won't show up on the device manager either. The only way I've got it to stop was by removing the battery. I've tried fastboot mode, recovery mode and regular boot but they all end up the same. I'd be grateful if anyone could could help me fix this.
Thanks!
Click to expand...
Click to collapse
Can you flash a copy of stock recovery.img via fastboot?
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Can you flash a copy of stock recovery.img via fastboot?
Click to expand...
Click to collapse
I tried to boot my phone into fastboot but it goes straight to twrp instead. My PC doesn't seem to detect it either.

fibonazi said:
I tried to boot my phone into fastboot but it goes straight to twrp instead. My PC doesn't seem to detect it either.
Click to expand...
Click to collapse
If there is a LineageOS ROM or some other custom ROM available for your device, try flashing a ROM.
If that doesn't work...
Flash a copy of stock recovery.img via TWRP. TWRP has the ability to flash .img files.
Or, if you can find a copy of your stock recovery that has been converted into a TWRP flashable .zip, you can flash that .zip via TWRP then reboot the device into recovery mode to see if it boots stock recovery.
If you can't get that to work, TWRP has a terminal emulator built in, you can try flashing stock recovery.img using dd commands in the TWRP terminal. You'll have to research your devices partition structure to get the correct dd command to make sure that the recovery gets flashed to the correct partition.
I'm only saying to do all of this because it seems that screwing with the recovery partition caused the issue, maybe, restoring/repairing the recovery partition might fix the issue.
If not, you'll have to find a fix that involves flashing your stock firmware or stock system.img.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
If there is a LineageOS ROM or some other custom ROM available for your device, try flashing a ROM.
If that doesn't work...
Flash a copy of stock recovery.img via TWRP. TWRP has the ability to flash .img files.
Or, if you can find a copy of your stock recovery that has been converted into a TWRP flashable .zip, you can flash that .zip via TWRP then reboot the device into recovery mode to see if it boots stock recovery.
If you can't get that to work, TWRP has a terminal emulator built in, you can try flashing stock recovery.img using dd commands in the TWRP terminal. You'll have to research your devices partition structure to get the correct dd command to make sure that the recovery gets flashed to the correct partition.
I'm only saying to do all of this because it seems that screwing with the recovery partition caused the issue, maybe, restoring/repairing the recovery partition might fix the issue.
If not, you'll have to find a fix that involves flashing your stock firmware or stock system.img.
Click to expand...
Click to collapse
Actually, the problem I'm having is that twrp runs into an error and shuts down before I can do anything on it. It is stuck in an endless boot loop and is unresponsive to any button or screen presses. I have a lineage os rom, but I don't have any way to flash it right now. Is there any way to make it responsive again? Or any way to connect it to a pc?

Qualcomm Crash Dump Mode - PLEASE HELP

Hello!
I wanted to update my oneplus 8 from 11.0.4.4 to newest version. OTA was not working idk why. I had magisk in place and I patched magisk to second partition or something like that [I dont remember how it was called] - I'm sure this is the reason of the problems. I turned off devices and wanted to boot into recovery, but suddenly it boot into Qualcomm crash dump mode with message: Attempted to kill init! exitcode: 0x00007f00 do_exit - that's all. I can't boot the system, I can;t boot into recover, I flashed patched boot, I flashed recovery - none of these works. Fastboot is present and recognized by PC.
First question can I do some backup through fastboot? To be honest I was not prepared for such problems. APKs are not even such a problem I care more about photos, documents and other data.
Can I flash some rom and restore phone back to life without wiping my personal data?
Please can you help me? I tried with some tutorials, but no success...

Maybe an idea would be to load TWRP recovery and then do backup, but how to boot into recovery when even after flashign recovery or booting via fastboot it enters in qualcoom crash dump mode. Something must be corrupted, but is it possible to fix some partition just in order to flash recovery to do backup of the files?

Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.

Hi, I'm facing the same problem but probably not for the same cause.
I'm right now on PE12 (with PE recovery) and wanna install TWRP recovery to then move on another A12 based ROM (Evox).
Basically my goal is to replace PE recovery with TWRP. So when trying to install twrp after downloading the ZIP file onto the phone, when I fastboot the img file, it sends me to the crash Dump mode.
How can I fix this? please note I have no issue booting to the main OS.

phone stuck in bootloop

i don't know how else to describe this, i was flashing a custom ROM, then flashed magisk and now my phone is stuck in bootloop unable to go to recovery or system, the phone boots then black screen, etc etc, the same goes for recovery except it is faster (i reflashed recovery and it still happens) unable to do basically anything other than stay in fastboot mode.
what should i do?
edit 1: i can reboot to recovery and only be able to access shell.

Enter fastboot and flash recovery again. Brigudav's TWRP is the most used one. Gringo80's TWRP is new but seems to be working as others have written. (Both are unofficial and a take or leave, we don't have their source code, unfortunately.)
Right after flashing reboot to RECOVERY (not system). Can do with fastboot command or by holding button as usual. Alternative: reboot to recovery image file itself.
Once in recovery, format data (the option that has to type "yes" ). Reboot to RECOVERY again. Wipe cache, dalvik.
Reboot to system. Probably will work if your custom ROM was flashed properly.
Otherwise you can do everything again and also reflash ROM.
EDIT: I missed the Magisk part. So, while in recovery, dirty flash same custom ROM again. Or alternative: rename the Magisk file to uninstall.zip and flash it....this will restore your original boot and completely clean Magisk.
After you properly booting to system, then you can again try install Magisk.

why does flashing TWRP and booting to it directly work? i don't know! but it worked!
it seems that the custom ROM i installed is probably corrupt and flashed anyway ( i reflashed dirty/clean to make sure ) thanks for your help.