[Multiboot] [Update 1/7/11] Create, manage and boot your ROM options via CWM! - Nexus One Android Development

Introduction
This thread describes an experimental mod that allows you to boot into other boot images stored in your sdcard.
The N1 does not have enough internal memory to store more than one android image, thus we have to use the sdcard for this.
NOTE:
This mod is experimental, and for advanced users only
Requirements (READ THEM CAREFULLY):
- A rooted and unlocked phone
- A FAST enough sdcard. This mod will work with any sdcard but I'd suggest at least a Class 4 card for performance reasons
- Your sdcard should have enough free space. Each 'boot option' that you create reserves 400MB of space in your sdcard
- In order to create a new boot option, you need a flashable zip over CWM of the ROM you wish to boot to. The flashable zip of the ROM is the same that is used for usual ROM installation. Also the zip should be using the latest update-binary format as is scripted in updater-script (e.g. the mount command takes 4 args, etc.)
Advanced Information regarding the process
- The mod requires a boot.img that is flashed by the zip. This is used for extracting the ramdisk, commenting out the mount mtd commands and using this ramdisk for chrooting into the ROM environment
- If no boot.img is existing, the ramdisk is picked up from /sdcard/ramdisk/
- The kernel used for booting all boot options is the one installed in the phone's boot mtd. This means that you need the respective kernel modules (e.g. WiFi) for this kernel, not the one that is bundled in the ROM that is multibooted. For example, if your main ROM is CM, pick the kernel modules from this one and push them to the multibooted ROM's /system/lib/modules/
Multiboot mod Installation
Download: N1_CWM-4.0.0.5-nobodyAtall-r2.img
Install via fastboot
Code:
Copy N1_CWM-4.0.0.5-nobodyAtall-r1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash N1_CWM-4.0.0.5-nobodyAtall-r1.img
Install via adb
Code:
adb push N1_CWM-4.0.0.5-nobodyAtall-r1.img /sdcard/
adb shell 'flash_image recovery /sdcard/N1_CWM-4.0.0.5-nobodyAtall-r1.img'
adb reboot recovery
Multiboot ROM Installation
- Boot into the recovery and navigate to the new 'multiboot' menu. There you'll see the following options:
Boot into selected option!
Select default boot option
Unset default boot option
Create boot option from zip
Delete existing boot option
Flash zip to boot option
- Select multiboot->Create boot option from zip and then pick the flashable ROM zip. Be patient, this step reserves the space and flashes the selected zip to the system.img in the sdcard
- If you need to flash additional zips for this ROM, Select multiboot->Flash zip to boot option, pick your newly created boot option and then pick the zip you need to flash.
- Select multiboot->Select default boot option and pick your newly created boot option
- Select multiboot-> Boot into selected option! (first boot will take some time depending on your sdcard speed).
To verify you have booted to your newly created boot option, check 'adb shell mount', it should say that /system /data and /cache is mounted from /loop* devices and not from mtd*
{
"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"
}
ROMS verified to multiboot
Well, any ROM should be able to multiboot provided the requirements stated above are covered. The following ones have been verified to work:
[ROM] CyanogenMod-7.1 for Nexus One
[ROM] NEXUS N1 Passion MIUI.us Presents MIUI Pure English [AOSP]
CM 7 ExtremeMod ROM by Ken Mood
Uninstall
- Normal reboots will boot from the phone's mtd partitions.
- This mod makes no changes to your phone's mtd partitions. Flashing a new recovery will uninstall the old one obviously.
- To remove installed boot options, navigate to multiboot->Delete existing boot option and pick you choice. Alternatively remove the boot option you want from /sdcard/clockworkmod/multiboot/
Disclaimer:
I can't be held responsible if this mod bricks your device / trashes your sdcard or makes it explode in your hands! Use it at your own risk!
​

Changelog:
(1/7/11) N1_CWM-4.0.0.5-nobodyAtall-r2.img
Fixed bug that flashed the multiboot ROM kernel in the phones kernel partition
Improved error reporting
(30/6/11) N1_CWM-4.0.0.5-nobodyAtall-r1.img
First version of CWM recovery providing the multiboot options

woww thanks

Well, this could be freaking awesome. I'll check it out at work

Nice one. Can we use CM nightlies that came after the RC?

method77 said:
Nice one. Can we use CM nightlies that came after the RC?
Click to expand...
Click to collapse
You can use it with any CM7 ROM

I am interested in this, i'm surprised that it hasn't created more of a stir.
I have installed the recovery, but don't want to do anything else without Nandroiding first. Only Nandroid seems to get stuck on "Backing up system..."
Any i doing something wrong?

Hello shorza,
To be honest, I've only been testing the multiboot part.
However, I think that backup works fine here:
Also the backup folder is created correctly:
~ # ls -la /sdcard/clockworkmod/backup/2011-07-01.06.49.58
drwxrwxrwx 2 root root 4096 Jul 1 06:52 .
drwxrwxrwx 5 root root 4096 Jul 1 06:49 ..
-rwxrwxrwx 1 root root 93489792 Jul 1 06:52 .android_secure.img
-rwxrwxrwx 1 root root 3670016 Jul 1 06:50 boot.img
-rwxrwxrwx 1 root root 37359168 Jul 1 06:52 cache.img
-rwxrwxrwx 1 root root 184136832 Jul 1 06:51 data.img
-rwxrwxrwx 1 root root 222 Jul 1 06:53 nandroid.md5
-rwxrwxrwx 1 root root 4194304 Jul 1 06:50 recovery.img
-rwxrwxrwx 1 root root 146908608 Jul 1 06:50 system.img
On another note, I'll be doing an update today to fix some bugs related to multiboot.

