Ok I will admit it, I screwed up royally this time. My SM-N9150 (Hong Kong version) was slowing down and draining the battery fast. I could not get the downloader of a new stock ROM to work in Sammobile (tried multiple times, with adblock off but no go) and so I bit the bullet and used Kies to upgrade to Marshmallow. Of course this lost root but I figured I could just re-root (I had rooted using Odin with my old phone, but this one I had rooted using KingoRoot). However, none of the 1-click systems like KingoRoot worked, and neither did Chainfire via Odin (which caused problems on its own). So I flashed the latest CWM via ODIN. It said pass, so I went into recovery, did a backup, then did factory reset, installed SuperSu, wiped the caches and rebooted.
I kept getting weird errors where it would not let me boot into recovery or boot at all. so I thought that maybe CWM was not a good choice. I tried the newest version of TWRP but that gave me the "recovery is not seandroid enforcing" error. So I went back the CWM and tried wiping again.
After a very long Samsung logo bootloop, it eventually showed gearings turning but with instructions in Chinese. It then showed the logo again for long time and then showed something that had only 1 English word "system" and the rest in Chinese. There seemed to be 2 choices at the bottom of the dialog box. When I chose the one of the right, the phone showed a grey progress bar with Chinese letters above, but then went back into a bootloop; when I chose the one on the left, the phone turned off for a long time then restarted but again seems to be stuck at the Samsung logo screen before returning to the message with the word "system".
After it going into a bootloop that lasted over 1 hour, I pulled the battery and then went into recovery and tried restoring the backup I had made at the start. That just left me in the endless Samsung logo bootloop. I left it plugged in overnight hoping it would do something but nada. At one pint I did get a message "unfortunately, the system UI has stopped working" but screen was unresponsive to press OK, and it just went back into the bootloop.
I realize I did not do anything to unlock the bootloader. Would using KIES have locked the bootloader again? Could this be my problem, and if so, how do I fix it?
Related
Hi guys,
Really sorry to ask about this but tearing my hair out!
I have a P6200 UK model. I installed CWM v6.0.1.0 and it worked fine. The intention was to install Galaxy ROM HD (build #06), so I downloaded it, put it on my SD card, and installed from CWM recovery. The install got stuck on "Flashing boot" - so after around 15 mins I reset it.
It went into a boot loop on the initial Samsung logo. Luckily I'd previously re-flashed stock HC with Odin (to cure a dead Wifi problem caused by, I think, an errant install of Busybox) so I did this again, rebooted, and the system came up, text started scrolling up the screen, followed by a red error message (see picture) and a reboot. I was then once again stuck on the initial Samsung Tab 7.0 Plus log. I repeated the process and it didn't even get past the Samsung logo.
So I thought I'd try the newly released ICS Rom (GT-P6200_ATO_P6200XXLQ1_P6200OXALQ1) - this seemed to install OK, then half booted, did some text type installation stuff with the blue Android, then rebooted again, finally getting stuck on the Samsung logo with blue pulsating behind it. It never gets any further than that.
I tried flashing HC back - same result as earlier. I can also reflash CWM and sometimes it works, sometimes it doesn't. It seems I've run out of options.
So - question is - where (if anywhere!) can I go from here?
Help greatly appreciated, many thanks!
have you tried a system wipe in cwm? if not do a system wipe and reflash HC using odin.. same thing happen to me 2 days ago.. I think something is up with HD rom
I have a bit of a problem. I am on a moto g sold in the UK with Vodafone. I followed all the steps posted by root junkie on his youtube video in an attempt to install cyanogen, however cyanogen was taking a long time to load(30 mins without loading). So i went back into cwm to wipe data, this process stalled, so i pressed volume down and power to to go back to fast boot mode.Now when i go to recovery instead of loading into cwm my phone stalls at the white screen which says "warning bootloader unlocked". I have tried reinstalling cwm which seems to install fine, however when i click recovery it goes back to the warning screen. I have also tried reinstalling the stock firmware, however the same problem occurs.
Do you have any suggestions?
Thanks
andy07070 said:
I have a bit of a problem. I am on a moto g sold in the UK with Vodafone. I followed all the steps posted by root junkie on his youtube video in an attempt to install cyanogen, however cyanogen was taking a long time to load(30 mins without loading). So i went back into cwm to wipe data, this process stalled, so i pressed volume down and power to to go back to fast boot mode.Now when i go to recovery instead of loading into cwm my phone stalls at the white screen which says "warning bootloader unlocked". I have tried reinstalling cwm which seems to install fine, however when i click recovery it goes back to the warning screen. I have also tried reinstalling the stock firmware, however the same problem occurs.
Do you have any suggestions?
Thanks
Click to expand...
Click to collapse
I have sorted this now.
How did you solve it, I have the exact same problem except I was reinstalling the stock android.
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 Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
somesortofthing said:
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
Click to expand...
Click to collapse
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
ShapesBlue said:
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Well, can I somehow get my phone into working order? Because it's as good as bricked right now.
Hi guys, so recently I bought a Galaxy S6 Verizon off of eBay. I got it for fairly cheap because it was stuck in a boot loop. I usually have no problem fixing stuff like this, but this time is different. So the first thing I tried when I got the phone was to do a reset and cache wipe from recovery. I rebooted the phone and it showed a screen that said "Android is starting, optimizing app 9 out of 31." when it got to 21 the phone rebooted and went back to 9. It did this several times before I attempted to wipe/reset again. I then downloaded the tar file G920VVRU4CPH1 and flashed it in Odin. I did a manual reset before the phone booted, and it is doing the same thing again. reboots to a green screen where it tries to optimize apps, stays there for about 20 seconds, and reboots over and over again in the same cycle. I have tried all other stock marshmallow roms that i can find, Odin won't flash older ones, (assuming its not letting me downgrade). Also another weird thing, every time I flash, the blue update screen goes to 32%, stops, erases, and reboots. Phone is on 6.0.1 version MMB29K.G920VVRU4CPH1 as seen in recovery. Any help would be gladly appreciated. Thank you!
I am having a similar problem with loading new rom. The farthest it gets is 32%. Sometimes it doesn't get even that far.
I ended up just buying a trashed s6 and swapping the motherboards. Only way I could fix it