Related
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.
You've been waiting patiently for it and it's finally here.
Welcome to the
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Combination of easiest methods
Integrated Console
All-in-one root
99% Automization (e.g. Not possible to detect fully booted phone through adb/shell)
Logging enabled for easy debugging
Will be updated periodically (as, and if, new versions are released)
prboy1969 and megaghostgamer - for helping me get started with android and stuff! :good:
All name credits go to rhodiggah HERE
Indirect,VICODAN, and JohnnyCakeXM for their rooting methods/finds:
Indirect's Root and downgrade for Android 2.3.4 {Script included - ShiftySonofA script dl added)
VICODAN's [VIDEO GUIDE] FULL S-OFF ROOT for Evo SHIFT. Froyo (2.2) + Gingerbread (2.3.3+2.3.4)
JohnnyCakeXM's 2.3.4 Latest OTA[2.77.651.8] Downgrade!!
Q. Will this root the latest OTA (2.77.651.8)?
Yes. This utility supports all releases of Android for the EVO Shift
Q. Does this work on Linux?
Mostly. I am still ironing out a couple bugs, but since this is written in java, a large chunk of the work is already taken care of by that.
Q: My phone goes into a bootloop after rooting 2.3.4. Did I do something wrong?
No. That is supposed to happen. Assuming you already have the downgraded PG06IMG.zip on the root of your sdcard, you can immediately click "OK" in my utility when prompted so that it takes you to the bootloader to downgrade. If not, you need to turn off your phone, get the PG06IMG.zip on the sdcard and then manually go into bootloader (Power off/Battery pull then Power + VolDown)
Q: After downgrading to 2.2, I tried to temproot with Visionary and it gives me a black screen. How can I fix this? Thanks @asbrand!
Press the home button to exit Visionary, then open it again and attempt to temproot, it should go through this time. I dont know why this happens, but I've had it happen to me as well.
Q: Does this tool give me full S-OFF / unlocked bootloader? Thanks Nooblube
This tool gives you S-OFF (Nand unlocked), and also gives you an unlocked bootloader.
Before starting: Make sure you have installed the HTC USB drivers. If you have not, go to THIS thread, download the ZIP and install both files. Additionally, make sure your phone is formatted to FAT32. If not, make a backup, format it to FAT32, move your files back, and get started.
Windows only: If you have adb in your $PATH, you do not need to download the zip.
Linux only: You MUST download the adb_linux and place the files into the same directory as the utility, even if you ALREADY have adb in your $PATH (absolute file path must be used by utility when running on Linux)
The latest version of Java must be installed to run this utility. (Java 7)
Rooting 2.2
Downloads adb_windows, adb_linux, or adb_mac depending on your OS
Download the root2.2.zip file
Download the utility.jar file
Place the adb files into the same folder as the jar
Extract the root2.2 folder into the same directory as the jar (see picture). DO NOT RENAME THE FOLDER TO ANYTHING BUT "root2.2" OR IT WILL NOT WORK.
Run the utility, thoroughly following ALL prompts and prerequisites
Rooting 2.3.3
Run the 2.3.4 RUU (either one, preferably the 2.77.651.3 version)
Follow the instructions for rooting 2.3.4
Note: There is a method for rooting 2.3.3 directly but I couldn't test it (no RUU found)
Rooting 2.3.4
Follow steps above for rooting 2.2
Download the root2.3.4.zip and extract the FOLDER into the same directory as the utility (same way as with root2.2 folder)
DO NOT RENAME THE FOLDER TO ANYTHING BUT "root2.3.4" OR IT WILL NOT WORK.
Run the utility, throughly following ALL prompts and prerequisites
Folder structure
Warning
You will be on older radios after rooting. Download the ZIP with the most recent radios, WiMAX, and touchscreen firmware from HERE.
Instructions to update:
Download the file from the URL above. Make sure that it is named "PG06IMG.zip" (without the quotes, on Windows 7 the extensions are hidden by default so make sure you are not naming it "PG06IMG.zip.zip" by accident)
Place the file on the root of your sdcard (meaning not inside any folders, just copy and paste to main sdcard drive)
Turn off your phone and go into bootloader by pressing Power+VolDown
Your phone should find the PG06IMG.zip file and commence the update process, follow the onscreen prompts to update the firmware on your phone
Note: This does not eliminate your root privileges or unroot your phone, it merely updates the radios and touchscreen.
IMPORTANT: Your sdcard must be formatted to FAT32 for this to work. If it is not, make a back up, format, and then move your files back and then start this update process.
Note: Please realize that I am only one person with one phone. I could not have possibly tested all scenarios, so if you find a bug, post what the bug is and I will fix it as soon as possible.
As a precautionary note, also check the md5sum of the files on your own. The utility checks some core files, but the rest is up to you, I recommend using THIS commandline one.
DISCLAIMER: I take no responsibility for your actions. However, I would be more than happy to troubleshoot any problems you encounter, post what your problem is and attach the log file too.
ALL Files Here: http://d-h.st/users/CNexus/?fld_id=7741#files
Take the most recent version of the desktop utility.
Other Links (Can be reached through link above as well)
Individual files here (if md5sum does not match): http://d-h.st/users/CNexus?fld_id=10377#files
Utility JAR's: http://d-h.st/users/CNexus?fld_id=10378#files
(New!) http://d-h.st/users/CNexus/?fld_id=10376#files
Code:
[B]1/13/13 - v0.50 [/B]
- Added ability to flash files to different partitions
- Reboot menu is now fully functional (no longer experimental)
- Added link to standalone "FlashImage Tool v1.0" in OP, also packaged in the utility now
[B]12/10/12 - v0.49 [/B]
- Internal md5sum checking for all dependent files (no need to download md5sum.exe anymore)
- Optimized code, removed unnecessary files -> significantly smaller file size. (50.48 KB)
- Reboot menu now included ( Advanced tab > Reboot Menu) [[B]Experimental[/B]]
[B]12/2/12 - v0.47[/B]
- Miscellaneous bug fixes. 2.77.651.8 root now works (accidentally checking Android version instead of firmware number)
[B]11/30/12 - v0.46[/B]
- Added the ability to toggle ADB connection between Wifi and USB.
[B]11/29/12 - v0.44[/B]
- [B]IMPORTANT[/B]: Fixed the 2.3.4 not running (accidentally running 2.3.3 root, which I had left unimplemented, hence the window staying blank and the log being blank as well). The utility should now function correctly for everyone using it.
[B]11/27/12 - v0.42[/B]
- Fixed md5sum checking for hboot_eng.nb0 that would sometimes be faulty.
[B]11/26/12 - v0.41[/B]
- Added support for Linux. Still a couple bugs, but they will be ironed out quickly. Note: Must give adb and md5sum executable permissions for it to work.
[B]11/22/12 - v0.4[/B]
- Initial build released, tested from all software versions
- Integrated console added
- Logging added
many thanks, hopefully i wont force myself into trying this
-somebody- said:
many thanks, hopefully i wont force myself into trying this
Click to expand...
Click to collapse
Thank YOU for the kind remarks!
CNexus said:
Thank YOU for the kind remarks!
Click to expand...
Click to collapse
Thanks man . Will try this out next time I need to Root a Shift. Which is more often than you would think .
prboy1969 said:
Thanks man . Will try this out next time I need to Root a Shift. Which is more often than you would think .
Click to expand...
Click to collapse
Ahhhh the irony.
I just had to root my phone manually because it won't show up in adb long enough for my utility to run everything lol
CNexus said:
Ahhhh the irony.
I just had to root my phone manually because it won't show up in adb long enough for my utility to run everything lol
Click to expand...
Click to collapse
Ummm.... yeah
Nice work, I might try it on this extra shift I picked up for parts/spare etc.
BigSplit said:
Nice work, I might try it on this extra shift I picked up for parts/spare etc.
Click to expand...
Click to collapse
Thanks!
Sent from my JB'd speedy
prboy1969 said:
Ummm.... yeah
Click to expand...
Click to collapse
Yeah I think I broke my phone in the process of making this
It won't root even when I do it manually...
And it just stopped showing up in ADB completely
Good thing my upgrade isn't too far off....
If you broke your phone, how can we know this is safe? I'm hoping it is, because if so it's greatly needed and appreciated.
hgelpke said:
If you broke your phone, how can we know this is safe? I'm hoping it is, because if so it's greatly needed and appreciated.
Click to expand...
Click to collapse
I broke my phone testing...but ive also dropped it. This tool is try at your own risk, but it is safe to use, to the best of my knowledge.
I believe my problem is a hardware issue anyway.
Sent from my JB'd speedy
Perfect timing on this, I had done the 2-step unroot process becuase I was going to sell my Shift on craigslist after upgrading to the Photon Q, but the Q is proving to have all sorts of problems, especially with the LTE network, so I think I may follow Vicodan's footsteps and return to the Shift. I figure if his expertise can't overcome the software and network problems on the Q, I can't either.
---------- Post added at 11:16 AM ---------- Previous post was at 10:58 AM ----------
Ok, so first attempts aren't going so well. First a couple notes:
Might want to include a note about Java being required to run a .jar - new PC didnt have it installed yet and double-clicking the .jar didn't do anything at all).
Also, in the instructions you don't mention downloading md5sum.exe and putting it in the folder, but I see it later in the directory tree. My first run of the utillity I didn't have it there, second attempt its there, but same results:
When I run the utility (v0.42), it comes up with the Prerequisites screen, I confirm my settings, then click next (or ok, or whatever the button said). The utility recognizes my phone and software version (2.77.651.3). I click Root Now! and the utility's console blanks out, and nothing happens, either in the utility or on my phone. Is there anything I can do to see what its hanging up on?
Edit: Here's my directory tree:
Code:
c:\RootEvoShift>dir
Volume in drive C has no label.
Volume Serial Number is 104A-11BE
Directory of c:\RootEvoShift
11/28/2012 11:09 AM <DIR> .
11/28/2012 11:09 AM <DIR> ..
11/28/2012 10:50 AM 191,488 adb.exe
11/28/2012 10:50 AM 96,256 AdbWinApi.dll
11/28/2012 10:50 AM 60,928 AdbWinUsbApi.dll
11/28/2012 11:04 AM 0 log-11282012.log
11/28/2012 11:09 AM 0 log-11282012.log.lck
11/28/2012 11:07 AM 2,048 md5sum.exe
11/28/2012 10:50 AM <DIR> root2.2
11/28/2012 10:49 AM <DIR> root2.3.4
11/28/2012 10:48 AM 41,821 speedy-root-utility-v0.42.jar
7 File(s) 392,541 bytes
4 Dir(s) 367,063,105,536 bytes free
cmags said:
Perfect timing on this, I had done the 2-step unroot process becuase I was going to sell my Shift on craigslist after upgrading to the Photon Q, but the Q is proving to have all sorts of problems, especially with the LTE network, so I think I may follow Vicodan's footsteps and return to the Shift. I figure if his expertise can't overcome the software and network problems on the Q, I can't either.
---------- Post added at 11:16 AM ---------- Previous post was at 10:58 AM ----------
Ok, so first attempts aren't going so well. First a couple notes:
Might want to include a note about Java being required to run a .jar - new PC didnt have it installed yet and double-clicking the .jar didn't do anything at all).
Also, in the instructions you don't mention downloading md5sum.exe and putting it in the folder, but I see it later in the directory tree. My first run of the utillity I didn't have it there, second attempt its there, but same results:
When I run the utility (v0.42), it comes up with the Prerequisites screen, I confirm my settings, then click next (or ok, or whatever the button said). The utility recognizes my phone and software version (2.77.651.3). I click Root Now! and the utility's console blanks out, and nothing happens, either in the utility or on my phone. Is there anything I can do to see what its hanging up on?
Edit: Here's my directory tree:
Code:
c:\RootEvoShift>dir
Volume in drive C has no label.
Volume Serial Number is 104A-11BE
Directory of c:\RootEvoShift
11/28/2012 11:09 AM <DIR> .
11/28/2012 11:09 AM <DIR> ..
11/28/2012 10:50 AM 191,488 adb.exe
11/28/2012 10:50 AM 96,256 AdbWinApi.dll
11/28/2012 10:50 AM 60,928 AdbWinUsbApi.dll
11/28/2012 11:04 AM 0 log-11282012.log
11/28/2012 11:09 AM 0 log-11282012.log.lck
11/28/2012 11:07 AM 2,048 md5sum.exe
11/28/2012 10:50 AM <DIR> root2.2
11/28/2012 10:49 AM <DIR> root2.3.4
11/28/2012 10:48 AM 41,821 speedy-root-utility-v0.42.jar
7 File(s) 392,541 bytes
4 Dir(s) 367,063,105,536 bytes free
Click to expand...
Click to collapse
Thats odd, I downgraded my phone from 2.77.651.3 before I even posted...the thing is I can't even test it anymore because my phone will not show up in ADB (hardware issue, I'm gonna be taking it in soon)
Can you attach the log file the utility makes?
And also, try running the utility again, when it hangs, open a cmd window and type "adb kill-server" and then "adb devices" and make sure your device is showing up as "device"
Sent from my JB'd speedy
Adb shows my device, but the logfile is 0 byte. Nothing to see in it. Any way to get at the backend java console to see what's happening, or maybe you have a debug build?
cmags said:
Adb shows my device, but the logfile is 0 byte. Nothing to see in it. Any way to get at the backend java console to see what's happening, or maybe you have a debug build?
Click to expand...
Click to collapse
Did you install the latest version of java? My program runs using java 7
Sent from my JB'd speedy
Yes, installed the latest today from java.com.
cmags said:
Yes, installed the latest today from java.com.
Click to expand...
Click to collapse
Sorry dude, I don't know why its not logging or why it hangs :\
I'll take a look at the code again and see, but I swear that I downgraded from 2.3.4 just the other day...
I will try to test it on my own phone but I've been having issues connecting it to adb
Sent from my JB'd speedy
[UPDATED 2017/08/21]
All
I felt it would make sense to start a new thread for the Blackphone 2, with an original ROM.
Here is: Blackphone BP2 3.0.14 ROM (RoW edition)
In order to install it you must be on 3.09. install via original recovery... which is here...
And for those who want the TWRP, here it is.
Root
(I know you been waiting for it...)
You got two options, let's start with an easy one:
Magisk
1) Download the latest version (ZIP file). copy to the sd card.
2) Boot to TWRP recovery
3) install
4) reboot. install the APK either from the play store or via a direct link (my preferred path)
5) Welcome to the brave world of root
6) Read the guide!
More... soon
Love
Aloha Friend,
links below (RoW edition) do not work (#8026) Not authorized: Link has been deleted).
Thx for your help
Cheers
Apostrike said:
Aloha Friend,
links below (RoW edition) do not work (#8026) Not authorized: Link has been deleted).
Thx for your help
Cheers
Click to expand...
Click to collapse
silent circle would it be behind deleting files !
Is it a joke? I tried to download the 3.0.9 row but here is the message that i received: " BP2_3.09_full_row.zip Apr 10, 2017 7:53 PM
808.2 MB 0% File too large to download with browser decryption.
What does exactly it mean?
Thank you.
---------- Post added at 04:53 PM ---------- Previous post was at 04:36 PM ----------
I did it, I downloaded with chrome, but strange that was impossible to donwload it with firefox on linux....
---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------
I confirm. It's a joke. Download file BP2_3.09_full_row.zip
File Date Size
BP2_3.09_full_row.zip Apr 10, 2017 7:53 PM
808.2 MB 0.63% Timeout error downloading
1 item"
It is absolutely absurd.
kenfalco_14 said:
Is it a joke? I tried to download the 3.0.9 row but here is the message that i received: " BP2_3.09_full_row.zip Apr 10, 2017 7:53 PM
808.2 MB 0% File too large to download with browser decryption.
What does exactly it mean?
Thank you.
---------- Post added at 04:53 PM ---------- Previous post was at 04:36 PM ----------
I did it, I downloaded with chrome, but strange that was impossible to donwload it with firefox on linux....
---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------
I confirm. It's a joke. Download file BP2_3.09_full_row.zip
File Date Size
BP2_3.09_full_row.zip Apr 10, 2017 7:53 PM
808.2 MB 0.63% Timeout error downloading
1 item"
It is absolutely absurd.
Click to expand...
Click to collapse
I tried to download it more then 30 times, always with same result. What is it gone wrong?
All ok. Download 3.09 ok. System updated to 3.10
Thank you androidblue
Sorry all, I accidentally enabled the "enhanced privacy" option. It is now fixed, and all should have no further problem to download.
androidblue said:
Sorry all, I accidentally enabled the "enhanced privacy" option. It is now fixed, and all should have no further problem to download.
Click to expand...
Click to collapse
The link to "REAL Blackphone 2 Silent OS 3.10 update (April 2017)" https://ln.sync.com/dl/c33995da0/63y9vshx-v9fwjz6c-3mz6yi7i-ky8ekwnr
still says "(#8026) Not authorized: Link has been deleted". Could you fix that too? Thanks.
Edit: also the link to the "original recovery" https://ln.sync.com/dl/9429c1020/rgjz6bep-dvmnd36x-r3j7q55c-3vrcmmsh
is broken "(#8026) Not authorized: Link has been deleted"
The link is not working anymore... Could you please reupload it?
akikoo said:
The link to "REAL Blackphone 2 Silent OS 3.10 update (April 2017)" https://ln.sync.com/dl/c33995da0/63y9vshx-v9fwjz6c-3mz6yi7i-ky8ekwnr
still says "(#8026) Not authorized: Link has been deleted". Could you fix that too? Thanks.
Edit: also the link to the "original recovery" https://ln.sync.com/dl/9429c1020/rgjz6bep-dvmnd36x-r3j7q55c-3vrcmmsh
is broken "(#8026) Not authorized: Link has been deleted"
Click to expand...
Click to collapse
Hi all
I can assure you that I didn't delete the links. The files still exists, but the link have been deleted.
I'm going to update the links and provide more soon to hopefully prevent this silly act of reporting the files are illigal.
Silent Circle - if you're behind this, please stop. This is unprofessional.
androidblue said:
In order to install it you must be on 3.09. install via original recovery... which is here...
Click to expand...
Click to collapse
How do you install this recovery_BP2_310_ORIGINAL.img file?
Thank you for these files.
akikoo said:
How do you install this recovery_BP2_310_ORIGINAL.img file?
Thank you for these files.
Click to expand...
Click to collapse
1) enter settings, about phone, scroll down to build, press until you are a developer, get out of about phone.
2) enter developer menu, allow oem unlock, shutdown phone, keep unconnected to computer/power.
3) install abd tools.
4) press the volume down, and then while being pressed press the power button. release when you see the "android" menu
5) magic time. connect cable to computer, type
Code:
fastboot flash recovery recovery_BP2_310_ORIGINAL.img
fastboot reboot
6) phones reboot. quickly press the power up + power key before the phone reboots. if it rebooted, just keep on pressing them until it reboots again and release when you see the android screen. welcome to recovery.
root have been posted. Have fun and try to break everything
(see 1st post in this thread)
hi, 4 is not working for me, no android menue, only reboot. 3.10 is installed. what do i have to do to get magisk installed ???
I updated to 3.0.10, but when i check updates, it still tells me update 3.0.10 available?
also when i try install twrp, it still says phone locked despite oem and usb debugging being unlocked
Rapyer said:
I updated to 3.0.10, but when i check updates, it still tells me update 3.0.10 available?
also when i try install twrp, it still says phone locked despite oem and usb debugging being unlocked
Click to expand...
Click to collapse
you missed an important step... unlocking it.
boot into bootloader (lower volume + power key)
connect to computer
If I remember correctly type:
Code:
fastboot oem unlock-go
and after your data will be deleted, you can now flash your recovery with TWRP.
Rapyer said:
I updated to 3.0.10, but when i check updates, it still tells me update 3.0.10 available?
also when i try install twrp, it still says phone locked despite oem and usb debugging being unlocked
Click to expand...
Click to collapse
Oh, forgot to mention - why do you still get a message that update 3.0.10 is available:
Your phone is still contacting to silent circle servers and it tries to brick you. soon to be explained how to stop it
Updates
Hello:
Phone already updated to 3.0.10 using your links.
No problem at all. Thank you very much.
Do you think you could provide additional updates in the near future?
Thanks
Good afternoon!
Make please the step-by-step detailed instruction on updating 3.10 and receiving root for simple users of lamers))
vendoelpiso said:
Hello:
Phone already updated to 3.0.10 using your links.
No problem at all. Thank you very much.
Do you think you could provide additional updates in the near future?
Thanks
Click to expand...
Click to collapse
Hi
Most likely yes. We will see
Hi all,
Here you will find modded TWRP recovery file with multiboot feature for Galaxy Note 3 Exynos (ha3g).
With it, you can have multiple ROMs on your device, test new roms without touching your principal rom, etc...
The method used is based on kexec-hardboot method created by mkasic (http://forum.xda-developers.com/showthread.php?t=1266827) with a lot of adaptations to make it work on our device (different kernel patches and usersapce program).
Generic demo of booting multiple roms from internal and external storages (https://www.youtube.com/watch?v=d9ekjWaUHYU)
Here is a simple video to show basically how to create and install a ROM. It shows also how to upgrade the rom with another zip after installation (https://youtu.be/B0cGRY4vwy0).
Very important recommendations before using multiboot :
BACKUP all your data first !
Please watch and follow video.
Use only if you have at least 5.5G available on your internal sdcard.
Installation :
Download here : https://www.androidfilehost.com/?fid=673368273298984528
Install zip in recovery mode
Informations :
- Your principal ROM is not affected at all by ROMS installed with multiboot
- Each ROM created sit in a subdirectory of your card : (Internal Storage)/multiboot/roms/NAME_OF_ROM
# ls -al /data/media/0/multiboot/roms/
drwxrwxrwx 2 root root 4096 Sep 8 03:32 Angelo-A7
drwxrwxrwx 2 root root 4096 Sep 9 00:10 DILSHAD-V10UX
drwxrwxrwx 2 root root 4096 Sep 8 02:05 Lineage14.1
drwxrwxrwx 2 root root 4096 Sep 8 03:33 RR-N-v5.8.4
drwxrwxrwx 2 root root 4096 Sep 8 02:21 aicp_ha3g_n-12.1
- Each ROM directory contains 5 image files (boot, system, data, cache and modem) with fixed size for the moment
# ls -al /data/media/0/multiboot/roms/Lineage14.1
-rw------- 1 root root 20971520 Sep 6 19:45 mmcblk0p13_modem.img
-rw------- 1 root root 329252864 Sep 8 21:10 mmcblk0p19_cache.img
-rw------- 1 root root 2554331136 Sep 7 05:59 mmcblk0p20_system.img
-rw------- 1 root root 3221225472 Sep 8 21:10 mmcblk0p21_data.img
-rw------- 1 root root 8388608 Sep 6 20:13 mmcblk0p9_boot.img
- Image files system, data and cache are sparsed so dont necessarely take all their size
# du -sh /data/media/0/multiboot/roms/Lineage14.1/
1.4G /data/media/0/multiboot/roms/Lineage14.1/
- Because android installation method with system.new.dat failed on external sdcard with vfat FS, I disabled option to install ROMs on external sdcard.
- You can copy /sdcard/multiboot/roms/NAME_OF_ROM to external/multiboot/roms/NAME_OF_ROM, il you want to boot ROM from external storage (only sdcard vfat supported). Copy can be done diretly from your PC with copy/paste of the folder.
- All kernels tested are working fine, except Aurora kernel which seems to work but takes long time to load (~1 minute). I recommend another kernel if you want to boot quickly.
- If you want to access your real internal sdcard, look at /multiboot/intsdcard
References / Credits :
mkasic : kexec-hardboot creator - http://forum.xda-developers.com/showthread.php?t=1266827
Tassadar : MultiROM creator - best project - http://forum.xda-developers.com/showthread.php?t=2011403 - bbootimg used
TWRP Team : https://twrp.me/
jcadduono : TWRP porting developper - https://forum.xda-developers.com/ga...elopment/recovery-official-twrp-ha3g-t3406899
All ROMs developpers
Version Information
Status: Stable
Current Stable Version: V1.0
Stable Release Date: 2017-09-09
Created 2017-09-09
Last Updated 2017-09-09
Philippe,
reserved
Hi,
First post updated with multiboot v1.0 released.
Please watch this video https://www.youtube.com/watch?v=B0cGRY4vwy0 and read carefully first post before using multiboot.
Philippe,
Ok...i'll try
Sent from my SM-A9100 using Tapatalk
Twrp nandroid
how to backup or restore twrp backup?
Thanks for the Multiboot option on Android
:good: Excellent option for trying out ROM without affecting the Usage ROM.
Tried out and it woks.
Thanks a lot Phil for providing this option.
First, Thank you for multiboot twrp.
Second, i m using rr rom and install multiboot twrp then install second rom angelo but i cant install gapps. Error 12.
Is there a way to have my actual storage for every rom?
nalbantoglu.mehmet said:
First, Thank you for multiboot twrp.
Second, i m using rr rom and install multiboot twrp then install second rom angelo but i cant install gapps. Error 12.
Click to expand...
Click to collapse
TW roms dont need gapps
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app
buick1356 said:
how to backup or restore twrp backup?
Click to expand...
Click to collapse
You can simply copy all the ROM folder (internal card/multiboot/roms) with your PC on another drive.
Maybe a next version will include nandroid backup for those without computer.
nalbantoglu.mehmet said:
First, Thank you for multiboot twrp.
Second, i m using rr rom and install multiboot twrp then install second rom angelo but i cant install gapps. Error 12.
Click to expand...
Click to collapse
I did not notice any trouble installing 6.0 gapps (pico) with AngeloA7 rom.
DontBrickYourPhone said:
Is there a way to have my actual storage for every rom?
Click to expand...
Click to collapse
Inside a multibooted rom, I already mentionned it on first post : If you want to access your real internal sdcard, look at /multiboot/intsdcard ( need a file explorer with root permission I guess)
Inside TWRP, when set to a ROM, your real storage is accessible in /sdcard2.
Philippe,
Phil_Suz said:
You can simply copy all the ROM folder (internal card/multiboot/roms) with your PC on another drive.
Maybe a next version will include nandroid backup for those without computer.
I did not notice any trouble installing 6.0 gapps (pico) with AngeloA7 rom.
Inside a multibooted rom, I already mentionned it on first post : If you want to access your real internal sdcard, look at /multiboot/intsdcard ( need a file explorer with root permission I guess)
Inside TWRP, when set to a ROM, your real storage is accessible in /sdcard2.
Philippe,
Click to expand...
Click to collapse
Thanks I noticed but I was wondering if I can have my data on that Rom as well, or is that not possible since they get sepereated?
DontBrickYourPhone said:
Thanks I noticed but I was wondering if I can have my data on that Rom as well, or is that not possible since they get sepereated?
Click to expand...
Click to collapse
Unfortunately no, I don't think that it could be possible with the way I separated the roms.
Philippe,
Backup and restore
Please add backup and restore options in multiboot for second ,.....roms
Can u write steps of how to do this ???
Pls
mehal123 said:
Can u write steps of how to do this ???
Pls
Click to expand...
Click to collapse
Please view the video post for the same purpose. if you still have a clarification, I will be glad to support.
well I've notice after adding ROM internal storage is just 8GB ,well is this default for TWRP? or there is option to choose exact space taken by each ROM?
check picture:
HTML:
https://ibb.co/inAtW5
Phil_Suz said:
Hi all,
Here you will find modded TWRP recovery file with multiboot feature for Galaxy Note 3 Exynos (ha3g).
With it, you can have multiple ROMs on your device, test new roms without touching your principal rom, etc...
The method used is based on kexec-hardboot method created by mkasic (http://forum.xda-developers.com/showthread.php?t=1266827) with a lot of adaptations to make it work on our device (different kernel patches and usersapce program).
Generic demo of booting multiple roms from internal and external storages (
)
Here is a simple video to show basically how to create and install a ROM. It shows also how to upgrade the rom with another zip after installation (
).
Very important recommendations before using multiboot :
BACKUP all your data first !
Please watch and follow video.
Use only if you have at least 5.5G available on your internal sdcard.
Installation :
Download here : https://www.androidfilehost.com/?fid=673368273298984528
Install zip in recovery mode
Informations :
- Your principal ROM is not affected at all by ROMS installed with multiboot
- Each ROM created sit in a subdirectory of your card : (Internal Storage)/multiboot/roms/NAME_OF_ROM
# ls -al /data/media/0/multiboot/roms/
drwxrwxrwx 2 root root 4096 Sep 8 03:32 Angelo-A7
drwxrwxrwx 2 root root 4096 Sep 9 00:10 DILSHAD-V10UX
drwxrwxrwx 2 root root 4096 Sep 8 02:05 Lineage14.1
drwxrwxrwx 2 root root 4096 Sep 8 03:33 RR-N-v5.8.4
drwxrwxrwx 2 root root 4096 Sep 8 02:21 aicp_ha3g_n-12.1
- Each ROM directory contains 5 image files (boot, system, data, cache and modem) with fixed size for the moment
# ls -al /data/media/0/multiboot/roms/Lineage14.1
-rw------- 1 root root 20971520 Sep 6 19:45 mmcblk0p13_modem.img
-rw------- 1 root root 329252864 Sep 8 21:10 mmcblk0p19_cache.img
-rw------- 1 root root 2554331136 Sep 7 05:59 mmcblk0p20_system.img
-rw------- 1 root root 3221225472 Sep 8 21:10 mmcblk0p21_data.img
-rw------- 1 root root 8388608 Sep 6 20:13 mmcblk0p9_boot.img
- Image files system, data and cache are sparsed so dont necessarely take all their size
# du -sh /data/media/0/multiboot/roms/Lineage14.1/
1.4G /data/media/0/multiboot/roms/Lineage14.1/
- Because android installation method with system.new.dat failed on external sdcard with vfat FS, I disabled option to install ROMs on external sdcard.
- You can copy /sdcard/multiboot/roms/NAME_OF_ROM to external/multiboot/roms/NAME_OF_ROM, il you want to boot ROM from external storage (only sdcard vfat supported). Copy can be done diretly from your PC with copy/paste of the folder.
- All kernels tested are working fine, except Aurora kernel which seems to work but takes long time to load (~1 minute). I recommend another kernel if you want to boot quickly.
- If you want to access your real internal sdcard, look at /multiboot/intsdcard
References / Credits :
mkasic : kexec-hardboot creator - http://forum.xda-developers.com/showthread.php?t=1266827
Tassadar : MultiROM creator - best project - http://forum.xda-developers.com/showthread.php?t=2011403 - bbootimg used
TWRP Team : https://twrp.me/
jcadduono : TWRP porting developper - https://forum.xda-developers.com/ga...elopment/recovery-official-twrp-ha3g-t3406899
All ROMs developpers
Version Information
Status: Stable
Current Stable Version: V1.0
Stable Release Date: 2017-09-09
Created 2017-09-09
Last Updated 2017-09-09
Philippe,
Click to expand...
Click to collapse
I tried and installed 3 different roms . It is working perfectly.
The minus points which i noted are,
we dont have enough internal space in the secondary roms(We have only 2 gb per rom)
If i restart the phone the original rom will be replaced the secondary roms ( without booting it via twrp)
Principal ROM
Sorry if I missed it in the OP.
How to get back to the original (primary/principal) rom which is parent to multiboot folder? set rom only shows the newly created roms.
notagamer said:
Sorry if I missed it in the OP.
How to get back to the original (primary/principal) rom which is parent to multiboot folder? set rom only shows the newly created roms.
Click to expand...
Click to collapse
Just restart or clear cache it will automatically revert to primary rom.
Can I give a working link to download !?
I don't believe I have seen this on the G7 forums so I figured I would make a quick guide for anyone whom is unfamiliar with the subject. RCTD is LGs Root Checking Tool that is triggered when the bootloader is unlocked as well as when BusyBox is installed, and is known to drastically affect the performance of the device after root. This is primarily seen in the V30 forums, but I assume it affects the performance of the G7 as well. There are tools to remove it as well as a script by John Fawkes, however from what I could tell, neither of them applied to the G7. It's a pretty simple process I recommend using root explorer and Zacaree1's Root Activity Launcher(play store). There are other ways to get to the hidden menu but if you have deleted the stock dialer or have any other issues, this app will always get you there and it has a massive amount of other great uses as well and I believe any root user should have it installed.
Step 1: Open Root Explorer and head to Product/Priv-app/SRTC and delete the app. This won't stop the process from starting however because LG uses an init.d script to run the tool at boot, leading to step 2.
Step 2: Head to System/Etc/Init and find
"lge.system.services.rc" long press on it to open it with text editor (if using Root Explorer) and scroll down until you see #RCT (Root Checking Tool). Under this line you will see a list of 3 or 4 commands. To stop them from running we want to put a # in front of each and save our changes. Example:
#service rctd /sbin/rctd
# class late_start
# user root
# group root
# seclabel u:r:rctd:s0
Now we've stopped the tool from running at start up, but it will still have the last time root was detected stored in the system. First, reboot to be sure that the edit survived a restart, and if it did then head to step 3.
Step 3: Head to Mnt/Vendor/Persist-LG/RTC and delete the file inside the RTC folder. If you delete the entire RTC folder, it will be recreated at reboot so it's pointless. Save and Reboot.
Step 4: Open the Root Activity Launcher app and type "Hidden" in the search box. This will lead you to the hidden menu activity (not operator hidden menu), so click on it to expand the list. Scroll down pretty far until you see "com.lge.hiddenmenu.HiddenMenu." You can click the icon that looks like a paperclip and it will pin the shortcut to your hidden menu to your home screen if you'd like, otherwise just click on the main line to open the Hidden menu, click SVC Mode and find LG RCT. If you did everything correctly, once you click LG RCT it should show Status-disabled. It will stay disabled regardless of a reboot. Other models like the V30 need additional init.d commands to be disabled. The G7 has these same init.d scripts, but for whatever reason we only needed to stop one of them. Done!
Attachments wouldn't load
Ty mate!!!
One question, i can do all these steps with magisk on stock? Would be reverted the changes at reboot?
---------- Post added at 02:04 AM ---------- Previous post was at 01:39 AM ----------
Bro, in the step 3, i cant find any path called "vendor" under the main path "Mnt", only a 0.00bit file called vendor
it did not work, step 4... status enable
manuhuelva said:
Ty mate!!!
One question, i can do all these steps with magisk on stock? Would be reverted the changes at reboot?
---------- Post added at 02:04 AM ---------- Previous post was at 01:39 AM ----------
Bro, in the step 3, i cant find any path called "vendor" under the main path "Mnt", only a 0.00bit file called vendor
Click to expand...
Click to collapse
You should be able to. I'm still stock, ULM20e Pie. What file manager are you using? That's strange that you can't to your vendor file. Is vendor accessible to you in TWRP?
Stvn77 said:
it did not work, step 4... status enable
Click to expand...
Click to collapse
Hmmm....can you check the Persist-lg folder and see if the file inside showed back up?
Yeedatoy said:
Hmmm....can you check the Persist-lg folder and see if the file inside showed back up?
Click to expand...
Click to collapse
following the path u post, i cant find, bc persist-lg is under vendor, and i cant find vendor
Delete
When you open up your file explorer, did you click the mount R/W button?
Yeedatoy said:
When you open up your file explorer, did you click the mount R/W button?
Click to expand...
Click to collapse
See this bro
https://youtu.be/5Tj5iCnkrj0
---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------
Ive done steps 1 and 2. Could not do 3
what's the point for the lg guys for slowing down the system if you have root?
and, the service is rct and after you have to look for rtc? they mess up the letters for what? something is strange
Yeedatoy said:
Hmmm....can you check the Persist-lg folder and see if the file inside showed back up?
Click to expand...
Click to collapse
yes. it showed back up
I've followed this guide on my v35 and i confirm it's working just fine!
Thanks!
Stvn77 said:
yes. it showed back up
Click to expand...
Click to collapse
Since None of my photos will load, check this post in the v40 threads to make sure your init.d script was edited with correctly.
https://forum.xda-developers.com/lg-v40/help/rctd-affects-devices-t3945207
cloud1250000 said:
I've followed this guide on my v35 and i confirm it's working just fine!
Thanks!
Click to expand...
Click to collapse
Awesome! I was getting a bit concerned for a moment while trying to think of why it hasn't worked for the others yet. Do you have LDB removed as well? I removed it so long ago that I forgot about it until I came across it in the V40 threads. I don't think it could interfere with this process, but I am trying to rule out anything that may be an issue for the others.
manuhuelva said:
See this bro
https://youtu.be/5Tj5iCnkrj0
---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------
Ive done steps 1 and 2. Could not do 3
Click to expand...
Click to collapse
https://photos.app.goo.gl/zgYxBS7uWJoAkGFm8
Yeedatoy said:
https://photos.app.goo.gl/zgYxBS7uWJoAkGFm8
Click to expand...
Click to collapse
bro, finally fixed, was the custom kernel, was no installed.
I fixed manually the 1.7 kernel !!!!!
Now reach 825mhz on gpu and have spectrum bro!!
if u want i can tell u how.
manuhuelva said:
bro, finally fixed, was the custom kernel, was no installed.
I fixed manually the 1.7 kernel !!!!!
Now reach 825mhz on gpu and have spectrum bro!!
if u want i can tell u how.
Click to expand...
Click to collapse
Tell me how? Please.
How to Fix
slyxo said:
Tell me how? Please.
Click to expand...
Click to collapse
steps:
1-Open ur bootloader
2-root and install magisk
3-flash xD-Kernel 1.7-Stock from drive folder (other stock folder) in TWRP and reboot to system https://drive.google.com/file/d/1MEFt7Ma2DOw8h7d_HjfyLN64Hnqz2bOo/view?usp=sharing credits to @Smart Ru
4a-poweroff
4b-go Qfil and extract ur boot_a or boot_b partition
5-extract Android image kitchen folder and put ur boot.img inside. https://forum.xda-developers.com/attachment.php?attachmentid=5024495&d=1590190159 credits to @osm0sis
6-run unpack script
7-paste the files i provided inside ramdisk folder and replace it https://drive.google.com/file/d/1HTT-0nm-y6tib_T1VQrws0EMreWia_Us/view?usp=sharing
8-go back and run repack script
9-pick the new image file and flash it on boot_a and boot_b by fastboot or qfil
10-dont care about error message at startup of android, it appears anyways with xd-kernel-1.7-stock kernel without modifications on every boot. It appears due to kernel kills dummy lg process from startup (2.0.2-custom doesnot)
11-download spectrum.
12-done.
Ive edited the profiles too for be more accurate to profile name:
-Balanced:
Governor "blu_schedutil" (is a light schedutil with powersaving on sleep mode, perfect for everyday use)
I/O "cfq" (most balanced I/O for everyday use)
Max/min Cpu.freq = 2.8ghz/800mhz (gold) 1.7ghz/300mhz (silver)
Max/min gpu.freq = 710mhz/160mhz (710mhz is stock top speed)
-Performance:
Governor "Performance" (cpu will run at full speed all the time, just pick it only for run benchmarks or for do selective heavy task u need, will consume battery fast)
I/O "deadline" (best for gaming-benchmarks)
Max/min Cpu.freq = 2.8ghz/1.05ghz (gold) 1.7ghz/748mhz (silver)
Max/min gpu.freq = 780mhz/160mhz
-Battery:
Governor "Powersave" (cpu will run at low speed most time, a really battery saving profile, u will have a little ui lag, but it gives u true promised battery saving)
I/O "SioPlus" (best battery saving I/O available in kernel)
Max/min Cpu.freq = 1.68ghz/825mhz (gold) 1.51ghz/300mhz (silver)
Max/min gpu.freq = 160mhz/160mhz
-Gaming:
Governor "Pixutil" (A port of official Pixel 3 Schedutil governor, awesome performance without stay full 2.8ghz all time, perfect for gaming ^^)
I/O "deadline" (best for gaming-benchmarks)
Max/min Cpu.freq = 2.8ghz/1.05ghz (gold) 1.7ghz/300mhz (silver)
Max/min gpu.freq = 825mhz/160mhz (highest gpu freq profile for more fps)
Yeah, I always get " there is an internal problem with your device" message on startup. That's normal. Spectrum never worked on 1.7 for me and neither did Klapse, but 2.0 fixed that for me.