Develop Bugs

Can only boot into fastboot mode anymore

Hey guys,
I have a problem with my Z1C.
I used CM 12.1 quite a while now and I wanted to know how much difference is to Android 6.
So I downloaded the Remix Resurrection rom and flashed the boot.img in fastboot mode to replace the CM-recovery with TWRP. That was a bit tricky, because CM deleted TWRP again and again and booted in the CM-recovery.
So, finally I got TWRP working, after booting directly into the recovery after flashing the boot.img via fastboot.
TWRP now told me, that no OS is installed. I tried to wipe the phone and to install the RR-rom, but the recovery always said that it has the wrong version (?).
So I flashed the boot.img from the Cyanogenmod-zip and was able to boot into CM again. But now there seems to be no recovery on the phone. Whenever I try to boot to the recovery, the Sony logo appears and the notification light turns into orange, but then it starts again to do so.
At the moment I try to boot into CM again, but I think it has stucked in a bootloop...
What can I do here? The only thing what works is to boot into fastboot mode, but without the system.img I cant flash any roms there. How can I fix this?
Thanks!
Reapy

Reapy1804 said:
Hey guys,
I have a problem with my Z1C.
I used CM 12.1 quite a while now and I wanted to know how much difference is to Android 6.
So I downloaded the Remix Resurrection rom and flashed the boot.img in fastboot mode to replace the CM-recovery with TWRP. That was a bit tricky, because CM deleted TWRP again and again and booted in the CM-recovery.
So, finally I got TWRP working, after booting directly into the recovery after flashing the boot.img via fastboot.
TWRP now told me, that no OS is installed. I tried to wipe the phone and to install the RR-rom, but the recovery always said that it has the wrong version (?).
So I flashed the boot.img from the Cyanogenmod-zip and was able to boot into CM again. But now there seems to be no recovery on the phone. Whenever I try to boot to the recovery, the Sony logo appears and the notification light turns into orange, but then it starts again to do so.
At the moment I try to boot into CM again, but I think it has stucked in a bootloop...
What can I do here? The only thing what works is to boot into fastboot mode, but without the system.img I cant flash any roms there. How can I fix this?
Thanks!
Reapy
Click to expand...
Click to collapse
Shut down your device and press volume up button while connecting it to your computer. Then it will boot into fastboot mode and you should be able to flash stock firmware in flashtool, and then you can start from scratch.
---------- Post added at 06:27 PM ---------- Previous post was at 06:12 PM ----------
Another option is to follow this guide to install Recovery and When done you can boot into Recovery and flash a custom rom. http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719

Reapy1804 said:
Hey guys,
I have a problem with my Z1C.
I used CM 12.1 quite a while now and I wanted to know how much difference is to Android 6.
So I downloaded the Remix Resurrection rom and flashed the boot.img in fastboot mode to replace the CM-recovery with TWRP. That was a bit tricky, because CM deleted TWRP again and again and booted in the CM-recovery.
So, finally I got TWRP working, after booting directly into the recovery after flashing the boot.img via fastboot.
TWRP now told me, that no OS is installed. I tried to wipe the phone and to install the RR-rom, but the recovery always said that it has the wrong version (?).
So I flashed the boot.img from the Cyanogenmod-zip and was able to boot into CM again. But now there seems to be no recovery on the phone. Whenever I try to boot to the recovery, the Sony logo appears and the notification light turns into orange, but then it starts again to do so.
At the moment I try to boot into CM again, but I think it has stucked in a bootloop...
What can I do here? The only thing what works is to boot into fastboot mode, but without the system.img I cant flash any roms there. How can I fix this?
Thanks!
Reapy
Click to expand...
Click to collapse
Try Rashr app from play store. It sounds to me like incompatible kernel/recovery combo. Download a recovery IMG, (latest TWRP, for example), then use Rashr to flash it. You can also use it for flashing a boot IMG. Its probably the same reason you had trouble flashing ROM.
Besides that, you can install real recovery, which works the same regardless of the kernel-
http://forum.xda-developers.com/xperia-e3/general/bootloader-devices-real-recovery-t3096837

