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
Related
Good evening everyone. I was running a custom mod for some time now. Everything was working well, until about 1 month ago.My phone would randomly turn off, and get stuck in a loop. All of a sudden as I was trading currency pairs from my phone. It looped again and has not been able to turn back on. So I searched the threads, and decide to change the custom mod to see if it would work (serendipity). In which I loaded to my sd card, ran from CWM, and it would get stuck on the samsung logo screen.
I then found this link. http://forum.xda-developers.com/showthread.php?t=1524081&page=27 which seemed promising. I have downloaded the file recommended, but I can't get into DOWNLOAD mode, because I keep getting stuck on the samsung screen. The only thing I can do is boot into CWM. So once I am there, what do I do? Where do I need to load the "Stock_SGH_I997_UCLB3_Repartition-One-Click" program as it isn't a ZIP file. Any help would be greatly appreciated.
Thanks in Advance,
Alex
After updating to Jelly Jean I've decided to wipe the phone in order to start clean and that's when everything started.
After wiping the phone it just didn't turn on automatically and everytime I've tried to do it I ended up on an Android animation, the same we get when we update the system, and anything happens, the animation goes away and the screen gets black.
So I've searched and found a way to get into the boot options and selected "Normal Boot" and everything seemed to be fine, but then I went out of baterry and after a full charge the Android animation came back. I did all the boot thing over again and now everytime I have to restart the phone I have to boot manually.
Can you guys help me?
Had exactly the same pub when I upgraded from its to job ota... And it's not the first time I read about this here. The only stable fix for me was to download rsd lite + the full firmware and to flash it through fast boot mode. This definitely looks like a corrupted upgrade.
I'm gonna send it back to Moto. Thanks for helping.
I've had my phone rooted with CM10.1 since I got it back in December and last week I was messing around with the new nightlies but because of the all the constant reboots and freezes I decided to go back to an earlier verson of CM10.1.
Now my phone will not boot up and stays in the CM loading screen, I tried to get into recovery but I just feel a vibration and the screen stays dark although sometimes it just goes straight to the boot screen and then stays there.
Have I messed up my phone permanently? Any help will be greatly appreciated (I'm desperate). Thank you very much
Edit: I can get into Odin.
Edit2: After a lot of trial and error I managed to get into recovery, wiped data and reflashed CM, thankfully it worked. Although no one responded thank you.
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.
Sorry everyone for this annoying post but I have done research enough to think that I may be out of luck so you guys are my last hope here.
Here is the senario;
I have been running Cyanogenmod 12 (courtesy of Sultan). Once the ROM was discontinued I decided to give Paranoid 5.1 a shot. I downloaded the new rom, suggested SuperSU and Gapps and booted to the most up to date TWRP. I flashed the rom, then supersu, and finally Gapps and then rebooted my phone. The phone stayed in the boot screen for about 45 minutes (maybe even an hour) so I powered off the phone, pulled the battery, and attempted to boot back into recovery using the power and volume buttons but nothing was working. The phone would just keep vibrating (pulsing) until i let the buttons go and then jump right back into the booting screen until I turned the phone off again. Hopefully I am doing something wrong and there is an easy fix but Im afraid that I now havae a brick on my hands.
Please help,
SuperNewb
[Update]
Now the phone will hold the boot screen for a couple minutes then the screen just goes black. Not sure what that means.
Also, just so you guys dont think im too ignorant, I will say that I I have flashed at least 10 different ROMs before this so I would like to think that I have a decent understanding of how this all should work.
My mistake on posting this question here. I have reposted in the Q&A Forum.