CWM 4.x has problems backing sd-ext, so that might be the reason why you don't see it (your pic shows you don't have an sd-ext partition to backup) and shorza does. It is also the reason why I haven't tried this yet - if it was based on AmonRa's I'd have jumped immediately, but since it is based on CWM I wanted first to see some feedback here...

Thanks for the help. Backup eventually worked, it just took a long time.
The problem is after zipping a new rom in multiboot, selecting it, then trying to boot into it, it took too long and I lost patience. It looked like it froze.
I'll try again tomorrow.

Maybe my sdcard is too slow.

shorza said:
Maybe my sdcard is too slow.
Click to expand...
Click to collapse
You need to be patient. It takes a long time to boot (especially for the first boot) and if the recovery seems frozen, this is a good sign - it means it's booting.

Posted -r2.
This fixes a bug that would flash the multiboot ROM's kernel to the phone's kernel partition. Also improves logging in case of errors.

Testing this out right now ... just got latest cyanogenmod nightly and latest miui (as of today) going on it and just switched back and forth. sucks about having to go into recovery to switch, needs to have a boot option when starting the phone haha.

So wifi doesn't work in the latest version of miui.us when using it as a multiboot option. such says in logcat "Failed to load Wi-Fi driver." it works when the rom is installed as normally so it must be the kernel from this application. but wifi on cyanogenmod works so that is good.

Will this work like a nandroid backup where it saves everythn from my last boot? Or will it save everythn on that same img. when i switch roms

looking at the directory structure, per multiboot rom it saves the boot.img, cache.img, data.img, and system.img .... I don't know how it uses them, but linux is magical in mounting images as a partition, doesn't have to be physical

This is because the ROM is run using the device's kernel and not the one that comes with the ROM as stated in the first post.
To make wifi work, simply copy your wifi kernel module from /system/lib/modules to this same did within the multibooted ROM.
Ellises said:
So wifi doesn't work in the latest version of miui.us when using it as a multiboot option. such says in logcat "Failed to load Wi-Fi driver." it works when the rom is installed as normally so it must be the kernel from this application. but wifi on cyanogenmod works so that is good.
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App

This actually works pretty well, however, the phone get quite hot.

[Q]Bug fixed??
I succeed multibooting
I got miui(main)&CM7(sub)
but subrom,cm7 can't use wifi
so I changed kernel but failed
and display
[mount expects 4 3args]
[error /sdcard/xxx... ]
[ status7 ]<<maybe
If you know what's the problem, plz teach me the way
thx and pardon my English

Related

[Multiboot] [Update 14/6/11] Create, manage and boot your ROM options via CWM!

