I was recently flashing a rom on my rooted Verizon S5 via Safestrap on one ROM slot. I flashed the rom then downloaded the 0A8 kernel. Upon bootup, the phone was stuck on a boot loop, but I can get into recovery and download mode. I have already tried to factory reset the phone via recovery and I have also tried to put on the stock kernel again. Both were unable to resolve the issue. I have a fulll nandroid backup so wiping anything would not be an issue, but is there any way to solve this problem?
Also, when the phone boots up, it stays on the S5 boot screen and you will hear the boot sound but it will remain at that screen for an infinite amount of time. Can anyone help?
Thanks
XDA Visitor said:
I was recently flashing a rom on my rooted Verizon S5 via Safestrap on one ROM slot. I flashed the rom then downloaded the 0A8 kernel. Upon bootup, the phone was stuck on a boot loop, but I can get into recovery and download mode. I have already tried to factory reset the phone via recovery and I have also tried to put on the stock kernel again. Both were unable to resolve the issue. I have a fulll nandroid backup so wiping anything would not be an issue, but is there any way to solve this problem?
Also, when the phone boots up, it stays on the S5 boot screen and you will hear the boot sound but it will remain at that screen for an infinite amount of time. Can anyone help?
Thanks
Click to expand...
Click to collapse
All Your Question/Answers Goes Here : Galaxy S5 Help Forums
Related
I picked up my phone and had tons of force closes and could not get the phone to respond. I pulled the battery and waited. Then tried to start the phone up again and it will not get past the "rethink possible" screen. It keeps looping on that screen and will not start. I was running stock 2.3.6 rooted only with the cwm recovery.tar flashed. My phone had been working great for a month, the length that I have had it. I can still boot into cwm. I tried formating data/cache/dalvik. Phone still would not boot. I decided to erase my emmc and remove the sd card and sim card and restore my phone with odin to uckj2 and again it is still stuck on the "rethink possible" screen. Any help is greatly appreciated.
nerdcompdork11 said:
I picked up my phone and had tons of force closes and could not get the phone to respond. I pulled the battery and waited. Then tried to start the phone up again and it will not get past the "rethink possible" screen. It keeps looping on that screen and will not start. I was running stock 2.3.6 rooted only with the cwm recovery.tar flashed. My phone had been working great for a month, the length that I have had it. I can still boot into cwm. I tried formating data/cache/dalvik. Phone still would not boot. I decided to erase my emmc and remove the sd card and sim card and restore my phone with odin to uckj2 and again it is still stuck on the "rethink possible" screen. Any help is greatly appreciated.
Click to expand...
Click to collapse
go into download mode and flash again
There seems to be an ongoing problem with our cwm recovery. This has happend to many of us. To the point where even an odin stock tar flash did notnresolve it. What you need to do is flash thebstock recovery tar...then boot into stock recovery and wipe data and cache. Then boot back into the rom you have. And use rom manager to flash the tmobile samsung galaxy s2 cwm recovery. That will fix your problem. I know of 4 others who have had the same issue
As well as myself and we were all able to recover from it. Using the steps i mentioned.
silver03wrx said:
There seems to be an ongoing problem with our cwm recovery. This has happend to many of us. To the point where even an odin stock tar flash did notnresolve it. What you need to do is flash thebstock recovery tar...then boot into stock recovery and wipe data and cache. Then boot back into the rom you have. And use rom manager to flash the tmobile samsung galaxy s2 cwm recovery. That will fix your problem. I know of 4 others who have had the same issue
As well as myself and we were all able to recover from it. Using the steps i mentioned.
Click to expand...
Click to collapse
Silver03wrx: is the problem that this CWM was written for the T-Mobile T989 and not the I727 Skyrocket?
Sent from my SAMSUNG-SGH-I727 using XDA App
Most likely.
silver03wrx said:
There seems to be an ongoing problem with our cwm recovery. This has happend to many of us. To the point where even an odin stock tar flash did notnresolve it. What you need to do is flash thebstock recovery tar...then boot into stock recovery and wipe data and cache. Then boot back into the rom you have. And use rom manager to flash the tmobile samsung galaxy s2 cwm recovery. That will fix your problem. I know of 4 others who have had the same issue
As well as myself and we were all able to recover from it. Using the steps i mentioned.
Click to expand...
Click to collapse
Thanks silver03wrx! Worked like a charm!
ok. the phone will not completely boot into a rom (stock or custom). but i have wiped all data, cache, dalvik MANY times, i have flashed stock kernel and rom from samsung. this will start to load the 4G LTE boot animation and just hangs there all night. i have tried the [ROOT] VRALEC Bootchain - Allows us to Odin a custom recovery method and flashed a stock rooted rom also, just either hangs at the 4glte boot screen or just reboots over and over never getting passed the samsung logo at initial power up.
I have tried beanstown, i have tried everything i can seem to find on the forums. same 2 outcomes. I am using ODIN, and i have never had issues with this before (usually test something out every 2-3 days tops).
is there a chance somehow my partition table is all screwed up? i am lost with ideas at the moment.
lol. has this scared everyone off?
does any one have a stock backup of the NANDROID from their phone? i would be great if they could hook me up as i am in desperate need of one.
bump for ANYONE with any ideas on this first post
did you make a back-up? if not, download root66 to your computer and ODIN to that, if you can get into download mode
goldsmitht said:
did you make a back-up? if not, download root66 to your computer and ODIN to that, if you can get into download mode
Click to expand...
Click to collapse
i can get into download mode, and i have used odin to do root66. reboot and same thing happens and hangs. also flashed stock kernel.
I do not have my backup because either it has erased my internal sd card, or it is not accessing it.
I rooted my device. Everything's all good.
I flashed a rom (xposed framework) using Flashify.
My phone started going crazy after the reboot.
Now I'm stuck in the samsung logo screen.
I need help.
I dont have TWRP Recovery or anything else. My recovery is still the Android Recovery.
I have tried wipe cache and wipe/factory reset. Nothing works after rebooting.
My option right now is downloading a stock ROM and installing it via Odin.
Problem is, I don't know if my phone is region locked and I cannot find my region/country stock ROM.
So I'm going to assume any of them will work as long as it has the same android and build version as my phone.
I cannot access my phone.
Only able to go into recovery and download mode. A normal boot will just stay stuck on the samsung logo screen for hours.
Any help is appreciated. I am very new to this, please help me.
Which device?
Wiped everything and have no back ups anymore. Cant figure out how to install a rom. TWRP and Download mode still work but No matter what I flash I get stuck at samsung loading screen. Halp?!
Trying to get Tekxodus installed on my N920T which currently has nothing on it.
Still can not figure out what Im doing wrong. I wiped internal storage which I know I shouldnt have but when I flash Tekxodus I get caught in a bootloop until the phone powers off to charge. Even flashing skyhigh kernal after the rom does nothing. Still boot looping.
Use download mode to Odin back to stock. Then re-send twrp. Let it boot first. Then go back to twrp and flash your rom
I was able to restore a stock rom, install twrp successfully but this rom (teksodus) does not boot no matter how I flash it. Stuck at samsung screen again but this time on a custom samsung load screen. If I flash a new kernal I get stuck at the black samsung screen. Haha its been too long since Ive done this.
Got it all sorted, thanks!
Hello people,
I just tried flashing TWRP to my J7 Prime phone. Odin flash was successful and I could boot into recovery. I followed through normal procedure(data format and no-verity-opt-encrypt flashed). I did not flash any other zips and when i tried to boot back into System my phone didn't get through the Galaxy Prime logo. It wouldn't even show the boot animation. Before this happened, I did root my phone and everything was fine, I accidentally deleted google play once and also wanted to flash stock firmware so I did. After I flashed the stock firmware, when I wanted to root it again it would work after flashing magisk and booting into the system but after some time passes the apps one by one would begin to freeze and at last no app would even load. When i try to reboot at this point, the phone wouldn't boot back into the system anymore. It would get past the Samsung logo but the boot animation wouldn't even play as i was stuck in a black screen. I tried to restore with TWRP then, (Only restoring Boot, System and Data but I didn't wipe anything on the system before restoring. I think that this might be the issue but I just recently got into rooting.) but when i rebooted to use my phone it wouldn't get past the Samsung logo. The Samsung J7 Prime logo would show up, then 1-2 seconds pass and then reboot. This was a loop.
I was able to reflash stock firmware and get it to work normally. Since I can't risk bricking the phone as I can't get a new one after this experience I didn't flash anything again. Because after i restored with TWRP back then and now my phone bricking just because of a TWRP flash I think if I just give it some more tries (even with difference in procedure) it might just get hard bricked. I think flashing firmware so often might brick it. I really don't know but I can't risk bricking this phone.
The phone right now is OK. I just want to learn why this might happen, what would cause this and how to fix this. I will not flash anything because again I can't risk getting this phone bricked.
Just getting some information for me is enough as I am also curious about this problem,
Thank you.