I am having a hard time getting Custom ROM's to load in the SDK. I have created a system.img using mkyaffs2 after setting permissions to 777 using CHMOD.
I am stuck on the text ANDROID and I am not able to get any custom roms to boot, including NAND backups of my phone (Incredible running SkyRaider 3.5).
Any help or direction would be greatly appreciated.
If the rom is intended for a device it will never run from the emulator.
You Would need to build a generic system image. Along with that the ram disk, and, the kernel you can use to boot it up
If the image is intended for a device you will need to make that system image into a flashable package. You can use dsixda kitchen to turn the system image into flashable package
Could you describe what you mean by 'load by the sdk'
Pm me if you would like some faster help
Sent from my ADR6300 using Tapatalk
Related
Hi,
I'm hoping somebody can simplify what it is I need to do to get sky go working on my desire.
I've have been reading through the sky go thread and spreadsheet etc but I'm still not clear if it is at is possible to get this app working on my current configuration. I have worked out that I need version 1.5 of gumbalds apk and voodoo ota to hide root but I'm not clear on the kernal bit (if/what I need to do). Hopefully somebody can simplify the steps needed?
My current set up is
Software : Cool Droid v3 gsm
Android version: 2.3.4
Kernal: 2.6.35.14-gingercakes-0.9-avs
Many thanks
ok thanks for your help everybody. Here is what I did to get skygo working on my desire. I think the key is to have a ROM based on an official HTC release and then update the boot.img as per the post at the top of this page
http://forum.xda-developers.com/show...06967&page=174
So the steps I followed:-
1. Make sure my desire is flashed with a Rom based on an official HTC release. I used Cool Droid v3 gsm but it should work with others
2. I then made a nandroid backup of my Rom
3. As per the above link I then downloaded, installed and research how to use the kitchen app.
4. I then connected my phone to pc and copied my system and boot.img files from my clockworkmod backup folder to the relevant kitchen folder on my pc.
5. Using the kitchen app I then made a working copy of my Rom.(this took a while to process) 6. Then from the kitchen advanced menu I unpacked my boot.img this then create a new temporaryfolder on my pc with all the files
7. In Windows explorer I then found the default.prop file and opened it in notepad
8. I updated a line in this file from ro.secure=0 to ro.secure=1 and saved.
9. I went back into the kitchen app and repacked my boot image.
10. In kitchen I then created a rom from the working folder (im was going to flash the Rom but got inpatient)
11. Using explorer I then located the boot.img and copied just this file back to my clockwork backup folder on my phone
12. I then did a restore from recovery in my phone. I got a warning at this point (something about md5um not matching) and I continued with restore.
13. I then hid root using voodoo ota root keeper and checked skygo and whoop whoop all was good
I'm not sure this will work for everyone but it worked for me and I made sure I created copies of my backup files just in case it didn't work...
If anybody requires any further clarity please shout.
Hello all,
I hoping that someone here at xda can help me gain r/w access to the /system folder on a skeye.dart.
This is custom device (google will find it) that has Android ported and is currently running Android 2.1. It has a custom bootloader but will has the functionality to update the Android ROM from the sdcard. I am looking to hack the current ROM (update.img) so that I can write to the /system partition.
This is where the but comes in. Having searched high and low, I found the following thread:
HTML:
http://forum.xda-developers.com/showthread.php?t=1477845
This seemed to be what I needed as I had troubles with any Windows/cygwin process but I I am getting the following message when I try to split the img file:
Code:
[email protected]:~$ perl split_bootimg.pl update.img
Android Magic not found in update.img. Giving up.
I'm hoping someone can throw a bit of light on this for me? I can supply the zip file to anyone who's interested in having a look at this.
SKeye.dart
Just encountered batch of Skeye.dart mobile devices. They are running CE6.0. Is there a path to upgrade? How to convert to Android?
Any hints, ideas, links etc would be appreciated.
Forum:
If this specific question is in another thread, please forgive me and redirect me.
If not, any instruction would be greatly appreciated.
Equipment:
Visual Land, Prestige 7
Model # VL - 107
ICS 4.0.3
Baseband 1.0
Kernel 3.0.8+
Build # 86F5-D1-H1-MO1-1718.20120327
Objective:
To create a backup/recovery img/dump of the existing stock ROM, without having to add "clockwork", "cynogen", etc...
Software on Hand:
Windows 7
Livesuit 1.09
Virtualbox
Ubuntu via Virtual Machine
Please detail everything and speak to me as if I were a little child...
Thanks in advance!
I'm sure you have a recovery on your phone that's a tool to create a backup of stock rom on your sdcard
enter recovery (usually volup+menu or something like that) or you have some options in phone menus to backup device
that will create a set of img files on sdcard that's your backup also you can restore your phone from this backup if you get in trouble
so it's a good idea to have one !
Can this be done with ADB?
ruscan.calin said:
I'm sure you have a recovery on your phone that's a tool to create a backup of stock rom on your sdcard
enter recovery (usually volup+menu or something like that) or you have some options in phone menus to backup device
that will create a set of img files on sdcard that's your backup also you can restore your phone from this backup if you get in trouble
so it's a good idea to have one !
Click to expand...
Click to collapse
That's a negative...
The tablet is completely stock - straight from the box.
In turn, I do not have a recovery (such as clockwork, cyanogen, etc.) that would allow me to make a backup img.
And, I would like to start/learn by making a backup img without such a recovery; i'm assuming this requires using ADB.
Therefore, I need detailed instructions on how to create said backup img...
I have not found any settings or options in the tablet itself that performs this function either.
gth826a said:
That's a negative...
The tablet is completely stock - straight from the box.
In turn, I do not have a recovery (such as clockwork, cyanogen, etc.) that would allow me to make a backup img.
And, I would like to start/learn by making a backup img without such a recovery; i'm assuming this requires using ADB.
Therefore, I need detailed instructions on how to create said backup img...
I have not found any settings or options in the tablet itself that performs this function either.
Click to expand...
Click to collapse
I understand now this is a tablet so it's common problem for some
well you have to find a way to root device to get access to system files then use a rom dumping tool just take a look here or here
nobody can tell you for sure how to do that this is device specific I do not know to much about that particular tablet just try
I just got this tablet today, and it's rooted out of the box.
Not sure if that helps you, but I wanted to contribute if I could.
[signature]
Recovery for Galaxy Ace 2 - i8160
Hi,
Any chance of a simple recovery for the Galaxy Ace2 i8160 ?
VL107 Update Down To 4.0.3/4.0.4
Hello,
I've been trying to figure out how to change my VL-107's OS, and a Recognized Contributor pointed me to this thread.
I've downloaded LiveSuit, but I can't figure out how to make it work. If at all possible, I need two things: an .img file for 4.0.3 or 4.0.4, and instructions on how to apply this update via command prompt or a program that utilizes command prompt.
I have Windows 8.1, my VL-107 (Visual Land Prestige 7), and LiveSuit (which I'd really rather not use).
The only experience I have in flashing involved using command prompt, and I'm much more comfortable doing this than relying on a program to do everything "behind the scenes". Otherwise, I would also be willing to put an .img file on my tablet's "SD card" and apply the update through Recovery mode.
This is my list of question's that apparently are complexMost EVERYTHING I've learned about android i've had to teach myself & while i'm fairly intelligent self-taught can be painfull & slow at times, with the exception of Marc12868 over at Android forums & a few other fellas, he took the time to teach me how to decompile & such. Anyway here's my questions:1) Need help with writing custom update-script for added apps & mods.2) How do I repack our kernel with a different recovery ?3) How do I extract recovery via ADB ? (Yes I know how to use ADB)4) How do I root the stock rom when its an Odin.tar file ?*5) What the hell does kernel panic mode do ?6) Splitting & rebuilding images, Zimage's, & tar files ?7) How do I extract our inframits ?So if anybody wants to help me out with these questions that would be great.
jaaydogg said:
Anyway here's my questions:
1) Need help with writing custom update-script for added apps & mods.
2) How do I repack our kernel with a different recovery ?
3) How do I extract recovery via ADB ? (Yes I know how to use ADB)
4) How do I root the stock rom when its an Odin.tar file ?*
5) What the hell does kernel panic mode do ?
6) Splitting & rebuilding images, Zimage's, & tar files ?
7) How do I extract our inframits ?
So if anybody wants to help me out with these questions that would be great.
Click to expand...
Click to collapse
I'll answer what I can - keep in mind it's a learning process for all of us!
1) I'll defer to someone else.
2) You'll need a repack tool to do it. You basically unpack, replace recovery components in ramdisk and restuff the ramdisk back in. Easier if we have source because then you have visibility of the whole picture.
Believe this is available.
3) You'll need to run this command under root:
dd if=/dev/block/mmcblk0p5 of=/sdcard/zImage_dump
4) There are two main ways. Inject root - modifying the image contents without flashing or a flash/root/dump method.
5) I'll defer to someone else
6) All of that requires a Linux box and tools readily available on XDA.
Each one has its own steps.
7) See #2.
The updater-script is very easy to modify/write. My suggestion is to take a look at other updater-script files and see how they are set up, how they are calling commands. Then use Notepad++ to make changes to the script.
Sent from my Slim E4GT using xda premium
You guys are good, I think I'm going to be picking up some android schooling. :thumbup:
Pp.:thumbup:
Transmitted from another Galaxy.
XDA University is available to those that want to learn about development.
http://xda-university.com/
Sent from my Slim E4GT using xda premium
As of build LCA44B the /system partition is no longer ext4, but squashFS. As I understand it this is a read-only file system, and there's no way to mount it as r/w.
Is it possible to somehow achieve root anyway? I've tried to extract the system.img from the LCA44B OTA package, and then converting it to ext4 to be able to fastboot flash it. That didn't work and I don't know if it's because it's impossible to do, because I did something wrong or because I'm on a windows machine with cygwin/ported UNIX tools binaries.
I've been struggling with this for the last couple of days, and I started out with absolutely 0 knowledge about anything regarding this kind of stuff. I still don't know enough to figure it out, but if anyone could point me in the right direction I think I might be able to.
Any help or knowledge is appreciated!
Latest thing I've tried:
1. Running sdat2img on the .dat files in the LCA44B OTA.
2. Running unsquashfs on the .img that sdat2img created to be able to make changes.
3. Adding su binaries and other files needed for root to the working directory.
4. Running mksquashfs on the working directory.
5. Flashing the new .img using Motorola's fastboot.
I really don't understand why this isn't working. Unless there's some hidden error in any of the tools I'm using, or if the bootloader somehow reacts to the fact the the new system.img is a few kb larger than the old one, I don't see a reason as to why this shouldn't work. What happens when I reboot after flashing is: The watch starts booting, showing the Motorola logo and vibrating for a split second. It then, instead of continuing to the bootanimation, reboots into recovery. The only thing I can see from there is that it seems to have a problem with mounting the cache partition.
Again, any help or knowledge is appreciated.
Sent from my A0001 using Tapatalk