Introduction
This thread describes an experimental mod that allows you to boot into other boot images stored in your sdcard. It's a good reason for users to upgrade to CWM recovery since it allows for much more extended functionality. It's also another good reason for devs to support CWM recovery.
Our 'petit' X10mini does not have enough internal memory to store more than one android image, thus we have to use the sdcard for this.
WARNING:
This mod is experimental, and for advanced users only. Use it at your own risk
Requirements (READ THEM CAREFULLY):
- CWM recovery pre-installed
- You need a FAST enough sdcard. I'd suggest not using this mod if your sdcard is less than Class 6
- Your sdcard should have enough free space. Each 'boot option' that you create reserves 400MB of space in your sdcard
- In order to create a new boot option, you need a flashable zip of the ROM you wish to boot to, as well as a patch for it's ramdisk.tar (if this is a custom ROM, stock ROMs don't need this). The flashable zip of the ROM is the same that is used for usual ROM installation. The patch should be provided by the ROM's cook.
Instructions for devs only
To create a bootable image, you have two options:
- Make use of CWM recovery (which can create boot images from update.zip) and provide a patch for your ROM that makes sure: app2sd is disabled, ramdisk.tar does not mount mtd* partitions under /system, /data, or /cache. This patch is also flashable via the new multiboot menu of CWM. If you need more info, see the attached MiniCM7-multiboot.zip
OR
- Manually create ext2 system.img, data.img and cache.img for users to push under /sdcard/clockworkmod/multiboot/<name>/
Multiboot mod Installation
- Flash the attached CWM multiboot zip via CWM
Multiboot ROM Installation
The following scenario is provided as a proof of concept in order to install MiniCM7 as a boot from sdcard option
- Reboot into the new recovery and navigate to the new 'multiboot' menu. There you'll see the following options:
Select default boot option
Unset default boot option
Create boot option from zip
Delete existing boot option
Flash zip to boot option
{
"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"
}
- Select multiboot->Create boot option from zip and then pick the MiniCM7 flashable zip (which you can find in the MiniCM7 thread). Be patient, this step reserves the space and flashes the selected zip to the system.img in the sdcard
- Select multiboot->Flash zip to boot option, pick your newly created boot option and then pick the MiniCM7-multiboot.zip. This will flash the patch needed for MiniCM7 in order to make it run from sdcard. You can use this option in order to flash any zip you want to any of the boot options you have already created
- Select multiboot->Select default boot option and pick your newly created boot option
- Reboot (first boot will take some time depending on your sdcard speed).
To verify you have booted to your newly created boot option, check 'adb shell mount', it should say that /system /data and /cache is mounted from /loop* devices and not from mtd*
Uninstall
- Practically, if you flash a ROM image it will revert CWM / chargemon to its original state. There is not problem in keeping this CWM / chargemon version though.
- To revert booting from your phone's memory instead of the sdcard, navigate to multiboot->Unset default boot option
- To remove installed boot options, navigate to multiboot->Delete existing boot option and pick you choice. Alternatively remove the boot option you want from /sdcard/clockworkmod/multiboot/
Disclaimer:
I can't be held responsible if this mod bricks your device / trashes your sdcard or makes it explode in your hands! Use it at your own risk!
​
wao great experiment NAA,
perfect time to install stock 2.1 and miniCM7
Damn, Great job nAa! My sdcard is lower than Class 6 (I am still using the stock 2GB sdcard!!) so I can't try this one. Waiting for other people's opinion about this.
Great work! =)
A class 4 sd is good?
Enviado desde mi X10mini usando Tapatalk
twins.7 said:
wao great experiment NAA,
perfect time to install stock 2.1 and miniCM7
Click to expand...
Click to collapse
IMHO, stock 2.1 should be installed as a 'multiboot option' and MiniCM7 in the internal phone's memory - not the other way round.
I'm hoping some dev could chip in with an update.zip for a stock 2.1 ROM that can be installed as a multiboot option
Damn, where the f**k is the "Thanks" button in tapatalk!?
Another great addition mate! Thank you for giving us, mods that other devices hadn't even dreamed of!
Regards,D_d
Sent from my Desire HD using Tapatalk
nobodyAtall said:
IMHO, stock 2.1 should be installed as a 'multiboot option' and MiniCM7 in the internal phone's memory - not the other way round.
I'm hoping some dev could chip in with an update.zip for a stock 2.1 ROM that can be installed as a multiboot option
Click to expand...
Click to collapse
why?
can I use this step below?
- backup my stock in recovery
- copy the backup file to multiboot folder
twins.7 said:
why?
can I use this step below?
- backup my stock in recovery
- copy the backup file to multiboot folder
Click to expand...
Click to collapse
No you can't do that.
You need to install the boot option from an update.zip.
Already created backups have a different fs type that can't be mounted seperately.
Does it works with miniCM6?
Hello nobodyAtall, can we install CM7 and CM6 in this multiboot? if yes how to do that? ( I have cm7 2.0.2 installed ) Thanks
gatobadio said:
Hello nobodyAtall, can we install CM7 and CM6 in this multiboot? if yes how to do that? ( I have cm7 2.0.2 installed ) Thanks
Click to expand...
Click to collapse
We need to 'edify' MiniCM6 first for that
nobodyAtall said:
We need to 'edify' MiniCM6 first for that
Click to expand...
Click to collapse
10Q !!! We'll be waiting for it
Going to try to boot CM7 on my CM6. Going to post results a bit later.
Thank you nobodyAtAll for another magnificent tool!
edit: Well, no harm for my device but no CM7 either. Tool created IMG's to my sdcard but doesn't boot from there.
Speechless with just a big smile in my face!!!
Thanks nobotyatall for this it's all you mate!!
My regards,
Ribben
just shifted to optimus 2x as my main device but decided to keep my Mini for my daughter and guess what (for nAa's absolute marvels) to keep my tweaking going on.
Great achievement nAa for that. you have made this small device a great value. addition. Thanks to you for that.
parthabhatta said:
just shifted to optimus 2x as my main device but decided to keep my Mini for my daughter and guess what (for nAa's absolute marvels) to keep my tweaking going on.
Great achievement nAa for that. you have made this small device a great value. addition. Thanks to you for that.
Click to expand...
Click to collapse
It's cause of SE having crippled it so badly that it's interesting to work on this stuff
Successfully boot cm7 from cm6 using my class 2 8gb sd card. But how can I boot back to my original cm6?
Send from my x10 mini using XDA premium app
@nobodyAtall
dude awesome work!!!
we need to talk!!!
i need ur help for this:
http://forum.xda-developers.com/showthread.php?t=1114544
does fix_permissions fix ownership/permissions on /system & /data ????
Is this method works with app2sd ( /data mounted on sd ext partition ) ?
And can I use this method to boot CM7 from SE 2.1.1.A.0.6 firmware ?

[GUIDE] Make any rom OS2SD

OS2SD for any rom ​
As I see there is many P500 users interested to put their ROM to sd card, so I'm providing this tutorial how to make any rom bootable from sd.
Requirements:
Linux or cygwin for Windows
Boot.img tools
Modified updater-script
Modified fstab
Correctly partitioned sdcard (Guide)
TWRP-OS2SD or TWRP-MULTI
Steps:
Replace updater-script in your's ROM zip with provided. It will probably work with all kitkat based roms. If not the idea is mounting /system on sd card so change all "mount("yaffs2", "MTD", "system", "/system");" lines with "mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system");" in original updater-script
Extract bootimg-tools.zip and paste boot.img from your rom in same foder
Open terminal or cygwin, locate folder with boot.img tools and type "./extractboot boot.img"
This will create out folder. Replace fstab.p500 and init.qcom.rc in out/ramdisk with provided (they might need rework on older roms)
In terminal type "./packboot"
Now rename boot_new.img to boot.img and pase it to rom zip
Flash rom zip with one of provided TWRP versions
should probably work back thru 4.0 but froyo/gingerbread init won't mount any sd partitions before boot is completed.
just curious, why this partition layout?
I used p2 for /data until wiping it by accident several times swapping my sd to a phone with pre-os2sd recovery.
of course, I've modded my own os2sd partition map several times now experimenting, and the order doesn't seem to matter.
and i was wondering, could you post your twrp modifications for internal/os2sd hybrid? i had one kinda working but it was glitchy.
I used this configuration to keep swap working if enabled, because default is p3. Also p4 for /data because it not used by anything else, so it's safe. I think you are right, order doesn't impact performance. Will send you config of twrp then be on pc.
Sent from my LG-P500 using xda premium
HardLight said:
I used this configuration to keep swap working if enabled, because default is p3. Also p4 for /data because it not used by anything else, so it's safe. I think you are right, order doesn't impact performance. Will send you config of twrp then be on pc.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I'm not seeing any other ROMs of this style floating around.
The only reason I didn't leave p3 for swap is that it wasn't being used yet when I started with the os2sd stuff. I tried sticking it on p2 (instead of the stubby sd-ext I had there to satisfy the odd this-or-that which demanded sd-ext,) and that worked ok, but I hadn't set sd-swap as a default in any builds.
since you're building similar stuff now, maybe I'll drift mine into your partition map in the interest of some sort of unification. and I'd like to match up the twrps, too.
especially if the sd-swap is working well on the p500.
everybody who's been dealing with my versions for any length of time now since it came out in February, is used to having to upgrade recovery and deal with incompatible backups from earlier releases anyway.
thanks for your contributions.
Thank You
HardLight said:
OS2SD for any rom ​
As I see there is many P500 users interested to put their ROM to sd card, so I'm providing this tutorial how to make any rom bootable from sd.
Requirements:
Linux or cygwin for Windows
Boot.img tools
Modified updater-script
Modified fstab
Correctly partitioned sdcard (Guide)
TWRP-OS2SD or TWRP-MULTI
Steps:
Replace updater-script in your's ROM zip with provided. It will probably work with all kitkat based roms. If not the idea is mounting /system on sd card so change all "mount("yaffs2", "MTD", "system", "/system");" lines with "mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system");" in original updater-script
Extract bootimg-tools.zip and paste boot.img from your rom in same foder
Open terminal or cygwin, locate folder with boot.img tools and type "./extractboot boot.img"
This will create out folder. Replace fstab.p500 and init.qcom.rc in out/ramdisk with provided (they might need rework on older roms)
In terminal type "./packboot"
Now rename boot_new.img to boot.img and pase it to rom zip
Flash rom zip with one of provided TWRP versions
Click to expand...
Click to collapse
Thank You for posting the guide as requested. Awesome, now I will try to make some ROMs bootable in sdcard, and try them in my phone.
bigsupersquid said:
should probably work back thru 4.0 but froyo/gingerbread init won't mount any sd partitions before boot is completed.
Click to expand...
Click to collapse
i think that you are wrong
i have a gingerbread installed on SD (and kitkat CM11 by mukulsoni on internal)
i used Multirom manager 5.1 by arnab321 based on work by Tassadar
http://forum.xda-developers.com/showthread.php?t=1828151
HardLight: can you make this procedure work like the one in Multirom ?
it allows me to have GB and KitKat installed at the same time, both are bootebel using the same recovery and im only a boot away from moving from one to the oder
danielboro said:
i think that you are wrong
i have a gingerbread installed on SD (and kitkat CM11 by mukulsoni on internal)
i used Multirom manager 5.1 by arnab321 based on work by Tassadar
http://forum.xda-developers.com/showthread.php?t=1828151
HardLight: can you make this procedure work like the one in Multirom ?
it allows me to have GB and KitKat installed at the same time, both are bootebel using the same recovery and im only a boot away from moving from one to the oder
Click to expand...
Click to collapse
multirom has preinit of its own, runs before GB init, and uses busybox to mount sd folders. It also mods init.rc to not mount the MTD partitions.
it would have to be recoded because, among other things, init.rc doesn't mount the filesystems anymore, it's moved to init.qcom.rc or init.device.rc (init.p500.rc or init.thunderc.rc in the current OS2SD versions.)
to use OS2SD like multirom, it would have to bind-mount folders or filesystem images from the card instead of mounting partitions directly, unless android can 'see' more than 4 card partitions now. It used to be limited to 4 back in GB.
Plus unless kexec is working every OS installed has to work with the kernel in the boot.img for tasssadar's original code (the app you're using is reflashing a new boot.img every time you change OS's, which will eventually trash your boot NAND memory,)
bigsupersquid said:
multirom has preinit of its own, runs before GB init, and uses busybox to mount sd folders. It also mods init.rc to not mount the MTD partitions.
it would have to be recoded because, among other things, init.rc doesn't mount the filesystems anymore, it's moved to init.qcom.rc or init.device.rc (init.p500.rc or init.thunderc.rc in the current OS2SD versions.)
to use OS2SD like multirom, it would have to bind-mount folders or filesystem images from the card instead of mounting partitions directly, unless android can 'see' more than 4 card partitions now. It used to be limited to 4 back in GB.
Plus unless kexec is working every OS installed has to work with the kernel in the boot.img for tasssadar's original code (the app you're using is reflashing a new boot.img every time you change OS's, which will eventually trash your boot NAND memory,)
Click to expand...
Click to collapse
ill start at the end
flashing boot is no worse then flashing a new rom but its less work and less time
i like GB for the speed and batt use but from time to time i need to run ting that wont work on GB(at list not on the 1 i chose after trying ~12 rom`s)
having kitkat installed and using multirom to change is faster
so, any chance of implementing the bind-mount option?
prite please
:fingers-crossed:
danielboro said:
ill start at the end
flashing boot is no worse then flashing a new rom but its less work and less time
i like GB for the speed and batt use but from time to time i need to run ting that wont work on GB(at list not on the 1 i chose after trying ~12 rom`s)
having kitkat installed and using multirom to change is faster
so, any chance of implementing the bind-mount option?
prite please
:fingers-crossed:
Click to expand...
Click to collapse
Just install your GB rom to internal memory and cm11 OS2SD to sd card, then make two flashable zips (or backups) of both roms boot.img and flash them respectively to rom you want to boot. Just keep in mind that GB won't be able to use sd-ext, because it's os2sd system partition.
Sent from my LG-P500 using xda premium
HardLight said:
Just keep in mind that GB won't be able to use sd-ext,
Click to expand...
Click to collapse
this is way i was hoping for the mount-bind
at the moment GB is on P2, swap on P3 and kitkat uses P4 as /sd-ext
i have some limited knowledge, ill try to see if i can do something wen ill have the time
any pointer on how i can use mount-bind ?
all the work on developing the p500 helps extend it life
thanks
p.s.
what is the MULTI in TWRP-MULTI?
danielboro said:
this is way i was hoping for the mount-bind
at the moment GB is on P2, swap on P3 and kitkat uses P4 as /sd-ext
i have some limited knowledge, ill try to see if i can do something wen ill have the time
any pointer on how i can use mount-bind ?
all the work on developing the p500 helps extend it life
thanks
p.s.
what is the MULTI in TWRP-MULTI?
Click to expand...
Click to collapse
the multi can flash os2sd & normal rom, so you have not to change between recoveries
ThAnKs
Thanks alot for this guide.....
have anyone tried it on an ICS rom ?
getting this error using cygwin
{
"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"
}
maybe it doesnt work with cygwin , i am trying to make genetICS 9.1.6 OS2SD compatible ..
nomancoolboy said:
getting this error using cygwin
maybe it doesnt work with cygwin , i am trying to make genetICS 9.1.6 OS2SD compatible ..
Click to expand...
Click to collapse
For starters , you need Perl installed for that script.
Second, ics don't use fstab, you'll have to change init.rc
And maybe even recompile init with a delay inside, like on GB.
otherwise init may not mount the card partitions.
The easy way to run ICS from card is tasssadar's multirom. You can find the thread buried in this forum.
I'm using HardLight's GenetICS 9.1.7 with the OS2SD mod. It's the most stable and smoothest with long battery life and 1.5GB in the data partition for my apps. Also successfully made it with Hephappy's ICS Plus simply modifying the updater-script inside the zip and search the mounting points in the 'init.rc' and 'init.qcom.rc', then just have to modify the lines following the first post.
Greetings from Costa Rica!
Enviado desde mi LG-P500 usando Tapatalk
@HardLight
This is twrp-multi, renamed to boot.img. I have previously extracted recovery images this way using apktool.
[email protected]:~/bootimg-tools$ ./extractboot boot.img
Page size: 2048 (0x00000800)
Kernel size: 2803424 (0x002ac6e0)
Ramdisk size: 2294087 (0x00230147)
Second size: 0 (0x00000000)
Board name:
Command line: mem=471M console=ttyMSM2,115200n8 androidboot.hardware=p500 no_console_suspend
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
gzip: ../../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Any other tools needed to make this work? (ubuntu 14.04)
manu3193 said:
I'm using HardLight's GenetICS 9.1.7 with the OS2SD mod. It's the most stable and smoothest with long battery life and 1.5GB in the data partition for my apps. Also successfully made it with Hephappy's ICS Plus simply modifying the updater-script inside the zip and search the mounting points in the 'init.rc' and 'init.qcom.rc', then just have to modify the lines following the first post.
Greetings from Costa Rica!
Enviado desde mi LG-P500 usando Tapatalk
Click to expand...
Click to collapse
Can you share the modified files to be replaced in the rom.
hi all - thanks for these instructions. I tried to apply these to cm-9.1.5-GenetICS-Final-P500+gapps.zip and cm-9.1.7-GenetICS-HardLight-p500.zip.
In those roms I had to update the updater-script (I had to remove the format command otherwise the install would fail - but i figured that should be ok since the ext4 partition can be formatted externally - if i remember to do it).
I also updated the init.rc in the (mount mtd partitions section), but no updates to the init.qcom.rc
Each time I try to install a ROM, the device gets stuck at the LG boot logo.
I get the same problem with those zip's installing from TWRP MULTI's "Internal" mode. So I suspect something else is wrong...
interestingly, the only zip I can install successfully is the cm11.0.0-20160101-os2sd-ext4-p500.zip. Works like a charm, just dies in a matter of hours with Wifi on.
eldamobo said:
hi all - thanks for these instructions. I tried to apply these to cm-9.1.5-GenetICS-Final-P500+gapps.zip and cm-9.1.7-GenetICS-HardLight-p500.zip.
In those roms I had to update the updater-script (I had to remove the format command otherwise the install would fail - but i figured that should be ok since the ext4 partition can be formatted externally - if i remember to do it).
I also updated the init.rc in the (mount mtd partitions section), but no updates to the init.qcom.rc
Each time I try to install a ROM, the device gets stuck at the LG boot logo.
I get the same problem with those zip's installing from TWRP MULTI's "Internal" mode. So I suspect something else is wrong...
interestingly, the only zip I can install successfully is the cm11.0.0-20160101-os2sd-ext4-p500.zip. Works like a charm, just dies in a matter of hours with Wifi on.
Click to expand...
Click to collapse
roms not built for kernel swapped system/userdata (kitkat only built this way, and not older kitkat versions) will flash to the wrong partition and won't boot.
change your updater-script to switch system and userdata for older roms to flash correctly with the twrp-multi in internal mode.

[MOD][V500] MultiROM v33a [No Kexec Workaround][2017-01-30]

{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for LG G PAD 8.3 (V500). It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install:
Modified recovery - download the IMG file from second post and use fastboot or TWRP to flash it.
MultiROM - download the ZIP file from second post and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file or TWRP Backup and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.​
Source code
MultiROM - https://github.com/multirom-v500/multirom
Modified TWRP - https://github.com/multirom-v500/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/multirom-v500/android_device_lge_v500​
Thanks a lot to Tasssadar for creating this awesome utility.
And to @nkk71 for the No-KEXEC workaround
XDA:DevDB Information
MultiROM, Tool/Utility for the LG G Pad 8.3
Contributors
beroid, nkk71
Source Code: https://github.com/multirom-v500
Version Information
Status: Stable
Created 2016-11-25
Last Updated 2017-01-30
Downloads
AndroidFileHost
No-kexec workaround
Mini FAQ:
Q: What is the no-kexec workaround?
A: The no-kexec workaround by @nkk71 allows you to use MultiROM without having to flash a kexec enabled kernel.
Please read all things about no-kexec workaround from the author words only, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4
@beriod can i install Malladus In this Or Stock 4.4.2?? You only say dont add Stock Lollipop Rom?
Bootloop!
Install Multirom and TWRP Patched By Multirom, then Add Rom And I flash is Validus (5.1.1) Romafter it go on list rom, click the validus in list, flash zip, (GAPPS) and (Patched kernel), and bootloop
Jansxel said:
Install Multirom and TWRP Patched By Multirom, then Add Rom And I flash is Validus (5.1.1) Romafter it go on list rom, click the validus in list, flash zip, (GAPPS) and (Patched kernel), and bootloop
Click to expand...
Click to collapse
You need to have kernel with kexec-hardboot patch only in your primary ROM!
beroid said:
You need to have kernel with kexec-hardboot patch only in your primary ROM!
Click to expand...
Click to collapse
Oh Ahaaha Sorry i try it later. This is the first time i use this.
@beroid can you link me to your kernel v500 sources so i can patch up my cm12.1 kernel, to use kexec hardboot? already doing it on Z2.
thanks.
Can anyone patch stock kernel ? Haven't enough knowledge to that,but I want very much have stock as primary
Написан с LG-V500. Работает на XDA Forums Pro
Maraudeur said:
Can anyone patch stock kernel ? Haven't enough knowledge to that,but I want very much have stock as primary
Написан с LG-V500. Работает на XDA Forums Pro
Click to expand...
Click to collapse
I was thinking about just installing CM12.1 , why do I want to keep stock as primary? if I might ask?
i've integrated that kexec hard-boot patch on my v500 kernel, working fine, but theres an issue...
the screen starts very dimmed, and stays that way until it fully boots CM12. it reminds me of the issue we have with the 4.2.2 base and the 4.4.2 base.
infected_ said:
i've integrated that kexec hard-boot patch on my v500 kernel, working fine, but theres an issue...
the screen starts very dimmed, and stays that way until it fully boots CM12. it reminds me of the issue we have with the 4.2.2 base and the 4.4.2 base.
Click to expand...
Click to collapse
brightness: MiltiRom -> Settings -> Screen Brightness
beroid said:
brightness: MiltiRom -> Settings -> Screen Brightness
Click to expand...
Click to collapse
you must have some sort of issue reading my posts, or my explaining skills suck ..
its not on MR recovery the issue.... its after boot, when the MR menu shows to select ROM, the screen is dimmed, and stays that way until it fully boots to CM12.
nevermind... you we're right... this doesnt happens on sirius, so it was a new prob for me.
thanks and regards!
Update is up (MultiRom + Kernel).
MultiRom Now Supports Stock rom V30A-Korea as secondary
hmmm... @beroid, can you explain the fact, deleted 3 secondary ROMs, after that i flashed 20E as secondary, booted fine..
next thing i am twrp, my internal partition only has 8223MB ? already wiped it 3 times, changed recovery, reflashed CM12.. same thing.
i suppose i will have to flash 4.2.2 and then upgrade to CM12 to fix it, right?
ps: screen in attachment is after the 3 wipes i did...
TWRP shows free space of partition.
in attachment:
Capacity: 11 Gib
Used: 3 Gib
Available: 8 Gib
beroid said:
TWRP shows free space of partition.
in attachment:
Capacity: 11 Gib
Used: 3 Gib
Available: 8 Gib
Click to expand...
Click to collapse
i dont have any secondary ROM installed... those 3GB are the system partitions of the host ROM?
11 GiB are 11.8GB
16GB are 14.90Gib
where did the 3.4GiB (3.6GB) + 3 GiB (3.2GB) went?
sorry for all the noobish questions but is the first time i ever used MR on the v500, and i suppose i never noticed the complete internal memory size.
check /data/media/0/multirom/
beroid said:
check /data/media/0/multirom/
Click to expand...
Click to collapse
ok give me a minute.
---------- Post added at 11:31 ---------- Previous post was at 11:28 ----------
beroid said:
check /data/media/0/multirom/
Click to expand...
Click to collapse
empty. the folder doesnt even exists 'cause ive uninstalled MR and the MR twrp.
infected_ said:
ok give me a minute.
---------- Post added at 11:31 ---------- Previous post was at 11:28 ----------
empty. the folder doesnt even exists 'cause ive uninstalled MR and the MR twrp.
Click to expand...
Click to collapse
Multirom uses only /data/media/0/multirom/
From device with Korean LP (never installed MultiRom).

[Recovery][6633][twrp] Unofficial TWRP 3.0.2 for Z3 Dual D6633

{
"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"
}
Bismillahi Alrahmani Alraheem
(in the name of God the most gracious, the most merciful)
Finally Unoffoicial TWRP 3.0.2 is here for Dual sim version of XPERIA Z3 (D6633)!!
Introduction:​
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
And much more...
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit Instance - http://gerrit.omnirom.org
Notes About Sony Devices:
The Xperia devices have a recovery-in-boot arrangement. This means that the recovery is booted using the regular kernel / boot image in the device. Team Win has worked with the FreeXperia device maintainers to come up with a way to extract the ramdisk from the FOTAKernel partition and use the ramdisk from that partition instead of the recovery that is included in the boot image of your device. This means that if you install current CM nightlies and flash TWRP to the FOTAKernel partition, you will be able to use TWRP instead of the CWM or CM recovery that normally comes in a CM boot image. Other boot images including stock kernels can be repacked to include this extraction utility to allow you to use TWRP from the FOTAKernel partition. This setup allows you to choose what recovery you want to have installed and allows you to update your recovery more easily. Unfortunately this setup requires that the boot image that you have installed include the ramdisk extraction utility. The source for this utility is here:
https://github.com/Dees-Troy/extract_elf_ramdisk
This utility is designed to work in conjunction with the current methods that most AOSP ROMs use for the ramdisk and can also be used on stock kernels. This setup means that you must have a kernel or boot image installed that will use the FOTAKernel method. Most AOSP based ROMs like OmniROM or CyanogenMod will support this method. Some stock kernels may also support the FOTAKernel method.
What does all this mean? It means that TWRP may not work on your device unless you install other custom software as well. Check with your ROM developer to see what they support.
DOWNLOAD:​
Please notice that it won't work in stock based roms, only custom roms will run it
20160907 (img)
20160907 (zip)
Installation methods
TWRP Install (Requires TWRP 2.8.4 or higher already installed):​
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash.
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/recovery-twrp-302-z3dual.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Fastboot method:
you should have fastboot in your pc (either downloaded separately or with android SDK)
fire up Terminal (Linux and OS X) or CMD window (MS Windows) in the folder you have the image on it and it is preferred to copy the image to the folder of fastboot so the following command work then type:
Code:
fastboot flash FOTAKernel recovery-twrp-302-z3dual.img
don't forget to put ./ before 'fastboot' if you are using OS X or linux (./fastboot)
ZIP method:
flash the zip using any recovery
Themes and colors:
HERE
(Read Post #2 in the link if you want to customize, I'll be making pre-made themes later on inshaaAllah (God willing) )
NOTE: You are free to repack it and even sharing it without taking my permission
Please Donate If you want me to support Z3 dual more and more, it is back to you ​
XDA:DevDB Information
TWRP 3.0.2 for Z3 Dual D6633, Tool/Utility for the Sony Xperia Z3
Contributors
Muhammad Ashraf
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Testing
Created 2016-06-25
Last Updated 2016-09-07
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
sorry for the late reply, I am not sure why does it act like that
i'll try to make a zip file for that issue
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Oh, I am SOOOOOOOO Sorry, You have noticed me, By mistake I have uploaded Cyanogenmod Recovery instead of twrp
figuring that out now
I am sorry all of you
thanks man
EDIT: DONE
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Unlocked or Locked bootloader?
(Does this require an unlocked bootloader?)
I cannot get to recovery mode using DD or fastboot
Command will go through but adb reboot or h/w combos wont get me recovery. How do I install recovery ? . I have a ROM that can only be installed via recovery pl help
I cannot get to recovery mode using DD or fastboot
FAILED (remote: Command not allowed)
it always says "FAILED (remote: Command not allowed)"
should the bootloader be unlocked ?!
what is the problem here?!
Hi, i flashed the .img using my twrp, the only option on "select partition" was kernel, i know i shouldn't have done it, but i did. Now the phone doesn't boot, it keeps on a black screen. I think i need to flash a new kernel, can someone help me? Thanks
edit
Locked bl
Excellent WORK +++++
Bismillahi Alrahmani Alraheem YOU are my god!
Well done. You are the man. Exellent work with this TWRP for my D6633 (z3 dual)
it saved my life!
bryantshurley said:
I cannot get to recovery mode using DD or fastboot
Click to expand...
Click to collapse
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.
"fastboot flash boot recovery-twrp-302-z3dual.img" got me to a new recovery screen and can no longer boot the system.
rzepek2pl said:
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.
Click to expand...
Click to collapse
That was a bad advice. Now I only have TWRP on my phone. Only boots into this!
Can it be saved? How?
Your 20160907.zip based on TWRP 3.0.2 was put into root & flashed with TWRP v2.8.7.0 which did not update, when re-launching recovery I was still on v2.8.7.0

[OREO]TWRP COMPLETE BACKUP

{
"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"
}
​Requirements:
Unlocked Honor 7x : See this [But don't flash twrp from anywhere else before backing up your device. Use twrpimgmount_ramdisk for backing it up first.]
Download:
TWRP Complete Backup
TWRP Img mount not tested yet
Instructions:
Flash twrpimgmount_ramdisk.img through fastboot
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
Press and hole both volume + power on to boot to erecovery OR volume up + power on to boot to twrp (i don't know which combination is of which one) i suggest you to flash twrp to erecovery_ramdisk partition using twrp too.
Backup/restore and flash image functions are tested for system/vendor/product/version/cust/oeminfo/recovery/recovery2/boot rest of them are not tested by me but should work.
Note: It is suggested to make a complete backup in memory card before rooting your Honor 7x.
After backing up, flash TWRP Complete Backup Ramdisk
Join Telegram group if you are willing to test latest stuff
Credits:
Ported form Honor 6x : OP
Follow next:
1. Flash Magisk 16.0+ to root
XDA:DevDB Information
[OREO]TWRP COMPLETE BACKUP, Tool/Utility for the Honor 7X
Contributors
Sudeep Duhoon, Pretoriano80, zxz0O0
Version Information
Status: Testing
Created 2018-03-17
Last Updated 2018-04-07
For Nougat : Go Here
Reserved
TWRP on my OREO Beta Not Detecting My Phone on Pc no Response Please Check Ur Recovery
Can I do this with the Bnd-L24 model that has the bootloader unlocked with TWRP installed?
Great bhai
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
topnomi said:
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
Click to expand...
Click to collapse
Computer doesn't see phone via USB - Known bug
TWRP reports "no OS installed" - Intentional, it has to work like this.
TWRP cannot read /sdcard (internal storage) - Your internal sd is encrypted and this twrp has no decryption support
Sudeep Duhoon said:
Computer doesn't see phone via USB - Known bug
TWRP reports "no OS installed" - Intentional, it has to work like this.
TWRP cannot read /sdcard (internal storage) - Your internal sd is encrypted and this twrp has no decryption support
Click to expand...
Click to collapse
one further note, using the "complete_twrp_ramdisk.img" TWRP was able to see the installed OS, and offered to install the TWRP app.
Sudeep Duhoon said:
i suggest you to flash twrp to erecovery_ramdisk partition using twrp too.
Click to expand...
Click to collapse
What does this mean?
---------- Post added at 10:08 AM ---------- Previous post was at 09:36 AM ----------
I couldn't get it to backup. It always fails at data or system (If I don't select data).
Tried both images.
how can i flash the stock recovery? i was able to brick my device
Edit: nvm i fixed it
topnomi said:
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
Click to expand...
Click to collapse
Hi, I'm glad to report that although the first recovery that is twrpimgmount_ramdisk.img failed to backup system as I got the same error message as above but I was able to flash some other partitions like kernel, recovery etc... I actually selected a bunch of them.
Anyway most importantly after flashing the complete_twrp_ramdisk.img, I was able to backup system successfully. I'm using the Indian variant BND AL10 MODEL. I hope this helps some one out there.
I have a dumb question: Now, that the system is backed up with twrp, if I mess up my phone ever, can I simply restore this system img and be able to boot back into the os? Do I need to install any other partitions? I don't care about data. Please let me know.
Hi, I flashed this complete_twrp_ramdisk.img and now I want to go back to stock recovery of oreo which is bnd_recovery_nocheck.img from the other post. I tried using adb and it fails. I tried using the this twrp but it shows a lot of partitions to choose from and I'm confused example: ramdisk recovery, recovery_vendor, recovery_ramdisk etc... there are sooooooo many. I tried recovery_vendor and also ramdisk but it doesn't work. Can you please tell me how to install the stock recovery?
Does anybody have a BND-L21 backup of the system partition?
Edit: nvm i found it
Can someone tell me how to install stock recovery after installing the above complete_twrp_ramdisk.img as I'm unable to flash using adb. I tried "fastboot flash recovery recovery.img" and also "fastboot flash recovery_ramdisk recovery.img" I tried flashing the BND_recovery_nocheck.img from the other post which is a stock one.
I also tried flashing it using this twrp to the partition recovery_ramdisk and gives the error saying "the size is larger than the device" Please someone help.
I have tried couple times to install new release
twrp_ramdisk_oreo_7-4-18.img
Click to expand...
Click to collapse
But I can only get to twrp splash screen.
OP change-log has no information about this new release, so maybe is still not ready.
telegram group has mention of this , but did not help Yet.
**EDIT**
It was suggested by DEV in telegram to just be patient and try again. This third time installed 4-7-2018 released version it loaded right into recovery, without any delay.
Don't know if it is coincidence or not but before I was on RRos ROM. and now I am back on EMUI 8
Well, the mess here you have gentlemen, nichrome you do not understand where the root for 7ku, where to 8ku, what tvrp to put for 8ki for everyday needs.
---------- Post added at 03:56 PM ---------- Previous post was at 03:52 PM ----------
Which TWRP can I put in order to flush the root on the 8th oreo?
What TWRP should I be using on RROS Room? In order to install Magisk?
what are the 2 images with dates for? twrp_ramdisk_oreo_19-4-18.img and twrp_ramdisk_oreo_7-4-18.img?
i tried flashing both in twrp after using fastboot to flash the inistial ramdisk and neither one boot into recovery they get stuck at the twrp splash screen but the image labeled complete_twrp_ramdisk.img boots fine.
darkmage1991 said:
what are the 2 images with dates for? twrp_ramdisk_oreo_19-4-18.img and twrp_ramdisk_oreo_7-4-18.img?
i tried flashing both in twrp after using fastboot to flash the inistial ramdisk and neither one boot into recovery they get stuck at the twrp splash screen but the image labeled complete_twrp_ramdisk.img boots fine.
Click to expand...
Click to collapse
Afaik they are test builds (ports) of data decryption enabled twrp.
I had them working when on the Oreo beta but cannot get to work on RR or the new official Oreo.

Categories

Resources