Okay, after flashing it with flashtool it starts again. I now put the RR rom with Android 5.1 on.
I have again the CM recovery, but at least it starts how it should.
I will try to flash the real recovery, thanks!

Update:
Currently running RR with Android 5.1.
I would now like to use RR with Android 6, but again, I can only boot into the Cyanogen recovery, which cant make a backup of the currently running OS. I have tried to flash the boot.img from RR 5.1 with fastboot, Rashr, but nothing seems to work, as it puts me back to the Cyanogen recovery every time. How can I replace the Cyanogen recovery?
And one more question: When the phone starts, the notification light turns into red before the Sonmy logo appears and then turns into pink. What does the red light mean?

Reapy1804 said:
Update:
Currently running RR with Android 5.1.
I would now like to use RR with Android 6, but again, I can only boot into the Cyanogen recovery, which cant make a backup of the currently running OS. I have tried to flash the boot.img from RR 5.1 with fastboot, Rashr, but nothing seems to work, as it puts me back to the Cyanogen recovery every time. How can I replace the Cyanogen recovery?
And one more question: When the phone starts, the notification light turns into red before the Sonmy logo appears and then turns into pink. What does the red light mean?
Click to expand...
Click to collapse
You need a recovery img, not boot img. Try this one - http://forum.xda-developers.com/showpost.php?p=65361797&postcount=78 or this one - http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719 Open Rashr, choose ' recovery from storage'.

Okay, i flashed the 2.8.6.0 version via Rashr and now Im stuck on the Sony logo...the notification light is orange all the time, but I cant restart the phone anymore...any suggestions?
Edit: Worked! Used the combination between power and Vol+ to reset, and now it starts!

You should disable CM Recovery Protection – On your phone go to Settings > Developer options. Then disable the ‘Update recovery with system updates’ option. Otherwise it will keep installing cm recovery itself.

Stuck at Logo after flashing rom [fixed] > solution!

Edit: solution added
problem:
after flashing a rom (in my case OP3lite or FreedomOS) you can't get past the boot logo
you have access to TWRP, so you can restore nandroid or flash flashable stock OxygenOS packages (tutorial here)
solution:
wipe: Dalvik /ART Cache, Cache, Data, System
flash your rom
try to boot (most likely will get stuck at boot logo)
boot into TWRP > Advanced > Fix Contexts, and swipe to Fix Contexts
Reboot
(wait a while, it might take a few minutes till it boots)
___________________________________________
original post:
hi,
I'm running official OxygenOS 3.1.3.
Rooted (systemless) , TWRP installed.
I don't have any problems on my rom, but everytime I flash a rom I get stuck at the boot logo.
I can just force reboot, goto twrp and restore my nandroid backup, and my phone works fine again.
But I can't flash any rom.
tried this:
Dirty flash OP3Lite rom - stuck at boot logo
wipe and install OP3Lite rom - stuck at boot logo
Restored nandroid backup, factory format, wipe and install OP3Lite rom - stuck at boot logo
wipe and install FreedomOS - stuck at boot logo
Restored nandroid backup, factory format, wipe and install FreedomOS - stuck at boot logo
wipe, Format userdata throught fastboot, install FreedomOS - stuck at boot logo
update to OxygenOS 3.2.1 (flashable zip throught twrp)
wipe and install FreedomOS - stuck at boot logo
Both roms I tried are OxygenOS 3.2.1 stock based, my problem is most likely not due to the rom I want to flash.
Anyone knows a solution for this?
is it possible that systemless root causes this problem?

are you encrypted? that might be the issue.
backup your internal sd data then go to fastboot and fastboot format userdata then flash the rom you want

Abaddon said:
are you encrypted? that might be the issue.
backup your internal sd data then go to fastboot and fastboot format userdata then flash the rom you want
Click to expand...
Click to collapse
I never did format my userdata throught fastboot, so I might be encrypted.
I'll try tomorrow and let you know if that was the solution.

@Abaddon I format my userdata throught fastboot (fastboot format userdata), but still roms wont go past the Logo . any other idea?

did you full wipe?
wiped /system too before flashing a rom then u go and flash the rom + gapps if needed
how long was it at the boot logo? no animation correct?

