Related
I am new to modding my vibrant (phone is rooted but that's all) but looking to flash a new ROM. I dl'd rom manager and installed cwr. When I reboot into recovery mode via rommanager or manually doing it,I do not get the prompt to backup. Only options I get are to reboot system, reinstall packages, delete all user data, delete cache data, and format internal sd-card. Anyone know how to fix this? I just updated to 2.2 froyo UVKB5 kernel 2.6.32.9 if that helps.
looks like you have stock recovery.
try reinstall packages, might take a couple times..
or install CWM via replacing update.zip
What he said, yeah.
So just delete the current update.zip file on my phone and replace it with a new one? Any links to download the update.zip file?
Sometimes you have to Reinstall Packages twice for it to go from regular recovery to CWR. If you flash a custom ROM though, most have a custom recovery built in.
If you have to replace the update.zip (which I don't think that you do), this worked for me the first time I rooted.
http://forum.xda-developers.com/showthread.php?t=849028
How to Root.
I am rooted, but I want to back everything up so that way if I do not like the new custom rom I can go back. I tried reinstalling the update.zip file from the link but s till have the same issue. Any other solutions besides going back to stock and going from there? And if I did go back to stock, would I lose everything?
I backed up using Titanium Backup, is that the same as going into recovery mode and backing up?
Re-download recovery using ROM Manager, then repeat. Worked when I had a similar issue.
Tried that several times. I also reuploaded the update file and reinstalled the package several times. Still no luck so I think I might go back to stock using Odin.
Then DL Eugenes froyo don't brick ROM with the 2e recovery update in it, then re-install packages, maybe twice and you'll have the green recovery menu your seeking
Googled Eugene's DL and I do not feel to confident with it. Is it supposed to fix the issue with getting into recovery mode?
So I went back to stock last night using Odin, upgraded to 2.2, and rooted using Superoneclick. Phone's back up and running but faster than the first time I upgraded to 2.2. I still have the issue getting into the proper recover to install the zip file. I've read that deleting Slacker helped some people, assuming it freed up space on the System ROM. My system ROM was full until I started to delete some apps. I now have 20.7 MB free. Could not enough System ROM space be the issue?
I am now also getting a "Fail" attempt when I try and update su saying that it failed to find currently installed su binary. Any advice on fixing this?
TIA!!!
it would probably be easier to just odin back to stock jfd and then flash a deodexed kb5 build thats rooted with SU already in it from here in the forums.
http://forum.xda-developers.com/showthread.php?t=1036193&highlight=deodexed
If you flashed kb5 from kies or odin and don't want to reinstall the rom then you will need to flash a modified 3e recovery because you probably are not quite rooted and won't be able to use CWM until you flash the modified 3e recovery...
http://forum.xda-developers.com/showthread.php?t=833423
You might want to check out the AIO vibrant toolbox (pinned topic in the development thread) it will give you big easy buttons and instructions to flash back to jfd and root and flash a new rom if you need to... It comes with Odin so you can wander into the install folder and fire up Odin to flash the modified 3e recovery if you decide to go that route too.
If I flash a deodexed kb5 will i still be able to flash a custom rom?
I have just bought an SGS2 to replace my HTC Desire.
I rooted it using SuperOneClick. It seemed to work, I can run apps requiring root now.
But the very first thing I want to do is make a nandroid backup of the phone in it's out of box state (or as close to). Is it possible?
On Desire you had to root first, then install a custom recovery such as CWM, and then do a nandroid backup from there. So I guess I will have to install CWM. But googling tells me that on the SGS2 I have to replace the entire kernel to get a new recovery, is that right? And how do I do that?
If the only way to make a nandroid backup is to install a new kernel, I guess the backup will contain the new kernel. Is it possible to go back to the out of box state with the original kernel and original recovery and no root etc.?
pinkfloydhomer said:
I have just bought an SGS2 to replace my HTC Desire.
I rooted it using SuperOneClick. It seemed to work, I can run apps requiring root now.
But the very first thing I want to do is make a nandroid backup of the phone in it's out of box state (or as close to). Is it possible?
On Desire you had to root first, then install a custom recovery such as CWM, and then do a nandroid backup from there. So I guess I will have to install CWM. But googling tells me that on the SGS2 I have to replace the entire kernel to get a new recovery, is that right? And how do I do that?
If the only way to make a nandroid backup is to install a new kernel, I guess the backup will contain the new kernel. Is it possible to go back to the out of box state with the original kernel and original recovery and no root etc.?
Click to expand...
Click to collapse
Just flash any of these and you'll get Super User, Busy Box, CWM, CWM Manager
CF-Root For Stock
http://forum.xda-developers.com/showthread.php?p=14283369#post14283369
Siyah Kernel (Custom)
http://forum.xda-developers.com/showthread.php?t=1263838
Speed Mod
http://forum.xda-developers.com/showthread.php?t=1182498
Flash em via Odin and you'll have CWM take a backup and you are good to flash any custom ROM
Just take note what your stock firmware and kernel is and if you ever need to send off to Samsung you can just flash back to stock using intratechs stock rom thread
Sent from my Galaxy S II using xda premium
Hi everyone. I'm running Galaxy Ace, stock ROM Android 2.3.4
Never flashed a custom ROM before, so be gentle.
Phone already rooted (I have the superuser icon)
From reading threads here at xda, I have download these 3:
1. ClockWorkModAce.zip
2. recovery-clockwork-5.0.2.6-galaxyace-fix.zip
3. GT-I9100_ClockworkMod-Recovery_4.0.0.2.tar
I'm guessing number 3 is not for galaxy ace, right? So that leaves 1 and 2.
QUESTIONS:
1. Are 1 and 2 essentially the same thing? Which do you suggest I use?
2. These two files are on my laptop. Should I simply copy either one of them to my phone's sd card, turn off phone, boot into recovery by pressing home and power button simultaneously, select "Apply update from sd card", then select either ClockWorkModAce.zip or recovery-clockwork-5.0.2.6-galaxyace-fix.zip?
3. After installing either of the two files, and rebooting, would "nandroid" be on my phone then?
4. I believe nandroid backs up EVERYTHING into sd card (recovery image, right?). Can I then copy it to my thumb drive or laptop so I can erase it from the sd card?
5. If I want to get back to my stock ROM, is it done by booting into the custom recovery (like the clockworkmod) and selecting an option there?
6. After going back to stock ROM, how would I go back to stock recovery too?
7. For clarification, when you guys are saying cwm or clockworkmod, do you mean ROM Manager? Because a lot of guys are warning me against it! I just found out clockworkmod is the name of the developer, not the app.
8. From the ROM Manager page at market.android.com ,
Samsung users: You must flash a Clockwork compatible kernel first (see XDA forums)
Is this really necessary?? So much prerequisites! =P
9. Should I install ICS Beta Full on my Galaxy Ace Android 2.3.4???
10. Already rooted, so how much time will it take from installing cwm to installing the custom ROM? I want to know so I won't panic
11. If I install cwm, does the recovery automatically becomes the custom recovery?
12. What does a full wipe mean and do I do it with the stock recovery or with the custom recovery?
Please be as detailed as possible, and use small words.
Appreciate it guys!
Thanks a lot!
first zip is for cwm4 official one
second is cwm5.. i personally prefer cwm4 as had no problems with it
cwm5 failed to take backup when i tried to several times
and i have flashed all roms that claims to do it with cwm5 with cwm4 with no problems at all
you can copy backup images to laptop but DO NOT modify names of any folder as it will result in mismatch of md5 so copy directly folder as it is without modification
ROM MANAGER IS ***** DO NOT INSTALL ON SGA or else you loose your device damn
you can flash it on stock kernel as well
if you want to go back to stock rom from restoring backup then your backup must be taken after converting filesystem to ext4 or else it will fail..
so before backing up flash cf-root and convert fs to ext4 to save time of flashing stock from odin and then restoring backups
thats your option to install cm9 on phone as its not stable and needs many changes at this time.. if you are ok with bugs then you can
1. yes u should delete it. judging by the name its for sgs2, would brick ur phone instantly if flashing that one.
2. i dont really sure about cwm 5.0.2.6 (ur second file) either it can be flash from stock recovery or not but the cwm 4.0.0.6 (ur 1st file) definitely can. and i think its "install zip from sdcard" in stock recovery to flash it.
3. yes.
4. yes, its located in /sdcard/clockworkmod/backup.
5. yes.
6. by flashing stock rom via odin.
7. nope. here if we said cwm or clockworkmod, its referring to the recovery itself (clockworkmod recovery). rom manager is different thing, a tool used to flash cwm or rom. and yes, u should avoid it as countless sga already bricked because of it. and yes, clockworkmod is nickname of the guy who created it and named it as clockworkmod recovery, and here we just called it cwm.
8. again, avoid using rom manager
and u probably wanna read this
http://www.addictivetips.com/mobile/what-is-clockworkmod-recovery-and-how-to-use-it-on-android-complete-guide/
1.First one is official CWM recovery..Its v4..Second one is unofficial CWM recovery..Its v5..I didnt have any problem with them both..But,you should not rename the backups you take with cwm5,it will give you a md5 mismatch error when you do that..
2.Yes..Just copy the file to the sd card
3.Nandroid is a feature of CWM...So,yes.When you flash cwm,you get Nandroid backup
4.Yes...It backsup everything on your phone.But as amit said,Dont rename them
5.By stock,if what you mean is,an untouched Firmware,like the one you got from the factory..Yes..But if you are going to flash any roms,it may convert the system partition to ext4,which will result in a bootloop if you try to restore the stock you have now.So,a better option will be to flash with Odin
6.If you go back to stock,you would still have cwm as your recovery..If you want your stock recovery back,you will have to do a flash with Odin(But,trust me,You will never feel to go back to a complete stock rom and the stock recovery after you start playing around with the other cm7 roms
7.CWM is a recovery..ROM Manager is an application..ClockWorkMod recovery is not a developer..Koushik Dutta is the developer of both CWM recovery and Rom Manager..If you have any thought about using ROM manager,then i suggest that you clean that thought because ROM manager does NOT support Galaxy Ace and if you use ROM manager to flash a rom,you are going to BRICK your device
8.Nothing like that,from what i know.I never flashed any kernel Right after i rooted my ace,i flashed cwm recovery..I didnt do anything else
9.Its your choice..The Myth Ics is an awesome rom
phew....
Prawesome said:
1.First one is official CWM recovery..Its v4..Second one is unofficial CWM recovery..Its v5..I didnt have any problem with them both..But,you should not rename the backups you take with cwm5,it will give you a md5 mismatch error when you do that..
2.Yes..Just copy the file to the sd card
3.Nandroid is a feature of CWM...So,yes.When you flash cwm,you get Nandroid backup
4.Yes...It backsup everything on your phone.But as amit said,Dont rename them
5.By stock,if what you mean is,an untouched Firmware,like the one you got from the factory..Yes..But if you are going to flash any roms,it may convert the system partition to ext4,which will result in a bootloop if you try to restore the stock you have now.So,a better option will be to flash with Odin
6.If you go back to stock,you would still have cwm as your recovery..If you want your stock recovery back,you will have to do a flash with Odin(But,trust me,You will never feel to go back to a complete stock rom and the stock recovery after you start playing around with the other cm7 roms
7.CWM is a recovery..ROM Manager is an application..ClockWorkMod recovery is not a developer..Koushik Dutta is the developer of both CWM recovery and Rom Manager..If you have any thought about using ROM manager,then i suggest that you clean that thought because ROM manager does NOT support Galaxy Ace and if you use ROM manager to flash a rom,you are going to BRICK your device
8.Nothing like that,from what i know.I never flashed any kernel Right after i rooted my ace,i flashed cwm recovery..I didnt do anything else
9.Its your choice..The Myth Ics is an awesome rom
phew....
Click to expand...
Click to collapse
if you want to backupp your stock original firmware and want to restore wit cwm
download cf root
and then use ext4 manager
to convert system to ext4
then wen done you can backupp your stock original rom
and restore it with no problems ( ive used this a lot )
======================
SGSII styled rom
for galaxy ace
======================
The Serious MOD V1
fir galaxy ace
======================
The Serious MOD V0
for galaxy gio
======================
made by Robinandroid
about number 5 and using odin in general
Hi. Thanks a lot guys for your effort in helping out a newbie.
I'm a bit confused about using odin. Is odin like the "safer" way to flash ROMs?
I know I can flash a ROM via booting into recovery, then "install update from sd card", and selecting the ROM. Does Odin do the same thing? When exactly should Odin be used? Only when I want to go back to my original stock firmware AND the original/stock recovery?
Thanks!
As far I know, ODIN is only for flashing stock ROM's.
And well, even if it can be used to flash custom rom's,please do not use it. ODIN can brick your phone. Flashing via recovery is the most safest way
further clarification
Hey guys, thanks a lot. Please clear these up for me:
1. If I am now on stock ROM (never flashed a custom ROM before), then I flash a custom ROM like TheMyth ICS Beta 2 Full, and wish to go back to my stock ROM (which was backed up with clockworkmod recovery), do I simply boot into cwm recovery and restore the stock ROM or do I use Odin?
2. If I am now on stock ROM (never flashed a custom ROM before), then I flash a custom ROM like TheMyth ICS Beta 2 Full, and wish to try another custom ROM like cyanogenMod, should I just flash cyanogenMod with cwm recovery? Meaning, from TheMyth ICS Beta 2 Full straight to CyanogenMod via cwm recovery? Or do I have to go back to stock ROM, as well as stock recovery, by using Odin, and then flash cyangogenMod via stock recovery?
3. If I am now on stock ROM and wish to upgrade to an official android version thru samfirmware.com, do I simply flash it with the stock recovery or do I have to use Odin?
Thanks a lot guys!
1- yes
2- yes, straight away. no need to go to stock rom
3- odin
This is my first time posting.
I am a noob, but I am trying to get beyond that. I have flashed kernels and ROMS to my GT-I9100, with success. The other day, I was going to flash a new ROM, and I tried to make a Clockworkmod backup of my current ROM...while the phone was charging. Is this a major blunder?
The reason that I ask is that CWM crashed in the middle of the backup, and now I can't enter CWM recovery and the phone doesn't boot properly. I just get stuck in a bootloop. I can get into download mode. I used Pistachio's post about how to fix a soft-bricked GS2 to flash back to stock thru Odin. Then I used CF-ROOT to re-root the phone. After that, everything works fine, and I can get to Android recovery mode. Then when I try to flash a ROM, Titanium Backup must be restoring the previous version of ROM Manager, and I get stuck in the same bootloop when trying to get into CWM recovery.
Is Clockworkmod corrupted? Did the recovery partition get corrupted? Should I flash back to stock, delete ROM Manager, then re-install it? Should I bite the bullet and delete my Titanium Backup folder, then re-install everything from scratch? Should I flash back to stock with Pistachio's .PIT file and tick RE-PARTITION?
I looked for an answer specific to this problem, and cannot find the exact same scenario in any other threads. There are similar problems, but I think that I have a CWM app or recovery partition problem, or I may have a NAND rw corruption. I don't think that it is a NAND rw corruption though, because I can flash different kernels and ROMs.
I have been using Resurrection Remix versions 2.2, 2.4.1, and 2.5.3.
I have been using Siyah 3.3.2 kernel.
Please help, and excuse my noobness if I am beating a dead horse with this question.
Sounds like Rom Manager borked CWM/CWRecovery, which it seems to do on SGS2 quite a lot.
Most of the scenario you outlined in para.3 of your post (back to stock, delete ROM Manager) sounds like a good WTG, but do not reinstall it.
If you're going to use a kernel which has CWM/CWRecovery (like Siyah), do not use Rom Manager at all. Uninstall it & keep it that way. CWM/Recovery can do pretty much everything Rom Manager can, and you're playing with fire having both on the phone. Eventually Rom Manager will bork CWM again if you use it.
In the first instance, go back to stock, re-root your phone & reinstall the rom/kernel you're wanting to use. If Rom Manager is installed by default, uninstall it before you do anything else. With a bit of luck, you shouldn't have to do anything else (like messing around with PIT's which you also mentioned in para.3). If you batch restore your apps with TI, make sure you don't restore Rom Manager.
Thanks for the speedy reply.
I will try what you have suggested, but how do I flash the .zip file from my phone without ROM Manager? Do I have to do it through Odin?
Yep, that's right. Get an Odin flashable rom from Intratech's thread (search for it on here). If links in that thread don't work, search here or Samfirmware.
Edit - And once you've got your phone back up & running the way you want, use CWRecovery to do all your flashing.
My apologies, I should have been more specific. I want to flash the RR 2.5.3.zip. Should I still download it to the PC, then flash through Odin, or can I use Android recovery to do it through the phone?
OK. Let's rewind a bit.
What state is your phone in right now ?
I am flashed back to stock, and about to use CF-ROOT.
OK. Root the phone, CWM/Recovery will be installed by default. Once the phone is rooted, reboot into CWRecovery, flash your RR zip & you should be GTG. Just remove Rom Manager if it's installed as part of that process before you do anything else (including backing up). If you're going to restore a backup, again, uninstall Rom Manager immediately after you restore.
OK, after I flash CF-ROOT, I will re-install Titanium Backup, and delete ROM Manager to be safe before proceeding. Then I will flash the ROM.zip and test CW recovery and reboot again. I will reply after doing so.
Thanks
ARRRGH!
After flashing CF-ROOT I cannot get to the splash screen upon reboot. I made sure that I ticked USB debugging before flashing the kernel. I can still get into download mode and CWRecovery, so I flashed back to stock, and tried again to no avail. I tried flashing the RR 2.5.3.zip, in CWRecovery, and it flashed. I get to the splash screen but no further. I feel like a terrible noob now, because yesterday I had the phone flashed to stock and rooted no problem. Is there something that I am missing? I made sure that I used the proper CF-ROOT kernel.
So you're getting bootloop when you flash RR ? Have you tried booting into recovery & doing a wipe/factory reset ?
I believe that I am fixed.
I restored a Nandroid backup of my stock ICS from right after my original rooting, and the phone booted fine. I did a wipe/factory reset and wiped cache. Then I flashed RR 2.5.3. The phone rebooted fine again. I IMMEDIATELY uninstalled ROM Manager and made sure it was out of Titanium Backup as well. I have rebooted several times, normal, download, and CWRecovery, and everything works as it should. I think that I am getting over my noobness.
I WILL NEVER INSTALL ROM MANAGER AGAIN...DOWN WITH ROM MANAGER!!!!!!!!!!!!!! Except for the Little Alex icon, that's still pretty cool.
A thousand thanks for your help. At least I was on the right track when I first asked for help. I was pretty sure it was a problem with ROM Manager, because when it crashed, it started this whole mess. I'll be sure to press the THANKS button for your help, and I'm going to thank Pistachio for his thread as well.
Not n00bness, stuff happens sometimes ;-) You weren't the first person to get tripped up by Rom Manager (I did not long after I got my phone), and you won't be the last.
Yep you had a fair idea of what might have caused it, and your detailed OP certainly made it a lot easier to work out WTF was causing the problems.
No probs. Glad you got it sorted ;-)
I tried following this:
http://forum.xda-developers.com/showthread.php?t=1580070
"INSTRUCTIONS" part:
* RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
* RECOVERY: Install Rom: Download
* RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
* RECOVERY: Wipe Cache Partition
* RECOVERY: Wipe Dalvik Cache
* Reboot and enjoy
Click to expand...
Click to collapse
did all the above, never forgot any of the 3 wipes/resets that were necessary.
used this rom file:
http://goo.im/devs/paranoidandroid/roms/i9100g
(latest one)
for my Galaxy Samsung S II GT-i9100g.
I had CWM and also had a rooted android 2.3.
first boot it showed me the normal samsung boot screen, for 45 minutes....
so I restarted and the phone gave me the same behaviour..
so I removed the battery to turn off the phone, and attempted to reinstall the whole thing, going through this process again from scratch
not forgetting any of the wipes etc...
now every time I boot it, it leads me to CWM instead of the normal boot screen and the expected paranoid rom eventually...
I followed this path because CM 10 failed me because upgrading from 2.3 to 4.x requires going through something that is called "stock" or as I think it actually is - google's /manufacturer's original firmware/rom production line thingy
and after that it needs me to re-enable root on that stock rom all over again. And only then I may attempt to install CM10...
so I picked paranoid instead, because in it's instructions is showed me no such constraint. heck it can't give me that constraint because there is no "stock" of android 3.x for smartphones
but then this issue happened... so I need your help.
I found similar search results but couldn't figure out their solutions or how whatever triggered that same problem (which isn't mentioned in those threads) is related to what I did to my phone... (so that I will not repeat the same mistake)
your help is much appreciated as I need it so so much!
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
gastonw said:
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
Click to expand...
Click to collapse
by "flash"ing you mean the option "install from a zip file" in CWM in recovery mod?
if I have some rom, the only way for me to install another would always be by going through that middle step of also installing a 'stock' rom as well?
there is no way around it?
installing a 'stock' rom, wouldn't it make me loose my root I have on the phone and force me to root it all over again before I can continue install anything at all?
thats the reason I wanted to try out the paranoid way of doing this instead of the CM10, because I have no interest in rooting my already rooted phone and I hoped that paranoid does not need me to go to stock first....
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
some questions
ONE QUICK IMPORTANT QUESTION BEFORE THE REST:
If I use mobile odin, will I be able to use it to install stock rom and also root it at the same time?
SECOND IMPORTANT QUESTION:
you said I could flash whatever I want and still have root, but my problem was not 'not having root', it was not having the flash process complete successfully... how do I attack that?
THIRD IMPORTANT... info... :
My "BUILD" version is "GINGERBREAD.XXKL5", isn't that a 'stock' one?
If you don't have a lot of time,
then the rest of this post is not as important as the 2 questions above...
gastonw said:
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
Click to expand...
Click to collapse
the saddest part is that I couldn't figure out most of what you just said
what is 'nandroid'? 'flashing'? do you mean like dd in linux? copying to the entire flash storage device?
'IMEI'? huh..? O_O
at the moment I was able to 'get back on my feet', I restored everything back to normal with manual copying of important parts of the CWM corrupted backup from this week, and old stuff for a CWM backup made few months ago.
now that I am at a 'normal' state.. I want to install paranoid or CM10 on my GT-I9100g.
which one of those 2 does not force me going through installing stock?
I have this fear of installing stock that it will take away my root and that I will have to use adb from command line to re-enable root afterwards, which I have bad experience with.
I need to know a few things before I attempt to install stock via CWM,
will installing stock disable my root? will installing stock disable my ability to load recovery boot menu CWM?
is 'root' an attribute or state that belongs to the running rom itself after boot has been completed and to that only?
or does it also belong to the state the device is at while in the recovery boot menu CWM ?
I tried messing around with ADB in the past to see if I could root devices via that way but it wasn't very successful so thats why I'm afraid of having to attempt it again.
bumpitybump
even though a year later, I would still love some replies
resurrecting my motivation to do this once again.
copy paste from my other post;
before flashing, you will need these;
-stock rom (get it from Sammobile, sign in and select your country and phone model)
-blazing kernel for recovery (search in XDA)
-custom rom (CM, PA, Supernexus...your choice)
-backup your data
-GApps (get the latest one)
-you must know what are you doing and dont flame/blame other member if something wrong
how to flash;
-make sure you are on latest stock rom (mine is JellyBean 4.1.2), if not like the OP, flash the latest stock rom using Odin;
*reboot your phone in Download Mode
*open Odin and in PDA option select your stock rom and then Start
*if done it will display Done and disconnect your phone, it will boot up
*if bootloop, reboot into Recovery Mode, and then wipe data and cache, and then reboot normally
-after updating your phone to latest stock rom, copy your custom rom, GApps, and Blazing kernel into external SD card, then reboot into Recovery Mode
-choose "apply update from external storage" and choose Blazing kernel, wait for it to finish update
-reboot normally, and then reboot back to Recovery Mode. this time you will notice that your recovery is different from the previous one
-select install zip > choose from external storage/sdcard 1 > and then choose your custom rom. then wait for it to finish update
-repeat the above step to install GApps, and after that reboot normally
-if bootloop, reboot back to Recovery Mode and then wipe data, cache and dalvik and then reboot
-done, now you are running on custom rom
Click to expand...
Click to collapse
and about the root, i believe that almost all custom rom rooted