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.
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.
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
UPDATE: Solved, i flashed TWRP over CWM using Odin, and was from there able to re-install the OS. Things seem to be working fine for the most part, with the exception of one random reboot last night.
Salomon3068 said:
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
Click to expand...
Click to collapse
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
buhohitr said:
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
Click to expand...
Click to collapse
I figured it out yesterday actually and forgot to update! Indeed I was able to flash TWRP with odin, since CWM seemed to be blocking me from doing anything. Once that was up and running, things went back to normal, i was able to flash CM 10.2.1 and things seem to be working now.
One thing though, while playing skyrim last night i had it on the charger next to me, and the phone randomly rebooted without any interaction from me. Was odd, but it hasnt done it since. Keeping an eye on it still.
I have a rooted and bootloader-unlocked Inspire 4G. A few months ago, I had been using the MoKee 4.2.2 ROM for some time, and one day, my phone's screen simply froze. I thought I shouldn't be worried about it, so I pulled the battery off, slapped it back in and tried turning on the phone again. It never got past the MoKee loading screen. I tried charging it, leaving it to boot for hours but nothing.
Next, I tried rebooting into CWMrecovery to try different stable backups I had from some time before that happened. The backups restored successfully, but again, the phone stayed stuck in the loading screen. I tried the same with 4EXT Touch Recovery and wiping all the data before the backup, but still nothing worked.
Since I was too busy at the time to install a new ROM and flash a new boot image, I decided to put the phone away and use my backup Galaxy Ace. Today, a few months after that happened, I tried to boot the phone into bootloader and I can't even achieve that. Holding the volume down rocket and power buttons, the phone still boots normally and stays stuck on the loading screen.
What weirds me out the most is that this was all random--I did not drop the phone or did things to it that could break it.
I feel if I could get into recovery I'd be able to do something else about it.
Any ideas?
Me too
Weird, mine just did the same thing today. Crashed, had to pull battery, now stuck at Mokee. Tried clearing DC, cache, factory reset. No luck.
Samsung Galaxy S5 G900A (AT&T)
Previously on a day off I became very bored, and decided to root my phone. After playing around with everything for a day i did not like it. So i just went into recovery mode and did factory rest on my phone. Now I used supersu and a basic root everything worked perfect after i rooted it. But once I tried to put the stock firmware back on my phone it started acting funny. With showing Unfortunately Context Service has stopped. It was so absurd my phone couldnt function properly. I tried flashing the stock firmware on there in hopes that it would fix my problem, but it only made my phone completely inoperable. I have been trying multiple ways to fix this using odin v3.09 and odin v 3.10.6. Here are some of the files I have tried to get my phone back to stock. (G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5) I have tried downgrades. Odin seems to fail on every single one besides this set up (AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5) (CP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5) (CSC_ATT_G900AATT1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5) Odin loads those three files onto my phone perfectly with in 3 minutes but after they are installed on my phone. When i power it up it gets through the first screen and only shows half of the samsung logo freezes and goes to a black screen with a blue light. I have been working at this problem for a little over a week a couple hours a night and i really can not seem to make any progess. Help would be greatly appreciated.
Still having troubles
Flashes firmware perfectly fine but still can not seem to get past the samsung logo loading super slow and then just cutting out and going to a black screen with a blue stationary light on top left of phone.
Still looking for advice
bump
ksutinen said:
Flashes firmware perfectly fine but still can not seem to get past the samsung logo loading super slow and then just cutting out and going to a black screen with a blue stationary light on top left of phone.
Still looking for advice
bump
Click to expand...
Click to collapse
Boot into recovery mode and do full wipes wipe cache ,wipe del Vick cache,factory reset
I think this will resolve your problem
Regards
Mohamed786