pdocwrite can write the dumped ROM image to Hermes-FlashROM.
(Hermes-FlashROM is m-sys tffs chip).
Is there any person who had actually written the partition data obtained by pdocread in hermes?
now,I Upload the "SoftBank X01HT Dumped Image"!!
Is there any person who can change this image into NBH format?
yoshito tagashira said:
pdocwrite can write the dumped ROM image to Hermes-FlashROM. (Hermes-FlashROM is m-sys tffs chip).
Click to expand...
Click to collapse
Sorry to say that hermes uses NAND flash (Samsung K5D5657) and not m-sys disc-on-chip. pdocwrite can't wirte to this type of flash.
yoshito tagashira said:
Is there any person who had actually written the partition data obtained by pdocread in hermes?
Click to expand...
Click to collapse
None that I know.
yoshito tagashira said:
now,I Upload the "SoftBank X01HT Dumped Image"!!
Is there any person who can change this image into NBH format?
Click to expand...
Click to collapse
Create an NBH is easy, sign the NBH so that it can be flashed into device without getting an "invalid cert" error... is not possible unless you have HTC private key or you patch the SPL to use your own certificate.
Nand Flash ?
Hi Pof
Thanks res to me!
If what is necessary is just to write a raw image to Flash,There is a method.
Surely, the WInCE version for "iPAQ-Linux bootloader-source" can be used.
There is much source of a CFI interface about Flash writing.
Now,I am just using X01HT By Docomo firmware as HTCz.
Do you mean you rewrite imgfs on X01HT using HTCz extracted raw image? Can you post step-by-step instructions?
CFI write
The following is my opinion.
It cannot actually judge whether it is possible.......
For example, in Linux, if the MTD driver for FlashROM is installed in the system, the contents of FlashROM can be written by the dd command.
I think it possible to make the program which can perform this on WinCE.
If the raw data which I extracted from X01HT using "pdocread" comes to correct, this data can be returned to an original state by writing in simply on CFI type ROM.
is it?
yoshito tagashira said:
The following is my opinion.
It cannot actually judge whether it is possible.......
For example, in Linux, if the MTD driver for FlashROM is installed in the system, the contents of FlashROM can be written by the dd command.
Click to expand...
Click to collapse
Right, the MTD subsystem allows you to do this, dd just does a raw copy.
yoshito tagashira said:
I think it possible to make the program which can perform this on WinCE.
Click to expand...
Click to collapse
I'm not wince programmer, but i guess it should be possible, there are such programs for windows plaform (rawrite.exe or psdwrite.exe from itsme).
yoshito tagashira said:
If the raw data which I extracted from X01HT using "pdocread" comes to correct, this data can be returned to an original state by writing in simply on CFI type ROM.
is it?
Click to expand...
Click to collapse
I'm not sure if you can 'hot-overwrite' it while the device is running wince, i'm not an expert in that area... probably itsme (the author of itsutils) can point you to the right direction on this.
pdocread
■Outline
pdocread and pdocwrite are delivering the command to the itutils.dll thread which moves on wince.
It seems that the reading and writing which went via WindowsAPI will be performed if -w option is attached to pdocread.
Therefore, it can be said that the raw data read by pdocread is reflecting the contents of FlashROM as it is.
However, when pdocwrite writes in FlashSOM via ituils.dll, the WinCE itself will rewrite itself.
"An act which replaces the head, living "->Danger
It seems that there are all contents of FlashROM in a NBH file.
But IPL is an OneTimeProgramr Aria.-> CanNot rewrite?!?!
What NBH contains IPL?
Since I want to use HermesOS of SoftBank somewhat newer than HermesOS of Docomo, I want to rewrite WM5.0 carried in SoftBank.
the product made from SoftBakk -- I want to kill that annoying SIM check thread from X01HT
If bootloader is started via mtty, although it will think that FlashROM can be rewritten directly ???
yoshito tagashira said:
For example, in Linux, if the MTD driver for FlashROM is installed in the system, the contents of FlashROM can be written by the dd command.
I think it possible to make the program which can perform this on WinCE.
Click to expand...
Click to collapse
It will be better to make Linux work on hermes
Related
Hi,
This is for those folks which have a special mainsplash/subsplash on their device which is not available in any .nbh and want to backup them (for example because you want to load another rom and need them in case of warranty or you simply want to put them back onto the device after flashing a different rom.
I wrote a little perl program which communicates to the device the over tty.
This means you have to setup your device in your linux as a tty device (needs some kernel drivers), normally it will be /dev/ttyUSB0. You also have to install the perl Module Device::SerialPort.
after that put your device into bootloader mode, connect to USB cable and run "perl splash_dumper.pl /dev/ttyUSB0" (or whatever your tty device name is).
This creates the two files mainsplash.nb and subplash.nb which can be used with rombaker to create a .nbh which can be flashed to the device.
Maybe someone else will also port the script to activestate perl for windows but I don't know exactly how to do it. All I can say is that you have to use Win32::SerialPort but I don't know how to make the device available as virtual serial device.
hope this helps some people.
nice work! thanks
verry cool..!
Thanks again
So, I've been reading a bit about how to install 2.2 on my g1. My initial impressions as a first time rooter is that it is a bit complicated. I really would like to know what I'm doing in case anything goes wrong. However, I've been a bit frustrated by any of the information I've found on google about it. Most of the tutorials only tell you what to do without explaining why you are doing it. Any explanations about how things works have been pretty brief and not much goes into how each piece of the android system relates to the other.
I'm going to run through my trouble points with learning it and if someone could jump in and explain any one of these things it would help me out a lot and hopefully other people as well.
There are (at least?) 4 main parts you need to be concerned with when installing a custom rom:
-the custom rom itself
I'm not totally sure of everything that goes into this. All the java stuff I'm guessing. Dalvik vm? Maybe the linux kernel? Some c libs too? busybox? Some other stuff?
-the spl.. aka second program loader.. I found the following explanation for this one:
Second Program Loader, in conjunction with the IPL comprise a device's bootloader. Aside from bootstrapping Android, the bootloader also fulfills various diagnostic functions. One of these functions is the manipulation of data in the device's internal flash ram. Depending on the SPL installed, the user can apply a signed NBH file, flash nand images, and more. Note that the SPL is installed and operates independently of the Android build that runs atop it. (Hold down the Camera button while the phone is booting to enter the SPL.)
Click to expand...
Click to collapse
Seems fairly straightforward. How does the IPL factor into this though? Why is the IPL typically not a concern when installing roms? What is a nbh? How does a nbh relate to a .img? Why does this get flashed?
-the radio.. i have no idea what this one is for.. references to it typically seem to be vague and mysteriousi have heard it is quote "the easiest way to brick your phone" which leads me to believe it is important. Appearantly danger SPL will kill you if you dare mess with it. This scares me because I dont really even know what it is so how am i supposed to know if I'm messing with it?
I have heard this description:
"radio.img is a image of partition table + several partitions, which are defined in the header.
You can open the file in hex editor and see it (starting at 0x18 offset):
MAGIC-NOTHING2DO: does nothing
OTA-QCSBL-UPDATE: updates qcsblhd_cfgdata.mbn and qcsblsec.mbn
OTA-OMSBL-UPDATE: updates oemsblhd.mbn and oemsblsec.mbn
OTA-RADIO-UPDATE: updates amsshd.mbn and amsssec.mbn (the actual baseband firmware)
OTA-APSBL-UPDATE: updates appsboothd.mbn and appsbootsec.mbn
OTA-CEFS--UPDATE: updates cefs.mbn (on some radio.img files this is done implicitly)"
Click to expand...
Click to collapse
What is this talking about? How do the partitions relate to what goes on when you are installing a rom? What is it used for? Why are there so many versions of it? Why?!
Finally:
-the recovery.img - this one is also a shroud of mystery to me. I'm not sure how it relates to the spl and it seems like sometimes you use this to install updates and sometimes you use the spl. I'm just not really sure how this factors into things.
This also seems to be involved a lot in things like 'repairing ext file systems' etc. What ext file system is it repairing? The sd card? The internal storage? Why are you supposed to repair it?
I have more questions but I will leave it at this. Thoughts anyone?
This is a very short guide for all of you looking to dual boot android from the sd card now that you have windows phone 7 taking up the nand space. It's originally posted by letama and I added a bit to it.
It's actually quite simple. All you have to do is add nand_init to one line in the init.rc file. For most builds, you will need to use a linux distro and mount the rootfs.img file, then edit the init rc file, add nand_init to this line:
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0
so it looks like this
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init
For builds that uses the cedesmith initrd method, you have to mount the system.ext2 file, everything else is the same.
Save your file. Make sure you haven't changed the permissions and unmount the image. Copy the build to your microsd, set magldr to boot from the directory you copied it to and boot ad sd, you should be good to go.
Problems: booting it this way does not read from your startup.txt, you have to wait for cotulla to add it in future magldr. I'm not sure if the old method of updating (dumping everything in a folder named root) still works.
Disclaimer: I've tried this with jdms, hd2one, superram, desire_hd2 and mdj rEVOlution 2.3 and they all work fine with my old data image, your mileage may vary. This is a very quick guide because that's all I know Anymore I'll have to search google, so you might as well do that yourself Anyone who have a better method of editing feel free to post it. I'll add it here if you post it in this thread.
Tip from aled99 to edit without linux.
Corias said:
I've managed to mount system.ext2 to Windows 7. Without VM and Linux at all.
What tools are needed:
1. Windows Ext2/Ext3 driver. You can get it from here.
2. Any software to mount image to virtual drive. I've used Gizmo Drive, but there are others also working.
Tip: Gizmo doesn't show ext2 as supportable image type, when you browse for image. So, manually type *.* filter.
Click to expand...
Click to collapse
Some files that are already edited:
CoreDroid HD 0.4 edited by ricola7
Desire_hd2 system.ext2 file
HD2ONE 0.3.5 system.ext2
JDMS 1.62
MDJ HD v4.6
MDJ rEVOlution 2.3 rootfs.img
NexusHD2-FRG83D v1.8 from nzxtneo
Superram 1.5 from letama
Builds that already work with magldr:
DL DesireZ v2.2 from dandiest
HD2 Gingerbread/CyanogenMod7 from copenhagen
Is this a method to boot a NAND Rom from SD Card without flashing?
blax123 said:
Is this a method to boot a NAND Rom from SD Card without flashing?
Click to expand...
Click to collapse
No it boots the sd builds from this subforum. Not the nand builds.
will this work if I have android in my nand, and want to run a different android off of sd card? Like if I wanna test drive gingerbread roms off the sd, while sticking with a froyo based rom in nand? I really want to do this.
izzy spun said:
will this work if I have android in my nand, and want to run a different android off of sd card? Like if I wanna test drive gingerbread roms off the sd, while sticking with a froyo based rom in nand? I really want to do this.
Click to expand...
Click to collapse
I haven't tried copenhagen's build but it should work the same way. Try it and let us know how it worked out
Edit: Actually I got curious and checked it out. Copenhagen's build does not require editing. You can boot it from sd using magldr as it is. Nice too. I think I'll play with that for a while
Sorry but I'm stuck on the first line. What is a linux distro? How do I edit the line? I'll be able to take care of the rest. This is the part that confuses me.
buzz killington said:
This is a very short guide for all of you looking to dual boot android from the sd card now that you have windows phone 7 taking up the nand space. It's originally posted by letama and I added a bit to it.
It's actually quite simple. All you have to do is add nand_init to one line in the init.rc file. For most builds, you will need to use a linux distro and mount the rootfs.img file, then edit the init rc file, add nand_init to this line:
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0
so it looks like this
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init
For builds that uses the cedesmith initrd method, you have to mount the system.ext2 file, everything else is the same.
Save your file. Make sure you haven't changed the permissions and unmount the image. Copy the build to your microsd, set magldr to boot from the directory you copied it to and boot ad sd, you should be good to go.
Problems: booting it this way does not read from your startup.txt, you have to wait for cotulla to add it in future magldr. I'm not sure if the old method of updating (dumping everything in a folder named root) still works.
Disclaimer: I've tried this with jdms, hd2one, superram, desire_hd2 and mdj rEVOlution 2.3 and they all work fine with my old data image, your mileage may vary. This is a very quick guide because that's all I know Anymore I'll have to search google, so you might as well do that yourself Anyone who have a better method of editing feel free to post it. I'll add it here if you post it in this thread.
Click to expand...
Click to collapse
thanks.. so i must use linux? any tools available in win?
buzz killington said:
I haven't tried copenhagen's build but it should work the same way. Try it and let us know how it worked out
Edit: Actually I got curious and checked it out. Copenhagen's build does not require editing. You can boot it from sd using magldr as it is. Nice too. I think I'll play with that for a while
Click to expand...
Click to collapse
can you elaborate on this please.
can you give a step by step.
i am real interested in trying this.
thanks in advance.
Anthonayy said:
Sorry but I'm stuck on the first line. What is a linux distro? How do I edit the line? I'll be able to take care of the rest. This is the part that confuses me.
Click to expand...
Click to collapse
It's just short for Linux distribution, such as ubuntu or redhat. I used ubuntu. Once you have it mounted you can use any text editor available.
vista1984 said:
thanks.. so i must use linux? any tools available in win?
Click to expand...
Click to collapse
Sorry, I don't know if there are. Maybe others can chime in. Anything that'll let you mount an ext2 image and edit its contents will do. Unfortunately I'm not familiar with any windows tools.
Will this hack enable me to run Android from my SD card, with WP7 installed on the phone?
I just want to make sure, because I've been searching around, and several indidual sources have said that WP7 doesn't recognize any SD cards, including compatible SD cards.
I would really love to try WP7, but without losing my android.
Sent from my HTC HD2 using XDA App
WOOZ!E said:
Will this hack enable me to run Android from my SD card, with WP7 installed on the phone?
I just want to make sure, because I've been searching around, and several indidual sources have said that WP7 doesn't recognize any SD cards, including compatible SD cards.
I would really love to try WP7, but without losing my android.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Dude, it has nothing to do with WP7, You boot Android from MAGLDR not WP7. So you would either use a different SD card to boot into Android BEFORE booting windows or you would partition your SD card in a way that it allows you to use it for WP7 and Android at same time.
How can I mount the system.ext2 by using terminal?
Code:
[email protected]# mount -o loop system.ext2 /mnt
system.ext2: No such file or directory
asdfg2010 said:
How can I mount the system.ext2 by using terminal?
Code:
[email protected]# mount -o loop system.ext2 /mnt
system.ext2: No such file or directory
Click to expand...
Click to collapse
you have to specify where your file is and I believe you have to create a mount point, you can't just put it in /mnt. Somebody correct me if I'm wrong
Code:
cd /mnt
sudo mkdir sys
sudo mount -o loop -t ext2 /home/usr/Desktop/system.ext2 /mnt/sys
buzz killington said:
you have to specify where your file is and I believe you have to create a mount point, you can't just put it in /mnt. Somebody correct me if I'm wrong
Code:
cd /mnt
sudo mkdir sys
sudo mount -o loop -t ext2 /home/usr/Desktop/system.ext2 /mnt/sys
Click to expand...
Click to collapse
I try but not successful
windows ext2 editing
buzz killington said:
It's just short for Linux distribution, such as ubuntu or redhat. I used ubuntu. Once you have it mounted you can use any text editor available.
Sorry, I don't know if there are. Maybe others can chime in. Anything that'll let you mount an ext2 image and edit its contents will do. Unfortunately I'm not familiar with any windows tools.
Click to expand...
Click to collapse
I think you can edit an ext2 image with windows using the method in post #4 from this thread: http://forum.xda-developers.com/showthread.php?t=808169
Corias said:
I've managed to mount system.ext2 to Windows 7. Without VM and Linux at all.
What tools are needed:
1. Windows Ext2/Ext3 driver. You can get it from here.
2. Any software to mount image to virtual drive. I've used Gizmo Drive, but there are others also working.
Tip: Gizmo doesn't show ext2 as supportable image type, when you browse for image. So, manually type *.* filter.
Click to expand...
Click to collapse
I've tried editing the file and it seemed to save the changes, but I haven't tried booting android yet.
I am trying to do this method in super ram Rom but no success. I have successfully mount system.ext2 but there wasn't any init.rc file. After a lot Google search I have managed to discover that this file is in file initrd.gz and I made the change. But the build starts and hangs in first screen.any suggestion;
Sent from my HTC HD2 using Tapatalk
can anyone uploade the files? i dont have linux..
Cool, thanks! I seems to be working for me with MDJ FroYo HD v4.6. Has anyone had any success getting two Android ROMs running from their microSD card? I was doing this when booting from WM6.5 by putting them in different directories and modifying rel_path in the startup.txt for one of them, but obviously this method won't work until MAGLDR supports startup.txt...
clio94 said:
I am trying to do this method in super ram Rom but no success. I have successfully mount system.ext2 but there wasn't any init.rc file. After a lot Google search I have managed to discover that this file is in file initrd.gz and I made the change. But the build starts and hangs in first screen.any suggestion;
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
I didn't do the superram built myself, but letama posted a full version later in that magldr thread. Try to see if you can find it. If not I'm sure I still have it somewhere I can post it for you.
You can change Android folder on SD using MAGLDR
Enter Magldr
Select 9. Services
then 1. BootSettings
then 3. AD SD Dir
Hi
I've done a bit of searching but can't find anything too specific to what I'm trying to do. Basically we have 10 Android tablets, and I want to make them all standardised e.g. have the same Apps on, configured in the same way (e.g. enterprise wireless network added).
Now the thing is if anyone messes around with them I want a really easy way to restore them to the original config which I've done.
One way I thought was to configure one fully, install Titanium Backup on it, do a full backup of apps/system data etc, and put the backup onto an SD card. Then I already have the base ROM on an SD card so if theres any problems, I can just flash the ROM over it again, install TB, and restore all the data. Would this be suitable to do to duplicate the data onto 10 tablets, and also restore the data if required?
The other thing I looked into was customising a ROM myself, don't want to do anything too tricky it'll just be a case of removing all the preinstalled crap I don't want, preloading the Apps we do want, and if possible preloading the wireless key and getting rid of the first boot initial set up wizard.
PS I've looked at installing CWM and doing whole image backups, but supposedly the tablet isnt supported (its an Ainol Novo 7 Elf 2)
Any advice would be great, hopefully theres some fairly straight forward way of managing this
Thanks
One of the reasons I integrated a full blown GNU/Linux on my devices, was the need to run full and automated backups. If you are looking into the possibility making a custom ROM, this might be a solution for you as well. I'm using BackuPC to run backups nightly, backing them up as any other GNU/Linux machine (using tar over ssh).
See the link in my signature for more information about this.
kuisma said:
One of the reasons I integrated a full blown GNU/Linux on my devices, was the need to run full and automated backups. If you are looking into the possibility making a custom ROM, this might be a solution for you as well. I'm using BackuPC to run backups nightly, backing them up as any other GNU/Linux machine (using tar over ssh).
See the link in my signature for more information about this.
Click to expand...
Click to collapse
Hi
Thanks for the reply, not too sure this would be the right option for us. I don't really need to take nightly backups, I just need to make a backup of a preconfigured image, and then put that image onto 10 other devices. Then I want to keep the original backup and have an easy way to restore it onto any devices which have been messed up. Sort of like image cloning for PCs, I want to prepare a base image, and then flash it over all the devices.
fro5tie said:
Hi
Thanks for the reply, not too sure this would be the right option for us. I don't really need to take nightly backups, I just need to make a backup of a preconfigured image, and then put that image onto 10 other devices. Then I want to keep the original backup and have an easy way to restore it onto any devices which have been messed up. Sort of like image cloning for PCs, I want to prepare a base image, and then flash it over all the devices.
Click to expand...
Click to collapse
Ok, I see. Compile the image to you likings (boot image and system partition), and then flash it using fastboot onto you devices.
Hi
Does anyone have any more thoughts on this?
I have experimented with Titanium Backup and this seems to work quite well. I have installed a ROM, and customised it e.g. installed the apps I need and configured the apps, wireless settings and home screens etc. Then I do a full apps + system backup in TB to my SD card.
Then the plan is, I can reflash the ROM onto the other device, install TB and then restore this backup. This saves my user state and wireless settings etc.
Only problems is when I flash the ROM, I have to go through all the initial set up again and also remove some preinstalled apps which I dont want. Any ways around this?
There must be something I'm missing. Why don't you install the device, walk through the setup, remove the bloatware you don't want and then dumps the disk partitions into images you flash the other devices with using fastboot? This way you'll get'em cloned, isn't it this you want..?
Of course there's still some tinkering needed once restored/cloned, such as giving them individual Google accounts etc, but you can easily fix this without re-running the setup wizard.
kuisma said:
There must be something I'm missing. Why don't you install the device, walk through the setup, remove the bloatware you don't want and then dumps the disk partitions into images you flash the other devices with using fastboot? This way you'll get'em cloned, isn't it this you want..?
Of course there's still some tinkering needed once restored/cloned, such as giving them individual Google accounts etc, but you can easily fix this without re-running the setup wizard.
Click to expand...
Click to collapse
Hi
Yes that's what I want to do! How would I go about dumping the disk into an image and then flashing?
fro5tie said:
Hi
Yes that's what I want to do! How would I go about dumping the disk into an image and then flashing?
Click to expand...
Click to collapse
There are several methods. Some boot loaders (such as nvflash for tegra based devices) can actually read back the disk partitions to a computer via the USB port. You can also on the tablet read the raw mtd device with busybox/dd. I assume you've unlocked the bootloader and gain root access to the device, since this is a requirement for flashing them as well. A third alternative is using busybox/tar, and then recreate the filesystem image using mkyaffs (or if ext3/ext4 even easier, just loopback mount an image on you linux maching to unpack the tar archive to). Once you got the images (system and userdata partitions), you flash the devices with "fastboot flash system system.img" and "fastboot flash userdata data.img". I don't believe you'll need to tamper with the other partitions.
kuisma said:
There are several methods. Some boot loaders (such as nvflash for tegra based devices) can actually read back the disk partitions to a computer via the USB port. You can also on the tablet read the raw mtd device with busybox/dd. I assume you've unlocked the bootloader and gain root access to the device, since this is a requirement for flashing them as well. A third alternative is using busybox/tar, and then recreate the filesystem image using mkyaffs (or if ext3/ext4 even easier, just loopback mount an image on you linux maching to unpack the tar archive to). Once you got the images (system and userdata partitions), you flash the devices with "fastboot flash system system.img" and "fastboot flash userdata data.img". I don't believe you'll need to tamper with the other partitions.
Click to expand...
Click to collapse
Hi
Thanks for the quick reply, much appreciated.
Unfortunately you've lost me a bit here!
Yes the device is rooted, I dont have a linux machine though.
Any chance you'd be able to provide some more specific instructions? The device is a chinese tablet from manufacturer Ainol, the model is a Novo 7 Elf 2. Unfortunately there isn't much discussion on these online so specific help is hard to find!
fro5tie said:
Any chance you'd be able to provide some more specific instructions? The device is a chinese tablet from manufacturer Ainol, the model is a Novo 7 Elf 2. Unfortunately there isn't much discussion on these online so specific help is hard to find!
Click to expand...
Click to collapse
I can provide you specific answers to specific questions, but I have no experience of the tablet in question, so you'll have to do some digging yourself first. Make sure it supports fastboot, investigate what the proprietary bootloader is capable of, see how/if you can obtain an original image etc.
One maybe easier solution, especially if you plan to restore the tablets on a regular basis, is to only make a new boot image to reflash the devices with. The only modification done is that you change the /init.rc script to mount /data and /system from the SDcard instead of from the internal nand disk device.
Once this is done, you'll power up and run the installation wizard and everything on your master tablet. Then power it down, and clone the SDcard. This SDcard now contains everything, so you'll simply restore a device by replacing its SDcard with a copy of this master card. I guess it's easier to clone a SDcard than reflashing several internal partitions. Easier to make the master as well - you don't need to dd or tar them, they are already in "image" format. If you can get hold of the original firmware, this should be quite easy without the need to preserving data from the device itself.
fro5tie said:
Any chance you'd be able to provide some more specific instructions?
Click to expand...
Click to collapse
Issue the commands "cat /proc/mtd" and "mount" on your device at command prompt (e.g. via "adb shell" or the "ConnectBot" terminal app). This shows you if the device allows you to copy the boot image from it. Paste in the output into this thread. If you believe the "clone the tablet via the SDcard" is a good solution for you, the process is in short terms something as below;
Copy the boot image to the sdcard:
# dd if=/dev/mtd/mtd2ro of=/mnt/sdcard/boot.img bs=2048 (device dependent of contents of /proc/mtd)
Remove the sdcard, insert into a computer, split the boot image info kernel + initramfs. Read http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images for instructions about how to work with the boot.img file. I really recommend a GNU/Linux environment for this.
Then edit /init.rc replacing the "mount yaffs2 [email protected] /system" with "mount ext3 /dev/block/mmcblk0p2 /system" for system and data (use p3 for data partition, the device name may be different on your tablet, see mount output).
Create an SDcard with three partitions: #1 vfat (standard), #2 and #3 ext3. Insert into you device and boot it up again.
# mount -t ext3 /dev/block/mmcblk0p2 /root
# cd /system
# tar cf - . | (cd /root ; tar xf - )
# umount /root
# mount -t ext3 /dev/block/mmcblk0p3 /root
# cd /data
# tar cf - . | (cd /root ; tar xf - )
# umount /root
This copies your partitions to the SDcard. Shutdown the tablet again.
Make a new boot.img using the instructions in the link above, using the edited init.rc script.
Now you can non-destrutive give this a try.
Place you tablet in fastboot mode (often vol-up (or vol-down) during power on).
$ fastboot devices
This vill verify the tablet is in fastboot mode. It should be listed. Then:
$ fastboot boot boot.img
Note here, only BOOT the tablet, do NOT use the "flash" keyword. This in case of the image isn't working, you'll just have to restart you tablet, and no harm's done.
Look around. Do a "mount" command. Everything works? Mount shows /data and /system from sdcard? Perfect. Now you can reflash it. Shutdown and flash:
$ fastboot flash boot boot.img
Now the device will use /data and /system from the SDcard every time. Customize your device, and then clone your SDcard and try it in tablet #2 you'll booting with your new boot.img and the cloned SDcard. Verify that #tablet #2 is a perfect clone of tablet #1. It is? Now you can flash the boot,img into all your tablets.
--------------------
But don't forget, there may be other solutions as well, maybe more suitable. This you'll have to investigate yourself.
And the usual disclaimer - you can probably not follow above by the letter. There sure is some obstacle you'll have to overcome, something non-standard, etc.
Also keep the original boot.img file for safekeeping in the case you want to restore the device's boot image some day.
Wow! Thanks for the info! This is really helpful, I need to set aside a bit of time to work through this and have a look. Thanks again its really appreciated, I'll be back with info once I've had chance to give it a go!
I certainly can't offer more detailed info than the fellow from Sweden who seems to really know his stuff...but what about making a nandroid backup of your fully configured reference tablet (I'm assuming all tablets are rooted). Ensure all your tabs have CWM recovery and copy your nandroid file to each one.
If any of your fleet get 'corrupted' you can simply restore the original, fully configured ROM.
In fact that sounds too obvious..likely I missed something about your scenario which precludes this option from consideration!
Good luck mate.
tweeny80 said:
I certainly can't offer more detailed info than the fellow from Sweden who seems to really know his stuff...but what about making a nandroid backup of your fully configured reference tablet (I'm assuming all tablets are rooted). Ensure all your tabs have CWM recovery and copy your nandroid file to each one.
If any of your fleet get 'corrupted' you can simply restore the original, fully configured ROM.
In fact that sounds too obvious..likely I missed something about your scenario which precludes this option from consideration!
Good luck mate.
Click to expand...
Click to collapse
Hi
Yes that was my first thought as well, tablets are rooted yes but there is no CWM for the tablet. Its an obscure Chinese branded tablet.
Unless there is another way to do nandroid backups?
hmm tricky situation. Catch 22 ! From what I know, your best bet is to backup all possible things through Titanium Backup given that you don't have the use of Nandroid backups. You can include wifi settings, messages etc but it's modular & not systemic.
I did a quick google search with no luck - time to upgrade your fleet dude :-0
Best of luck.
I would like to know what will happend if i will flash the rainbowmod 2.1 rom on my Lumia 800 with the One key flashing tool.
Does it work ? or it is necessary to flash the partition 3 files under linux.
It would be easyer for me to do it under windows; not having eny experience with ubuntu.
As it says on the rainbowmod instructions;
Before flashing this custom ROM you must flash this file to sdb3 partition (thx biktor_gj)
Thank you,
Hi there,
as far as i know, RainboMod 2.1 will only work with updated files on partition 3.
The actual files for partition 3 (in the first post) are not up-to-date and will only work for RainbowMod 2.0.1.
We still have to wait until lucifer puts his 2.1 version back online, with the updated files for partition 3 i posted on page 12 of the thread.
For now, you can only use 2.0.1 version.
You can try if the rom works, if you only flash partition 9 using nokia lumia downloader in windows.
If it does not work, you have to flash the files of partition 3, which can only be done in linux.
It's very simple, i can help you when you need help.
cheers
help needed
Hello,
So i would gladly use your help,
I just finished installing ubuntu.
As i understand the procedure should be the same for my lumia800 as in these instructions for the lumia 700.
http://forum.xda-developers.com/showthread.php?t=1626317 (100%noob instructions). Am i right?
only thing missing there is the 3rd partition instructions, but if im not wrong the commands should be the same, only have to flash the 3rd partition.Yes?
(6.4: Now using the partition we obtained in step 4 (In my case: sdc9) use this command to flash your phone with the unlocked firmware:
Code:
dd if=os-new.nb of=/dev/sdX9
Replace X with your partition letter (In my case it's c)
so in my case I would enter:
Code:
dd if=os-new.nb of=/dev/sdc9)
Thanks in advance Lordmaxey
hi there,
yes, first, check your drive letter using
sudo fdisk -l
this will show you if your phone is sda, sdb, sdc etc...
for flashing partition 3 it's the same as flashing partition 9 ( dd if=os-new.nb of=/dev/sdc9 )
of course you have to replace 9 with 3 and the input file (if), so it will be: dd if=partition_3_file of=/dev/sdc3
cheers
CAUTION:
Before flashing anything i strongly recommend you backing up every single partition.
eg. sudo dd if=/etc/sdX1 of=backup_partition_1
sudo dd if=/etc/sdX2 of=backup_partition_2
...
repeat for every drive letter
...
sudo dd if=/etc/sdX9 of=backup_partition_9
Thank you lordmaxey,,
i will try..
Done,,
Feeling good.
Thank you again lordmaxey.
So now i checked around a little bit, and i like it allot, especially file explorer, what i was missing . Only one app what i miss is the nokia drive,
i used it allot. Is it possible to deploy this or is this complicated.
whitenegga said:
Done,,
Feeling good.
Thank you again lordmaxey.
So now i checked around a little bit, and i like it allot, especially file explorer, what i was missing . Only one app what i miss is the nokia drive,
i used it allot. Is it possible to deploy this or is this complicated.
Click to expand...
Click to collapse
No worries, you're welcome
You're missing Nokia Drive? Then simply install it via Marketplace
cheers
Ok tried that,but incountered a small problemo, live id key.
searched the forum for eny useful information, . Found some, but aint very shore, how to obtain the live id key asked by microsoft.
so if you have some useful informatipn, i would appreciate it,
hope i wont bother you after this, at least for a while,
Tnx Lmaxey,
did you make a backup of all partitions as i recommended?
if yes, you can use DPPImplant to "extract" your activation code from your backup file.
you'll find dppimplant here: http://forum.xda-developers.com/showpost.php?p=25126572&postcount=642
no worries, that's what we're here for: helping
So i have to tell you the whole story. (you can laugh on my stupidity, no harm don )
Wanted to unlock my lumia by TP. So i ordered the atf box, cables and everything. Not beeing the best solderer in the world i managed to destroy a resistor, but fortunatly the phone still works(only not giving the tp connection). Im no quitter , so i bought a used phone with a brocken LCD.
So now;
1. i have my old phone with DLOAD where should be my Live ID. (is it possible to exctract the key under linux from dload?)
2. And the TP unlocked used phone what i flashed with some old rom, dowloaded when i was searching information about the TP unlock .
After that i managed to flash the rainbowmod by your help.
And yes , i didnt make partition backups,
because I THOUGHT :good: that if i allready flashed it with the older rom , this live id info would be owerwritten.
so it wouldn be eny use for me to backup a custom rom partitions.
And maybe this used phone had somebody elses ID, what i couldnt have used enyway.
This all has to happend to me.
what are my chances?
Wow... holy sh**
whitenegga said:
And yes , i didnt make partition backups,
because I THOUGHT :good: that if i allready flashed it with the older rom , this live id info would be owerwritten.
so it wouldn be eny use for me to backup a custom rom partitions.
And maybe this used phone had somebody elses ID, what i couldnt have used enyway.
Click to expand...
Click to collapse
Yes, the live ID was overwritten anyway, so you're right
Of course i didn't know this situation, that's why i told you to make a backup.
What you can do now:
- TP unlock your resistor-broken DLOAD Lumia, backup and do the DppImplant thing i posted above
- use the avtivation code posted in this thread: http://forum.xda-developers.com/showpost.php?p=32700983&postcount=7
but note: this is not your activation code, so i don't know what happens if you're using it.
hello again
I'm back,
Succeeded with everything. Most of it thanks to you lordmaxey.
So now I have another question.
As it is all new to me, can you explane to me how to use the wm device center to connect it with PC.
So I could see the folders in my computer.
Thx.
whitenegga said:
I'm back,
Succeeded with everything. Most of it thanks to you lordmaxey.
So now I have another question.
As it is all new to me, can you explane to me how to use the wm device center to connect it with PC.
So I could see the folders in my computer.
Thx.
Click to expand...
Click to collapse
Yeah, sure
you have to install Wmdc on your pc, and you have to install the wmdc launcher on your phone.
- then open the application on your phone, select "launch" (click launch to run windows mobile device center phone client)
- then swipe right and selcet all 3 boxes (start wmdc automatically, start debugger automatically, use vs debugger from pc)
- connect your phone to your pc
if wmdc is not starting automatically on your pc, open it.
you should now see your phone.
strange, its not connecting.
I have tried with the zune running in the background, and viceversa.
Allso in the device manager it shows prtable devices-lumia 800 ---This device is working properly.
Eny ideas,
All the best,