HELP - stuck in fastboot/bootloop, can't reach after Sony logo - Sony Xperia XZ2 Compact Questions & Answers

Hi guys!
Today I tried again to install TWRP on my Sonyh Xperia XZ2C because LineageOS Recovery doesn't provide Nandroid backup, which is a shame.
I tried many ways described over the web, none of those worked, and I ended up with a boot loop at startup with that naughty message "your device is corrupted it cannot be trusted and will not boot". I can't boot to Lineage, neither to recovery. I'm stuck.
With device turned off, I can eventually press volume down, plug it to computer, access fastboot mode (blue led), flash+boot the LineageOSrecovery.img, then the device restart, Sony logo appears... and that's all, I'm stuck with logo in boot loop, and I can't go anywhere further.
I tried to change boot slot (without knowing if it could help with this problem at all) but I alway get "unknown option".
I'm panicking right now, I can't find any way out to this bootloop, if someone could help it will be sooo appreciated!
I tried hard to find a solution for 4 hours now, I'm completly stuck and I can't even sleep. That's why I finally reached out here.

For an unknown reason, I succed to boot on Lineage Recovery (not TWRP) this morning. I flashed LineageOs rom.zip using adb sideload. After rebooting, the recovery tolds me that I had to wipe everything because the system partition seems to be corrupted, so I did.
I'm a bit tired to lost everything since I made all of this to do Nandroid backups with TWRP........ but I have a fresh new install, my phone works again so it's fine.
But I still need to make Nandroid backups. If someone had ever successfully booted/flashed TWRP on his XZ2C without bricking it, It will be really appreciated for sharing is knowledge

Related

Recovery induced reboot loop - help!

I need help understanding why I'm stuck in reboot loop with my EVO 4G.
I originally was trying to root the device using unrevoked3 but getting the ERROR "Backup CID is Missing" message and unable to proceed. I followed the instructions at http://androidforums.com/evo-4g-all-things-root/194918-rooting-dummies.html which talk about troubleshooting this. It talks about going into recovery mode to see if I've lost the recovery mode which I did (black screen with phone and read arrows). It says to reboot but I was unable to so I unplugged the battery.
Since then I have been stuck in a mode where the device boots but the sdcard is not recognized and upon completion of boot up it shuts down and vibrates five times. I did a bunch of research last night on understanding what I thought I needed to do alleviate this. My thought was since I was stuck without a recovery image I need to flash new one. At this point I'm fine with not being rooted with all the trouble I've had.
I downloaded the latest stock recovery rom (3.70.651.1) from http://androidforums.com/evo-4g-all-things-root/259446-clockwork-amon-ra-pc36img-files.html and pushed it to my sdcard under the name PC36IMG.zip (with two files .info and recovery.img). I restarted my phone via HBOOT and it sees the zip file, reads it in, goes to checking and then does nothing (back to HBOOT screen). I don't get what I'm doing wrong. I also tried getting the stock image from http://forum.xda-developers.com/showthread.php?t=874091 but I can't seem to open the firmware.zip file to try that recovery image.
Again I just want to get back to stock ROM and recovery files now. Any help would be greatly appreciated!

Error «Encryption was interrupted and cannot be complete»

Hi Guys! I have a problem, and i really don't know how can i fix it.
My phone boots normally, but when boot finish this error appear in the screen:
«Encryption was interrupted and can't be completed. Phone data cannot be used anymore.
To continue using your phone, you must restore factory settings. After the restoration, you can restore data backed up in your Google Account to your phone»
There is a "Reset Phone" button but if i push it nothing happen.
I have tried to clear data/cache in recovery but nothing changed, I have tried to install a new ROM (i tried a lot of ROMS) but when it arrive to 50% more or less installation fails.
I have tried this guide oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ but it cannot work (Image Attachment)
Also FASTBOOT can't work. (For exemple: if i try to flash recovery it fails remote: failed to flash recovery / erase userdata / cache)
I really don't know where can i also looking
Help me please!
Anyone?
I'm having the same problem....
Restoring an old backup woth TWRP results in the same error.....
hi guys this happened to me too,
luckily I had twrp 2.8.6.0 flashed for recovery.
think you should still be able to get into fastboot if you do a battery pull
then poweron with the powerbutton and volume up till you see the oppo man icon.
then you should be able to flash your recovery with the latest twrp.
if you seen the penquin then this may not work for you. As i have not done a hard recovery before so i dont know if it would work.
I saw the oppo man so i was able to fix it by:
booting into twrp recovery,
i selected wipe --> advanced and there was an additional option to do a wipe for encrypted volumes and i selected all partitions to be wiped
then i installed i had downloaded on my SD card, it was ColorOS 2.0.8i i believed and it fixed it.
sorry if i am a bit grey about the details i did it a while ago so.
Actually found this in the cm12.1 nighlies thread
http://forum.xda-developers.com/showpost.php?p=58304054&postcount=14
issue is possibly due to unified partitions

