Develop Bugs

CWM 3.0.2.5 borked, can Heimdall help?

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.

Flashing ROMs

Hello everybody!
Firstly I'd like to apologize for posting a few threads here recently! I'll be picking up this device in under 2 weeks when I get paid and I'll be tinkering with it as soon as possible so I'd rather know what I'm doing now instead of waiting till I get the device and then start asking questions and getting help so...
I'm not a complete noob when it comes to Android phones. I've flashed both of my devices and messed around with other things along with ROM Porting etc so the HTC One V shouldn't be too much of a challenge/task for me to mess about with!
Basically, when I get the device I'll be using the Toolkit to unlock bootloader and install a recovery then flash the PROVISION ROM as it seems to be the best for me.
So when I open the Toolkit do I simply follow the instructions to unlock the Bootloader followed by flashing a Recovery (Which one is recommended? I've used Clockworkmod on my past devices) then the next option is flashing a Kernel, which one do I choose or can I just skip this part and reboot my device into recovery and start flashing? And will I need to flash the Superuser app via the Toolkit or are the ROMs pre-rooted?
The ROM which I want to flash (Provision) mentions something about flashing the boot.img in the zip folder before flashing the ROM, how do I go about flashing that or can I just flash the ROM folder with the boot.img in it and that's fine?
Finally, does this device have decent internal memory or will I need to use A2SD scripts and move my Dalvik to SD?
Any nice idiot-proof tutorial/help would be great.
Thanks.

I recommend cwm I find it more easy to use. But u may always try the other. flash the kernel inside the rom.zip or any other one that is prescribed by the dev(u will have to flash kernel from fastboot,u can't skip it as the rom won't boot without this step)how to flash is described in the link given below .most Roms are pre-rooted if not flash the superSU.zip from recovery.
I have accidentally thanked you enjoy!
See this for info regarding flashing-
http://forum.xda-developers.com/showthread.php?t=1996665

Try TWRP u will never switch back
Sent from my One V using xda premium

Thanks for the replies. I appreciate it.
I've created a folder on my desktop with the Toolkit in along with the Provision rom zip, the gapps and the boot file. Do I basically follow the toolkit then fastboot the boot.img then reboot into recovery and flash the rom and gapps then reboot and everythings fine? Also should I keep the boot.img inside the zip or should I remove it now?

no harm if you keep it
Sent from my One V

Use toolkit which is best way to all this type.of stuff
Sent from my HTC One V using xda premium

[Q] Ok, I did install CM 10 on Xperia S but I have some doubts

I started off by install unlocking bootlodaer, install CWM and then finally CM10.
But, when I was install CM10 via update.zip, I got some symlink error and phone just didn't boot & it always got hunged up at "SONY" logo screen. Clicking on Lolo of Sony more than 3 times was not helping either to get to CWM.
The way I solved this issue was by starting mobile in fastboot state and using recovery-nozomi file to flash it. May I know what this file did, because after that, I was able to enter CWM directly without doing any taps on Sony logo.
Someone please guess as to what might have happened? It's just a start & I've to do a lot of things from here on.

General is not for Questions. Post question on Q&A section.
And answering your question, I think you didn't flash CM10 Kernel. Isn't it? Stock kernel not work with CM10. You have to flash CM10 kernel in the package. Go HERE if you want more info about flashing kernel.

pharix said:
General is not for Questions. Post question on Q&A section.
And answering your question, I think you didn't flash CM10 Kernel. Isn't it? Stock kernel not work with CM10. You have to flash CM10 kernel in the package. Go HERE if you want more info about flashing kernel.
Click to expand...
Click to collapse
That was the thing, flashing the boot.img from CM10's zip fixed some random freezes that I was having. Why don't we flash those boot.imgs from the zip+CWM method itself? Is it like, it's not possible?

I think it is not possible to flash boot.img from cwm.
Sent from my LT28h using xda app-developers app

shadyabhi said:
That was the thing, flashing the boot.img from CM10's zip fixed some random freezes that I was having. Why don't we flash those boot.imgs from the zip+CWM method itself? Is it like, it's not possible?
Click to expand...
Click to collapse
Its not possible to flash boot.img from rom via cwm over stock kernel. Once you have a custom kernel, the recovery will automatically flash the kernel from zip the next you flash a different rom .
Sent from my Xperia S using xda premium

Need help installing kernel

So im pretty new to this but here is what im trying to do. I just got an asus nexus 7 2013 and i want to install it in the dash of my car. I plan to use a usb dac (dragonfly) and i want to be able to hook a hard drive up to it for media storage. So far ive rooted and backed up the tablet using the wugfresh NRT, and i want to try out this kernel http://forum.xda-developers.com/show....php?t=2389022 because it has usb charging and it can charge the device at the same time. But i have no idea how to install something like this and i couldnt find anything after i searched. Thanx.

That link isn't taking me anywhere...
Basically you just download the .zip file, copy it to your internal memory/sdcard (which is /sdcard), boot into your custom recovery, I would recommend wiping /cache and Dalvik (but some people say you don't have to), then selecting "Install" then browsing your /sdcard to find the zip, then Install...Reboot.

Alrite so i have no idea what you just told me too do, i tried to boot it up by holding the VOL down and power buttons. I went to custom recovery, but from there, i cant understand what commands im supposed to give the tablet that would enable it to bootup on the new rom. but i figured out that i can install a custom recovery with my wugfresh nexus root tool kit. But my problem is when i try to select the rom file that i want to use, It wont show an actual img file. When i go to the page to download the rom, all i get is an automatic download for a zip file. The NRT wont flash the zip file, and when i extract it, theres no image for the NRT to target. So how do i get this rom to be an IMG file or is there another way to do this. thanx.

You flash zips from the custom recovery on the phone. You flash imgs from fastboot on the computer.
If you have a custom recovery installed, you don't need a computer at all to flash a kernel (or a ROM). Just the custom recovery on your phone. Select the kernel zip and install it.

Oh boy. You sure you have a custom recovery?
My advice.
Install GooManager from Play Store.
Open and click on the three dots.
Install OpenRecovery Script.
Click the option for Reboot Recovery.
Install.
Navigate to the zip file.
Swipe to install.
You may want to wipe or whatever but up to you.
I mean this is the basis for everything and you don't know. I'd suggest doing more research before blasting away on the tablet and asking these types of questions. This is all very basic.
Good luck.
Sent from my Nexus 7 using xda app-developers app

i went with goo.im and installed the elemental IX kernel. the only thing wierd that happened was that it wouldnt let me install it if i checked the verify zip box, so i just didnt verify it. everything else looks like it worked fine. thanx.

[Q] Need a working s2w kernel for ViperX 4.1.1 that actually works.

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