I've made a few mistakes when trying to install the latest cyanogen Nightly to my SGS2.
I initially tried the ROM Manager method of flashing to Cyanogen but only managed to get myself stuck in only being able to boot into ClockWork Mod Recovery mode so I ended up having to use Odin to re-flash with Stock Mod (had to guess which stock rom I needed as I hadn't looked it up before heh) and when that completed my phone booted up ok and all my apps were there but the screen was strangely washed out in appearance. Not sure if the o2 UK rom that came with the phone had some tweaks to make the colours richer or something - I checked the display settings and it was at the setting I'd chosen previously.
Anyway, I re-tried using the Recovery mode instructions and now my phone is stuck at the boot screen and has been for 20 minutes. I'm aware the first boot after cyanogen is installed is meant to be longer (while it dexopts or something like that) but 20 minutes seems a trifle tardy so I suspect it's gone tits up again.
Oh well.
Onto my question:
I want to flash with the correct o2 UK version of the SGS2 rom whilst completely wiping everything from my phone including system internal sd and external sd.
Is this possible and how?
try this procedure provided by ithehappy.
Wipe Cache+ Factory Reset should work.
Anyway, try this in keypad,
*2767*3855#
Thanks for the help
Hey guys,
Not exactly what to make of this which is why I'm posting. Here's the run down. Started off running Scamble_v01.3[CM6.1.3] for quite some time with everything just fine. About 2 weeks back, decided it was finally time to step it up to a Gingerbread ROM, and went with Wolfbreak's. For the first week, everything ran perfectly fine. This past week, I started to have issues with it rebooting every time I would run an app. Finally, this morning, it rebooted, and then just as it would get to the lock screen, it would say formatting SD card and then reboot. It would continue to do this repeatedly. I tried reinstalling in xRecovery (mind you I did Factory Reset (Full wipe), Wipe Cache Partition, & Wipe Dalvik Cache as well).
With high hopes, I restarted it. Unfortunately, this didn't change anything. I took my microSD card out and put Wolfbreak's updated ROM on it which just came out in hopes that maybe the file was corrupted somehow, just to find that when I tried to install it through xRecovery it, gave me an error that it couldn't because the SD card was busy. Stated in his ROM even, it says that you need to backup the ROM just for this very reason, however the only backup I had was of Scamble_v01.3[CM6.1.3] since I found it pointless to try and back up a messed up ROM.
Not knowing what else to try, and knowing that that was the last stable state my x10 was in, I restored that. Once again, it did nothing as far as the boot loop. I've gotten to the point where I have used FlashTool to flash the Generic Gingerbread ROM which just as all the others, gets to the first screen (which asks me to choose a language) and then reboots.
I'm completely stuck here and can't think of what I may be missing here. Any help would be greatly appreciated.
downwardzspiral said:
Hey guys,
Not exactly what to make of this which is why I'm posting. Here's the run down. Started off running Scamble_v01.3[CM6.1.3] for quite some time with everything just fine. About 2 weeks back, decided it was finally time to step it up to a Gingerbread ROM, and went with Wolfbreak's. For the first week, everything ran perfectly fine. This past week, I started to have issues with it rebooting every time I would run an app. Finally, this morning, it rebooted, and then just as it would get to the lock screen, it would say formatting SD card and then reboot. It would continue to do this repeatedly. I tried reinstalling in xRecovery (mind you I did Factory Reset (Full wipe), Wipe Cache Partition, & Wipe Dalvik Cache as well).
With high hopes, I restarted it. Unfortunately, this didn't change anything. I took my microSD card out and put Wolfbreak's updated ROM on it which just came out in hopes that maybe the file was corrupted somehow, just to find that when I tried to install it through xRecovery it, gave me an error that it couldn't because the SD card was busy. Stated in his ROM even, it says that you need to backup the ROM just for this very reason, however the only backup I had was of Scamble_v01.3[CM6.1.3] since I found it pointless to try and back up a messed up ROM.
Not knowing what else to try, and knowing that that was the last stable state my x10 was in, I restored that. Once again, it did nothing as far as the boot loop. I've gotten to the point where I have used FlashTool to flash the Generic Gingerbread ROM which just as all the others, gets to the first screen (which asks me to choose a language) and then reboots.
I'm completely stuck here and can't think of what I may be missing here. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Maybe give flashtool a go, just flash one of the stock firmwares.
Already tried that. As stated before, it gets to the first screen which prompts me to chose a language, and then immediately reboots
So it started when I wanted to do a factory reset. I was running 4.1.2 stock and the phone has never been rooted or modified. For some reason, no matter what i tried i could not get the phone into recovery mode. I tried every button combination and watched every youtube video, no luck. Download mode was working though.
So i gave up and just did the reset from within the OS settings. After this was done i was curious to see if the recovery mode would work, still no luck. I think it's important to have that working in case you have trouble with your phone so i felt the need to resolve this. I also thought it would be cool to root my phone so i planned to flash a new kernel which would also rewrite the recovery mode, root the phone, and leave the stock rom.
By this time i had added some of the apps back to my phone that were wiped during the factory reset, most of which i put on my sandisk sd card. I first tried flashing a no frills kernel called Jeboo using heimdall on my mac. It worked fine but still no luck getting to recovery mode. The phone looked like it was trying. After the appropriate button combo the screen would would keep flashing a faint grey but never load to recovery.
Also, after i flashed this kernel i noticed that all the apps i downloaded to my sd card were gone. Only a transparent image with a little "sd" icon remained and when i clicked on one it would say the app was not installed. Not sure why a kernel would affect this since i didn't change the rom.
Anyhow, i was still focused on getting recovery mode working so that i could finally root my phone. I tried another kernel called speedmod.
http://forum.xda-developers.com/showthread.php?t=2140192
Good news it worked and i was finally able to get to recovery mode which was now run by CWM. Finished rooting,
As far as the apps go i was able to re-download all the apps that disappeared from my sd card. The weird thing is, there were a couple of apps i notice so far that were not on my sd card that disappeared completely. Season zen hd and betterbatterystats. The problem is when i re-download these ones it says "cannot install to usb or sd card" I tried wiping dalvik and cache partition with no change.
The question is:
Why would apps get wiped from a kernel update? As i will likely update kernels in the future is this going to be a constant issue?
Why can't a reinstall a few of the apps?
So I updated to the newest software MI5. Went from that and did the root which was sucessfully. I had put on OUDHS Touch CWM-based Recovery thru ODIN which was sucessful as well. After doing all of that, I downloaded Josh Beach's Jellybomb test rom. The steps I did was booted into recovery which is the one above, factory data reset, wiped cache, and wiped dalvik, then flashed the zip. The zip looked to flash ok but when i went to reboot, it just keeps getting stuck at the samsung galaxy note 3 screen, then it will reboot then go to the same screen. Did I do something incorrect? This happened to me on this ROM and the stock MI5 ROM rooted.
Might want to read through this thread...
http://forum.xda-developers.com/showthread.php?t=2473036
Process system isn't responding
Sent from my Note 3 on Android
runner77 said:
Might want to read through this thread...
http://forum.xda-developers.com/showthread.php?t=2473036
Process system isn't responding
Sent from my Note 3 on Android
Click to expand...
Click to collapse
so it sounds like i cant flash any custom roms right now? Just odin back to stock and root it and leave it at that?
this probably wont help for this particular problem, or maybe it will.. but for anyone else getting a bootloop..
i just now had a bootloop experience that i got out of.. and here's how it started - i have not rooted my note 3 (i have rooted my galaxy gear though, but i don't think that would affect the note 3).. anyway, i use the nova launcher as my main launcher.. and just before i got stuck in a loop, i had been playing with a new launcher called Themer... i just started it without setting it as default.. then i went back to my main launcher and i noticed that almost all ram was used up and i thought i might as well do a restart as it has been a while... and then it just would not start.. i got to the lock screen image, and then it would restart again and again, with no sound for the animated logo.... it eventually booted up ok, but i have no idea how i got it to work... however, i held down the power button for a while longer and it would "force" a new restart and basically abort the one already in progress, and if i did that, the boot up sound would come back... i continued doing that a couple of items and then it finally worked.
use twrp or phones as of right now dont like cwm recovery...found this out the hard way
odin back to stock rom non root wipe phone using default recovery odin back to stock again root your phone use twrp to flash whatever rom u want
lunchboxVA said:
use twrp or phones as of right now dont like cwm recovery...found this out the hard way
odin back to stock rom non root wipe phone using default recovery odin back to stock again root your phone use twrp to flash whatever rom u want
Click to expand...
Click to collapse
And when flashing make sure to wipe dalvik/caché several times for good measure.
Sent from my SM-N900P using Tapatalk
checking in to add that i found a new solution to my own problem here.... it "magically" started the last time just by me keeping on rebooting.. but that's not really a good solution and i don't think it lasts
and for me it didn't... as today i did a new restart, and it got the same stuck in a loop again, however, i followed the first mentioned workaround in this link here and it worked perfectly.. it was really that simple in my case it seems, i have done several restarts now and the bootloop is gone!...
oops, seems i cant post any links for not having enough posts yet...
i'll just add the steps mentioned instead
1 . Remove the battery and the SD card.
2. Put the battery back in and turn on the device.
3. Try Menu > Settings > Wi-Fi > Menu > Advanced and uncheck Always allow scanning.
4. Now you should be able to turn the device off and reinsert the SD card.
5. Boot it up and your problem might be gone
i have no idea how it works though as i personally don't understand the connection between then external sd card and the setting you turn off in the wifi advanced options..
cheers!
I've been using CM13 on my phone for a long while, but it was heavily bugged (my camera kept crashing, I've kept losing cell reception, couldn't receive calls etc), so I finally decided to try another ROM. I've heard good things about ResurrectionRemix ROMs, so I've decided to give it a try. I did factory reset and wiped cache (using CWM 6. something) and flashed RR 7.1 along with the appropriate gapps and rebooted the phone. It's worth noting that I've put the ROM and Gapps zip files on USB stick and connected it to the phone via micro USB cable. It all went smoothly, and the phone booted right up. However, once I got into the startup setting and choosing the language suddenly it just rebooted all on its own. Same thing happened 2 more times, and I got stuck in a bootloop after that.
So I figured I should flash another ROM, and I wanted to give RR 6.0 a try. I've downloaded it and saved it to my USB stick, however, when I tried to flash any zip files from my stick, it just kept randomly unmounting, disrupting the process, giving me "USBdisc0 idle-unmounted" message. Since I don't have an SD card, only thing I could do was push files to my phone, and I've managed to do so via Quick ADB Pusher. This time, flashing went without a hitch, however, I've tried cleaning my phone completely (formatting all the data and system files), and I think I messed it up a bit when I did that, since I didn't flash SuperSU along with ROP and gapps. Again, I got stuck in a bootloop without any signs of the ROM working.
So I decided to flash CM13 again. At least I was sure it was working on my phone, and I figured it was better to have a crappy phone than no phone at all. So I pushed the CM13 file onto the phone and flashed it, but still got stuck in bootloop. I finally remembered about SuperSU and tried to flash it too, but now my phone kept restarting in the middle of the flashing process. I've tried doing the factory reset and cache wipe, but I can't flash any files now without it restarting only few seconds into the process.
I have no idea what's going on, but seems that my phone is doing worse and worse as time moves on. At least I can still boot into recovery and download mode, so (hopefully) something can still be done. As it's probably painfully obvious, I'm not too knowledgeable about this stuff, I'm just following instructions people smarter than me put out, but seems I've messed it up good this time. Am I beyond help?
Try to download newest firmware from sanmobile.com and flash it with odin. Then root it make backup flash recovery and flash rom that you choose with recovery. There are lots of tutorials here on xda and on youtube. Just remember that flashing stock firmware with odin will delete all of your data so try to back them up somehow (i think that if you boot phone in recovery (twrp) the pc will see it like a pendrive)
Sirius8 said:
...
As it's probably painfully obvious, I'm not too knowledgeable about this stuff, I'm just following instructions people smarter than me put out, but seems I've messed it up good this time. Am I beyond help?
Click to expand...
Click to collapse
TBH you made the mistake many beginners make... Going ahead too fast with insufficient knowledge. But never too late to learn that lesson
Since you are getting more and more confused and your phone seems acting strange I recommend starting from scratch an be analytic about it. This will take just a few minutes more but you can be sure where a problem comes from.
First of all: Take 30 minutes to get acquainted with the basics and read through the first thread in my signature (just do it...)
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
If all is fine go back to ODIN and install latest TWRP (cwm is seriously outdated, can cause lots of errors). Then boot into TWRP and flash whatever custom rom you like. If you install e.g. LOS 14.1 or RR 7.1.1 make sure you install gapps direcly after you flash the rom (do not reboot in between).
Any questions pop up: Shoot. I'm happy to help.
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
McXred said:
Try to download newest firmware from sanmobile.com and flash it with odin. Then root it make backup flash recovery and flash rom that you choose with recovery. There are lots of tutorials here on xda and on youtube. Just remember that flashing stock firmware with odin will delete all of your data so try to back them up somehow (i think that if you boot phone in recovery (twrp) the pc will see it like a pendrive)
Click to expand...
Click to collapse
Since he already wiped system and data there is no point in a backup of those partitions. Only thing worth saving would be the efs partition.
And you don't need to root stock rom to go further...
If you are unrooted you have to REMOVE the "auto-reboot" checkmark in odin options and then - after the flash of twrp - reboot to recovery (TWRP) manually via holding Power+Home+VolUp for a few seconds.
If you do not uncheck that "auto-reboot" box, an thus allow the unrooted system (stock samsung system) to boot, it will overwrite the new twrp recovery you flashed 2 seconds before...
This is the point where I believe many confusion comes from. If you root first, any recovery you flash will not be overwritten. That is - I think - why many tutorials/tips say you must root stock first before installing a custom rom, which is simply not true.
But you are right that it would help to flash TWRP fist as outlined above, boot into it and make a backup to a microSD card... but of the efs partition (!) as the very first step. Then keep that backup safe and go from there with stock rom, testing for any problems.
So to reiterate the steps I would go:
1) Flash TWRP via odin and boot directly into it
2) Backup efs partition to a microSD card
3) Flash stock rom via ODIN and test
4) Go from there / report baback
Thank you so much for the replies guys, I'm glad there's still hope for my trusty SIII.
Are there any alternatives for sammobile.com though, since it requires premium account for the firmware I need. I've found another mirror on the site mrcrab.net/stockrom/2444.html (mirror 1 leads to sammobile.com, while mirror 2 leads directly to rapidgator), but can I trust it not to mess my phone up further?
Try updato.com for the firmware.
Hawaiihemd said:
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
Click to expand...
Click to collapse
I've manage to flash stock ROM via Odin, however, as soon as the phone booted up it gave me the "low battery" message, even though I think there was plenty of battery left. But I figured the flashing process must have drained it. As I've tried to tap the OK button, the screen just froze and remained frozen for over 5 minutes. I took battery out and reinserted it, since nothing else worked, and got stuck in bootloop again, just as before flashing stock firmware.
Sirius8 said:
I've manage to flash stock ROM via Odin, however, as soon as the phone booted up it gave me the "low battery" message, even though I think there was plenty of battery left. But I figured the flashing process must have drained it. As I've tried to tap the OK button, the screen just froze and remained frozen for over 5 minutes. I took battery out and reinserted it, since nothing else worked, and got stuck in bootloop again, just as before flashing stock firmware.
Click to expand...
Click to collapse
Try to charge phone without turning it on, when it says its fully charged try to flash it again.
McXred said:
Try to charge phone without turning it on, when it says its fully charged try to flash it again.
Click to expand...
Click to collapse
Good idea. I would also keep it on the charger while booting.
This could be a symptom of a defective battery. So these steps might help.
Looks like you were right guys. I've recharged the battery and tried to flash the stock firmware again, but for some odd reason (it seems like I can't do the same thing twice with this phone ) Odin was giving me grief and couldn't establish proper connection with my phone, even though it recognized it at the beginning of the process. I've tried changing cables and ports, but with no avail.
After I gave that up, I tried booting the phone up anyway, but keeping it plugged in the charger this time. It booted right up, but I expected it to crash and reboot at any moment. So I sped up through the settings a and login processes, but it still worked like a charm. I've checked the camera and everything worked perfectly. So I kept it on charger for a couple of hours, to check if I would have any random crashes, but nothing happened. After I was sure it was stable, I unplugged the charger, and within the second I did that the phone crashed and got stuck in the bootloop again.
I've plugged the charger back in and it booted up just fine. The battery level was 89%, and I left it on charger the whole night (12+ hours). It had 90% when I woke up, it's back at 89% right now.
So, everything points to a faulty battery, but it seems strange to me this happened just as I was flashing another ROM, even though I never had any problems with it before. And even though it wouldn't let me boot, I could use recovery and download mode for as long as I liked, and once I did boot with the charger plugged in, the battery wasn't drained but it was around 90%.
Hawaiihemd said:
TBH you made the mistake many beginners make... Going ahead too fast with insufficient knowledge. But never too late to learn that lesson
Since you are getting more and more confused and your phone seems acting strange I recommend starting from scratch an be analytic about it. This will take just a few minutes more but you can be sure where a problem comes from.
First of all: Take 30 minutes to get acquainted with the basics and read through the first thread in my signature (just do it...)
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
If all is fine go back to ODIN and install latest TWRP (cwm is seriously outdated, can cause lots of errors). Then boot into TWRP and flash whatever custom rom you like. If you install e.g. LOS 14.1 or RR 7.1.1 make sure you install gapps direcly after you flash the rom (do not reboot in between).
Any questions pop up: Shoot. I'm happy to help.
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
Since he already wiped system and data there is no point in a backup of those partitions. Only thing worth saving would be the efs partition.
And you don't need to root stock rom to go further...
If you are unrooted you have to REMOVE the "auto-reboot" checkmark in odin options and then - after the flash of twrp - reboot to recovery (TWRP) manually via holding Power+Home+VolUp for a few seconds.
If you do not uncheck that "auto-reboot" box, an thus allow the unrooted system (stock samsung system) to boot, it will overwrite the new twrp recovery you flashed 2 seconds before...
This is the point where I believe many confusion comes from. If you root first, any recovery you flash will not be overwritten. That is - I think - why many tutorials/tips say you must root stock first before installing a custom rom, which is simply not true.
But you are right that it would help to flash TWRP fist as outlined above, boot into it and make a backup to a microSD card... but of the efs partition (!) as the very first step. Then keep that backup safe and go from there with stock rom, testing for any problems.
So to reiterate the steps I would go:
1) Flash TWRP via odin and boot directly into it
2) Backup efs partition to a microSD card
3) Flash stock rom via ODIN and test
4) Go from there / report baback
Click to expand...
Click to collapse
Still on charger, still 90 percent.