Team Win Recovery Project !
{
"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"
}
Permanent TWRP Recovery 2.8.1.0
Huawei Ascend P6
Changelog :
Code:
What's new in 2.8.1.0 :
[LIST]
[*] MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
[*] TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
[*] Temperature support - thanks to bigbiff
[*] Various other bugfixes and tweaks
[/LIST]
What's new in 2.8.0.0 :
[LIST]
[*] Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
[*] Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
[*] Add support for color in the console and give error, warning, and highlight lines different colors
[*] Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
[*] Improve handling of /misc thanks to mdmower
[*] Improve setting of time on Qualcomm devices thanks to [NUT]
[*] Allow using images on slidervalue GUI objects thanks to Tassadar
[*] Allow using variables and addition and subtraction in variables for easier theming
[*] Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
[*] Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
[*] Other minor fixes and improvements
[/LIST]
What's new in 2.7.1.0 :
[LIST]
[*] Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
[*] Various bugfixes to backup and restore
[*] Improvements to USB storage handling
[*] Added a class to search for files to make finding the correct brightness file automatic in most cases
[*] Various other bugfixes and tweaks
[/LIST]
What's new in 2.7.0.0 :
[LIST]
[*] Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
[*] Allow sideloading from /tmp on encrypted devices
[*] Check for a crypto footer before asking for a password to prevent user confusion
[*] Additional checks for validity to auto generated backup names
[*] Text wrap in the console output
[*] Proper caps lock support in the keyboard
[*] Mouse support via USB OTG for devices with a broken digitizer
[*] Improve scanning of storage locations for OpenRecoveryScript
[*] Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
[*] Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
[*] Update SuperSU to 1.93 and improve installation process
[*] Added selinux contexts restoration to fix permissions
[*] Load RTC offset on Qualcomm devices to fix the date/time in recovery
[*] USB Mass Storage fixes Add SELinux support checking
[*] Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
[*] Add 4.4 AOSP decrypt support
[*] Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
[*] Various SELinux fixes and bug fixes
[/LIST][CENTER][/CENTER]
Downloads :
Code:
[CENTER]
* [B][I][FONT="Courier New"][COLOR="DeepSkyBlue"][SIZE="3"]New Update :[/SIZE][/COLOR][/FONT][/I][/B] [URL="http://forum.xda-developers.com/showpost.php?p=56615625&postcount=170"]TWRP 2.8.1.0[/URL] !
* [URL="https://www.androidfilehost.com/?fid=23622183712471258"]openrecovery-twrp-2.8.0.0.img[/URL]
* [URL="https://www.androidfilehost.com/?fid=23622183712471268"]openrecovery-twrp-2.8.0.0.zip [/URL]
* [URL="http://www.androidfilehost.com/?fid=23501681358547533"]openrecovery-twrp-2.7.1.0.img[/URL]
* [URL="http://www.androidfilehost.com/?fid=23501681358547536"]openrecovery-twrp-2.7.1.0.zip[/URL]
* [URL="http://www.androidfilehost.com/?fid=23329332407584760"]openrecovery-twrp-2.7.0.0.img[/URL]
* [URL="http://www.androidfilehost.com/?fid=23329332407584761"]openrecovery-twrp-2.7.0.0.zip[/URL][/CENTER]
Installation :
Code:
[CENTER]
* [FONT="Arial Black"]Make Sure That Your Device Already Running Android Version KitKat ![/FONT]
*[FONT="Arial Black"] Image File ( openrecovery-twrp-2.8.0.0.img ) :[/FONT]
[LIST]
[*] boot your device in bootloader mode by :> adb reboot bootloader
[*] flash custom recovery :> sudo fastboot flash recovery openrecovery-twrp-2.8.0.0.img
[*] reboot your device :> sudo fastboot reboot
[/LIST]
* [FONT="Arial Black"]Zip File ( openrecovery-twrp-2.8.0.0.zip ) :[/FONT]
[LIST]
[*] copy this archive in your device ( internel/external storage )
[*] boot your device in previous TWRP 2.7.1.0 : > adb reboot recovery
[*] flash zip file
[*] reboot to system
[*] next reboot in recovery will be on TWRP 2.8.0.0 instead TWRP 2.7.1.0 !
[/LIST]
[/CENTER]
Issues :
Code:
[CENTER]
* Internal Storage Not Mount ;
* Wipe -> Advanced Wipe -> Internal Storage -> Repair or Change File System -> Cannot Be Done : [B][COLOR="Red"]Invalid partition selection[/COLOR][/B] ;[/CENTER]
Source :
Code:
[CENTER]* [URL="https://github.com/TeamWin/Team-Win-Recovery-Project/tree/twrp2.7"]TeamWin GitHub[/URL] !
* [URL="https://github.com/omnirom/android_bootable_recovery/tree/android-4.4"]omnirom github[/URL] !
* [URL="https://github.com/surdupetru/twrp"]Huawei P6 TWRP - GitHub[/URL] [/CENTER]
Credit :
Code:
[CENTER]* [URL="http://teamw.in/project/twrp2"][B]Team[COLOR="RoyalBlue"]Win[/B][/COLOR][/URL]
* [URL="http://forum.xda-developers.com/showthread.php?t=1943625"]Dees_Troy[/URL][/CENTER]
regards,
Surdu Petru
Revert To Stock Recovery KitKat
Downloads :
Code:
[CENTER][FONT="Arial Black"]* Stock Firmware Huawei B510 KitKat :[/FONT]
* boot.img image format : [URL="http://www.androidfilehost.com/?fid=23501681358546458"]boot.img[/URL]
* recovery.img image format : [URL="http://www.androidfilehost.com/?fid=23501681358546459"]recovery.img[/URL]
[/CENTER]
Code:
[CENTER][FONT="Arial Black"]* Stock Firmware Huawei B506 CN KitKat :[/FONT]
* boot.img image format : [URL="http://www.androidfilehost.com/?fid=23329332407584770"]boot.img[/URL]
* boot.img zip format : [URL="http://www.androidfilehost.com/?fid=23329332407584771"]stock-506-boot.zip[/URL]
* recovery.img image format : [URL="http://www.androidfilehost.com/?fid=23329332407584772"]recovery.img[/URL]
* recovery.img zip format : [URL="http://www.androidfilehost.com/?fid=23329332407584773"]stock-506-recovery.zip[/URL][/CENTER]
Installation :
Code:
[CENTER]* flash stock boot.img in bootloader mode : > fastboot flash boot boot.img
* flash stock recovery.img in bootloader mode : > fastboot flash recovery recovery.img
* reboot your device from bootloader mode : > fastboot reboot
* zip files : stock-506-boot.zip & stock-506-recovery.zip must be installed under custom recovery TWRP ![/CENTER]
Oooh! Awesome job!
Thanks for your amazing job surdu!!
Enviado desde mi P6-U06
surdu_petru said:
Team Win Recovery Project !
[*] Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
Click to expand...
Click to collapse
Faster graphics rendering only in recovery and does not mean better gamming performance right???
Thanks for this !! u'r awsome!
Thanks surdu!
BTW is this official build? Just wondering.
EDIT:
Tried flashing the boot.img, resulted with my wifi not working on OMNI ROM.
I reflashed the boot.img from the omni.zip, and now its working. idk.
Here I made an user friendly cmd installer for TWRP 2.7.0.0. If you guys want to, take a look here.
http://forum.xda-developers.com/showthread.php?t=2709607
Will it work if I flash Stock 506 boot and recovery and then run B125 on top of that?
Or MUST JB use its own boot and recovery and KK its own boot and recovery?
Thank you,
Falci
RicardoA said:
Faster graphics rendering only in recovery and does not mean better gamming performance right???
Thanks for this !! u'r awsome!
Click to expand...
Click to collapse
Yes, available only in recovery !
bokchoi2020 said:
Thanks surdu!
BTW is this official build? Just wondering.
EDIT:
Tried flashing the boot.img, resulted with my wifi not working on OMNI ROM.
I reflashed the boot.img from the omni.zip, and now its working. idk.
Click to expand...
Click to collapse
Stock boot.img is ONLY for Stock Firmware and not for custom rom !
Not yet official, cause I have some issue packing boot/recovery-ramdisk from OmniROM ! As soon as I solve this problem, will be also officially launched.
Falcifer said:
Will it work if I flash Stock 506 boot and recovery and then run B125 on top of that?
Or MUST JB use its own boot and recovery and KK its own boot and recovery?
Thank you,
Falci
Click to expand...
Click to collapse
Yes, this is true : " Or MUST JB use its own boot and recovery and KK its own boot and recovery"
Awsome work. Flashed and works like a charm again (as we're used to with all yr works). Looking forward to use 2.7.0.0 to flash yr future OMNI rom updates or possibly CM11 full release.
Cheers!
Good News !
Hello !
Slow development on our device, but what is essential that is not stopped ...
While I managed to solve all issues related to build TWRP from source ( now resulting recovery.img from build can be flashed without any modificattion ) , I'll start to push my source code to omnirom github - in this way TWRP will be officially and it could be installed directly from GooManager !
So, this point was achieved !
If you wonder how it was possible
> first , to use all features of this TWRP, we will need to perform a few small changes :
1° 100% compatibility with custom rom based AOSP , unsure whether they will be ( CM, AOKP, Carbon, Pac-MAN, OmniROM & .... )
2° on custom rom based stock Huawei Firmware, Internal Storage will not be available ( other functions will be not affected ) - so rom developers need to make some changes on ramdisk from their boot.img - in order to bring full access to Internal Storage on TWRP !
If I'll have some free time, tomorrow I'll start to push source code also on omnirom github !
For moment only TWRP will be officially, following later to do the same thing with OmniROM !
Best Regards !
Hi!
A final test, will be out here soon !
Will be exactly like the official version, or downloadble from GooManager when will be available for our device !
This version, will make some change in our device regarding Internal Storage !
After flashing this version ( fastboot flash recovery openrecovery-twrp.img ) on your device , you also need to flash an update.zip for custom rom based Huawei Stock Firmware KitKat, and currently also for OmniROM - in order to bring full access for Internal Storage on TWRP !
Downloads :
* custom TWRP 2.7.0.0 recovery : openrecovery-twrp-2700.img
* update_sdcard_stock.zip
* fixed : new update update_sdcard_aosp.zip
Installation :
* install TWRP : fastboot flash recovery openrecovery-twrp-2700.img
* if you use stock Huawei KitKat B506 or other custom rom based on this firmware , please flash update_sdcard_stock.zip on your TWRP !
* if you use the last update OmniROM , please flash update_sdcard_aosp.zip on your TWRP !
Please, after test ( install ) let me know how it work on your device ( if you have issue with Internal Storage on your recovery TWRP or in your ROM ) !
Please report if it's OK in stock Huawei B506 , cause should be work fine ! ( report after flashed the new TWRP from here and also after flashed update_sdcard_stock.zip )
Thank you very much for your confirmation, in this way you help me to get it official !!!
Info:
After flashing this new TWRP, your old internal sdcard path will not be removed, so you can still navigate to : /data/share/0 to see all your files on internal sdcard !
The new path for internal sdcard is now /data/media/0 , so if you want to keep this new twrp , you must manually copy and remove all files from /data/share/0 to /data/media/0 !
Edit :
Final source code for building TWRP from source , pushed on my github ! OP also updated !
Best Regards !
i'm on omni and i get bootloop after install this ( last update ) !
any help surdu ? Tnx for your hard work on this phone !
amin-DESIRE-c said:
i'm on omni and i get bootloop after install this ( last update ) !
any help surdu ? Tnx for your hard work on this phone !
Click to expand...
Click to collapse
Do you already do it like this :
> adb reboot bootloader
> fastboot flash recovery openrecovery-twrp-2700.img
> fastboot reboot
Sure, now your device will not boot ( you will be on bootloop ) , but you must go on :
> adb reboot recovery
> and flash here update_sdcard_aosp.zip !
Now your device will boot fine !
Thanks !
I tried it, I only get External USB working on Ubuntu.
On Windows, they Internal and External mount doesn't work for me.
In device manager (windows), when I mount the USB, there is no new device that is shown.
I flashed the update_aosp.zip for the OMNI ROM, still same issue.
Am I doing something wrong?
Also, getting a bootloop.
bokchoi2020 said:
I tried it, I only get External USB working on Ubuntu.
On Windows, they Internal and External mount doesn't work for me.
In device manager (windows), when I mount the USB, there is no new device that is shown.
I flashed the update_aosp.zip for the OMNI ROM, still same issue.
Am I doing something wrong?
Also, getting a bootloop.
Click to expand...
Click to collapse
Thank you for testing !
Maybe I was not clear, please let me doing some tests with stock firmware !
Thanks !
Edit :
I think we need to wipe all on the new twrp ( apart external storage ) , than upplay update_sdcard_stock/aosp.zip in the new twrp !
I'll make more tests and I'll confirm later !
OK !...was my fault , is boot.img issue under update_sdcard_aosp.zip ( update_sdcard_stock.zip it's ok - checked right now - but wasn't tested yet ) ! I'll reupload very soon new update_sdcard_aosp.zip ! Thanks !
Ok, right now fixed and also tested : Just wipe cache & dalvikl after flash the new update_sdcard_aosp.zip !
Tested right now, ( I'm on OmniROM ) - the new openrecovery-twrp-2700.img with the new update_sdcard_aosp.zip and work very well ! I can see on Win 7 the both storage when I connect my USB cable via MTP ! Also I can see on Win 7 my external sdcard on recovery mode by checking : Mount -> Mount USB Storage
This time I had no bootloop, so thats fine. But still doesn't see the USB.
I had to go to Device Manage > USB Serial Bus controllers > USB Mass Storage Device --> Right Click, Update driver --> Then now I have external USB storage, still no Internal USB storage on TWRP.
Is necessary to update the TWRP 2.6.3.7 to this version?
thanks
On Stock B509 works perfectly no issues at all!
But why you changed the place of the internal storage? And when I now flash OMNI for example must I flash the aosp fix afterwards or is it than already done?
EDIT: You must flash the update_sdcard_aosp.zip otherwise you will have a bootloop
taaeem said:
On Stock B509 works perfectly no issues at all!
But why you changed the place of the internal storage? And when I now flash OMNI for example must I flash the aosp fix afterwards or is it than already done?
EDIT: You must flash the update_sdcard_aosp.zip otherwise you will have a bootloop
Click to expand...
Click to collapse
Huawei has a custom path for Internal Storage ! Almost all device has Internal Storage on /data/media or in a separate partition like : /dev/block/../sdcard !
Huawei Ascend P6 keep Internal Storage to /data/share and also we have no partition for mount Internal Storage ( so there is no /dev/block/../sdcard ) !
For bring officialy TWRP in our device , we need to change Internal Storage path from /data/share to /data/media , why ? - because TWRP is made for most devices that support Internal Storage to data/media !
I have installed it and it works great no bootloops no problems. Runing on stock B506
Related
{
"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 Motorola Moto G. 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.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.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-titan.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_titan_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file 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 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.
2. Ubuntu Touch - Not available yet
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.
3. Firefox OS - Not available yet
Firefox OS is just another Android ROM from MultiROM's point of view, so grab the ZIP file from Firefox OS' thread and add it as if it were Android
4. SailfishOS - Not available yet
Download CyanogenMod and SailfishOS ZIP as described on Sailfish wiki page. You need alpha2 (20140810) or newer!
Put both CM and SailfishZIP on your device.
Reboot into recovery
Advanced -> MultiROM -> Add ROM
Choose "SailfishOS" as ROM type. Installation to USB drive is not supported, so leave install location as is. Click Next.
Choose first CyanogenMod ZIP and then SailfishOS ZIP. Click install.
Head to SailfishOS thread for more info: http://forum.xda-developers.com/google-nexus-5/development/rom-sailfish-os-alpha-t2841266
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.
Changelog
Code:
MultiROM v32
=====================
* Minor GUI improvements
* Support for device encryption (with Android-based secondary ROMs only). See
FAQ in this device's XDA thread for more info.
* Bunch of ROM compatibility fixes
MultiROM v31
=====================
* Add support for "multimount" fstab (fixes CM12)
* Support interlaced PNGs (fixes wrongly rendered icons in boot manager, e.g.
the L icon)
MultiROM v30
=====================
* Fix logs generated by the "emergency reboot" screen, they were incomplete
MultiROM v29
=====================
* Implement "autoboot if no key pressed" mode - the boot manager won't show up
unless you hold down a volume down button during boot. Must be enabled in
recovery.
* Android 5.0 preview related tweaks
MultiROM v28
=====================
* You can now swipe between the tabs in the boot manager
* Minor UI adjustments
MultiROM v27a
=====================
* Fix freezes in the boot manager
* Add support for SailfishOS
MultiROM v27
=====================
* Redesign the boot manager GUI. Looks much better now.
* Fix separate radio.img not working on Android L preview ROMs
* Fix issues with unaccessible /sdcard on Android L preview. Do NOT run
restorecon manually on /data/media, ever - it breaks MultiROM!
* Workaround bug which caused franco.Kernel on N5 to break secondary ROM's
boot
* Update Ubuntu Touch init scripts
* Use power+volume down (you have to press power first!) to save screenshots.
They are now PNG images and are saved to /sdcard/Pictures/Screenshots/.
MultiROM v26
=====================
* Fix boot into secondary ROM from the MultiROM Manager app broken in v25
MultiROM v25
=====================
* Add support for the Android L preview
MultiROM v24
=====================
* Add F2FS support
* Show icons in ROM list, configurable via MultiROM Manager app
* Improve compatibility with different ROMs and kernels when booting a ROM
from the Android app
MultiROM v23
=====================
* Fix compatibility with Ubuntu Touch rev 290 and higher. If your Ubuntu
installation won't boot, go to recovery and use "Re-patch init" option in
Advanced -> MultiROM -> List ROMs -> *ubuntu*.
MultiROM v22c
=====================
* Fix graphics corruption with some custom kernels
MultiROM v22b
=====================
* Mount the real /data partition to folder /android/realdata in Ubuntu Touch,
enabling sharing data between Android and Ubuntu Touch. See
[url]http://bit.ly/ut_sharing[/url] for more info.
MultiROM v22a
=====================
* Add support for ROMs with DTB only as separate blob in boot.img (AOKP)
MultiROM v22
=====================
* Fix Ubuntu Touch boot taking long time
* Fix Ubuntu Touch freezing on Google logo for some users
MultiROM v21a
=====================
* Add support for testing builds of Ubuntu Touch (see XDA thread, post #323)
MultiROM v21
=====================
* Revert "mount /system in secondary ROMs read-only" - if done so, SuperSU
breaks the boot.
MultiROM v20
=====================
* Support booting ROMs directly from Manager App
* Fix FCs on CyanogenMod-based ROMs
* Fix support for USB drives formatted with NTFS, broken in v17
* Mount /system in secondary ROMs read-only
MultiROM v19
=====================
* Initial version
Recoveries:
Code:
28.3.2015
=====================
* Update to TWRP 2.8.6
* Added "restorecon" option to secondary ROMs (in MultiROM -> List ROMs),
should be used to fix broken SELinux contexts, which can be causing
bootloops of secondary ROMs
* Bunch of ROM compatibility fixes - recovery now uses entirely new way to
inject ZIP installation files, which should be much more robust and reliable
* Big ZIPs (> 450MB) are no longer permanently modified when flashed as
secondary ROMs
* Fix sideloading of big ZIP files (> 450MB) into secondary ROMs
12.2.2015
=====================
* Update to TWRP 2.8.5
* Fix support for ROMs containing a supersu.zip in their installation file
(e.g. AICP)
15.11.2014
=====================
* Support for ZIP files which are using the new 'block_image_update' command
(e.g. SimpleAOSP ROM)
29.10.2014
=====================
* Update to TWRP 2.8.1
21.10.2014
=====================
* Update autoboot settings for MultiROM v29
14.9.2014
=====================
* Update with changes from 2.8.0.1 upstream version: fix a bug that causes
weird graphics glitches and touch issues
11.9.2014
=====================
* Update to TWRP 2.8.0
* Fix adding ROMs from backup to a FAT32 USB drives
* Remove "share kernel with internal?" from "Add ROM" page, there is usually
no reason to use it anymore and it might be confusing to figure out what it
actually does. You can still get the same behavior by clicking "Remove
boot.img" on the List ROMs -> *rom name* page.
12.8.2014 - 1
=====================
* Fix 'Flash ZIP' function for Android ROMs, broken by a typo in previous
version
11.8.2014
=====================
* Remove Ubuntu Touch installation, installing via recovery is deprecated
* Add SailfishOS installation
8.8.2014
=====================
* Show secondary ROM's name in the title bar while executing it's script (e.g.
during OTA update)
* Update Ubuntu Touch updater
* Fix failure to swap ROMs if it contains filenames starting with a dot
* Fix add ROM from a backup producing unbootable ROM with Android L preview
* Add option to remove radio.img from secondary ROMs
* Add config options for MultiROM v27
5.6.2014
=====================
* Update to TWRP 2.7.1
* Hide misleading "Mount: Unable to find partition for path '/data'" message
which appeared during secondary ROM installation, it is not _actually_ an
error.
4.6.2014
=====================
* Fix installation of bigger (>350MB) ZIPs as secondary ROMs
12.5.2014
=====================
* Fix crash during settings loading, causing a bootloop with certain settings
11.5.2014
=====================
* Add F2FS support
* Add tool to switch F2FS<->ext4 to Advanced menu
* Fix problems with backups introduced by TWRP 2.7.0
8.3.2014
=====================
* Update to TWRP 2.7.0
* Remove "save" button from MultiROM settings page, it is saved automatically
now
27.2.2014
=====================
* Support for system-image based (from the Manager app) Ubuntu Touch
installation
* Fix time in recovery
* Some rendering optimizations, resulting in noticeably higher FPS in recovery
4.2.2014
=====================
* Update to support latest Ubuntu Touch testing builds
* Fix date and time in recovery
* Add support for mice connected via USB-OTG
* Fixup scrollbar behaviour in file list
26.1.2014
=====================
* Fix radio in Ubuntu Touch
24.12.2013
=====================
* Fix installing ROMs to USB drive
* Fix ZIP verification
* Support ZIP verification for secondary ROMs
Credits :
@Brawn_Sg for multirom falcon port
@Picohackr hackr for the recovery
@tassadar for the entire multirom
@h2o64 for the OP
@luca020400 for helping me with TWRP
DOWNLOADS
Tested Configuration:
Primary Rom: PAC-5.0
Sec. Rom: CM12
Sec. Rom: CM11
Donations (Tasssadar)
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
Thanks to all donors, it is much appreciated
XDA:DevDB Information
Multirom v32 Titan, ROM for the Moto G 2014
Contributors
LuK1337, luca020400
Source Code: https://github.com/multirom-titan
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Abandoned
Created 2015-03-03
Last Updated 2016-02-14
Reserved
DOWNLOAD
Bugs:
Sdcard may not work in secondary roms: fix
Your sdcard or USB storage partition must be formatted as EXT4 if you want to store roms on it.
Stock based roms are not supported.
Changelog:
2015-07-06
- Updated MultiROM to the latest source (2.8.7.0)
2015-06-19
- Added support for software encrypted /data (TWRP)
2015-03-30
- Source updated to v32
2015-03-30
- Multirom TWRP now uses LP kernel
2015-03-27
- Updated MultiROM to the latest source (2.8.6.0)
2015-03-15
- Fixed volume keys in boot menu
2015-03-14
- Added sdcard (EXT4) support
2015-03-02
- Initial release
MultiROM:
MultiROM v32
MultiROM TWRP:
MultiROM TWRP 2.8.6.0
KEXEC PATCHED KERNEL:
CM12.1
CM12: LP KK
CM11
Stock 5.0.2
MISC:
UNINSTALLER
It doesn't work for me
But it does for Luk xd
Good flash to anyone hahaha
THIS IS IT.....tnks, surely gonna give my full to try right now
Edit: PAC 5 as primary?? Link pls or suggest which one should be primary??
deeplyyoung said:
THIS IS IT.....tnks, surely gonna give my full to try right now
Edit: PAC 5 as primary?? Link pls or suggest which one should be primary??
Click to expand...
Click to collapse
Yes, I tested it with PAC which is based on CM12 so I didn't waste my time to flash CM12.
You can use every CM12 based rom (PAC, CM12, etc.)
LuK1337 said:
Yes, I tested it with PAC which is based on CM12 so I didn't waste my time to flash CM12.
You can use every CM12 based rom (PAC, CM12, etc.)
Click to expand...
Click to collapse
Except roms with supersu ( like aicp and blisspop ) as primary
Can I use cm11 as primary ROM? Please patch a cm11 kernel, so that I can test it..
ishubhamsingh said:
Can I use cm11 as primary ROM? Please patch a cm11 kernel, so that I can test it..
Click to expand...
Click to collapse
I'll build patched CM11 kernel later.
the best roms can not be primary
Awesome stuff multiboot finally, no more wiping nice setups
Thanks Luk
Sent from my XT1068
Wow....Just tried it....Works great....All I can say is hats of to you Luk
No blisspop as primary
Yuppies
Sent From My XT1068{LP} Using TapatalK
Multibooting cm12 and cm11 possible?
Does multirom doesn't work for other guys ?
Or I'm the only one ...
luca020400 said:
Does multirom doesn't work for other guys ?
Or I'm the only one ...
Click to expand...
Click to collapse
Working perfectly here.
pINKman cm12 and pINKman cm11 are compatible too. So kexec patch implemention is working
slukk said:
Working perfectly here.
pINKman cm12 and pINKman cm11 are compatible too. So kexec patch implemention is working
Click to expand...
Click to collapse
I said it wasn't working becuase in my device multirom doesn't work
I got it working before ( at the 1st attempt )
But my device ****ed it up ...
That's why I haven't released it ...
Any kernel with kexec hardboot should work fine right?
And can I keep cm12 as primary and add any stock based kk Rom to secondary Roms?
Vidhanth said:
Any kernel with kexec hardboot should work fine right?
And can I keep cm12 as primary and add any stock based kk Rom to secondary Roms?
Click to expand...
Click to collapse
Cm12 as primary with patched boot.IMG and till now you can't use stock ROM
Sent from my XT1033{LP} using TAPATALK
deeplyyoung said:
Cm12 as primary with patched boot.IMG and till now you can't use stock ROM
Sent from my XT1033{LP} using TAPATALK
Click to expand...
Click to collapse
Cm12 as primary with boot.img from OP
And cm11? Is that perfect? How do we switch booting roms?
{
"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 Nexus 7, But Ported over to the LG G3 (D851), It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.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, daily prebuilt image files to install Ubuntu Touch 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
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
* Boot from USB drive attached via OTG cable
-=[ Watch Video To See It In Action ]=-
I am not responsible in any way for anything that happens to your device in the process of flashing.
Please familiarize yourself with flashing and custom rom use before attempting to flash the MultiRom & its parts.
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. 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. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are choosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation. The LG G3 (D851) Isn't compatible with this app yet.
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.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
Note 2: There have been reports that (not only) MultiROM does not work properly with older bootloaders. Update it to version 4.13 or newer in case you have problems.
MultiROM has 3 parts you need to install:
MultiROM (multirom_vXX_D851-signed.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_D851_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file 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 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.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed 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.
-- Under Construction at this time
Source code:
MultiRom: https://github.com/Tasssadar/multirom (Branch Master)
Modified TWRP: https://github.com/Tasssadar/Team-Win-Recovery-Project (Branch Master)
Stock kernel w/ kexec-hardboot patch: Not Ready (Use Released ones)
CM kernel w/ kexec-hardboot patch: CM-HardBoot Kexce patched Kernel (Branch test-2)
Device Tree: https://github.com/Eliminater74/multirom_android_device_lge_d851.git (Branch multiromkk)
HardBoot Kexec Kernel Patch: D851-CM_hardboot_kexec_kernel.patch
777Kernel By @777jon: 777Kernel NOT PATCHED
TootsiePop By @aclegg2011: TootsiePop NOT PATCHED
Note: Patch works on Stock as well. Just make sure you edit kernel config by hand. if used on stock.
Good IRC Clients: HexChat or Mirc
IRC Server:irc.freenode.net or chat.freenode.net
IRC Channels:#ubuntu-touch #multirom #twrp #android-root #android-dev #android #ubuntu #ubuntu+1 #ubuntu-devel #ubuntu-gnome #ubuntu-kernel #ubuntu-motu #ubuntu-offtopic #ubuntu-packag
IRC Server:irc.lightning.net
IRC Channels:#c-64 #warez+
XDA:DevDB Information
MultiRom Resurrected (D851) [Updated: 03/30/2015], ROM for the T-Mobile LG G3
Contributors
Eliminater74, Tasssadar
Source Code: https://github.com/Tasssadar/multirom
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: Android 4.4.X +
Based On: AOSP
Version Information
Status: Stable
Created 2015-03-31
Last Updated 2015-04-06
Please Try and let me know:
- MultiRom Installer: multirom-20150717-v32-unofficial-d851-zip
- MultiRom Installer: Mirror: multirom-20150717-v32-UNOFFICIAL-d851.zip
- TWRP Modified 2.8.6.X: twrp_multirom_2-8-7-x_d851_20150717-signed-zip
- TWRP Modified 2.8.6.X: Mirror: TWRP_MultiRom_2.8.7.x_D851_20150717-signed.zip
- MultiRom UnInstaller: multirom_uninstaller-zip-4f423237-22f2-4fe4-9509-9e52cb3dc3e6
- MultiRom UnInstaller: Mirror: multirom_uninstaller.zip
- Patched Kernel: LP kernel_hardboot_kexec_patch_20150403-signed.zip [Updated To Work Right]
-=[ Patched External HardBoot Kexec Kernels ]=-
-=[ Compiled By Eliminater74, w/permission By Respected Owners ]=-
- Updated 777Kernel: 777Kernel_Hardboot_Kexec_20150515-signed.zip [SaberMod 6.0] [LP 5.1.1]
- TootsiePop - - By @aclegg2011 : LP TootsiePop_HardBoot_Kexec_20150408-signed.zip [LP 5.0.2]
- 777Kernel - - By @777jon : LP 777Kernel_HardBoot_Kexec_20150408-signed.zip [LP 5.0.2 ]
-=[External Patched Kernels ]=-
- Patched Kernel: [AOSP][D851]Rin Kernel 1.6.5[LOLLIPOP 5.0.2 ]
- MultiRom Dev Test:
- MultiRom Dev Test:
--=[ D851 Flashable BootLoaders ]=--
- D851_BootLoader_10c.zip -
- D851_BootLoader_10m.zip -
- D851_BootLoader_10r.zip -
- D851_BootLoader_20b.zip -
Tips & Hints
Code:
MultiROM v32
=====================
* Minor GUI improvements
* Support for device encryption (with Android-based secondary ROMs only). See
FAQ in this device's XDA thread for more info.
* Bunch of ROM compatibility fixes
MultiROM v31
=====================
* Add support for "multimount" fstab (fixes CM12)
* Support interlaced PNGs (fixes wrongly rendered icons in boot manager, e.g.
the L icon)
MultiROM v30
=====================
* Fix logs generated by the "emergency reboot" screen, they were incomplete
MultiROM v29
=====================
* Implement "autoboot if no key pressed" mode - the boot manager won't show up
unless you hold down a volume down button during boot. Must be enabled in
recovery.
* Android 5.0 preview related tweaks
MultiROM v28
=====================
* Fix freezes in the boot manager
* You can now swipe between the tabs in the boot manager
* Minor UI adjustments
* SailfishOS support (for certain devices)
MultiROM v27
=====================
* Redesign the boot manager GUI. Looks much better now.
* Fix separate radio.img not working on Android L preview ROMs
* Fix issues with unaccessible /sdcard on Android L preview. Do NOT run
restorecon manually on /data/media, ever - it breaks MultiROM!
* Workaround bug which caused franco.Kernel on N5 to break secondary ROM's
boot
* Update Ubuntu Touch init scripts
* Use power+volume down (you have to press power first!) to save screenshots.
They are now PNG images and are saved to /sdcard/Pictures/Screenshots/.
MultiROM v26
=====================
* Fix boot into secondary ROM from the MultiROM Manager app broken in v25
MultiROM v25
=====================
* Add support for the Android L preview
* Misc F2FS fixes
MultiROM v24
=====================
* Add F2FS support
* Show icons in ROM list, configurable via MultiROM Manager app
* Improve compatibility with different ROMs and kernels when booting a ROM
from the Android app
MultiROM v23
=====================
* Fix compatibility with Ubuntu Touch rev 290 and higher. If your Ubuntu
installation won't boot, go to recovery and use "Re-patch init" option in
Advanced -> MultiROM -> List ROMs -> *ubuntu*.
MultiROM v22b
=====================
* Mount the real /data partition to folder /android/realdata in Ubuntu Touch,
enabling sharing data between Android and Ubuntu Touch. See
http://bit.ly/ut_sharing for more info.
MultiROM v22a
=====================
* Fix hardware keys not working for some users
* Update Ubuntu Touch patches
MultiROM v22
=====================
* Fix linux-type ROMs (Ubuntu Touch) failing to boot for some users
MultiROM v21
=====================
* Revert "mount /system in secondary ROMs read-only" - if done so, SuperSU
breaks the boot.
MultiROM v20
=====================
* Support booting ROMs directly from Manager App
* Fix FCs on CyanogenMod-based ROMs
* Fix support for USB drives formatted with NTFS, broken in v17
* Mount /system in secondary ROMs read-only
MultiROM v19
=====================
* Implement "boot the last ROM" auto-boot type
MultiROM v18
=====================
* Fix silent-but-unpleasant crash with exFAT
MultiROM v17
=====================
* Changes to support MultiROM Manager app
* Add support for exFAT
MultiROM v16a
=====================
* Fix kexec not working on some kernels
MultiROM v16
=====================
* Add overscroll bounceback effect to rom list
* Add support for controling via physical keys
* Bunch of under-the-hood changes for mako and m7 support
MultiROM v15
=====================
* Fix cmdline handling for kexec, doesn't change anything for grouper, just to
have the same version for both flo and grouper (no need to update)
MultiROM v14
=====================
* Find and change correct fstab (fixes freezes on boot)
* Mount /realdata without nosuid (fixes no root on 4.1 and 4.2 ROMs)
* Use libbootimg to work with boot.img files
MultiROM v13
=====================
* Partial rewrite of the codebase to make it compatible with multiple devices
* Add run-on-boot scripts (for advanced users who know linux and bash, see
https://github.com/Tasssadar/multiro...n-boot-scripts)
* Use libbootimg to work with boot.img files
MultiROM v12a
=====================
* Detect kexec-hardboot patch in kernel even if /proc/config.gz is not
available
MultiROM v12
=====================
* Implement screen rotation and 1280x800 theme
* Fix auto-boot option
* Fix listview's fast scrollbar behavior
MultiROM v11
=====================
* Option to hide Internal ROM
* Option to rename Internal ROM
* Support for Ubuntu Touch
MultiROM v10
=====================
* Non-error message boxes aren't red now
* Add possibility to switch between several color themes, go to misc tab and
try it out
* New MultiROM installer format
* Add "discard" option to /data mounting
* Add battery status to misc tab (bottom right corner)
* Add brightness setting
* Implement ADB
MultiROM v9
=====================
* Make it compatible with LZ4 ramdisk compression
* Improve touch-related code. You should not get anymore phantom button
presses nor listview freezes
MultiROM v8
=====================
* Fix kexec-hardboot with new bootloader v4.18
* Search for already present USB drives on start
* Centre "MultiROM" title in main UI
MultiROM v7
=====================
* Correctly boot Ubuntu after recent kernel update. Read this post:
http://forum.xda-developers.com/show...postcount=1031
* Remove specific support for Ubuntu - it is now handled as "generic linux"
(with rom_info.txt file). Nothing should change for the users
* Sort ROMs alphabetically
* Add "progress dots" to USB screen, so that user knows that it is doing
something
* Recovery was also updated, don't forget to flash it
MultiROM v6
=====================
* Properly check for kexec-hardboot patch in kernel
* Internal" is always first in ROM list now, as originally intended
* Much more logging for kexec-related stuff
* Print last 50 lines of klog to "Emergency reboot" screen
MultiROM v5-2
=====================
* Fix ubuntu
* MultiROM still says it's v5. I did not change the version number because it
is literally one character fix.
MultiROM v5
=====================
* Support for ROMs with configuration file. This makes porting
Ubuntu/plasma/webos/anything much more easier. See the third post.
* MultiROM will no longer let you boot Ubuntu ROM if it's name contains
spaces, because the boot would fail.
MultiROM v4
=====================
* Fix GPS on ROMs other than Internal
* Minor UI changes
MultiROM v3
=====================
* Switch to Ubuntu 13.04. Version 12.10 is no longer supported
* Switch to kexec-hardboot based multi-booting. Read the first post.
* Add support for booting from USB drive
* MediaScanner no longer scans /sdcard/multirom, which means no useless
battery drain
* Recovery was updated, make sure to flash it, too.
MultiROM v2
=====================
* Add support for Ubuntu on 3G version of Nexus 7
* Fix some issues with 4.2 ROMs
* Recovery was updated, make sure to flash it, too.
MultiROM v1
=====================
* Initial version
Code:
28.3.2015
=====================
* Update to TWRP 2.8.6
* Added "restorecon" option to secondary ROMs (in MultiROM -> List ROMs),
should be used to fix broken SELinux contexts, which can be causing
bootloops of secondary ROMs
* Bunch of ROM compatibility fixes - recovery now uses entirely new way to
inject ZIP installation files, which should be much more robust and reliable
* Big ZIPs (> 450MB) are no longer permanently modified when flashed as
secondary ROMs
* Fix sideloading of big ZIP files (> 450MB) into secondary ROMs
12.2.2015
=====================
* Update to TWRP 2.8.5
* Fix support for ROMs containing a supersu.zip in their installation file
(e.g. AICP)
15.1.2015
=====================
* Fix "Swap ROMs" feature after the last update
14.1.2015
=====================
* Update to TWRP 2.8.4
* Lots of ZIP compatibility fixes (e.g. for CM 12)
15.11.2014
=====================
* Support for ZIP files which are using the new 'block_image_update' command
(e.g. SimpleAOSP ROM)
29.10.2014
=====================
* Update to TWRP 2.8.1
21.10.2014
=====================
* Update autoboot settings for MultiROM v29
14.9.2014
=====================
* Update with changes from 2.8.0.1 upstream version: fix a bug that causes
weird graphics glitches and touch issues
11.9.2014
=====================
* Update to TWRP 2.8.0
* Fix adding ROMs from backup to a FAT32 USB drives
* Remove "share kernel with internal?" from "Add ROM" page, there is usually
no reason to use it anymore and it might be confusing to figure out what it
actually does. You can still get the same behavior by clicking "Remove
boot.img" on the List ROMs -> *rom name* page.
21.8.2014
=====================
* Remove Ubuntu Touch installation, installing via recovery is deprecated
* Add SailfishOS installation (only for supported devices)
8.8.2014
=====================
* Show secondary ROM's name in the title bar while executing it's script (e.g.
during OTA update)
* Update Ubuntu Touch updater
* Fix failure to swap ROMs if it contains filenames starting with a dot
* Fix add ROM from a backup producing unbootable ROM with Android L preview
* Add option to remove radio.img from secondary ROMs
* Add config options for MultiROM v27
5.6.2014
=====================
* Update to TWRP 2.7.1
* Hide misleading "Mount: Unable to find partition for path '/data'" message
which appeared during secondary ROM installation, it is not _actually_ an
error.
* Fix installation of non-Android systems to USB drives
4.6.2014
=====================
* Fix installation of bigger (>350MB) ZIPs as secondary ROMs
28.5.2014
=====================
* Fix installation of Ubuntu Desktop
12.5.2014
=====================
* Fix crash during settings loading, causing a bootloop with certain settings
11.5.2014
=====================
* Add F2FS support
* Add tool to switch F2FS<->ext4 to Advanced menu
* Fix problems with backups introduced by TWRP 2.7.0
8.3.2014
=====================
* Update to TWRP 2.7.0
* Remove "save" button from MultiROM settings page, it is saved automatically
now
* Some rendering optimizations, resulting in noticeably higher FPS in recovery
2.2.2013
=====================
* Fix GPG signature verification of Ubuntu Touch installation files
* Add support for mice connected via USB-OTG
* Fixup scrollbar behaviour in file list
24.12.2013
=====================
* Fix installing ROMs to USB drive
* Fix ZIP verification
* Support ZIP verification for secondary ROMs
15.12.2013
=====================
* Support OTA updates on secondary ROMs (tested with omni)
* Add "Swap ROMs" feature
* Implement "boot the last ROM" auto-boot type
* Many bugfixes
10.11.2013 - 01
=====================
* Fix some mounting issues when using ntfs or exFAT
10.11.2013
=====================
* Add exFAT support
* Support system-image based Ubuntu Touch installation
* Support Ubuntu Touch OTA updates, if Ubuntu is installed
via MultiROM manager app
22.10.2013
=====================
* Fix SuperSU reporting "failed" when flashed to secondary ROM
and completely borking the MultiROM part for any subsequent
uses of "Flash ZIP" or "Backup" option
16.10.2013
=====================
* Automatically inject boot sector with MultiROM
after ZIP installation or ADB sideload. Can be
turned off on "confirm flash" or "ADB sideload"
pages.
12.10.2013
=====================
* Support 'adb sideload' when adding ROMs
* Support rotation while using custom recovery theme
5.10.2013
=====================
* Don't display unsupported systems in "Add ROM" menu
23.9.2013
=====================
* Use libbootimg to work with boot.img files
22.9.2013
=====================
* Fix custom theme support
19.9.2013
=====================
* Partial rewrite of the codebase to make it compatible with multiple devices
* Add option to backup secondary ROMs
* Don't show "Flash ZIP" option for Ubuntu Touch ROM, it is not an Android
13.9.2013
=====================
* Update to TWRP 2.6.3.0
* Fix Ubuntu desktop image decompression
30.8.2013
=====================
* Update to TWRP 2.6.1.0
* Temporarily removed Timur's USB kernel, because it is not
4.3-compatible and I can't find sources
25.8.2013
=====================
* Clean rebuild of the recovery, I probably forgot to do that last time
and it wouldn't boot on some tilapia devices. No function changes.
21.8.2013
=====================
* Fix updater-script incompatibilities for some ROMs (e.g. PAC-Man)
27.7.2013
=====================
* Fix deletion of 4.3 ROMs with new SuperSU version installed
24.7.2013
=====================
* Don't ignore format("/system"); when flashing ZIPs to secondary ROMs,
this should fix updating secondary ROMs, particulary from 4.2 to 4.3
* Some fixes for 4.3 ROMs
* Add "remove boot.img" option to Android ROMs
21.7.2013
=====================
* Fix crash when installing Android ROM with kernel sharing enabled
20.7.2013
=====================
* Add rotation option to MultiROM settings
* Properly handle kernel flashing for Android ROMs:
you can now flash kernel via "Flash ZIP" option in "List ROMs" menu,
Aroma installer should work properly
* Fix ZIP flashing for 3G version of Nexus 7
9.7.2013
=====================
* Update to TWRP 2.6.0.0
* Support for screen rotation, Settings -> Screen
* Support for Ubuntu Touch
* Added options from MultiROM v11 to hide or rename Internal ROM
* MultiROM Settings menu was reorganized
* MultiROM options added to landscape layout
* Recovery now has Timur's USB host kernel
16.4.2013
=====================
* Fix "Add ROM" option not properly installing /data partition from
backup, if the backup is bigger than 1.5gb
* Make names of ROMs created from Android Backup prettier
9.4.2013
=====================
* Update to TWRP 2.5.0.0
4.4.2013
=====================
* Add support for MultiROM installer format
* Add new MultiROM settings (brightness, adb)
12.3.2013
=====================
* Updated to TWRP 2.4.4.0
* Add support for LZ4 & LZMA ramdisk compression
* Add some handy buttons to "flash complete" page,
thanks ikslawlok for suggestion
2.3.2013
=====================
* Fix freeze when selecting ROM in "Add ROM" option
in MultiROM menu
1.3.2013
=====================
* Updated to TWRP 2.4.3.0
27.2.2013
=====================
* Fix recovery kernel, so that you can boot linux ROMs even if
kernel in internal memory has older kexec-hardboot patch
* Enable brightness settings from TWRP
26.2.2013
=====================
* Updated to TWRP 2.4.2.0
* Add fast scrollbar to fileselectors
* Voldown to turn off screen ("sleep" mode)
22.2.2013
=====================
* Fix Ubuntu Touch installation with
combination of 4.2 as Internal ROM
21.2.2013
=====================
* Don't copy the ZIP to RAM while flashing ZIPs bigger
than 450 MB (currently only Ubuntu touch) in "Add ROM"
or "Flash ZIP" options. This prevents crash which would appear
due to low memory, but also means that these ZIP files
will be modified, which makes them unusable outside MultiROM
after flashing.
* Add Ubuntu touch support
2.2.2013
=====================
* Update to TWRP 2.4.1.0
* Don't reset ROMs location in "List ROMs" when going back
from managing ROM to the ROM list
* Fix recovery crash when there is too deep directory structure
in /data, thanks rifraf for debugging this
30.1.2013
=====================
* Update to TWRP 2.4.0.0
* Properly disable flash-kernel during Ubuntu installation.
This is important fix, because without it, Ubuntu
can rewrite your boot.img.
* Add option to wipe /data, /cache and dalvik-cache
of secondary Android ROMs
* Use gnutar binary compiled specifically for tegra 3,
means faster installation of Ubuntu
* Add "pressed" effect to all buttons, so that you know
if you pressed it or not.
* When installing Android ROM from ZIP which does not have
boot.img (armoma installer...), try to use current boot sector
instead of boot.img. The ROM may not boot, so you should always
add boot.img which is compatible to the ZIP file.
* Update to keep up with MultiROM v7
20.12.2012
=====================
* Fix "Add ROM" for backups in internal memory
------------------------------------------
* Update TWRP to 2.3.3.0
* Add option to Add ROM from backups
* Should be able to flash ZIP files for both grouper and tilapia
18.12.2012
=====================
* Update to support MultiROM v3
2.12.2012
=====================
* Fix "flash zip" option for ROMs without whitespace in name. I've
accidentally broke it in previous update, sorry :/
29.11.2012
=====================
* Fix "flash zip" option for ROMs with whitespace in name
25.11.2012
=====================
* Add Ubuntu support for Nexus 7 3G
24.11.2012
=====================
* Initial version
Code:
- 04-02-2015: First patched Kernel LP 5.0.2 (Source Directly from CM Github)
- Please understand That not all of the patched Kernels are OverClock.
- All Compiled External Patched Kernels By Eliminater74 W/Permission, Will Not have the kernel Name in the about box.
- If a kernel isnt listed that you would like patched, Please Leave a msg to OP along with Links.
- OP received permission from all external kernel owners which kernels he used for patching.
- If you are owner, And your kernel is listed without Permission, Leave msg to op to have it removed.
-=[ I find the best way to utilize MultiRom ]=-
- Create a 2nd partition on your External sdcard Formated ext2 (maybe 5 gigs, I use 10gb, But I have a 128gb card)
- Keep your main partition exfat or fat32, exfat is better for sdcards.
- Remember to create the 2nd partition as the last part. First partition is the one that gets automounted.
- Use that ext2 partition as your Secondary external rom install location.
- fat32 is limited and slow, exfat is faster then fat32
- Remember that your Primary rom must have a Hardboot Kexec patched Kernel.
- Your Secondary roms dont need to have that patch.
*** Please Read: ***NOTE: Do to some bug, Do not flash from Internal Memory if your flashing for secondary rom. The bug will always cause it to overwrite primary rom.
So flash from SD Card Always when flashing secondary roms.
-=[ Please Read ]=-
Just to clarify The patched kernel section,
You must have a kexec hardboot Patched Kernel for whatever Android Rom your using,
Example: Stock 4.4.4 Needs a stock based Patched kexec hardboot Kernel
CM 4.4.4 Needs a patched Kernel based off the CM source
You can not have Stock Rom with a patched Kernel from a CM source. and vise versa..
They have to match..
DO to most people running Custom Roms, I was only going to work on CM related kernel patches.
I really didnt think about stock based roms. I hope that maybe someone else could take up that project for me.
Anyone Interested in Porting kexec hardboot
Thats the link for anyone who wants to give that a shot.
Firsttttttt
---------- Post added at 08:38 PM ---------- Previous post was at 08:36 PM ----------
I managed to soft brick my phone twice on Multirom. Than I stupidly somehow made it so the ROMs would ONLY flash from OTG flashdrive and if I pulled it out it would soft brick...
Soooo... Testers? Not I. But thanks brotha
yanowman said:
Firsttttttt
---------- Post added at 08:38 PM ---------- Previous post was at 08:36 PM ----------
I managed to soft brick my phone twice on Multirom. Than I stupidly somehow made it so the ROMs would ONLY flash from OTG flashdrive and if I pulled it out it would soft brick...
Soooo... Testers? Not I. But thanks brotha
Click to expand...
Click to collapse
I dont blame you. After that, I wouldnt wanna try anything either...
People that test this out, Must be able to recover from a softbrick just in case.. I wouldnt want anyone that doesnt know how to Recover from a Softbrick to try this.
NOTE: I am not saying this Will Softbrick your phone, What I am saying is: Be Prepare Just in case of the unthinkable happens.
Will give it a try as soon as I get home and have easy access to a PC for recovery, in case anything would go wrong.
Also, I have the previous MultiROM right know, how would I go installing this?
I loved MultiROM on this device, so glad you're bringing the development back.... And just in time for LG LP
Papote3 said:
Will give it a try as soon as I get home and have easy access to a PC for recovery, in case anything would go wrong.
Also, I have the previous MultiROM right know, how would I go installing this?
I loved MultiROM on this device, so glad you're bringing the development back.... And just in time for LG LP
Click to expand...
Click to collapse
Since your version is most likely the older version, Just zap the uninstaller.zip after your take a nandroid backup.
That way, if something messes up, you can boot to recovery and reinstall your original backup..
Thats the main reason, I wanted to make sure the recovery worked. ( I had my finguers crossed when I flashed that) :fingers-crossed:
I can personally verify That MultiRom Resurrected Works......... I did take the time to Flash Compatible patched Kernel and Recovery then MultiRom..
Booted menu and everything worked.
I do need to fix the res on it. Too small. Its just a tw flag or mr flag in boardconfig.mk under device tree..
Now I did compile a 2nd version with a few fixes and patches that I made.. First compile was 100% @Skin1980's source to his device tree..
2nd one is from my patched device tree.
Update: I found out how to fix the small looking boot screen. Will compile fix and re-up it later.
Fix was: MR_DPI_FONT := 350 # Was set at 219, and since 340 would be for a 4.95" screen.. I figure try out 350.
I'm still using the original MultiROM and still have all the files. Couple of questions...
1. Uninstaller. I can use the one I have now or the one you provide (assuming there's some difference).?
2. Can I still use skin1980's kernel or is it preferable to use Rin?
On a related note, there was a time when if a ROM's kernel would crash when flashing a secondary I would go to 777jon kernel (because it was new and cool). After awhile, though, it no longer worked with ROMs released in the past month. Furnace kernel, too, on a few tests. Only the tootsie-pop kernel works for me.
Was just wondering why 777jon worked in the past with this MultiROM but no longer does. Is it the kernel, this aged multirom, or something in newer ROMs.
Fusion ROM is one secondary using 777jon kernel w/out issue. It's from February. Validus includes that kernel but it doesn't work. With tootsie-pop it's A-OK.
Am I rambling.? Sorry. ?
Sent from my LG-D851 using Tapatalk
marcdw said:
I'm still using the original MultiROM and still have all the files. Couple of questions...
1. Uninstaller. I can use the one I have now or the one you provide (assuming there's some difference).?
2. Can I still use skin1980's kernel or is it preferable to use Rin?
On a related note, there was a time when if a ROM's kernel would crash when flashing a secondary I would go to 777jon kernel (because it was new and cool). After awhile, though, it no longer worked with ROMs released in the past month. Furnace kernel, too, on a few tests. Only the tootsie-pop kernel works for me.
Was just wondering why 777jon worked in the past with this MultiROM but no longer does. Is it the kernel, this aged multirom, or something in newer ROMs.
Fusion ROM is one secondary using 777jon kernel w/out issue. It's from February. Validus includes that kernel but it doesn't work. With tootsie-pop it's A-OK.
Am I rambling.? Sorry.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
You experienced kernel panics because of this:
MR_RD_ADDR
This option might not be needed for your device. It sets address in boot.img to unpack ramdisk into, and most devices can handle MultiROM changes even without this option. But, some devices (Nexus 7 and Nexus 4) will panic on boot when the ramdisk is bigger than expected. As to what value to set, well, it's more about guessing than anything else. Look at default ramdisk address in your boot.img and try to use a bit higher address.
I set it too MR-RD-ADDR 0x2500000
I took the ramdisk address of a common boot.img which came out at 0x2200000 So I made it 0x2500000 Should be just the correct size.. If not. I change again.. its more of a guessing game.
You can use any kernel that has the patch.. So yes. and as to uninstall.. I think they are all pretty much the same.. but better use the one that came with your multirom version.. since skin's version. Multirom has changed alot,
but also the uninstaller I have should clean up the older version as well. its all pretty much touch and go kinda thing.
I was one of the testers of the skin1980's multirom port.
Stopped using it since it was not updated and the roms from the last month or so did not boot as secondary.
Now I installed TWRP 2.8.6.1 and deleted all secondary roms.
So now I should use the un-installer from you and then flash the multirom TWRP and the Multirom file?
EDIT: Secondary roms install but when selected during the boot options, only the primary rom boots in its place
Many thanks sir for the quick response. Always fun having something new to try (and break and fix).
Will check this all out tonight.
Sent from my LG-D851 using Tapatalk
Anybody other than me try this?
I used MultiRom for about a month. I had a ball with about half a dozen Lollipop Roms. I even sent a donation . It was fun but now I need the G3 for work and can't take the risk.
arifqur said:
I was one of the testers of the skin1980's multirom port.
Stopped using it since it was not updated and the roms from the last month or so did not boot as secondary.
Now I installed TWRP 2.8.6.1 and deleted all secondary roms.
So now I should use the un-installer from you and then flash the multirom TWRP and the Multirom file?
EDIT: Secondary roms install but when selected during the boot options, only the primary rom boots in its place
Click to expand...
Click to collapse
Can you tell me where you installed secondary rom to, and what file system if other then internal.. also ill check into this.
Im still working on getting the screen in place.. Dont forget you have to inject the multirom into every secondary install.
you might want to reinstall, and make sure that box is clicked. Im not sure, but that could be the problem why its not booting that rom after you install it.
Ill check into it though.
hmm.. There is a problem with the booting of the secondary roms.. It seems to only boot the internal only.
Im looking into this. I got so much going on right now, ill try and see what the problem is and fix it.
Yea, seems to install just fine, and everything works up to the point it only boots the Primary rom and nothing more.
So, could be one of my settings that I added to the boardconfig.mk for ramsize. Ill delete it and recompile and try again.
I did manage to get the screen size correct at least.. dpi set too 430 corrected that..
ramdisk address Ill remove that setting and recompile.
Ill let you know when I get a fix for this.
Update: Booting works when installed on External Drive. If install on Internal It wont work right. Im looking into that.........
But like I said, it worked for me installing it on my external Drive thats 128gb /fat32 ....
Eliminater74 said:
Can you tell me where you installed secondary rom to, and what file system if other then internal.. also ill check into this.
Im still working on getting the screen in place.. Dont forget you have to inject the multirom into every secondary install.
you might want to reinstall, and make sure that box is clicked. Im not sure, but that could be the problem why its not booting that rom after you install it.
Ill check into it though.
Click to expand...
Click to collapse
Eliminater74 said:
hmm.. There is a problem with the booting of the secondary roms.. It seems to only boot the internal only.
Im looking into this. I got so much going on right now, ill try and see what the problem is and fix it.
Yea, seems to install just fine, and everything works up to the point it only boots the Primary rom and nothing more.
So, could be one of my settings that I added to the boardconfig.mk for ramsize. Ill delete it and recompile and try again.
I did manage to get the screen size correct at least.. dpi set too 430 corrected that..
ramdisk address Ill remove that setting and recompile.
Ill let you know when I get a fix for this.
Update: Booting works when installed on External Drive. If install on Internal It wont work right. Im looking into that.........
But like I said, it worked for me installing it on my external Drive thats 128gb /fat32 ....
Click to expand...
Click to collapse
Thanks for your response.
Yeah installed it to my Internal Storage as you mentioned.
Waiting anxiously for a working Multirom.
Good to know that you got the DPI fixed
arifqur said:
Thanks for your response.
Yeah installed it to my Internal Storage as you mentioned.
Waiting anxiously for a working Multirom.
Good to know that you got the DPI fixed
Click to expand...
Click to collapse
Im trying to get a fully working multirom. I would say this is about 75% working...
I did find out that it only boots the first listed on internal rom and first listed on external rom.
Example:
internal storage: 1rimary rom 2: blisspop 3: Nobody would have 3 on their internal I hope.
External SDCard: 1:RR 2:Blisspop 3:Noname
USB Storage: 1:BlissPop 2:RR 3:something
Here is the example in action now:
you get boot menu, now you choose to boot from USB, and you want to boot RR but it boots blispop since its #1
Now again you get to boot menu and you boot from external SD Card: you choose #2 blispop but it boots #1RR
same thing with internal storage..
Now you get it.
But im running test and checking out pluss im on #multirom on irc freenode.. the creator or multirom is there but away from his computer.
Ill talk to him when he gets back. Creator is Tasssadar..
MultiRom Logs:
MultiROM logs everything into kmsg.
Usually, when some error happens during boot, it will create /sdcard/multirom/error.txt file in which is dmesg exported.
If it does not, you can reboot to recovery and get kmesg from last boot from file /proc/last_kmsg. This only lasts through one reboot. All MultiROM's messages are prefixed with multirom, so you can just grep for that.
There is a chance that MultiROM just crashes (you'll know that when Internal ROM boots instead of the ROM you've selected).
In that case, there is message MultiROM exited with status X in the kmesg. If the X is anything else than 0, it has crashed.
Report this to me along with the rest of the log.
Update: I need people who installed this and tried to boot second rom, to drop to shell
and type: dmesg | grep multirom >multirom.txt
connect phone to computer; type adb shell
then cd sdcard
then type: dmesg | grep multirom >multirom.txt
send me the txt file.. I need to check something out.
MultiRom Resurrected Now Fully Works:
After a 20 min talk with Tassadar, Who is the Creator of Multirom, He helped me fix the problem that was keeping Multirom from
running Correctly. It was pretty much a very simple 1 line fix.
So now, Download the New Fixed Version, and Try it out.
I will upload it after I press Submit on this message.. Download it all, Because I fixed everything..
IRC Conversation With Tassadar:
Code:
<Tassadar> <3>[ 14.922921 / 03-02 17:01:51.359] trampoline: MultiROM exited with status code 256!
<Tassadar> it crashed
<Tassadar> https://github.com/Tasssadar/multirom/blob/master/main.c#L42 somewhere around here
<Elimin8er> what would the status code 256 be ? I am kinda new to this.
<Tassadar> that won't tell you much, it's probably segfault
<Elimin8er> Is this going to be a pain in the ass for me to fix? or am I pretty much screwed
<Tassadar> dunno why it would be crashing there. I'd probably just ran it under debugger, which is indeed not easy to set-up if you don't know what you're doing
<Elimin8er> give me a idea on what debugger and how and im sure I can figure out the rest
<Tassadar> hmm, how exactly did you add support for your device into kexec-tools?
<Elimin8er> https://github.com/Eliminater74/multirom_android_device_lge_d851.git <--- do you mean my device tree
<Elimin8er> I didnt do the patch kernel.. I used a already patched kernel
<Elimin8er> rin kernel
<Elimin8er> I pretty much just stuck to your guide on how to build for my device..
<Elimin8er> I used the multiromkk branch.. the master is just the one I got from skin1980 who ported the first one
<Elimin8er> long ago.
<Tassadar> https://github.com/Tasssadar/kexec-tools/blob/master/kexec/arch/arm/mach-hammerhead.c#L185 try adding "d851" into this list (kexec-tools is a folder in the multirom source directory)
<Elimin8er> Tassadar, ok, Now what exacity did you want me to do?
<Tassadar> like explain what is it doing or what are you supposed to do?
<Elimin8er> you said try adding d851 into some list..
<Tassadar> yeah, add it and rebuild it and try if it still crashes
<Tassadar> into the list I linked there
* nkk71 is now known as nkk71__away
<Elimin8er> Tassadar, you mean here: .boardnames = { "hammerhead", "bacon", NULL }, ?? change that or add to it ?
<Elimin8er> sorry im not a pro at this.. im just learning
<Tassadar> change that line to be ".boardnames = { "hammerhead", "bacon", "d851", NULL },"
<Elimin8er> ok I got it.
<Elimin8er> hmm
<Elimin8er> ok done that.. going to try the recompile now.
<Elimin8er> btw, could java version cause any of tht :???
<Tassadar> no
<Elimin8er> just making sure.. and I am compiling on a ubuntu 15.04 system.. but I also build a few roms with no problems on that machine too
<Elimin8er> I compile CM12 and RR for the samsung galaxy S tab 10.5 on that machine. so I know everything needed is there\
<Elimin8er> im going to go get something eat while its compiling still. afk...
* Santhosh_m90 has quit (Remote host closed the connection)
<Elimin8er> Tassadar, system/extras/multirom/kexec-tools/kexec/arch/arm/mach-hammerhead.c:185:51: error: called object '"d851"' is not a function <---- error un multirom_zip
<Tassadar> show me how does the line look like now
<Elimin8er> .boardnames = { "hammerhead", "bacon", "d851" NULL }, <-- I forgot the ,
<Tassadar> yes
<Elimin8er> ok fixed that...
<Elimin8er> I only fixed it locally, if everything works ok, ill push it to my github and just track changes from your main one
<Tassadar> I'll push it to my github if it works for you
<Elimin8er> ohh ok
<Tassadar> there is one other error there, it shouldn't have crash, just tell you that d851 is not supported
<Elimin8er> the device tree is the same one the skin1980 used on an older version of your multirom and it worked ok. Just alot of kernel panics do to the ramdisk address size thing that I read on your guide.
<Tassadar> it got changed
<Tassadar> for v32
<Elimin8er> ok im sending it over.. btw, could a messed up kernel cause any of that? I used a pretty repital kernel well known.. they create for most all G3's
<CaptainThrowback> wait, there was a ramdisk address size change?
<CaptainThrowback> is that why I haven't been able to get anything booted since the encryption merge?
<Elimin8er> No.. im talking about the mr flag
<CaptainThrowback> maybe Tassadar can help me with my mach-m8.c file some day
<Elimin8er> MR_RD_ADDR := 0x82500000 <--- this flag
<Elimin8er> but I used 0x2600000
<Elimin8er> im installing 2nd rom now.. then ill see what happends
<Elimin8er> Tassadar, I think it that worked.. its loading the 2nd rom now..
<Elimin8er> Tassadar, thank you for your help
<Elimin8er> yep, it worked..
Hello !
{
"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"
}
Permanent TWRP Recovery 3.0.2-0
Huawei - G8 & GX8
Changelog :
Code:
[URL="https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html"]What’s new in 3.0.2-0[/URL]
What’s new in 3.0.1-0:
[LIST]
[*] support new CM 13.0 pattern encryption (sultanqasim)
[*] fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
[*] libtar updated to latest upstream and fixes (jcadduono)
[*] fixes for loading custom themes (_that)
[*] TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
[*] translation updates - added Italian, Czech and Polish and significant updates to Dutch
[*] progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
[*] fix input box text display (Dees_Troy)
[*] reboot option after zip install complete (bigbiff)
[*] other mostly invisible bug fixes and improvements
[/LIST]
What’s new in 3.0.0-0:
[LIST]
[*] Completely new theme - Much more modern and much nicer looking (by z31s1g)
[*] True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
[*] Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
[*] Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
[*] Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
[*] Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
[*] SuperSU prompt will no longer display if a Marshmallow ROM is installed
[*] Update exfat, exfat fuse, dosfstools (by mdmower)
[*] Update AOSP base to 6.0
[*] A huge laundry list of other minor fixes and tweaks
[/LIST]
What’s new in 2.8.7.0:
[LIST]
[*] Initial ground work for software drawn keyboard (_that)
[*] Fix handling of wiping internal storage on datamedia devices (xuefer)
[*] Allow DataManager to set and read values from the system properties (xuefer)
[*] Fix crash when taking screenshots on arm64 devices
[*] Fix error message after an ORS script completes (Dees_Troy)
[*] Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
[*] Add system read only option – more details below (Dees_Troy)
[*] Add resize2fs and GUI option to run resize2fs (Dees_Troy)
[*] Fix crash loop caused by empty lines in AOSP recovery command file (_that)
[*] Prevent duplicate page overlays such as multiple lock screens (mdmower)
[/LIST]
What’s new in 2.8.6.0:
[LIST]
[*] Fix daylight savings time rules for USA and Europe (_that)
[*] Allow mulitple overlays for popup boxes (Dees_Troy)
[*] Add pattern style password entry for decrypt (Tassadar)
[*] Keyboard improvements (_that)
[*] Update AOSP base to 5.1 (Dees_Troy)
[*] Reduce theme count to 5 and rely on scaling (Dees_Troy)
[*] Various scaling improvements (Dees_Troy)
[*] Improved handling of resources in the GUI (_that)
[*] Make scroll bar size proportional to list size (_that)
[*] Allow scoll lists to render without a header (_that)
[*] Make console scroll per pixel with kinetic scrolling (_that)
[*] Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
[*] Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
[/LIST]
What's new in 2.8.1.0 :
[LIST]
[*] MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
[*] TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
[*] Temperature support - thanks to bigbiff
[*] Various other bugfixes and tweaks
[/LIST]
What's new in 2.8.0.0 :
[LIST]
[*] Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
[*] Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
[*] Add support for color in the console and give error, warning, and highlight lines different colors
[*] Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
[*] Improve handling of /misc thanks to mdmower
[*] Improve setting of time on Qualcomm devices thanks to [NUT]
[*] Allow using images on slidervalue GUI objects thanks to Tassadar
[*] Allow using variables and addition and subtraction in variables for easier theming
[*] Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
[*] Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
[*] Other minor fixes and improvements
[/LIST]
What's new in 2.7.1.0 :
[LIST]
[*] Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
[*] Various bugfixes to backup and restore
[*] Improvements to USB storage handling
[*] Added a class to search for files to make finding the correct brightness file automatic in most cases
[*] Various other bugfixes and tweaks
[/LIST]
What's new in 2.7.0.0 :
[LIST]
[*] Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
[*] Allow sideloading from /tmp on encrypted devices
[*] Check for a crypto footer before asking for a password to prevent user confusion
[*] Additional checks for validity to auto generated backup names
[*] Text wrap in the console output
[*] Proper caps lock support in the keyboard
[*] Mouse support via USB OTG for devices with a broken digitizer
[*] Improve scanning of storage locations for OpenRecoveryScript
[*] Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
[*] Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
[*] Update SuperSU to 1.93 and improve installation process
[*] Added selinux contexts restoration to fix permissions
[*] Load RTC offset on Qualcomm devices to fix the date/time in recovery
[*] USB Mass Storage fixes Add SELinux support checking
[*] Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
[*] Add 4.4 AOSP decrypt support
[*] Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
[*] Various SELinux fixes and bug fixes
[/LIST][CENTER][/CENTER]
Downloads :
Code:
[CENTER]
[B][I][COLOR="Blue"]New Update : [/COLOR][/I][/B] For CM-14.1/LOS-14.1 : [URL="http://forum.xda-developers.com/showpost.php?p=70296158&postcount=79"] twrp-recovery-N.img[/URL]
* Update [URL="http://forum.xda-developers.com/showpost.php?p=67179568&postcount=56"]TWRP 3.0.2-0[/URL]
* Update [URL="http://forum.xda-developers.com/showpost.php?p=66171376&postcount=37"]TWRP 3.0.1-0[/URL]
* Update [URL="http://forum.xda-developers.com/showpost.php?p=66002614&postcount=33"]TWRP 3.0.0-0[/URL]
* Update [URL="http://forum.xda-developers.com/showpost.php?p=65817315&postcount=18"]TWRP 3.0.0-0[/URL] !
* [URL="https://www.androidfilehost.com/?fid=24421527759889994"]openrecovery-twrp-3.0.0-0.img[/URL] md5 : 23cb0c91aa3a577e24fb183b23ebf62c
[/CENTER]
Installation :
Code:
[CENTER]
* [FONT="Arial Black"]Your Device Must Have A Unlock Bootloader ![/FONT]
*[FONT="Arial Black"] Image File ( openrecovery-twrp-3.0.0-0.img ) :[/FONT]
[LIST]
[*] boot your device in bootloader mode by :> adb reboot bootloader
[*] flash custom recovery :> fastboot flash recovery openrecovery-twrp-3.0.0-0.img
[*] reboot your device :> fastboot reboot
[/LIST]
[/CENTER]
Boot into TWRP :
Code:
[CENTER]
* > adb reboot recovery
* keep pressing at the same time : power off button and volume up - as soon as your device vibrate , please relase power off button and keep pressing volume up -> your device will enter very soon into TWRP recovery !
[/CENTER]
Source :
Code:
[CENTER]* [URL="https://github.com/TeamWin/Team-Win-Recovery-Project/tree/twrp2.7"]TeamWin GitHub[/URL] !
* TWRP G8 : [URL="https://github.com/Huawei-Dev/TWRP-G8"]GitHub[/URL]
[/CENTER]
Credit :
Code:
[CENTER]* [URL="http://teamw.in/project/twrp2"][B]Team[COLOR="RoyalBlue"]Win[/B][/COLOR][/URL]
* [URL="http://forum.xda-developers.com/showthread.php?t=1943625"]Dees_Troy[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=4878287"]_that[/URL]
[/CENTER]
FAQ :
Code:
[CENTER]
* please perform a Backup with this version of TWRP - after that, you'll be able to restore successfully !
* do not perform a Restore from a Backup performed with other version of TWRP - your device will end with boot loop into TWRP !
[/CENTER]
SHARE :
Code:
[CENTER]
* [B][I]please, if you want to share or your work is basend on my source code - first, you should ask my permission via PM ![/I][/B]
* [B][I]also on your OP, you must provide adequate credit, for my works ![/I][/B]
* [B][I]you are always free to use & improve my works ![/I][/B]
* [B][I]thanks for understanding ![/I][/B]
[/CENTER]
regards,
Surdu Petru
XDA:DevDB Information
TWRP, Tool/Utility for the Huawei GX8
Contributors
surdu_petru
Source Code: https://github.com/Huawei-Dev
Version Information
Status: Stable
Created 2016-02-27
Last Updated 2017-03-24
*** reserved ***
Hi Surdu petru, thanks for your great work. I d like to ask you to post stock recovery from android 6.0 rom. Or can you provide adb commands for extracting it from phone as you provide for extracting boot.img. Thanks.
I had bootloops with TWRP in android 5.0 FW. Couldn´t boot to system with TWRP. Had to flash stock recovery after playing with TWRP to be able to boot normaly.
krispin said:
Hi Surdu petru, thanks for your great work. I d like to ask you to post stock recovery from android 6.0 rom. Or can you provide adb commands for extracting it from phone as you provide for extracting boot.img. Thanks.
I had bootloops with TWRP in android 5.0 FW. Couldn´t boot to system with TWRP. Had to flash stock recovery after playing with TWRP to be able to boot normaly.
Click to expand...
Click to collapse
My device is dual sim, so there is no Android M from Huawei ,( not yet ...) . You should try to flash stock Huawei update.app via stock recovery ... because stock recovery from M will not be available very soon .
Good luck .
surdu_petru said:
My device is dual sim, so there is no Android M from Huawei ,( not yet ...) . You should try to flash stock Huawei update.app via stock recovery ... because stock recovery from M will not be available very soon .
Good luck .
Click to expand...
Click to collapse
I am already on Marshmallow, but wanted to flash twrp and then root, but on lollipop I couldn´t boot to system after flashing twrp. So I dont want to stay stucked in recovery.
I have tried to extract update.app of marshmallow update and I ve got two images: system.img and file23.mbn.img. Size of cecond one is similar to stock recovery. couldn´t it be that recovery? I ll upload it shortly. But found in 4pda forum, thet it could be the right file.
krispin said:
I am already on Marshmallow, but wanted to flash twrp and then root, but on lollipop I couldn´t boot to system after flashing twrp. So I dont want to stay stucked in recovery.
I have tried to extract update.app of marshmallow update and I ve got two images: system.img and file23.mbn.img. Size of cecond one is similar to stock recovery. couldn´t it be that recovery? I ll upload it shortly. But found in 4pda forum, thet it could be the right file.
Click to expand...
Click to collapse
Yep, first upload here and than I'll told you if is the recovery or not. Thanks!
surdu_petru said:
Yep, first upload here and than I'll told you if is the recovery or not. Thanks!
Click to expand...
Click to collapse
Here it is: https://onedrive.live.com/redir?resid=51ABB765045AF487!5772&authkey=!AC-ps4vpEPRcJ6U&ithint=file,img
krispin said:
Here it is: https://onedrive.live.com/redir?resid=51ABB765045AF487!5772&authkey=!AC-ps4vpEPRcJ6U&ithint=file,img
Click to expand...
Click to collapse
Thanks ... is only new boot.img for M and not a recovery !
Do you have also system.img ... or a link for downloads , thanks !
Great work, thanks and keep going.
Source code for TWRP pushed on my git ...
I hope that on this occasion, officially TWRP for G8 - will fix boot loop issue on recovery .
surdu_petru said:
Thanks ... is only new boot.img for M and not a recovery !
Do you have also system.img ... or a link for downloads , thanks !
Click to expand...
Click to collapse
I have it. it is just 61 MB big. Will upload it and post a link. And here is whole update.zip: https://mega.nz/#!aRczQR5J
and system.img:
https://onedrive.live.com/redir?resid=51ABB765045AF487!5774&authkey=!AGwds04zqnLeAcQ&ithint=file,img
So could it be possible, that recovery remained the same, if its not in the update.zip? I have read on htcmania, that they downgraded to B170 android 5.0 just by flashing full package.
PS: It is sad, what happened with your phone.
krispin said:
I have it. it is just 61 MB big. Will upload it and post a link. And here is whole update.zip: https://mega.nz/#!aRczQR5J
and system.img:
https://onedrive.live.com/redir?resid=51ABB765045AF487!5774&authkey=!AGwds04zqnLeAcQ&ithint=file,img
So could it be possible, that recovery remained the same, if its not in the update.zip? I have read on htcmania, that they downgraded to B170 android 5.0 just by flashing full package.
PS: It is sad, what happened with your phone.
Click to expand...
Click to collapse
Theoretically can remain the same recovery from L ... also I was able to boot on cm-13.0 with my TWRP , and my TWRP is builded on cm-12.1 !
I've already sent my device to the repair center .. I hope to have news soon
Hi mate, I ve just took the risk and flashed your recovery and 2.65 SuperSU in android 6.0 beta and everything seems to OK. I am rooted.
krispin said:
Hi mate, I ve just took the risk and flashed your recovery and 2.65 SuperSU in android 6.0 beta and everything seems to OK. I am rooted.
Click to expand...
Click to collapse
Yes, today I received a new device from Huawei , the same model as first device , dual sim HUAWEI RIO-L01 !
Please, can you put the whole system from your device into zip archive and than uploaded on Mega ? , sure from 6.0 beta .
As you are already rooted, will not be very difficult , just do it :
> mkdir systemM
> adb pull system systemM/
- than just zip systemM directory and share for me into Mega , or wherever you want . From Mega I can download very quickly !
Thank you very much !
Should i write both commands throught adb?
Solved, extracting done, starting upload. Please keep in mind, that I have one SIM version of RIO L01.
PS: I am happy, you are back in game.
Here we go: https://mega.nz/#!rI1VAL7A!9aVx1tpHRcIuJZ-B_IEleAjPnxfCYXT6_fgTwcRG_pA
surdu_petru said:
Yes, today I received a new device from Huawei , the same model as first device , dual sim HUAWEI RIO-L01 !
Please, can you put the whole system from your device into zip archive and than uploaded on Mega ? , sure from 6.0 beta .
As you are already rooted, will not be very difficult , just do it :
> mkdir systemM
> adb pull system systemM/
- than just zip systemM directory and share for me into Mega , or wherever you want . From Mega I can download very quickly !
Thank you very much !
Click to expand...
Click to collapse
Huawei RIO-L01 is dual sim ?? I have it and my is singel sim I was thinking that dual sim is RIO-L03
badbar said:
Huawei RIO-L01 is dual sim ?? I have it and my is singel sim I was thinking that dual sim is RIO-L03
Click to expand...
Click to collapse
Yes, my device is Huawei G8 , HUAWEI RIO-L01 , dual sim !
Update TWRP !
Hello !
Here is a new light update for TWRP 3.0.0-0 Huawei G8 & GX8 !
- fixed device assert for CyanogenMod and others CustomROM !
- add battery percentage - unfortunately, sometimes it drop to zero - may be fixed on the next release !
Downloads : TWRP-3.0.0-0_Update01.zip md5 : 5cd83c5270b70f473f6734881b8136d3
Installations : install via twrp , no wipe required !
You should have this update of TWRP in your device , in order to be able to flash the future CyanogenMod 13.0 !
Best regards !
Hi mate, I just want to report, that I am loosing root after every reboot on marshmallow. I dont remember, if I allow system modification in twrp after first start. Is it possibility to check it somehow?
I have the Huawei RIO-L01 (dual sim) with official Marshmallow update via ota, is it safe to flash this?
{
"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:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: joyeuse
Maintainer/Authors build: @Kry9toN
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Kernel: https://github.com/Kry9toN/kernel_xiaomi_sm6250
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Downloads
Flashable zip
https://drive.google.com/uc?id=1XUIrTfSeQ6rgYfvb4_XO6NIIRnWZJOOj&export=download
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the Redmi Note 9 Pro
Contributors
Kry9toN, Reza Adi, Shovon, Manjot Sidhu, Mohd Faraz, Sagar
Version Information
Status: Stable
Current Stable Version: 3.0.0
Created 2020-08-10
Last Updated 2020-08-10
Great, will test it now !
dungphp said:
Great, will test it now !
Click to expand...
Click to collapse
Nice if you found bug please tell me
Kry9toN said:
Nice if you found bug please tell me
Click to expand...
Click to collapse
It work ! Needed unmount system, vendor then flash rom
Why do you need to crosspost here? https://forum.xda-developers.com/redmi-note-9-pro/review/recovery-pitch-black-recovery-t4145151
Thumbs up. Backup seems to work.
@Kry9toN
After installing Island backups only fail as you can read on
https://www.reddit.com/r/Android/comments/chhcm6/psa_twrp_backup_does_not_like_android_for_work/
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1256
Island is similar to Shelter and is used to isolate certain proprietary Apps. I won't delete it. I could send you my PBRP log, if you want to work on the problem. How about it?
heyadmwutanime said:
Why do you need to crosspost here? https://forum.xda-developers.com/redmi-note-9-pro/review/recovery-pitch-black-recovery-t4145151
Thumbs up. Backup seems to work.
Click to expand...
Click to collapse
My miss take for choose form
Hi,
i tried to install this version but failed. Please see my steps belwo:
1) installing recovery.img via "fastboot flash recovery recovery.img" worked fine
2) installing the PitchBlack-joyeuse-2.9.1-20200722-1350-UNOFFICIAL.zip file via twrp returned "ERROR 1"
3) after rebooting into system and then back to PBRP, PBRP was gone and defualt recovery came up
Is there anything i miss?
Try to unmount some partitions and then install/sideload the zip. Try both install (from internal memory) and adb sideload. I also wasn't able to install many zip files through Recovery. Either the custom recoverys aren't ready yet or the zip files aren't made for Android 10 AOSP.
Tried adb sideload as well but it doesnt start on device side. Its just loading or startign endless.
I wantred also to get hands on the logs but once i install magisk, its getting into bootloop. Also the filemanager cannot be installed from PBRP.
Maybe its jjust to early.
Flashing Magisk from recovery will get u to bootloop. Extract ur roms boot.img from rom zip and patch it with Magisk Manager app then flash it with adb in fastboot mode
Hi,
I unlocked the bootloader of my RN9 Pro, rooted by patching the .img file with Magisk, now I would like to install a custom recovery. Does installing PBR format data like Czech TWRP found in neighboring forum? And how to install it with the official Recovery, the latter is not familiar to me, I come from a Mimax2.
Thank you
dungphp said:
It work ! Needed unmount system, vendor then flash rom
Click to expand...
Click to collapse
Thanks! I spent hours trying to figure out why I couldn't flash anything, unmounting vendor fixed it instantly!
2x super with the same size.
A bug?
You can't use adb sideload it glitches and gapps aroma doesn't work
Please help me
I unlocked bootloader, then flash pitch black recovery but once I booted to recovery, I flash miui rom and then my internal data got encrypted. It's not encrypted anymore but I can't flash any custom rom using this recovery.
When I access fastboot mode, adb devices doesn't show any device. I previously flashed twrp for curtana.
I'm still able to access pbr but everytime I try to flash rom, here's the error message:
Updater process ended with ERROR: 7
An Assert failed. Please check the output above for more details.
Error installing zip file 'file-location-info-bla-bla-bla'
Updating partition details...
Failed to mount '/product' (No such file or directory
...done
Please help me solve this
Edit:
I solved it by flashing through fastboot
Guys i want to try it. I will flash it via fastboot. I dont want to lose my data. Am ı need to flash rom after installing pbrp?
Hmm, looks like this does not support dynamic partitions.
I run into an assertion error trying to install the xiaomi.eu 11.0.5 ROM.
cheers
afx
a.f.x. said:
Hmm, looks like this does not support dynamic partitions.
I run into an assertion error trying to install the xiaomi.eu 11.0.5 ROM.
cheers
afx
Click to expand...
Click to collapse
Make sure to unmount /system and/vendor before flashing
crisagler said:
Make sure to unmount /system and/vendor before flashing
Click to expand...
Click to collapse
Not mounted by default anyway...
cheers
afx
{
"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:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.7.0
PitchBlack version: 3.2.0
For device: Redmi Note 8/8T
Maintainer/Authors build: Erwin Abu Bakar Sidik
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: Github
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Changelog
PBRP Side Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR\
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Device Side Changelog
Code:
• Update Blobs
• Update Prebuilt Kernel
• add Support busybox, bash & Nano Editor
• Disable Patching DM-Verity By Default
• Disable Treble Compatibility Check By Default
• Manage a new Willow version
Bugs
- You tell me!
Downloads
Willow
Ginkgo
Project TypeTool/UtilityProject NamePitchBlack Recovery Project
Additional ContributorsReza Adi, Shovon, Manjot Sidhu, Mohd Faraz, SagarProject statusStableStable Version3.2.0
good job
one question to ask ：can i use this to flash android11？
wsdyleon said:
good job
one question to ask ：can i use this to flash android11？
Click to expand...
Click to collapse
Yes
Thanks
I'm stuck on the splash screen sir
Fyahipoh said:
I'm stuck on the splash screen sir
Click to expand...
Click to collapse
work well for me ，using twrp to flash the pbrp.zip
i wana learn how to use the tools
wsdyleon said:
i wana learn how to use the tools
Click to expand...
Click to collapse
install twrp.zip again
wsdyleon said:
i wana learn how to use the tools
Click to expand...
Click to collapse
install twrp.zip again
does it fix, MIUI Global Stable.v12.0.3 encryption/decryption?
thanks..
Erwin Abs said:
install twrp.zip again
Click to expand...
Click to collapse
thanks， appdel tool is wired.maybe on miui？
unable to mount storage when wiping data（when mount usb storage ...）
stuck at pbrp logo after flashing android11
Fyahipoh said:
I'm stuck on the splash screen sir
Click to expand...
Click to collapse
Same here on Willow.
predatorian said:
Same here on Willow.
Click to expand...
Click to collapse
willow use this https://sourceforge.net/projects/pb...kgo-3.0.0-20210126-1128-OFFICIAL.zip/download
wsdyleon said:
thanks， appdel tool is wired.maybe on miui？
unable to mount storage when wiping data（when mount usb storage ...）
stuck at pbrp logo after flashing android11
Click to expand...
Click to collapse
yeah on miui work, grab log
Erwin Abs said:
yeah on miui work, grab log
Click to expand...
Click to collapse
sorry，it stuck ，i donnt know how to take log
another question:i had format all kinds of partions ,which lead to sensor abnormal
find the reason why sensor dead：i format the persist partion for mistake，and to my surprise the full fastboot rom never help
I wanted to flash a new rom, formatted data, rebooted, installed new firmware and rom and then I wanted to try another rom, rebooted back to recovery and now I see this
Formatting again gives me the same errors and whole internal memory is encrypted, nothing helps. Any advice?
numbazZ said:
I wanted to flash a new rom, formatted data, rebooted, installed new firmware and rom and then I wanted to try another rom, rebooted back to recovery and now I see this
Formatting again gives me the same errors and whole internal memory is encrypted, nothing helps. Any advice?
Click to expand...
Click to collapse
i used many recoverys to flash miui12.5 beta，not any rom aceess root perfectly！some recoverys cannot format encrypted data，some boot stuck at recovery logo
wsdyleon said:
another question:i had format all kinds of partions ,which lead to sensor abnormal
find the reason why sensor dead：i format the persist partion for mistake，and to my surprise the full fastboot rom never help
Click to expand...
Click to collapse
why format all? just format data this fine
numbazZ said:
I wanted to flash a new rom, formatted data, rebooted, installed new firmware and rom and then I wanted to try another rom, rebooted back to recovery and now I see this
Formatting again gives me the same errors and whole internal memory is encrypted, nothing helps. Any advice?
Click to expand...
Click to collapse
format data