did u advance wipe - data, caches, system instead of factory wipe, try it 3 times

I did a few wipe 3 times, still stuck at logo.
I get stuck on this logo, never reboot, just get stuck there.
I noticed that it does flash the rom, cause if I restore my nanodroid backup layers and adblock is added.
I also get zero error while flashing in twrp.

I fixed it .
did a fill whipe, then flashed feedomOS, then tried to boot, didnt get past the logo, booted into recovery, selected "fix Contexts" and then rebooted, started without any problem .

doesent work for me..!! any help

Same here this issue keeps occuring again and again. then i always have to follow mega unbrick guide

Resurrection ROM 7.1.1 stuck at logo after every restore
nikhilsnigam said:
Same here this issue keeps occuring again and again. then i always have to follow mega unbrick guide
Click to expand...
Click to collapse
Faced this issue every time I restore any nandroid on one plus 3. It stucks at rotating resurrection logot . Even tried fix contents from TWRP, no output. Please help without a functional TWRP backup and restore - phone is useless. Only everytime mega unbrick guide needs to be repeated with painful reinstall of apps

hello guys. sorry if I'm a bit slow on this topic. I'm using the the op3t A3010 version (not dure whether I'm at the right forum or not lol) Recently I updated my phone to the new 4.1.7, in which I had already rooted the phone before with magisk v12. But right after the update, as usual, the phone will unroot and yes I did root the phone back by using the magisk v13.0 version. But it failed the safety net. So after a few 'research', I installed the superuser just in case that the safety net will work this time. But this is when it all went wrong. The phone did restart back to factory settings, but the phone is not rooted (checked by using the rootchecker app) So again, I'm back to the twrp recovery, clean wipe all the data, with hope that I can start from scratch which is from installing the magisk all over again. But after this step, it stuck at the boot logo for like more than half an hour. Than at this moment, I restart my phone back to recovery mode by long pressing the power button, and when I try to install both the magisk 12 and 13 version, there is a line of error code on the screen. There's a site that says simply go to the advance setting on the twrp interface, check fix contents and ur phone will be as good as new. After done doing that, I'm now stuck with a phone with no os installed and about 38% battery left. Can anyone help me here? This is the only phone that I had :crying: Urgent help needed here guys

Unless your original installation is without storage encryption (no dm-verity) this will happen. So next time install custom rom after flashing OB22 firmware+modem, then boot patch for dm-verity followed with custom rom and gapps then boot without wipe

i have the same problem but with p9 lite : when i tried a flash lineageOS or ResurrectionRemix my phone stucks at boot logo and when i flash the original os my phone works perfectly
sorry for my english

washichi said:
I fixed it .
did a fill whipe, then flashed feedomOS, then tried to boot, didnt get past the logo, booted into recovery, selected "fix Contexts" and then rebooted, started without any problem .
Click to expand...
Click to collapse
How long did you wait?

washichi said:
Edit: solution added
boot into TWRP > Advanced > Fix Contexts, and swipe to Fix Contexts
Reboot
(wait a while, it might take a few minutes till it boots)
Click to expand...
Click to collapse
What is the work around for CWM v6.0.5.1 Philz Touch6; it does not have Fix contexts under Advanced Functions
My issue: Tecno Spark K7 stuck at boot logo after flashing with ported ROM from Infinix XOS Chameleon . Both kernels match

This is EXACTLY my issue with the galaxy s9 plus. Gonna try the solution you wrote tommorow.

i have the same problem with galaxy s5 and the solution mentioned in the thread did not work with me.

im having the same issue but in lenovo z5 pro gt

PauloVillaflor said:
im having the same issue but in lenovo z5 pro gt
Click to expand...
Click to collapse
Search for answers HERE and if not successful, create a thread in the Q&A forum there.
You may not get any help here since this is the OP 3 forum.

stuck on samsung screen; can't install ROM

Hey guys,
I just flashed the recovery via odin on my GT-I9195 and installed the latest release from cyanogenmod.org It worked fine, the phone started normally. But when i tried to restart the phone it was stuck on the samsung screen, saying "set warranty bit kernel". I tried to install the ROM again doing factory resets and so on but whenever I start the installation the screen goes black for a second or so and jumps back to the main menu of the recovery... I also tried the cwm-recovery which gives the same result. screen goes black and jumps back into recovery.
Anyone got a solution?
Recovery used:
openrecovery-twrp-3.0.2-1-serranoltexx-STABLE-signed.zip
CyanogenMod:
cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx.zip (snapshot)

jacob00 said:
Hey guys,
I just flashed the recovery via odin on my GT-I9195 and installed the latest release from cyanogenmod.org It worked fine, the phone started normally. But when i tried to restart the phone it was stuck on the samsung screen, saying "set warranty bit kernel". I tried to install the ROM again doing factory resets and so on but whenever I start the installation the screen goes black for a second or so and jumps back to the main menu of the recovery... I also tried the cwm-recovery which gives the same result. screen goes black and jumps back into recovery.
Anyone got a solution?
Recovery used:
openrecovery-twrp-3.0.2-1-serranoltexx-STABLE-signed.zip
CyanogenMod:
cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx.zip (snapshot)
Click to expand...
Click to collapse
Have you install "Gapps" after flashing CM13?
If you backup you custom rom than try fresh installation: copy CM13 & Gapps to Ext SD Card, Wipe everything (Dav cache, Cache, Data, Perload, Internal Storage) Dont wipe your Ext SD Card.
Than flash CM13 & Gapps after flash simply reboot. Don't wipe anything, Don't factory reset.
Hope it could be worked...

Try to go back to stock rom. Hope your phone revives.

Strange issue with mi5s not booting flashed rom

Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.

goatlad said:
Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.
Click to expand...
Click to collapse
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer

crzykiller said:
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer
Click to expand...
Click to collapse
tried official twrp 3.1.1-0, did these steps only, maybe I've missed something:
installed twrp 3.1.1-0 then went into fastboot and typed fastboot format userdata
rebooted into TWRP, i was promted whether to keep system read only, I tried first swiping to allow mods, and also keep read only then proceeded:
changed data to F2FS (didn't wipe or factory reset anything else)
rebooted system
copied lineage and gapps zip files to phone
installed latest lineage then gapps 7.1 arm64
rebooted system, back into twrp

[Solved]Can't flash rom+gapps

So i originally had a p2c...blabla
Ota updated to p2a4 or something like that. sf244 ROW
unlocked oem (waited 14days)
flashed twrp.
factory resetted+format system. + data partition is ext4
rom flashed successfully
gapps starts flashing but keeps stuck after just 1% of flashing.. always.
or twrp keeps freezing.
Does anyone have a solution?
Right now i'm back to Stock Rom+Magisk 13.3 .

sm00th4f3 said:
So i originally had a p2c...blabla
Ota updated to p2a4 or something like that. sf244 ROW
unlocked oem (waited 14days)
flashed twrp.
factory resetted+format system. + data partition is ext4
rom flashed successfully
gapps starts flashing but keeps stuck after just 1% of flashing.. always.
or twrp keeps freezing.
Does anyone have a solution?
Right now i'm back to Stock Rom+Magisk 13.3 .
Click to expand...
Click to collapse
If you have backup then Install your stock rom and its every components such as boot, recovery etc....
Or download the fastboot files from the p2 thread and flash it.
Then properly install twrp.

How can i properly install twrp?.. I mean, i think i always installed in correctly...otherwise magisk wouldn't work., right?. Because it does. I need your help. I even got Safetynet Pass and Root Apps like Root Explorer is working Fine.
Only the Flashing of Custom Roms etc fails for me... It's weird.

Okey. I just redid it like 5 Times. And i got a bit farther.. new boot animation shows up. But still blue led after it stops.

I FINALLY found the SolutioN!!! I used this https://androidfilehost.com/?fid=817550096634780916 and did the upgrades per ota. Then adb'd my twrp on my phone. And changed data to ext4. Rebooted. Activated usb debugging again. flashed twrp again(just to be sure), booted into twrp. Formatted system,data,cache,dalvik and then flashed my roms. SUCCESS <3