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.
I've run into a very strange issue where ADB isn't functioning properly in two of the sense Roms I've tried recently, both Fresh 3.5.0.1 and the newest Evio Rom by Caulkin, 1.8 I believe.
I can't get the phone to go into USB debugging mode, although it works just fine in CM7 and another gingerbread rom I tried yesterday.
Here's some of the things I've tried, give me something I haven't tried, I dare ya!
Wiping properly in recovery (with Amon Ra 2.3, 1.8.0, and clockwork recoveries 3.x and 2.5.x)
Using Caulkin's Format All in recovery
my golden nandroid backup of Fresh didn't work, neither did a fresh fresh install
ADB works in fastboot or recovery, but not in the ROM
ADB works just fine in CM7 and non-sense ROMS (tried 2)
I tried going back to the roots by flashing my post nand-unlocking PC36img.zip and it worked fine, new fresh 3.5 install, borked.
Different USB ports
Different USB cables
Different Android SDKs
Different Android USB Drivers
My wife's HTC Hero works fine on those same ports on the same machines
two machines, one XP 32 bit and one win7 64 bit, wifes works on both, my evo works on neither.
doesn't work on stock fresh kernel, doesn't work on netarchy custom kernel.
Used to work, because I use my Evo for a test device on my apps, but I can't remember if it has ever worked on Fresh 3.5
Tried formatting my SD just to be sure there wasn't a remnant on it.
And oh yes, I made sure USB Debugging was checked.
As you can see I tried a lot. I'm very familiar with ADB and its nuances. This is genuinely stumping me, as I feel I've eliminated nearly all variables and tried nearly all configurations.
Any ideas, or anyone have something similar happen?
Not sure if this is it, but could it be something to do with boot.img.
http://modmymobile.com/forums/403-m...x-remount-failed-operation-not-permitted.html
I have the same problem. Mine is a stock rom thats been rooted by unrevoked but I haven't flashed anything on it yet. Apparently there is a line in default.prop for ADB and if it is deactived some features do not work well. You can change it but the only way to get it permanent is to edit the default.prop in boot.img.
Not sure if this is remotely the case because these are custom roms ... but its worth getting it out there because I never knew this before.
trimeijer said:
Not sure if this is it, but could it be something to do with boot.img.
http://modmymobile.com/forums/403-m...x-remount-failed-operation-not-permitted.html
I have the same problem. Mine is a stock rom thats been rooted by unrevoked but I haven't flashed anything on it yet. Apparently there is a line in default.prop for ADB and if it is deactived some features do not work well. You can change it but the only way to get it permanent is to edit the default.prop in boot.img.
Not sure if this is remotely the case because these are custom roms ... but its worth getting it out there because I never knew this before.
Click to expand...
Click to collapse
I'll flash back to Fresh tonight and check the build.prop to see if you're right.
I did notice that Flipz said he took the debug message out so it shouldn't pop up, but maybe that meant he disabled those lines in the build.prop. I would think he would know better than to do that, though, as that would disable ADB altogether, something he surely would see. It's totally possible though.
is there any way that mine could have gotten modified or something I wonder? I'd think no, because that would have to come from his install, especially on my new installs I did. Weird.
Unfortunately, my default.prop is the same as in the correct version in the link you posted. I'm literally at a loss of what else to try. Hoping some more pop in to share as I doubt we're the only two with this or have experienced this before.
I think I've figured out what's going on, now I just need to figure out how to fix it.
Like this post below, I think that the ADBD process isn't running because I couldn't find it in my process list. They used one from another build image and replaced their current one.
http://code.google.com/p/android/issues/detail?id=9437
Anyone done this before or could provide some guidance in addition to that thread?
I'd really appreciate the help.
My problem is that I can't write to /system but I think that might be something wrong with my root, even though I have s-OFF and I did flash a rooted rom ... not sure whats going on. I can only write to it in recovery.
Other ADB things work for my, like writing else where, shell, logcat ..etc
trimeijer said:
My problem is that I can't write to /system but I think that might be something wrong with my root, even though I have s-OFF and I did flash a rooted rom ... not sure whats going on. I can only write to it in recovery.
Other ADB things work for my, like writing else where, shell, logcat ..etc
Click to expand...
Click to collapse
Have you tried the "adb remount" command prior to trying to write to system? That will get you sometimes.
I pulled the boot.img from CM6 and replaced the /sbin/abdb process with the one from CM6 inside the Fresh boot.img. When I repacked, everything looked good, I installed Fresh Rom, and then it won't boot. Not at all. Wish I knew more about how to do that. I think I'm going to try again, but was following the perl scripts he posts on this page:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I had to suppress a message in one of them because there was a fourth file, and it says it was not created to be able to handle those. Read on another forum to comment it out. Anyway, it didn't work but I'm going to keep trying.
Installed CM7 again, and there it is as a process, /sbin/adbd. That's got to be the key.
Yeah adb remount doesn't do anything for me. Still errors.
I looked for my processes using ps ux and got nothing. Then in my default.prop is a line
"persist.service.adb.enable=0"
which they said was a problem and it sounds like my/our problem of there being no service. So i'm going to try another stock rom. I am using the OTA from teshxx but when I tried to modify it in the kitchen it said it had no boot.img (which could be why the setting is disabled and I don't have 'root adb'.)
@kmartburrito sounds like a signing issue right? I mean I messed with stuff like that before but I could never get it to boot properly after editing anything. Never really pursued it too much though. Read through the guide and it doesn't really have anything to do with signing ... but i know the space allocated for each section of the RAM is very specific so maybe there was a mismatch.
trimeijer said:
Yeah adb remount doesn't do anything for me. Still errors.
I looked for my processes using ps ux and got nothing. Then in my default.prop is a line
"persist.service.adb.enable=0"
which they said was a problem and it sounds like my/our problem of there being no service. So i'm going to try another stock rom. I am using the OTA from teshxx but when I tried to modify it in the kitchen it said it had no boot.img (which could be why the setting is disabled and I don't have 'root adb'.)
@kmartburrito sounds like a signing issue right? I mean I messed with stuff like that before but I could never get it to boot properly after editing anything. Never really pursued it too much though. Read through the guide and it doesn't really have anything to do with signing ... but i know the space allocated for each section of the RAM is very specific so maybe there was a mismatch.
Click to expand...
Click to collapse
Yep, I'm betting that's your problem. My line with that has a value of 1, so I'm not going to be any help from that standpoint. However, when you remount your filesystem as writable, you can modify that default.prop file and it SHOULD stick, in case you hit that same issue on your next rom.
I'm still trying to figure out what the hell is going on with my situation. I talked to another guy in a different thread and he explained that he is able to ADB in froyo sense roms, so even though I'm getting the same issue in multiple roms and not in non-sense roms, there's another person somewhere without the problem, so it logically can't be the ROM, unless it's a per-rom basis, and I've just hit the wrong rom three times in a row. Who the eff knows! This is really frustrating, but I guarantee you I will figure this out soon. I need to continue working on my app, so this needs to get fixed. Soon.
kmartburrito said:
Yep, I'm betting that's your problem. My line with that has a value of 1, so I'm not going to be any help from that standpoint. However, when you remount your filesystem as writable, you can modify that default.prop file and it SHOULD stick, in case you hit that same issue on your next rom.
I'm still trying to figure out what the hell is going on with my situation. I talked to another guy in a different thread and he explained that he is able to ADB in froyo sense roms, so even though I'm getting the same issue in multiple roms and not in non-sense roms, there's another person somewhere without the problem, so it logically can't be the ROM, unless it's a per-rom basis, and I've just hit the wrong rom three times in a row. Who the eff knows! This is really frustrating, but I guarantee you I will figure this out soon. I need to continue working on my app, so this needs to get fixed. Soon.
Click to expand...
Click to collapse
Have you tried the SprintLovers Rom? It is the closest to Stock you can get and it has regular updates. If that works maybe you can examine the difference with Fresh.
Maybe a logcat would help.
From a # prompt try the following
stop adbd
setprop persist.service.adb.enable=1
start adbd
Then try connecting via usb/adb shell.
JusticeAA said:
Have you tried the SprintLovers Rom? It is the closest to Stock you can get and it has regular updates. If that works maybe you can examine the difference with Fresh.
Maybe a logcat would help.
Click to expand...
Click to collapse
Hey, trying this now, will let you know what I find. Thanks for the idea!
gpz1100 said:
From a # prompt try the following
stop adbd
setprop persist.service.adb.enable=1
start adbd
Then try connecting via usb/adb shell.
Click to expand...
Click to collapse
Unfortunately, this is already set as such in my properties. I tried it anyway though on Mikz rom, and ADBD still isn't starting or working afterwards.
You know what it seems like? It seems that this is an issue with the HTC Kernel after one of the first versions that they released after FroYo. I say that because it works on Fresh's 3.1.0.2 rom which was one of the first FroYo builds, and it doesn't really work after that, which was a newer base build and newer Kernel. Doesn't work on really any other sense-based ROM for me either.
It DOES, however, work on any AOSP rom (which also uses a diff kernel) Which is one thought as to why it might not be working for me. The strange thing is though that this is somewhat isolated to my Evo. Maybe I have a lot of bad blocks or something, but something's fishy in that it works with early FroYo roms and any AOSP roms consistently, but not new Sense roms. So, either the majority of Sense devs are using Fresh's stuff as a base, or the problem is a bigger one related to the base build or Kernel itself.
I tried using the old HTC Kernel on a new build of Fresh, and found that the ADBD process did in fact appear when using a ps command, but it still did not function properly.
And furthermore, there is absolutely jack **** on documentation out there on what makes ADB work, or what could make it not work.
Since you mentioned kernels, have you tried a different one than what's in fresh?
I'm using the net's latest cfs kernel, and was using the previous 4.3.2 before. I'm not a big fan of the #15 kernel as it breaks the processing of scripts in init.d .
gpz1100 said:
Since you mentioned kernels, have you tried a different one than what's in fresh?
I'm using the net's latest cfs kernel, and was using the previous 4.3.2 before. I'm not a big fan of the #15 kernel as it breaks the processing of scripts in init.d .
Click to expand...
Click to collapse
Yep, several versions of Netarchy's kernel, several HTC, no dice. I suppose that should rule out the Kernel and point to the base build. What is really weird though is that it's happening mostly just to me, although there are a couple others for the Evo I'm sure (many might not even know it) and there are definitely others affected like I am on different devices.
Hardware 002 and rooted using part 1 and part 2 of toast's method.
Hi all!
I have spent over half an hour searching but to no avail so thought I'd ask here, how are the kernels hacked or modified?
When it comes to the real tech stuff I'm a bit lost, and to be honest before I stumbled across this site I knew nothing about making custom ROMS, but thanks to all of you out there, you have taught me loads without me asking much, so its here I need to ask!
Thanks in advance for your time & replies,
Arty.
just search the web for "linux kernel" the android kernel is a linux one.
when you know a bit about linux kernel you can add kernel mods to it, as in android.
you just need to download the source of the kernel modify it and compile it than.
hope this helped a bit
ps.: and if you dont have the source you have to be a tech/kernel genius like -snq
Thanks for your reply there crendot!
I was afraid I'd have to know about Linux stuff, which to be quite honest I dont!
I have messed about with a Ubuntu Virtual Machine in the past (when I first read how to root the Desire) but I find it too difficult to understand, I'm much more at home with the old DOS commands personally!
Only reason I ask is that my fone is playing up and has overheating / reboot loop issues with anything greater than Android 2.2 (since it came back from repair when I dropped it & cracked the screen completely) and so far I am stuck with my own slightly customed Rooted 2.2 with standard features (no 4-in-1 menu, no wake & unlock on trackpad and the DSP manager wont work) also, I have not yet tested it, but I know only a few kernels will let me send & recieve MMS, the previous build was a lightly customed LeeDrOiD_V3.0.8.2_GB_A2SD ROM, but alas kept bootlooping after it became warm and I found I couldnt do much with it :-(
I am hoping to get a shiney new Sensation soon, but until then I wanted to know how to modify the kernel to add / remove stuff!
Is there an easy way to take a kernel file & be able to 'read' it so I could copy the stuff I need into the stock kernel at all, or is that my wishfull thinking again?
Thanks again & sorry about the long reply!
Arty.
to understand what a kernel for the desire is, u can download the stock one on the htcdev.com site http://htcdev.com/devcenter/downloads
for example u can download the latest for our desire: "HTC Bravo – GB MR – 2.6.35 kernel source code"
that is the source code..u will see there are thousands of .c files...is not easy at all modify the kernel..it requires strong skills on linux and C language
about the send sms and mms, that is related to the rom and ur apn settings i think..not to the kernel..the kernel handle very low level actions..
maybe u would like to make custom roms..this is a bit much easy if u just cook it for example with the android kitchen (search for it)..the rom contain the kernel and the operating system and some apps
so lets check the facts!
did the phone overheat when it came back from repair (with stock rom)?
or have you flashed the new rom instant?
i would say you save all your stuff and do a nandroid backup.
than you follow this instructions to flash the rooted stock 2.2 rom and the radio
if the problem is still there i would say its a hardware problem, if not you can try other roms as long as no problems occure
dont play around with kernels, you dont have to, the stable kernels are in the roms
if they arent stable for you its not the kernels fault
i guess something messed up while you flashed something...
ps.: if you have absolutly no linux skills and so on, i would say you read into that before playing around with your mobile ^^
andQlimax:
Thanks for your reply also!
I know the APN settings for the mobile data & the MMS as I have written them down, the strange thing is I rooted my fiancee's Desire with the same ROM I was using at the time & she couldnt send or recieve MMS either (I'm O2 and she on Orange, both contract) and I have only found a few custom ROMs that allow the sending & recieving of MMS messages.
Also, I can make custom ROM's, I use Android Kitchen for most of the stuff (such as de-odexing, adding root, bash, busy box etc) but I find mostly when I bake the ROM using the kitchen I have errors on install, so I just prefer to use the kitchen for adding the needed stuff, then I'll just use windows to add / remove apps, boot animations & the audio files I want and just zip it myself & flash which has a higher success rate if I'm honest!
crendot:
so lets check the facts!
Q: did the phone overheat when it came back from repair (with stock rom)?
A: No, I didnt have stock ROM on, I still had either LeeDroid HD or a HD InsertCoin ROM, which when I got the phone back I did a nandroid restore (I make them quite regular & copy them to my PC for extra piece of mind!)
Q: or have you flashed the new rom instant?
A: I also have installed an untouched ROM(untouched by me) a day or so after as the nandroid backup wasnt the version I wanted, I was due to be on holiday to Blackpool for a week, so I flashed the LeeDrOiD_V3.0.8.2_GB_A2SD ROM on both my desire & my fiancee's desire, hers was stable, mine I couldnt have the screen on for long before it got too hot (managed about 5 picture captures before I had to turn screen off for a while or it got too hot) then thing is, my fiancees gets got too, mine is the metal holders for the memory & sim cards, i either have to place something cold on them like a glass or even hold a fan to it for a few minutes until it cools down again!
Q:i would say you save all your stuff and do a nandroid backup.
than you follow this instructions to flash the rooted stock 2.2 rom and the radio
A:My current ROM is the standard one after downgrading HBOOT & using Unrevoked, but I used the phone's update feature to update everything to 2.2, then I rooted it and all works fine, BUT, if I add any modifications, like circle battery it is too much for the phone & gets too hot & power cycles, it gets to the boot anim then automatically reboots again, it can do this for about half hour before it works again, but I mostly just pull the battery & put something cold on the affected area! Yesterday I put my fone in the freezer for 10 mins, but using even the most basic customisation was getting hot again so I reverted back.
Q:if the problem is still there i would say its a hardware problem, if not you can try other roms as long as no problems occure
I have tried a number of other ROM's, but I think I will just stick with what I know works for now!
Q:dont play around with kernels, you dont have to, the stable kernels are in the roms if they arent stable for you its not the kernels fault
A: thanks for that, think I'll leave them alone for now lol!
Q: i guess something messed up while you flashed something...
A: Nothing went wrong with the flashing, as Ive done it so much in the past year or so I know what its sucessfull or not!
Q: ps.: if you have absolutly no linux skills and so on, i would say you read into that before playing around with your mobile ^^
A:Thanks!
I really dont know what the cowboys done with my fone, but they have totally screwed it up, the microphone dont work and I have to almost eat the damn thing n shout, even then sometimes nobody can hear me! The WiFi signal is horrendous since it came back, can only get a full signal if I sit on top of the router, so using the WiFI out of the room is now out of the question! I also noticed they had cut off or pulled off something that I am convinced is the WiFi aerial, it sits just under the flash, a black tab it looks like, they insist they didnt do it, I KNOW otherwise!
When I first saw the phone, the back cover wouldnt fit on & it looked like they hadnt installed everything right, so they had it back as also the in-call speaker didnt work either, there are still outstanding problems, but as I have left it so long (main shop in Glasgow, me in Paisley with no way of getting there myself) I doubt they will do anything about it, i am SOO angry there isnt a swear word I dont shout every time the bloody fone hets hot & power cycles!
Again thanks for all your replies & sorry for the essay lol!
Arty.
hi, ok it really sounds like they have messed up your little desire!
first of all i want to apologize i thought you dont have a clue about anything ^^
so i would suggest you try to flash a new radio maybe the 32.56.00.32U_5.17.05.23 helps, if you have it on your mobile reflash it just to be sure(if you have a different hboot, you have to do it with fastboot)
if this didnt help, i would say you try to flash the RUU
and when that fails i would start yelling at the customer support
wish you the best
ps.: i just started thinking if it is maybe the battery, change it with a/the other one
Hi,
I trawled threads and guides before starting my upgrade from CM7 to CM9. Thought I had everything in order so set-off. Ended up in a bootloop when I was done. Managed to get the phone sort-of working by installing my previous CM7 zip. I installed just the CM9 file over that and it started working....to a point. It wouldn't take the ICS gapps but did take an older version which at least has my mail and contacts working but I can't get into Play and get regular errors for basic stuff, like clock etc.
I've tried what I can but am now plain stuck and could really do assistance. I'm comfortable with the install procedure (I think!) although realise now that I cocked up my back-up first time round. Have to live with that now. Just want to get to a functioning ICS install.
These are files running right now.
CM9-NIGHTLY-120329-Defy
gapps-20111128
Honestly can't remember which kernel is running now, and confused which should be running. 95% confident that mine is a red lense but never seen another to compare.
CM9_Kernel-signed
CM7_Kernel-signed
These gapps didn't seem to work.
gapps-ics-20120317-signed
gapps-ics-4.0.3-20111217
I'm UK based with a regular Defy. I followed the guide and links (also pulled files from elswhere when the probs kicked in) in here.....http://forum.xda-developers.com/showthread.php?t=1386680
I have posted the problem in there but not sure it's the best place. I'll put a note in there to say I've started a thread. Don't want to upset anyone by double-posting!
Did I mention that I really could do with some guidance?!!!
Gobsheen said:
Hi,
I trawled threads and guides before starting my upgrade from CM7 to CM9. Thought I had everything in order so set-off. Ended up in a bootloop when I was done. Managed to get the phone sort-of working by installing my previous CM7 zip. I installed just the CM9 file over that and it started working....to a point. It wouldn't take the ICS gapps but did take an older version which at least has my mail and contacts working but I can't get into Play and get regular errors for basic stuff, like clock etc.
I've tried what I can but am now plain stuck and could really do assistance. I'm comfortable with the install procedure (I think!) although realise now that I cocked up my back-up first time round. Have to live with that now. Just want to get to a functioning ICS install.
These are files running right now.
CM9-NIGHTLY-120329-Defy
gapps-20111128
Honestly can't remember which kernel is running now, and confused which should be running. 95% confident that mine is a red lense but never seen another to compare.
CM9_Kernel-signed
CM7_Kernel-signed
These gapps didn't seem to work.
gapps-ics-20120317-signed
gapps-ics-4.0.3-20111217
I'm UK based with a regular Defy. I followed the guide and links (also pulled files from elswhere when the probs kicked in) in here.....http://forum.xda-developers.com/showthread.php?t=1386680
I have posted the problem in there but not sure it's the best place. I'll put a note in there to say I've started a thread. Don't want to upset anyone by double-posting!
Did I mention that I really could do with some guidance?!!!
Click to expand...
Click to collapse
To install ICS from scratch first make a backup of evrything you would like to hae later and then refer to the below mentioned link and install ICS:
How To Flash ICS(Defy Builds)
1:Head Over To Stable recovery
2:Wipe Data
3:Install ZIp from SD Card
4:Select ICS(Defy) .zip
5:Flash
6:Flash CM7 Kernel
7:Clear Cache and Dalvik Cache
FIrst Boot will take some time...
Click to expand...
Click to collapse
Ref: http://forum.xda-developers.com/showthread.php?t=1432100
Hope this helps!!
Thanks,
I'll have a good look through that thread tonight. I thought the CM9 kernels were the right one for my red lense defy......?
Should I just leave installing the Gapps zip until after everything else is done? I assume using one of the ICS gapp files is fine?
I installed they Defy+ nightly by Quarx:
http://quarx2k.ru/cm9-nightly-defy+/CM9-NIGHTLY-120330-Defy+.zip
This should already contain the GB kernel right? I flashed it anyway, just to be sure.
I have the Red Lense Defy, it's detected as a Defy+ now and the camera works.
HOWEVER, i had to flash the 'Batter fix for Red Lense', see first post here http://forum.xda-developers.com/showthread.php?t=1432100
This actually caused me a few hours sweat, since i did not flash it at first and then thought my battery was dead. It went empty after an hour or so, and then there was this battery you see when it's charging when then phone is powered 'off', with a big question mark within the battery -- and it would not boot!
I could get into recovery, but once i unplugged it from the power cable it went off shorty after and i did not have the battery fix on the SD card. For some reason i was only able to enter recovery when the usb was only charging, once it was a 'data' connection it would not turn on or turn off quickly. If i turned off my laptop and used the offline charge feature it would power on, however i could not copy over any files I had no microSD -> SD adapter to use my SD card reader.
Finally, having it on power only, I started into the bootloader (power on + Vol+), which also said low power (more fear of a broken battery). After a minute or so, it terminated itself and began to boot CM9 flawlessly. I was able to copy the battery fix from my webserver onto the sdcard. Flashed it. Battery detected again and charging like it should *phew*
This should be stressed A LOT more in the HOWTOs, i was not able to post to the CM9 dev thread yet (<10 posts). Maybe someone can.
Besides all that, it runs really nice now. Overclocked it to 1.3GHz and lots of things run quite smoothly, can't wait for full HW-Acceleration
It worked!!!
Thanks for your help guys. Flashed it as a Defy+ and all seems fine. Pity my main sd card seems to have crapped out during the mess so hoping I'll be able to get my files off it. But, the phone works again!
Gobsheen said:
It worked!!!
Thanks for your help guys. Flashed it as a Defy+ and all seems fine. Pity my main sd card seems to have crapped out during the mess so hoping I'll be able to get my files off it. But, the phone works again!
Click to expand...
Click to collapse
Congrats!!
You may use any data recovery software to retrieve the files ....
Thanks,
One thing I've noticed is that I've never had a 'H' signal since upgrading. It stays on 3G even in areas where I would have had a solid 'H' before. I double checked my APN & it's fine.
Any ideas?
I am trying to build a custom kernel from official and/or cynogenmod sources. I can get it to build successfully and I use Android Kitchen to extract boot.img to an zImage / ramdisk and back together again. Also, I am using known working configs as a base (/proc/config.gz)
My issue is this.... More often that not, the phone will immediately reboot after the first couple of seconds which I can only guess something went horribly wrong. I've complied lots of linux kernels for desktops and never had any issues, but this is either really hard or I am doing something completely wrong. I will be glad to hear any feedback I have tried factory reset & cache wipe
enigma99a said:
I am trying to build a custom kernel from official and/or cynogenmod sources. I can get it to build successfully and I use Android Kitchen to extract boot.img to an zImage / ramdisk and back together again. Also, I am using known working configs as a base (/proc/config.gz)
My issue is this.... More often that not, the phone will immediately reboot after the first couple of seconds which I can only guess something went horribly wrong. I've complied lots of linux kernels for desktops and never had any issues, but this is either really hard or I am doing something completely wrong. I will be glad to hear any feedback I have tried factory reset & cache wipe
Click to expand...
Click to collapse
Can't be much help myself but perhaps the XDA-U can be: http://www.xda-developers.com/andro...ing-features-to-your-freshly-compiled-kernel/
BWolf56 said:
Can't be much help myself but perhaps the XDA-U can be: http://www.xda-developers.com/andro...ing-features-to-your-freshly-compiled-kernel/
Click to expand...
Click to collapse
Well, thanks for the guide, but I was building it correctly after all. Samsung has added a one byte hex in the boot.img and the phone checks for it. Thanks Samsung!