stuck on samsung screen; can't install ROM - Galaxy S 4 Mini Q&A, Help & Troubleshooting

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.

Related

[Q] Cannot install custom ROMs anymore

Hi,
I am on CM 10.2 nightly. Everytime I try to install an different ROM on CWM 6.0.27, eg. Android Revolution 22.0, the installation procedure goes fine. During Aroma installer I choose to wipe user data partition and so on. Then after reboot my phone stucks on "samsung galaxy note gt-n7100" screen. Afterwards I have to go back into recovery and have to recover my rom so the phone will boot again. Really strange. Any suggestions why my phone is behaving this way?
Regards, heinzelrumpel
heinzelrumpel said:
Hi,
I am on CM 10.2 nightly. Everytime I try to install an different ROM on CWM 6.0.27, eg. Android Revolution 22.0, the installation procedure goes fine. During Aroma installaer I choose to wipe user data partition and so on. Then after reboot my phone stucks on "samsung galaxy note gt-n7100" screen. Afterwards I have to go back into recovrey and have to recover my rom so the phone will boot again. Really strange. Any suggestions why my phone is beahving this way?
Regards, heinzelrumpel
Click to expand...
Click to collapse
Change the recovery, often Philz 5.15 works best with Aroma installer.
Androidwizzard said:
Change the recovery, often Philz 5.15 works best with Aroma installer.
Click to expand...
Click to collapse
Unfortunately this does not do the trick Still stuck after reboot.
I can't tell you why its happening, but what I've done in the past to get around the issue is to flash a stock rom with Odin, then flash a new recovery before going to another custom rom. If you worry about the Knox warranty bit being set you'll have to find an old 4.1 image somewhere to flash. Since I'm past warranty I don't care anymore.
Good luck!
Wipe data cache dalvik format system etc nstall the new rom reboot and after go again to recovery and factory reset it.
Sent from my GT-N7100 using Tapatalk

Stuck in CWM / Crash on every Rom installations

Hi everyone
Sorry in case of repost.
I have a P5210 (Samsung Tab 3 Wifi). Once rooted everything was allright until I entered in recovery mode from the Rom Toolbox app.
I'm now stuck in a recovery loop mode and can't get out (CWM v6.0.4.7)
I've tried everything from factory reset / cache and dalvik cache wipe, to "fix" zips and so on. But nothing changes.
I've tried to reinstall CWM by putting a recovery image into a script and flash it through CWM. Seems to be done correctly, but when I reboot, it's still the same CWM (no update)
Eventually, i've tried to install some custom ROMs to start fresh : Every installation crashes at "WRITING SYSTEM PARTITION". I get black screen and a reboot.
And I've tried every custom Rom compatible with P5210.
Can you help me to get back to a clean configuration ?
N.
nicobee75 said:
Hi everyone
Sorry in case of repost.
I have a P5210 (Samsung Tab 3 Wifi). Once rooted everything was allright until I entered in recovery mode from the Rom Toolbox app.
I'm now stuck in a recovery loop mode and can't get out (CWM v6.0.4.7)
I've tried everything from factory reset / cache and dalvik cache wipe, to "fix" zips and so on. But nothing changes.
I've tried to reinstall CWM by putting a recovery image into a script and flash it through CWM. Seems to be done correctly, but when I reboot, it's still the same CWM (no update)
Eventually, i've tried to install some custom ROMs to start fresh : Every installation crashes at "WRITING SYSTEM PARTITION". I get black screen and a reboot.
And I've tried every custom Rom compatible with P5210.
Can you help me to get back to a clean configuration ?
N.
Click to expand...
Click to collapse
Hi
It seems you were on kitkat rom which may have updated your bootloader to kitkat version. The CWM needs to be updated to work well with kitkat. I had similar problem with my SM-T210, and solved the problem after updating CWM as per this post for T210:
http://forum.xda-developers.com/showthread.php?t=2433853
Your tab is different from mine so i think you need a fresh stock rom install using odin, then find an updated CWM for your tab.

