Related
I was hoping some of the kernel devs can help me with a quick question. I am familiar with unpacking and repacking boot.imgs for the Droid but not for the Evo, I usually use the method found here. Is there an alternate method or even some perl scripts that will make the job as easy as it is for the Droid? Note: I am not trying to compile a boot.img, I just want to be able to edit the ramdisk of existing ones. Thanks in advance!
BuglessPete said:
I was hoping some of the kernel devs can help me with a quick question. I am familiar with unpacking and repacking boot.imgs for the Droid but not for the Evo, I usually use the method found here. Is there an alternate method or even some perl scripts that will make the job as easy as it is for the Droid? Note: I am not trying to compile a boot.img, I just want to be able to edit the ramdisk of existing ones. Thanks in advance!
Click to expand...
Click to collapse
reading through the tutorial you linked to, i see perl scripts and directions. is there a certain part of that tutorial you've used on the EVO and have had trouble or its resulted in some kind of error? guess i didn't catch what isn't working for you?
edit: reviewing the tutorial again, i have been wondering which partitions are which on our phone? boot mtd2/3 ? recovery mtd2/3? i know system is mtd4 and data is mtd5 ...
once i know which partition for sure is boot, it might be worth while for me to grab the kernel and post up the stock ramdisk as a starting point for all those looking to do simple kernel mod'n ...
Not sure why this got moved out of development section, as it is related to developing a boot.img although it was a question.
I used the unpack perl script and it threw an error. I will also try the split script when I get off work.
Sorry to resurrect a dead topic, but I'm looking into this as well, and I haven't been able to modify a ramdisk successfully (I'm basically looking to set ro.secure=0 in default.prop). I typically use the same procedure as Pete outlined in the link, but using that for the EVO results in a hang at the bootscreen. (the white HTC EVO 4G screen seen on boot) Any help would be appreciated.
Resurrecting this topic once again.
ADB functionality is broken in Sense FroYo roms, maybe all froyo roms. I can communicate appropriately through fastboot and through ADB in Recovery, but not when running.
The /sbin/adbd process isn't running like it is on other ROMS, such as eclair and gingerbread.
Following this link:
http://code.google.com/p/android/issues/detail?id=9437
I found that some nexus one devs had the same issue, and had to replace the adbd process on the ramdisk with one from another build that worked in froyo.
Following this guide that everyone links to:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I was not able to use the included unpack/repack perl scripts without modifying them. It appears that the Evo has another file at the end and that script wasn't meant to handle that. Others commented out that line that kills it, I did so, but apparently that script doesn't grab the header appropriately, and the repack doesn't work appropriately for another. I get the white boot screen and it stays indefinitely.
I took the Boot.img and went through a hex editor to do it manually, and wasn't able to get the ramdisk to unzip correctly.
I'm at the end of my rope, and need someone else who's much smarter than I am to assist in what steps to take next.
I am developing a new app, and desperately need to have ADB working inside FroYo. I would run CM7, but it doesn't work right all the time, and has bad battery life for me. I use my phone for business too, so it all has to be stable.
Any ideas? I have lots of this stuff available as I've been working on it for the past couple days, so I can post links and the like to help bring anyone up to speed with what I've done. Thanks a crap-ton in advance. If you can help me get this working, I will send you a donation!
Also, this will fix ADB in all Froyo roms too, so you'd be doing the community a great favor as well.
-Nathan
kmartburrito said:
Resurrecting this topic once again.
ADB functionality is broken in Sense FroYo roms, maybe all froyo roms. I can communicate appropriately through fastboot and through ADB in Recovery, but not when running.
The /sbin/adbd process isn't running like it is on other ROMS, such as eclair and gingerbread.
Following this link:
http://code.google.com/p/android/issues/detail?id=9437
I found that some nexus one devs had the same issue, and had to replace the adbd process on the ramdisk with one from another build that worked in froyo.
Following this guide that everyone links to:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I was not able to use the included unpack/repack perl scripts without modifying them. It appears that the Evo has another file at the end and that script wasn't meant to handle that. Others commented out that line that kills it, I did so, but apparently that script doesn't grab the header appropriately, and the repack doesn't work appropriately for another. I get the white boot screen and it stays indefinitely.
I took the Boot.img and went through a hex editor to do it manually, and wasn't able to get the ramdisk to unzip correctly.
I'm at the end of my rope, and need someone else who's much smarter than I am to assist in what steps to take next.
I am developing a new app, and desperately need to have ADB working inside FroYo. I would run CM7, but it doesn't work right all the time, and has bad battery life for me. I use my phone for business too, so it all has to be stable.
Any ideas? I have lots of this stuff available as I've been working on it for the past couple days, so I can post links and the like to help bring anyone up to speed with what I've done. Thanks a crap-ton in advance. If you can help me get this working, I will send you a donation!
Also, this will fix ADB in all Froyo roms too, so you'd be doing the community a great favor as well.
-Nathan
Click to expand...
Click to collapse
Adb does work in sense froyo roms. It works on mine and I nandroid between my daily sense rom and my dev sense rom when I need to. I prefer to use adb through recovery but I have successfully adb pulled and pushed com.htc.resources from the framework while my device was running just last night. I have also not changed the adb file in the ramdisk (even though I could if I wanted to) so I doubt adb not working in sense roms is the issue unless the rom maker did in fact mess with the ramdisk and inadvertently messed something up.
lovethyEVO said:
Adb does work in sense froyo roms. It works on mine and I nandroid between my daily sense rom and my dev sense rom when I need to. I prefer to use adb through recovery but I have successfully adb pulled and pushed com.htc.resources from the framework while my device was running just last night. I have also not changed the adb file in the ramdisk (even though I could if I wanted to) so I doubt adb not working in sense roms is the issue unless the rom maker did in fact mess with the ramdisk and inadvertently messed something up.
Click to expand...
Click to collapse
It's not working for me on Fresh 3.5, Evio 1.8, or Mik's Z rom that was just released. I can go back to my PC36IMG.zip (eclair) or CM7, and it works just fine.
I've tried stock and custom kernels, to no avail. I'm absolutely NOT the only person with this issue. As you can see in the post above, Nexus one users are having the same problem, as are tablet owners with Tegra 2 chipsets, etc.
So, let me ask you, what ROM are you using? Is that the only ROM you've used since upgrading from Eclair?
I am at a loss for why this isn't working. As I said before, the /sbin/adbd process is NOT running, and I get a segmentation fault when attempting to launch it. It works fine on CM7 and Eclair, but NOT froyo. Not brand new, unaltered ROM installs, nothing. Whatever it is, the only thing in common is Sense and FroYo.
Thanks for responding, I think at this point I just need people to provide other things to look at that I haven't thought of. I'd still like to learn how to unpack and repack though, it could be a last resort.
kmartburrito said:
It's not working for me on Fresh 3.5, Evio 1.8, or Mik's Z rom that was just released. I can go back to my PC36IMG.zip (eclair) or CM7, and it works just fine.
I've tried stock and custom kernels, to no avail. I'm absolutely NOT the only person with this issue. As you can see in the post above, Nexus one users are having the same problem, as are tablet owners with Tegra 2 chipsets, etc.
So, let me ask you, what ROM are you using? Is that the only ROM you've used since upgrading from Eclair?
I am at a loss for why this isn't working. As I said before, the /sbin/adbd process is NOT running, and I get a segmentation fault when attempting to launch it. It works fine on CM7 and Eclair, but NOT froyo. Not brand new, unaltered ROM installs, nothing. Whatever it is, the only thing in common is Sense and FroYo.
Thanks for responding, I think at this point I just need people to provide other things to look at that I haven't thought of. I'd still like to learn how to unpack and repack though, it could be a last resort.
Click to expand...
Click to collapse
For my daily I use a rom based on miks eng base that I rooted and edited myself. For my dev rom I use joeykrims odexed rom that I deodexed. I also use a barebones 3.70 taken directly from the ruu, rooted and edited myself as well as deodexed it.
My two dev roms provide me with at least some sort of variables since joeykrim adds some extras to his rom.
In all three roms, the only thing I changed in the ramdisk is the kernel I compile and use (htc15 compiled to have sbc, havs, undervolt, etc.).
It could be (possible though unlikely since others do have success with adb on the roms you mention) that the ramdisk may have been edited in a way that prevents adb from starting in the init files.
Again just last night, both on my replacement evo and my wifes evo (she runs what I put on her evo which is usually a more polished version of mine) I used adb while the devices were running to pull some system apps and do some editing and then pushed them back. These are both sense based 3.70 roms using the same kernel.
Your situation is puzzling me at the moment since you said it works fine on cm7 and eclair but not on any sense based froyo roms. I would have drawn the same conclusion but since I personally can use adb on a sense based froyo rom I have to think the problem lies somewhere else and not solely on froyo. I'll try to duplicate this situation though I don't think I can without seeing what your device looks like.
This is my first post and I was wondering if anyone can help.
I have an incredible, 2.2, rooted, with Rom Manager. I flashed the lastest recovery through Rom Manager but when I try to boot into recovery the screen stays black with a thin white line on both sides. I had some backups from another Dinc I had and took a chance at a restore from one of my older Roms. Although the screen stayed black it did load the backup so my recovery appears to be working fine only I can't see it.
Doing this before I am scared if I load a bad rom or something and get locked up I won't be able to see the recovery to restore my backups. I have tried older recoveries through Rom Manager with the same problem however when I flash RA_GNM Recovery v1.7.6 it works perfectly. Only problem is Rom Manager won't use that.
Any suggestions would be greatly appreciated.
Search for slcd recovery.
Sent from my ADR6300 using XDA App
ok now I am really confused. I research the slcd and not quite sure what I have or looking at. How do I know? My old Dinc was literally only about a month older than my previous one. Can you give me a brief "Dumbed Down" version of what exactly this is?
Sorry to be such a newbie.
mmjets said:
ok now I am really confused. I research the slcd and not quite sure what I have or looking at. How do I know? My old Dinc was literally only about a month older than my previous one. Can you give me a brief "Dumbed Down" version of what exactly this is?
Sorry to be such a newbie.
Click to expand...
Click to collapse
From what you're describing, your phone has a slcd screen, not amoled. As such, you're going to have a few issues here and there with recoveries as well as ROMS (due to your hardware not being supported by the included kernel). Search the forums for slcd and you'll see suitable workarounds for this.
To see what screen you have... Menu > Settings > About Phone > Hardware Version. If yours is 003, you have a SLCD screen.
Anyone who has the.new guy Rom ..is there a way to get the HTC pot penguin to as my boot image. That penguin is great lol
Sent from my ADR6300 using XDA App
Just incase anyone is having this problem I did find a site with a fix. Download the file, change the name and flash through hboot. It has worked for me and now I can get into recovery. Here is the link:
**Sorry the site wouldn't allow me to post the link***
Only problems I have now and I am hoping someone can help is that I can't seem to install any custom roms that don't have sense. When installing MIUI or CyanogenMod, etc I get locked up on the white HTC screen.
Anyone know a solution?
http://www.incredibleforum.com/foru...nly-see-black-screen-white-bars-recovery.html
That has the custom recovery you need for an slcd screen. I used that exact dl link to get the image. Then i used the unrevoked 3.21 tool to set it to flash a custom recovery then let the tool run. All went flawlessly
*Edit sorry i didn't see you fixed it. As far as cyanogen mod goes, I know it doesn't work with slcd screened incs because we have different display drivers. I believe that is true for all aosp roms. If you want a vanilla feel go with skyraider vanilla 3.0. It works perfectly for me
Thanks for posting that link and the help. I will keep checking to see if a solutions for slcd screens comes around so that I can install some other roms.
I just hate that I thought I upgraded my inc and as it turns out it was probably a downgrade.
To my understanding, I believe all roms work except aosp roms. I remember reading somewhere (but don't remember where) that they were working on a fix. So maybe it'll come before you know it
Koush's test #2 kernel works fine and will boot aosp on my Slcd.
Just wanted to let you know I found a way to make MIUI and cyanogen work on a slcd Dinc. I found the fix in one of the forums so I don't want to take any credit for it but it worked for me so I wanted to pass that info along to anyone else having the same issue.
I downloaded the Koush test kernel from Rom Manager, then I flashed the MIUI rom. Once flashed it gets stuck on the white HTC screen. I pull the battery, go to recovery, and then open zip from SD card. I find the Koush kernel, install, and reboot and it has worked for everything I have tried so far (MIUI and Cyanogen).
Hope that helps someone.
mmjets said:
Just wanted to let you know I found a way to make MIUI and cyanogen work on a slcd Dinc. I found the fix in one of the forums so I don't want to take any credit for it but it worked for me so I wanted to pass that info along to anyone else having the same issue.
I downloaded the Koush test kernel from Rom Manager, then I flashed the MIUI rom. Once flashed it gets stuck on the white HTC screen. I pull the battery, go to recovery, and then open zip from SD card. I find the Koush kernel, install, and reboot and it has worked for everything I have tried so far (MIUI and Cyanogen).
Hope that helps someone.
Click to expand...
Click to collapse
Really? My post above says that.
Your kidding right?? i didn't see your post as it was on page two so my apologies. I didn't mean to steal any of your credit!!! lol. I am just trying to help others out.
Is anyone else still having these problems?
I can't seem to ever complete a function in CWM3. I've flashed it through RM wiping any previous recoveries; I've installed from hboot, even tried using several different flash cards, but still no luck.
CWM3 will stop responding completely and the only way out is to yank the battery.
Anybody have any ideas?
I know one answer is "Use 2.5.x.x," but is there anything else?
Thanks for your help!
I had a lot of issues with CWM3.0.0.5 until I took someones advice and checked the "Erase Recovery" option in setting. Since then I have been running great, no issues.
Yea, I've done that too....still same errors.
Thanks for the suggestion though! I appreciate the help.
I personally never had any issues with CWM 3. But since so many other people have had a lot of trouble with it, I decided to install the Amon RA recovery for our devices. My favorite capability of it is installing zips from /emmc.
As for CWM 3, I have to ask when you installed it via HBOOT did you make sure to check the MD5 sum? At this point CWM 3 gives you no added functionality...maybe it is best to stick with 2.5.0.5 or 2.5.1.2 until 3 works well. Seems like it has a multitude of bugs at this point.
The new CWM is giving people fits because koush tweaked it to 'force?' developers to use an updated/different coding method in/for their ROMs, in anticipation of gingerbread. He noted this change on his twitter and his site.
Tremendous respect for koush - but this, imho, is hurting the user community more than forcing devs to adapt new methodoligies.
I'm staying on 2.x.
my $0.02
I'm also getting issues with CWM3 and have tried every suggestion I have read (install via HBOOT, check md5, set "erase recovery," install stock recovery then install CWM3 over it) and none of them have worked. I can get into CWM3 and navigate for a few seconds but it eventually completely freezes and requires a battery pull. One trigger I noticed for my CWM3 problems is that touching the optical trackpad while in recovery will occasionally cause my screen to briefly spazz (artifacting and diagonal white lines) and then my phone will reboot. 2.5.1.2 works fine but I would still like to upgrade for future edify scripts.
I have an S-off, amoled Dinc.
Edit: And I have tried updating to CWM3 with 3 different microSD cards (2 2gb Samsungs and a 1gb Sandisk)
Sterlic,.sounds like the exact same problems I'm having. Glad to know its not just me.
I might give Amon a try, does it use the edify script too? I don't know anything about that recovery or even where to look to find info on it.
Thanks everyone for your help.
Sent from my Droid Ostentatious...
I had quite a few problems with 3.0.0.5 initially. Lot's of cursing and hair pulling. Since then I have done a complete wipe and reinstall of CM7 RC1 up to #5 and CMR 3.0.0.5. Fingers crossed...everything seems to be working at the moment...
But I don't think I will be able to nandroid back to any of my older sense ROMs anymore. I believe I read this somewhere. I can't remember if there are any other limitations...
So I tried installing Both Lou's Kernel #6 and 7. As well as Ziggy's latest beta. I cleared the Dalvik Cache as well. I still cannot seem to figure out what the issue is.
I'm running Myn's Warm 2.2 the latest release.
I have the newer Incredible with the SLCD screen but I didn't think the touch sensor would have changed at all...
I hope somebody can help me clear this up.
Thanks in advance.
What version of CWM do you have? It requires a certain version. I think it's 2.5.0.5, and it has to be unmodded (no fast scrolling, etc.).
I recently upgraded to 3.0.0.5. I hadn't had any problems with 3.0.0.5. I'll try downgrading and trying again.
Chad has a modded clockwork out that supposedly fixes it. I've never tried it personally.
So I couldn't get chads version of Rom manager to download clockwork 2.5.0.5 and I can't seem to find a 2.5.0.5 version of clockwork anywhere. I tried flashing via amon ra 1.81 for incredible but that didn't seem to work either. What exactly is the issue here? I'm not understanding how the clockwork version would interfere with installing a kernel.
Thanks a ton guys.
So I finally found a 2.5.0.5 version of clockwork, however it doesn't support SLCD screens (Just get the black screen and white lines). On top of that I booted up the phone and the touch screen wouldn't respond at all. Couldn't even unlock the phone. I had to install the SD card in my old enV 2 and rename and move the Amon Ra Recovery back to the root of the SD card and reinstall.
I'm gonna try to figure out where I can find Chad's modded version of clockwork, but this is getting very frustrating.
This has turned into an ordeal. AmonRa didn't fix my touch screen. I tried restoring an AmonRa backup but it errored and told me to restore using adb commands. I am currently at my parents house in and don't have access to ADB here. This computer is terrible. I won't be back to my house until Monday.
I reflashed Clockwork 3.0.0.5 and now am currently restoring a backup. I hope this fixes the issue...
So I found a version of clockwork 2.5.0.5 that was modified to work with SLCD, (Doug Piston's Website) and still no dice. Only 2 touches registering. I have no idea what else to try...
Bump. Im really stumped here guys. Thanks for the help.
Sent from my ADR6300 using XDA App
I use clockwork 3.7 & get 5 on chads & 10 on tiamat. Amoled tho
sent from dinc
Try opening term emulator: and type su, then cat /sys/android_touch/vendor and put the output here:
If it's AMTEL_x004F_x0016, then 2 touch is likely the limit. During all the testing that went on by Chad, I don't think anyone with SLCD or AMOLED that had the x004f_x0016 panel got more than 2. I guess they figured 2 was enough for that panel. It made no difference what version of cwm or which kernel was used. They all got 2.
If it's not what was mentioned ^^ then you can probably keep messing around with cwm versions and kernels until you find some magic combo that works.
Thanks hamchacha. I do have that panel, that's unfortunate. Not the end of the world though...
Thanks again.
LakesideWiseman said:
Thanks hamchacha. I do have that panel, that's unfortunate. Not the end of the world though...
Thanks again.
Click to expand...
Click to collapse
Sure thing. I've got it as well. I went to the Amtel website and tried to look it up, but they don't use those numbers on the site or if they do they're in some other format I can't figure out. They do , however, talk about 5-10 touch panels, and 2-touch and 1-touch panels all in the 'cellphone' (or so it appears) section, and those panel pictures all resemble the ones on our phones.
I know you can buy another one from some reseller if this is a big deal for some reason, but I'm not sure if that reseller (I could find them again) will tell you which you're getting. I think they were 30-40 bucks. I'll see if I can dig up the link. Getting it all apart might not be too simple as well.
It was for a MIDI controller. Which someone wrote an app that turns your phone into a wireless one. If you're unfamiliar, a MIDI controller allows you to program and change values in music production software with faders or different input methods on my phone.
However it is a fairly small workspace for sure a use. Because of this a plan on getting a tablet very soon. So i think it would be a waste to buy a new panel.
Thanks for all the hard work on this. Can never learn enough about my phone.
I have a rooted HTC Desire with the Amethyst (http://forum.xda-developers.com/showthread.php?t=878901) ROM installed. The phone has busybox etc, but when I try to set up swap either using Swapper2 or "swapon" directly from the Terminal I get an error saying that the functio is not implemented. This happens when I use a swap file, or a swap partition.
How can I get this to work? Is it a problem with the ROM? If so, could anyone point me in the direction of a ROM that does support this.
Thanks in advance.
You need a kernel that supports it
OK, so I guess I should switch to the Cyanogen one then?
Does anyone know of any AOSP Gingerbread compatible kernels with Swap support?
Sent from my HTC Desire using XDA App
+1
I need one too
bump I need a desire Rom that supports swap file too
Even though this thread is more or less dead, I decided to attach the build I did today for anyone who stumbles upon it.
The kernel is by droidzone, for Sense 3.5, the same as the one used in RSK SE, git revision fb1198d, same config, I only enabled swap.
There might be some problems with the wifi module, I had to try different toolchains to get it to compile and load, in the end it did load OK but the wifi settings activity was still giving me errors; restoring a nandroid backup with the default kernel and applying the kernel zip immediately seems to have solved it.
In other words, take a nandroid backup before flashing this (should be obvious anyway...)
Also, for those looking for a swap-enabled AOSP kernel, have a look at CronMod.