Mate suddenly stuck in bootloop

After running Joe stones cyanogenmod10.1 for almost a year I suddenly found my phone in a bootloop
It is stuck at the boot animation, restarting it brings it back to the same state.
All I did was somehow keep one of the buttons pressed (not even sure which one), and did see the shut down/reboot menu flashing by.
The mt1 U06 does appear in my file manager (linux) but cannot be ejected, trying to connect does nothing but show progress indicator.
Tried adb reboot> device not found
fastboot recovery> waiting for device
I have started making a backup using twrp, (yes, could access it) but that may backup what's broken too...)
Any idea if this is fixable?
But also, Why, oh why did this happen?
SvenHee said:
After running Joe stones cyanogenmod10.1 for almost a year I suddenly found my phone in a bootloop
It is stuck at the boot animation, restarting it brings it back to the same state.
All I did was somehow keep one of the buttons pressed (not even sure which one), and did see the shut down/reboot menu flashing by.
The mt1 U06 does appear in my file manager (linux) but cannot be ejected, trying to connect does nothing but show progress indicator.
Tried adb reboot> device not found
fastboot recovery> waiting for device
I have started making a backup using twrp, (yes, could access it) but that may backup what's broken too...)
Any idea if this is fixable?
But also, Why, oh why did this happen?
Click to expand...
Click to collapse
Usualy for the fastboot output that you got it means you need to reinstall the drivers.
Sent from my SM-G850F
Reinstalling drivers if for windows is it not?
Until now I found that linux is super easy in installing adb and fastboot, and previously, during instalation of the phone, installing adb and fastboot was all I did.
Assuming that the 10.1 ROM still is present on your SD card try to reinstall it dirty. Just wipe cache and dalvik cache before rebooting into the system. Only the rom.
Got it working again with just a factory reset, but off course, all data and settings were gone.
I did try to put (partial) backups back but that broke the system again.
It is a shame that all my texts are gone, but I'll get over it.
Thanks for the help guys!

problem after updating rom/soft-bricked?

So I was updating six rom and phone went into continuous boot. So went into recovery and wiped all but internal memory and reinstalled. Same boot problem. Went into fast boot and pushed another over as well as a vendor image. Tried installing the new rom, beans gaps, super su and same result. I've left the phone for over 20 mins with no result but the boot screen.
I'm having a similar problem.
My status- Unlocked bootloader, twrp accessible, devices not getting detected in fastboot mode by the pc, rooted, restoring using the backup results in a bootloop, correct drivers installed on the pc, superSU and full backup in the mobile.
i cant transfer files since device not getting detected.
my timeline- i followed every instruction on https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 and everything went successful, but when it rebooted to the 'Welcome' page (the page which comes when u open mobile for the first time) i restarted my nexus 5x 32gb to recovery mode and then the every boot procedure doesn't complete for several minutes(doesn't go ahead the ball animation)

Stuck in install loop - keeps getting wiped on boot?

I'm trying to install LineageOS 17 on a OnePlus 6.
I can boot into twrp and the install process appears to work successfully. I can swap slots and install into either slot.
When I reboot the phone I get to the screen that says "Start" and "Fastboot mode" at the top. If I try to start the phone it comes back to this screen. When I go back into twrp, the contents of /sdcard is empty. I can copy over files using adb push, install the rom and then reboot. However, every time I reboot it seems like it completely wipes the phone including the install it's just done and /sdcard is also wiped.
When I booted into twrp previously, it required my unlock code. It now no longer does that. I wonder if this is part of the problem?
If I install just oxygenos, it takes me to the oxgenos recovery screen but I cant' do anything from there. I'm guessing that won't allow me to boot with an unlocked bootloader?
Can anyone advise how I can get out of this? Installing anything using twrp looks like it works, but it's like it gets wiped every time I reboot.
I can't even seem to get OxygenOS back to working.
Can anyone give me some tips on where to go from here? Nothing I can do from TWRP seems to help. I have tried wiping everything in both slots and reinstalling oxygen, no luck
Still stuck?

Categories

Resources