My phone won't wipe nor flash a new rom/recovery

Hi there. Here I have my t989 with stable cm11 by Sultanxda and twrp 2.7.0.0 installed.
Everything was fine until I wanted to try 5.0.1.
I got into twrp and did the usual wipe and install ParanoidAndroid 5.0. It failed.
Ok stuff happens so I just went restore my backup no big deal.
Now when I reboot back my phone looks as it were before BUT it reboots after 2-3 minutes in every time it boots back up.
So I thought the power button has problem but soon I figured it is not because my phone won't self reboot in recovery and download mode.
I went back to twrp and try to wipe it clean and install cm11 instead of restoring to my previous backup.
Wipe says successful, install says successful, reboot system. And only to find myself still in my old Rom and nothing was wiped.
All my apps are still there blahblahblah. I tried to update my twrp through twrp manager but phone reboot before it finishes installing.
I grab my odiin and try to update recovery there. Odin says success. Goes to recovery only to find its still in 2.7.0.0
Download a stock .tar and flash it with Odin. Odin says success, boot up and still in my old cm11 rom...
Now I went out of option but ask for help. I have done flashing for 3 years with this phone and I have never gotten this problem before.
Please Help

twrp causes bootloop

Hey everyone, i got a neat little problem with my one X.
I wanted to install Resurrection Remix LP v5.5.0 according to this Thread.
So first of all I flashed twrp 2.6.3.0 to my phone and tried to install RR 5.5.0., which threw me an error (because of layout differences).
I moved on by flashing another recovery twrp2811.BiG to my phone and booted into it, np. So i wiped everything, I think it was the advanced wipe option, I ticked every checkbox and swiped to wipe.
After a short time my phone blackscreened back into the bootloader and when I tried to enter recovery again, it displays the twrp logo for a short time, then crashes and reboots.
Since theres no Android to boot, it repeats it's bootloop. I tried flashing twrp2853-BiG, twrp-2.6.3.0-endeavoru,twrp-2.6.1.0-endeavoru. Fastboot flashes the recoveries and right before my phone restarts it even shows the correct "recovery splash screen" according to the current recovery image flashed.
When I flash recovery-clockwork-touch-6.0.4.8-endeavoru and boot into recovery everythin works, but I can't manage to mount my USB storage anymore.
But that almost doesn't matter since I need twrpXXXXBiG to flash the latest Resurrection Rom, but I cant get any twrp recovery back to work (erase cache didn't help at all).
Lip0ly said:
Hey everyone, i got a neat little problem with my one X.
I wanted to install Resurrection Remix LP v5.5.0 according to this Thread.
So first of all I flashed twrp 2.6.3.0 to my phone and tried to install RR 5.5.0., which threw me an error (because of layout differences).
I moved on by flashing another recovery twrp2811.BiG to my phone and booted into it, np. So i wiped everything, I think it was the advanced wipe option, I ticked every checkbox and swiped to wipe.
After a short time my phone blackscreened back into the bootloader and when I tried to enter recovery again, it displays the twrp logo for a short time, then crashes and reboots.
Since theres no Android to boot, it repeats it's bootloop. I tried flashing twrp2853-BiG, twrp-2.6.3.0-endeavoru,twrp-2.6.1.0-endeavoru. Fastboot flashes the recoveries and right before my phone restarts it even shows the correct "recovery splash screen" according to the current recovery image flashed.
When I flash recovery-clockwork-touch-6.0.4.8-endeavoru and boot into recovery everythin works, but I can't manage to mount my USB storage anymore.
But that almost doesn't matter since I need twrpXXXXBiG to flash the latest Resurrection Rom, but I cant get any twrp recovery back to work (erase cache didn't help at all).
Click to expand...
Click to collapse
Just had an similar issue,
Try flashing first boot.img from the rom you will flash
then flash the recovery twrp big
then do the wipes ..
then flash boot.img and then rom
I thought this worked for me. (i flashed with the unboxed rom)
Just tried it, didn't work for me.
Bump

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.

Categories

Resources