I am aware that this has been asked before but there are conflicting answers withing the threads that I have read.
I am running 4.1.2 WLSW having worked my way through the various jb releases over time. Root has been retained using everroot in mobile odin. The kernel is stock.
Having decided to install a stable release of cyanogenmod (10.1.3) I have been reading around for days to avoid pitfalls or to know what to do should a problem arise.
The only one thing that I am still unsure about is whether it is indeed safe to use a temporary cwm (flashed via stock recovery) to install cyanogenmod. I have downloaded the latest temporary cwn from the rommanager site and it appears to work just fine - I have created a backup without issues so I can get back to where I am now if I don't like or have problems with cyanogenmod.
I was planning to flash [KERNEL] ClockworkMod Recovery 6.0.2.9 from this thread http://forum.xda-developers.com/showthread.php?t=1118693 - but in the last couple of pages in the thread there are users that have had boot failures after flashing it. This is what has lead me to ask the question is it safe to use the temporary cwm?
I am aware that there are other kernels that I could use (Philz/Siyah) but would like to know which cwm is safest/best for the installation of cyanogenmod.
Install philz kernel by flashing in stock recovery and put that zip on ext sd. Stay away from rom manager. Dont use it. When you have philz installed make a nandroid bkup and make sure preload is included too. Also bk up you're efs folder with ktool free from playstore. As you have root get that and bk efs up asap. once you have done a nandroid bkup and done the efs bkup then flash cm. May be good to get a copy of you're modem now too.
andrewwright said:
Install philz kernel by flashing in stock recovery and put that zip on ext sd. Stay away from rom manager. Dont use it. When you have philz installed make a nandroid bkup and make sure preload is included too. Also bk up you're efs folder with ktool free from playstore. As you have root get that and bk efs up asap. once you have done a nandroid bkup and done the efs bkup then flash cm. May be good to get a copy of you're modem now too.
Click to expand...
Click to collapse
I have backed up efs already using ktool and have already made a nandroid backup using temporary cwm - good advice none the less.
I have read that rommanager is problematic with the i9100 so am not planning to use it.
My method of choice to flash Philz would be mobile odin (unless there is some disadvantage by doing it this way?).
Regarding my modem, it is included in the stock firmware so I could flash just the modem from this using mobile odin if I have trouble (I have assumed mobile odin works in cm).
My original question remains however - why not use temporary cwm?
Mobile odin will work on cm. And yes you can flash with temp cwm. Get you're modem from here on xda. Makes no odds how you flash philz Use odin or recovery its up to you.
andrewwright said:
Mobile odin will work on cm. And yes you can flash with temp cwm. Get you're modem from here on xda. Makes no odds how you flash philz Use odin or recovery its up to you.
Click to expand...
Click to collapse
If I can flash with temp cwm, there is no need to flash philz at all - or have I missed something?
If you flash with temp there's no guarantee. Philz then flash is a safer way of doing things.
andrewwright said:
If you flash with temp there's no guarantee. Philz then flash is a safer way of doing things.
Click to expand...
Click to collapse
Presumably the latest Siyah kernel will also do?
Yes that's ok
It's simply a matter of preference.....temporary CWM is as it 'says on the tin'........temporary....
You have to reflash it every time you want to use it.
PhilZ is permanent....once it's flashed, it's there, no further action needed, plus it has a touch interface unlike regular CWM......
If you intend to stay with stock, but want to have the advantages of CWM, then I'd advise go with PhilZ...purely because a few steps less are necessary to be able to use it.......
(Enter stock recovery, flash CWM then use CWM to flash whatever..... every time with temporary CWM)
If you intend to flash a custom ROM, it'll come with its own permanent CWM anyway (which will overwrite the PhilZ kernel and/or remove the need to continuously reflash the temporary CWM)
Sent from my GT-I9100 using xda app-developers app
Thanks for the advice folks. I flashed Siyah then installed cm 10.1.3 and the associated gapps. All went without a hitch. I was actually surprised how quickly the process completed. I had the rotating cm boot image less than 2 minutes after starting the install from first zip.
Off topic, but I am totally impressed with the cm ROM. I find my frustration at constantly waiting for phone manufacturers to catch up with vanilla android releases has completely melted away.
Glad it's sorted :thumbup:
Add solved to name of thread pls
Related
Hi. I'm running CyanogenMod on my Samsung Galaxy S II i777 (the AT&T one). I was running UnNamed ROM on it, and that had ClockworkMod Recovery v5.0.2.7. But after I flashed CyanogenMod, the ClockworkMod Recovery downgraded to v5.0.2.3. How can I update back to the 5.0.2.7 version?
The reason I ask is because in v5.0.2.3, the backup options are limited, and it doesn't allow me to restore my old, v5.0.27 Nandroid backups in case I need to. I've done a Google search and searched the XDA forums, and the only help I found was to use the ROM Manager app. However, in this post, user creepyncrawly advises me not to use ROM Manager because it "has problems on this phone." I also found some custom kernels, but those were for different phone models.
So how can I update ClockworkMod Recovery without losing any data?
You need to install a kernel that has the newer CWM.
Your post doesn't make sense unless you installed a VERY old CM7 release, considering that the CWM 5.0.2.7 binary in my kernels was pulled FROM CyanogenMod.
I made a mistake. I meant to say that I have CWM Recovery 5.0.2.6, not 5.0.2.7. But my problem is still the same: in CWM Recovery, I don't have the option to "Advanced Restore from SD card." Even when I move my old Nandroid backups (created under CWM Recovery 5.0.2.7) to my phone, they're still not picked up by CWM Recovery 5.0.2.6.
Anyway, thanks for letting me know how to update. Any zImage from any custom ROM will work, right? I'm just trying to do this without incrementing the flash counter on my phone. So I need to choose one from this subforum, and flash with Mobile Odin?
Completely_Clueless said:
I made a mistake. I meant to say that I have CWM Recovery 5.0.2.6, not 5.0.2.7. But my problem is still the same: in CWM Recovery, I don't have the option to "Advanced Restore from SD card." Even when I move my old Nandroid backups (created under CWM Recovery 5.0.2.7) to my phone, they're still not picked up by CWM Recovery 5.0.2.6.
Anyway, thanks for letting me know how to update. Any zImage from any custom ROM will work, right? I'm just trying to do this without incrementing the flash counter on my phone. So I need to choose one from this subforum, and flash with Mobile Odin?
Click to expand...
Click to collapse
Flashing in CWM won't trip the flash counter. I suggest using SiyahKernel, since I'm pretty sure Entropy's Daily Driver doesn't support CM7.
Solved!
jcracken said:
Flashing in CWM won't trip the flash counter. I suggest using SiyahKernel, since I'm pretty sure Entropy's Daily Driver doesn't support CM7.
Click to expand...
Click to collapse
This worked beautifully! I now have CWM Recovery 5.0.2.7, and my phone info shows that I have SiyahKernel as well.
Thank you very much!
jcracken said:
Flashing in CWM won't trip the flash counter. I suggest using SiyahKernel, since I'm pretty sure Entropy's Daily Driver doesn't support CM7.
Click to expand...
Click to collapse
It doesn't support CM7, but should be able to restore a CM7 Nandroid.
So let me see if i understand this correctly. From what i have read, it looks like i cant install CWM recovery without installing a custom Kernel? So me backing up my stock set up is pretty much out of the question? So everytime i wish to install a different custom rom i am essentailly reinstalling CWM recovery as well?
How can i backup my stock set up and restore it if i screw something up, or install a rom that i am not happy with? I am coming rom an epic 4g on sprint and it was different with that galaxy phone.
Flash a CF Root kernel that matches your firmware, create your near stock b/u. This will be your point to fall back on. 99.99% of ROMs you flash will include a kernel, that also has CWM, it may be a different version but they all work the same, for the most part. The majority of kernels include CWMr 5 or higher.
You'll always have the option of restoring your "stock" b/u so long as you don't delete it. Titanium b/u is the ticket to back up all your apps and their data rather than having to extract those apps/data from a CWM b/u.
You only have to root once. The easiest way to unroot is to flash a stock firmware. Flashing a stock kernel back on after you've rooted will replace CWM recovery with stock recovery, but you'll remain rooted. Probably doesn't address all your questions, but you've got a start.
mudferret said:
Flash a CF Root kernel that matches your firmware, create your near stock b/u. This will be your point to fall back on. 99.99% of ROMs you flash will include a kernel, that also has CWM, it may be a different version but they all work the same, for the most part. The majority of kernels include CWMr 5 or higher.
You'll always have the option of restoring your "stock" b/u so long as you don't delete it. Titanium b/u is the ticket to back up all your apps and their data rather than having to extract those apps/data from a CWM b/u.
You only have to root once. The easiest way to unroot is to flash a stock firmware. Flashing a stock kernel back on after you've rooted will replace CWM recovery with stock recovery, but you'll remain rooted. Probably doesn't address all your questions, but you've got a start.
Click to expand...
Click to collapse
forgot to mention that i am rooted now. using oneclickroot.
Just flash a custom kernel with CWM recovery installed inside.
Such as:
- Siyah
- Phoenix
- Ninphetamine
etc...
DO NOT FLASH STOCK KERNEL AS IT WILL DELETE CWM RECOVERY. ROM MANAGER DOES NOT INSTALL RECOVERY ON YOUR PHONE.
nicholaschum said:
Just flash a custom kernel with CWM recovery installed inside.
Such as:
- Siyah
- Phoenix
- Ninphetamine
etc...
DO NOT FLASH STOCK KERNEL AS IT WILL DELETE CWM RECOVERY. ROM MANAGER DOES NOT INSTALL RECOVERY ON YOUR PHONE.
Click to expand...
Click to collapse
is it as simple as using Odin, clicking PDA and flashing the downloaded kernel? and there should be no side effects from using a custom kernel such as Siyah?
Getting back to 100% stock is easy, odin flash a rom.
CF root *is* the stock kernel, just with some bits added (CWM recovery and root).
CF root with your stock rom is defo the safest bet.
jerseykat1 said:
is it as simple as using Odin, clicking PDA and flashing the downloaded kernel? and there should be no side effects from using a custom kernel such as Siyah?
Click to expand...
Click to collapse
Yes if you get the kernel in odin tar file, otherwise flash CF root and use CWM recovery to flash the zips.
Hi Everyone,
Every time I restore a sammy JB install from recovery it always hangs on the bootscreen and never boots up. I was wondering if anyone has had this issue before or its something that I'm doing wrong
When restoring I always run an odin flash using mobile odin and root it with philz. I then delete all the system folders, wipe cache etc and restore.
If i used a different kernel to backup the install i will install that kernel before restoring.
I've tried several roms such as neatrom, Alliance and Wanam but get the same result. CM/AOSP roms restore ok.
If anyone has any suggestions it would be much appreciated.
Many thanks
Question since you state you using philz kernel why dont you use his CWM to backup and restore your backups instead of Odin mobile.
iT comes as part of the kernel http://forum.xda-developers.com/showthread.php?t=1877270
Nyssa1104 said:
Question since you state you using philz kernel why dont you use his CWM to backup and restore your backups instead of Odin mobile.
iT comes as part of the kernel http://forum.xda-developers.com/showthread.php?t=1877270
Click to expand...
Click to collapse
Thanks for your reply.
I only use mobile odin to flash official firmware so its a fresh start before installing a rom.
I've tried to restore from philz before but had the same problem. Normally use Dorimanx.
I myself had no probles with Mobile odin pro of CWM in Philz kernals and since Philz kernal this tends to be the normal backup or flashing aid for me. Since I have a Micro SD card install back up and roms are place on this..
by the way Im using SuperSUPro and not Superuser for root.
symondo12 said:
Hi Everyone,
Every time I restore a sammy JB install from recovery it always hangs on the bootscreen and never boots up. I was wondering if anyone has had this issue before or its something that I'm doing wrong
When restoring I always run an odin flash using mobile odin and root it with philz. I then delete all the system folders, wipe cache etc and restore.
If i used a different kernel to backup the install i will install that kernel before restoring.
I've tried several roms such as neatrom, Alliance and Wanam but get the same result. CM/AOSP roms restore ok.
If anyone has any suggestions it would be much appreciated.
Many thanks
Click to expand...
Click to collapse
I have a possible solution just flash entire original rom(the one you are going to restore) once, then restore your nandroid backup, clear cache/dalvik, reboot. I have a hunch on the problem that it might be caused by another roms /preload partition data (our nandroid backup won't usually backup it by default so it actually never gets wiped or overwritten)
Edit :I forgot to mention a factory reset at the beginning.
Sent from my GT-I9100 using xda app-developers app
I am almost ready to perform my first custom ROM installation.
I am only travelling with a Mac so I can't use Windows software.
Is there a way to backup my/EFS directly from the phone?
Sent from my GT-I9100 using Tapatalk
You need a custom recovery. How will you flash a custom rom w/o custom recovery?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Blomberg said:
I am almost ready to perform my first custom ROM installation.
I am only travelling with a Mac so I can't use Windows software.
Is there a way to backup my/EFS directly from the phone?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Download HC ktool from the market, create your efs backup with it and use a root explorer to copy it to an external removable micro SD card......
Edit.......you need to be rooted in order to use HC ktool.......
This might be my S2, or it might be my W...but it's definitely CM
mezo91 said:
You need a custom recovery. How will you flash a custom rom w/o custom recovery?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For rooting I will use Framaroot.
For installing CWM I believe that you can install it via ROM Manager, or you can install the ROM directly via Mobile Odin.
Sent from my GT-I9100 using Tapatalk
OK....first....
Why look elsewhere for rooting methods? Everything you need is right here on XDA.
Second.....NEVER use ROM manager on an S2.....it breaks things.
Third....mobile Odin can only be used on rooted devices....primarily for flashing stock firmwares.
What version of android is on your S2....GB, ICS or JB?
This might be my S2, or it might be my W...but it's definitely CM
Yes, I found Framaroot here and am planning to use it for the rooting purposes.
Thanks, good to know. So I will need to install CWM manually I guess. Somehow.
What is it that Mobile Odin does, is it an actual reovery ROM itself or does it install CWM which in turn installs the ROM?
But I can use Mobile Odin to install a custom ROM I think?
I am 4.1.2 JB
Sent from my GT-I9100 using Tapatalk
Mobile Odin is a phone based version of PC Odin.....it is designed to flash back to stock from a rooted modified phone without the need to hook the phone to a PC....
You're on 4.1.2.....
Search for the PhilZ thread.......
With the downloads contained, you can root and flash CWM via the stock recovery in one flash.....don't get much easier than that.......
This might be my S2, or it might be my W...but it's definitely CM
I can root it and flash it in one step? I've found like 50 guides but none of them as simple as you're suggesting.
There are so many ways to do each individual step.
I reckon the steps after that would be to install my custom ROM via CWM via SD card. Clear/Wipe cache and install the custom ROM again?
Sent from my GT-I9100 using Tapatalk
Edit: How can I backup EFS before using the technique you mentioned to root/flash CWM in one go, if my device is not yet rooted?
As I said........easy.....
1) flash PhilZ via stock recovery to root and flash CWM
2) At this stage your phone will still boot normally and allow you to download HC ktool in order to make your EFS backup. It might be an idea to make a full backup (nandroid backup) of your current setup using CWM too....
3) use CWM to flash the ROM (and it's associated gapps package) of your choice.
4) use CWM to perform the cache, dalvik and data wipes.
5) reboot, perform initial setup download user apps.......
Job done.......
This might be my S2, or it might be my W...but it's definitely CM
You could also juse Siyah Kernel, a good alternative to philz:good:
Except that it can't be flashed via the stock recovery.....it has to be flashed via Odin......
This might be my S2, or it might be my W...but it's definitely CM
In which way does a Kernel replace a rooter/bootloader flasher, are these not different things?
Sent from my GT-I9100 using Tapatalk
keithross39 said:
As I said........easy.....
1) flash PhilZ via stock recovery to root and flash CWM
2) At this stage your phone will still boot normally and allow you to download HC ktool in order to make your EFS backup. It might be an idea to make a full backup (nandroid backup) of your current setup using CWM too....
3) use CWM to flash the ROM (and it's associated gapps package) of your choice.
4) use CWM to perform the cache, dalvik and data wipes.
5) reboot, perform initial setup download user apps.......
Job done.......
This might be my S2, or it might be my W...but it's definitely CM
Click to expand...
Click to collapse
I very much appreciate your help Keith. I've been on numerous forum but never got this good feedback.
I searched the PhilZ thread and got so many results. My model is i9100 of the Galaxy S2, I guess the methods you have been describing works for this model?
I need to backup program data and EFS before I dare start playing around.
How can I backup EFS before using the technique you mentioned to root/flash CWM in one go, if my device is not yet rooted?
You can't. And you don't need to unless your phone is rooted, because if your phone is rooted nothing you can do to the phone is capable of borking the EFS/IMEI.
Edit - Also, I'm detecting a lack of knowledge of 'the basics' in the threads you've posted recently; I strongly suggest you read all the guides/tutorials stickied in the thread near the top of the General section before you do anything to your phone. A lack of knowledge exponentially increases the risk of you permanently breaking your phone depending on how little knowledge you have when you attempt to 'do stuff' to the phone.
For backing up the efs you'll need to flash a recovery first (like Philz as already suggested).
But anyway, problems with the efs won't be caused by just rooting so you can go ahead and root first and then use KTool.
kestrel5915 said:
For backing up the efs you'll need to flash a recovery first (like Philz as already suggested).
But anyway, problems with the efs won't be caused by just rooting so you can go ahead and root first and then use KTool.
Click to expand...
Click to collapse
* * *
Thank you. As I want to perform all the necessary steps directly on my phone, I am now thinking of doing the following.
Installing Framaroot (APK) and rooting my Samsung Galaxy S2 i9100 (http://forum.xda-developers.com/showthread.php?t=2130276)
Installing KTool and backing up EFS to external SD-card
Installing Titanium Backup (Root version) to backup AppData
Alt 1.) Downloading Mobile Odin to OS. Flashing ROM + GApps via this. But this keeps my stock recovery? (http://forum.xda-developers.com/showthread.php?t=1347899)
Alt 2.) Downloading PhilZ Touch Recovery 3.0 for Galaxy S2 i9100 which flashes + re-roots for me (?). Not sure if it's the right version as the post is old? (http://forum.xda-developers.com/showthread.php?t=1840223)
Alt 3.) Flashing CWM via Mobile Odin, and then in turn boot to recovery (now CWM) and flashing ROM + Gapps via CWM. This should update my recovery as well as my ROM?
After flashing ROM, entering recovery to Wipe Cache, Dalvik and Data
Flash ROM again as previous step supposedly deletes the ROM?
Boot ROM, Configure, Install Apps and restore App Data
Does the above look correct?
Is the version of PhilZ the correct one? It appears to be a 'temporary recovery' rather than a permanent, which might be what I am after if I want to flash the current version of CWM for Galaxy S2 from www.clockwerkmod.com/rommanager
Follow the instructions I gave in this post....
http://forum.xda-developers.com/showthread.php?p=48583106
and you will have a rooted phone running a custom ROM. No need to reflash the ROM after the wipes. Wiping cache, dalvik and data will NOT erase the ROM, all it'll do is erase any personal settings and downloaded apps.
Mobile Odin can't be used to flash custom ROMs, I think it can be used to flash CWM.... but only if you can find a compatible version in a .tar format.
PhilZ is still your best bet.....you will root your phone and install CWM in one hit.....all from your existing stock recovery. The CWM inPhilZ is NOT temporary, though it WILL be overwritten when you flash the ROM which will contain it's own permanent version of CWM. Just match your phones build version to the PhilZ kernel that you download.......
Why make extra work for yourself by increasing the number of steps you have to take (use framaroot then try to find a compatible CWM) when you can do it in one step?
And as mentioned before.....DON'T use ROM manager on an S2.....it breaks things....specifically recovery....one of your prime goals.....
This might be my S2, or it might be my W...but it's definitely CM
cubflyer said:
You could also juse Siyah Kernel, a good alternative to philz:good:
Click to expand...
Click to collapse
I made big projects of things. As a complete novice within Android, I've read through numerous threads, made project notes, consolidated info and made Mindmaps to understand this.
From my understanding, a kernel (I've seen Siyah mentions on many places) is the interpreter between hardware and the instructions given by the software.
In which way is this comparable to a recovery partition/ROM, namely PhilZ?
I'm sure it's some detail I'm missing, and thanks for the tip.
keithross39 said:
Follow the instructions I gave in this post....
http://forum.xda-developers.com/showthread.php?p=48583106
and you will have a rooted phone running a custom ROM. No need to reflash the ROM after the wipes. Wiping cache, dalvik and data will NOT erase the ROM, all it'll do is erase any personal settings and downloaded apps.
Mobile Odin can't be used to flash custom ROMs, I think it can be used to flash CWM.... but only if you can find a compatible version in a .tar format.
PhilZ is still your best bet.....you will root your phone and install CWM in one hit.....all from your existing stock recovery. The CWM inPhilZ is NOT temporary, though it WILL be overwritten when you flash the ROM which will contain it's own permanent version of CWM. Just match your phones build version to the PhilZ kernel that you download.......
Why make extra work for yourself by increasing the number of steps you have to take (use framaroot then try to find a compatible CWM) when you can do it in one step?
And as mentioned before.....DON'T use ROM manager on an S2.....it breaks things....specifically recovery....one of your prime goals.....
This might be my S2, or it might be my W...but it's definitely CM
Click to expand...
Click to collapse
Thank you once again Keith for your engagement and good tips.
I think the reasons why I am considering the different options, and also trying them out - is to get a broader understanding of Android and the alternative processes as I approach my goal of flashing a new ROM.
1.) So far I installed Framaroot and rooted the device successfully.
2.) I then downloaded Hellcat's kTool and made an EFS backup (and a kernel dump, whatever that is)
3.) Then I installed Titanium Backup and backed up all user + system apps (+data I think)
4.) I then downloaded CWM from www.clockworkmod.com/rommanager > recovery as a zip, booted the stock recovery and started CWM (locally, without replacing stock recovery for some reason), from which I did a full Nandroid backup (with stock recovery intact in this backup, I guess. Device was however rooted so it's not fully original).
I reckon I now just need to download my custom ROM and it's relevant Gapps.
I have read good things about Mobile Odin, and since a while back it supports *.zip files so I believe it is a good alternative for flashing custom ROM's now as well.
PhilZ was a bit intimidating, as there was a general thread and different model based threads in each subforum. They were also in different versions, dates and basebands. Also it appears to be available in a "permanent" download as well as a "temporary", which caused my confusion in the last thread.
I did not know that the recovery was replaced when installing a custom ROM, as I did not know that they contained their own partition of a recovery ROM.
Thanks for the information about not needing to re-flash ROM after the relevant wipes.
Thanks for the discouragement of ROM Manager, I promise to stay away from it.
From my understanding, PhilZ seems to be a modified version of CWM6, which includes ChainFire's Auto Root and some other add-ons as well. Is this a correct understanding?
You don't need to backup system apps/data from Titanium Backup because restoring them on a new rom will definitely cause issues.
Plus in case of a bad flash or something nandroid is always there for you so before doing anything new with the phone always do a nandroid backup.
Hi
I reccently bought i9300 ( hongkong ) and it came with 4.3, i tried rooting it with CF-Root, The process itself completes with no problem but when i open SuperSu, It asks to update binaries but when i do it fails.
All of the fellow xda helpers have suggested to install CWM and than flash Update SuperSU ***.zip from chainfire, I did that as well ( i flashed the latest zip) But the problem is there.
Can anybody help me with that?
The CF-ROOT and flashable supersu i have flashed are:
UPDATE-SuperSU-v1.91
UPDATE-SuperSU-v1.86
UPDATE-SuperSU-v1.10
CF-Auto-Root-m0-m0xx-gti9300
CF-Root-SGS3-v6.4
Now as i am not rooted so i can't backup the EFS (i don't want to take the risk of loosing my IMEI) and flash stock 4.1.2.
-----------------------------
Here are the details of my phone:
Model no: i9300
Android version: 4.3
Baseband: I9300XXUGNA8
Kernel: 3.0.31-i902166 [email protected]#1
Build no: JSS15J.I9300ZSUBNB1
------------------------------
Thanks
Backup your data.Try to use factoy rom (XXUGMJ9) for odin with pit and repartition.. Flash philz touch recovery and flash lastest update-supersu-v2.01 and should work without error.
Enviado desde mi GT-I9300 mediante Tapatalk
MD500 said:
Backup your data.Try to use factoy rom (XXUGMJ9) for odin with pit and repartition.. Flash philz touch recovery and flash lastest update-supersu-v2.01 and should work without error.
Enviado desde mi GT-I9300 mediante Tapatalk
Click to expand...
Click to collapse
i already did a backup through cwm, Is it good enough ? as i have read in the forum that if you dont have efs backup and you flash stock through odin, you may end up with lost imei; That's the boat i don't wana be on ... so i await your response on that.
Also can you guide me or give me a link to PIT and Repartition stuff, as i am new to samsung, i moved from htc.
After flashing stock, philz, do i need to flash cf-root through odin or update-supersu will do the rooting trick?
Thanks for your response
predator_b4u said:
i already did a backup through cwm, Is it good enough ? as i have read in the forum that if you dont have efs backup and you flash stock through odin, you may end up with lost imei; That's the boat i don't wana be on ... so i await your response on that.
Also can you guide me or give me a link to PIT and Repartition stuff, as i am new to samsung, i moved from htc.
After flashing stock, philz, do i need to flash cf-root through odin or update-supersu will do the rooting trick?
Thanks for your response
Click to expand...
Click to collapse
You should only use pit files as a last resort! Use only if your phone is not booting or major problems like that and definitely not because you can't root!
If you flash latest PhilZ there is a option in the settings to fix supersu try that way first or try a different version of su from playstore.
tallman43 said:
You should only use pit files as a last resort! Use only if your phone is not booting or major problems like that and definitely not because you can't root!
If you flash latest PhilZ there is a option in the settings to fix supersu try that way first or try a different version of su from playstore.
Click to expand...
Click to collapse
using odin i have installed latest PhilZ recovery, although the superSu is having the similar problem but i was able to find " backup efs" underr custom backup, i think internally my phone is already rooted, as custom recovery went on smooth. Will that efs recovery be enough to bring my phone IMEI back? Can you suggest what else should i backup ?
predator_b4u said:
using odin i have installed latest PhilZ recovery, although the superSu is having the similar problem but i was able to find " backup efs" underr custom backup, i think internally my phone is already rooted, as custom recovery went on smooth. Will that efs recovery be enough to bring my phone IMEI back? Can you suggest what else should i backup ?
Click to expand...
Click to collapse
If done properly then yes also I would also suggest making another backup with PhilZ recovery there is a option in settings to do that ( you can never have too many backups) also if you want you can do a full nandroid backup which will restore your phone to how it was before you flashed anything.(but remember nandroid won't backup efs you have to do that separately)
For any fellow xdaz who are seeking help in the same case as mine, Let me update on what i did and what went wrong (although i am still not upto the rooting part)
so as i was on 4.3 ( I9300XXUGNA8)- The rom won't let me root, whatever i did, and i am talking about clearing cache, dalvik, cf-root, superSU update, clearing all superSU app and reinstalling via market and odin.
Than i thought i would ditch the rom and maybe downgrade ( for me that was the wrong idea )
along the way ( as suggested by " tallman43 " i did install PHILZ and did custom backup of efs and i made around 4-5 backups, Big thanks for the awesome suggestion ....i suggest you do the same, as trust me i later found out that 1-2 backups have corrupted files ( i don't know why).
i also downloaded neat rom and in that Aroma installer (rom installer) there was an option for efs backup as well, so i did that and installed that rom. Rom installed without any problem, root was also working fine, i personally love the rom but i have to give my phone to someone and i was hoping for total stock whereas in neat rom there are tags here and there, i would love to have em but as i said earlier...
i downloaded Stock 4.1.2 (I9300OZSEMK2) -- flashed it, flashed went fine but now i got 0000 as my imei, i tried restoring through philz but nothing happened
i restored previously made backup of my old 4.3 but now the imei was displaying " NULL "
finally i stopped there and searched the forums and read through many similar problems, i downloaded 4.3 (I9300XXUGNA8) from sam mobile , flashed it and voila the imei and network is back.
I am not sure what fixed the imei and why was it giving problems on 4.1.2 but i am happy with the results.
I will update for the rooting part and that would be my next step.
http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289
I came across this thread as I am facing the same problem with rooting.
I was on a rooted i9300 and did an upgrade to 4.3 via Kies.
Now when I run through the rooting process using CF method, Odin posted success.
I see inside the console (while flashing cf auto root) that SU binaries are being installed and all. But once the phone reboots, root checker reports phone is not rooted.
I tried a couple of other ways and the closest I got was to see TWRP recovery console once, but once the phone reboots, and I try to go back into recovery - it is still Samsung's recovery console.
Actually all I want is to flash a custom ROM because the phone has been running ridiculously slow. Can I flash it through Odin (under AP) or I have to use a custom recovery like clockwork or TWRP.
duoxx said:
I came across this thread as I am facing the same problem with rooting.
I was on a rooted i9300 and did an upgrade to 4.3 via Kies.
Now when I run through the rooting process using CF method, Odin posted success.
I see inside the console (while flashing cf auto root) that SU binaries are being installed and all. But once the phone reboots, root checker reports phone is not rooted.
I tried a couple of other ways and the closest I got was to see TWRP recovery console once, but once the phone reboots, and I try to go back into recovery - it is still Samsung's recovery console.
Actually all I want is to flash a custom ROM because the phone has been running ridiculously slow. Can I flash it through Odin (under AP) or I have to use a custom recovery like clockwork or TWRP.
Click to expand...
Click to collapse
If you want only to flash a custom rom then you do not need to root custom roms come already rooted (alot of people make this mistake )..Just flash a custom recovery with Odin then follow the procedure in the stickies to flash a custom rom.