After installing the unofficial CyanogenMod 11 build, whenever I try to boot into TWRP it hangs at the logo.
I've went back to stock and reflashed the latest TWRP via Odin but it refused to go past the "teamwin" screen.
I tried different versions of TWRP and nothing works. My SD Card is not detected either; I don't know if that's related.
I'm not sure where else to go from here.
You can try the version of TWRP before the current one, read somewhere that a few people where having problems with latest version. Might help.
Sent from my SM-N900P using XDA Premium 4 mobile app
tonyevo52 said:
You can try the version of TWRP before the current one, read somewhere that a few people where having problems with latest version. Might help.
Click to expand...
Click to collapse
I'll give it a try and update with results.
EDIT: Didn't work. Got stuck on the "RECOVERY BOOTING....." screen with nothing coming up.
Just flashed 2.6.3.0 and got stuck at the splash screen again.
Read through the TWRP feed, might something, or someone who can help.. http://forum.xda-developers.com/showthread.php?t=2471564
Sent from my SM-N900P using XDA Premium 4 mobile app
Not sure what happened but my after my Note 3 detected my SD Card, recovery started working again.
Related
I have a TF201 and I have it rooted and unlocked. I tried installing CWM Recovery using some method I found online using fastboot. It seemed to work but whenever I tried to boot into recovery it would just say "Booting recovery kernel image" and stay there. So I restarted the device and went to the playstore and downloaded CWM and flashed it from there. Same thing happened. So I installed TWRP via fastboot and yet again I couldn't boot into recovery. Take in mind I'm a noob so I probably did something wrong. I then went to wipe the data to retry and of course it said the same message. I waited awhile then restarted the device. Now I'm stuck on the Asus splash screen and if I turn it off it just restarts again. Please help me! I clearly did something stupid, I didn't think it would be this much trouble to load a ROM. Thanks!
So can you access fastboot?
Sent from my Galaxy Nexus using xda premium
Makrilli said:
So can you access fastboot?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Nope. No matter what I do I go back to that screen. I let it die and turned it back on, same thing. Upon further research I've come to the conclusion that it's hard bricked so I guess I'll be sending it in. But for future reference, what steps should I take to root, unlock, and install CM10 on it? Because there's so many guides that approach these things in so many ways which is what caused me to mess up. I learned my lesson at least.
was installing the hyperdrive Rom using clockwork recovery mod, it says it installed sucessfully but when i go to reboot the device it just going into reboot loop, i can get back into recovery mod but when i try to factory reset and try it again it just does the same thing again, tried installing a different rom and still same thing, what am i doing wrong?
im having the same problem. i cant boot into recovery. is there anything i can do. i was on cm10.1 before this and it worked fine. i flashed hyperdrive using OUDHS and it installed and everything. i let it sit for 10 minutes like it said to then i continued to reboot... and now its stuck on the custom padlock screen and im cant boot into recovery for some reason...
OMsupp said:
im having the same problem. i cant boot into recovery. is there anything i can do. i was on cm10.1 before this and it worked fine. i flashed hyperdrive using OUDHS and it installed and everything. i let it sit for 10 minutes like it said to then i continued to reboot... and now its stuck on the custom padlock screen and im cant boot into recovery for some reason...
Click to expand...
Click to collapse
Try to get in to Odin mode. If you can flash the Stock Image and go from there.
RLS7 Verizon S4 continuous reboot loop
galaxyfans said:
was installing the hyperdrive Rom using clockwork recovery mod, it says it installed sucessfully but when i go to reboot the device it just going into reboot loop, i can get back into recovery mod but when i try to factory reset and try it again it just does the same thing again, tried installing a different rom and still same thing, what am i doing wrong?
Click to expand...
Click to collapse
Hi I have the exact same pb, I flashed several times my S4 (I was on RLS4 before) following the instructions, no way to get out from the endless reboot loop.
There is a suggestion using ODIN, I am not very familiar on how to do that, any help?
Thanks
abalgir66 said:
Hi I have the exact same pb, I flashed several times my S4 (I was on RLS4 before) following the instructions, no way to get out from the endless reboot loop.
There is a suggestion using ODIN, I am not very familiar on how to do that, any help?
Thanks
Click to expand...
Click to collapse
dont install any audio mod and also dont install any of the music players just the samsung one !
before you go through all the trouble of ODIN, which seems to be everyones answer now a days, it is a kernel issue, flash a verizon loki kernel. It should boot.
abalgir66 said:
Hi I have the exact same pb, I flashed several times my S4 (I was on RLS4 before) following the instructions, no way to get out from the endless reboot loop.
There is a suggestion using ODIN, I am not very familiar on how to do that, any help?
Thanks
Click to expand...
Click to collapse
First, if you have a back up, restore just the system partition (this will also format your current /system) Then do a factory reset and reboot. Now I if that doesn't work, Odin is your best bet.
Sent from my SCH-I545 using xda app-developers app
FOR anyone installing Hyperdrive, the most probable cause of boot loop in the Walkman Music App. Don't choose it in Aroma!!!
If you already have, the only way to fix the boot loop is to ODIN back to stock, as Dark Menace suggested.
He can PM you the stock image, which you will have to flash in ODIN to successfully boot up again.
hey I do plenty of flashing, and from time to time get into trouble... But ODIN is not the first choice to fix... Please read the forums:cyclops:
Sent a few PM's to see if that helps. You can try the kernels first then go from there.
Sent from my SCH-I545 using xda premium
fix
I had the same problem had to go back in odin mode and reflash a old stock. If that does not work reset data and cache and install a new rom. Worked for me
DarkMenace said:
Sent a few PM's to see if that helps. You can try the kernels first then go from there.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
I will try again without selecting the music app. I was always selecting the Sony one. I will try this afternoon and keep you informed.
Thanks
abalgir66 said:
I will try again without selecting the music app. I was always selecting the Sony one. I will try this afternoon and keep you informed.
Thanks
Click to expand...
Click to collapse
It worked perfectly if we do not select any music app. Thanks
Device gets stuck at S4 logo with blue font RECOVERY BOOTING, even after Odin, any ideas??
I'm so stuck!
TheAxman said:
before you go through all the trouble of ODIN, which seems to be everyones answer now a days, it is a kernel issue, flash a verizon loki kernel. It should boot.
Click to expand...
Click to collapse
I can't get my phone to see the the SD card in recovery. My Verizon Galaxy S4 is stuck in a boot loop thanks to Hyperdrive RLS12 and Odin fails every time I try it. Any help would be greatly appreciated!!
Surge1223 said:
First, if you have a back up, restore just the system partition (this will also format your current /system) Then do a factory reset and reboot. Now I if that doesn't work, Odin is your best bet.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I am trying hyperdrive on Baseband I545VRUEMJ7 and build JSS15J.I545VRUEMJ7 (4.3). I am able to root and install safestrap. Even hyperdrive/dirty unicorns (i tired both) installs fine, but ends up in reboot loop. am i missing anything here?.
I am on the MJ9 radio flashed via Odin, rooted and unlocked bootloader. Have TWRP recovery and just flashed and set up Trents B7. Was having issues with colors and didn't have a lot of time to play around with it to get it where I wanted so I went to restore Alliance 26 back on and noticed that when I swiped the go bar, it stuck and then rebootet into recovery.
I have tried several times to wipe data and TWRP or Philz wont let me. I can boot back into the rom and it is working but whats wrong with my recovery?
I even Odined TWRP and then tried Philzs thrroigh Odin hoping I just needed to reload my recovery.
Any help would be appreciated.
Sent from my GT-N5110 using XDA Premium HD app
glockman4519 said:
I am on the MJ9 radio flashed via Odin, rooted and unlocked bootloader. Have TWRP recovery and just flashed and set up Trents B7. Was having issues with colors and didn't have a lot of time to play around with it to get it where I wanted so I went to restore Alliance 26 back on and noticed that when I swiped the go bar, it stuck and then rebootet into recovery.
I have tried several times to wipe data and TWRP or Philz wont let me. I can boot back into the rom and it is working but whats wrong with my recovery?
I even Odined TWRP and then tried Philzs thrroigh Odin hoping I just needed to reload my recovery.
Any help would be appreciated.
Sent from my GT-N5110 using XDA Premium HD app
Click to expand...
Click to collapse
Check out the data corruption thread stickied in General section. It will show you how to fix this, very easy. Make sure you thank the OP
Yes, I found it about an hour ago. I ended up wiping my internal SD card and that fixed it. I've never had that happen to me before.
Sent from my GT-N5110 using XDA Premium HD app
glockman4519 said:
Yes, I found it about an hour ago. I ended up wiping my internal SD card and that fixed it. I've never had that happen to me before.
Sent from my GT-N5110 using XDA Premium HD app
Click to expand...
Click to collapse
Yea it's been happening ever since 4.3.. TWRP and Philz have both done it for me.. But luckily we have a easy fix for it thanks to @Deckoz2302
Hello, I have an i717 and I'm having an extremely annoying issue with LiquidSmooth 3.1. So basically, after the first boot/setup, it runs perfectly fine. Beautifully. But if I turn it off, it won't load the OS when I turn it on again. It'll sit on a black screen for several hours. I've tried reinstalling this ROM about 5 times and had the same issue each time.
Anyone having the same issue, or know a fix?
MoronDroid said:
Hello, I have an i717 and I'm having an extremely annoying issue with LiquidSmooth 3.1. So basically, after the first boot/setup, it runs perfectly fine. Beautifully. But if I turn it off, it won't load the OS when I turn it on again. It'll sit on a black screen for several hours. I've tried reinstalling this ROM about 5 times and had the same issue each time.
Anyone having the same issue, or know a fix?
Click to expand...
Click to collapse
Just restarted the phone, booted after the 12th time.
LS goes through the bootanimation twice so it will look like its boot looping. Plus it does seem to take a while to boot into the os, just gotta be patient with the ROM on initial boot.
sent from my sweetened CandyKat SGH-I717
dzee206 said:
LS goes through the bootanimation twice so it will look like its boot looping. Plus it does seem to take a while to boot into the os, just gotta be patient with the ROM on initial boot.
sent from my sweetened CandyKat SGH-I717
Click to expand...
Click to collapse
This is really weird. I formatted all of the partitions, and did a fresh re-install of LiquidSmooth 3.1. It installed just fine, the Polluti0n V2 patch installed fine as well. But when I tried installing the Gapps (pa gapps stock 4.4.4 20140629), it came up with:
"file_getprop: failed to stat "/system/build.prop": No such file or directory.
E: Error in /sdcard/pa_gapps-stock-4.4.4-20140629-signed.zip
(status 7)
Installation aborted."
MoronDroid said:
This is really weird. I formatted all of the partitions, and did a fresh re-install of LiquidSmooth 3.1. It installed just fine, the Polluti0n V2 patch installed fine as well. But when I tried installing the Gapps (pa gapps stock 4.4.4 20140629), it came up with:
"file_getprop: failed to stat "/system/build.prop": No such file or directory.
E: Error in /sdcard/pa_gapps-stock-4.4.4-20140629-signed.zip
(status 7)
Installation aborted."
Click to expand...
Click to collapse
Status 7 is upgrade your recovery, but I have never seen it hit with gapps or just gapps.
Weird
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
Status 7 is upgrade your recovery, but I have never seen it hit with gapps or just gapps.
Weird
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
How do I fix this?
MoronDroid said:
How do I fix this?
Click to expand...
Click to collapse
What recovery are you running?
Have you tried a different gapps package?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
What recovery are you running?
Have you tried a different gapps package?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I have tried 3 different Gapps packages, all had the same result. I don't know what recovery version I am using. But I'm using CWM 5.5.0.4
MoronDroid said:
I have tried 3 different Gapps packages, all had the same result. I don't know what recovery version I am using. But I'm using CWM 5.5.0.4
Click to expand...
Click to collapse
CWM is your recovery and your version#
TWRP is also a recovery used.
Let me ask you how long have you been flashing on this version of recovery and is there an updated version?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
CWM is your recovery and your version#
TWRP is also a recovery used.
Let me ask you how long have you been flashing on this version of recovery and is there an updated version?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I purchased this phone used, and I've had it for 2.5 weeks and have been flashing every couple of days between CM10.1.3 and LS 3.1. I believe there may be an updated version, I'll look around.
MoronDroid said:
I purchased this phone used, and I've had it for 2.5 weeks and have been flashing every couple of days between CM10.1.3 and LS 3.1. I believe there may be an updated version, I'll look around.
Click to expand...
Click to collapse
Oh yeah....if you are flashing CM 10 with it wow. That is quite an older version and LS 3.1 is kit kat. CM 10 is the equivalent of JB so your bouncing back and forth and the up to date recoveries were designed to handle KK.
go to development and find the TWRP thread from "GIMMIEORILLTELL". it is TWRP version 2.8.0.1 ???
TWRP is a touch based recover which is sooooooo simple to use. No more toggle of the volume rocker.
Download and flash like you would any rom.
Once flashed, boot up whatever or pull battery and replace.
Boot back into recovery and it will be there.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
Oh yeah....if you are flashing CM 10 with it wow. That is quite an older version and LS 3.1 is kit kat. CM 10 is the equivalent of JB so your bouncing back and forth and the up to date recoveries were designed to handle KK.
go to development and find the TWRP thread from "GIMMIEORILLTELL". it is TWRP version 2.8.0.1 ???
TWRP is a touch based recover which is sooooooo simple to use. No more toggle of the volume rocker.
Download and flash like you would any rom.
Once flashed, boot up whatever or pull battery and replace.
Boot back into recovery and it will be there.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I'll surely give it a try, but not at this ungodly hour. I'll be without a phone for the day, but oh well.
captemo said:
Oh yeah....if you are flashing CM 10 with it wow. That is quite an older version and LS 3.1 is kit kat. CM 10 is the equivalent of JB so your bouncing back and forth and the up to date recoveries were designed to handle KK.
go to development and find the TWRP thread from "GIMMIEORILLTELL". it is TWRP version 2.8.0.1 ???
TWRP is a touch based recover which is sooooooo simple to use. No more toggle of the volume rocker.
Download and flash like you would any rom.
Once flashed, boot up whatever or pull battery and replace.
Boot back into recovery and it will be there.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Flashed... and now it continually boot loops with the Samsung logo flashing. I think it's bricked. This is fantastic...
MoronDroid said:
Flashed... and now it continually boot loops with the Samsung logo flashing. I think it's bricked. This is fantastic...
Click to expand...
Click to collapse
No no no.......deep breath. Relax.
Pull battery.
What were you doing?
And what did you do?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
No no no.......deep breath. Relax.
Pull battery.
What were you doing?
And what did you do?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I selected the Zip using CWM, and told it to flash it. It successfully flashed, replacing the recovery.img. Then I reboot, and it bricked. Keeps flashing the samsung logo, pressing the recovery buttons (volume up+ power) does nothing. There's nothing I can do. It's dead.
MoronDroid said:
I selected the Zip using CWM, and told it to flash it. It successfully flashed, replacing the recovery.img. Then I reboot, and it bricked. Keeps flashing the samsung logo, pressing the recovery buttons (volume up+ power) does nothing. There's nothing I can do. It's dead.
Click to expand...
Click to collapse
Continually powers off and reboots. Vibrates and such.
MoronDroid said:
Continually powers off and reboots. Vibrates and such.
Click to expand...
Click to collapse
PRAISE THE ANDROID MODDING COMMUNITY
http://forum.xda-developers.com/showthread.php?t=1784857
MoronDroid said:
PRAISE THE ANDROID MODDING COMMUNITY
http://forum.xda-developers.com/showthread.php?t=1784857
Click to expand...
Click to collapse
Could be a stuck power button my friend. Flick the back of the phone behind the power button with your finger.
Dont be shy, but done break your finger either.
Very common problem.
Pull battery. Can you get download mode?
Unless you flashed files for the wrong device, I don't think you are bricked.
If you can get download mode, you are not bricked.
What file did you flash?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
Could be a stuck power button my friend. Flick the back of the phone behind the power button with your finger.
Dont be shy, but done break your finger either.
Very common problem.
Pull battery. Can you get download mode?
Unless you flashed files for the wrong device, I don't think you are bricked.
If you can get download mode, you are not bricked.
What file did you flash?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I fixed her. All I did was install Odin, and reinstall the stock ROM (md5 file). Also just rooted it with a new verision of CWM.
I want to thank you for your patience.
MoronDroid said:
I fixed her. All I did was install Odin, and reinstall the stock ROM (md5 file). Also just rooted it with a new verision of CWM.
I want to thank you for your patience.
Click to expand...
Click to collapse
We were getting close to that option. Every once in a while, and I have had to do it recently, we have to return to stock. Basically it takes out all the garbage that has accumulated, even though our process is clean.
I couldn't get anything to flash, not even an alternate recovery. Went back to complete stock, Re root and Bob is your uncle. (that means everything as good as new).
Glad your fixed. Dont let it detour you from flashing. It's a lot of fun. Keeps me off the streets.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
I'm trying to use TWRP to update to a new cm12 nightly, but every time I select the zip and try to flash it, TWRP crashes and reboots. Is there something I'm missing? It's probably just a noob mistake... For example I only today figured out how to get TWRP to cooperate with encryption and my pattern lock on boot up, hah. I thought it wasn't mounting storage because something was corrupted. Anyways, thanks for any suggestions you can give.
What version of twrp are you using?
Sent from my Nexus 5 using XDA Free mobile app
I have the same issue. It is only with 5.1 Android and I am using 2.8.5 TWRP
Sent from my VS985 4G using Tapatalk 2
I had the problem this afternoon. I just tried it again and it worked. Didn't change anything.. never had problems like this on any other Nexus device. Creepy.
jd1639 said:
What version of twrp are you using?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
2.8.5.0. But I did some more tinkering today and eventually solved my problem. Here's to help you others who saw the same thing: I tried using progressively older versions of TWRP to see if they're used work, until version 2.8.2.1 I think. At that version, instead of crashing, it gave me an error that my zip file was corrupted. I deleted the zip and downloaded it again, switched back to version 2.8.5.0, and everything worked. (except for the Rom, which had bugs that made it unusable, but at least it flashed successfully and booted lol). Hopefully my experience can help someone else now.
I'm having issues with twrp hopefully I found the right thread. It shows no storage available? I'm trying to flash CM. Thanks