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 was trying to install CWM recovery on this phone , I used Odin to flash recovery . I flashed recovery then removed battery and then booted to recovery then CWM loaded but as soon as I restarted the phone and again tried opening recovery phone took me to stock recovery , how can I solve this? I am running 4.2.2 firmware . And also I tried flashing CM11 with this temporary CWM but package installation stopped because of a error (status 7) saying some problem with partition , I was not rooted at the time . Is root needed to flash CM11 ?
cyb3r.pr3dat0r said:
I was trying to install CWM recovery on this phone , I used Odin to flash recovery . I flashed recovery then removed battery and then booted to recovery then CWM loaded but as soon as I restarted the phone and again tried opening recovery phone took me to stock recovery , how can I solve this? I am running 4.2.2 firmware . And also I tried flashing CM11 with this temporary CWM but package installation stopped because of a error (status 7) saying some problem with partition , I was not rooted at the time . Is root needed to flash CM11 ?
Click to expand...
Click to collapse
1. Once u boot into CWM recovery flash SuperSU (If u don't have get it from here). This will ensure that the recovery doesn't revert back to stock.
2. Status 7 error has various reasons. Ensure that u r using most latest recovery and perform clean install.
Trilochanaaya said:
1. Once u boot into CWM recovery flash SuperSU (If u don't have get it from here). This will ensure that the recovery doesn't revert back to stock.
2. Status 7 error has various reasons. Ensure that u r using most latest recovery and perform clean install.
Click to expand...
Click to collapse
it was telling me some error with partition like eemc when i flashed cm11 , can this be due to because i was't rooted?
cyb3r.pr3dat0r said:
it was telling me some error with partition like eemc when i flashed cm11 , can this be due to because i was't rooted?
Click to expand...
Click to collapse
First of all root your device.
Secondly install philz recovery using odin.
Then flash your desired ROM
(i suggest you aogp dual sim).
PM me if you need any help.
All the best :thumbup:
Press thanks Button
Sent From AWSOME AOGP ROM for I9082
emmc is a partition i believe, if you see such errors, recheck if you are using the correct recovery... I flashed my tablet with wrong recovery and it wiped out all my partitions. It's as good as a brick now if not worse.
Hey guys, I just recently got some parts for my old One X to start playing with it again (bored with ios). I was running an older version of ViperXL and wanted to get lollipop so my goal was to put CM12.0 on my phone. My recovery was twrp but a version that was older so I had to update it. The in app update wasn't working so I updated cwm instead. When I did this I tried to boot to recovery and it would attempt to go to recovery but then boot back to the os.
Then I was trying to flash the recovery using fastboot which resulted in the same problem. Somewhere in there I flash the recovery.img as my boot image (sudo fastboot flash boot recovery.img) This made my phone repeatedly try to boot into recovery. I tried flashing new ViperXL boot.img as well as a couple others but none let me get into my os again. Now it is just a bootloop trying to start my phone up.
When I try flashing a .zip I get the error 'FAILED (remote: not allowed)'. Flashing recovery and boot images work though.
I've tried a lot and done a lot of searching but nothing can get me into recovery or even out of any sort of bootloop.
I'm using Ubuntu and my phone is S-On if that means anything.
Thanks!
Try restoring any backups of old roms from the recovery. Make sure Recovery is written properly in recovery partition. If this works fine , the appropriate boot.img shud be automatically flashed , i guess.
If u dont have a backup , try finding another one x user using a custom recovery, create a backup from his mobile and copy it to ur sd card by mounting it thru recovery and restore it.
If it doesnt work , wipe all the partitions - System , cache, boot and recovery.. then try flashing a Recovery and then a Boot.img and a rom.
I havent faced such a situation. Just my suggestions as no experts have responded.
Cheers if u have already sorted it out !!!
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.
my phone c2005 all apps isn't responding after reboot and restarts automatically
my system was cm11 and removed some system apps
my custom recovery changed automatically from twrp to cwm and doesn't accept installing new rom and give error 7 and doesn't remove system or wipe data or make factory reset
when i flash twrp by flashtool gives ok and no thing changes and when flash by fast boot gives remote:command not allowed
tried to flash new ftf or new kernel but gives errror flashing .sin file
so i am stuck in this useless recovery and i dont know what to do
any help please