Hello,
my girlfriend had a S5839i that I rooted and put a custom recovery on (CWM) and to gain some performance I flashed a kernel that was described as being compatible to this specific device, too and after flashing in CWM I got a phone stuck at boot logo. I can't get into recovery mode anymore and now I need to recover data that is not stored on external, but the internal storage. I really need to get into a mode where I can copy data from the storage.
Is there any possibility to do this or does someone even know how to unbrick the device?
Thanks a lot!
Regards,
Nash.
nashsx said:
Hello,
my girlfriend had a S5839i that I rooted and put a custom recovery on (CWM) and to gain some performance I flashed a kernel that was described as being compatible to this specific device, too and after flashing in CWM I got a phone stuck at boot logo. I can't get into recovery mode anymore and now I need to recover data that is not stored on external, but the internal storage. I really need to get into a mode where I can copy data from the storage.
Is there any possibility to do this or does someone even know how to unbrick the device?
Thanks a lot!
Regards,
Nash.
Click to expand...
Click to collapse
Humm,, Please define the version of Temp-CWM you did flash( CooperVe compatible assuming)
Define 'flashed a kernel' please, Your stock firmware already contains a stock kernel, which is quite capable of performing what we are expecting from basic kernel. ( Explains in details how did you install custom kernel or custom Roms etc etc,,)
Always do your Nandroid/EFS/Data back up prior to tinkering though.
IF the only option available to you due to soft bricking is , Downland mode >> upon flashing over Odin your /data partition will be wiped out for successful restoration of your device.
waiting for your through explanation,,,,,,
Hello,
thanks for your reply. Unfortunately I cannot specify the CWM version anymore, but I flashed a custom kernel via the CWM, it was a flashable zip file downloaded somewhere in this forum that I flashed using CWM (which I installed using ODIN, iirc). The reason I cannot say what CWM I installed is, I had a data loss on the hard drive inside my computer where I downloaded the files to. If it's really important to know what kernel it was, then I believe I could reconstruct this by searching the custom kernel section for the specific device in this section, I am sure I will know when I read the name again. While waiting for a new reply I'm gonna do this to find out what kernel I flashed via CWM.
The problem with the last resort suggested by you, ODINand download mode and this stuff, is that the data I need to restore is located in data partition if I am correct. Or maybe I'm wrong? The data is from the android text editor notepad which I found out doesn't store data in /sdcard partitions, neither internal nor external, so if I'm right, this means it's being stored in the application's data directory. Please tell me if I'm wrong with this guess.
.
Regards,
Nash.
@nashsx, I fully understand your concern in regards of sensitive data recovery from internal SD partition. However you need to be more specific with all of the tools and Roms you did use whenever you ask for accurate assistance .
Nevertheless I am going to explain all of the errors and possible symptoms you might encounter during CWM flashing to Kernel procedure .
First , You need to comprehend that for your device's ( known as CooperVe) safety we need to use compatible temporary CWM flash able zip file or CWM comes with kernel . The latter is not recommended though for many reasons I would not engage at the moment ( files could be found here or here for instance,,,OR any official sticky topic )
As for kernel Let me be clear : We do not flash custom kernel on top of stock firmware for s5830i/C/M/5839i devices under any circumstances. This is a correct order >>
Stock Firmware >Custom Rom based on stock kernel > Custom kernel
Alternative : flash Custom Rom comes with custom Kernel , and there are so many wiping and formatting process will be involved in between flashing I would not go into more details .
Basically we are obtaining an exclusive right to use Mods/Scripts/Tweaks : performance , battery ,, etc etc at boot time , by activating our init.d support with the help of custom kernels and much more stuff we can perform after flashing. ( Well established name you requested : Rafael.Baugis ; ThunderKernel ; CyanogenMod 7.2 Specific BASIC Kernel ; Hells Fusion )
Now a little educational standard internal memory partitions one- on-one :
/boot
/system
/recovery
/data
/cache
/misc
SD card partitions :
/sdcard
/sd-ext
/data or User data , is the part in question you are trying to access via recovery , which is not an option anymore sadly.
This is where your contacts, messages, settings and apps that you have installed go. Wiping this partition over Odin with the help of wipe - flash able 3 parts package made by splitfus2 app( and other options ticked : re-partition and pit & boot loader selected ) for example ;essentially performs a factory reset on your device; restoring it to the way it was when you first booted it.
We only have 2 options ( if you can call it an option at all in reality ) for recovery procedure , since you don't have access to either of stock e3 / CWM recovery consoles .
1.Normally During boot loop ADB won't work, but we can give it a try ( ADB debugging option must be ticked inside Developer settings inside your Android OS ; platform-tools is required or any GUI based app such as Droid manger will do .
2. Flashing only one part file ( xxx.tar.md5) Over Odin3.v3.07.Cooperve ; you may pick your file from here < registration is required >. Proper drivers installed inside your PC; Put the file into PDA part and do not touch anything else ( Factory reset and Re-partition not selected, Reboot option is OK though ) > click start. ( Do not remove USB cable till the process being terminated and take a complete screen shot of Odin log file entries for me.
This method does not wipe the partition in question., but there is a strong possibility you can not bypass the initial boot loop to get into the OS though.
Hi All,
Android Lolipop 5.1.1
features
Android 5.1.1
kernel of badadroid
change or delet Some app
smooth
stable
Battery is very good
Downloads
v8
http://www.mediafire.com/download/qhuk4ypwhialp21/omni+5.1.1+LionDroid+V8.zip
V7
http://opizo.com/N1ATZ
V6
http://opizo.com/Xakla
V4
http://opizo.com/F2bZr
V3
http://opizo.com/J1PpH
V2
android 5.1.1
http://opizo.com/f2eWy
V1.1
http://opizo.com/nHkIT
2015/02/25 Initial release
http://opizo.com/A2Tvt
changelog ROM
better battery & smoother
more optimization
more speed & free ram
more stable
update source
and other...
INSTALLATION
FIRST INSTALLATION
Bada 2.0 is required
Warning! It will remove Bada!
Download BOOTFILES, Kernel and FOTA for your device:
for 8500:
BOOTFILES https://yadi.sk/d/KhxqKyg4bP2nu
"start" kernel https://yadi.sk/d/ilhyKTaEfTo6L
FOTA https://yadi.sk/d/OtpVoaXpfNggE
for 8530
BOOTFILES https://yadi.sk/d/cBPD41VEbP2od
"start" kernel https://yadi.sk/d/wVGzUA96fGW55
FOTA https://yadi.sk/d/-WnbHbFHfNgZK
Flash BOOTFILES, "start" kernel and FOTA using Multiloader.
After reboot it will open android recovery
Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back -> Reboot -> Recovery -> Swipe to Reboot
Mount -> Enable MTP (if you see disable MTP - it is already activated) on this step PC can ask to install driver, use Android MTP driver
Copy Zip with ROM to Internal Storage or Sdcard -> Disable MTP -> Back
Install -> choose zip with ROM(mount point /sdcard for Internal storage and /external_sd for SD card) -> Swipe to Confirm Flash
Wait for flashing (about 10 min) -> Reboot System
First start take about 10-15 min, be patient.
Enjoy OMNI!
ROOT
Omni is without root support from default
To activate root flash zip via Recovery from XDA thread http://forum.xda-developers.com/showthread.php?t=1538053
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
https://mega.co.nz/#F!G0QXXRAC!pZ063qCaa5lxdD73SarU6Q
Thanks to
volk204 [for any things]
omni team
code rom team
@jeffreyvh
Rebellos
blue59
hero355
Tigrouzen
Benzox
and other Badadroid devs
reserved ....
first build android 5.1.1 but very Slow
now build android 5.0.2 smoother and more ram
please test rom and tell me bug
thnaks
good news!!!!!!
Sent from my GT-P5100 using Tapatalk
thank you nima
new version uploading ....
edit: uploaded
Thanks for your dedicated work to support the Waves!
One question: Will updating from Omni4.4 work in the same manner as described here?
Renth said:
Thanks for your dedicated work to support the Waves!
One question: Will updating from Omni4.4 work in the same manner as described here?
Click to expand...
Click to collapse
your welcome
Yes, the same is
nima.yavari said:
your welcome
Yes, the same is
Click to expand...
Click to collapse
Thanks again. Forgot to ask: Will it remove Bada and all its contents or stay in parallel like the OMNI does?
And is there a list of problems/missing features or similar regarding this version?
Renth said:
Thanks again. Forgot to ask: Will it remove Bada and all its contents or stay in parallel like the OMNI does?
And is there a list of problems/missing features or similar regarding this version?
Click to expand...
Click to collapse
remove Bada and all its contents.But then returned Flash Bada
i can't found bugs
features on post 1
nima.yavari said:
remove Bada and all its contents.But then returned Flash Bada
Click to expand...
Click to collapse
Thansk again. That's a little bit of a pitty since I am still regularly using Route66 navigation of Bada (bought the lifelong version) - did not find any reliably and suitably working free offline Android navi app.
Unfortunately I cannot copy over the zip when mounting the USB from recovery, in Windows Vista it is only shown as %SingleADBInterface% so I cannot copy data onto it.
Is there any way to get this fixed? Search in Google and here did not help yet (still investigating).
Ok. Managed to copy it via ADB push but cannot install: Flashing gives error:
executing updater ... failed
and before
failed to mount dev/lvpool/system ... ... ..at /system no such file or directory AppliedParsedPerms: ... removeexeattr of /system/binbackuptool.sh to 0 failed: operation not supported on transport endpoint
ß
When copying the zip into / folder I get:
Unable to find partition for path /omni 5.0.2 LionDroid V1.1.zip
Anything I can do here? Do I have to copy the .zip file to a special place? Or do I have to extract the boot.img and copy it separately (since the one in the 5.0.2 Liondroid is different from the one of OMNI4.4.4 which is currently on my S8500)?
Currently I've got the OMNI4.4.4 on SDCard, booting from SDCard. So I have not /external_sd as a directory. So maybe I need to set something as mountpoint (if so - how?) or have to copy the ROM ZIP to another place?
Renth said:
Thansk again. That's a little bit of a pitty since I am still regularly using Route66 navigation of Bada (bought the lifelong version) - did not find any reliably and suitably working free offline Android navi app.
Unfortunately I cannot copy over the zip when mounting the USB from recovery, in Windows Vista it is only shown as %SingleADBInterface% so I cannot copy data onto it.
Is there any way to get this fixed? Search in Google and here did not help yet (still investigating).
Click to expand...
Click to collapse
Renth said:
Ok. Managed to copy it via ADB push but cannot install: Flashing gives error:
executing updater ... failed
and before
failed to mount dev/lvpool/system ... ... ..at /system no such file or directory AppliedParsedPerms: ... removeexeattr of /system/binbackuptool.sh to 0 failed: operation not supported on transport endpoint
ß
When copying the zip into / folder I get:
Unable to find partition for path /omni 5.0.2 LionDroid V1.1.zip
Anything I can do here? Do I have to copy the .zip file to a special place? Or do I have to extract the boot.img and copy it separately (since the one in the 5.0.2 Liondroid is different from the one of OMNI4.4.4 which is currently on my S8500)?
Currently I've got the OMNI4.4.4 on SDCard, booting from SDCard. So I have not /external_sd as a directory. So maybe I need to set something as mountpoint (if so - how?) or have to copy the ROM ZIP to another place?
Click to expand...
Click to collapse
It is a bad copy
you can't copy files on recovery
go to bada or with ram reader and copy .zip
after go to recovery and install rom
nima.yavari said:
It is a bad copy
you can't copy files on recovery
go to bada or with ram reader and copy .zip
after go to recovery and install rom
Click to expand...
Click to collapse
Already tried this (copied within Bada) when I posted/edited my entries above - the error keeps the same - I cannot install this ROM (I used the one from V1.1 download)! Do I have to copy it on a certain place?
I took the OMNI4.4.4 from here (German only) which leaves Bada unharmed and completely runs from SD card. I managed to install that version again after wiping but whenever I try to install the version from here I get this very long cryptical error message from above (the one ending with "operation not supported on transport endpoint").
Since the boot.img of OMNI4.4.4 is different from the one contained in the OMNI5.0.2 here. Do I have to extract and copy it manually before trying to flash this rom here?
Ok, tried that but it damaged Bada installation and also Android did not work anymore. Had to flash a Bada update version and my previous OMNI4.4.4 FOTA to restore everything.
Any hints appreciated (cannot get rid of this cryptic error)!
Renth said:
Already tried this (copied within Bada) when I posted/edited my entries above - the error keeps the same - I cannot install this ROM (I used the one from V1.1 download)! Do I have to copy it on a certain place?
I took the OMNI4.4.4 from here (German only) which leaves Bada unharmed and completely runs from SD card. I managed to install that version again after wiping but whenever I try to install the version from here I get this very long cryptical error message from above (the one ending with "operation not supported on transport endpoint").
Since the boot.img of OMNI4.4.4 is different from the one contained in the OMNI5.0.2 here. Do I have to extract and copy it manually before trying to flash this rom here?
Ok, tried that but it damaged Bada installation and also Android did not work anymore. Had to flash a Bada update version and my previous OMNI4.4.4 FOTA to restore everything.
Any hints appreciated (cannot get rid of this cryptic error)!
Click to expand...
Click to collapse
full flash bada
format memory to fat32
flash fota and start kernel and bootfile JUST for this rom
now go to recovery Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back ->wipe every thing without external ->Swipe to wipe
now you can install rom
nima.yavari said:
full flash bada
format memory to fat32
flash fota and start kernel and bootfile JUST for this rom
now go to recovery Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back ->wipe every thing without external ->Swipe to wipe
now you can install rom
Click to expand...
Click to collapse
Meanwhile I already did so. Partitioning worked, installation worked but after reset Wave only shows its startscreen (Samsung Wave GT-S8500 in white letters) for about 15 minutes now and nothing happens (besides Wave getting really warm, nearly hot). Also restarting the wave does not change anything!
Anything else I can try? Do I have to checkmark Master Rom in Multiloader?
Renth said:
Meanwhile I already did so. Partitioning worked, installation worked but after reset Wave only shows its startscreen (Samsung Wave GT-S8500 in white letters) for about 15 minutes now and nothing happens (besides Wave getting really warm, nearly hot). Also restarting the wave does not change anything!
Anything else I can try? Do I have to checkmark Master Rom in Multiloader?
Click to expand...
Click to collapse
sure flashed fota this rom?
wave 1 or 2?
nima.yavari said:
sure flashed fota this rom?
wave 1 or 2?
Click to expand...
Click to collapse
It is Wave 1. Yes I flashed all 3 parts: Bootfiles, FOTA and kernel. But not sure what to checkmark in Multiloader. Decided to go with Master Rom.
Meanwhile tried a 2nd time with full flash of bada + the wipe you mentioned (but no formatting of SD since it already has been for OMNI4.4.4). Still no change. Everything worked fine but Wave stays in Start Screnn (Samsung Wave GT-S8500 in white letters) for 20 minutes now - just getting very warm.
And now? Doesnt seem to work for my devive.
Renth said:
It is Wave 1. Yes I flashed all 3 parts: Bootfiles, FOTA and kernel. But not sure what to checkmark in Multiloader. Decided to go with Master Rom.
Meanwhile tried a 2nd time with full flash of bada + the wipe you mentioned (but no formatting of SD since it already has been for OMNI4.4.4). Still no change. Everything worked fine but Wave stays in Start Screnn (Samsung Wave GT-S8500 in white letters) for 20 minutes now - just getting very warm.
And now? Doesnt seem to work for my devive.
Click to expand...
Click to collapse
to multiloaeder just chek bootfile / rc1 / fota
nima.yavari said:
to multiloaeder just chek bootfile / rc1 / fota
Click to expand...
Click to collapse
For flashing bootfiles you need either checkmark "Boot Change" or "Full Download" in Multiloader. Otherwise Boot will be grayed out.
But as said - already did so 2 times: Flash Bada (Full flash at 2nd time), wiped everthing (2nd time) partitioned everything, flashing omni5.0.2. Everything worked but wave1 stays in Startscreen forever afterwards. Neither bada nor android starts at all.
Any idea on how I can support hunting down this problem?
{
"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"
}
PREFACE
I've had this running for quite a while, but due to the amount of time I can dedicate to coding and testing, I've come to the conclusion of sharing it, even if it is not as ready as I would like it to be, and more changes are already on the way.
This is a beta version, so please treat it as such, and have your backup handy.Seeing the no-kexec workaround has been in use for quite a while, and also being used on other devices successfully, I consider it a stable release.
I also ask you to read every single word in the thread (well at least the first four posts), as I continue to elaborate on them.
As a community, it's easier to track down bugs, misbehaviours, etc. when working as a team, so your feedback will be greatly appreciated, but I kindly ask you to be very specific, every little detail counts, and the "it doesn't work" posts will not be taken into account.
Thank you for your understanding.
For your information, I have successfully tested and multi-booted:
ViperOneM9 3.5.0 (in primary)
MaximusHD 6.0.0 (directly to secondary)
ViperOneM9 3.5.0 (directly to secondary)
CM-13.0-20151210-NIGHLTY (directly to secondary)
Slim-himaul-5.1.1.beta (directly to secondary)
Notes:
* the supposedly "corrupted/inaccessible" external sdcard on Android 6 (Marshmallow) is not multirom related afaik.
* some of these ROMs take a long time to boot up, well above 10minutes, so patience
You use this tool at your own risk!!
I have tried to put as many safeguards as I can,
but I cannot be held accountable for any soft-bricks, hard-bricks, loss of data and/or information,
or anything else going wrong.
Introduction
MultiROM is one-of-a-kind multi-boot mod for HTC One M9 (hima). 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
Warning!
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.
Now seriously: Warning!
Beware of Dragons, Goblins, Gremlins and lingering primary_boot.imgDue to lack of kexec-hardboot kernel support, I am messing with your boot partition!
Since we lack kernels with kexec-hardboot patch on the M9, I'm using a workaround to bypass that restriction, and although tested successfully on the HTC One M7, HTC One M8 and HTC One M9, there are still several circumstances where things can go wrong.
If you are in doubt, either ask, or avoid it completely; MultiROM has always been a huge hack to begin with, and this is even more of a hack.
Always have a backup ready.
If you do get stuck [trying to (re)boot to primary] (i.e. starring at the boot animation, for a very long time) it is likely you have a lingering primary_boot.img (a gremlin), your primary ROM, should in fact be intact, but the workaround has "confused" the primary kernel, and has an incompatible one being used.
This is usually easily fixable by just restoring your "boot.img" from within TWRP->Restore.... there should be no need to restore everything else.
Please bear in mind, that some ROMs (particularly Sense based ROMs), can will take a long time to boot up, well above 10minutes, so patience!
Installation
Not supported at this time: 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 chosing 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.
2. Manual installation
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 (well, it should, but in this case it only has 2) you need to install:
Modified recovery (TWRP_multirom-YYYYMMDD-vXX-UNOFFICIAL-hima.img) - download the IMG file from second post and use
"fastboot flash recovery TWRP-multirom-20151210-v32a-beta1-UNOFFICIAL-hima.img"
(in download mode, for example)
Code:
C:ADB>fastboot flash recovery TWRP-multirom-20151210-v32a-beta1-UNOFFICIAL-hima.img"
target reported max download size of 800000000 bytes
sending 'recovery' (40248 KB)...
OKAY [ 2.883s]
writing 'recovery'...
(bootloader) HOSD CL#576582
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.475s]
finished. total time: 6.359s
C:ADB>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
MultiROM (multirom-YYYYMMDD-vXX-UNOFFICIAL-hima.zip) - download the ZIP file from second post and flash it in the MultiROM Recovery.
.
.
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.
We don't have a patched kernel, so I'm using a workaround.
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 this is NOT SUPPORTED
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.
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.
Screenshots here
Source code
MultiROM - https://github.com/Tasssadar/multirom (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Device files - ....
Everything is here:
https://github.com/multirom-htc
https://github.com/nkk71
XDA:DevDB Information
MultiROM, Tool/Utility for the HTC One (M9)
Contributors
nkk71, Captain_Throwback
Version Information
Status: Stable
Current Stable Version: 33testbuild
Stable Release Date: 2016-11-15
Created 2015-12-10
Last Updated 2016-11-15
FAQ and other notes
HTC One M9 - Peculiarities / Bugs
There are no kexec-hardboot kernels for the M9, so you need to enable the no-kexec-workaround. Please refer to post 4 for details.
Deprecated info (used to be a problem in v1 of the workaround)
Potential problems resulting in lingering primary_boot.img:
* Reboot from secondary to recovery, flash new primary ROM/kernel (this may be fixable in inject.c, but my first attempt had unexpected results)
* Reboot from secondary, then fastboot flash boot boot.img
* While in secondary, use an app (MultiROM, Flashify, etc), which dd's the boot.img
* Others??
In short, do NOT try to mess/flash/etc your primary kernel if the last ROM you had booted was a secondary. ... this will result in a "lingering" primary_boot.img
.
A few notes about enabled adb in MultiROM boot menu: having adb enabled in MultiROM boot menu (TWRP->MultiROM->Settings->Enable ADB) may interfere with the ROMs "connection" (MTP, etc), possibly even prevent the ROM from booting (rarely, but I've seen it happen). Since this option is usually only used for debugging, I recommend to keep this option disabled.
.
Something not working, or you need help debugging
Please provide the following information:
a detailed explanation of the problem
.
the recovery.log (found in /tmp/recovery.log or by copying it to the sdcard and then copying it to PC)
.
the link to the thread and name of file (+ which version) you are having problems with
.
due to the large size of some of these ROMs, I may not have time to download and test them, so please also upload the updater-script (found in ROM.ZIP under /META-INF/com/google/android/)
Device encryption
Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.
I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Downloads
Current Test Builds
All Current Test Builds can be found on androidfilehost under MultiROM TEST BUILDS
You should be using these, not the ones mentioned below!
Definition of Test Builds: These are stable builds which I have and am using (and testing). They contain the most up to date fixes as mentioned in the changelog under <tba>.
The main reason I'm calling them "Test Builds", is because they have not gone through extensive testing as what I would usually do for a "release version". I think most people would call them release versions, but I tend to be more conservative.
.
The second reason, they get uploaded to AFH instead of directly here, is two fold:
I'm maintaining the M7, M8, M9 and HTC 10 MultiROM versions, and uploading to AFH is easier and faster for me.
Updating the actual threads and posts, is too time consuming every time I want to push an update.
Changelog and NO_KEXEC 4.1 Information can be found in the HTC 10 MultiROM thread.
1. Main downloads
Modified recovery (based on TWRP): TWRP_3.0.2-0_multirom_hima_20160723-01.img
MultiROM Main ZIP: multirom-20160723-v33d-UNOFFICIAL-hima.zip
Not supported at this time MultiROM Manager Android app: Google Play or link to APK
AndroidFileHost (mirror & old versions): https://www.androidfilehost.com/?w=files&flid=45256
Installation Note: if you were using the previous no-kexec workaround, please reboot to primary ROM first (to get rid of legacy files), then flash TWRP and multirom
2. third-party kernels with kexec-hardboot patch
None exist at the moment, hence the use of the workaround.
3. Uninstaller
MultiROM uninstaller: multirom_uninstaller-20160424-v33c-UNOFFICIAL-hima.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash [RECOVERY][Hima] TWRP touch recovery, but it is not needed - those menus don't do anything if MultiROM is not installed.
Changelog
Code:
MultiROM v33d
=====================
* Fix MultiROM Boot Menu touchscreen for Sprint
* Fix MultiROM Boot Menu boot to recovery & bootloader
MultiROM v33b
=====================
* Updates for Android 6.0 compatibility
* New kernel logging + history (needs to be enabled in TWRP)
* Added no kexec-hardboot workaround version 2
[I][B](needs to be enabled in TWRP)[/B][/I]
MultiROM v32a-beta1
=======================
* initial port for HTC One M9 (hima)
[B]* Note: encryption not supported at this time[/B]
Recoveries:
Code:
2016-07-23 (33d)
=====================
* Rebased on android-6.0 tree
- fixes TWRP progress bar
* Includes official TWRP commits up to Jun 9, 2016
* Add support for package_extract_file("system.img", <block device>)
2016-04-19 (33c)
=====================
* Fixed external sdcard ext4 partition flashing
[I]Note: booting from OTG may be broken[/I] :(
2016-04-17 (33b)
=====================
* Rebase to TWRP 3.0.2
* Use new stock theme made by z31s1g - thanks!!!
* New partition selector
* Fix ZIP selector being set to wrong storage after flashing ZIP to a
secondary ROM
* Fixes for 6.0 compatibility
* Fixes for SuperSU compatibility. Use BETA 2.67-20160203160253 (
[URL="http://bit.ly/m_su"]http://bit.ly/m_su[/URL] ) or newer!
* Fixes for several installer scripts using non-conventional methods
when installing systemless root
* Fix inject multriom checkmark not showing on startup
* New option to enable kernel logging + history for multirom
* New advanced options for no kexec-hardboot workaround version 2
[I](yes the Info page is missing)[/I]
[I]refer to [URL="http://forum.xda-developers.com/showthread.php?p=64248526&postcount=4"]post 4[/URL] for detailed info[/I]
* Add progress tracking in multirom 'restore' install
2015-12-11 (32a-beta02)
=======================
* fixed access to ext4 partition on external sdcard
2015-12-10 (32a-beta1)
=======================
* initial port for HTC One M9 (hima)
Enabling no-kexec workaround
As of this version you need to manually enable the no-kexec workaround.
Go to TWRP -> MultiROM -> Settings
and enable the No-KEXEC workaround option
once you do you'll also have the option for ADVanced settings, please see below for a detailed description, though in most cases the default should suffice.
Explanation of the no-kexec workaround advanced options
(the Info page is supposed to provide the same information as here, but I haven't added that yet)
1- Use no-kexec only when needed
This should be the default for most users, the other options are more intended for advanced uses (kernel debugging, and such).
If MultiROM detects a kexec-hardboot enabled kernel in primary slot, it will use the standard kexec method to boot the secondary. If on the other hand it does not detect that the kernel supports kexec-hardboot then it will use the workaround.
2- ... but also ask for confirmation before booting
Same as option 1 above, but in addition you will be presented with a confirmation message, if the workaround is about to be used:
3- Ask whether to kexec or use no-kexec on booting
If the kernel in primary slot does support kexec-hardboot'ing then you will be presented with a choice of which method to use
If the kernel does not support kexec-hardboot then you'll be informed as in option 2 above
4- Always force using no-kexec workaround
Forces the no-kexec workaround to be used, even if the kernel in primary slot has kexec-hardboot support
Options 2 and 3, always present the user with a GUI confirmation, whereas option 1 and 4 will act as instructed without prompting the user.
Visual feedback provided by the Booting... card
Regular kexec-hardboot boot
Booting using no-kexec-workaround
Booting into primary, while the previous rom was using the no-kexec-workaround
(in which case the real primary needs to be restored first)
How does all this work, etc
The workaround:
MultiROM TWRP recovery works, and is able to flash ROMs to secondary
MultiROM in essence works (in particular, able to change the mount points during bootup)
what does not work is being able to use the secondary ROM's kernel (due to the lack of kexec-hardboot kernel and tools)
So how do we deal with booting any ROM if we can't use the proper kernel for the ROM?
Easy :
Upon selection of the ROM during MultiROM boot menu, we do the following:
"flash" secondary boot.img to primary partition slot
initiate a full reboot (secondary boot.img is in primary slot)
let the ROM auto-boot up on second boot
The good part:
It works.... has been for quite some time, but I kinda kept it hidden
.
Every secondary ROM has a boot.img file we can easily access to use the workaround; when you flash a ROM in MultiROM TWRP, not only are the "virtual" system, data, and cache partitions created, but also the boot.img.
The secondary ROMs' boot.img will be found /data/media/0/multirom/<name of rom>/boot.img or if it's on your external ext4 in the appropriate rom folder
We use that file and flash it to primary real boot partition and then upon second boot, the correct boot.img is in place for the correct ROM.
The bad part:
Note: the below needs to be revised as the "lingering primary_boot.img" is no longer an issue, however to do my affection for it, I can't just delete all references to it
What we (yes, we) have come to affectionately call the "lingering primary_boot.img" this should now be taken care of, as much as possible
.
Unlike secondary ROMs, the primary ROM does not have a boot.img file... since it is the primary ROM, the boot.img should always be in the real boot partition, since MultiROM expects the primary kernel to have kexec-hardboot capability, but it does not, so I just go ahead and mess with your primary boot partition.
Since we have no "boot.img" file for the primary, my workaround makes a backup of the kernel and names it primary_boot.img
This backup is created and/or used only under certain situations, for example (this is not an exhaustive list):
the last ROM was primary, and we want to boot a secondary ---> backup the primary boot.img, flash secondary one
.
the last ROM was secondary, and we're booting another secondary ---> just flash the secondary boot.img
.
the last ROM was secondary, and want to boot the primary ROM --> restore the primary_boot.img we backed up
.
^^ and here lies the problem, we cannot actually say if the backup we created is actually correct for the primary ROM.... ideally it is, but there are easy ways to break that UPDATE: not so easy to break it all, anymore
one very simple example (as mentioned in the FAQs) would be:
==> Reboot from secondary to recovery, flash new primary ROM/kernel ---> the backup of primary_boot.img will still be there, MultiROM will still think the last ROM was a secondary, and therefore restore the backup; which will result in a non-booting primary ROM since the backed up kernel doesnt actually belong to this ROM
this is what I call a "lingering primary_boot.img"
this is just one simple example, but it can happen for a variety of reasons... interrupted boots, some app/method flashed a new kernel, etc.
The solution for the "lingering primary_boot.img":
Delete (if it's there): /data/media/0/multirom/last_rom_was_2nd no longer used
[*]Delete (if it's there): /data/media/0/multirom/primary_boot.img
Reflash or restore the correct boot.img for your primary ROM
New safe guards to avoid a "lingering primary_boot.img":
TWRP will restore the primary boot.img when entering recovery
MultiROM identifies whether the boot.img currently in primary slot is secondary, by checking the boot.img itself;
it no longer relies on a separate file (last_rom_was_2nd)
If the boot.img in primary slot is not tagged as a secondary, it is considered a new primary boot.img
Long story short: the difference between kexec and no-kexec-workaround
Usual kexec-hardboot MultiROM
Select secondary ROM
MultiROM detects a boot.img
MultiROM reads the secondary boot.img into memory
MultiROM initiates a kexec second boot but into the secondary boot.img from above
MultiROM continues
No-kexec-workaround MultiROM
Select secondary ROM
MultiROM detects a boot.img
MultiROM flashes the secondary boot.img into the primary boot partition
MultiROM initiates a full second boot but with the secondary boot.img in the real boot partition
MultiROM continues as usual
so the difference is in point 3... whereas normal kexec'ing loads the secondary boot.img into memory and goes from there, the workaround, actually flashes it to the real primary boot partition... and continues normally from there
Small note regarding encrypted devices using the no-kexec workaround
Since I dont use encryption, I haven't tested this to much extent, but I believe that there is a BOOT PRIMARY ROM option, which you can choose to boot into Internal without decrypting the device first.
Please be aware that this should not be used, if: the last booted ROM was a secondary using the no-kexec workaround.
The reason is that the backup of the primary_boot.img, is stored in the multirom folder, so for the no-kexec to be able to restore it, it needs access to the /data partition:
Booting into primary, while the previous rom was using the no-kexec-workaround
(in which case the real primary needs to be restored first)
It's not too much of a big deal, because when the no-kexec workaround encounters an error, it reboots to recovery (and since recovery will restore the primary_boot.img), another reboot would be fine.
I do however (until I address this particular issue), encourage you not to use the BOOT PRIMARY ROM option, but instead decrypt the device, and then select the Internal ROM to boot.
Will this remain a "beta" version?
Most probably YES it will.... MultiROM is supposed to work with a kexec-hardboot enabled kernel; since that does not exist (at this time), on arm64 devices, I am using a workaround; since it doesn't exist and doesn't work, just work around it, if possible ... (call it "non-linear thinking" thinking if you wish)
until such time as the original author sees fit, or I decide to rename as "stable" (imho it is), it will remain called a "beta"
I have extensively tested this on the HTC One M7, the M8, and the M9 and have not found any side effects, so as of version 33b (2016-04-16), I consider this a stable release.
Devices using the no-kexec-workaround successfully
MultiROM threads for:
HTC One M7
HTC One M8
HTC One M9
.
Moto G 2015 by @GtrCraft
Moto X Play by @GtrCraft
OnePlus One (starting here) by @KINGbabasula
OnePlus 3 by @martinusbe
OnePlus X by @martinusbe ... (alpha status)
Sony Xperia Z5 by @Myself5
Sony Xperia L by @STRYDER~007
Sony Xperia SP by @Adrian DC
Xiaomi Redmi 2 by @premaca
.
(possibly Samsung Note 4, unsure if that was continued or not)
Others; unofficial builds? (if you are, kindly let me know, and I'll add you to the list)
Great worki @nkk71!
--
wysłane z HTCOne (m9) przez Tapatalk v5.4.0
Delete
--
wysłane z HTCOne (m9) przez Tapatalk v5.4.1
qriozum said:
Application "MultiROM" not working is HTCOne m9:
View attachment 3571948
--
wysłane z HTCOne (m9) przez Tapatalk v5.4.1
Click to expand...
Click to collapse
Somebody didn't read the OP . . .
Didn't flar2 add hexec path to elementalx kernel??
Does your workaround affect performance or functionalities in any way?
Dear All,
This is a highly experimental build, it is not meant for people who want a one-click-does-it-all solution, please read the OP, in particular:
I also ask you to read every single word in the thread (well at least the first four posts), as I continue to elaborate on them.
Click to expand...
Click to collapse
Thank you
In case, I wasn't clear enough, this is an "experiment", it works for me (mostly, except some bugs I've mentioned), if you want to join, you are more than welcome (at your own discretion and risk), otherwise, I can fully understand you being not comfy using it.
nkk71 said:
Dear All,
This is a highly experimental build, it is not meant for people who want a one-click-does-it-all solution, please read the OP, in particular:
Thank you
In case, I wasn't clear enough, this is an "experiment", it works for me (mostly, except some bugs I've mentioned), if you want to join, you are more than welcome (at your own discretion and risk), otherwise, I can fully understand you being not comfy using it.
Click to expand...
Click to collapse
is there a method to uninstall the mod?
throcker said:
is there a method to uninstall the mod?
Click to expand...
Click to collapse
yes of course, plenty, probably the easiest would be:
1- reflash "normal" TWRP to get rid of this one
2- restore backup (actually you only need to restore the boot.img)
you can delete the multirom folder manually, until I post an uninstaller
nkk71 said:
yes of course, plenty, probably the easiest would be:
1- reflash "normal" TWRP to get rid of this one
2- restore backup (actually you only need to restore the boot.img)
you can delete the multirom folder manually, until I post an uninstaller
Click to expand...
Click to collapse
many thanks. I just read somewhere elementalx kernel has kexec patch...am I wrong?
I read the entire op, i know about your workaround, is just a question to help and maybe get things easier for you (no more hacks)
throcker said:
many thanks. I just read somewhere elementalx kernel has kexec patch...am I wrong?
I read the entire op, i know about your workaround, is just a question to help and maybe get things easier for you (no more hacks)
Click to expand...
Click to collapse
You are wrong.
throcker said:
many thanks. I just read somewhere elementalx kernel has kexec patch...am I wrong?
I read the entire op, i know about your workaround, is just a question to help and maybe get things easier for you (no more hacks)
Click to expand...
Click to collapse
Feel free to ask any kernel dev about any of the following:
* kexec
* kexec-tools
* kexec-hardboot
* kexec-hb-tools
on arm64
I did not create this to make things easier on myself, so either
1- feel free to correct me, and point me in the right direction
2- stick to the thread
Just for info: thinking/creating/coding and testing this ("make it easy") workaround
wasnt easy at all
Please stick to the thread, I think my information and feedback requests were specific enough, so can we stick with them.
Sent from my HTC One M9 using Tapatalk
Just installed this on Verizon m9. So far so good. I have Candy Six running as primary and FluentRom as a secondary. Thanks for this.
MultiROM TWRP updated to "TWRP-multirom-20151211-v32a-beta02-UNOFFICIAL-hima.img"
downloads and changelog are in the third post
(this fixes the external ext4 partition problem)
Thank for your work. I try it as soon as possible.
I apologize if I missed this in the thread, I read through but have a tendency to overlook things I'm actually looking for. Is touch working for you guys in the rom selection menu?
Just wondering, I don't mind using volume keys to select
Sent from my HTC One M9 using Tapatalk
grim489 said:
I apologize if I missed this in the thread, I read through but have a tendency to overlook things I'm actually looking for. Is touch working for you guys in the rom selection menu?
Just wondering, I don't mind using volume keys to select
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Ah yes, one of those bugs
touch generally works, but is dependant on how the kernel was built, as @Captain_Throwback mentioned, if SECURE_TOUCH is not specified then touch wont work
which ROM is that?
nkk71 said:
Ah yes, one of those bugs
touch generally works, but is dependant on how the kernel was built, as @Captain_Throwback mentioned, if SECURE_TOUCH is not specified then touch wont work
which ROM is that?
Click to expand...
Click to collapse
Oh OK I see, haha I'm on candySiX primary ROM and viper secondary. Thank you!
Sent from my HTC One M9 using Tapatalk
Nexus 4 Repartition
No one is responsible for your actions except yourself. Everything written further may potentially brick your device, although risk is reduced to minimum.
This repartition package offers 1.5G /system; a /vendor partition and it is fully backward compatible with any ROM (including stock system.img).
Known-issues
HTML:
- If repartition pack says that device isn't correct,
than, if partition table wasn't modified before,
congrats! your device has different memory chip
that those I worked with. No worry, PM me and
I'll add support for it.
DO THE BACKUPs. Repartition will erase all your data
USB connection to PC is MANDATORY else you will not have opportunity to push ROM to your device
Installation
HTML:
# Before processing further we highly recommend you to use our TWRP which has support of EFS/Persist backup
# Or you might lose your IMEI/WIFI + BT mac addresses
# This mod is backwards compatible with any ROM so we highly recommend NOT to reverse it if repartition went well.
# You should use ONLY recovery from this thread since other don't support all benefits of this mod.
# When installing ROM just after you flashed zip and before installing GAPPs you MUST make a resize in TWRP since all roms are build for ~800M system.
# To restore stock layout use same zip and steps as for repartition.
1. Boot into recovery (You need to allow system partition modification to be able resize /system in recovery).
2. Backup your data & Move your files from flash to your PC.
3. Flash repartition pack zip.
4. Do the actions asked by repartition pack (go to Terminal in ordinary recovery and input word that pack will tell you. Everything else will be done automatically).
5. Phone will reboot into recovery.
6. Install TWRP from below (it is build with support of new partitions layout and sizes. It can be differed from official TWRP by next format 3.x.x-1 UA).
7. Format everything. (mount errors will not affect formatting!)
- In TWRP: Wipe > Format data
- Type yes
- Once this completes go to: Wipe > Advanced Wipe
- Tick all the boxes and wipe. There should be no further mount errors.
8. Install ROM which you like.
9. Enjoy better flash partition layout.
If something gone wrong - we recommend you using this guide to restore your phone back
Downloads:
Repartitioning package: GitHub
Credits:
Special thanks to
- Unlegacy-Android team;
- Sudokamikaze;
- ddaggebi for 8GB model layout;
- surfrock66 for his gide for Nexus 5;
As usual, feedback is appreciated
XDA:DevDB Information
Nexus 4 Repartition, Tool/Utility for the Google Nexus 4
Contributors
Clamor, sudokamikaze
Source Code: https://github.com/clamor95/android_device_unlegacy_recovery
Version Information
Status: Stable
Created 2018-09-19
Last Updated 2019-01-18
Common issues and F. A. Q.
Repartition pack should be safe for most devices. Common mistakes, issues and their solution will be published here.
1. You shouldn't flash any internal parts of repartition pack (*.sh files) only flash whole zip using TWRP. You may use my scripts for personal use or projects but authorship should to be kept.
2. If something isn't mounting after repartition try to format partitions that don't mount using Wipe -> Advanced Wipe in TWPR. Ideally you should format in that way all partitions in Advanced Wipe menu (see 5-th step of installation guide).
3. To be sure that repartition went well I enclose loging zip. Flash it after repartition (when device reboots into TWRP). It won't modify anything only generates a partition.log in root of internal storage and outputs your current partition layout to screen. You shoud check if your layout is same as those fragments I provide under spoiler (file systems doesn't matter). If there are any differences you have to discribe what you did and enclose partition.log to your post.
MAKO STOCK
Code:
21 159383552B 1040187391B 880803840B system
22 1040187392B 1627389951B 587202560B cache
MAKO MODIFIED
Code:
21 159383552B 1732247551B 1572864000B system
22 1732247552B 1994391551B 262144000B vendor
23 1994391552B 2099249151B 104857600B cache
4. If you have touchscreen problems use common instructions till you reach entering word. Than plug your phone to PC while you remain in recovery. Enter adb shell from cmd (if you don't know how - google) and enter word that repartition pack asked. Than your phone will reboot automatically into your old TWRP but with new partition layout.
5. Flashable resize zip for ROMs that support addon.d (automatic resize when dirty flashing updates).
actually the lower left corner of my phone screen doesnt work so can you please elaborate what kind of commands are we used to use and terminal and is there any other way to access terminal
mine q,a,z,1 these key are inaccessible in twrp as screen rotation is not supported
bgoel4132 said:
actually the lower left corner of my phone screen doesnt work so can you please elaborate what kind of commands are we used to use and terminal and is there any other way to access terminal
mine q,a,z,1 these key are inaccessible in twrp as screen rotation is not supported
Click to expand...
Click to collapse
Plug your phone to PC while you remain in recovery. Enter adb shell from cmd (if you don't know how - google) and enter word that repartition pack asked. Than your phone will reboot automatically into your old TWRP but with new partition layout.
What can I do to add support for 8GB models? Can I send you some partition tables that you can tinker with? Or sth else? Anyway, huge thanks for your dedication for this device!
ddaggebi said:
What can I do to add support for 8GB models? Can I send you some partition tables that you can tinker with? Or sth else? Anyway, huge thanks for your dedication for this device!
Click to expand...
Click to collapse
PM me, I need a partition table and I'd ask you to test if you have 8GB model.
Something went wrong and now I have only 552mb space. When I try to flash again it says it's not a Nexus 4.
Can anyone help please?
cyberon said:
Something went wrong and now I have only 552mb space. When I try to flash again it says it's not a Nexus 4.
Can anyone help please?
Click to expand...
Click to collapse
Sure. In PM.
OK so my nexus 4 can't transfer files to or from PC at all so if I do this and have the ROM downloaded it will wipe the ROM and the ROM would be gone and my phone would be a nice brick because I can't transfer any files to my PC like it charges with the PC but data transfer doesn't work so again would I be screwed?
@Nathan4923 correct. Usb connection and PC are mandatory
For those who downloaded repartition pack before this message is published, please redownload pack since previous version might have a problems with repartition. If repartition was already made, don't worry everything should be fine. Just use up-to-date pack.
can i return back to old partition if i want to? i hope someone would post a video tut for this one
@jluspo you can with same zip and same steps as for repartition. You didn't read first post carefully.
Clamor said:
@jluspo you can with save zip and same steps as for repartition. You didn't read first post carefully.
Click to expand...
Click to collapse
im using xda appits different layout on browser
I'm I doing it right? I still can't flash gapps
failed to mount Vendor, any suggestions ?
@jluspo resize /system with TWRP after ROM install before GAPPs because ROMs are designed to use ~800MB system.
@cqloveqc you had to format all partitions available in advanced wipe after repartition.
Clamor said:
@jluspo resize /system with TWRP after ROM install before GAPPs because ROMs are desined to use ~800MB system.
@cqloveqc you had to format all partitions available in advanced wipe after repartition.
Click to expand...
Click to collapse
Thanks for the help !
I've found that even with that error, i still succed the process
Hello ho can I do ,,resize /system with TWRP after ROM,,??? I can't find how to do that...
I installed your TWRP > backup > repartition zip > format all partitions > ROM
And now I'm stuck because I can't flash GAPPS...
Mato_xXx said:
Hello ho can I do ,,resize /system with TWRP after ROM,,??? I can't find how to do that...
I installed your TWRP > backup > repartition zip > format all partitions > ROM
And now I'm stuck because I can't flash GAPPS...
Click to expand...
Click to collapse
just read the OP carefully it already mentioned that you had to resize system after installing rom
you can do that by going to advanced wipe in twrp