I've been away from Samsung phones for a bit over a year now, so I may have just forgotten something simple, but on my Note 2, I have TWRP on it and when I flash a ROM and gapps in TWRP, everything is fine, I reboot, and it's in a boot loop kinda? The whole phone doen't continuously boot and boot and boot, but the ROM never boots, the bootanimation is just there, going along, forever. I've tried Liquidsmooth 4.0 & 3.1.
Am I missing something? I'd like to NOT run stock/stock rooted, as I was using my Note 2 for Vainglory but now it lags too much on stock and I need to run a custom rom that's fast, great battery life, and minimalistic.
does it stuck at the samsung logo? if yes, try to boot into recovery and wipe data and cache.
i sometime had that happen, when i odin to stock.
cfli1688c1 said:
does it stuck at the samsung logo? if yes, try to boot into recovery and wipe data and cache.
i sometime had that happen, when i odin to stock.
Click to expand...
Click to collapse
No, it boots into the rom but all it does is boot forever, it plays the boot animation non stop and never fully enters the rom
xBr4v3x said:
No, it boots into the rom but all it does is boot forever, it plays the boot animation non stop and never fully enters the rom
Click to expand...
Click to collapse
Keep away from TWRP on the Note 2, it is known to cause such problems. I did my self the experience.
Instead, use Philz recovery who do his job perfectly with all roms i tried until now.
zlazaar said:
Keep away from TWRP on the Note 2, it is known to cause such problems. I did my self the experience.
Instead, use Philz recovery who do his job perfectly with all roms i tried until now.
Click to expand...
Click to collapse
Still getting the same problem.
I've tried twrp& philz. No success.
Trying to use LiquidSmooth, and all I get to is the bootanimation, an infinite loop of it.
Related
Hi Guys,
Was hoping to get help on a matter that has rendered my one x bricked.
All was going well on Android Revolution HD.
Decided to change roms, and my phone started messing up:
It doesn't boot in to clockwork mod recovery, instead appears for a second and then reboots.
I've tried reverting back to the stock recovery and then reflashing CWM Recovery via fastboot, but the same thing keeps happening.
Frustratingly, if i try to flash twrp recovery, exactly the same thing happens - it shows the splash screen for the recovery, then reboots again.
My current ROM is a bit buggy, and I want to go back to android revolution HD.
Im pretty stuck, Any suggestions?!
maaz_talha said:
Hi Guys,
Was hoping to get help on a matter that has rendered my one x bricked.
All was going well on Android Revolution HD.
Decided to change roms, and my phone started messing up:
It doesn't boot in to clockwork mod recovery, instead appears for a second and then reboots.
I've tried reverting back to the stock recovery and then reflashing CWM Recovery via fastboot, but the same thing keeps happening.
Frustratingly, if i try to flash twrp recovery, exactly the same thing happens - it shows the splash screen for the recovery, then reboots again.
My current ROM is a bit buggy, and I want to go back to android revolution HD.
Im pretty stuck, Any suggestions?!
Click to expand...
Click to collapse
for the 5,000,000,000,000,000th time
Code:
fastboot erase cache
legend
Use twrp recovery I'm using since its released and no reboot issues so far
im aware how old this post is
i have the same problem and no amount of erase cache is working any suggestions
martipello86 said:
i have the same problem and no amount of erase cache is working any suggestions
Click to expand...
Click to collapse
cwm has been abandoned and don't work on modern software circa 2012 and forward
Flash twrp instead ( you can read more about new vs old layout here https://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358 )
New layout
https://forum.xda-developers.com/htc-one-x/orig-development/twrp-htc-one-x-t3429300
Old layout (choose older than v3, for example twrp-2.6.3.0-endeavoru.img)
https://eu.dl.twrp.me/endeavoru/
I have had my GS4 for a few days now. Its rooted and running DarthStalker. When I reboot the phone esp from TWRP it just gets stuck on the GS4 screen. Its most of the time sometimes when I reboot from the screen it fixes it self, Or do a full wipe. Do I have to odin stock again? I got it working by full wiping DarthStalker and reinstalling again.
I had this issue too, i even tried to use cwm and see if that fixed the problem but it wouldnt even boot doing a full wipe, i odined back to stock and rerooted , installed twrp and i have no problems now.
unciviilized said:
I had this issue too, i even tried to use cwm and see if that fixed the problem but it wouldnt even boot doing a full wipe, i odined back to stock and rerooted , installed twrp and i have no problems now.
Click to expand...
Click to collapse
Issue has been experienced here as well. I may reinstall twrp if it continues and re-root if it continues after that. Good to hear its not just me
C.Sweat said:
Issue has been experienced here as well. I may reinstall twrp if it continues and re-root if it continues after that. Good to hear its not just me
Click to expand...
Click to collapse
I dont think it would do any good, after installing cwm i couldnt do anything just boot into recovery. So to get it running i pushed twrp .tar file thru odin but still had to fully wipe everytime i reboot it. So i just odined to stock. I was a little scared as a week before i had hard bricked an S3.
re: bootup issues
unciviilized said:
I dont think it would do any good, after installing cwm i couldnt do anything just boot into recovery. So to get it running i pushed twrp .tar file thru odin but still had to fully wipe everytime i reboot it. So i just odined to stock. I was a little scared as a week before i had hard bricked an S3.
Click to expand...
Click to collapse
Next time you have problems booting up normally or have bootloops for whatever reason, do a "factory reset"
in either cwm or twrp and nine out of ten times after doing that the phone will boot normally.
Misterjunky said:
Next time you have problems booting up normally or have bootloops for whatever reason, do a "factory reset"
in either cwm or twrp and nine out of ten times after doing that the phone will boot normally.
Click to expand...
Click to collapse
it didnt work for me, you even replied to my thread suggesting the same method.
I can't say I've ever been stuck on the Samsung logo, but I can't count how many times I've gotten hung up on the TWRP splash screen. :\
lordcheeto03 said:
I can't say I've ever been stuck on the Samsung logo, but I can't count how many times I've gotten hung up on the TWRP splash screen. :\
Click to expand...
Click to collapse
Yeah i still get that from time to time, still buggy.
Sent from my SGH-M919 using Tapatalk 2
Use this and you won't have anymore problem.http://forum.xda-developers.com/showthread.php?t=2281367
flash the zip in recovery.
As the title says i am trying to install the Saberkat 1.5 rom on my SGH-I317. I am using Philz recovery and i am on the 4.4.2 bootloader. I was running DN3 previously and attempted to do a clean flash to Saberkat 1.5. The installation of the rom goes fine, but when i reboot the phone gets stuck at the Samsung screen for 15+ mintues. I have gone through the Saberkat 1.5 forum post, but i can not find anyone who is having the same issue as myself.
Thank you for any help you may be able to provide me.
Avaleria said:
As the title says i am trying to install the Saberkat 1.5 rom on my SGH-I317. I am using Philz recovery and i am on the 4.4.2 bootloader. I was running DN3 previously and attempted to do a clean flash to Saberkat 1.5. The installation of the rom goes fine, but when i reboot the phone gets stuck at the Samsung screen for 15+ mintues. I have gone through the Saberkat 1.5 forum post, but i can not find anyone who is having the same issue as myself.
Thank you for any help you may be able to provide me.
Click to expand...
Click to collapse
Format everything except the sd card like the system the preload boot dont format the modem tho and then reboot the recovery and it should say if you wanna root hit no the flash the rom like normal and it should work
terpin32 said:
Format everything except the sd card like the system the preload boot dont format the modem tho and then reboot the recovery and it should say if you wanna root hit no the flash the rom like normal and it should work
Click to expand...
Click to collapse
That is what i always do. I format everything except for the sd card, and wipe both caches. I selected no at the root screen, and it gets to the samsung screen and just sits there.
Avaleria said:
That is what i always do. I format everything except for the sd card, and wipe both caches. I selected no at the root screen, and it gets to the samsung screen and just sits there.
Click to expand...
Click to collapse
I had a similar problem when I first tried to flash DN3 v5 4.4.2 (from Skynote Air 4.3 w/4.1.2 bootloader). The problem was that I was using an old version of Philz (5.5) and it would always stick at the "Samsung" screen after the flash. I switched to Philz 6.41 and it worked fine after that. The only problem is that the backups are not compatible (6.41 can't restore 5.5 and 5.5 can't restore 6.41).
I will attempt this when I get home, will advise on the outcome.
jsdad said:
I had a similar problem when I first tried to flash DN3 v5 4.4.2 (from Skynote Air 4.3 w/4.1.2 bootloader). The problem was that I was using an old version of Philz (5.5) and it would always stick at the "Samsung" screen after the flash. I switched to Philz 6.41 and it worked fine after that. The only problem is that the backups are not compatible (6.41 can't restore 5.5 and 5.5 can't restore 6.41).
Click to expand...
Click to collapse
Updated to the latest Philz version, and still gets stuck at the Samsung screen. I am going to flash TWRP and try again to see if that makes a difference.
Avaleria said:
Updated to the latest Philz version, and still gets stuck at the Samsung screen. I am going to flash TWRP and try again to see if that makes a difference.
Click to expand...
Click to collapse
I couldn't get twrp to work I only got it to work on Philz after I formated everything and I mean everything but the modem and the ext sd card then reboot the recovery and then just flash the rom and only the rom first if it doesn't have a boot sound it won't work
terpin32 said:
I couldn't get twrp to work I only got it to work on Philz after I formated everything and I mean everything but the modem and the ext sd card then reboot the recovery and then just flash the rom and only the rom first if it doesn't have a boot sound it won't work
Click to expand...
Click to collapse
I appreciate your help, i havnt had issues with any other rom. Ive done DN3, EzKat, Slimfast, and they all installed and booted up perfectly. I will chuck it up to bad luck and try a different rom.
Avaleria said:
I appreciate your help, i havnt had issues with any other rom. Ive done DN3, EzKat, Slimfast, and they all installed and booted up perfectly. I will chuck it up to bad luck and try a different rom.
Click to expand...
Click to collapse
4.4.2 is the only I had problems with not booting but Philz is the only one I can get every rom to boot
Funny thing, I tried to flash Saberkat 1.0 and it worked fine. Must be something with 1.5 that isn't working
/Close this thread please
Last night I successfully rooted my Samsung tab pro 10.1, and this morning I used Flashify to attempt to install CWM custom recovery, it said everything worked but now it won't boot past the screen mentioned in the title, any suggestions are most welcome!
Can you still get in recovery mode? (Volume UP + Home button + Power button while device is off)
Miniricho said:
Last night I successfully rooted my Samsung tab pro 10.1, and this morning I used Flashify to attempt to install CWM custom recovery, it said everything worked but now it won't boot past the screen mentioned in the title, any suggestions are most welcome!
Click to expand...
Click to collapse
Are you still having problems? You might try going back to stock and try again. I personally use flashify and Twrp
Well I was able to get into download mode and flash a recovery that worked thank god. I do not like stock though, any roms to recommend? Tried GraveD's rom but it freezes on the Samsung boot screen I'm afraid.
Miniricho said:
Well I was able to get into download mode and flash a recovery that worked thank god. I do not like stock though, any roms to recommend? Tried GraveD's rom but it freezes on the Samsung boot screen I'm afraid.
Click to expand...
Click to collapse
I have not yet found a rom that I have stuck with. CM 12 has been my favorite so far.
Phone is a ginko variant Redmi Note 8, running the PixelOs rom.
It's been running fine for about 2 months now without issue until today.
This morning after using it briefly, it was placed in my pocket. About an hour later I removed it to find the screen black but lit up.
Power cycling the phone resulted in it getting to the boot screen (Google logo with loading bar) where it sits indefinitely. The bar at the bottom is animated, so it's not frozen per say.
If I try to reboot to recover(OrangeFox) it shows the Orange booting screen, and sits there.
I have tried flashing several other orangefox recovery's as well as 2 different TWRP recoveries with the same result, they display the startup screen and then hang there.
Any suggestions?
Sickify said:
Phone is a ginko variant Redmi Note 8, running the PixelOs rom.
It's been running fine for about 2 months now without issue until today.
This morning after using it briefly, it was placed in my pocket. About an hour later I removed it to find the screen black but lit up.
Power cycling the phone resulted in it getting to the boot screen (Google logo with loading bar) where it sits indefinitely. The bar at the bottom is animated, so it's not frozen per say.
If I try to reboot to recover(OrangeFox) it shows the Orange booting screen, and sits there.
I have tried flashing several other orangefox recovery's as well as 2 different TWRP recoveries with the same result, they display the startup screen and then hang there.
Any suggestions?
Click to expand...
Click to collapse
Bro I am afraid you'll have to install the whole firmware again and it will boot into MIUI. You need to flash it with the help of Mi Flash and be in the Fastboot mode and also it will erase all the data. and then you can install the custom recovery again and after installing MIUI and you can flash another ROM. Some AOSP Android 12 ROMs have this bug.
Download Firmware from here: https://mifirm.net/
Spuffyffet said:
Bro I am afraid you'll have to install the whole firmware again and it will boot into MIUI. You need to flash it with the help of Mi Flash and be in the Fastboot mode and also it will erase all the data. and then you can install the custom recovery again and after installing MIUI and you can flash another ROM. Some AOSP Android 12 ROMs have this bug.
Download Firmware from here: https://mifirm.net/
Click to expand...
Click to collapse
Managed to get it going again. I used fastboot to format the userdata partition and that seemed to fix it.
Interesting that some AOSP roms have this bug...I will have to do some research to avoid this in the future.
Sickify said:
Managed to get it going again. I used fastboot to format the userdata partition and that seemed to fix it.
Interesting that some AOSP roms have this bug...I will have to do some research to avoid this in the future.
Click to expand...
Click to collapse
Yup formatting data also helps. Glad it got fixed brother.
Sickify said:
Running the PixelOs rom
Click to expand...
Click to collapse
Of course it's PE time !
Sickify said:
I used fastboot to format the userdata partition and that seemed to fix it
Click to expand...
Click to collapse
That is an encryption problem, no need to format anything just flash DFE
Spuffyffet said:
Bro I am afraid you'll have to install the whole firmware again
Download Firmware from here: https://mifirm.net/
Click to expand...
Click to collapse