So, I've been trying to root my Galaxy s5 for a while now and I just got it to work successfully a few hours ago. With that, I installed CWM and everything was fine.
Now, I downloaded the latest nightly of CM12 for the S5 and I threw it on my SD card and ran my phone with the up volume home and power thing, selected the zip and it's now looping. It's been looping for maybe 25-30 minutes. It stopped and said it was upgrading apps for optimization, rebooted and is now stuck on the loading screen for CM12.
I literally know nothing about CM12 or rooting or any of it, I just successfully did it today, so I'm extremely new and know nothing. I didn't factory restore my device, I didn't do anything fancy like that, the tutorial didn't say that I needed to, I just selected it and installed and rebooted.
I tried taking the battery out, and it's still doing the same thing.
Any help is appreciated.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
Related
Hey XDA, just a long time stalker who has finally given up trying to find his solution on already posted items (I think 10 hours of trail and error means I'm not gonna catch what I'm failing to see...)
When I first got my galaxy s4 I downloaded KangaBean and it was on 4.2.2 I believe. Today I decided I should upgrade to 4.4.2 since I've only been hearing good things about it, and I wanted the slight updates that came with it.
Well, I have a AT&T s4, sgh-i337 that was on CWM 6 when I tried updating to another ROM, the first one I tried was GOOGLE EDITION 4.4.2 BY DANVDH. Did a wipe, cache, dalvik, format system, flashed it, flashed loki doki, said no to re-root/root fix prompt that followed, then I came to the yellow triangle, I thought that was odd, believed I missed something.
So, I downloaded TWRP 2.5.0.2 like the thread suggested, tried again, no luck. Then I tried Unoffical Carbon KitKat, which just caused the "Samsung Custom" logo to stay on indefinitely (I let it sit for 40 minutes before giving up.) After 2 failed ROMs, I tried KangaKat, updated version of KangaBean, so it should be just dandy right? Narp, same luck. This one boots, then reboots into recovery.
At this point I considered myself to be stupid in some way so obvious that I would die before I noticed it. So, then I just flashed the stock firmware thats like 2.5 gb through odin, re-rooted and installed CWM 6.0.4.4 LOKI'd and tried to flash KangaKat, being confident it would work this time, again I got boot to the logo and then reboot into recovery.
At this point I attempted the other 2 ROMs again, multiple times.
After some sobbing, I re-did the stock firmware, tried again, failed again.
My sadness turned into rage, I just destroyed one of my micro sd to usb-s because it was being annoying and I was annoyed, I took a picture and got over it.
I tried a 3rd time with the re-flashing stock firmware and tried with twrp again, no cigar.
Now, after MANY hours and MANY false hopes... I shall be using my blackberry and hoping to return to android soon, if somebody can help me figure out what I'm missing. Many thanks ahead!
Did you do lokidoki after?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Did you doa hard reboot clear the cache and davlik after it got stuck on the lock screen ? It seems odd that it would just not boot up at all. I was about to wonder if maybe it was the CM kernel bug that will keep it from booting past the initial screen but you tried aGE rom so...
Guys,
I'm not even sure where to start with what I'm seeing, but maybe you can help me.
I have had Timur's ROM on my N7 2012 for a couple years. It's been crashing randomly, even though I have few things installed on it, and a good power supply. I took it out of my car and put it on an iPad 2 amp supply, and it still crashed a bunch so I knew I needed to wipe and reinstall. I also wanted to go from 4.2.2 to 5+, which I know takes away a lot of the good features I need (like power on/deep sleep).
I booted into TWRP and wiped my tablet, which appeared to softbrick it (I think I have the usage right from searching). I downloaded the Pure Nexus 6.0.1, CM13, and already had Autodroid ROMs to use. I tried to install Pure through ADB sideload, and got it installed. When I finished and tried to reboot, it said I had no OS. When I rebooted, I got the boot animation, and nothing else.
Long story short, I tried Autodroid and CM13, and using CM13 I got it back going. Unfortunately, every time I try to flash another ROM over it, it will no longer go past the boot screen. With CM13, it boots properly, but doesn't like the gapps pico I tried to install (error message when booted, keeps returning to the same pop up error).
I'm quite sure there's something I'm missing, but I don't know what it is.
Thanks!
Eric
Ok, before anyone goes nuclear on me, I think I better understand what happened. When I got ANYTHING to work, I stopped doing anything. As I understand, it wasn't functioning...it was just in a temporary mode of some sort.
After not being able to get it to work properly, I used this: http://forum.xda-developers.com/showthread.php?t=1781250 to try and restore the system. I followed all the directions, except for using the 5.1.1 version of the ROM, and used the corresponding file name for the zip file used.
After doing so, the bootloader won't go to TWRP, but goes to the pic as seen below. I did reboot the tablet, and after waiting quite a while, the tablet came on, but I don't understand what that picture means.
Thanks!
Eric
Ok...I realized that I lost root. I'm fixing it now. I had read before, but didn't understand what I saw.
Thanks,
Eric
Hello Folks,
Looks like I borked my Note 3 tonight. Was attempting to install a new ROM and things didn't go well at all.
Phone was last running BajaROM 4.4.2 with Safestrap as a virtual recovery.
After a failed install of a new ROM from SS, I tried restoring from the backup file I just made tonight before upgrading the OS. Failed. Then, from SS, I wiped the phone and attempted to install the old AllianceROM, and it too, failed. When I went to reboot phone to see what would happen it simply loops the custom Note 3 screen, then blue text Recovery appears in the upper left hand corner, then repeat. Can't boot into recovery, and now, can't get back to Safestrap. All I got is Download mode when I pull the battery and hold Power/Volume Down/Home when I reinsert battery.
I'm following the guide at this link currently, http://forum.xda-developers.com/showthread.php?t=2483380, but have to wait over an hour for the stock Android firmware to download from one of the few hosting servers that still have one of them loaded.
In the meantime, is there anything else anyone recommends? This is my primary device so I'm kinda screwed till I can get it back up again. Any additional info would be appreciated.
Thanks.
For anyone reading who might be in a similar predicament, the soft-brick fix at the link above got me up and running again. Got the Note 3 running on stock OF1/5.0, rooted, and am now looking into unlocking bootloader so I can properly upgrade to 6.0.
A little disappointed no one bothered to respond in what could've turned into a bad situation, but the site itself did bail me out so no big complaints. Thanks to all the devs for their hard work.
Hello all,
I recently went through the process of installing CM 14.1 on my Verizon-Unlocked Galaxy S5.
Everything was working fine until about 3 weeks ago when I started messing with the system settings.
My phone started freezing and crashing, so I attempted to reinstall CM 14.1 multiple times.
I have wiped everything on the phone multiple times through TWRP (System, Data, SD Card, Everything...) and I am still having the same issue.
The phone boots fine, and I am able to get through the first two menus in the initial setup, but then the screen freezes and the phone restarts.
I have tried replacing the battery, thinking that would fix the problem, but it didn't...
Should I revert back to the stock ROM and start from there, rooting and such, until I make my way back to CM?
Thanks everyone, Luke
If youre still having problems, try reflashing your rom and then flash an older version of opengapps, I think I used the one from 01/16/17. The new opengapps were giving me the same exact problem.
Dang, I wish I would have seen this sooner... I went ahead and flashed back to the stock Verizon ROM with root. Thanks though! Maybe this can help someone else.
Hi, recently, I wanted to download the Xposed Framework. Everything turned out to be fine until I rebooted my phone. Based on the last step, it states that it might take longer than usual (10-20 min). Well, my phone ran on for about half an hour on the screen that says Samsung Galaxy S5 and so I decided to reboot it by taking out the battery. The same thing happened and I retried it a few times before one of the tries managed to go past the Samsung Galaxy S5 Screen and showed the Samsung icon. I thought everything was alright and let it run. It ran on for about 2 hours before I decided I had did something wrong. I wiped off all my data and of course, when I rebooted it on TWRP recovery, it states No OS installed. I decided to take this chance to upgrade my OS to 7.1.1 Nougat. Right now it is still downloading and I would like advice on what to do next. Thanks in advance!
P.S Since this is my first post, i am unable to provide the link in this message, if there is a need to, I can provide it in the chat.