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.
Hey people!
I read a few posts dealing with same error below, but the descriptions of the problem was a bit different so I wanted to be sure.
I'm quite new to this so bear with me. I got an EVO last month (dec 24) and have since wanted to root. I've been reading up on it, and finally decided to root using Unrevoked earlier today. The root process worked perfectly, so I proceeded to create a nand backup and flashed the CM6 Mod using Clockworkmod rom manager app.
I was a bit excited played around with it a bit, and decided to flash the Miui ROM. I placed it on the root of my SD card, and this is where I lost control. I tried to flash using the ROM manager and it never completed, citing an error. I tried to reboot phone but I didnt get past the white HTC EVO 4G screen. I entered bootloader, and I tried to restore my original Nand backup but I keep getting this error, "Error while flashing boot image."
What would be the appropriate (or least risky) course of action? I can mount my SD card on computer through ClockworkMod recovery, should I try placing stock ROM zip or cm6 zip file and try to flash?
I do not think this is a battery issue, I had my phone plugged to charger while trying to flash nand.
I appreciate the help, I know I probably sound like a noob, but for almost a month I was reading, learning and trying to be careful (obviously not enough), once I rooted I got overzealous.
MOD Version is 2.5.0.1
Thanks for all your help,
DJ
I flashed a the recovery, after a few issues...my phone is back up and running...DISREGARD. Sorry for the noob ?.
so i have the bell pay as you go edition of the gio
and when i got it, i just uninstalled as much crap as i could
one of those happen to be 'Talk', which i now discovered is google talk (thought the app was called gtalk)
uninstalling it makes it disappear forever and you cannot find it in the market
in addition to that, i uninstalled whatever app/service needed to run live wallpapers
so if someone could rip/backup those apps and upload it here, many thanks
(i tried installing the talk apk on it's own, and the talk service apks, it does not like me install for some reason)
last question is,
any 5660m users got adobe flash running, i tried the stand alone armv6 apk, installed it, and does nothing
the other flash apk with loading the lib files into the root dir, i have not tried, if i can get the standalone apk working, i'd rather do that
any other tips for the 5660m would be great
thanks
edit - see post #9 (need help with stock browser)
Promise you'll back things up the next time?
Look at my stock rooted ROM for the files you shouldn't have deleted. You should be able to read (not write, at least not in a way the phone can handle) the RFS partitions with MagicISO among others. (Basically any program capable of handling FAT partition images.)
ADB push back the files into place, make sure their permissions are correct.
Can't help you for Flash, I've never tried it myself and my Gio is out of order for the time being.
For flash you need root and push LIB files to /data/data/com.adobeflash***/lib ant set permissions
Sent from my GT-S5660 using Tapatalk
Darkshado said:
Promise you'll back things up the next time?
Look at my stock rooted ROM for the files you shouldn't have deleted. You should be able to read (not write, at least not in a way the phone can handle) the RFS partitions with MagicISO among others. (Basically any program capable of handling FAT partition images.)
ADB push back the files into place, make sure their permissions are correct.
Can't help you for Flash, I've never tried it myself and my Gio is out of order for the time being.
Click to expand...
Click to collapse
so this is something i cant just grab someone's titaniumbackup files and install?
That too, if you have another rooted Gio at your disposal. I answered based the info I got.
ya, sorry, that's sorta what i meant in the first post,
i was actually asking for someone's to backup the gtalk/talk service/app and the live wallpaper service/app with titanium backup and upload it
if someone could do that for me, much appreciated
Try this and let me know if it works.
View attachment TitaniumBackup.rar
thanks, that did the trick
additionally i want to ask:
is the reason 5660m incompatible with most of the custom roms is the slight difference in hardware?
if i were to change microsd card, is a drag and drop to the new card sufficient or are there hidden/protected files that cannot be copied
lastly,
if i were to update the rom/install custom rom, is there any way to back up settings and apps or would i have to do stuff all over again?
gonna bump this again,
I need the stock browser this time, if someone would kindly back up from titanium backup
i'm just testing some compatibilities on certain websites
anonxlg said:
gonna bump this again,
I need the stock browser this time, if someone would kindly back up from titanium backup
i'm just testing some compatibilities on certain websites
Click to expand...
Click to collapse
Enjoy.
FusiveR said:
Enjoy.
Click to expand...
Click to collapse
finally got around, i tried installing it, doesnt work
it starts installing, then resets and browser does not appear in app list
tried both app and app+data
anonxlg said:
thanks, that did the trick
additionally i want to ask:
is the reason 5660m incompatible with most of the custom roms is the slight difference in hardware?
if i were to change microsd card, is a drag and drop to the new card sufficient or are there hidden/protected files that cannot be copied
lastly,
if i were to update the rom/install custom rom, is there any way to back up settings and apps or would i have to do stuff all over again?
Click to expand...
Click to collapse
Only the roms flashed from Odin usually aren't compatible with our phone anything else such as CM7.1, CM7.2, CM9, and all the other roms able to be flashed from
Recovery mode are mostly compatible with our version of gio hope I helped
Sent from my GT-S5660M using xda premium
What isn't compatible are the baseband and the bootloaders.
As long as an Odin-flashable ROM contains only system and boot.img you're in the clear. This is mostly a problem with early Europe/Asia 5660 ROMs.
Drag and dropping your files to the new SD card should do the trick. Hidden files and folders for Android (and Linux) have a dot at the beginning of their name, e.g.: /.android_secure/ and by default there shouldn't be any files with the FAT32 "hidden" attribute set on the SD card. The settings of your Windows Explorer will influence whether or not the latter copy over or not.
Backing up your applications and their settings can be done by applications like Titanium Backup. Most should transfer well from one ROM "family" to another. (As in: from stock to CM7, or CM7 to CM9, or CM9 to stock...) Your mileage will vary if you try to transfer system apps, or system settings.
so why do you (have to?) use odin, i thought there is CWM for gio, isnt that better than odin?
and still looking for a titanium backup of stock browser
maybe i should just install the ics rc
anonxlg said:
thanks, that did the trick
additionally i want to ask:
is the reason 5660m incompatible with most of the custom roms is the slight difference in hardware?
if i were to change microsd card, is a drag and drop to the new card sufficient or are there hidden/protected files that cannot be copied
lastly,
if i were to update the rom/install custom rom, is there any way to back up settings and apps or would i have to do stuff all over again?
Click to expand...
Click to collapse
I dunno what you are talking about, My canadian Gt-S5660M runs all custom firmwares, kernels, scripts etc just fine.
Odin and CWM are different and each serves their purpose.
Odin works with the lower level Download Mode, and can recover from situations CWM can't. It is also the usual way to install CWM in the first place. (You could also do it with a clever dd command on a rooted phone.) It is however cloakware, undocumented, difficult to install, buggy at times and just quirky overall.
CWM is more stable, doesn't require a computer to run, and is generally much safer to use.
AlwaysDroid: If you look at very early posts about the 5660M, many users encountered major issues after flashing European 5660 ROMs. Screen brightness all over the place and no network connection.
The problem was that those ROMs were Odin flashable "One Package" files that contained bootloaders and radio images as well. Those files were required for users upgrading from Froyo to Gingerbread, as stock Gio 5660s were also sold with 2.2 unlike the 5660M.
I came from this thread http://forum.xda-developers.com/showthread.php?t=1911718
In the first time, i believe that this error was because hardware issues, but, the ICS rom, works perfect, so, i try to flash gingerbread again, and in the first boot (if the boot succes) when the logo like recovery from android appear, there is a error: can't acces /system/csc/ATT/system/. this error, doesn't appear with ICS, maybe that is the problem, someone know how to fix? if i install CWM, the phone will have that problem when i enter the recovery, so, i have no idea how to fix it. I am not an expert with android, so,maybe someone can tell me about that error, is the only idea that i have for this problem.
Thanks and sorry for my english
Edit, the path is /system/csc/ATT/system/
How do you flashed back from ICS into GB?
If you just simply downloaded a firmware flashable by odin, then that firmware may does not contains a kernel for GB, and you're still trying to use the ICS one.
If the downloaded firmware doesn't includes a kernel (downloaded from sammobile example, the GB ones does not has a kernel), you has to manually flash one. You can find several GB kernel at this topic.
So, the problem is kernel? I download the gb from another website, thw ics that i use was that one named oneclick, where can i get the stock kernel? There are custom only, and one of the problem is when i flash something custom , like cwm, and custom kernels rooted in ics, the problem of the freeze came back.
I tried the kernel, and the error persist, and in GB, its freeze, in ICS no, and the only difference iis that error
lorddavid said:
So, the problem is kernel? I download the gb from another website, thw ics that i use was that one named oneclick, where can i get the stock kernel? There are custom only, and one of the problem is when i flash something custom , like cwm, and custom kernels rooted in ics, the problem of the freeze came back.
I tried the kernel, and the error persist, and in GB, its freeze, in ICS no, and the only difference iis that error
Click to expand...
Click to collapse
I've seen notes that say use kies, and do full wipe in that process.
bs27975 said:
I've seen notes that say use kies, and do full wipe in that process.
Click to expand...
Click to collapse
I try it, but it doesnt work, i use the option to update and initialize (i have it in spanish, actualizar e inicializar), ask me the name, and S/N, i use it, download something, i put in download mode, and when starts, give me a message like japanesse or chinesse, i dont know, and the program close.
Anybody any idea? i would like to keep this phone, but if i cant root, i cant be happy with the phone. I am thinking that the problem is about storage maybe, because i see problems only in the rogers version (with 4gb internal), maybe someone can look at this, ICS works perfect, but i cant install any customs because the problem
When I take my stock backup and make it into a flashable ZIP ROM it seems that it defaults my SGS3 to a have SIM card error; and wont let me connect to any cell networks...
I cannot seem to find anything to resolve this issue....
I can restore this same system and have no issues with networks connectivity but if i zip it up and make an updater script and try to flash it as a ROK then i start to have problems... Please help i'd like to make a DEODEX ROm but i need to make a functional stock ODEX ROM first
Thanks in advance to anyone who can help.... This has NEVER been a problem before with other phones...
Why not use Freezas stock rom? He offers both odexed and DeOdexed in his thread. They are bone stock and already zipped ready to go. Or use his reverse engineer and see where yours is going wrong?
Sent from the future via Tapatalk 4
edfunkycold said:
Why not use Freezas stock rom? He offers both odexed and DeOdexed in his thread. They are bone stock and already zipped ready to go. Or use his reverse engineer and see where yours is going wrong?
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Because i am using the Virgin Mobile variant... Same model number, different framework.... Ive tried every possibility of replacement and exchange of files with working booting ROMs and yet still to no avail...
I'm not 100% sure. But I believe it might have something to do with your APN settings.
I used a stock odex sprint ROM as a template ([ROM|Stock Rooted] 4/24/13 Sprint TouchWiz Jelly Bean 4.1.2 (L710VPBMD4) Odex/DeOdex ) and tried every combination of file replacement; /system replacement, kernel replacement configurations...
If i deleted everything but the update script and dropped a /system inside directly from a backup tar with the permissions set correct before being obliterated by the FAT based ZIP file system; then put in our stock kernel.. i could boot up but my phone would think it needed a SIM card (which does not exist) and would lock out the selection of cdma service until it was inserted.... Weird.
If i flashed a straight untouched odexed version of the sprint ROM that i used as a template, i found that to be the one and only sprint ROM that boots on our phones with data as soon as it starts.....
Soooooo... When combining the ROMs: If you try and combine or exchange any set of the filesets in the system partition (e.g. /framework /libs /etc) you would end up with bootloops, If you switch kernels and try to boot you will end up with bootloops....
I made about 30 varaitions of flashable ROMs but the only ones that would boot were my exact backup (but with no data & SIM error) or the odexed version of the sprint ROM and only when untouched.....
So there's the story as far as i've gotten
I have read numerous threads that have described this problem occurring when jelybean was first leaked and the SGS3's were still on ICS, people flashed the JB leaks or JB ROMs and were left with a SIM error and locked up data....
But no matter how many of these threads i read through, no solution was ever found, at least not one that was shared in forums...
Whatever was found out to be the issue with flashing JB ROMs to SGS3's was discovered by DEVs and then integrated into ROM releases without informing the public of what was fixed.
Hope this helps
bump