So hello people.
A few minutes ago I rooted for second time( I unrooted it on the first time) my samsung galaxy s5 SM-G900F with Odin. I booted just fine.
After that I installed Philz touch 6 recovery and it boots just fine, but if I leave my phone to boot normaly, I have to wait for 30secs give or take on the Samsung gif, and then when it loads up, it says unfortunately System UI has stopped, and there is no background or anything. I can use the phone, but if I lock it its done, I gotta reboot it again and so on. I tried running safe mode, and I gotta say I think I messed it up.
I left "Auto reboot" and "F. reset time" ticked, even though the guide said I should uncheck it, I messed up, but idk if it made any difference. I also read that it might take some time for all of that stuff to properly install or something, so it might be good tomorrow. Thanks for your time and pls respond ASAP since Im on vacatiion and I really need the phone fully functional. I will update this as it goes for any news.
Sincerely,
Deathrunc
PS. I will just back everything up and flash the stock rom again. then try to do everything right tomorrow. In the meantime, if anyone knows whats up, pls tell me.
EDIT: I flashed the stock rom, and re-rooted the phone with the same file, without installing Philz touch 6 CWM this time and it worked perfect. Do I need to unlock my bootloader for it?
Hi there,
You'd be best served asking for help from the experts who own your device here:
Galaxy S 5 Q&A, Help & Troubleshooting
Good luck
Related
Hi guys...thanks for taking a minute to help me out.
I have been using the Cyanogenmod Nightlies for a few months, and have recently been experiencing a few random quirks since upgrading to the new version of Android. I decided that I'd do a full wipe and then install the new nightly. Everything worked fine, the phone booted, I could use apps, etc. Then, I decided to restore some of my apps and data from Titanium Backup.
It took about 40 minutes, and then finally got stuck on 98% which was "android data" or "system data" or something like that...i checked back a few minutes later and the phone was completely dead/frozen. I eventually pulled the battery and rebooted the phone, and now it's just stuck in a bootloop.
When I try to boot into recovery, it freezes on the "Samsung Galaxy S3" screen for a while, and then turns off. However, i CAN boot into download mode.
Can someone please point me in the right direction here? I know that android 4.2.2 reworks some of the system folders, making reverting back to a previous version difficult..? I don't know what to do. Really, I just need to be able to get into recovery, but I'm too ignorant to figure it out.
Thanks so much for taking the time to help me, it's very much appreciated!
hold tight, guys! for some reason, it booted into recovery after like the 50th try. hopefully i can figure it out from here! thanks
Hello fellow XDA members! I am a Noob.
So I believe I have a Bricked Galaxy Note 10.1. Model GT-N8013
I Rooted Stock ROM, and flashed Collective Edition 5 Dark Side.
So heres what happened, everything seemed fine, until I made a mistake, I was Pimping my ROM with the PimpMyRom app. Every change seemed fine and my note worked, but when i saw the double boot screen slide in the app, i did what it said, i have the imf support or something like that. Then after i had the ''support'' needed, i clicked install button on the double boot slide, it seemed to do something and requested nothing, so i went ahead chose a second clip, and clicked set as second boot screen. It said it wont take effect until the 3rd boot, so i rebooted 3x, but at the third time, it was stuck at the boot screen with the galaxy note 10.1 logo ! It did not start or did anything, over time it would turn off and automatically reboot, but it would get stuck again !.
To attempt to fix it, I Booted into recovery (CWM) and did everything i could. I wiped nearly all cache, factory reseted, then out of fear, i flashed the stock firmware ROM from Sammobile website, with ODIN, and to my knowledge, it got worse!! It booted, seemed to do something then in the logo screen it got stuck once again!! Stock recovery says unable to mount /efs, i don't believe EFS is completely corrupted, I left it stuck for awhile and it shut down in like an hour. Help, what can i do to fix this!?!?!?!
Device cannot boot up.
I could boot into recovery and download mode only.
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
jusliloleme said:
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
Click to expand...
Click to collapse
i did what u said...but all i got is i able to get through the logo but without seeing anything only able to hear the sound. any other tip? i got the same problem as above.
Hello everyone, i come bearing bad news. Over the last few months my Htc One m8 on Verizon has been deteriorating slowly. I was running a dirty unicorns 4.4.4 rom with TWRP custom recovery on 2.8.4.0. Then, one day, out of know where, my recovery stopped working. I couldn"t boot into it no matter what i tried. So naturally I tried reinstalling it but it gave me an error. So I gave up on trying to install custom roms. Soon after, my phone began swiping and typing and opening apps on its own. This got out of hand very quickly so I decided to factory reset it. The reset was successful and I though maybe I could flash CWM over TWRP then re flash TWRP. So i flashed CWM and everything was normal there up until I rebooted into recovery. The recovery mode looked like the stock recovery and if i try to reboot, It sends me to the splash screen and wont load my rom. It just stays at the HTC screen with the red text at the bottom. I can get to fastboot mode but can't do much from there because adb doesn't pick up my phone. I've decided that ill probably have to get a new phone and use bluestacks until then. But any help or advice would be greatly appreciated.
Hi there,
You'd be best served asking for help from the experts who own your device here:
Verizon One (M8) Q&A, Help & Troubleshooting
Also please see this thread too: [GUIDE] RETURN TO STOCK(Mostly)
Good luck
Hey guys i have a somewhat serious issue here. About 3 months ago I performed a backup of my entire system on my SD Card but somehow it got erased. This is where things start to go bad. I tried to make another one but it rebooted and the boot screen became disorted. So I tried performing a factory reset. I was given the same screen. I tried to reboot to recovery manually and was given the same screen. So now iam unable to reset, backup, or change my rom. I hasn't bothered me until now. I have a Samsung Galaxy Exhibit SGH T599N. It is currently running cyanogenmod 5.1 but from a different developer. I think it's called Meticilous Devlopment or something closer to that. This actually started happening when I downloaded NikeRun and when i turned on the GPS thats when i got the disorted boot screen for the first time. Keep in mind that Iam still able to load it up, use it, make calls, search the web, etc. I just can't load it into my custom recovery which is TWRP. Please help! Thanks so much.
Hi,
Thanks for using XDA Assist Kindly post here Android Q&A, Help & Troubleshooting
Good Luck!
Let me start by addressing I know this isn't the sprint thread but there's a lot more development here which equals more help. Plus this issue seems to be able to happen to any variant.
Second, this isn't my device I'm trying to see if it can be fixed for a friend. I'm not that familiar with Samsung devices but I have been able to get them working in the past via Odin or kies but this time I need some help.
So this is what's going on, my friend recently rooted his S6(SM-920P) not sure which method he used (don't think it matters at this stage) and was on stock rom (LP5.0.2) with xposed framework installed. He hadn't changed the kernel AFAIK oh but I did install TWRP for him and everything was working. Long story short he woke up a couple days ago to his phone being unable to turn back on. I told him how to get to download mode and I asked him what did it say on the top left corner it said something like "system binary not SEandroid locked" underneath that it said fac lock
So I had him give me the phone thinking somehow it did a OTA update while he was asleep or something either way I was confident using Odin to flash the firmware would solve the issue. Had the firmware finished flashing I'm confident it would have but halfway through Odin simply froze on installing system. I figured its just gonna take a while 45 mins later it was still stuck at the same spot.
Not really thinking about it I figured I will just reboot the phone back into download mode restart the process it should be fine. Not a good idea. Now all I get is a green screen saying to access the smart switch emergency recovery system. But it gets better.
My computer isn't recognizing the device now. I installed smart switch software and it's not recognizing it. I even installed Kies and it's not recognizing either.
Is his phone toast or what? I tried emergency system recovery but I need the S/N of his phone to possibly get this thing working again, but it boot into anything anymore except the screen that says Samsung switch...
PLEASE HELP ME if it's bricked it's bricked I get that but if there's a way to figure out what to do I'm all ears. Thanks in advance