Hello,
I flashed my device (recovery only) with Odin, installing TWRP v2.6.3.0. The recovery works properly. After that, I did a complete wipe and I flashed my Galaxy Tab 3 10.1 WiFi with this ROM. Unfortunatelly it boots into recovery every time and I can't install any ROM on my device. Is there any way how to fix it, or am I completely lost? I've installed cynaogen mod in similar way on my I-9000 and everything worked fine, so this accident was a real surprise for me. Please, could anyone help?
Regards,
Max
redbull00 said:
Hello,
I flashed my device (recovery only) with Odin, installing TWRP v2.6.3.0. The recovery works properly. After that, I did a complete wipe and I flashed my Galaxy Tab 3 10.1 WiFi with this ROM. Unfortunatelly it boots into recovery every time and I can't install any ROM on my device. Is there any way how to fix it, or am I completely lost? I've installed cynaogen mod in similar way on my I-9000 and everything worked fine, so this accident was a real surprise for me. Please, could anyone help?
Regards,
Max
Click to expand...
Click to collapse
I am having the same problem with my G Tab 3 7 -ST217 from Sprint. I have root access. At first I could only reboot to recovery ONCE after Odin. Now I can consistently reboot to recovery. Every time I try to install anything from a zip in TWRP then reboot, it didn't install and instead restarts the factory android and goes through the first time startup and update cycle. Can't seem to get a ROM to stick.
When you do the ROM installation with TWRP, do you see a message after installation saying "unable to mount" or something similar? If so, the ROM was not installed and the device would either stop at the boot logo or restart to recovery. You might need to try flashing a different recovery.
Thats one theory. The other is that there was a problem with the ROM. Maybe corrupted during download or something of that sort. In which case re-download and if a md5 is there run the checksum and try again.
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.
I have a GTN-7100 which has CWM 6.0.4.3 and previously had a rooted stock ROM. I am trying to install CM11. I have downloaded a snapshot of t0lte and copied it to the external SD card. I have wiped data/cache using CWM and installed the zip file via CWM. The installer process doesn't report any errors. When I reboot the phone gets stuck on the logo screen.
I have tried downloading a more recent nightly and also repeated the process and installed gapps via CWM. The MD5 sums of the downloaded files are correct. However, the phone always gets stuck on the logo screen. I have left it for up to four hours, just in case it was taking a long time to start.
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.
Yesterday I decided to root my Nexus 7 2013 Wifi running stock 6.0.1 (build MOB30X). I first unlocked the bootloader, then immediately after that I flashed TWRP (twrp-3.0.2-0-flo.img). When I booted up, it would got stuck on a loop with TWRP running OpenRecoveryScript, saying something about unable to mount /data and renaming something, then reboot into TWRP again.
I did some research and it seemed I had to use a multirom TWRP version instead, so I went ahead and flashed it. Now I can go into TWRP, but when booting up I got stuck in the booting animation (the four spinning circles)
How can I fix this?
chinhodado said:
Yesterday I decided to root my Nexus 7 2013 Wifi running stock 6.0.1 (build MOB30X). I first unlocked the bootloader, then immediately after that I flashed TWRP (twrp-3.0.2-0-flo.img). When I booted up, it would got stuck on a loop with TWRP running OpenRecoveryScript, saying something about unable to mount /data and renaming something, then reboot into TWRP again.
I did some research and it seemed I had to use a multirom TWRP version instead, so I went ahead and flashed it. Now I can go into TWRP, but when booting up I got stuck in the booting animation (the four spinning circles)
How can I fix this?
Click to expand...
Click to collapse
Just run these two commands:
Code:
fastboot format cache
fastboot format userdata
Don't worry, you have lost all your data already while unlocking it.
The first boot and the booting animation will be initially longer than usual.
Incidentally, no need to use multirom-TWRP anymore because TWRP v3+ has been properly updated.
I actually solved this myself before k23m's reply by flashing the stock rom (MOB30X), then completed the initial setup, then reflashed TWRP (twrp-3.0.2-0-flo.img, not the multirom version). After that I booted up then restarted into recovery but then realized that TWRP had been wiped (only the android with the red triangle showing). So I re-flashed TWRP again and this time rebooted directly into recovery, and renamed the file recovery-from-boot.p into recovery-from-boot.backup. Then I flashed su and all went well.
k23m said:
Just run these two commands:
Code:
fastboot format cache
fastboot format userdata
Don't worry, you have lost all your data already while unlocking it.
The first boot and the booting animation will be initially longer than usual.
Incidentally, no need to use multirom-TWRP anymore because TWRP v3+ has been properly updated.
Click to expand...
Click to collapse
Thank you for the hint!