So I know we need CWM recovery to flash any custom roms easily so I threw this recovery together.
It is flashed in the PDA section of Odin and includes our EG04 kernel.
Credits- Imnuts for the recovery.bin
http://dl.dropbox.com/u/64301631/GBRecovery.tar.md5
Disclaimer - I am not responsible for anything that happens ever! :fingers-crossed:
Flash and enjoy!
-Justin
this is imnuts' ec09 recovery with eg04 kernel, correct?
just to be clear....
non the less, thanks!
Yes sir! Imnuts' recovery and the EG04 kernel.
Thumbs up
Sent from my SPH-M580BST using Tapatalk 2
Related
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.
while trying many cusOMS RomS ANd FLAshable ZiPS ,Came aCRoss TWo TERMS Flash BY cwm RecOVeRy or sTOck cwM Wats THE Difference betwen THE two Sorry FOR a A NOOB quESTion but WAS very Anxious to KNow tHE DiFereNCE......THANKS IN ADVANCE
custom roms are modified versions of your current stock rom to make it beautiful and faster.
flashable zips are of 2 types:
1. They are made for updating/adding something in your current rom.
2. Its a file format which lets you to install things using cwm. It can be a rom itself too!
hell_lock said:
custom roms are modified versions of your current stock rom to make it beautiful and faster.
flashable zips are of 2 types:
1. They are made for updating/adding something in your current rom.
2. Its a file format which lets you to install things using cwm. It can be a rom itself too!
Click to expand...
Click to collapse
i want to ask wat is difference if we flash a rom using cwm or using stock recovery
talwarrokzz said:
i want to ask wat is difference if we flash a rom using cwm or using stock recovery
Click to expand...
Click to collapse
cwm has more options than the stock one so using cwm is preferable
hell_lock said:
cwm has more options than the stock one so using cwm is preferable
Click to expand...
Click to collapse
your answers are good but still cant fullfill my requirements (sorry if rude)
wanted to ask why some roms only prefer cwm recovery not stock and why only cwm is used to replace boot image of our phone
hell_lock said:
cwm has more options than the stock one so using cwm is preferable
Click to expand...
Click to collapse
CWM has more options and very simple to understand and use!
STOCK=less option.... hard to use... some times its cause a boot loop!
talwarrokzz said:
your answers are good but still cant fullfill my requirements (sorry if rude)
wanted to ask why some roms only prefer cwm recovery not stock and why only cwm is used to replace boot image of our phone
Click to expand...
Click to collapse
u can flash a rom from stock recovery too but as I said above, it is recommended to use so that u can restore ur phone if something goes wrong. Wen i tried to flash boot.img frm stock recovery it gave an error but wen u flash it from cwm it is successful . Any more doubts or are you still unsatisfied? ASK MORE!
hell_lock said:
u can flash a rom from stock recovery too but as I said above, it is recommended to use so that u can restore ur phone if something goes wrong. Wen i tried to flash boot.img frm stock recovery it gave an error but wen u flash it from cwm it is successful . Any more doubts or are you still unsatisfied? ASK MORE!
Click to expand...
Click to collapse
are you mad?
PwN.CraZyTagZ said:
are you mad?
Click to expand...
Click to collapse
Yes I am!!
its depends on scripting... stock recovery runs only amend scripting but cwm 3.0 or later edify scrpiting... and it has so many options then stock... one notable option and frequently using option is dalvik cache wipe... this is y most of em prefer cwm...
I GUESS THIS IS THE ANSWER... BUT IM NOT SURE ABOUT... GOOGLE IT FOR MORE INFO... I READ IT SOMEWHERE ONCE UPON A TIME... SO I FORGET SOME OF THE THINGS...
stock recovery require your zip to be signed for security reason. cmw is not. signing itself is simple process that only need few second, but once you signing your zip you can't change it's content. you must resign your zip if you do. that's why some people prefer cmw, because you can easily change zip content with regular archive manager without resign.
irfanbagus said:
stock recovery require your zip to be signed for security reason. cmw is not. signing itself is simple process that only need few second, but once you signing your zip you can't change it's content. you must resign your zip if you do. that's why some people prefer cmw, because you can easily change zip content with regular archive manager without resign.
Click to expand...
Click to collapse
Yes friend u r right............
Sent from my GT-S6102 using xda premium
Let's get to your qeury . . . Flashing via stock or CWM
With CWM Recovery you can:
Flash boot.img (kernel)
Flash Custom ROMS
Flash .zips without resinging packages
Choose what partition to be mounted during flash
With stock:
Flash boot.img (kernel) -but most kernel are ment to be flashed via CWM as it has a higher chance of success and less likely to cause bootloops
Flash Custom ROMS - but some ROMS use scripts that are NOT SUPPORTED by stock recovery
Flash .zips but requires zips to be signed and resigned if there are modifications on the package
CarlDeanCatabay said:
...
With stock:
Flash boot.img (kernel) -but most kernel are ment to be flashed via CWM as it has a higher chance of success and less likely to cause bootloops
Flash Custom ROMS - but some ROMS use scripts that are NOT SUPPORTED by stock recovery
...
Click to expand...
Click to collapse
that's not stock recovery problem, but custom rom problem. a lot of custom rom have poorly written (or generated) updater-script. rom dev put a lot of work on making his/her rom looks good, but give very small attention to installation process. some rom event try to mount /dev/stl19 to /system in instalation process. that partition not exist in sgy. and updater-script not depend to which recovery that you use. it's depend to updater-binary inside your zip file.
Hi guys,
I have searching the forums before posting but I can't find a definitive answer to my queries.
Anyway here goes.
I have a rooted Galaxy Note 2 N7100. I want to flash Android Revolution 9.1 but don't want to have a custom recovery on my phone.
I was looking to use Mobile Odin to flash the ROM. Is this possible?
Also I haven't used AROMA before, does the AROMA installer load up when you begin flashing the ROM?
Thanks and sorry if this is such an obvious question.
Cheers
Paul
If you mean you want to flash custom rom in flashable zip then do this
Copy flashable zip to sd card (int/ext)
Open mobile Odin
Select ota/update zip
Point to zip you have copied
Flash.
Sent from my GT-N7100 using xda premium
Thanks.
Yeah this is what I was going to do but wasn't sure if all custom roms were compatible with mobile odin.
Iassume I can then to a full wipe inside aroma before the actual flashing takes place?
Cheers
Paul
I recommend also having a custom recovery for at least making nandroid back ups. ..I too commonly use mobile Odin to flash roms, kernels and zips
scribbled from my note 2 (N7100)
Thanks.
I have used cmw before. Is that the best recovery to use? Is the touch version decent?
I have reset the binary counter one as i used chainfires rooting through odin.
Do i have to reset it everytime i boot to recovery if its a custom recovery?
Final question. Is it safe to use rom manager to flash recovery?
Thanks for your help sorry for all the questions.
Sent from my GT-N7100 using Tapatalk 2
- i apologize in advance if this is a stupid question, its driving me nuts.
I downloaded the stable cm10.1.0 RC1 ROM and the zip file only had 3 files (META-INF, system, and boot(.iso) )
My question is, how does one flash this using odin? Just wanted to make sure, i dont want to brick my phone.
dont unzip it. it wont flash in odin. you must be rooted and have a custom recovery (twrp or cwm) installed.
check out the link in my signature.
xBeerdroiDx said:
dont unzip it. it wont flash in odin. you must be rooted and have a custom recovery (twrp or cwm) installed.
check out the link in my signature.
Click to expand...
Click to collapse
Haha i thought it had to be flashed with CWM.
Thanks alot!
Sorry for the noob question.
I have upgraded my 5X to 7.0 and flashed a custom recovery and kernel. Everything went fine but I would like to try other kernels. A lot of the custom kernels say they should only be flashed on the original stock kernel. Where can I download the stock kernel and is it as straight forward as flashing the custom builds?
TIA
purpse said:
Sorry for the noob question.
I have upgraded my 5X to 7.0 and flashed a custom recovery and kernel. Everything went fine but I would like to try other kernels. A lot of the custom kernels say they should only be flashed on the original stock kernel. Where can I download the stock kernel and is it as straight forward as flashing the custom builds?
TIA
Click to expand...
Click to collapse
In TWRP, backup only boot.img and name it appropriately. Now flash your custom kernel. Each time you want to switch custom kernels while on the stock rom, reflash that boot.img.
To switch custom kernels while on custom roms, dirty flash your rom then flash the custom kernel. Dirty flashing (no wipe) restores the boot.img that ships with the custom rom.
Sent from my Nexus 5X using Tapatalk
Thanks. Do I flash kernel followed boot.img or other way round ir or does it not matter?
Sorry I read your post wrong. I didn't backup boot while on stock so I will need to go back to stock everything first
purpse said:
Sorry I read your post wrong. I didn't backup boot while on stock so I will need to go back to stock everything first
Click to expand...
Click to collapse
Or download the factory image from Google and pull the boot.img from the zip.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Or download the factory image from Google and pull the boot.img from the zip.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Hmm, I just did this as well.
With ElementalX I was stuck on the android loading screen (bouncing bubbles)
Now after flashing boot.img from google, I"m stuck on the black "Google"
derrickl1990 said:
Hmm, I just did this as well.
With ElementalX I was stuck on the android loading screen (bouncing bubbles)
Now after flashing boot.img from google, I"m stuck on the black "Google"
Click to expand...
Click to collapse
Try flashing the boot and system image.
Sent from my Nexus 5X using Tapatalk