I'm fairly new to rooting and flashing kernels so sorry if I'm ignorant about all this. I have the latest version of TWRP (3.0.2-0). I would install the latest BluSpark zip (r128), wipe the data and cache and then format them into F2S2 and the phone would reboot fine. However, if I try and reboot the phone or turn it off and turn it back on again I just get stuck at the bootloading animation. Is there any advice or anything I do to prevent this? Did I install something wrong or using the wrong version of something? Thanks in advance for any and all help!
JudoFreak said:
I'm fairly new to rooting and flashing kernels so sorry if I'm ignorant about all this. I have the latest version of TWRP (3.0.2-0). I would install the latest BluSpark zip (r128), wipe the data and cache and then format them into F2S2 and the phone would reboot fine. However, if I try and reboot the phone or turn it off and turn it back on again I just get stuck at the bootloading animation. Is there any advice or anything I do to prevent this? Did I install something wrong or using the wrong version of something? Thanks in advance for any and all help!
Click to expand...
Click to collapse
Your title seems like bluspark have some kind of problem, but that's not the case. You should change that; the kernel works flawless and the problem is clearly you that doesn't know what you're doing. Read and learn from guides, videos and everything else before going flashing around.
And, of course, search. There are threads out there pointing out how to unbrick your phone and solve this kind of mistake.
(and you may have flashed the kernel for CM13, not the OOS kernel...)
Oedipus Rex said:
Your title seems like bluspark have some kind of problem, but that's not the case. You should change that; the kernel works flawless and the problem is clearly you that doesn't know what you're doing. Read and learn from guides, videos and everything else before going flashing around.
And, of course, search. There are threads out there pointing out how to unbrick your phone and solve this kind of mistake.
(and you may have flashed the kernel for CM13, not the OOS kernel...)
Click to expand...
Click to collapse
My apologizes if it seemed like I was implying or insinuating that something was wrong with the kernel, I was only stating it so that it would provide the necessary information for those at were interested in troubleshooting and saving them the hassle of asking. This is my first Android device, and first time rooting and I don't think it would be inappropriate to ask for a slight bit of patience. Again, I did not mean to imply something was wrong with the kernel, I am fairly certain it is something of my doing that I can (hopefully) repair.
Is there any guide that you would recommend specifically for the BluSpark kernel? I know for certain I donwloaded and installed the OOS version so I know that's not an issue.
I think you have to use an older version of twrp to flash this kernel. The recommended version of twrp is 2.8 I believe maybe this is your problem but I'm not sure since I am using cm13 based rom with this kernel.
Go dig through the Blu_Spark thread, I'm pretty positive he said he will never support using F2FS as no one's shown that it's either better or worse than EXT4 which has been trusted for years.
JudoFreak said:
I'm fairly new to rooting and flashing kernels so sorry if I'm ignorant about all this. I have the latest version of TWRP (3.0.2-0). I would install the latest BluSpark zip (r128), wipe the data and cache and then format them into F2S2 and the phone would reboot fine. However, if I try and reboot the phone or turn it off and turn it back on again I just get stuck at the bootloading animation. Is there any advice or anything I do to prevent this? Did I install something wrong or using the wrong version of something? Thanks in advance for any and all help!
Click to expand...
Click to collapse
You did a couple of things wrong. When you flash the kernel there is no need to wipe data. You basically reset your phone. Also, formating to f2fs after you flash the kernel will also wipe data and therefore reset the phone.
Your best bet is to start over from factory rom and kernel to get the phone to boot right and then do some research and reading before you start changing kernel and partition formats.
Search the question and answer forums for restoring to factory settings.
Good luck.
I have the same issue. after flashing latest build of blu_spark, phone stuck on boot screen .. i tried latest TWRP and Blu_Spark TWRP in his download section, neither worked for me. I did not format f2fs as I would like to keep it the same EXT4 .. any ideas how to solve this issue?
Related
Hi All,
Just got my S2 last week. Planning to move to CM7 this weekend. I have rooted the device and am on the Codeworkx kernel. I had a few questions:
1. Is there a problem while flashing via Odin if Debugging is not enabled (I think it is more of a OS feature which we haven't entered when in download mode, so shouldn't matter according to me.) ? I tried to disable debugging, and then went to download mode and Odin did detect the phone, but I did not try to flash anything so if anyone has tried that, your input is more than welcome.
2. The reason for above question is: What if I completely brick my phone (with debugging disabled) and no ROM .zip in the sd storage, how do I get the phone up and running ? I understand that I can flash kernels via Odin, but is it true for ROMs as well ?
3. What's the issue with ROM manager ? Is it recommended to stay away from it for S2 ? I have tried to do a Nandroid backup and it always takes me to the Android robot with a exclamation mark screen. Then I have to reboot and the backup magically restarts and completes successfully. Most people have suggested to use CWM recovery directly, so not sure if I should get rid of the ROM manager altogether.
That should be all for now. I have a jig ready by the way, so am not that worried about the process and plan to do a fair bit of reading before proceeding, however, the answers to above queries would be really great !
Thanks in advance,
Ish
I can answer some of your doubts.
I don't know if you can flash via odin in case you don't have the usb debuggin enabled so I'm not going to say anything about it.
Anyway if something happens to your phone and you dont have any ROM on your sd card but you have CWM recovery installed (which is almost everytime the case) then in CWM there is a mount usb stoage option. With it you can easily transfer .zip ROM files to flash, or even a nandroid backup you saved in your PC.
ABout ROM manager, this is what I suggest you. The first time you flash CM7 don't use ROM Manager (I even tried using it with the codeworkx kernel with no luck). Now, once you are in CM7 it works perfectly and it's really helpful to flash nightlies withouth wiping data (I flash half the nightlies as they are realeased). So the first time you flash CM7 wipe everything (do a nandroid backup first), even wipe /system, /data, cache partition, dalvik cache, so you don't have any problems. THen install zip from sd card and when it finish install the zip file again (just two installs in a row no wiping in beween, trust me, the first time I tried I didn't do that and couldn't boot the phone).
Hope it helps.
EDIT: You can flash stock ROM via odin, there is a thread by infratech were this is explained and you have a list of downloable stock ROMS you can flash with Odin, these are region and carrier specific and you probably will get the one for your carrier. I found the stock ROM for my carrier and I'm from chile, you shouldn't have any problems with that. Well, good luck, CM7 is by far the best ROM I've flashed.
Oh another thing, go for the latest nightly since the battery life is incredibly improved over the RC (or was it stable?) version.
Thanks !
tomascunill said:
Anyway if something happens to your phone and you dont have any ROM on your sd card but you have CWM recovery installed (which is almost everytime the case) then in CWM there is a mount usb stoage option. With it you can easily transfer .zip ROM files to flash, or even a nandroid backup you saved in your PC.
Click to expand...
Click to collapse
Awesome ! This is exactly what I was looking for. I haven't dived into all the options of the CWM, so didn't know that this feature existed.
Also, many thanks for explaining most of the things in a single concise post, it was very helpful. I'll have to check the ROM flash with Odin, so I will search for that thread and have a go through it later today.
Once I get a hang of CM7, I'll go in for the nightlies as well. And yes, I did read about the CM7 guys revert the status to an RC because of the bugs reported, so will give it a try once I definitely know what I'm getting into .
Thanks again,
Ish.
cheemais said:
Awesome ! This is exactly what I was looking for. I haven't dived into all the options of the CWM, so didn't know that this feature existed.
Also, many thanks for explaining most of the things in a single concise post, it was very helpful. I'll have to check the ROM flash with Odin, so I will search for that thread and have a go through it later today.
Once I get a hang of CM7, I'll go in for the nightlies as well. And yes, I did read about the CM7 guys revert the status to an RC because of the bugs reported, so will give it a try once I definitely know what I'm getting into .
Thanks again,
Ish.
Click to expand...
Click to collapse
Well good luck! Tell me if you get any problem.
Hey all, I know this has been discussed to death but I had never had this issue til yesterday... I started having the sideload errors when trying to flash any custom kernel immediately after the ROM IN TWRP 2.0. I've now tried this on every version of TWRP and still can't get it to take. I am s-off and only do full wipes prior to any flashing, cache/dalvik between flashing of ROM and the kernel. Any input would be greatly appreciated... I'm at work right now otherwise I'd just unearth one of the old threads likely asking this same question. Anyone who can help me troubleshooting this will get well deserved thanks of course.
Just to add to this... I just went through and flashed a kernel by itself in TWRP 1.0.3 after clearing cache/dalvik. I just don't understand why I would be able to do this by itself, but not in the same recovery session as I've always done...
its a scripting error in the update-binary not your phone
Well this now seems to randomly happen with any of the .zips on my phone and using any version of TWRP. I can't imagine what caused this, It's just so frustrating... I basically have to reboot to recovery several times to get all the zips I need to flash.
joehunni said:
Hey all, I know this has been discussed to death but I had never had this issue til yesterday... I started having the sideload errors when trying to flash any custom kernel immediately after the ROM IN TWRP 2.0. I've now tried this on every version of TWRP and still can't get it to take. I am s-off and only do full wipes prior to any flashing, cache/dalvik between flashing of ROM and the kernel. Any input would be greatly appreciated... I'm at work right now otherwise I'd just unearth one of the old threads likely asking this same question. Anyone who can help me troubleshooting this will get well deserved thanks of course.
Click to expand...
Click to collapse
i would recommend d/l twrp 2.0.1 just released. make sure you wipe cache/devlic/system/factory default... I usually would do this in this order... a factory / sys/ dev/ cache wipe and then flash your new stuff and work with the new rom you wish to flash ... I did it and it worked well on 2.0.1 .... not the 2.0
I was running the Spike Pure ICS on my SGS2, before which I had the ICS version of MIUI. I tried flashing Lite'ning Rom 3.6 through Odin, but was unsuccessful. Also, that's time I noticed the 7.2 version of CM and decided to flash that and that's when the problem occurred.
Although I could flash CM 7.2 properly and could also install the GApps through CWM, on rebboting it through the CWM, my phone got stuck and it wouldn't go into Recovery any more.
Luckily, it would boot into Download Mode and I could flash the stock rom through Odin and get my phone back to stock, thereby losing the Root and CWM.
I wanna know as to what could cause such an issue to arise. so that I can prevent it later!
Your help and time are appreciated!!
Why start a 2nd thread ?
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
And you couldn't make another post to your initial post along the lines of 'Why did this occur in the first place ?' You could even easily change the title of your initial thread to reflect your desire to know the answer to this question.
One of the main rules of XDA is don't spam.
I'm extremely sorry if I've spammed as it wasn't my intention at all!
This thread was and still is a genuine question which I want to know!!
Also, could you please tell me about the occurrence of such a problem on my phone??
gadgyfreak said:
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
Click to expand...
Click to collapse
I think answer was there but might be not clear......
When you flash gb over ICS you have to wipe, when you mix stuff after that, meaning trying different kernels to fix the issue it might get worse.
Because recovery is somewhat linked to kernel in s2, you won't get recovery in a messed up system.
So when you flash a complete firmware using Odin and then do data cache wipe, it get fixed.
Hope this helps.
But then how is it possible that my phone didn't get all messed up when I flashed CM 9(Nightly) over my pre-existing CM 7.1, while it happened when I tried it vice versa?
already told you, when you go from ICS newer kernel to GB older kernel, wipe is necessary. Going from GB to ICS will work but wipe is better there too.
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Flash a GB rom.
gadgyfreak said:
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Click to expand...
Click to collapse
save data
Wipe dial *2767*3855#
Flash GB Rom, preferably stock using Odin.
Should boot now, if not go into recovery and wipe data cache.
It will boot now.
Hi,
I rooted my GSII, using step 2c from the guide found here: http://forum.xda-developers.com/showthread.php?t=1311081 with the UCKK6 Stock + Root package found here: http://forum.xda-developers.com/showthread.php?t=1286432
Afterwards, I used CWM to flash PhoneBricker v2.7 (http://forum.xda-developers.com/showthread.php?t=1560759). After only a few minutes of use, my phone began locking up and rebooting randomly. It didn't matter what I was doing at the time. After reading through some threads, I tried wiping cache, factory reset, and flashing only the ROM again, to no avail. I also noticed the phone would get pretty hot when it would lock up.
I thought the ROM was the issue, so I flashed Mystic's Glory ROM (v.4.9.2beta) after wiping cache, factory reset. Same behavior.
I've resorted to restoring the first nandroid backup I did, which is just stock + root.
Would anyone have any suggestions? Thank you.
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
wgoldfarb said:
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
Click to expand...
Click to collapse
wgoldfarb,
I do, in fact, have the I777 variant.
Can you please tell me what you mean by FCs?
The random lockups/reboots began even before I started installing other apps. I do not have Titanium Backup. I installed the apps from the Play store.
Yes, I made sure to do a factory reset, wipe cache, and wipe dalvik cache.
Could it be an issue with the way the ROM is handling CPU usage? Perhaps there is a preset that is on by default that may be causing lockups.
I'm also wondering rooting using the UCKK6 package was the correct way, as opposed to rooting back to the UCKH7.
I appreciate your help.
What kernel are you running? That sounds like the issue to me
jthatch12 said:
What kernel are you running? That sounds like the issue to me
Click to expand...
Click to collapse
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
wwjd3 said:
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
Click to expand...
Click to collapse
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
creepyncrawly said:
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
Click to expand...
Click to collapse
I'm sorry. I failed to mention that after rooting, I used MobileOdin to flash a custom kernel (Siyah 2.6) with CWM (step 3a in the first link I provided). From there, before flashing PhoneBricker, I did a factory reset, cache wipe, dalvik cache wipe, all from within CWM. I did NOT perform factory reset from phone settings.
I have not performed a md5 sum check. I guess that would be the next step.
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
wgoldfarb said:
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
Click to expand...
Click to collapse
Ah, I understand. What I meant by lockup is that the system freezes. The capacitive buttons no longer respond. Neither do the volume/power buttons. The screen simply freezes, and I have to force a restart by holding down the power button for a number of seconds. I hope that makes sense.
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
wwjd3 said:
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
Click to expand...
Click to collapse
1. Short answer - yes. Long answer - no (I remember a few other options floating around). For all intents and purposes, just pick one of those; either will accomplish what you need.
2. From what I remember about looking at the script, it wipes dalvik cache and deletes the contents of /etc/int.d (to prevent incompatible scripts across kernels - not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Simba501 said:
not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Click to expand...
Click to collapse
If I read correctly, Phalanx was offering up a secondary option to try out before taking the complete stock route which would make it relevant. However, if he does the return to stock... Then you're right, not gonna do much for him. (though it wouldn't hurt)
Clay
Team Pirate
Sent from my PINK SGH-I777
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
creepyncrawly said:
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
Click to expand...
Click to collapse
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
wwjd3 said:
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
Click to expand...
Click to collapse
How did you root your phone b4? which method?
Use that.
votinh said:
How did you root your phone b4? which method?
Use that.
Click to expand...
Click to collapse
I used method 2c, Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader previously. I was thinking of using a different method, since I ran into problems using Entropy512's method. Try something different.
-------------------------------------------------
EDIT:
I'm sorry, I was wrong. Since I had UCKK6 build previously I used Odin to flash the Kernel + cache + rooted UCKK6 system package found here: http://forum.xda-developers.com/showthread.php?t=1286432
So, using method 2c would, in fact, be a different method altogether. I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
wwjd3 said:
I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
Click to expand...
Click to collapse
It's as good a theory as any other... I guess.
Hi sirs,
The title says it all, I want to change back to stock rom or change to other custom roms but I am not sure what to do. I have cm12.1 nightly build 5.1.1 (i guess that's the name) currently installed in my phone. I followed a tutorial on how to do THINGS in my phone but I am unsure whether it will work or not. I am SO VERY VERY VERY new to these things and I don't know how to proceed. And also, i get confused of the terms like KERNEL or ROM and i kind of mixed them up. So I am here to ask for your help and clarification on my problem.
According to a tutorial that I've read, a custom recovery is needed. So, following a tutorial, I replaced the Cyanogenmod recovery with TWRP recovery. My questions are:
1. Is it safe to flash a ROM (like Omega Series Rom, which I kind of bumped in while doing research) over the current CM12.1 system?
2.Is there any patterns or magical incantations in order to flash a new rom into my device successfully? If so, can someone show me a step-by-step instructions?
3.Will it brick my phone if I missed a step?
I know this is too much to ask for, but please help me Sirs/Maams. I'm desperate. THANKS SO SO SO MUCH in advance.
P.S. Sorry if my english is so horrible. English is not my first language.
Sincerly,
Me
To install a new ROM, boot into recovery, and wipe /data and /cache and if you want also /system. After that install the ROM and Gapps zip files. Always double-check you're using & choosing the correct files. I recommend to always use the smallest possible Gapps package to make sure it fits into the /system partition.
Make sure you're using the right recovery. For example Cm12.1 needed a KitKat-compatible recovery for a successful install.
Notice that all apps and app data will be deleted at a new flash. In some cases, the recovery is included in the ROM, then it will overwrite the one you had before.
I personally think flashing a new ROM isn't that dangerous. There are more critical things, for example repartition. But there are some rare cases at almost every ROM where someone's phone dies, for whatever reason. So there's always a little risk. But even if you should succeed soft-bricking your phone, there already are some guides how to solve it.
And one more tip: in general, always read as much as possible about a ROM before flashing it. Avoid less documented ROM threads. You decide what you risk and do everything on your own responsibility.
I know this things are logical, but it seems as if there are still people flashing everything, reading nothing, spamming everything with their problems they get then
Hope I helped you a little bit.
BenjyTec said:
To install a new ROM, boot into recovery, and wipe /data and /cache and if you want also /system. After that install the ROM and Gapps zip files. Always double-check you're using & choosing the correct files. I recommend to always use the smallest possible Gapps package to make sure it fits into the /system partition.
Make sure you're using the right recovery. For example Cm12.1 needed a KitKat-compatible recovery for a successful install.
Notice that all apps and app data will be deleted at a new flash. In some cases, the recovery is included in the ROM, then it will overwrite the one you had before.
I personally think flashing a new ROM isn't that dangerous. There are more critical things, for example repartition. But there are some rare cases at almost every ROM where someone's phone dies, for whatever reason. So there's always a little risk. But even if you should succeed soft-bricking your phone, there already are some guides how to solve it.
And one more tip: in general, always read as much as possible about a ROM before flashing it. Avoid less documented ROM threads. You decide what you risk and do everything on your own responsibility.
I know this things are logical, but it seems as if there are still people flashing everything, reading nothing, spamming everything with their problems they get then
Hope I helped you a little bit.
Click to expand...
Click to collapse
Thanks for the reply kind sir.
So it's safe to flash a new ROM over the current CM12.1 system? And if so, will my current recovery (which is TWRP recovery) suffice for flashing a new ROM? or do I have to replace my recovery? If ROMs have compatibility issues with recovery systems, can you please give or show me a list of ROMs that can be flashed using TWRP recovery (I'm so sorry, I have don't completely understand these kinds of things).
Thanks for your help sir. I really appreciate it. And sorry for the questions.
ZaorotheFirst said:
Thanks for the reply kind sir.
So it's safe to flash a new ROM over the current CM12.1 system? And if so, will my current recovery (which is TWRP recovery) suffice for flashing a new ROM? or do I have to replace my recovery? If ROMs have compatibility issues with recovery systems, can you please give or show me a list of ROMs that can be flashed using TWRP recovery (I'm so sorry, I have don't completely understand these kinds of things).
Thanks for your help sir. I really appreciate it. And sorry for the questions.
Click to expand...
Click to collapse
It's safe to flash whichever rom you want over cm12.1. The only thing to keep in mind is whether it is a .zip file or .tar file(as for stock rom), which will tell you whether to use recovery(your TWRP is fine for this), or odin(for stock rom in .tar format)
But as BenjiTec said, READ, READ, READ before you go ahead and flash a rom. Always read the OP(first post) and maybe first 2 or 3 pages of the rom thread, plus the all the pages from when the rom version you want to flash was released(maybe 10-20 pages). You probably don't need to read ALL pages if it is an old version. Understand what you are doing, rather than follow steps blindly, and you will always know what to do in case of something going wrong
Thanks a lot sirs, both of you, BenjyTec and noppy22, for the clarification.
One last question (or sets of questions. sorry )
So I have decided that I will flash a stock ROM to my S2 from SamMobiles using Odin. Do I have to wipe the the /data, /system, etc. before flashing the stock ROM via Odin? Or i can just directly flash the ROM over the CM12.1 system and TWRP recovery? And I have searched a lot of the possible outcomes and failures (like Odin ROM installment failure). What are the chances that the installation will fail? And what do I do if it DID fail (let's hope not)?
I know that these kinds of questions have been already answered in many threads but I just want to have my answers DIRECTLY from experts. Not from old threads and guide thingies.
Again, THANK YOU SO MUCH for the clarifications and answers. GOD BLESS
ZaorotheFirst said:
Thanks a lot sirs, both of you, BenjyTec and noppy22, for the clarification.
One last question (or sets of questions. sorry )
So I have decided that I will flash a stock ROM to my S2 from SamMobiles using Odin. Do I have to wipe the the /data, /system, etc. before flashing the stock ROM via Odin? Or i can just directly flash the ROM over the CM12.1 system and TWRP recovery? And I have searched a lot of the possible outcomes and failures (like Odin ROM installment failure). What are the chances that the installation will fail? And what do I do if it DID fail (let's hope not)?
I know that these kinds of questions have been already answered in many threads but I just want to have my answers DIRECTLY from experts. Not from old threads and guide thingies.
Again, THANK YOU SO MUCH for the clarifications and answers. GOD BLESS
Click to expand...
Click to collapse
It doesn't matter so much whether you wipe before or after. The easiest way is:
1. Run odin on your pc
2. Connect your phone, after booting in download mode(turn off, then hold vol down, home, power buttons until samsung screen) Use a trusted data cable, not all cables work
3. Flash stock rom through odin until PASSED(untick reboot device/auto reboot before flash)
4. Disconnect phone, take battery out, then put it back in. Reboot to recovery(vol up, home, power buttons)
5. In stock(3e) recovery, do a factory reset
6. Reboot and leave it for 5-10 minutes until you get a brand new stock rom
Stock ROM installing succeeded! THANKS SO MUCH SIRS! THANKS for all the clarifications and answers to my questions! KUDOS to both of you!!!