eltoffer
|
2012-07-06
, 17:27
|
Posts: 98 |
Thanked: 20 times |
Joined on Jan 2012
|
#11
|
|
2012-07-06
, 18:06
|
Posts: 1,067 |
Thanked: 2,383 times |
Joined on Jan 2012
@ Finland
|
#12
|
i used this but still no success im i doing something wrong?
|
2012-07-06
, 23:04
|
Posts: 245 |
Thanked: 915 times |
Joined on Feb 2012
|
#13
|
The Following 6 Users Say Thank You to itsnotabigtruck For This Useful Post: | ||
|
2012-07-07
, 04:05
|
|
Posts: 6,436 |
Thanked: 12,701 times |
Joined on Nov 2011
@ Ängelholm, Sweden
|
#14
|
The Following User Says Thank You to coderus For This Useful Post: | ||
|
2012-07-07
, 05:26
|
Posts: 98 |
Thanked: 20 times |
Joined on Jan 2012
|
#15
|
|
2012-07-07
, 06:35
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#16
|
|
2012-07-07
, 07:15
|
Posts: 164 |
Thanked: 47 times |
Joined on Jun 2012
|
#17
|
It's possible to pack your own firmware images without any keys - the caveat is that flashing them will put your phone into open mode no matter what starting with the PR1.2 bootloader version.
The procedure is to:
- Unpack FIASCO image using flasher 3.5
- Unpack sparse image (rootfs.jffs2) using unlzo.py
- Mount rootfs image as an ext4 loopback device
- Do what you'd like
- Unmount rootfs
- Repack sparse image using sparsify.py
- Build FIASCO image from sparse image and layout file using fiasco-gen
- Flash FIASCO image to device using flasher 3.12.1
It isn't very easy to do, and most of those steps have to be done from a Linux system. Also, realistically, it isn't all that useful - though I released sparsify hoping that someone would do it anyway. If you really want to pack a custom image I'd help out with more info.
Edit: On second thought, one potential use would be for quick deployment of NITDroid, but IIRC e-yes wasn't too interested in this.
|
2012-07-09
, 03:42
|
Posts: 98 |
Thanked: 20 times |
Joined on Jan 2012
|
#18
|
|
2012-11-23
, 16:28
|
Posts: 4 |
Thanked: 0 times |
Joined on Nov 2012
@ China
|
#19
|
It's possible to pack your own firmware images without any keys - the caveat is that flashing them will put your phone into open mode no matter what starting with the PR1.2 bootloader version.
The procedure is to:
- Unpack FIASCO image using flasher 3.5
- Unpack sparse image (rootfs.jffs2) using unlzo.py
- Mount rootfs image as an ext4 loopback device
- Do what you'd like
- Unmount rootfs
- Repack sparse image using sparsify.py
- Build FIASCO image from sparse image and layout file using fiasco-gen
- Flash FIASCO image to device using flasher 3.12.1
It isn't very easy to do, and most of those steps have to be done from a Linux system. Also, realistically, it isn't all that useful - though I released sparsify hoping that someone would do it anyway. If you really want to pack a custom image I'd help out with more info.
Edit: On second thought, one potential use would be for quick deployment of NITDroid, but IIRC e-yes wasn't too interested in this.
|
2012-11-23
, 18:35
|
Posts: 458 |
Thanked: 783 times |
Joined on Jan 2010
@ France
|
#20
|
its possible mounting pr1.1 on a virtual device and using apt-get -d swype-keyboard, why not legal????