Related
From Manups 1.4 on, i was not able to flash any Eclair Rom to my 32B Magic. Now, i could get this done, and i could reproduce my faults. This is now for everyone with fc or Bootloops after applying an Update:
- Wipe data
- Wipe ext
- Wipe dalvik
- repair ext
- reboot (this maybe our fault !)
- flash your rom
- reboot again
-> With this, i can succesfully run Manups 1.5
Thanks to everyone, especially to cyanogen, jac an manup for making us happy !!
Yeah, hope this helps somebody else, too
meisterlampe2000 said:
From Manups 1.4 on, i was not able to flash any Eclair Rom to my 32B Magic. Now, i could get this done, and i could reproduce my faults. This is now for everyone with fc or Bootloops after applying an Update:
- Wipe data
- Wipe ext
- Wipe dalvik
- repair ext
- reboot (this maybe our fault !)
- flash your rom
- reboot again
-> With this, i can succesfully run Manups 1.5
Thanks to everyone, especially to cyanogen, jac an manup for making us happy !!
Yeah, hope this helps somebody else, too
Click to expand...
Click to collapse
i think step 5 is where people get messed up at..i dont see why people get boot loops n cant get past the G-1 screen or anything..
meisterlampe2000 said:
From Manups 1.4 on, i was not able to flash any Eclair Rom to my 32B Magic. Now, i could get this done, and i could reproduce my faults. This is now for everyone with fc or Bootloops after applying an Update:
- Wipe data
- Wipe ext
- Wipe dalvik
- repair ext
- reboot (this maybe our fault !)
- flash your rom
- reboot again
-> With this, i can succesfully run Manups 1.5
Thanks to everyone, especially to cyanogen, jac an manup for making us happy !!
Yeah, hope this helps somebody else, too
Click to expand...
Click to collapse
Those are the steps i follow when i flash any rom, (except if its an upgrade of the same rom), and i have never had a bootloop or anything like that...
MY steps are like your but I wipe data a second time after the first reboot and like other have said I have never run into boot loops
- Wipe data
- Wipe ext
- Wipe dalvik
- repair ext
- reboot (this maybe our fault !)
- Wipe data
- flash your rom
- reboot again
In most cases, rom dev's post in their OP instructions for upgrading their line of Roms or upgrading from another rom. So in that regards, this thread is useless, but none the less important for new comers.
Yeah of course they do !
But have a look at all those Threads...Almost one third of all questions is about fc or Bootloops... I just want to make clear that it really works, when do it right. I was also confused because i just did not read the right lines. Maybe a Thread about "wipes" is justified - If some people can get helped out by that !
If you have apps2sd isn't your dalvik cache on ext already, so when you wipe ext you are wiping dalvik too, correct?
meisterlampe2000 said:
From Manups 1.4 on, i was not able to flash any Eclair Rom to my 32B Magic. Now, i could get this done, and i could reproduce my faults. This is now for everyone with fc or Bootloops after applying an Update:
- Wipe data
- Wipe ext
- Wipe dalvik
- repair ext
- reboot (this maybe our fault !)
- flash your rom
- reboot again
-> With this, i can succesfully run Manups 1.5
Thanks to everyone, especially to cyanogen, jac an manup for making us happy !!
Yeah, hope this helps somebody else, too
Click to expand...
Click to collapse
Thanks for the tips, but I never have boot loop. I perform steps 1-3, then flash rom. No reboot, nothing! Then again, I have a G1. I think this was meant for MT3G devices.
Code:
I//system/xbin/busybox( 47): +++ "This is your world, these are your people. Y
ou can live for yourself today, or help build tomorrow for everyone."
I//system/xbin/busybox( 47): +++ Welcome to Android 2.1 / Manup456_ECLAIR_ERD7
9
I//system/xbin/busybox( 47): e2fsck 1.41.6 (30-May-2009)
I//system/xbin/busybox( 47): ext2fs_check_if_mount: Can't check if filesystem
is mounted due to missing mtab file while determining whether /dev/block/mmcblk0
p2 is mounted.
I//system/xbin/busybox( 47): /dev/block/mmcblk0p2: clean, 11/249856 files, 396
09/499300 blocks
I//system/xbin/busybox( 47): cp: cannot stat '/data/app-private/*': No such fi
le or directory
I//system/xbin/busybox( 47): cp: cannot stat '/data/dalvik-cache/*': No such f
ile or directory
I/DEBUG ( 140): debuggerd: Nov 20 2009 10:17:15
I/vold ( 139): Android Volume Daemon version 2.0
D/AKMD ( 148): akmd 1.6.6 START
D/AKMD ( 148): library version: 1.2.1.1129
I/vold ( 139): New MMC card 'SU04G' (serial 2420584359) added @ /devices/pla
tform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa
I/vold ( 139): Disk (blkdev 179:0), 7744512 secs (3781 MB) 3 partitions
I/vold ( 139): New blkdev 179.0 on media SU04G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 3
I/vold ( 139): Partition (blkdev 179:1), 6682977 secs (3263 MB) type 0xc
I/vold ( 139): New blkdev 179.1 on media SU04G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 2
I/vold ( 139): Partition (blkdev 179:2), 998601 secs (487 MB) type 0x83
I/vold ( 139): New blkdev 179.2 on media SU04G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 1
I/vold ( 139): Partition (blkdev 179:3), 62871 secs (30 MB) type 0x82
I/vold ( 139): New blkdev 179.3 on media SU04G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 0
I/vold ( 139): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mm
c1:aaaa/block/mmcblk0' for mountable filesystems for '/sdcard'
I/vold ( 139): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 139): Volmgr not ready to handle device
D/vold ( 139): Bootstrapping complete
I//system/xbin/busybox( 47): Setting up swapspace version 1, size = 32185856 b
ytes
I//system/xbin/busybox( 47): UUID=89298fcc-2d7e-4440-b962-646ec1c0891d
I//system/xbin/busybox( 47): --- Enabling compcache
I//system/xbin/busybox( 47): Failed to open /dev/block/ramzswap0: No such file
or directory
I//system/xbin/busybox( 47): swapon: can't stat '/dev/block/ramzswap0': No suc
h file or directory
I//system/xbin/busybox( 47): run-parts: /system/etc/init.d/06compcache exited
with code 1
I/logwrapper( 47): /system/xbin/busybox terminated by exit(1)
Trying the steps that were mentioned in the original post, and I still get the errors listed above. I have a 4 gig SD card, partitioned as FAT/EXT/Swap....for the life of me I can not figure out what is going on. I have repartitioned and all, to no avail.
That's all mostly unnecessary. Simplest explanation is that you guys are doing it wrong. Most roms take care of the formatting if it's necessary, more often than not it's not. Often, the culprit will be a poor (as if the "better" one is better... ) a2sd implementation that causes conflicts when mounting and linking the partitions. Most often, it will be just a matter of removing the links and creating new ones.
If you really feel you must wipe (really, it's not necessary), then just do a factory reset (does both /data and /cache (erasing all /app, /app-private, /dalvik-cache and /lost+found in the process)) and wipe the ext (which also erases all /app, /app-private, /dalvik-cache and /lost+found but in the ext partition). That's all that's needed, the rom does the rest.
OP u r an idiot this is for developers not noobs who trying to make something out of themselves, this **** should've been in general or actually not even exist.
If you think there is no need for this, you have to ban all the new Android user that don´t have any clue about what this "wipe" is about...
Almost every developer says, "do a wipe first", and in every thread is somebody having problems with that. I just wanted to tell how it worked for me after a long time of nothing...
Custom MTD Partitions
This is an implimentaion of lbcoder's Custom partition layouts
be sure to checkout that thread for the full history
What does it do?
Well, basically Custom MTD Partitions resizes your MTD partitions
for instance this is a CM6.1RC1, ( heavily customised )
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock3 73.0M 72.8M 236.0K 100% /system
/dev/block/mtdblock5 134.8M 107.2M 27.6M 80% /data
/dev/block/loop0 896.0K 896.0K 0 100% /system/lib/modules
/dev/block/loop1 4.0M 4.0M 0 100% /system/xbin
/dev/block/mmcblk0p2 457.4M 201.8M 231.1M 47% /sd-ext
/dev/block/mmcblk0p2 457.4M 201.8M 231.1M 47% /cache
/dev/block/mtdblock4 2.0M 776.0K 1.2M 38% /dev/cache
most of my Apps are on sd-ext, dalvik-cache is on data
/dev/cache is where the real cache partition is mounted, /cache is actually a bind mount from /sd-ext/cache
Applicable to..
Probably any device that uses the same kind of nand as the G1 MT3G ( msm_nand )
The intial scripts are geared towards G1 / MT3G. however I have 'rewritten' much of the script for v1.5 , it now reads the partition table in dmesg, so it _should_ be universal **
v1.5.3 confirmed to work on heroc
v1.5.6 confirmed to work on bravo + bravoc ( with S-OFF )
unsure if it will work with your device? checkout the source on github ( or ask your favourite dev to take a look )
The 'Tech' in Breif
This method is beautifully simple...
When booting we give the kernel the mtd partition table we want to use..
Thats it
In practice we need to do this when booting to recovery, and booting the rom.
below are files to make this as simple flashing a rom.
Credits :-
Lbcoder - for coming up with the idea
Skraw ( CM forums ) - for getting lbcoder interested
Koush - for AnyKernel
Cyanogen & Co - for giving us all such great ROMs to play with
Amon_RA and Koush - for giving us something to patch
Techjosh - for fixing the patchers for use with Rogers (EBi1)
Mblaster - for pointing out my nasty habit of using -r zip flag at the end of command ( breaks compatibility with older zip versions, fixed in AutoPatcher v1.5 )
Safety First
This method is safe, however it is not without risk
Two things could potentially go wrong
Recovery flash corrupt
This is extremely unlikely, and tbh could happen anytime you flash recovery
If in the very unlikely event that you find you can't reboot to recovery you have three options
re-flash recovery via fastboot ( the preferred option )
re-flash recovery via ROM ( not a great option with cm5.0.x/cm6 )
Do the whole root thing all over again ( no one wants to do that )
system, cache , data partition unmountable - corrupt
Under the right ( or wrong ) circumstances it is possible to get 'junk' files stuck in system ( or cache,data ), and in such away that recovery can not delete them, more serious corruption can render the partitions unmountable.
It is actually quite straight forward to fix this, but it does require fastboot
Code:
fastboot erase system -w
Clockwork Recovery 2.0.2.0 and later has erase_image binary, if you can adb shell in then
Code:
for i in system cache userdata;do erase_image $i;done
and reboot
I would advise you seek out how to 'fastboot', which tbh is a good thing to have regardless of using this 'hack' as it can get you out of so much trouble
*NB* don't use a patched recovery to flash SPL or RADIO ( you should avoid using recovery to flash these anyway, feel free to ask for current advice on spl / radio flashing )
Prevention is better than cure
I have only managed to corrupt partitions when switching partition layouts while having files on cache or data, for example going from System 67.5 Cache 67.5 to System 90 cache 5 with
cache approx 80% 'used'...
I have not been able to repeat this if I wipe Cache before rebooting,
therefore I advise that you wipe both cache and data * after patching recovery ( and rebooting )
* along with system if you are using clockwork
OK, now lets patch recovery and a ROM
Install Instuctions
It really is quite simple
download FR-recovery-v1.5.6-CustomMTD_S.zip and FR-boot-v1.5.6-CustomMTD_S.zip
create mtdpartmap.txt and put on /sdcard/ see configuration *
reboot to recovery
nandbackup
wipe cache + data
flash FR-recovery-v1.5.6-CustomMTD_S.zip
reboot to recovery ( reboot and hold Home )
Either : -
Nandrestore
Flash ROM + extras
flash FR-boot-v1.5.6-CustomMTD_S.zip
reboot
* configuration
The script in the recovery patcher checks for /sdcard/mtdpartmap.txt and reads that to override the default sizes.
e.g. for system 90mb and cache 2mb
NB make sure you mount sdcard first, else you won't write to sdcard/mtdpartmap.txt !
Code:
echo "mtd 90 2" > /sdcard/mtdpartmap.txt
data would be 117.8mb ( 116.7 useable )
e.g. for system 55mb and cache 2mb ( Purhaps a nice 'sugar free' Donut )
Code:
echo "mtd 55 2" > /sdcard/mtdpartmap.txt
data would be 152.8mb ( 151.7 useable )
NB, above data sizes are for G1s, MT3Gs should add ~78mb
All In One Patch runner ( New to v1.5.3 )
new option to run the All In One Patch script ( versions 1.3.6 and higher )
the format is
Code:
aio <option1> <option2> <option3>...
e.g.
Code:
aio swap remount shabang lwp
By default it will install the sd-ext mount ( option sdext )
so a line just reading aio will be fine
Note: the patch must be on the root of the sdcard, and its file name must start with "fr-patch" and end with ".txt"
if you have several versions the newest ( as per files datetime stamp ) will be used
Faking your SPL
If your using an SPL that is not officially supported by your ROM and that ROM checks your SPL you can 'patch' to fake it.
Code:
echo "spl 1.33.2005" >> /sdcard/mtdpartmap.txt
note that we are using ">>" here, this is to append to the file ( ">" would overwrite it )
you can by all means use any text editor you like, the script will automatically convert to unix format
NOTE : you are dodging the checks the ROM dev put in place, do not complain to them if this doesn't workout for you
in post 2 I have some 'CM6' Kernels I compiled for (1)0.95.xxxx SPLs
but I will only likely do these for RCs and Finals ( and there maybe a delay ).
In that post I point you towards the 'SafeSPL' ( 1.33.2003 ) this SPL is compatible with the current CM6 kernels ( so no need to wait for me or someone else to compile with bluetooth as modules ), but 1.33.2003 is not 'officially' supported ( its stock at 67.5mb system ) so you need to Fake your SPL ( say 1.33.2005 ) and resize to 90mb system ( or whatever you feel is optimum )
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
Downloads
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
http://tinyurl.com/customMTD
aab0fadf658ed275954aea8d0aed9c8f FR-AutoMTD_partitionPatcher_v1.5.6.tar.bz2
8857194cdbe34a52d173def4441ad2ae FR-AutoMTD_partitionPatcher_v1.5.6.zip
1f84a5ec50684a7830a93a8d455bc159 FR-boot-rpp-v1.5.6-CustomMTD_S.zip
bca0360f91aed0acf6e2dc82dfe01b56 FR-boot-v1.5.6-CustomMTD_S.zip
94b4238c2668cbe7cd52fb8ad5a2ee12 FR-recovery-v1.5.6-CustomMTD_S.zip
5404f1a41dbc60105d59c7fa0c335a70 FR-remove-v1.5.6-CustomMTD_S.zip
NB New Config option !!! to automatically run fr-patch136+
e.g.
Code:
mtd 90 2
spl 1.33.2005
aio swap remount shabang lwp a2sd
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
ROM Zip Patcher for Devs
To make life even simpler for end users it is possible to integrate the 'patch' within a ROM
AutoMTD_partitionPatcher_v1.5.6.zip
currently Linux only,
within the zip is a tarball, untar that.
get that directory into your PATH, ( or just cd into it )
and then execute
Code:
PatchUpdateScript.sh <zip file to patch>
it will then
create a temp directory ( in your current directory )
copy your zip to it
extract required files
patch update(r)-script
zip and sign.
It simply saves the user from flashing the boot patch after flashing your ROM
The Future....
lbcoder has already suggested ways in which we can implement this 'on the fly'
so for instance it would be possible for a ROM , to instruct recovery what MTD partition layout is required, reload mtd kernel modules, and then flash ROM + boot.img
for those with huge partitions
Hey, you could go all silly and dual boot between ROMs ..
Anyway, enjoy and feel free to modify/improve on these
Changelog
v1-5-6 : 2010-10-28
Calculate userdata size, greatly improves compatibility
Added a version to patch a boot.img ( boot-rpp ) with run-parts
didn't want to , but some are using roms which don't have run-parts, so the 06BindCache script wasn't running
Added a remove version ( remove )
flashing this will return the recovery to SPL's layout
I may well integrate that better, so you don't need a separate zip
AutoMTD_partitionPatcher can convert a recovery.img to a AutoMTD flashable zip
PatchUpdateScript.sh <full path to>/recovery.img
boot patcher is much cleaner, it just uses the cmdline of the running recovery
removed the default 90 2 sizing, you *must* set your own size in mtdpartmap.txt
v1-5-4/5
added stuff
removed stuff
moved stuff
see v1-5-6
v1-5-3 : 2010-08-13
This should be last version we need
greater compatibility with none dreams/sapphires
option to launch All in One Patcher
v1-5-2 : 2010-08-0
Bug fixes
recovery was getting written to boot ( flash_image <partition> is now a variable )
typo in env variable was causing cache and data calculations to fail
AutoMTD now prints version number ( when flashing patched Zip )
tided up system "0x" 'fudge' ( to be compatible with trout/sapphire fall back )
removes temp files from memory when done
v1-5-1 : 2010-08-06
Bug fixes, had an extra '0x' on the system start + functions had wrong env var for the location of dmesg derived partition map
v1-5 : 2010-08-06
Version numbers brought into sync
Zipe Filename - 'reordered' ( easier to see version numbers in CWR )
AutoMTD Patcher - changes as per boot Patcher + zip recursion fix ( my bad habit, thanks go to mblaster for pointing this out )
Boot Patcher - cleaned up cache bind mount
Now supports leagcy /system/sd mount point
[*]supports ROM Manager ( real cache partition mounted on /dev/cache, recovery dir symlinked from 'fake' to 'real' cache )
Recovery Patcher - can 'fake' your SPL ( see configuration )
Recovery Patcher - creates more noise ( advise wipe and reboot )
Single Patcher script ( so I don't have make the same changes to three different files that essentially do the same job )
No longer 'Hardcoded' to 32[a/b] Partition Layout ( figures out SPL layout via dmesg ) **
uses original boot/recovery img's base configuration ( i.e. EBi0 and EBi1 compatible )
=< v1.4
Recovery Patcher v1.3, added SPL faker
Boot Patcher v1.2, fixed oversite where boot.img was not 'dumped'
Recovery Patcher v1.1 initial
Boot Patcher v1.1 ( was a fail, it didn't patch boot.img on CM roms as the tmp boot.img was deleted, my fault for just using the AutoMTD Patcher's script ( which runs before the tmp boot.img is deleted )
Boot Patcher v1 initial
Todo
- 2010-08-13 redundent ( launching AIO script ) - I might add some stuff to cm5/6's backup routine via the Auto patcher, things like the "All in One" installed scripts: 05mountsd and remount
windows compatible AutoMTD script ( meh, I hate batch scripts )
- 2010-08-13 DONE - thinking of adding a config option to launch the "all in one" script, but have to make that recovery compatible first
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
Downloads
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
mediafire downloads
http://tinyurl.com/customMTD
aab0fadf658ed275954aea8d0aed9c8f FR-AutoMTD_partitionPatcher_v1.5.6.tar.bz2
8857194cdbe34a52d173def4441ad2ae FR-AutoMTD_partitionPatcher_v1.5.6.zip
1f84a5ec50684a7830a93a8d455bc159 FR-boot-rpp-v1.5.6-CustomMTD_S.zip
bca0360f91aed0acf6e2dc82dfe01b56 FR-boot-v1.5.6-CustomMTD_S.zip
94b4238c2668cbe7cd52fb8ad5a2ee12 FR-recovery-v1.5.6-CustomMTD_S.zip
5404f1a41dbc60105d59c7fa0c335a70 FR-remove-v1.5.6-CustomMTD_S.zip
The attached files are OLD
Custom MTD FAQ
FAQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q my SPL starts with 0 or 10, and I want to try CM5.0.8 or/and CM6. DO I need to do anything extra?[/b]
A yeap, it seems the newer kernels are just a bit too big for x0.95.x00x SPLs, you can get round it with the below kernels. And to flash CM6 you need to 'fake' your SPL ( see configuration in OP ) or edit the updater-script. faking is easier.
However, I would recommend the 1.33.2003 SPL ( you still need to fake your SPL, but you won't need the 'special' kernels )
guide for flashing 1.33.2003 SPL by Ezterry
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-07-11
I have compiled a kernel, which I hope is NoneDanger compatible
the source is simply CyanogenMod's github, I have taken the config from cm6rc1, and simply changed the bluetooth to modules
this approach has worked in the past
It is pre-patched with AutoMTD, so just flash cm6rc1, then flash this
FR-CM6RC1-bootimg4NoneD-AutoMTD.zip(MD5: 386D9A05A3C0FFC08E5B3F844D437AA7)
mirrors
http://rapidshare.com/files/406402016/FR-CM6RC1-bootimg4NoneD-AutoMTD.zip
http://www.mediafire.com/?152jnqwyme3
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-07-27
NoneDanger compatible Kernel for RC2
FR-CM6RC2-bootimg4NoneD-AutoMTD.zip (MD5: 7858a8a8d126919318d1718c6e5167ec )
http://www.mediafire.com/file/ttxfcocsti3mma3/FR-CM6RC2-bootimg4NoneD-AutoMTD.zip
I'll have to dig out the src
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-08-15
NoneDanger compatible Kernel for RC3
2010-08-17 ( Sorry, old one had a status6 bug )
New one here
87F160F08FCD2233DDD40FBFC50D3711 FR-CM6RC3-bootimg4NoneD-AutoMTD.zip
src = http://github.com/CyanogenMod/cm-kernel/tree/48c57f11abaaf3de6c81f6f5c44cfe2637251184
no modifications its straight cm ( besides the config, which you can get from the compiled kernel or zcat /proc/config.gz )
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
*NB* don't use a patched recovery to flash SPL or RADIO ( you should avoid using recovery to flash these anyway, feel free to ask for current advice on spl / radio flashing )
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q do I need to flash both of the files each time I install a new rom?
A No, you only need to flash the recovery patcher once, unless you want to resize or you install a new recovery.
the boot patcher *must* be flashed after you have installed a new ROM or Kernel update
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q my cache looks odd in df, I see two and its the same size as data or sd-ext, is something wrong?
A everything is fine, since we shrunk cache its no good for things like the Market, so a script is installed to 'bind mount' cache with /sd-ext/cache or data if sd-ext is not mounted.
it actually turns out that /cache is not actually used in CM6, so I might adapt the script a little in a future release.
EDIT: as of version 1.5 the cache bind mount script mount 'real cache' separately, which should reduce confusion
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q When I tell ROM Manger to do something in recovery, it just reboots to recovery and does nothing. it used to do the action but not since I installed CustomMTD
A yeah, nearly forgot about that, I was going to fix it last week, basically ROM Manger writes commands to /cache, but its writing it to our bind mount so.. when recovery boots it doesn't see the commands.
In all honesty that one hasn't been pointed out to me yet, but yeah I can fix it..
EDIT: as of version 1.5 the cache bind mount is compatible with ROM Manager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Scripts
'source' is now available on github
http://github.com/Firerat/CustomMTD
errm, tbh I'm not all that clued up on it yet
looks very promising
So, will i need to change the values everytime i flash a different rom? or can i just set them to a large size and everything will work?
asb123 said:
looks very promising
So, will i need to change the values everytime i flash a different rom? or can i just set them to a large size and everything will work?
Click to expand...
Click to collapse
most roms have a target of 90mb system ( DangerSPL )
so 90 2 config will basically give you an extra 28mb on data than you would have with stock DangerSPL MTD map
so yeah
90 2 is a good all rounder
Firerat said:
most roms have a target of 90mb system ( DangerSPL )
so 90 2 config will basically give you an extra 28mb on data than you would have with stock DangerSPL MTD map
so yeah
90 2 is a good all rounder
Click to expand...
Click to collapse
is it okay if I make system 70mb?
The rom im using is only using 66 out of 90, i want more space for data instead. I remember you said something about it being a miltiple of 128K.
With this, could Devs stop skimping on stuff like wallpapers and ringtones or additional apps, and surpass the 90MB danger spl mark? It would seem so. Also, I do not make roms so I do not know how it works but if there is compression or lower quality stuff they would now be able to use up as much space as wanted correct?
Ace42 said:
is it okay if I make system 70mb?
The rom im using is only using 66 out of 90, i want more space for data instead.
Click to expand...
Click to collapse
yeap, should be fine
personally I would be tempted to use clockwork, since you can erase system ( part of partition options )
.img files can be found here
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
I don't recommend flashing via ROM Manager with CM5 or CM6
fastboot it over, or flash via recovery
I may be a little over cautious recommending a full wipe, but I have never had problems when system, cache and data are clean.
if you are 'growing' system make sure cache and data are clean
if your 'shrinking' make sure system is clean ( so 'hangovers don't mess up /cache or data )
asb123 said:
With this, could Devs stop skimping on stuff like wallpapers and ringtones or additional apps, and surpass the 90MB danger spl mark? It would seem so. Also, I do not make roms so I do not know how it works but if there is compression or lower quality stuff they would now be able to use up as much space as wanted correct?
Click to expand...
Click to collapse
yes, you can 'grow' or 'shrink' at will
just hope it doesn't get used to be lazy and not trim bloat
Hi firerat,
you mentioned once before something about market data on the cahe... or something so downloads would be ok if a certain partition was big enough?....something like that... I am having a prob that might be related since it started when I tried to change from default to system 80 5 for data. now I cant sign in to google and after flashing gaaps there is no market? everything else in the gaaps zip is there...? It could be google i know but i remembered you saying that somewhere.
TheNewGuy said:
Hi firerat,
you mentioned once before something about market data on the cahe... or something so downloads would be ok if a certain partition was big enough?....something like that... I am having a prob that might be related since it started when I tried to change from default to system 80 5 for data. now I cant sign in to google and after flashing gaaps there is no market? everything else in the gaaps zip is there...? It could be google i know but i remembered you saying that somewhere.
Click to expand...
Click to collapse
I very much doubt it is related in anyway
/cache is where the market downloads apks to prior to install
it should be bind mounted to /sd-ext/cache or /data/cache if sd-ext is not mounted
your missing Market is related to something else
Firerat said:
I very much doubt it is related in anyway
/cache is where the market downloads apks to prior to install
it should be bind mounted to /sd-ext/cache or /data/cache if sd-ext is not mounted
your missing Market is related to something else
Click to expand...
Click to collapse
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Ace42 said:
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Click to expand...
Click to collapse
Because he bind mounted it.
Ace42 said:
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Click to expand...
Click to collapse
JAguirre1231 said:
Because he bind mounted it.
Click to expand...
Click to collapse
sorry for confusion
When I download stuff with dolphin HD it goes to /sdcard/download
maybe its different with stock browser
the cache bind mount is
added a few extra comments to make it easier to follow
/system/etc/init.d/06BindCache
Code:
#!/system/bin/sh
# check we don't already have a bind mount
# ( so if ran manually multiple times we don't end up with strange things happening )
if [ "`awk '/\/cache/' /proc/mounts |sed -n '$='`" -gt "1" ];
then
echo "cache already bind mounted"
echo `awk '/\/cache/' /proc/mounts`
exit
fi
# check if /sd-ext mounted, if yes then bind to /sd-ext/cache, if not /data/cache
if [ "`grep -q sd-ext /proc/mounts;echo $?`" = "0" ];
then
CacheDir=/sd-ext/cache
else
CacheDir=/data/cache
fi
# check we have something to bind mount, and create if not
if [ ! -d $CacheDir ];
then
install -m 771 -o 1000 -g 2001 -d $CacheDir
fi
mount -o bind $CacheDir /cache
# check dalvik-cache exists ( this is really for magics )
# so they don't end up in bootloop because dex files can not be created
if [ ! -d $CacheDir/dalvik-cache ];
then
install -m 771 -o 1000 -g 1000 -d $CacheDir/dalvik-cache
fi
actually, errm yeah it is d/l to /sdcard/downloads
not my doing
I guess cache really is pointless on froyo
hey firerat great job bro! again ive been really busy and i still didnt get to try this or the earlier betas you made...hell i havent even tried a froyo rom yet. ima try this right now and let you know how it goes!
speedysilwady said:
hey firerat great job bro! again ive been really busy and i still didnt get to try this or the earlier betas you made...hell i havent even tried a froyo rom yet. ima try this right now and let you know how it goes!
Click to expand...
Click to collapse
Froyo has been nice so far
but you may run into issues
for one the updater-script is actively 'kicking' NoneDanger
you can just remove the getprop checks
I have had problems booting cm5.0.8's kernel, I did get round it by compiling a new one from cm github,
I
'm not sure is cm6's kernel has the same issue
it does seem SPL related, I flashed Danger and it was fine, I plan to go back to NoneDanger and confirm it still doesn't work.
but figured that while I was on Danger I might as well put this (Custom MTD) through its paces with a DangerSPL
Firerat said:
Froyo has been nice so far
but you may run into issues
for one the updater-script is actively 'kicking' NoneDanger
you can just remove the getprop checks
I have had problems booting cm5.0.8's kernel, I did get round it by compiling a new one from cm github,
I
'm not sure is cm6's kernel has the same issue
it does seem SPL related, I flashed Danger and it was fine, I plan to go back to NoneDanger and confirm it still doesn't work.
but figured that while I was on Danger I might as well put this (Custom MTD) through its paces with a DangerSPL
Click to expand...
Click to collapse
lol yeah i was just gonna say the get prop error occured lemme remove those asserts resign and see what happens
hmm oddly everything flashed fine on the latest nightly build but when it gets past the g1 screen it keeps rebooting to recovery? ima rewipe and try again and see if i can get a logcat if it happens again
edit: no dice when i run logcat =/
-exec '/system/bin/sh/' failed: permission denied (13) -"
double edit: i get the same error for any rom i try to flash when i look at the logcat. the only difference is cm's latest nightly build rebooted on the g1, super e freezes at the g1 screen...ima try to modify the .txt to go back to the stock layout so i can nandroid my cachehacked cm5.08 back if not...idk what to do..
speedysilwady said:
hmm oddly everything flashed fine on the latest nightly build but when it gets past the g1 screen it keeps rebooting to recovery? ima rewipe and try again and see if i can get a logcat if it happens again
edit: no dice when i run logcat =/
-exec '/system/bin/sh/' failed: permission denied (13) -"
Click to expand...
Click to collapse
Odd, but at leasat the kernel is booting, I wasn't getting anywhere with cm5.0.8
It could be a general error
Which build are you using
I'm on a nightly, but I know Defcon works
If its still not working, try the older v1 version of boot patcher in lbcoders thread
I did change boot v1.1 to the script I use in the automtd one
I'm on the nightly 0704 (944 I think ) btw
Firerat said:
Odd, but at leasat the kernel is booting, I wasn't getting anywhere with cm5.0.8
It could be a general error
Which build are you using
I'm on a nightly, but I know Defcon works
If its still not working, try the older v1 version of boot patcher in lbcoders thread
I did change boot v1.1 to the script I use in the automtd one
I'm on the nightly 0704 (944 I think ) btw
Click to expand...
Click to collapse
noo this wasnt cm5.08 this was the latest nightly, same one youre 0704 on.
it got to the g1 screen and right when its abt to hit the boot animation it reboots.
i tried super e but it froze on the g1 screen
trying to get back to 67 67 for cache and system so i can nandroid but its weird that the logcat wont show no matter what rom i use.
hello everybody.
first of all i will present myself.
i'm from France and this is the first time i have a smartphone.
my phone is :
Téléphone : Acer Liquid express E320 -orange
Android : 2.3.4
ROM : acer E320 1.013.00 EMAEA ORGFR
Bande de base : C6-1.013.00
Kernel : 2.6.35.7
after several check in different forums, i didn't find the solution in order to root my phone.
i have tried Doomlord V4 and V3 and it don't work.
i want to root my phone in order to delete some ORANGE application that i would never use.
then it can give some free space on the phone memory (that is very smal = 150Mo).
on a french forum, we are 3 people with exactly the same problem.
so if you help me, you help 3 people....!!
we have tried with all software available on the net but nothing as work.
please find in the link below, the screen shot of my last try with doomlord V4.
https://docs.google.com/open?id=0B9iSIWzMh8dueThpRnJBbGdYTlU
if you need more information or if you have some other things to test, do not hesitate to ask.
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
chapoune42 said:
hello everybody.
first of all i will present myself.
i'm from France and this is the first time i have a smartphone.
my phone is :
Téléphone : Acer Liquid express E320 -orange
Android : 2.3.4
ROM : acer E320 1.013.00 EMAEA ORGFR
Bande de base : C6-1.013.00
Kernel : 2.6.35.7
after several check in different forums, i didn't find the solution in order to root my phone.
i have tried Doomlord V4 and V3 and it don't work.
i want to root my phone in order to delete some ORANGE application that i would never use.
then it can give some free space on the phone memory (that is very smal = 150Mo).
on a french forum, we are 3 people with exactly the same problem.
so if you help me, you help 3 people....!!
we have tried with all software available on the net but nothing as work.
please find in the link below, the screen shot of my last try with doomlord V4.
https://docs.google.com/open?id=0B9iSIWzMh8dueThpRnJBbGdYTlU
if you need more information or if you have some other things to test, do not hesitate to ask.
Click to expand...
Click to collapse
Salut, t'as essayé avec le OneClickRoot ? USB DebugMod ON ?
Essaye ici... http://www.androidust.com/how-to-root-acer-liquid-express-e320-with-one-click-root/
Sinon essaye avec ça... je sais pas si ça fonctionne par contre... http://www.actualitemobile.com/foru...5df3c2a0662ba09e5bc74a7a1&/topic,19874.0.html
A+
@prg626
oui j'ai essayé avec ces 2 méthodes et aucune ne marche.
merci quand même
Hope someone could help me (and the 2 other french user i know with the same trouble)
thanks
Try This...
I don't have that device nor seen it but in my shop experience, you can modify the rooting programs by extracting the SU and SUPERUSER files from other SuperOneClick programs and pasting those files into that one you posted here and try that. If that does'nt work, then try to get that device in a custom recovery and find a root.zip flashable file and paste the SU and SUPERUSER files into it. Then flash the Root.zip file from the root of your sd card. I got that to work on alot of IMPOSSIBLE devices Sometimes devices are "read only error" so your only alternative is to flash from recovery.
thanks but it seems a litle bit complicated for me...
nonody has another easyest solution for me ?
probably someone has already reach the goal of root this phone... so if he can give us the way to do it, he will be great.
It would seem all rooting exploits are or have been blocked, the only way I have found to root the E320 is the Xakep ROM Flash from acer-club.ru although the rom flash is for 1.008.00 and not 1.013.00 (I did read that 1.008.00 could gain root access using DoomLords tool but not sure of version but depending on your phones production date may now be blocked) I have flashed Xakep ROM 1.008.00 after 1.013.00 now cannot update or reflash as the Radio/AMSS side of ROM is still 1.013.00 ... just to make you aware.... would advise to read as much as possible from Xakep's postings
Rooted Xakep E320/C6 EUU Hacked Update
thanks for this info.
probably i have found a solution :
replace the original ROM Orange (impossible to root) by another ROM Acer already rooted...
does someone can confirm me that it will be possible ?
i want to replace : OS_Acer_1.013.00.EMEA.ORGFR_A23G_A
by this one : acer_E320_1.008.00_EMEA_GEN1:
That is what I'm on now although it has given me the problem that neither the Xakep 1.008.00 or the Orange 1.013.00 EUU'S will reflash the phone.
I must admit I have not tried to solve this problem yet as phone is working 100% other than unable to reflash.
One thing it will not update is the RADIO part of the phone, this will remain as 1.013.00 and this is probably the reason for being unable to reflash.
Rooted Xakep E320/C6 EUU Hacked Update
Since it was stated in another post (possibly on another site just can't remember ) that prior to an OTA update root access was gained using DoomLords exploit, finally a ROM has surfaced *** :highfive: *** that may be of use - Link at the bottom of the page for the ROM
Yes I have it on my phone now and seems A-OK BUT..... and this is a big BUT!!!!......
Please..............(the dreaded disclaimering bit)
DO NOT ATTEMPT TO FLASH THIS IF YOU ARE NOT 100% SURE YOU CAN RECOVER FROM ANY PROBLEMS WITH FLASHING THE ROM
AS YOU WILL HAVE TO EDIT FILES TO 'DOWNGRADE' YOUR PHONES SYSTEM.
If you are confident in editing and flashing then by all means do so BUT I am not held accountable for errors or unusable software/hardware, what may have worked for me may NOT work for you.....
(Basically if you're not sure don't do it - I was only 80% sure trying it but I take risks and fully accept the consequences if I brick my phone)
What you will need to do is the following:
Firstly you will need the Temp files of both the ROM you are using and 1.005.00 ROM.
Current Rom...
No Need To Connect Your Phone For This.
Run the update program.
Search for (depending on your ROM) a folder in
C:\Documents and Settings\*Current_User*\Application Data\
the folder named ACER_EUU_Download_Tools (Stock Update)
Click to expand...
Click to collapse
or for
C:\Documents and Settings\*Current_User*\Local Settings\Temp\
a folder named 7ZipSfx.000 (Xakep ROM's as I have come across no others yet and the .000 can increment .001 .013)
Click to expand...
Click to collapse
Copy that folder to another location then cancel the update (you will notice if you check all but a few files are deleted - this happens even if the update succeds or fails to flash your phone)
Now do the same for the 1.005.00 update and copy the folder to another location.
From the 1.005.00 copied update folder copy the following files:
AMSS_C6.Orange.1.005.00_4G_2Die.hex
Android_C6.Orange.1.005.00_User_Signed.hex
flex-Orange_FR_C6.Orange.1.005.00_User_Signed.hex
Click to expand...
Click to collapse
Paste into the copied Current ROM folder.
Rename the corresponding files - examples:
AMSS
Orange = AMSS_C6.Orange.1.014.00_4G_2Die.hex
Xakep =C6_Image_4G_2Die_MODEM.hex
Android System
Orange = Android_C6.Orange.1.014.00_User_Signed.hex
Xakep = C6_Android_WB_1.008.00_release_key.hex
FLEX
Orange = flex-EMEA_GEN1_signed.hex
Xakep = flex_Orange_UK_C6.Orange.1.014.00_User_Signed.hex
rename and add .bak to the files (we want to preserve the filenames)
Click to expand...
Click to collapse
Now rename the copied 1.005.00 files to the corresponding files renamed .bak (to suit your ROM's files)
Make a backup copy of your now edited folder incase of any failure
(the EUU deletes files on success AND failure - we don't want to have to go through this again)
You can now delete/remove any files you no longer require (1.005.00 copied folder - .bak files)
You can now run the file EUU.exe from the edited folder and update the phone.
SKU - The French/Russian ROM's use different SKU than the UK ROM, the above method is the only one i've been able to
revert my phone back to a UK ROM - FR and RU ROMS can flash over each other and UK...UK is unable to flash over FR/RU ROM.
Click to expand...
Click to collapse
Any DEV interested in modding and maybe making Root Access persistant (think this is the only ROM prior to 1.008.00 update that is rootable) --==>>HERE<<==-- is the link for ACER 1.005.00 ORGFR ROM I found.
Have Fun.
*** Tested and rooted with DooMLoRD V4 ROOT ***
Code:
--- STARTING ---
--- WAITING FOR DEVICE
* deamon not running. starting it now *
*daemon started successfully *
---creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergrush
720 KB/s (23060 bytes in 0.031s)
--- correcting permissions
--- executing zergrush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploit Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x00015180
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40121cf4 0x0064
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd24fcf 0xafd39027
[*] Popping 8 more zerglings
[*] Sending 157 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root...enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets sstuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
---pushing busybox
1049 KB/s (1075144 bytes in 1.000s)
--- correcting permissions
--- remounting /system
--- checking free space on /system
27 KB/s (439 bytes in 0.015s)
df: /data/DxDrm/fuse: Permission denied
--- Free space on /system : 5356 bytes
--- Not enough free space on /system!!!
--- making free space by removing Google Maps
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transfered in 0.452 secs (2378637 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
347 KB/s (22228 bytes in 0.062s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
2135 KB/s (785801 bytes in 0.359s)
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
:cyclops: . . . . . and here is an OTA .zip I grabbed - Official OTA contains .mbn & .img files so here's some info .txt
Has anyone else tried this yet?
I have tried it but I had firmware from acer-club.ru and I have bricked my phone, so as this post says be careful.
If anyone know how to get past 'aFlex download fail!!!' and the USB is not recognized by PC then let me know.
For those that come across this I finally got it working. I am not sure what did it but this is what happened.
Phone was left with battery disconnected most of the day.
I formatted a 4GB mini SD card and copied the folder from OTA.ZIP file on the bottom of Antagonist42 post.
Inserted this mini SD refitted the battery and whilst holding volume up and volume down press and held the power button.
Not sure if I released one of the volume keys but modem download came up without the dreaded 'aFlex download fail!!!' message.
Connected to laptop flashed with standard 1.013.00 firmware from Acer UK website.
Phone then booted and did OTA update to 1.014.00 and all looks OK. (sorry Antagonist42 was not quick enough to the OTA files)
I don't know what helped here but I thought I would let you all know what I did.
My warranty is still sending out a replacement phone tomorrow even though I got it going so I will try Antagonist42's root fix when I have the new one as this one needs to go back with the stock ROM.
Finally have phone working ( to a degree ) and moved house ( unable to play with phone and OTA ).
aSYSTEM/aFLEX/etc download fails
Initially rerun the update program and/or download the updater again, ensure you're not getting decompression/write errors on your PC as this will give you the same errors.
If after doing the above the error remains then it could actually be hardware failure ( still trying to iron my own NAND/partition error out )
As for running OTA over an error the OTA is not written to memory in the same way as the PC updater as with prior post my guess is corrupt file and not an actual 'brick' as running a fresh updater (the same as the rom that was installed and not a different rom) would probably have corrected the fault.
I'll soon post what other small but interesting things you can do with a stock updater that does not require hacking or vast programming knowledge
Sent from my Poorly Acer E320
Does anyone got the file EUUs_E320_1.005.00_EMEA_ORGFR.zip? The link to dropbox is dead/blacklisted
Need this file urgently, i would really appreaciate it....
Thanks
Orange French EUU 1.005.00
here's a link for EUU EMEA ORGFR if you're in UK you may not get some apps that appear on Google Play as it uses a different SKU (says which country it can be used in)
https://anonfiles.com/file/b197e1af76f99f9628ce0576c9f2d0b3
Dual booting - the idea:
Use of recovery partition to boot second rom ( stock recovery isn't very useful anyway)
How to on post:
http://forum.xda-developers.com/showpost.php?p=63735205&postcount=10
Already tested:
Boot from SD card possible.
Video:
http://www.dailymotion.com/video/x3d8xq1_g386f-dual-boot-from-sd-card_tech
Cons:
lack of recovery makes flashing roms rather complicated (but we can't use stock recovery for that anyways)
second rom must be compatible with kernel
I know there's nothing interesting to be booted from sd card for now. But I hope that it'll be useful to test any compiled or ported rom, yet still have a fully usable phone.
Bypassing secure boot - kexec idea:
Kexec
is a mechanism of the Linux kernel that allows "live" booting of a new kernel "over" the currently running one
Click to expand...
Click to collapse
In short words it runs "stock" kernel and then it runs any other kernel.
As we know that stock kernel can be modified and repacked in boot.img.
The difficult is to implement kexec hardboot to kernel.
I already tried twice with no succes.
More detailed description:
http://forum.xda-developers.com/showthread.php?t=2104706
TO DO LIST:
boot from /recovery
- add hard kexec to Samsung kernel - most important
- repartition phone with 'parted' to dualboot from internal memory - low priority, but everyone may try
Already done:
- boot from /recovery with custom Samsung kernel (should be easy)
- boot from sd card possible
- boot from /recovery with changed initramfs - is it possible or will secure boot react?
--------------------------------------------------------------------------------------------------------------
Version Anglaise - English Version
--------------------------------------------------------------------------------------------------------------
Hello,
I'm very thankful that you're there to lead this project.
Such as you, I want to pass this problem of secure boot to create a custom ROM (cyanogenmod in fact).
However I'm just a web developer (PHP, Javascript...) and I know just a little (very little ) the Java (but no oriented-object).
I want to be useful... So have you some tasks to assign me ?
While I'm waiting your answer, I will read some docs !
(Sorry for my english, if you don't understand me I could try to explain in other words )
--------------------------------------------------------------------------------------------------------------
Version Française - French Version
--------------------------------------------------------------------------------------------------------------
Bonjour,
Je suis vraiment content que tu sois là pour gérer ce projet.
Comme toi, je voudrai passer ce problème de sécurité au démarrage pour créer une ROM custom (Cyanogenmod en fait).
Cependant je suis juste un développeur Web (PHP, Javascript) et je connais un petit peu (vraiment un petit peu) le Java (mais pas la programmation orientée objet).
Je souhaiterai être utile... As-tu quelques tâches à me confier ?
En attendant ta réponse, je vais lire quelques documentations !
Hello ! In the past, i already managed to compile a CWM and TWRP for our phone. But well, sadly i ran into the secure boot issue.
Now i can't even work anymore on that, since my pc is broken, and i lost almost everything. But if we understand how to bypass it i'll be glad to restart my work on it anyway, as soon as i got a new computer ^^
BTW i'm french too
Thanks for awesome job, @Agasharr.
After seeing many questions how to help you with development, I thought it would be nice to have a TODO list in first post so anyone could try to "do the magic" with their devices.
Example goals:
boot from /recovery
☐ boot from /recovery with custom Samsung kernel (should be easy)
☐ boot from /recovery with changed initramfs - is it possible or will secure boot react?
☐ add hard kexec to Samsung kernel - most important
☐ repartition phone with 'parted' to dualboot from internal memory - low priority, but everyone may try
☐ fix power off problem
Please write your own list and add to main post.
Could you answer me a question in 3rd goal - can we change initramfs when secure boot is enabled?
Sorry about my English and a bit low quality of this post but I think we have to make the thread alive and every help count. I don't have Core LTE atm but it is sad how few ppl are working with it.
Hi.
Firstly:
Your english is perfectly understandable. It's not a native language for most of us, mistakes are naturally so we shouldn't care that much about it. It's not a english philology.
Second:
To do list is a great idea, I'll update the first post, hope You don't mind if I just copy yours
As for initramfs I'll check and let You know next week.
Third:
I know some c++ and php basis, but never consider myself as a dev. I'm just and user who can't wait any longer for someone to do the job I spend almost all my free time "playing" with this phone. The problem is that I've full time job, wife, 2 kids, i'm helping my wife run her business, and i'm selling modules on prestashop addons so my all free time is in fact very little.
PS. broken PC is not an excuse ;P I currently run on old netbook with amd e450 cpu as graphic card in my PC breaks up almost 2 months ago.
Great idea for the todo list !
Firstly, I tried to extract my boot.img however the tuto which I read wasn't very adapted...
Have you some websites to advise me ?
bobo159951 said:
Great idea for the todo list !
Firstly, I tried to extract my boot.img however the tuto which I read wasn't very adapted...
Have you some websites to advise me ?
Click to expand...
Click to collapse
hi, if You insist to dump boot.img from a phone this is a good guide:
http://forum.xda-developers.com/showthread.php?t=2450045
But the easiest way is to unpack it from downloaded firmware:
http://www.sammobile.com/firmwares/database/SM-G386F/
We may decide on which firmware of this phone we will work together in order to haven't any sort of compatibily problems, no ?
I download this firmware personally : G386FXWUAOI2
-- On devrait peut-être décider sur quel firmware de ce téléphone nous devrions travailler pour ne pas avoir de problème de compatibilité, non ?
J'ai téléchargé ce firmware personnellement : G386FXWUAOI2
I was using boot and system img from latest polish and french firmware and mixed them without any problems. But we can stick with french.
Post updated:
How to dual boot from sd card:
What You need:
sd card - kinda obvious
micro sd card reader - can be useful
linux (or other way to unpack and copy system.img to sd card)
Terminal Emulator installed on phone.
How to:
With gparted on linux (or on windows with any program capable of creating ext4 partition)
Create partitions on sd card:
1. it not necessary but I advice to create some fat32 partition of size You wont, it will be available as sd card on base rom, without this partition base rom will constantly notify that sd card is damaged and You need to format it.
2. cache partition - ext4 format - stock size is 200 MB
3. system partition - ext4 format - stock size is 1475 MB
4. data partition - ext4 format - size You want
Copy system.img to system partition:
On linux:
unpack system.img to some folder
copy simg2img to that folder and create in the same place folder sys (it's an example)
open terminal and paste:
Code:
simg2img system.img sys.raw
then:
Code:
sudo mount -t ext4 -o loop,rw sys.raw sys/
sys.raw will be mounted in sys folder and You can copy files from there
if You need a root for that, open terminal in sys folder and paste:
Code:
sudo cp -r * /patch/to/your/system/partition/on/sd/card
On windows:
unknown
When You all done with sd card it's time to place it in phone and make sure how partitions are mounted.
Run terminal emulator and type:
Code:
cat /proc/partitions
It'll show all partitions on a phone, check your partitions names if You are not sure check size. You need some math to do so, as You have to divide blocks by 1024, for example 204800 / 1024 it's 200 MB.
It's time to mod fstab.u2evm from boot.img . It defines mount points so You have to change mount points for system, cache and data partitions.
It looks like "/dev/block/mmcblk0p18" (stock cache) and after change: "/dev/block/mmcblk1p6" (cache on sd card) in my case.
On windows:
Repack boot.img, rename new file to "recovery.img" and make flashable tar with
"tar-Tool_Odin3-v3.07_by_mkh.mourad"
http://forum.xda-developers.com/showthread.php?t=2446269
Flash with Odin and boot to recovery.
First boot take about 15 minutes.
Great works ! doesn't it slow down ?
I'm sorry I didn't have so much time to work on it but also I have a problem with the Java JDK on linux :-/
bobo159951 said:
Great works ! doesn't it slow down ?
I'm sorry I didn't have so much time to work on it but also I have a problem with the Java JDK on linux :-/
Click to expand...
Click to collapse
Well, phone boots like 3 times slower than normal and lags at the beginning, but after a while it runs almost like normal (at least with less demanding tasks). Performance drop is strictly related to sd card quality. Better the card better the performance will be. I have old 8 GB card class 10.
I'll update the first post with a short video.
As for your problems with java, You can use builduntu:
is a custom branch of the Ubuntu operating system for compiling Android ROMs from source. It includes everything you need to sync with the repo of your choice (Cyanogenmod, AOSP, etc) and start building.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2585828
I'm sorry but finally I decided to sell my phone..
It's interesting that you can boot on sdcard. But can you do the same with recovery ? Booting a recovery in a micro sd ? y the way i'm still searching for hints to bypass the secure boot.
I made some tests :
--Booting Stock recovery with stock kernel (but reflashed) - OK
--Stock Recovery extracted, Edited (config text files) and repacked - OK, Boot after showing the red exclamation mark
-- Custom recovery with stock kernel - won't skip the red exclamation mark
--Stock Recovery Extracted and repacked with custom kernel - Not Yet Tested
--Custom Recovery with custom kernel : Not Yet Tested
wondering if a custom kernel would change something, since the G386W needed a custom kernel to boot into custom recovery
AmineIzumi said:
It's interesting that you can boot on sdcard. But can you do the same with recovery ? Booting a recovery in a micro sd ?
Click to expand...
Click to collapse
No, I'm not booting "boot" partition from sd card, just replace recovery with another boot that points to system on sd instead of internal memory.
AmineIzumi said:
Stock Recovery Extracted and repacked with custom kernel - Not Yet Tested
Click to expand...
Click to collapse
If stock boot partition can be repacked with custom kernel and it works well, I presume that recovery will work in similar way.
AmineIzumi said:
wondering if a custom kernel would change something, since the G386W needed a custom kernel to boot into custom recovery
Click to expand...
Click to collapse
Not sure if it'll help but I already removed SECURE_BOOT_ENABLE verification from drivers/char/rtapi/rtboot/rtboot and rt_boot_sub
changing in rt_boot_sub from:
Code:
#ifdef SECURE_BOOT_ENABLE
data_addr = ioremap(PRIMARY_COPY_ADDR, info.image_size);
#else
data_addr = ioremap(info.boot_addr, info.image_size);
#endif
to:
Code:
data_addr = ioremap(info.boot_addr, info.image_size);
and in rtboot from:
Code:
#ifdef SECURE_BOOT_ENABLE
phys_cert_addr = (PRIMARY_COPY_ADDR + g_rtboot_info.image_size + 0x00001000) & (0xFFFFF000);
cert_size = read_rt_cert(phys_cert_addr);
if (cert_size == 0) {
MSG_ERROR("[RTBOOTK] |read_rt_cert failed\n");
do_iounmap_register();
ret = misc_deregister(&g_device);
if (0 != ret)
MSG_ERROR("[RTBOOTK] |misc_deregister failed ret[%d]\n", ret);
MSG_HIGH("[RTBOOTK]OUT|[%s] ret = 1\n", __func__);
return 1;
}
ret = sec_hal_memcpy((uint32_t)g_rtboot_info.boot_addr, (uint32_t)PRIMARY_COPY_ADDR, (uint32_t)g_rtboot_info.image_size);
if (ret == SEC_HAL_CMN_RES_OK) {
ret = sec_hal_authenticate(phys_cert_addr, cert_size, NULL);
if (ret != SEC_HAL_CMN_RES_OK)
MSG_ERROR("[RTBOOTK] |sec_hal_authenticate ret[%d], phys_cert_addr[0x%08x], cert_size[%d]\n",
ret, phys_cert_addr, cert_size);
}
if (SEC_HAL_CMN_RES_OK != ret) {
MSG_ERROR("[RTBOOTK] |RT boot secure error\n");
MSG_ERROR("[RTBOOTK] |boot_addr[0x%08x], image_size[%d]\n", g_rtboot_info.boot_addr, g_rtboot_info.image_size);
do_iounmap_register();
ret = misc_deregister(&g_device);
if (0 != ret)
MSG_ERROR("[RTBOOTK] |misc_deregister failed ret[%d]\n", ret);
MSG_HIGH("[RTBOOTK]OUT|[%s] ret = 1\n", __func__);
return 1;
}
MSG_ERROR("[RTBOOTK] |secure boot on\n");
#else
MSG_LOW("[RTBOOTK] |write_rt_imageaddr bootaddr[%x]\n", bootaddr);
MSG_LOW("[RTBOOTK] |write_rt_imageaddr start\n");
write_rt_imageaddr(bootaddr);
#endif
to:
Code:
MSG_LOW("[RTBOOTK] |write_rt_imageaddr bootaddr[%x]\n", bootaddr);
MSG_LOW("[RTBOOTK] |write_rt_imageaddr start\n");
write_rt_imageaddr(bootaddr);
After some effort, I present you TWRP 3.0.2.0 custom recovery for Alcatel OneTouch pixi 3 (8) Wifi, model 8070.
The specific recovery is currently under some progress, but this build is working really well except from touch input.
CREDITS :
@yuweng for providing a convenient and automated way to build a twrp recovery -> twrp-build script.
Changelog:
- v2.2: Changes in partition scheme. Also the "wipe with rm -rf" instead of formating is now the default setting, for compatibility in restoring a backup.
- v2.1: Some minor changes in recovery.fstab. Thanks to @yuweng for mention it out!
- v2.0: Now the graphics are displayed in better resolution. Cpu temp is now working. Still touch is not fixed though
Things that work:
- Battery Percentage
- CPU Temp
- Installing superSU
- Installing xposed-framework
- full backup/restore process (explained at the end of the post)
Things that don't work:
- Touch (You'll have to connect a mouse through OTG cable in order to use the recovery)
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
In order to install it, you'll have to unlock the bootloader of the device first. Read the steps before procedure. Take a backup of your files before proceeding!
How to unlock bootloader:
- Power on device and boot into Android.
- Connect the device to PC through cable
- Go to settings -> storage and press the 3-dot menu and select "USB computer connection". Next, select connect as Built-in CD-ROM option.
- Now, go to My Computer and install the driver of the virtual disc that is mounted from device.
- Supposing that the driver is installed correctly, we activate adb for our device.
- Go to settings -> about tablet -> hit 7-8 times on "build number", congrats, you're now a developer!
- Go to settings -> developer options -> hit USB debugging and press OK on the popup window. If the connection is working, one more popup is going to appear asking you to allow the connection, Tick the box "always allow from this computer" and press OK.
- Open an adb terminal and check if the device is working properly typing "adb devices". The serial number of your device should appear, so everything is OK!
- Now, boot into fastboot typing "adb reboot-bootloader". The device is going to reboot and boot into fastboot mode, waiting for command.
- For the bootloader to be unlocked, you have to type "fastboot oem unlock". A warning message regarding bootloader unlocking should appear on the device, waiting for an answer. Press the volume+ key and the bootloader is now unlocked! WARNING! ALL DATA ON THE DEVICE IS GONNA BE WIPED, so backup your files before.
- Wait for the wiping of the device to be finished and then you're ready to install the twrp custom recovery!
How to install TWRP:
- We must be in fastboot mode once again. You can either boot holding power button & vol+ while the device is powered off, or type the command in the adb terminal "adb reboot-bootloader" while the device is connected to PC and is booted into Android.
- Assuming that you are in fastboot mode and the device is connected to the PC, you open an adb terminal and type "fastboot flash recovery /path/to/twrp-recovery".
Replace the path reflecting your path's downloaded twrp.
- Congrats! You now have your twrp custom recovery installed!
In order to operate the twrp, due to lacking of touch input, you'll have to connect a mouse using an OTG cable.
You can now install whatever you want, from supersu to xposed-framework, you can take full backups with restore capabilites, and many more interesting stuff!
I'll try to fix the bugs, but because I'm not a developer, I'm just a power user with some advanced linux knowledge, if any dev knows and willing to help me fix the touch screen issue, he's more than welcome!
Info about backup/restore process:
The specific device has one ubnormality. It stores some of the data in a separate partition called "custom". What I found out was that if you format this partition, even if you restore a backup image, the device doesn't boot, or it boots in boot loops.
So, after some testing, I found out that the process for a reliable and working backup image, is to do the next steps:
For creating a backup:
- Go to twrp settings and select use -rm instead of formatting
- You should only choose Data, Custom & System. No need for anything else, but if you want, you can backup the rest of the dirs, just in case.
For restoring a backup:
- Wipe the Dalvik Cache, Cache, System, Data, Custom partitions. You don't need to wipe the Internal Storage or/and External SDcard, if you don't want to lose your personal data like, photos, music, etc. But, you should always take a backup of these files at any case!
- Choose Data, System, Custom partitions from twrp backup dir
- Reboot
Can we get some screenshots?
kirito9 said:
Can we get some screenshots?
Click to expand...
Click to collapse
It's planned but I have to install a screenshot script first. But if you want to see, I'll take some shots in analogue way.
dam85 said:
It's planned but I have to install a screenshot script first. But if you want to see, I'll take some shots in analogue way.
Click to expand...
Click to collapse
Nicee .
@kirito9 You can see the images on the first post
dam85 said:
@kirito9 You can see the images on the first post
Click to expand...
Click to collapse
Good, you'll get your thanks tomorrow (ran out)
Can I use it on Pixi 3 (8) WiFi I220 model?
zakk87 said:
Can I use it on Pixi 3 (8) WiFi I220 model?
Click to expand...
Click to collapse
I'm not sure. Probably not. This build is for mt8127 cpu and the most important thing, is the partition scheme of your device. The recovery partition has to be in the same position with pixi 3 8 in order to not cause brick.
But I can help you. If you could post your dumchar_info (/dev/proc/dumchar_info), I can tell you if it's the same. Maybe you must to be rooted in order to view this file. Try with kingroot.
Unfortunlately i have a bootloop and I don't know how to recover this device. Alcatel upgrade tool say it's up to date.
zakk87 said:
Unfortunlately i have a bootloop and I don't know how to recover this device. Alcatel upgrade tool say it's up to date.
Click to expand...
Click to collapse
If it's already bricked, you could try it (won't get worse afterall). But you'll have to unlock the bootloader first, follow my guide to do this.
Mobile Upgrade tool doesn't work? Can you tell me the full model name, to have a look please?
Did you try with this one? I've just checked that it has your model in the list.
My device is i220 model. No 3G, wifi only. I think its mt8127 CPU and I'm wondering how can I recover software.
zakk87 said:
My device is i220 model. No 3G, wifi only. I think its mt8127 CPU and I'm wondering how can I recover software.
Click to expand...
Click to collapse
First of all, how did you get into bootloop? Did you try to install xposed framework? In order to restore your tablet, you have to get the stock rom, through a rom readback or through a custom recovery backup. For alcatel devices, through mobile upgrade tool. Try the one I posted and give me a feedback.
I have this update tool but doesn't work.
Now I'm trying backup but it's very slow.
This device is from Orange, my friend hit factory data reset button by menu and it's all. Device bricked.
zakk87 said:
I have this update tool but doesn't work.
Now I'm trying backup but it's very slow
This device is from Orange, my friend hit factory data reset button by menu and it's all. Device bricked.
Click to expand...
Click to collapse
Try with mobile upgrade 4.4.5 version. Uninstall the other one first.
I don't think that a read back of your already bricked rom is gonna make any good. You need a working rom
Basically, your device is not bricked. Your friend just wiped your rom from device, so there isn't any os to boot, that's why the boot loops.
Try to restore it through mobile upgrade tool 4.4.5 (uninstall all other versions), and give me a shot of the fail screen.
the fail screen and log:
The phone's cu is I220-2DRGPL1
The phone's IMEI is 94D85xxxxxxxxxxxx
The phone's version is D33EO30
The version in the server is NULL
Click to expand...
Click to collapse
2015/06/16 10:53:40 [DEBUG] Thread #0xe08 has been successfully started.
2015/06/16 10:53:40 [INFO] ############################################################
2015/06/16 10:53:40 [INFO] OTU DLL Version 3.1.8, Build Id=2015031600, Protocol Id=20130822.
2015/06/16 10:53:44 [INFO] Shutting down O.T.U. Library ...
2015/06/16 10:53:44 [DEBUG] Thread #0xe08 received shutdown request.
2015/06/16 10:53:44 [DEBUG] Thread #0xe08 terminated.
2015/06/16 10:53:44 [INFO] O.T.U. Library: Succeeded to join AM!
2015/06/16 10:53:44 [INFO] O.T.U. Library: Succeeded to join MD!
2015/06/16 10:53:44 [DEBUG] Request Executor Thread #0xde4 has been terminated.
2015/06/16 10:53:44 [INFO] O.T.U. Library: Succeeded to join ReqExecutor!
2015/06/16 10:53:44 [INFO] O.T.U. Library: Great! No timer exists in scheduler after shut down all threads.
2015/06/16 10:53:44 [INFO] O.T.U. Library has been shutdown!
2016/05/17 18:55:45 [INFO] ############################################################
2016/05/17 18:55:45 [INFO] OTU DLL Version 3.2.8, Build Id=2015052611, Protocol Id=20130822 SessionBackupFile path=downloaded/session_backup.txt.
2016/05/17 18:55:45 [ERROR] Failed to open file 'downloaded\E1\FE\E1FE54CF356003567A2579519EFE0582F6A1DA0A.bin' due to non existing path.
2016/05/17 18:55:45 [ERROR] Failed to open session file.
2016/05/17 18:55:45 [ERROR] load session from disk failed!
2016/05/17 18:55:45 [ERROR] Failed to open file 'downloaded\65\A2\65A22D35BB44A8D51AE2ECF8936A5B25C9763242.bin' due to non existing path.
2016/05/17 18:55:45 [ERROR] Failed to open session file.
2016/05/17 18:55:45 [INFO] O.T.U. Library has been successfully initialized!
2016/05/17 18:55:45 [DEBUG] Thread #0x4d4 has been successfully started.
2016/05/17 18:55:45 [DEBUG] Request Executor Thread #0x4f8 has been successfully started.
2016/05/17 18:55:45 [INFO] ############################################################
2016/05/17 18:55:45 [INFO] OTU DLL Version 3.2.8, Build Id=2015052611, Protocol Id=20130822.
2016/05/17 18:55:56 [DEBUG] GisusDllImpl::create_device_info...
2016/05/17 18:55:56 [DEBUG] Thread #0x4d4: Request Processing is Starting ...
2016/05/17 18:55:56 [DEBUG] Thread #0x4d4: We have to connect first to 184.73.174.232 ...
2016/05/17 18:55:56 [DEBUG] Thread #0x4d4: Successfully connected to 184.73.174.232!
2016/05/17 18:55:57 [DEBUG] AMConnection::TickVersionReq: Connection #0x4d4: to check report info !
2016/05/17 18:55:57 [INFO] Thread #0x4d4: Upgrade for current software is not available.
2016/05/17 18:57:27 [INFO] Shutting down O.T.U. Library ...
2016/05/17 18:57:27 [DEBUG] Thread #0x4d4 received shutdown request.
2016/05/17 18:57:27 [DEBUG] Thread #0x4d4 terminated.
2016/05/17 18:57:27 [INFO] O.T.U. Library: Succeeded to join AM!
2016/05/17 18:57:27 [INFO] O.T.U. Library: Succeeded to join MD!
2016/05/17 18:57:27 [DEBUG] Request Executor Thread #0x4f8 has been terminated.
2016/05/17 18:57:27 [INFO] O.T.U. Library: Succeeded to join ReqExecutor!
2016/05/17 18:57:27 [INFO] O.T.U. Library: Great! No timer exists in scheduler after shut down all threads.
2016/05/17 18:57:27 [INFO] O.T.U. Library has been shutdown!
Click to expand...
Click to collapse
I found i213 model ROM but i don't know is it fit -
Code:
[url]http://chomikuj.pl/marcin.l19/Alcatel+pixi+7+i213+MT8127[/url]
So, you have to get a working rom from another same, working device through read back. I suggest to mail alcatel support asking for an image, or for a working method of mobile upgrade tool, they should reply to you within 24-48 hours.
I'll have a look too. When you get a reply, post again on the thread.
zakk87 said:
the fail screen and log:
I found i213 model ROM but i don't know is it fit -
Code:
[url]http://chomikuj.pl/marcin.l19/Alcatel+pixi+7+i213+MT8127[/url]
Click to expand...
Click to collapse
Maybe it will. The cpu is the same. Try to flash only system partition to see if it works.
I flashed android but memory test gives me:
============ Memory Detection Report ===========
Internal RAM:
External RAM:
Type = DRAM
Size = 0x20000000 (512MB/4096Mb)
NAND Flash:
ERROR: NAND Flash was not detected!
EMMC:
EMMC_PART_BOOT1 Size = 0x0000000000400000(4MB)
EMMC_PART_BOOT2 Size = 0x0000000000400000(4MB)
EMMC_PART_RPMB Size = 0x0000000000080000(0MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000000e9000000(3728MB)
UFS:
ERROR: UFS was not detected!
Click to expand...
Click to collapse
zakk87 said:
I flashed android but memory test gives me:
Click to expand...
Click to collapse
How did you try to flash it? Through sp flash tool? This tool isn't working properly on alcatel tablets. You should try through twrp, maybe it works.