I feel like one of my daily job is flashing new ROMs these days.....
Any way, we are getting lots of ROMS that we can flash with different methods.
Because I'm flashing the ROMs almost every day in these days, I just wanted to share some information how I do my daily job. (Lot's of Devs are flashing the Roms with their own ways but I believe the general concept is same and we are always trying to avoid the 'bricks' caused by wrong direction.
In here, what I'm doing is my safest way and I never failed with this method but please do this with your own risk if you want to follow this guide. There are tons of other guide and directions that you may also want to consider.
[Most important thing is, you must follow ROM publisher's instruction first. The information in here is the way what I'm doing day to day basis. So, it may not work based on your situation. Don't blame be if you phone bricked]
* Flashing Calk rooted Stock Rom
1. if you don't have the Modified CWMRecovery kernel something like Rogue Recovery Kernel, before following this guide, you need to download 'it' first.
For me, I use Rogue's FB27 recovery Kernel until another newest stable version comes out. You can download it from
http://forum.xda-developers.com/showthread.php?t=1390393
If you use the .tar file, then I assume that you already have a odin executable in your pc (.tar file in you pc) or mobile odin in your phone (.tar file in your sdcard).
Or if you use the zip file, you need to be sure that you are able to install the zip file through the recovery (zip file in your sdcard).
2. download Calk's rooted stock Rom and place into your sdcard (or external SD).
Most recent Calk's rooted stock Rom can be found at
http://forum.xda-developers.com/showthread.php?t=1552117
Modem file also needs to be required if you want to install the modem at the same time when you flash his rom. If the modem tar file available from other Dev's post, you can flash the modem later or before the flashing his rom thru odin or mobile odin.
3. Be sure that you already have nandroid backup of your current rom or make the nandroid backup before flashing his rom.
4. Check if there's any stock kernel available. If there's no separate kernel available, you need to extract zImage file from Calk's zip file and save to sdcard (for mobile odin) or to PC (for odin). If you want to keep the current Recovery Kernel, you don't need this step.
5. Now I assume that you have all the files ready and placed those to the right places. If your current kernel is not Rogue's, then install his recovery kernel. For me, I use mobile odin and pick it up from sdcard.
After installation, phone automatically reboot. Before the first screen comes out, press vol up + power keys at the same time. It will bring you to the Rogue CWM recovery screen.
6. From recovery screen, select install from zip and point the Calk's zip file you saved. Select and install it.
7. If you want to install the modem at the same time, do the same thing as step 6 but choose the modem zip file. There's no special sequence between step 6 & 7. Anything can be installed first. If you don't have modem zip file but have modem tar file, modem can be installed later. Or you can install the modem first before starting all these steps.
8. reboot
9. The kernel went back to stock kernel. So, if you need to do some recovery task, you need to start from step 5. One example is, if you want to run Calk's Bare Rom converter tool but you missed doing it after installing the ROM, then you need to install the Rogue recovery Kernel again. Usually Rogue Kernel is behind of current Kernel. But don't worry about coming back after the recovery task. This is the reason why I added step 4 above.
Additional steps coming back to current Kernel after the Recovery Task -
1. Install Rogue Recovry Kernel (usually previous kernel version)
2. Reboot and do the recovery task (backup, running Bare Rom converter zip file, cleaning data/dalvik cache, format battery stat, etc).
3. Reboot
4. if you use mobile odin, then install the zImage file or any kernel that you want.
If you use odin, go to the download mode by pressing vol down + power button together and install the kernel.
- if the kernel zip file is also available, then you can skip the steps 3 and 4. Just after the step 2, install the kernel zip file and reboot.
* Flashing ODIN/TAR rooted stock Rom
The basic idea is same to flashing Calk's ROM.
The most recent Stock rooted odin/tar file can be found in http://forum.xda-developers.com/showthread.php?t=1551901
1. if you don't have the Modified CWMRecovery kernel something like Rogue Recovery Kernel, before following this guide, you need to download 'it' first.
For me, I use Rogue's FB27 recovery Kernel until another newest stable version comes out. You can download it from
http://forum.xda-developers.com/showthread.php?t=1390393
If you use the .tar file, then I assume that you already have a odin executable in your pc (.tar file in you pc) or mobile odin in your phone (.tar file in your sdcard).
Or if you use the zip file, you need to be sure that you are able to install the zip file through the recovery (zip file in your sdcard).
2. download odin/tar file. For me, I use sfhub's one-click self-extractor package.
To install this ROM into your phone, please read his instruction carefully. In his package, you can install everything with just one odin or you can install modem/kernel/rom separately. Also, there are two packages available, one is for whom don't want the old data, and another one is for whom want to keep the old data.
3. after the odin finished, phone restarts automatically. Now you have the new ROM installed on your phone but there's no modified recovery Kernel. To do the recovery task, you need to follow the steps in 'Additional steps coming back to current Kernel after the Recovery Task'.
Important - if you don't know what you are doing, please be sure that you know what you are doing before doing anything by asking your questions to someone! There would be someone who can help you about your questions but there's no one who is responsible for your bricked phone!
Related
Because SuperOneClickv1.4 Root did not work for me, I repacked zImage(kernel) from JPM to a single tar for rooting the old fashioned way (flash old kernel, apply update.zip, reflash new kernel): http://www.multiupload.com/I8DCOJBT6J
- extract and copy update.zip to internal sd-card of your phone
- run odin with auto reboot UN-checked, loading the i9000_Kernel.tar as PDA
- put the phone into download mode and flash the i9000_Kernel.tar
- pull the battery. reboot into recovery mode and flash the update.zip you put in the root folder of your sdcard.
- pull the battery again, reboot into download mode again.
- run odin with auto reboot checked, loading the I9000XXJPM_KERNEL.tar as PDA
Hopefully someone can created an update for a working Recovery 2e and ClockworkMod and maybe a fully deodexed and zipaligned ROM (without any other changes).
Also waiting for a Circle Battery Mod and Stock Lockscreen Mod... and voodoo of course!
I so wish someone could create a simple update.zip which would work with stock recovery.
Also custom roms would be cool
kooltools said:
I so wish someone could create a simple update.zip which would work with stock recovery.
Also custom roms would be cool
Click to expand...
Click to collapse
Can't, because they have to be digitally signed.
Can't you guys use the rageagainstthecage method we use on Captivate Froyo JI6? That method does not need having to flash three different times with Odin.
CF-Root (single flash) is coming up.. already built it, but having trouble flashing JP6 itself :/
CF-ROOT based kernel for JPM is coming soon.
sztupy said:
CF-ROOT based kernel for JPM is coming soon.
Click to expand...
Click to collapse
Waiting for a perfoct easy root, ember
Hello all,
OneClickRoot for CWM 3.0.2.5 from stock Froyo (EC05) no worky.
Seemed to work, as phone booted just fine after running the Run.bat. But then on reboot, no recovery, no boot.
I read drockstar's post in his thread on the new CWM - and he mentioned flashing just recovery via Heimdall. Anyone do this? What is the process? He said to extract the zImage and flash to recovery - but that's real confusing because there's a space for the Kernel (zImage), and there's a space for Recovery in Heimdall.
Any thoughts? Any help? Anything is awesome. Thanks!
That's the exact same thing that happened to me.
In the PIT file devices do have a separate entry for both recovery and kernel, which is why Heimdall provides both options. However in the past I've flashed a kernel just in the Kernel slot and had it appear in recovery mode. Ultimately it's up to the secondary bootloader and not Heimdall (Odin or Kies) where the files end up.
Anyway if you just use the Recovery slot and it works then that's great. However there's no harm in placing the file in both Kernel and Recovery slots.
Nooo, if you place it in Kernel, it flashes to bml7, in recovery it flashes to bml8.. they are both technically kernels. a recovery kernel uses fota.rc, and a bml7 (normal) kernel uses init.rc. you DO NOT want to flash a recovery kernel to your bml7, i believe DRockstars cwm3.0.2.5 wont break your phone, but it wont be what you want, its a minimaist kernel. you will lose whatever features you have from whatever kernel you have (twilight zone, genocide, clean kernel, etc) just place the zImage in recovery and thats it. or rename it to recovery.bin and use odin.
chris41g said:
Nooo, if you place it in Kernel, it flashes to bml7, in recovery it flashes to bml8.. they are both technically kernels. a recovery kernel uses fota.rc, and a bml7 (normal) kernel uses init.rc. you DO NOT want to flash a recovery kernel to your bml7, i believe DRockstars cwm3.0.2.5 wont break your phone, but it wont be what you want, its a minimaist kernel. you will lose whatever features you have from whatever kernel you have (twilight zone, genocide, clean kernel, etc) just place the zImage in recovery and thats it. or rename it to recovery.bin and use odin.
Click to expand...
Click to collapse
Sorry! I don't know much about the individual recovery kernels floating around. I made the false assumption that they all added functionality without removing functionality, hence I figured they couldn't cause problems. Obviously a mistake.
I'm obviously aware there are to different kernel locations on the device. However I have flashed certain kernels to bml7 only in the past and had them end up in bml8 for recovery also (probably a kernel feature now that I think about it). Presumably this is to make up for the fact that Odin doesn't allow you to flash the recovery partition directly.
Anyway the lesson here is to make sure you know the details of the particular kernel you're flashing!
I ended up going the odin routw, but thanks fo the knowledge!
In the future, I will try heimdall again and either go only to recovery and/or rename the file to recovery.bin.
Sent from my SPH-D700 using XDA Premium App
funktron said:
I ended up going the odin routw, but thanks fo the knowledge!
In the future, I will try heimdall again and either go only to recovery and/or rename the file to recovery.bin.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Slight correction so that other readers don't get confused. Renaming a file will make no difference in Heimdall. Heimdall intentionally allows any filename to be used. Placing a file in the Recovery slot will result in the file ending up on the device as a recovery kernel. Hence your existing "regular use kernel" will not be modified.
However Odin does look at filenames and matches these to entries in a PIT file. As most PIT files don't contain a separate filename for the recovery partition, in the general case Odin will not allow you to upload to the recovery partition only.
Hi all, I was on AKOP's milestone ROM before trying to flash their newest one. I did not do anything to the kernel or anything by the way.
I'm using ClockworkMod Recovery v6.0.2.7 and I rebooted into recovery and flashed super dark side wipe and then JB-MR1 and then gapps.
I went through the entire start up process with inputting your information and then finally I got into the actual home screen. I clicked around to see how the UI looked and then decided to reboot through the menu.
It was in the rebooting animation icon for at least 30 min before I decided to pull the battery. I want to wipe and start again but my cwm recovery isn't installing anything.
EDIT: The phone still works as I can boot into the phone and use it. I'm trying to reboot now: power button hold>reboot, but its taking ages still...need help on this reboot thanks
Any help here?
EDIT 2: Pretty much phone is "functional" but any method of trying to reboot or reboot into recovery fails
Thanks all!
Check the Md5 hash to make sure it is a good download.
Otherwise it sounds like it is CWM that can be causing issues.
Which version of gapps are you flashing?
8Fishes said:
Check the Md5 hash to make sure it is a good download.
Otherwise it sounds like it is CWM that can be causing issues.
Which version of gapps are you flashing?
Click to expand...
Click to collapse
Checked the Md5 with an app and it matches up perfectly with akop's main website.
I'm running 6.0.2.8 cwm. Is it even possible that its cwm? I used the same version to flash AKOPs new ROM.
and im flashing gapps-jb-20121212-signed.zip
Does it have anything to do with my kernel?
You aren't supposed to use super wipe with cwm 6. That is probably your problem.
meekrawb said:
You aren't supposed to use super wipe with cwm 6. That is probably your problem.
Click to expand...
Click to collapse
Thanks so much for pinpointing the problem! Is there a fix to this?
And is this the recommended method of flashing? (Taken from http://forum.xda-developers.com/showthread.php?t=1926754):
1. Wipe factory data/reset
2. Wipe cache
3. Go into mounts and storage
4. Format /system
5. Format /data
6. Format /cache
7. Enter advanced
8. Wipe dalvik
9. Flash ROM then gapps
10. Reboot and let the ROM settle for 5-10 minutes if flashing TW ROMs, this step is unnecessary for AOSP based ROMs.
11. (Optional) if flashing a new radio flash AFTER the ROM has been initially booted for the first time. No wipes are necessary when flashing a new radio but it HAS to be flashed after the ROM is loaded and settled in. Flashing a radio first and then a ROM has caused issues like the phone not even recognizing there is a network for it. ( phone remains in emergency mode )
Edit:
Pretty sure my phone is bricked now... in a continuous boot up loop... BUT i can still access recovery
Ostyrion said:
Thanks so much for pinpointing the problem! Is there a fix to this?
Edit:
Pretty sure my phone is bricked now... in a continuous boot up loop... BUT i can still access recovery
Click to expand...
Click to collapse
Yes, those are the proper flashing instructions for CWM6.
It sounds like you have a soft brick. I think your best bet is to Odin back to stock. Have a look here:
http://forum.xda-developers.com/showthread.php?t=1858435
Good luck.
meekrawb said:
Yes, those are the proper flashing instructions for CWM6.
It sounds like you have a soft brick. I think your best bet is to Odin back to stock. Have a look here:
http://forum.xda-developers.com/showthread.php?t=1858435
Good luck.
Click to expand...
Click to collapse
You sir are a saving grace!
I'll try this at once!!
I have 2 questions though.
1. in regard to kernels. Do i need to do anything (aka change my kernel?) Or is the stock kernel suitable for 4.2.1?
2. If i cant boot into my phone to get to my SD card, how do i download and put files onto my phone?
Ostyrion said:
You sir are a saving grace!
I'll try this at once!!
I have 2 questions though.
1. in regard to kernels. Do i need to do anything (aka change my kernel?) Or is the stock kernel suitable for 4.2.1?
2. If i cant boot into my phone to get to my SD card, how do i download and put files onto my phone?
Click to expand...
Click to collapse
Stock kernel is just fine.
Odin will flash the stock OS to your phone from the computer. Make sure to read the Odin directions a few times before trying it because it could hard brick if something goes wrong.
meekrawb said:
Stock kernel is just fine.
Odin will flash the stock OS to your phone from the computer. Make sure to read the Odin directions a few times before trying it because it could hard brick if something goes wrong.
Click to expand...
Click to collapse
I'm trying to read through the thread you gave me but its kinda cluttered and its hard finding exactly where to start...pointers?
From the first post of that thread you will need
1. The prerequisites
-Odin
-Drivers
-Kies(dunno if this is mandatory but I guess it couldn't hurt.)
2. T-Mobile t989 uvlhi stock ROM(Odin)
You will need some type of zip software to extract the files from this.
3. Follow the steps under Installation - Odin installation(skip step 1)
After you get the stock ROM running you can install custom recovery and then flash your custom ROMs.
meekrawb said:
From the first post of that thread you will need
1. The prerequisites
-Odin
-Drivers
-Kies(dunno if this is mandatory but I guess it couldn't hurt.)
2. T-Mobile t989 uvlhi stock ROM(Odin)
You will need some type of zip software to extract the files from this.
3. Follow the steps under Installation - Odin installation(skip step 1)
After you get the stock ROM running you can install custom recovery and then flash your custom ROMs.
Click to expand...
Click to collapse
IT WORKS!!!! I LOVE YOU!! THANK YOU SO SO SO SO SO MUCH!!
THANK YOU THANK YOU THANK YOU!!
So now that I'm back on stock ROM, is my phone still rooted? Or do i need to reroot?
Edit: Downloaded a root checker. Looks like I need to reroot. Thank you again SOOOOO much!!!
Ostyrion said:
IT WORKS!!!! I LOVE YOU!! THANK YOU SO SO SO SO SO MUCH!!
THANK YOU THANK YOU THANK YOU!!
So now that I'm back on stock ROM, is my phone still rooted? Or do i need to reroot?
Click to expand...
Click to collapse
You are welcome. You are now unrooted so you have to download the recovery of your choice to the internal SD card and flash it from the stock recovery. After you reboot back into recovery you can flash a ROM and you will be rooted.
meekrawb said:
You are welcome. You are now unrooted so you have to download the recovery of your choice to the internal SD card and flash it from the stock recovery. After you reboot back into recovery you can flash a ROM and you will be rooted.
Click to expand...
Click to collapse
So in essence, once i have cwm/twrp on my phone, i have "root"?
Just to check:
1. download cwm recovery
2. via usb put onto phone.
3. reboot into recovery
4. flash cwm
5. restart phone
6. copy AOKP ROM onto phone
7. reboot into recovery
8. flash AOKP ROM?
Again, i cant thank you enough!
Ostyrion said:
So in essence, once i have cwm/twrp on my phone, i have "root"?
Just to check:
1. download cwm recovery
2. via usb put onto phone.
3. reboot into recovery
4. flash cwm
5. restart phone
6. copy AOKP ROM onto phone
7. reboot into recovery
8. flash AOKP ROM?
Again, i cant thank you enough!
Click to expand...
Click to collapse
That should do it. You won't be rooted until you install a custom ROM though(they come already rooted).
meekrawb said:
That should do it. You won't be rooted until you install a custom ROM though(they come already rooted).
Click to expand...
Click to collapse
Apparently stock recovery doesn't allow to install via internal SD card so I need odin to flash cwm dont i?
What boxes do i need checked besides the PDA checkbox?
Ostyrion said:
Apparently stock recovery doesn't allow to install via internal SD card so I need odin to flash cwm dont i?
What boxes do i need checked besides the PDA checkbox?
Click to expand...
Click to collapse
If you download the flashable zip from the first post here:
http://forum.xda-developers.com/showthread.php?p=30497342
you should be able to flash it from stock recovery. If it doesn't work I will have to look up how to install it with Odin.
meekrawb said:
If you download the flashable zip from the first post here:
http://forum.xda-developers.com/showthread.php?p=30497342
you should be able to flash it from stock recovery. If it doesn't work I will have to look up how to install it with Odin.
Click to expand...
Click to collapse
I actually got cwm 5.0.2.7 on my phone through odin. I just need root now to upgrade it to the most recent version.
I've been seeing busybox paired with superuser.
Do i need busybox? Or can i just flash superuser through cwm recovery 5.0.2.7?
Ostyrion said:
I actually got cwm 5.0.2.7 on my phone through odin. I just need root now to upgrade it to the most recent version.
I've been seeing busybox paired with superuser.
Do i need busybox? Or can i just flash superuser through cwm recovery 5.0.2.7?
Click to expand...
Click to collapse
Why do you need root? You should be able to just flash the newer cwm zip.
Here is a superuser zip that I used successfully on my t989:
meekrawb said:
Here is a superuser zip that I used successfully on my t989:
Click to expand...
Click to collapse
Thanks for the file!
I downloaded cwm from this site:
http://www.clockworkmod.com/rommanager
but it comes as an img file...and I dont seem to be able to flash that from recovery
Hi everyone.
I recently got a used Note 2. I've been doing a bit of reading in this section and just wanted to confirm a couple of things.
First off my phone's description:
Carrier: Sprint
Model Number: SPH-L900
Android Version: 4.3
Baseband Version: L900VPUBMK4
Kernel Version: 3.0.31-2106854 [email protected] #1 Mon Nov 11 20:33:03 KST 2013
Build Number: JSS15J.L900VPUBMK4
SE for Android Status: Enforcing SEPF_SPH-L900_4.3_0010
Hardware Version: L900.09
(1) Even though the phone came wiped of all previous data I would like to do a factory reset. Billard412's guide is mentioned several times. Is this the option to go with for my phone?
(2) The phone is not rooted at the moment. Should I use the CF-Auto Root method by Chainfire first and then proceed to install TWRP and then restore back to stock using Billard412's guide?
Thanks for your help in advance.
To start with you have the 100% KNOX on your phone so Billard412's back to stock will be the option you want to use.
You will need to download
TWRP recovery (recommended because billards zip works best with it)
Billards back to stock mc2 with counter reset
The root file located in billards thread
Prep steps
Backup everything you want from your internal sdcard (this will get wiped)
place billards rom and root files on your external sdcard
1. boot phone into download mode
2. use odin to flash twrp recovery (any version but 2.7) make sure you uncheck the reboot option in odin
3. once finished remove cable and battery
4. hold the recovery boot key sequence (vol up, home, and power keys) then insert battery (while holding keys)
5. once in recovery wipe everything
6. flash billards rom (do not wipe anything else after this step)
7. flash the root file
8. reboot and dont get worry when things get funky this is normal
9. the phone will take a bit to boot
10. now you have stock mc2 with root
11. install your recovery of choice (if flashing touchwiz 4.3 or aosp 4.4 roms use Philz 6.07.9) this can be done with odin or an image flashing app
12. now you can flash whatever rom you want
FYI -- when going from touchwiz 4.1x to 4.3 or aosp 4.4 you should format your internal sdcard. The newer roms use a different location for your internal sdcard and without proper formatting you will end up with issues (mostly random reboots and apps force closing) -- Same goes if you go from 4.3 TW/aosp 4.4 to 4.1x TW/4.3 or lower aosp
jlmancuso, thanks for the reply. Couple of things to clarify from your post:
- Regarding the Prep steps.
- I don't have anything on this phone yet so I don't think I need to back anything up. Even if if did the "Android system recovery <3e>" recovery menu does not have an option to back anything up
- Regarding using Odin to flash TWRP
- The 2.7 version to avoid is for TWRP correct? I went to TWRP's Sprint Note 2 page and I cannot seem to find a different version. Where should I get the version of TWRP that actually works?
- From the XDA page on Odin, which version should I use 3.09 or 1.85?
- All of the boxes must be unchecked including the reboot option? If not which ones need to be checked?
- I click on the "PDA" button to load the TWRP zip file correct?
- Regarding step 8:
- What do you mean "dont get worry when things get funky"? Funky as in the phone takes long to reboot or the screen flashes weird colors/patterns?
- Also, I came across Galaxy Note2 TOOLKIT V5.0.0 SPRINT thread. That one seems pretty easy to follow through. Would that option work for me given that I have the KNOX update?
Thanks again for your help.
Well, I've done a bit more reading into the Galaxy Note2 TOOLKIT V5.0.0 SPRINT thread and it seems that might be the way to go. Mark mentions the KNOX update in his changelog. I don't have the necessary posts to post a question in that thread so hopefully someone sees this that's familiar with that method. Does this method apply to a phone that has already undergone the KNOX update?
From what I can understand, Mark has made a recovery as well as a root tool. I bought this phone second hand so any warranty issues (e.g. flash counts, etc.) don't really apply to me. I'm just looking to get the phone to a clean state where I can start fresh and then add TWRP and Root. As far as the version of TWRP, Billard412 says (in post #604) that "Version of twrp doesn't matter as far as I know."
My second question is, using the Unified Toolkit, will i be able to restore my phone to stock and then root it with the least amount of problems?
roofus1218 said:
Well, I've done a bit more reading into the Galaxy Note2 TOOLKIT V5.0.0 SPRINT thread and it seems that might be the way to go. Mark mentions the KNOX update in his changelog. I don't have the necessary posts to post a question in that thread so hopefully someone sees this that's familiar with that method. Does this method apply to a phone that has already undergone the KNOX update?
From what I can understand, Mark has made a recovery as well as a root tool. I bought this phone second hand so any warranty issues (e.g. flash counts, etc.) don't really apply to me. I'm just looking to get the phone to a clean state where I can start fresh and then add TWRP and Root. As far as the version of TWRP, Billard412 says (in post #604) that "Version of twrp doesn't matter as far as I know."
My second question is, using the Unified Toolkit, will i be able to restore my phone to stock and then root it with the least amount of problems?
Click to expand...
Click to collapse
I belive your best option is billard412s thread. You are correct with your Odin steps. Flash TWRP and follow thread you should be golden
Awesome thanks a bunch!
As the title said, I just flashed a custom rom into my device ( CM11 kitkat 4.4.2)
Its the first time i root and flash my device
So now, goo manager told me that there is an update available for my device, i follow the instruction of it by downloading it
after that it pop up saying that my device need to have an open script recovery, (I searched youtube, they usually use twrp to update the CM custom ROM), so press yes and it started to download + install
There's a small pop up that saying I have installed twrp on my device, but when i press on reboot into recovery, it shows CWM recovery, even I try reboot into recovery by using ROM Manger.
How do I solve this ?
I just want to install TWRP and uninstall CWM as they said TWRP works better with CM version ?
and one small question, can i delete the zip file that i use to flash the ROM in my external sdcard, and the zip file that i have to use to update after flashing them or updating them ?
wk0308 said:
As the title said, I just flashed a custom rom into my device ( CM11 kitkat 4.4.2)
Its the first time i root and flash my device
So now, goo manager told me that there is an update available for my device, i follow the instruction of it by downloading it
after that it pop up saying that my device need to have an open script recovery, (I searched youtube, they usually use twrp to update the CM custom ROM), so press yes and it started to download + install
There's a small pop up that saying I have installed twrp on my device, but when i press on reboot into recovery, it shows CWM recovery, even I try reboot into recovery by using ROM Manger.
How do I solve this ?
I just want to install TWRP and uninstall CWM as they said TWRP works better with CM version ?
and one small question, can i delete the zip file that i use to flash the ROM in my external sdcard, and the zip file that i have to use to update after flashing them or updating them ?
Click to expand...
Click to collapse
Cause you need to reflash your recovery.If you downloaded a zip file boot in CWM and flash the recovery zip file.If you downloadeded .tar.md5 file you need to put your phone into download mode ,open odin on your laptop and flash the recovery file (you need to transfer the .tar.md5 file to your laptop).Well you shouldn't delete your current ROM zip file to be honest you should have atleast have one ROM zip file (with the appropriate add ons needed ) just incase you run into trouble you can always flash the ROM from scratch (incase you don't have a back up of it on your sd card) I always keep one touch wiz ROM and one CM11 ROM zip file along with zip files of philz touch and twrp recovery (i don't do nandroid backups-personal choice) on my sd card.
singhpratik87 said:
Cause you need to reflash your recovery.If you downloaded a zip file boot in CWM and flash the recovery zip file.If you downloadeded .tar.md5 file you need to put your phone into download mode ,open odin on your laptop and flash the recovery file (you need to transfer the .tar.md5 file to your laptop).Well you shouldn't delete your current ROM zip file to be honest you should have atleast have one ROM zip file (with the appropriate add ons needed ) just incase you run into trouble you can always flash the ROM from scratch (incase you don't have a back up of it on your sd card) I always keep one touch wiz ROM and one CM11 ROM zip file along with zip files of philz touch and twrp recovery (i don't do nandroid backups-personal choice) on my sd card.
Click to expand...
Click to collapse
Wow, so what i have to do is to boot into cwm and flash that recovery zip file ?
And so the twrp will replace cwm ?
wk0308 said:
Wow, so what i have to do is to boot into cwm and flash that recovery zip file ?
And so the twrp will replace cwm ?
Click to expand...
Click to collapse
Correct,that's how one replaces their existing recovery with another recovery.At end of flashing the zip file ,go back to main menu and click on "reboot recovery" ,You'll see your new recovery
singhpratik87 said:
Correct,that's how one replaces their existing recovery with another recovery.At end of flashing the zip file ,go back to main menu and click on "reboot recovery" ,You'll see your new recovery
Click to expand...
Click to collapse
Thanks will try it now
but not sure if it is a zip file or not hahaha
Cuz the file name end up with .img
its not a image right?
wk0308 said:
Thanks will try it now
but not sure if it is a zip file or not hahaha
Cuz the file name end up with .img
its not a image right?
Click to expand...
Click to collapse
This the goomanager link http://goo.im/devs/OpenRecovery/t03g scroll to the bottom and download 2.7.0.2.zip (img.tar is the ODIN file) ,I am not sure what .img file is never used that .But ya you need the .zip one
EDIT: You got GT N7100 right not 7105?just to be sure cause the recovery is different for 7105
singhpratik87 said:
This the goomanager linkscroll to the bottom and download 2.7.0.2.zip (img.tar is the ODIN file) ,I am not sure what .img file is never used that .But ya you need the .zip one
EDIT: You got GT N7100 right not 7105?just to be sure cause the recovery is different for 7105
Click to expand...
Click to collapse
Thanks you really helped me a lot
sorry for late reply as my replies are limited because im just new to here
By the way, one more question is is there anyway i can flash back to my stock rom but remain rooted?
and what if i want to unroot it
because i found this ROM quite buggy as in the camera app, i am a person that will take picture everyday, panaroma is quite important to me
i found this camera is very very very poor haha
furthermore, whenever in a skype call, i will hear nothing if i plugged in my earphone o.o
so i will probably flash back to stock rom but remain rooted is case of flashing other more stable rom