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.
Related
Recently clockwork mod is shot for me, It won't do anything to put it simply.
I have searched these forums for 3 weeks trying to find a solution and thus far haven't come up with one. Odin however, works flawlessly. So my question is it possible to take a zip file that you flash via clockwork mod and make it Flashable via Odin instead?
although I am unsure of being able to package a tar from a zip I have a question for you. how are you flashing your cwm? if its through rom manager it won't stick. you need to odin a kernel packaged with cwm to work.
patrao_n said:
although I am unsure of being able to package a tar from a zip I have a question for you. how are you flashing your cwm? if its through rom manager it won't stick. you need to odin a kernel packaged with cwm to work.
Click to expand...
Click to collapse
Running Calk's Rom with his recovery that is pre-packaged, I have manually installed clockwork mod via Odin with no luck. Flashing a zip after just results in it hanging (Loads the boot animation and then turns off, or just doesn't load the boot animation at all.) Restoring a backup fixes it (Which leads me to believe its not flashing the files correctly)
oh ok gotcha. well I hope you get an answer soon
patrao_n said:
oh ok gotcha. well I hope you get an answer soon
Click to expand...
Click to collapse
If you have any other ideas as to what it might be please let me know, I've completely exhausted my ideas...
I would use this tar. its gunslinger. http://db.tt/XSVcu2it remember to flash it in pda section of odin let me know if it doesn't work k.
Autris said:
Recently clockwork mod is shot for me, It won't do anything to put it simply.
I have searched these forums for 3 weeks trying to find a solution and thus far haven't come up with one. Odin however, works flawlessly. So my question is it possible to take a zip file that you flash via clockwork mod and make it Flashable via Odin instead?
Click to expand...
Click to collapse
All you have to do is take the zImage out of the zip and use 7zip or similar to create a tar file. You should be able to flash that with Odin.
http://androidforums.com/behold-2-all-things-root/54424-creating-custom-roms-backups-odin.html
For all interested parties.
really good info thanks man
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!
My Google-fu is lacking tonight. Having built myself a new kernel, how do I flash it onto the phone? (either straight from the root commandline or in CWM - I don't really want to have to find a Windows machine for Odin). All the "how to flash a custom kernel" guides out there seem to assume you want to install a kernel that someone else has already packaged for you...
Secondly, if it all goes wrong and the kernel won't boot, am I right in thinking that CWM will still work and I can just recover my old image using nandroid?
Go here
http://forum.xda-developers.com/showthread.php?t=2067896
Download the kernel, open in 7zip or winrar, delete boot.img and replace with yours and flash away.
Sent from my SGH-I927 using xda premium
Excellent, thank you! I now have a kernel with CONFIG_USB_SEC_WHITELIST turned off so I can use any USB device with the phone.
Question, if you are mucking around with kernels and want to restore to stock without doing a full TWRP nandroid restore, can you just restore the boot partition?
Alternatively, how does one pull just the stock kernel (including ramdisk) from the factory image? In the past with other brands its been more convoluted e.g. with HTC I remember in addition to flashing the stock kernel in zip you had to push something in fastboot as well (the ramdisk). Unfortunately I can't find just the stock kernel file(s) in this forum hence asking if it can be pulled from the factory image
Thanks in advance
wintermute000 said:
Question, if you are mucking around with kernels and want to restore to stock without doing a full TWRP nandroid restore, can you just restore the boot partition?
Alternatively, how does one pull just the stock kernel (including ramdisk) from the factory image? In the past with other brands its been more convoluted e.g. with HTC I remember in addition to flashing the stock kernel in zip you had to push something in fastboot as well (the ramdisk). Unfortunately I can't find just the stock kernel file(s) in this forum hence asking if it can be pulled from the factory image
Thanks in advance
Click to expand...
Click to collapse
Hi
If you use Nexus Root Toolkit you can start the program and exists the option Launch and there exists restore stock kernel. I think it can solve your problem but first confirm.
There are stock JWR66N and JSS15J kernels attached to this post:
http://forum.xda-developers.com/showthread.php?t=2415497
boot into bootloader
fastboot flash boot boot.img
done
Need jss15q
Sent from my C6603 using Tapatalk 4
wintermute000 said:
Need jss15q
Sent from my C6603 using Tapatalk 4
Click to expand...
Click to collapse
It is there now.
http://forum.xda-developers.com/showthread.php?t=2415497
That are only .img files and not zImage files.
So only with PC or MAC flashable.
TDO said:
That are only .img files and not zImage files.
So only with PC or MAC flashable.
Click to expand...
Click to collapse
I am not sure what your idea of a zImage file is. These are compressed kernels with compressed root filesytems, which is what a zImage is.
You can flash these in fastboot over a PC or you can use dd to restore the partition while in android. Just make sure you know what you are doing in the latter case and don't overwrite the wrong partition or you can have big issues.
sfhub said:
I am not sure what your idea of a zImage file is. These are compressed kernels with compressed root filesytems, which is what a zImage is.
Click to expand...
Click to collapse
I know what a zImage is and this files can easily be flashed via Recovery (TWRP, ...)
If you know a similar method for .img files you can share it.
TDO said:
I know what a zImage is and this files can easily be flashed via Recovery (TWRP, ...)
If you know a similar method for .img files you can share it.
Click to expand...
Click to collapse
If you compare the md5 of a TWRP backup of the stock kernel against the system.img in my posts, they will be exactly the same. I didn't use TWRP, but used the same method as TWRP. Thus if your definition of a zImage is that it can easily be flashed via Recovery (TWRP, ...)
rename system.img to boot.emmc.win
copy into TWRP dated backup folder
restore in TWRP, check boot, uncheck everything else, disable MD5
If you want to do md5
md5 boot.emmc.win > boot.emmc.win.md5
echo " boot.emmc.win" >> boot.emmc.win.md5
I've already seen the list of kernels here, but none have been updated in the last one year, and some say they're discontinued. So far I've tried Alex's kernel from that list (marked as discontinued) and Lyapota's kernel that was recently updated, but in both cases after reboot my phone radios stay disconnected and in settings, Airplane mode is shown as 'turning off..', so I revert to the stock one. Is there a fix for the radio problem, or better still, can someone point me to a kernel that works with the latest ViperX?
Read the instructions a bit better ! Flash the boot.img and install the zip via the recovery. They all work, what you are experiencing is a user error !
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Yes, I'm on Lyapota's kernel and everything working very well.
I already have viper x 4.1.1 working with the stock kernel. All I'm doing is replacing the kernel with one of those that I mentioned. Does one need to reflash the whole ROM every time one changes the kernel?
What zip do I flash? There's only several .IMG files for each different kernel. Lyapota offers multiple different kernels in a single zip file, surely I'm not supposed to flash that? And there are no instructions, his English is terrible and I can't even figure out the features and differences between his various under and over clocked kernels.
Sent from my HTC One X using XDA Free mobile app
KaiserSnorezay said:
I already have viper x 4.1.1 working with the stock kernel. All I'm doing is replacing the kernel with one of those that I mentioned. Does one need to reflash the whole ROM every time one changes the kernel?
What zip do I flash? There's only several .IMG files for each different kernel. Lyapota offers multiple different kernels in a single zip file, surely I'm not supposed to flash that? And there are no instructions, his English is terrible and I can't even figure out the features and differences between his various under and over clocked kernels.
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
If you google "how to flash a custom kernel HTC one X" it will come up with several clear hits......
1: take out 1 of the desired boot.img files
2: fastboot flash it
3: install the downloaded .zip file via the custom recovery
4: reboot
Done.
I'm confused about downloaded zip here. Is this kernel or ROM zip? On those threads for kernels, they provide different kernels (img files) for different voltage settings and features within the same zip file and say to extract and flash the appropriate kernel using fastboot flash boot boot.img. There is no individual zip file for each kernel, and the only zip I have is of the whole ROM. Do I need to flash ROM again each time I change the kernel?
Sent from my HTC One X using XDA Free mobile app
Flash the desired boot.img and yes install the whole downloaded kernel.zip via the recovery. Do not flash the rom after this ! In the kernel threads they never speak about flashing the rom.zip at all.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
KaiserSnorezay said:
I already have viper x 4.1.1 working with the stock kernel. All I'm doing is replacing the kernel with one of those that I mentioned. Does one need to reflash the whole ROM every time one changes the kernel?
What zip do I flash? There's only several .IMG files for each different kernel. Lyapota offers multiple different kernels in a single zip file, surely I'm not supposed to flash that? And there are no instructions, his English is terrible and I can't even figure out the features and differences between his various under and over clocked kernels.
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
His English isn't terrible, it's more like yours isn't up to standard that's why
KaiserSnorezay said:
I already have viper x 4.1.1 working with the stock kernel. All I'm doing is replacing the kernel with one of those that I mentioned. Does one need to reflash the whole ROM every time one changes the kernel?
What zip do I flash? There's only several .IMG files for each different kernel. Lyapota offers multiple different kernels in a single zip file, surely I'm not supposed to flash that? And there are no instructions, his English is terrible and I can't even figure out the features and differences between his various under and over clocked kernels.
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
I can see how this can all seem confusing to a new comer. Fact of matter is, after 2 years of development and updates, devs usually stop posting basic info for new versions of release. They sort of assume the person who is reading have already read the same thing several times and knows exactly what to do.
So to explain plainly:
Kernel is comprising of 2 parts. The img file and "modules". On most HTC phones, you cannot flash BOOT partition from phone itself (done with fastboot boot bootfilename.img). Remember also that you cannot flash MODULES from fastboot, so you have to go into recovery after flashing new boot.
1. Download the kernel you want. It will be in 1 zip file. Make 1 copy of this file on your PHONE and 1 copy on PC.
2. Extract the boot.img file (whichever version of kernel you prefer) ON YOUR PC. Flash this from PC using fastboot commands. Doing this will update kernel in BOOT partition.
3. Now enter custom recovery, use Install option and browse to the zip file obtained in step 1. Flashing this in recovery will copy "modules" in SYSTEM partition.
Doing step 2 only (without step 3), _may_ leave you with a working device that cannot connect to wifi or get phone signals. Doing only step 3 will usually leave unstable phone.
asestar said:
I can see how this can all seem confusing to a new comer. Fact of matter is, after 2 years of development and updates, devs usually stop posting basic info for new versions of release. They sort of assume the person who is reading have already read the same thing several times and knows exactly what to do.
So to explain plainly:
Kernel is comprising of 2 parts. The img file and "modules". On most HTC phones, you cannot flash BOOT partition from phone itself (done with fastboot boot bootfilename.img). Remember also that you cannot flash MODULES from fastboot, so you have to go into recovery after flashing new boot.
1. Download the kernel you want. It will be in 1 zip file. Make 1 copy of this file on your PHONE and 1 copy on PC.
2. Extract the boot.img file (whichever version of kernel you prefer) ON YOUR PC. Flash this from PC using fastboot commands. Doing this will update kernel in BOOT partition.
3. Now enter custom recovery, use Install option and browse to the zip file obtained in step 1. Flashing this in recovery will copy "modules" in SYSTEM partition.
Doing step 2 only (without step 3), _may_ leave you with a working device that cannot connect to wifi or get phone signals. Doing only step 3 will usually leave unstable phone.
Click to expand...
Click to collapse
Good explanation. Had the exact problem as the TC. Thanks
Anyway, I have three additional questions.
1. Do I have to do the exact process every time after I flash another ROM?
2. This kernel apparently works well with MIUI?
3. How do I change to another (non-lyapota's) kernel?
Many thanks