so i have a custom build over in the vogue forums but i would love to get it working on the hero, it is basically just a heavily customized version of AOSP so i took asop mod as a base and added my custom changes to it (that part i got) i then signed it and attempted to flash it to my hero, it got about half way through the installation and said i was missing and update script so if anybody can give me advice that would be awesome i would really love to get this build running on my daily phone.
thoughtlesskyle said:
so i have a custom build over in the vogue forums but i would love to get it working on the hero, it is basically just a heavily customized version of AOSP so i took asop mod as a base and added my custom changes to it (that part i got) i then signed it and attempted to flash it to my hero, it got about half way through the installation and said i was missing and update script so if anybody can give me advice that would be awesome i would really love to get this build running on my daily phone.
Click to expand...
Click to collapse
When you unzipped the ROM you should have seen some folders and a boot.img. There are some folders in the boot.img that need to be replaced along with the kernel for our phone. So just using a boot.img from another ROM might be the easiest. Otherwise you will have to unpack it, switch out files and repack with a kernel for our phone.
The update script is found in /META-INF/com/google/android/. You should be able to pull it from another ROM.
unCoRrUpTeD said:
When you unzipped the ROM you should have seen some folders and a boot.img. There are some folders in the boot.img that need to be replaced along with the kernel for our phone. So just using a boot.img from another ROM might be the easiest. Otherwise you will have to unpack it, switch out files and repack with a kernel for our phone.
The update script is found in /META-INF/com/google/android/. You should be able to pull it from another ROM.
Click to expand...
Click to collapse
ah i deleted the meta-inf folder thats probably what cause the problem
also am i able to have a folder that keeps things in /data like i am on the vogue or does it all have to be in the system?
Related
Hello all,
I'm curious if there is a way to install ROMs in the Android emulator from the SDK for testing..?
I've done some digging and experimenting, and can't find any information on this -- if it's possible, could someone point me in the right direction?
I play around with different ROMs a lot and like to see them in action, and am changing ROMs often. This is a pain to do on my phone, and it's beginning to show its wear ; ) Ideally, I'd be able to install the ROMs in the emulator to play around with the different flavors before deciding on one to install and keep on the phone.. also to stay up-to-date without risking the stability of my device..
I've tried using a nandroid dump of system.img off my phone mixed in with the Android SDK's images, and this boots OK with the ROM (I had Cyanogen 4.2.3.1 at the time).. but the problem then is getting a system.img of the new ROMs from the "update.zip" files that are available, without putting them on my phone first (kind of defeats the purpose)..
Is this doable? Either "flashing" these updates to the emulator image, or creating a system.img from the zip's?
Thanks!
From what I've found, you can do it from Nandroid images. However, I didn't really have any luck with it.
I'd LOVE to finally find a real solution.
also from what i know only cyans roms will work other roms frameworks are too heavily modded to work on the 1.5 sdk ie. hero,pulse,blur
sad i know
grivad said:
I've tried using a nandroid dump of system.img off my phone mixed in with the Android SDK's images, and this boots OK with the ROM (I had Cyanogen 4.2.3.1 at the time).. but the problem then is getting a system.img of the new ROMs from the "update.zip" files that are available, without putting them on my phone first (kind of defeats the purpose)..
Is this doable? Either "flashing" these updates to the emulator image, or creating a system.img from the zip's?
Thanks!
Click to expand...
Click to collapse
lol i well didnt read the post before replying no there is no way that you can test it from a update.zip sorry
I wanted to apply one of the battery mods to my captivate i896 (running the stock rogers rom), specifically version E.
I tried using the UOT Kitchen website at first but that failed. So then I tried to do it myself, but that also fails. Something seems to be going wrong when I try to apply the update.zip I have and I see no error output to help me trace it. Here's what I've been doing (when I tried it from scratch):
So I downloaded the related zip file from the second post, "scbm_E_grey_number.zip".
I then used "Android Theming and Tweaking" to get the framework file from my phone, and decompile it. I replaced the corresponding .png and .xml files from "scbm_E_grey_number.zip" to the appropriate folders in the decompiled folder from the ATT software. Then using the same software, I compile the framework apk again.
I then use the update.zip creator. I create a "framework" folder in the "placehere" folder for the update creator. Inside the framework folder I placed my new APK. I then ran the update creator to generate a new script, which copies from "framework" to "framework" on SYSTEM. Finally, I have it create the update.zip for me.
Everything is fine up to this point. I place the update.zip on my SD card, boot my phone into recovery, try to flash it...I get the following:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried this a few times with no luck
I'd like to figure this out in the hopes that I can do some mods of my own in the future, so any help would be great Thanks!
If you ever figuered this out please let me know too, i am having the same issue. I am using a Captive that I just restored with Odin. I unroot it and remove the applock on it. I get the same installation aborted issue. I then tried to install it with ClockWork recovery... that just crashed my phone and I had to reinstall again. So if anyone know what the problem is please chime in.
Can't theme the stock rom. It has to be a deodexed rom, which is essentially all of the custom ones. Also, don't flash mods through the stock 2e recovery, you want to do it through CWM.
TheEscapist said:
Can't theme the stock rom. It has to be a deodexed rom, which is essentially all of the custom ones. Also, don't flash mods through the stock 2e recovery, you want to do it through CWM.
Click to expand...
Click to collapse
Hmm I see, thanks for the info... there was no odex file for that particular file, so I thought I'd be lucky and it was possible :/
And, why should you use CWM to flash instead of the stock recovery?
ootz0rz said:
Hmm I see, thanks for the info... there was no odex file for that particular file, so I thought I'd be lucky and it was possible :/
And, why should you use CWM to flash instead of the stock recovery?
Click to expand...
Click to collapse
No problem. While on the topic, is that thanks button new, or am i just blind, and missed it all this time?
It's something about signatures, if I remember correctly, though, that may be 3e. I think part of it is that it's just typically done with CWM.
ootz0rz said:
I wanted to apply one of the battery mods to my captivate i896 (running the stock rogers rom), specifically version E.
I tried using the UOT Kitchen website at first but that failed. So then I tried to do it myself, but that also fails. Something seems to be going wrong when I try to apply the update.zip I have and I see no error output to help me trace it. Here's what I've been doing (when I tried it from scratch):
So I downloaded the related zip file from the second post, "scbm_E_grey_number.zip".
I then used "Android Theming and Tweaking" to get the framework file from my phone, and decompile it. I replaced the corresponding .png and .xml files from "scbm_E_grey_number.zip" to the appropriate folders in the decompiled folder from the ATT software. Then using the same software, I compile the framework apk again.
I then use the update.zip creator. I create a "framework" folder in the "placehere" folder for the update creator. Inside the framework folder I placed my new APK. I then ran the update creator to generate a new script, which copies from "framework" to "framework" on SYSTEM. Finally, I have it create the update.zip for me.
Everything is fine up to this point. I place the update.zip on my SD card, boot my phone into recovery, try to flash it...I get the following:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried this a few times with no luck
I'd like to figure this out in the hopes that I can do some mods of my own in the future, so any help would be great Thanks![/QUO
Flash perception
Click to expand...
Click to collapse
dfuse06 said:
Flash perception
Click to expand...
Click to collapse
Eh, I'm hesitant to flash a custom rom. I have a rogers captivate and don't want to be stuck with an at&t boot screen (in case I need for repair or whatever) and I don't want to be stuck with poor GPS performance (as mine works VERY VERY well right now).
ootz0rz said:
Eh, I'm hesitant to flash a custom rom. I have a rogers captivate and don't want to be stuck with an at&t boot screen (in case I need for repair or whatever) and I don't want to be stuck with poor GPS performance (as mine works VERY VERY well right now).
Click to expand...
Click to collapse
AT&T boot screen can be replaced, but you have to do a whole bunch of Odin stuff to get there. Also, that's because we(I'm on rogers as well) have a tweaked modem.bin. You can flash that, or one of the jupiter/JM9 fixes to get similar gps performance. But obviously, it's your choice. You are messing with a quite expensive piece of hardware. However, if you want to apply mods, you need to get a custom rom.
TheEscapist said:
AT&T boot screen can be replaced, but you have to do a whole bunch of Odin stuff to get there. Also, that's because we(I'm on rogers as well) have a tweaked modem.bin. You can flash that, or one of the jupiter/JM9 fixes to get similar gps performance. But obviously, it's your choice. You are messing with a quite expensive piece of hardware. However, if you want to apply mods, you need to get a custom rom.
Click to expand...
Click to collapse
I'd love to have a set of concise instructions detailing all that...but everything is all over the place and difficult to find :/ Right now I'm just mostly reading up on things and trying to learn
There's instructions in the dev forum. If I wasn't on my phone, I'd grab the link for you. As far as learning, you just have to spend hours and hours on here.
TheEscapist said:
There's instructions in the dev forum. If I wasn't on my phone, I'd grab the link for you. As far as learning, you just have to spend hours and hours on here.
Click to expand...
Click to collapse
Heh I've been trying. It's certainly a bit of a learning curve
Hi,
as the title states I am looking for an Eclair ROM for the Nexus One with SLCD support.
I tested official ROMs, though couldnt find any which supports the SLCD, which means:
I know how to flash it and the process itself worked, but the display was just off when the mobile booted up. Buttons worked but the touch display didnt.
It needs to be an Android 2.1 or 2.0 and the Hardware is also fixed: Nexus One with SLCD.
I was looking for a week now and couldnt find a suitable ROM.
Any help is welcome, thx in advance.
Cheers, stas
There is none in existence. Nexus didn't come in SLCD variant until Froyo was released.
Would it be possible to get Eclair running on the Nexus One with a homebrew linux kernel? I mean: Is the slcd driver just some kernel issue or do I need something more?
Anyone knows a way of how to make it work?
Cheers, stas
Have you seen this post?
http://blog.akisaarinen.fi/booting-android-21-in-nexus-one-with-slcd
It seems this guy was able to boot his slcd nexus one with eclair.
Sent from my Nexus One using XDA
I have seen this post and tried to use a stock eclair rom and unpack the boot.img to replace the kernel with an own one. I took the kernel config off a froyo image and build a kernel. though after repacking and flashing the device didnt boot. I could try to use a froyo kernel with slcd support in an eclair boot.img, would do it tomorrow.
Thanks, stas
I actually managed to boot up android 2.1 but couldnt get the wifi working.
Steps I did:
flash boot.img from froyo
flash system.img from eclair
that way the display was working and the phone booted up. But the wifi didnt work. After some reading I encountered that the kernel modules are located in the system.img and the kernel is as expected in boot.img. Since both are from different branches the module for the wifi didnt match the kernel. So I extracted the appropriate kernel module from froyos system.img and pushed it on the mobile. That way the wifi could be activated but still could not connect to the AP. How ever I leave it for now and try a different approach.
Thanks for your time.
You can try to take any custom kernel for Froyo, look at the files being flashed besides boot.img, grab all those files from Eclair ROM and flash them on Froyo ROM. This way you'll get most of the functionality in the kernel.
Hi everyone, I need help over here as I'm stuck in the process of rooting & upgrading my Xperia TX (LT29i).
I have successfully downgraded the firmware & rooted it. However, I can't seem to find a stock ROM for Xperia TX (LT29i) 7.0.A.3.197 firmware. I just gone through all the hard ways to create a stock ROM myself & successfully flashed it. Perhaps bcuz of the improper build, my WiFi can't be turned on & there might be other problems coming up later.
Now I am also worrying that would it cause any prob to my phone. I followed this guide to create the ROM.
http://forum.xda-developers.com/show....php?t=1931189
& I took the META-INF folder from this custom ROM.
http://forum.xda-developers.com/show....php?t=2040989
Plz kindly help that if there's any resource to the stock ROM or any way to fix this, as well as have a look if there is any side effect from flashing that ROM. Many thanks! ><
You could try the repair phone option in SUS, with will reflash the stock firmware on your phone
One way to fix your problem is to copy /system/lib/modules/prima/prima_wlan.ko to /system/lib/modules/wlan.ko. An issue that I found with this solution, though, is the MAC address I got after copying the .ko file is different from what it was in stock. I can't figure out why. But regardless, your wireless LAN should work after you copy the file.
Montoyatok said:
You could try the repair phone option in SUS, with will reflash the stock firmware on your phone
Click to expand...
Click to collapse
Thx, I'm aware of this option. It's just that I want to know if what I did would create any prob to my phone in future, as well as if there's any stock ROM available on the forum. =)
chibikit said:
One way to fix your problem is to copy /system/lib/modules/prima/prima_wlan.ko to /system/lib/modules/wlan.ko. An issue that I found with this solution, though, is the MAC address I got after copying the .ko file is different from what it was in stock. I can't figure out why. But regardless, your wireless LAN should work after you copy the file.
Click to expand...
Click to collapse
Alright, will try. Thx. =) Do I've to keep the original file at the original location? Btw, is the way I'm building a ROM a proper way to do it? Do u know is there any ready-built stock ROM available?
Look in the very first thread of this section to find an index of every ROM and ftf
Sent from my LT30p xda premium app.
How do I customise the signature on xda premium app?
SCC2002 said:
Thx, I'm aware of this option. It's just that I want to know if what I did would create any prob to my phone in future, as well as if there's any stock ROM available on the forum. =)
Click to expand...
Click to collapse
Links to stock ROM FTFs are available in gregbradley's FAQ here under FTFs. You will need Flashtool to flash these to your phone.
Available stock-based TX ROMs are gregbradley's Assaye and travis82's 240 DPI stock ROM. I haven't tried either since I'm just fiddling about on my own, so I can't tell you how well those work, but Assaye is a good reference if you're trying to build your own stock-based ROM.
Alright, will try. Thx. =) Do I've to keep the original file at the original location?
Click to expand...
Click to collapse
I didn't do anything else except copy the file, so the original prima_wlan.ko is where I found it on my ROM.
Also, I've been watching this thread on similar problems with the Xperia V and a solution has been found. I'm planning on trying it out on my TX some time this week to see if it will solve my MAC address woes.
Btw, is the way I'm building a ROM a proper way to do it?
Click to expand...
Click to collapse
The thread you linked to are instructions on building ROMs for older Xperia phones. Steps 1 - 4 don't need to change for our phones, but the TX uses a different partition scheme (or something), and this means step 5 needs to be different since our system.sin's contents are actually in ext4 format, not YAFFS. A typical Windows installation will not be able to handle the file contents. You can use mounting utilities to read the file and copy them over to your Windows hard drive, but all symbolic file links will basically be destroyed.
Currently, I'm using dsixda's Android Kitchen to build my own stock-based ROM. It's really just a collection of utilities that allows me to make all the necessary file changes and edits that I want before generating a ROM .zip file that can be flashed in CWM. This really needs Linux to work, which is a plus because the file system used by Linux is usually ext4 by default, making it easy to work with the contents of the decrypted system.sin.
If you're planning to build a simple custom ROM, I suggest you read up on how to use dsixda's Kitchen, but keep the following in mind:
- the Kitchen works with a system.img file, which is really just the system.ext4 you get from decrypting system.sin
- the Kitchen will complain about not having a boot.img to work with. Ignore it; I don't think you're building a ROM with a custom kernel, so you don't have to worry about it.
- the default contents of META-INF that the Kitchen generates does not work with CWM for locked bootloaders on the TX. I don't think it works with unlocked bootloaders either. The solution is to stea-... err, borrow the update binary and updater-script from a working ROM zip and edit it for use on yours.
Also, read gregbradley's Assaye ROM thread and TiMiN8R's stock and deodexed ROM thread. They are using dsixda's Kitchen as well, and you can learn a lot about fiddling with stock ROMs from reading about the problems they encountered and how they fixed them.
I'm going to try building a stock-kernel-3.5.3.zip that can be flashed via TWRP for anyone that wants to go back to the stock kernel. I've gone along to a custom kernel that I really like and I was under the mistaken impression that I could restore by restoring boot.img from 3.5.3. I knew there were probably /system/lib/modules that went with the kernels, but I was told otherwise.
Anyway, if you wouldn't mind and you've got a 100% stock 3.5.3 ROM installed with stock kernel, I'd like to get the following files, just one folder, zipped up is fine:
/system/lib/modules/ (the contents of that folder are the files I need). With that I can try to build a stock-kernel-restore.zip file. I've got the boot.img.
Note: I've been a dev of one sort or another for a long time, but I've not done any Android kernel work since pre-marshmallow days and the way TWRP .zip files works, as well as the structure of the install itself (the scripting for the updater) appears to have changed a lot, so I've got a little learning curve ahead of me (unless it's easier than I think). Don't hold your breath waiting for me but I'd greatly appreciate those files.
Many thanks in advance.