When I bought the tablet from the alixpress seller it had a shady version of MoKee on it and given I in general don't like Mokee very much I decided to reflash to other roms, but none of them had auto-rotate.
I've tried MoKee (flashing my own file), LineageOS, and am now running Carbon.
I'm wondering if I'm the only one with the problem - and if not, if anyone was able to figure out how to fix it?
Using the "Sensor Test" app it's as if there is no accelerometer/gyroscope within the device at all (No Input Data).
Software wise I'm at:
TWRP & CarbonROM (from here)
{
"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"
}
I've reinstalled the MIUI China rom using the XiaomiFlashUtility, and that gave me back auto-rotate.
I've since installed XiaomiEU's TWRP & "Globalized" Rom, and auto-rotate persists.
I'm gonna try and install a custom AOSP/LOS -based rom now and see if that solved the issue, or if it's ROM-related.
Edit: After installing Carbon's TWRP (for treble support, it was the only 3.2.3 TWRP for Clover I could find) & LineageOS 16.0 ROM, auto-rotate is gone, and my bet's on the rom. I guess I'll go "back" to XiaomiEU's MIUI10, but it would be cool to know whether or now I'm the only one with the weird issue and whether or not there's a fix coming.
The only custom I tested is AICP-mordiford and I do not have a problem with auto-rotate .
^^
great rom, using it myself also, not a single problem
https://cloud.akane.blue/nextcloud/s/PbGugWPefp9fFNZ?path=/clover
Hi.
I'm in the same situation. The mi pad 4 worked flawless on the stockrom. With lineageos 15.1 and 16 it won't auto-rotate. I found no solution yet.
I just installed the Unofficial LineageOS 16.0. Auto rotate is turned off by default, but once I turned it on it worked as it did with the stock ROM.
Tomek0000 said:
The only custom I tested is AICP-mordiford and I do not have a problem with auto-rotate .
Click to expand...
Click to collapse
Update.
The autorotate stops too work after some time (long time). I using my automagic script/widget for this ocasion.
banesi said:
^^
great rom, using it myself also, not a single problem
Click to expand...
Click to collapse
----
Is its UI beautiful?Can I flash it directly with TWRP?
---------- Post added at 06:37 PM ---------- Previous post was at 06:30 PM ----------
Hello, may I have any questions about MoKee? Some people say that it is very stable, I want to know what are the disadvantages? Because I am trying to flash.
I tried flashing the china developer and stable stock roms via fastboot with 'clean all' and the problem of auto rotation persists. when I hold my tablet portrait the screen turns landscape, is there maybe a setting in the build.prop I can change to fix this?
Please help
yakie996 said:
I tried flashing the china developer and stable stock roms via fastboot with 'clean all' and the problem of auto rotation persists. when I hold my tablet portrait the screen turns landscape, is there maybe a setting in the build.prop I can change to fix this?
Click to expand...
Click to collapse
I have the same problem. Did you find a solution?
This problem I observed only in android 8 based custom roms . From the moment I tested some android 9 , I never had this problem .
Do not clear or format the Persistence folder
Do not clear or format the Persistence folder or you will lose - tada - autorotation. Plus you risk losing your IMEI.
If you have done this already then re-flash a stock ROM, confirm all is well, then put your ROM of choice back and in the process when using TWRP leave the persistence folder alone.
GregEden said:
Do not clear or format the Persistence folder or you will lose - tada - autorotation. Plus you risk losing your IMEI.
If you have done this already then re-flash a stock ROM, confirm all is well, then put your ROM of choice back and in the process when using TWRP leave the persistence folder alone.
Click to expand...
Click to collapse
Thanks for solution
Thanks for solution
Click to expand...
Click to collapse
Hi, did the solution work for you? I have the same problem, just reinstalled the official eu ROM, where auto rotate is working. Then back to a custom ROM, without deleting the "vendor" files ( I think that is what it is called on newer TWRP) an the auto rotating does not work.
I had a problem with autorotation, power off display during call, ... And all sensors. The subdirectory sensors disapered from persistant partition. When I restored persistant partition from backup all work again .
Install app to test sensors and check if it works.
The test app does not show any sensors unfortunately. I do not have a backup though, where can I get the files from?
You can unpack persistent partition file from the last official stock image. I am not sure if it is in the recovery version, but maybe only in fastboot version.
Extracting stock Boot, Recovery and Persist images
Talking here about how to extract the stock Boot, Recovery and Persist images, needed in case of e.g. bootloop upon flashing Magisk or TWRP, to reflash the stock image(s). Also, boot image is needed for patching from Magisk Manager (and flashing...
forum.xda-developers.com
If you will have it , install it.
Else you will can install full stock and repeat all steps.
Thanks for your answer. I can't find the persist.img for MI Pad 4 though, any idea where I could get it from? Instead I tried flashing an official ROM again, verified the rotation is working and then made a backup of the Persist partition in TWRP. Then I installed the Pixel Plus Rom again and restored persist from backup, but again the sensors are not working. Any idea what I made wrong? Or where can I get the persist.img from?
nalpo said:
Thanks for your answer. I can't find the persist.img for MI Pad 4 though, any idea where I could get it from? Instead I tried flashing an official ROM again, verified the rotation is working and then made a backup of the Persist partition in TWRP. Then I installed the Pixel Plus Rom again and restored persist from backup, but again the sensors are not working. Any idea what I made wrong? Or where can I get the persist.img from?
Click to expand...
Click to collapse
You should not need to restore the /persistence partition - just do not format it. It has had a name change in Android 11 i think it is now in Vendor. So do not clear or format /Vendor. Someone else can verify that. I am using the March release of Lineage with NikGapps and have no issues. Newer versions of Lineage have had many issues.
GregEden said:
You should not need to restore the /persistence partition - just do not format it. It has had a name change in Android 11 i think it is now in Vendor. So do not clear or format /Vendor. Someone else can verify that. I am using the March release of Lineage with NikGapps and have no issues. Newer versions of Lineage have had many issues.
Click to expand...
Click to collapse
Well that was interesting... So after your mention of LOS I installed the current version from xda after wiping Dalvrik/Cache/Data and System). Rotation now worked! But in LOS, my external DAC does not work so I tried isntalling Pixel Plus again, wiping the same stuff as before and now it suddenly worked! Strange why it didn't after installing the official ROM. Nevertheless it works now, thanks a lot
Related
After spending two whole days trying to flash my Galaxy S2 with MIUI 2.1.6 (also tried the latest Cyanogenmod and DarkyROM) and with nothing to show for it, it's time to ask for help.
My main goal is to install MIUI 2.1.6. The starting point is stock Gingerbread 2.3.5 (XXKI3). This is what I did:
- flashed stock 2.3.5 (XXKI3) via Odin
- rooted XXKI3 with CF-Root
- copied MIUI 2.1.6 on SD card (the zip file)
After that comes the part where I have to flash ClockworkMod Recovery and that's where the troubles start. My phone comes with 3e recovery which gives me the "failed to verify whole file signature" error after I try to flash CWM via the ROM Manager.
After browsing XDA forums, a lot of reading and trying both methods of overriding that bloody signature check (Untermensch's script method and Existenz's method of placing the Recovery file in /system/bin), none of them worked for me.
Untermensch's script method starts doing its thing but at one point it gives me an error message and suggests that my phone isn't rooted (which it definitely is, as I'm able to use Superuser, Root Explorer, AdBlock and every other root-only app).
Existenz's method of manually putting the Recovery file in /system/bin swaps the 3e recovery with CWM (orange letters, if I recall correctly), but after doing all the neccessary wipes and installing MIUI (or Cyanogenmod) from a zip file on my SD card, all I get is a boot loop. DarkyROM won't install at all, it simply gives me an error at the very beginning of the installation process.
At this moment I'm running stock Gingerbread 2.3.5, rooted by CF-Root and flashed with SpeedMod kernel. When I try to enter recovery, I'm getting CWM Recovery 5.0.2.3 (blue letters). However, if I try to wipe the phone and install MIUI from zip, all I get is another boot loop. And I'm back on 3e recovery.
Perhaps it's also worth mentioning my 3e recovery menu has no "reinstall packages" option which was mentioned in several threads on this forum that were vaguely related to my issue.
Anything I'm missing? Any ideas at all?
Thanks in advance and kind regards!
YouLaxy said:
My main goal is to install MIUI 2.1.6
Click to expand...
Click to collapse
Try the MIUI forums for support.
1) Flash CF-root
2) Copy the Miui zip into the sdcard
3) flash the Miui zip twice
4) reboot into CWM recovery
5) Flash the miui zip again
6) wipe cache/data
7) reboot into miui
oinkylicious said:
Try the MIUI forums for support.
Click to expand...
Click to collapse
The thing is, I'd ultimately like to be able to install any custom ROM, not just MIUI. So far none of them worked (MIUI, Cyanogenmod, DarkyROM), I'm guessing due to that nasty 3e recovery (nothing else comes to mind)
veyka said:
1) Flash CF-root
2) Copy the Miui zip into the sdcard
3) flash the Miui zip twice
4) reboot into CWM recovery
5) Flash the miui zip again
6) wipe cache/data
7) reboot into miui
Click to expand...
Click to collapse
I'll give that a go later today and post back the results. Cheers!
Nope, that didn't work. After flashing with MIUI twice via CWM and powering the phone off, I'm unable to enter recovery to flash MIUI for the third time, as the phone goes into boot loop.
Any other ideas, anyone? Thanks in advance!
Your not using rom manager are you?
Maybe its a bad miui download, where did you get the zip from?
Nope, I'm flashing the zip via CWM recovery, so after turning the phone off and doing the three-key thingy. I got the MIUI zip from MIUIAndroid.com and downloaded it three times, just to be sure there's not an issue with the zip.
YouLaxy said:
Nope, I'm flashing the zip via CWM recovery, so after turning the phone off and doing the three-key thingy. I got the MIUI zip from MIUIAndroid.com and downloaded it three times, just to be sure there's not an issue with the zip.
Click to expand...
Click to collapse
I have no clue then, it should work
Maybe you could try galnet miui?
Have you tried flashing other custom roms, eg hyperdroid or checkrom?
I did try to flash CyanogenMod (ended up with a boot loop, just like MIUI), as well as DarkyROM (got an error shorty after the start of the installation, can't remember what it was anymore). Seems my SGS2 simply isn't up for anything but stock ROMs. Bastard.
YouLaxy said:
I did try to flash CyanogenMod (ended up with a boot loop, just like MIUI), as well as DarkyROM (got an error shorty after the start of the installation, can't remember what it was anymore). Seems my SGS2 simply isn't up for anything but stock ROMs. Bastard.
Click to expand...
Click to collapse
CM7 does need doubleflashing, so when you go into CWM double flash the zip before wiping/rebooting.
And what was the error on the stock rom? Have you tried others.
Try this.
Its the resurrection edition of darkyrom. Its something to fall back on when other roms failI, it completely repartions your phone and should replace 3e with CWM and you'll have a nice darky custom rom
Make sure you follow the instruction to the letter
http://www.darkyrom.com/community/i...arkyrom-hd-v1-0-r5-resurrection-edition.6565/
veyka said:
CM7 does need doubleflashing, so when you go into CWM double flash the zip before wiping/rebooting.
And what was the error on the stock rom? Have you tried others.
Click to expand...
Click to collapse
Just tried to doubleflash CM7 and then do the wipe. Ended up in yet another boot loop (and unable to get into recovery). Then I restored the stock 2.3.5, rooted with CF-Root and tried to flash DarkyROM (via CWM recovery, of course). This is the message that it gives me:
{
"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"
}
So now I'm back on stock 2.3.5 once again. Blimey.
thteddieboii said:
Try this.
Its the resurrection edition of darkyrom. Its something to fall back on when other roms failI, it completely repartions your phone and should replace 3e with CWM and you'll have a nice darky custom rom
Make sure you follow the instruction to the letter
http://www.darkyrom.com/community/i...arkyrom-hd-v1-0-r5-resurrection-edition.6565/
Click to expand...
Click to collapse
I'll give it a go in a couple of minutes and post back with the results. Thanks for your input!
Wait you have an sgs 2? Well the darkyrom your trying to flash in your pic is for the galaxy one
This will seriously mess up your phone.. try the link.I posted should work
thteddieboii said:
Wait you have an sgs 2? Well the darkyrom your trying to flash in your pic is for the galaxy one
This will seriously mess up your phone.. try the link.I posted should work
Click to expand...
Click to collapse
Hahah, really? wow, hes lucky it didnt brick it, good old status 0 (oops should have noticed that, it means that the firmware isnt for this the phone you are trying to flash it on)
veyka said:
Hahah, really? wow, hes lucky it didnt brick it, good old status 0 (oops should have noticed that, it means that the firmware isnt for this the phone you are trying to flash it on)
Click to expand...
Click to collapse
Yeah I noticed cause it was darky 10.2.2 which I remember from my s1 days of flashing.. I was wondering why the 0 was there. Very lucky its not bricked
Let us.know how you go with the darkyrom HD resurrection.. darkyrom HD is for galaxy s 2 just in case you wanted to update in future and so you don't get confused
Feeling like a bit of a dumbass right about now. And just when I thought I tripple checked everything... Okay, that explains the DarkyROM issue, however still no clue what's wrong with MIUI and/or CM7. I'm sure I downloaded correct versions of those
I'm downloading the ROM from your link at this very moment, trying it shortly.
YouLaxy said:
Feeling like a bit of a dumbass right about now. And just when I thought I tripple checked everything... Okay, that explains the DarkyROM issue, however still no clue what's wrong with MIUI and/or CM7. I'm sure I downloaded correct versions of those
I'm downloading the ROM from your link at this very moment, trying it shortly.
Click to expand...
Click to collapse
All good. Its not hard to get mixed up. I remember how overwhelming it was when I first started learning to flash
Bit scary for a while til I learnt more and understood things better
Hmm I'm not to sure about the miui issue or cm7
Never used them, except for cm9 cause I like the aosp ICS..
Let us know how darkyrom HD goes for ya
Well, that worked. Had to flash twice to get it to work, though (got stuck on step #14 for 10 scary minutes and then just turned the phone off an reflashed)
I'll give DarkyROM a go. I do have one more question though. If I decide to try to flash MIUI once again, would it be enough to boot into CWM recovery and try to install it from zip (so, without doing anything to my DarkyROM installation) or do I have to go back to stock ROM for that?
Thanks a ton for your help guys, my SGS2 can run custom ROMs after all! Horray!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Lg G3. 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
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-d851.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.
Source code
kernel https://github.com/Skin1980/android_..._lge_msm8974ac
Device Tree https://github.com/Skin1980/device-ls990-multirom
TWRP https://github.com/Skin1980/Team-Win-Recovery-Project
Credits: @tassadar for the awesome work; @invisiblek and @savoca @patrik.KT for them help
@Tectas cause i used his ( awesome) source code for building the kernel
And sure... tnx to @HPTesla and the other guy ( sorry i deleted for error the messages) for testing this!
...and all the people that now i forget
reservedPLEASE READ THE MULTIROM WIKI TO UNDERSTAND BETTER WHAT YOU ARE DOING
IMPORTANT: Need to be with a Kitkat stock Rom ( if you use my kernel ) or with a rom that have a kernel with the kexec hardboot patch.
HOW TO INSTALL:
1- reboot in recovery and flash the new TWRP with Multirom support; --> HERE
2- reboot the recovery;
3- flash the kernel with the kexec hardboot patch HERE
4- flash the multirom zip; ---> HERE
5- install every Rom you want ( advanced--> multirom --> add rom )
6- reboot and choose the rom you want to boot.
You can also use a Cyanogenmod or similar with the wonderful Rin Kernel by @Tectas --> DOWNLOAD FOLDER
If you want show me your love for this you can consider a small DONATION
Issues:
1- On boot the touch need some seconds to work in multirom menu, you can use the volume keys to move and the power button to select.
You are awesome man. Flashed and installed with no issues. Currently running BarRin and a backup of Dirty Unicorns. I was kinda stressing on setting this up but it was way easier then I imagined it would be.
You will have a donation coming your way as soon as I get paid.
Thank you! Thank you! Thank you!
It's so exciting to see how far the G3 is coming along and I love it! Thank you! I will definitely be testing this in the future (just not right now) :good::good::good::good:
I remember this. Also safestrap. These are sweet. Thanks.
Sent from my LGLS990 using XDA Free mobile app
this sounds incredible....so is it possible to run barrin and a lolipop rom?
If I flash the modified twrp in the op so I can use this ROM, would I need to re flash a different twrp if I didn't want to use multirom anymore? Or is the twrp in the op good for any rom?
mrkrabs said:
this sounds incredible....so is it possible to run barrin and a lolipop rom?
Click to expand...
Click to collapse
I've been testing this since a few days ago. Once properly installed and set up, when my phone boots I have the choice of stock and 6 other roms to choose from. It's the best, really. Since BarRin is modified stock, you can use it as your primary as long as you use the included kernel from this post. Also, rin kernel which is included with BarRin will be getting a kexec-hardboot patch shortly. I'm sure engine will start using it once I build it.
---------- Post added at 07:52 AM ---------- Previous post was at 07:50 AM ----------
Will32 said:
If I flash the modified twrp in the op so I can use this ROM, would I need to re flash a different twrp if I didn't want to use multirom anymore? Or is the twrp in the op good for any rom?
Click to expand...
Click to collapse
I was able to restore my nandroid made with the original bump twrp just fine. If you do it the classic way thru twrp you will lose multirom boot bc it restored my old kernel but yes. You can restore old backups in this twrp just fine from my tests.
I cant for the life of me get my BarRin backups to restore, either as primary or secondary roms, I took two for safe measure, one to my internal and one to a USB OTG, both say when being Restored: "Unable to find file system (first period)." when it first moves to restore then finally fails completely with the same error followed by "Unknown restore method for '/rpm'
Now I have two questions:
I created this backup using the original non-multirom twrp and am trying to restore it with the multirom twrp, could this be the issue?
Is it as simple as with the N7 multirom to just flash the original twrp, restore, and restart the process?
I can confirm I can flash both CM12 and BarRin fresh to the Primary partition and both boot without error.
EDIT: Color me even more confused.. Flashed back to 2.8.40 twrp, got the same errors when restoring but phone booted just fine, Truly stumped
JaceAlvejetti said:
I cant for the life of me get my BarRin backups to restore, either as primary or secondary roms, I took two for safe measure, one to my internal and one to a USB OTG, both say when being Restored: "Unable to find file system (first period)." when it first moves to restore then finally fails completely with the same error followed by "Unknown restore method for '/rpm'
Now I have two questions:
I created this backup using the original non-multirom twrp and am trying to restore it with the multirom twrp, could this be the issue?
Is it as simple as with the N7 multirom to just flash the original twrp, restore, and restart the process?
I can confirm I can flash both CM12 and BarRin fresh to the Primary partition and both boot without error.
EDIT: Color me even more confused.. Flashed back to 2.8.40 twrp, got the same errors when restoring but phone booted just fine, Truly stumped
Click to expand...
Click to collapse
Yeah i have no idea. I made a nandroid of zv4 stock, installed everything then made another nandroid after. I never wiped anything, until I went to test nandroids. But ultimately I just kept stock as primary and multiple aosp as secondaries. I restored both nandroids thru twrp fine, but didn't try to add backups via multirom advanced option in twrp.....
Like I said I have no clue, Works currently though and thats what matters BarRin Primary and CM12 Secondary, Now to try the other lovelies!, Thanks for this!
I'm using barin now and I have a backup of it. I don't have the full barin zip downloaded. Can I restore my barin backup as my primary rom as long as I use the kernel in the op? I don't want to download barin unless I have to. Slow speeds where I'm at today.
Will32 said:
I'm using barin now and I have a backup of it. I don't have the full barin zip downloaded. Can I restore my barin backup as my primary rom as long as I use the kernel in the op? I don't want to download barin unless I have to. Slow speeds where I'm at today.
Click to expand...
Click to collapse
I believe so. Restore your backup and reflash the kernel. If that doesn't bring back up the multirom boot, go back into twrp and reflash the third zip, the multirom scripts. But hopefully you only need the kernel.
HPTesla said:
I believe so. Restore your backup and reflash the kernel. If that doesn't bring back up the multirom boot, go back into twrp and reflash the third zip, the multirom scripts. But hopefully you only need the kernel.
Click to expand...
Click to collapse
Man I appreciate the help. Hopefully this last question will clarify all of it for me.
As I said, I'm on barin now. If I flash all 3 items in the op in order, will my current rom then be known as my "primary rom"? Then I can flash secondary roms, right?
Will32 said:
Man I appreciate the help. Hopefully this last question will clarify all of it for me.
As I said, I'm on barin now. If I flash all 3 items in the op in order, will my current rom then be known as my "primary rom"? Then I can flash secondary roms, right?
Click to expand...
Click to collapse
Yeah, that's what I did. I restored my stock zv4 nandroid(since BarRin is stock based you're good) then flashed the kernel, twrp and multirom. I rebooted after each(kernel I rebooted system to make sure kernel was OK, twrp, I rebooted back into recovery to make sure twrp was updated then flashed multirom and rebooted system again). Then under advanced->multirom in twrp I added roms from flashable zips and under list roms I flashed gapps for each.
As for the help, anytime, it's what this community should be all about. Just pay it forward man.
I keep getting kernel crash and unable to load my 2nd rom...my default rom...cm12 runs fine...I installed the rin kernel for that...and I.tried using the kernel in post 2 for the 2nd rom which is barin...I tried with and without the kernel...
edit: ok...got 2 cm roms working as multi boot...but still can't get cm 12 and barrin working..kernel crash right after the lg screen when trying to load barrin as secondary rom
Sent from my LG-ls990 using XDA Free mobile app
Fantastic thanks a lot guys
Using the AOSP kernel provided in 2nd post, I'm not getting any MultiROM features in TWRP. Do I need to flash the stock-based kernel on install and then overwrite with AOSP? Thx!
otroguero said:
Using the AOSP kernel provided in 2nd post, I'm not getting any MultiROM features in TWRP. Do I need to flash the stock-based kernel on install and then overwrite with AOSP? Thx!
Click to expand...
Click to collapse
So after you tap advance, you don't have see a button for multirom? Are you using a theme in twrp?
Pump Ac7i0n said:
So after you tap advance, you don't have see a button for multirom? Are you using a theme in twrp?
Click to expand...
Click to collapse
I have a theme in my current TWRP 2.8.3 and that's what reboots. Same 2.8.3 as before. No MULTIROM options in Advanced. I've been per the OP. I guess my question is, can this be initiated from an AOSP system? All flashes and reboots are successful, but nothing changes... Thanks for the help @Pump Ac7i0n. Your builds make my g3 rock like it oughta.
Hello.
I am currently trying to bring my Samsung Galaxy SII (GT-I9100) to a current CM version. The phone is completely untouched and has never had any custom upload or anything similar.
The problem now is, while there are loads and loads of guides out there, all of them seem very old - and different. One says i need heimdall, other says odin, others seem way easier just adding the files to my SD card and installing through recovery - and basically all that does is confusing the hell out of me.
So, first things first - the most important thing seems to get root access - i've done that successfully using the "How To Root Samsung Galaxy SII GT-I9100"
The one thing that confuses me now is - where is CWM? I thought i installed it using that root method?
Another method i tried before updated my recovery while it was running from the stock one to CWM - but after rebooting into recovery it was the stock one again.
SO i am even more confused now as before.. At least i hope that my phone is and stays rooted, so that is a plus.
The question now is, what am i missing?
Were all of these CWM things i've "installed" just temporary? Where do i get the full version, and how do i install it?
Basically what i'm asking is, is there a current guide for all of the flashing? Can anyone maybe guide me through it? I mean, nowadays it seems the S2 should be flashed very easily, and i'm guessing it's just getting the correct CWM version and flashing it via recovery - but since i'm not sure, i'm asking for some guidance.
The easiest way to get a CWM custom recovery is to flash PhilZ recovery through your standard stock 3e recovery.
Look for your Android build number (under settings>>about device/phone) then go to the PhilZ thread......
http://forum.xda-developers.com/showthread.php?t=1877270
download the matching kernel/recovery zip (NOT .tar), copy to a micro SD card (or possibly even internal storage I can't be sure of that....It's been a while since I rooted my S2), boot into recovery and flash......
Simple as......
Edit....The thread states 'external sd card' so forget about using internal storage......
{
"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"
}
Thanks a lot, worked flawlessly!
I hope it is okay that i just ask about the next steps here.. Since i immediately ran into new problems.
So, i booted into the CWM and tried to push my cm package that i want to install via mfastboot-v2 and it failed stating the following errors:
Warning: No file_contextdetected filesystem ext4 for /dev/block/mmcblk0p9
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
It seems obvious ofcourse that i need to do a factory reset before, but the S2 is probably susceptible to a superbrick and i should not do that factory reset on my stock rom.
The question is - what now? Also i was not able to mound the external SD card in CWM.
ThePatchelist said:
Thanks a lot, worked flawlessly!
I hope it is okay that i just ask about the next steps here.. Since i immediately ran into new problems.
So, i booted into the CWM and tried to push my cm package that i want to install via mfastboot-v2 and it failed stating the following errors:
Warning: No file_contextdetected filesystem ext4 for /dev/block/mmcblk0p9
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
It seems obvious ofcourse that i need to do a factory reset before, but the S2 is probably susceptible to a superbrick and i should not do that factory reset on my stock rom.
The question is - what now? Also i was not able to mound the external SD card in CWM.
Click to expand...
Click to collapse
1) I can't comment on mfastboot v2 as I have no experience of using it.
2) which CM package are you trying to install?
3) the super brick bug only affects android 4.0.4 Icecream Sandwich....
And PhilZ kernels have removed/patched the EMMC_cap_erase command that activates the 'bug' anyway.
4) if your CM package came from XDA or the CM website, then it should install through PhilZ recovery.
5) what are you trying to achieve that requires external SD to be mounted?
The cm i'm trying to install is the latest stable one, being cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100
About the superbrick, i did not know that the philZ kernels fixed that, good to know.
And i tried to simply put the ROM image onto the external SD card to simply flash it from the CWM - but since that external SD card cannot be mounted, i tried using the adb push method.
Could i use the internal storage and simply apply update from zip file from there? Thought that might be an issue due to it being erased in the process?
CM 12 is lollipop base isn't it? The last CM I flashed to my S2 was 11.....but then my eldest son asked me for a phone so I returned it to stock and loaned it to him.
Obviously haven't been able to flash it since.
As for CM12, I've read that overall, it's not as stable as 11 (contains more bugs) and is heavier on the battery. I'm sure I've also read that the S2s memory partitions have to be re - mapped @gsstudios maybe you can help here as I'm not sure)
As far as I am aware, installing the rom from internal storage shouldn't be an issue......The only time data on that partition is compromised is if you perform a factory reset....and you would only have to do this (if at all) AFTER you have installed the rom. I'm also fairly sure that you have to have a specific version of CWM installed to be able to install newer CM roms, but again, I'd have to suggest waiting for @gsstudios to comment here......
ThePatchelist said:
The cm i'm trying to install is the latest stable one, being cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100
About the superbrick, i did not know that the philZ kernels fixed that, good to know.
And i tried to simply put the ROM image onto the external SD card to simply flash it from the CWM - but since that external SD card cannot be mounted, i tried using the adb push method.
Could i use the internal storage and simply apply update from zip file from there? Thought that might be an issue due to it being erased in the process?
Click to expand...
Click to collapse
Hi,
There are a few points I will give:
- cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100 is an old build of CM12.1. It doesn't have all of the latest features like Isorec (isolated recovery for TWRP 3 recovery support), hence it should be avoided. Instead, use CM12.1 Unofficial by CNBLACK or CM12.1 Unofficial by Markox89. Although they are unofficial builds, these are considered more stable than the CM12.1 snapshot build being offered.
- You can install CM12.1 via internal storage. It won't get erased during the flashing process, instead, this only happens when you re-partition your phone using a .pit file. You will need to increase you system partition size in order to flash gapps (google play store, etc) using Lanchon's repit tool. Documentation is already provided.
- Once you've installed CM12.1, it is recommended to change the recovery to TWRP (preferred) or CWM. This is because CM recovery is very limited and will become a problem later if you decide to flash CM13.
gsstudios
Hey there again.
First of all, thank you very much! I successfully flashed one of the cm's you posted @gsstudios and so far it works.
Now though i am struggling with the TWRP installation since i have to increase the partition size for gapps.. As i've read it TWRP must be flashed via heimdall (back to square one..) and there i am having problems with the connection (claiming interface error, was googling for 2 hours now, nothing helped)
Basically what i am now looking for is a way to get TWRP without having to flash via heimdall, but rather installing it through the cm recovery which seems not possible?
I am really sorry that i continue to post my issues here since i'm sure you guys helping out are really annoyed by this.. But currently i am again running my head into a brick wall not knowing how to proceed :/
Edit: jesus..
I have no idea how or why, but apparently i got it now.
I installed ROM manager externally and it showed me that i have CWM and TWRP already installed.. At first i was confused and set up TWRP as my recovery, but that only booted into the normal cm recovery. Then i tried the CWM one and when going into recovery i am now in TWRP.. Am reformatting my partitions, so far without any errors.
I am not less confused but close to being happy. As soon as i can flash gapps afterwards all of this is over and done.
Thanks still, for all the help guys! And sorry for being the usual annyoing user..
No problem fella....but in future, STAY AWAY from rom manager.....It sometimes doesn't play nice with the S2.
In the past I've read that it can 'fubar' recovery and can cause boot loops. (So up til now, you've been lucky).
For further info, Heimdall simply isn't needed.....The primary method of TWRP installation is via Odin. I'm a bit concerned that rom manager said you have both CWM and TWRP installed....Some investigation is in order....
Whichever recovery you boot into with the button combination is the recovery you have installed.....
Hi, so i need some help regarding an issue i'm currently facing ( and have been facing for about a month now).
I'll give you the full story of my device and what i did:
First, when i got the phone. First thing i did was unlock bootloader and install custom recovery + rom (sultanXDA rom)
Then, when the android 7.1 ROMs started coming out, i installed one of those, worked great.
After a while i got bored, and decided to actually try the stock ROM, so i used a tool which took the phone back to 100% stock.
After this, i wanted to install a custom recovery so i could root and install xposed, i unlocked bootloader and tried installing THIS recovery.
It seems to install just fine via fastboot, but when try to go into the recovery, it tries to boot into it, then it just boots into the system instead. And after this, i have no recovery at all. I tried going back to stock again (which also got me the recovery back). But once again, when i try to install the recovery it doesnt work.
Anyone got any idea why this is?
Any help would be appreciated
Shpped said:
Hi, so i need some help regarding an issue i'm currently facing ( and have been facing for about a month now).
I'll give you the full story of my device and what i did:
First, when i got the phone. First thing i did was unlock bootloader and install custom recovery + rom (sultanXDA rom)
Then, when the android 7.1 ROMs started coming out, i installed one of those, worked great.
After a while i got bored, and decided to actually try the stock ROM, so i used a tool which took the phone back to 100% stock.
After this, i wanted to install a custom recovery so i could root and install xposed, i unlocked bootloader and tried installing THIS recovery.
It seems to install just fine via fastboot, but when try to go into the recovery, it tries to boot into it, then it just boots into the system instead. And after this, i have no recovery at all. I tried going back to stock again (which also got me the recovery back). But once again, when i try to install the recovery it doesnt work.
Anyone got any idea why this is?
Any help would be appreciated
Click to expand...
Click to collapse
That recovery is only for Oxygen OS 3.1.3 and ROMs based on it.
I take it you flashed Oxygen OS 2.x that's why it didn't boot.
Joshwin Aranha said:
That recovery is only for Oxygen OS 3.1.3 and ROMs based on it.
I take it you flashed Oxygen OS 2.x that's why it didn't boot.
Click to expand...
Click to collapse
Thanks for your reply
Unfortunately (see image below) i am on OOS 3.X
EDIT: sorry about the large image, i dont know how to make it smaller
{
"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"
}
Don't think anything wrong with that recovery but you could also try Sultans twrp or blu sparks V41 twrp.
Exodusche said:
Don't think anything wrong with that recovery but you could also try Sultans twrp or blu sparks V41 twrp.
Click to expand...
Click to collapse
I tried different Recoveries too, (i know i tried both Sultan and Blu Spark's Recoveries). I tried all i could find on Android Development page.
The issue does seem very weird, i dont know where i messed up in the process. It seems like when i try to install the new recovery, it does replace the old one but never boots.
Shpped said:
I tried different Recoveries too, (i know i tried both Sultan and Blu Spark's Recoveries). I tried all i could find on Android Development page.
The issue does seem very weird, i dont know where i messed up in the process. It seems like when i try to install the new recovery, it does replace the old one but never boots.
Click to expand...
Click to collapse
What recovery did you use to install 3.1.3? I think it has to be old stock recovery from 2.X.X or won't work. When I used the new stock recovery from 3.x.x had issues myself.
Exodusche said:
What recovery did you use to install 3.1.3? I think it has to be old stock recovery from 2.X.X or won't work. When I used the new stock recovery from 3.x.x had issues myself.
Click to expand...
Click to collapse
Thanks for your reply
I used the stock rom to install 3.1.3 from 2.x.x (don't remember exactly which version i was on). Anyways, the issue right now is the fact that i cannot install any custom recoveries.
Shpped said:
Thanks for your reply
I used the stock rom to install 3.1.3 from 2.x.x (don't remember exactly which version i was on). Anyways, the issue right now is the fact that i cannot install any custom recoveries.
Click to expand...
Click to collapse
What it tells after flashing in fastboot?
cva_kabil said:
What it tells after flashing in fastboot?
Click to expand...
Click to collapse
Hi, this is what it shows me on install. After installing when i try to go into the recovery it stays on the oneplus logo :/
Okay so this is weird.
After installing adb drivers on my work pc (im currently at work) and flashing, it for some reason works!
Thanks for all the help guys
For anyone facing the same issue: Try using a different pc with different adb and fastboot drivers, dont know why it worked for me, but it did!
Shpped said:
Okay so this is weird.
After installing adb drivers on my work pc (im currently at work) and flashing, it for some reason works!
Thanks for all the help guys
For anyone facing the same issue: Try using a different pc with different adb and fastboot drivers, dont know why it worked for me, but it did!
Click to expand...
Click to collapse
Glad it worked
Hello, so I unlocked the bootloader and I installed a rom but when I want to configure it, the phone restarted and only lasts 10 seconds on and restarts back.
This problem happens with every android I want to install.
It isn't a hardware problem because I buy it few days ago
Agustinmds said:
Hello, so I unlocked the bootloader and I installed a rom but when I want to configure it, the phone restarted and only lasts 10 seconds on and restarts back.
This problem happens with every android I want to install.
It isn't a hardware problem because I buy it few days ago
Click to expand...
Click to collapse
Please give a detailed explanation, as of what you did, and what custom rom you flashes. Did tou flash the firmware ?
MyNameIsRage said:
Please give a detailed explanation, as of what you did, and what custom rom you flashes. Did tou flash the firmware ?
Click to expand...
Click to collapse
The phone went into bootloop because I was trying to install miui 9 with the "dualboot patcher" program and the phone did not start any operating system, I made a wipe and wanted to install another rom, but when I tried to install it, problems with bootloop started .
I tried with everything and I can not make it work, it's infinite bootloop, when I install the stock rom through miflash it installs successfully but when I start it restarts while loading android about two / three times and then loads android and after about ten seconds of having loaded it restarts and that's how it is always
Yes,I flash Miui, Resurrection Remix, Nitrogen Os, Lineage Os (13, 14.5), Paranoid Android, Slim and a few more, and I've tried many firmwares but nothing, I can not get it out of the bootloop.
Help pls
Agustinmds said:
The phone went into bootloop because I was trying to install miui 9 with the "dualboot patcher" program and the phone did not start any operating system, I made a wipe and wanted to install another rom, but when I tried to install it, problems with bootloop started .
I tried with everything and I can not make it work, it's infinite bootloop, when I install the stock rom through miflash it installs successfully but when I start it restarts while loading android about two / three times and then loads android and after about ten seconds of having loaded it restarts and that's how it is always
Yes,I flash Miui, Resurrection Remix, Nitrogen Os, Lineage Os (13, 14.5), Paranoid Android, Slim and a few more, and I've tried many firmwares but nothing, I can not get it out of the bootloop.
Help pls
Click to expand...
Click to collapse
I guess the problem is with the partitions which dual boot makes, please ask this on the official dual boot patcher thread, you will get a better answer there.
Agustinmds said:
The phone went into bootloop because I was trying to install miui 9 with the "dualboot patcher" program and the phone did not start any operating system, I made a wipe and wanted to install another rom, but when I tried to install it, problems with bootloop started .
I tried with everything and I can not make it work, it's infinite bootloop, when I install the stock rom through miflash it installs successfully but when I start it restarts while loading android about two / three times and then loads android and after about ten seconds of having loaded it restarts and that's how it is always
Yes,I flash Miui, Resurrection Remix, Nitrogen Os, Lineage Os (13, 14.5), Paranoid Android, Slim and a few more, and I've tried many firmwares but nothing, I can not get it out of the bootloop.
Help pls
Click to expand...
Click to collapse
Having some experience from dual booting with my previous device, I guess somehow you messed up your kernel and partitions. I would suggest to make a fresh start, meaning that you flash twrp recovery, boot into recovery and make a factory reset, and then flash a kernel image according to the rom that you want to install, then install the rom and try boot again. If you flash original miui rom make sure you flash lazyflasher or rom will not boot.
akisg said:
Having some experience from dual booting with my previous device, I guess somehow you messed up your kernel and partitions. I would suggest to make a fresh start, meaning that you flash twrp recovery, boot into recovery and make a factory reset, and then flash a kernel image according to the rom that you want to install, then install the rom and try boot again. If you flash original miui rom make sure you flash lazyflasher or rom will not boot.
Click to expand...
Click to collapse
Oh ok, i'll try it but I don't think this is going to work..
anyway thanks
No, it didn't worked, there are the logs, I don't know how to do
{
"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"
}
Agustinmds said:
No, it didn't worked, there are the logs, I don't know how to do
Click to expand...
Click to collapse
I can't see any error in the above screenshots. Is your device still not booting?
Try this: extract boot.img from rr rom and flash it through twrp by selecting install -> image -> boot.img -> and select boot
This should flash rr kernel in case your kernel is messed up and so rom can't boot. Reflash rom and see if that works.
akisg said:
I can't see any error in the above screenshots. Is your device still not booting?
Try this: extract boot.img from rr rom and flash it through twrp by selecting install -> image -> boot.img -> and select boot
This should flash rr kernel in case your kernel is messed up and so rom can't boot. Reflash rom and see if that works.
Click to expand...
Click to collapse
So I have to flash boot img and then flash the zip with the rom?
Agustinmds said:
So I have to flash boot img and then flash the zip with the rom?
Click to expand...
Click to collapse
Yes, try that in order to restore your rom's kernel and then flash rom as normal. Be sure to flash boot.img as "boot" and not recovery after selecting image
Damn it didn't work
I'm going to take a video with the error
Agustinmds said:
Damn it didn't work
I'm going to take a video with the error
Click to expand...
Click to collapse
You get an error while flashing or your device just can't boot?
Also, have you tried flashing any official miui rom?
akisg said:
You get an error while flashing or your device just can't boot?
Also, have you tried flashing any official miui rom?
Click to expand...
Click to collapse
I don't get any error, just when I turn on the phone it enters in an infinite bootloop.
Yes, I've tried with a lot of official roms and the same result.
https://www.youtube.com/watch?v=0xU4ABxlAyE
Agustinmds said:
I don't get any error, just when I turn on the phone it enters in an infinite bootloop.
Yes, I've tried with a lot of official roms and the same result.
https://www.youtube.com/watch?v=https://www.youtube.com/watch?v=0xU4ABxlAyE
Click to expand...
Click to collapse
have you tried flashing lazyflasher after flashing rom before rebooting?
akisg said:
have you tried flashing lazyflasher after flashing rom before rebooting?
Click to expand...
Click to collapse
Yes, but it does not work, I do not know what else to do, should I send it to a technical service or is there still hope?
Agustinmds said:
Yes, but it does not work, I do not know what else to do, should I send it to a technical service or is there still hope?
Click to expand...
Click to collapse
I just saw the video you uploaded. If this happens with any kernel/rom combination then i think your device might be faulty. Have you tried another kernel? Does the same happen with stock kernel and rom? Have you tried flashing stock rom from pc with mi flash tool?
Sent from my Redmi Note 4 using Tapatalk
akisg said:
I just saw the video you uploaded. If this happens with any kernel/rom combination then i think your device might be faulty. Have you tried another kernel? Does the same happen with stock kernel and rom? Have you tried flashing stock rom from pc with mi flash tool?
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
I tried everything and it's the same, I don't think that the phone is faulty because I bought it a few days ago and it worked well.
Agustinmds said:
I tried everything and it's the same, I don't think that the phone is faulty because I bought it a few days ago and it worked well.
Click to expand...
Click to collapse
Well maybe you should try another kernel compatible with this rom or another rom/kernel combination. Also, flashing baseband firmware might also help.
How I do that?