Here is the system dump from the Motorola Droid ERIS for developers:
* Download zip HERE *
CAUTION: This is not a phone image, so please DO NOT try to flash your phone with it!
I know XDA guys can cook good things with system dumps
source androidspin
First of all, its the HTC Droid Eris. Not motorola. Second this is just copied and pasted, and third its just an extracted system.img from the firmware update. Meaning you can't do anything with it, as you need some of the info encoded in the system.img file.......
Related
I found this on http://cliq-development.com/forums/viewtopic.php?f=5&t=13
hopefully this can help anyone who is trying to develop a way for root on the cliq.
To get where we are at in development you must learn about a few things
.SHX = A re-flashing file similar to a .nbh on the HTC brand. It is a full re-flash of everything on the phone, full stock. When extracted it creates three files the main one is the CG2
CG2 = A file extracted from the shx that hold the main partitions that will be flashed to the phone.
-----------------------------------------------------------------------------------------------------------------------
How to extract a shx
(http://modmymoto.com/forums/showthread.php?t=525344)
A developer by the name of Meiner Einer created a program named SbfRecalc. With this program we can extract three files and as i stated above the most important one is the CG2
How to extract a CG2
(http://modmymoto.com/forums/showthread.php?t=525477)
A developer by the name of Skrilax_CZ created a program named CG2 Parser. With this program we can extract all of the files within the CG2.
-----------------------------------------------------------------------------------------------------------------------
After you extract all of the files from the CG2 you will find that some of the names were similer to the partitions of the cliq. With a little file manipulation i recreated a boot.img and a recovery.img from some of the files. The guys over at modmymoto dumped a full system partition.
(http://android-dls.com/wiki/index.php?t ... oot_Images)
To recreate both the boot.img and the recovery.img just do these simple steps
1. Create a directory and put either bootsec.mbn or recoverysec.mbn from the CG2 dump inside it
2. Download the split_bootimg.pl from the link above and run it with the file in the directory to get both a kernel and a ramdisk file.
3. Using the mkbootimg from the android source code you can recombine the kernel and the ramdisk files to create your boot.img/recovery.img strait from the re-flash file
------------------------------------------------------------------------------------------------------------------------
With the system dump from modmymoto and my boot.img(+a little root) I created an update.zip file with root ready to be flashed when the keys are ready.
This is where we are at any help would be greatly appreciated.
Wow, nice work!
This could really so with a sticky...
Thanks for the update! The cliq goes hard. Once rooted its ova, best android phone on tmo!
Nice! It would be really great if you could repost this at android-devs.org over in the cliq development section of the forum
Since XDA is only for HTC phones and most people here most likely don't have the cliq and there really isn't a correct forum to have this posted in..
I'd reccomend using android-devs.org forums
I couldnt get my system to update because the build prop was not the right cheksum. I found links to the default system and got a dump. If you are getting checksum errors on files. try to replace with these. For those how need it.
So this is a sys dump so far that I was able to get.
http://www.ti-x.com/files/roms/Acer-a500/acersysdump.7z full dump with everything I could get access to so far
http://www.ti-x.com/files/roms/Acer-a500/Acer-A500.7z deodex and odex app/framework
gravyplaya said:
I couldnt get my system to update because the build prop was not the right cheksum. I found links to the default system and got a dump. If you are getting checksum errors on files. try to replace with these. For those how need it.
So this is a sys dump so far that I was able to get.
http://www.ti-x.com/files/roms/Acer-a500/acersysdump.7z full dump with everything I could get access to so far
http://www.ti-x.com/files/roms/Acer-a500/Acer-A500.7z deodex and odex app/framework
Click to expand...
Click to collapse
Where are you located? US. If in US. can you dump the boot.img and flexrom.img if you havent already updated.
could you please dump your .img's I could really use the
Boot.img
Flexrom.img
System.img
You have the same firmware I have so I can get back to true stock. It will help a lot of other people out as well. If your unsure how I can give you the commands to dump each individual image to your SD card.
Hi,
I readed this
http://forum.xda-developers.com/showthread.php?t=1041572
then I had an idea that is just simple
I got tired with my att atrix for many months now we can't flash any sbf on that phone.
I suggest that people dump data and system files and all other folders for all the sbfs that are shared.
that is as simple as it is, after that we just need to update the folders and files over the old ones.
I will also try myself to extract contents inside the .smg files of sbfs using linux but I can not garantee it will work since I don't know what is the real file format of current atix smgs right now.
I will create a shell script that will do the job easily and I need people that have Bell atrix, Europe Atrix, Latin atrix or Asia Atrix.
If we succesfully overwritte those folders and files on our phones, I'm pretty sure that future update will also work since update.zip is just looking for right files on the phones and not checking for 1init bootloader version.
Who would like to participate and try?
for those who have questions, feel free to ask me
extract sbf
rename CG57.smg to system.img
use kitchen to make a update zip
or
make a nandroid backup
use system.img from clockwork/backup folder
use in kitchen to create update.zip
Hi,
i would like to know how i could get my stock rom from my N4, like a .zip file. Because i tried nandroid, but i would like to modify the rom with the kitchen, and i don't know how to do if i don't have a zip file... Thanks !
AutruiP said:
Hi,
i would like to know how i could get my stock rom from my N4, like a .zip file. Because i tried nandroid, but i would like to modify the rom with the kitchen, and i don't know how to do if i don't have a zip file... Thanks !
Click to expand...
Click to collapse
You should be able to extract the boot and system images from Google's factory image.
https://developers.google.com/android/nexus/images#occam
I wasn't aware that the kitchen worked with the Nexus 4 as its still listed as one of the unsupported devices but the thread hasn't been updated since October of last year so maybe that changed.
this is copied from dsixda's kitchen thread (http://forum.xda-developers.com/showthread.php?t=633246 post #3):
How do I import a ROM into the kitchen to use as my base?
(The instructions below are for HTC devices in general. For other devices, please visit the appropriate thread.)
From a shipped ROM:
First, find the shipped ROM for your device, usually from htc.com or from searching xda-developers (check the Wiki or sticky posts under your device's sub-forum).
This link may help: Various devices
Please don't ask me for links, as I don't know everything or own all devices.
The shipped ROM can be found in three different formats. Identify the type you have downloaded:
If the shipped ROM is in a .ZIP format, then simply copy it to the kitchen's original_update folder.
OR if the shipped ROM consists of system.img and boot.img files, then copy those two files to the kitchen's original_update folder. If the ROM also includes a lib.img (found in some newer HTC ROMs), then copy that as well!
OR if the shipped ROM is in an .EXE format, then do the following:
In Windows, run the shipped ROM's .EXE file till it gets to the first dialog. Stop there but don't close the window yet.
Go to Start->Run and type: %TEMP%
When the folder opens, search for Rom.zip (use the "magnifying glass" Search button)
Copy Rom.zip to your kitchen's original_update folder
OR from a cooked/custom ROM:
Copy the update.zip (or equivalent ZIP file) to your kitchen's original_update folder
OR from a Nandroid backup (under /sdcard/nandroid) [NOT RECOMMENDED FOR NON-STOCK ROM BACKUPS]:
Copy the system.img and boot.img files from the backup folder to your kitchen's original_update folder
Hm, i see. But the problem with the dev links for Google is that it's 4.2.2 and not 4.2.1... I would like to stay to an older version for the moment, with those problems with bootloaders, kernels etc... I will try with system and boot img, thanks !
Sent from my Blade S using xda app-developers app
Well, i tried to use the tutorial about shipped rom, but my system.img and boot.img files aren't recognized by the kitchen... So i don't know how to do Halp ?
In this thread you have posted link to factory image with android 4.2.1 http://forum.xda-developers.com/showthread.php?t=2145848
Great !! Thanks a lot eskeyy !
Hi all,
The usual DISCLAIMER: I am in no way responsible for any and all damage the following does to your phone.
I'm new to this whole flashing ROM business, having started by flashing stock Lollipop upgrade to my LG G3 as I was using it on Ultra Mobile and therefore wasn't getting OTA updates. I've now done the same with my brand new Moto Maxx (US) xt1250, which has the exact same phone as the xt1254 (as I'm sure all of you know but it bears repeating just in case).
I found the easiest way to install all of the upgrades to Lollipop from stock Kitkat was just to download these files:
http://rootjunkysdl.com/files/?dir=Droid Turbo/Firmware
I then extracted them into ADB + Fastboot folder one at a time, going in this order:
VRZ_XT1254_KDF21.128-15_15_CFC.xml.zip
VRZ_XT1254_SU2-12_12_CFC.xml.zip
VRZ_XT1254_SU3TL-38_38_CFC.xml.zip
VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
After copying the first group of files into the ADB/fastboot folder and starting up my phone in bootloader, I'd simply click on the batch file for that group (for example the VRZ_XT1254_KDF21.128-15_15_CFC.bat file) to install the first Rom. Then I'd unzip the files for the second lot xml files, allow it to replace the files that had the same name, and then click on the batch file for that Rom.
However, all this was a bit tedious, and I imagine that some people might like to be able to just go direct to the latest 5.1 OTA of stock verizon without all this copying and pasting. So I renamed the files for the first xml batch with a "1" in front, the second with a "2" and so on, and renamed all the commands in the batch xml files to include these modifications. I then put all of the batch file commands together, but also removed some of the unnecessary commands (like "pause", "%fastboot% oem fb_mode_set" and "%fastboot% oem fb_mode_clear") to give you one single batch file.
IN SUMMARY:
I have at your disposal all of the images with modified names, and a single batch command that'll install the upgrades sequentially, which you can do by simply copying all of these files into adb/fastboot folder and clicking on "VRZallupgrades".
I tested this on my droid, and it works great!
My question is this: Would anyone find this helpful? I'm currently uploading all 8GB of files to mega.nz on ****ty hotel internet, but it should be done by tomorrow morning.
Rhuagh3 said:
Hi all,
The usual DISCLAIMER: I am in no way responsible for any and all damage the following does to your phone.
I'm new to this whole flashing ROM business, having started by flashing stock Lollipop upgrade to my LG G3 as I was using it on Ultra Mobile and therefore wasn't getting OTA updates. I've now done the same with my brand new Moto Maxx (US) xt1250, which has the exact same phone as the xt1254 (as I'm sure all of you know but it bears repeating just in case).
I found the easiest way to install all of the upgrades to Lollipop from stock Kitkat was just to download these files:
http://rootjunkysdl.com/files/?dir=Droid Turbo/Firmware
I then extracted them into ADB + Fastboot folder one at a time, going in this order:
VRZ_XT1254_KDF21.128-15_15_CFC.xml.zip
VRZ_XT1254_SU2-12_12_CFC.xml.zip
VRZ_XT1254_SU3TL-38_38_CFC.xml.zip
VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
After copying the first group of files into the ADB/fastboot folder and starting up my phone in bootloader, I'd simply click on the batch file for that group (for example the VRZ_XT1254_KDF21.128-15_15_CFC.bat file) to install the first Rom. Then I'd unzip the files for the second lot xml files, allow it to replace the files that had the same name, and then click on the batch file for that Rom.
However, all this was a bit tedious, and I imagine that some people might like to be able to just go direct to the latest 5.1 OTA of stock verizon without all this copying and pasting. So I renamed the files for the first xml batch with a "1" in front, the second with a "2" and so on, and renamed all the commands in the batch xml files to include these modifications. I then put all of the batch file commands together, but also removed some of the unnecessary commands (like "pause", "%fastboot% oem fb_mode_set" and "%fastboot% oem fb_mode_clear") to give you one single batch file.
IN SUMMARY:
I have at your disposal all of the images with modified names, and a single batch command that'll install the upgrades sequentially, which you can do by simply copying all of these files into adb/fastboot folder and clicking on "VRZallupgrades".
I tested this on my droid, and it works great!
My question is this: Would anyone find this helpful? I'm currently uploading all 8GB of files to mega.nz on ****ty hotel internet, but it should be done by tomorrow morning.
Click to expand...
Click to collapse
It is not necessary to flash anything other than VRZ_XT1254_SU4TL-44_44_CFC.xml.zip. This file contains the full firmware package and does not need previous updates to build upon.
TheSt33v said:
It is not necessary to flash anything other than VRZ_XT1254_SU4TL-44_44_CFC.xml.zip. This file contains the full firmware package and does not need previous updates to build upon.
Click to expand...
Click to collapse
seriously? Wow. major noob moment. With my Lg G3 it definitely wasn't possible to flash straight to 5.1
Thanks for the heads up