Hello guys!
After learing a lot from these great devs arround here i decided to start to try out a new project! Multirom!!
You might or might not have heared of it, THE multi-boot mod for the Nexus 7. I found it and have decided to port it for our device.
First of all, it is a very initial release now. Though I have tested multiple cases and didn't find any problem except those in the bug list, bugs can arise. Do have a backup! Also, do read through the whole OP and 2nd post! If you don't understand something, rather read again and/or ask!
For more information on how it works and what it does, I suggest that you read the first few posts in the original thread. Those are very detailed and well-written posts that explain MultiROM in general. Installing roms to USB and Ubuntu/Ubuntu Touch of course doesn't work for our device atm.
Installation
The device must not be encrypted!
You need to flash the modified TWRP recovery that has MultiROM extensions. My version is based on the latest sources with gordon0001's device-specific modifications included. You can keep this recovery if you don't want to use MultiROM anymore and you like TWRP, because the MultiROM extensions don't interfere with other functions, even if the boot sector is not injected.
You have to flash a kernel that is capable of Kexec-hardboot.
Links
You can find everything at https://www.androidfilehost.com/?w=files&flid=32204.
multirom-20150521-v32-UNOFFICIAL-p880.zip : The multirom zip
CM12_Kernel_Patched.zip : CM 12 Kernel with Kexec-Hardboot Patch ; Thanks to @Adam77Root the patch and @laufersteppenwolf for building Kernel
multirom_uninstaller.zip : Selfexplaining
Known Bugs
-Reboot to recovery doesn't work.
-UI has some graphical bugs
-Double Press to boot Secondary Rom doesnt work -> Press twice on the Rom you want to boot and press Powerbutton at the same time till you recoginze a vibration
-You tell me more
Changelog
23 May 2015: Initial release
Credits
@Tasssadar for MultiROM, Kexec-hardboot for Nexus 7 and his help with debugging and porting
@Adam77Root for Thread Content
XDA:DevDB Information
[MOD][23 MAY] MultiROM v32, Tool/Utility for the LG Optimus 4X HD
Contributors
fritzcola
Version Information
Status: Testing
Created 2015-05-23
Last Updated 2015-05-24
Explanation
In the next two examples, I will refer any official, unofficial, or CM-based roms as CM. Keep this in mind.
I use the word 'injected', because MultiROM is actually injected into the boot partition. It works on any kernel that is capable of doing Kexec-hardboot (and if you don't want to use different kernel (i.e. you will use kernel sharing), it will work on unpatched kernels as well).
I may refer to non-shared kernel method as Kexec(-hardboot) method
Example scenario of multi-booting CM with CM and kernel sharing
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Since the base rom is CM, you can share the same kernel. It will be faster as there will be no hardboot needed.
The installation steps are easy and it doesn't take more time than a normal installation.
Example scenario of multi-booting CM with CM and different kernel
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Select 'Don't share'.
Continue with installation.
Now, since the target kernel (that is installed with the rom) is very likely not patched, you will have to flash one of my linked kernels to that rom. Do this by selecting 'List roms', selecting the desired rom, than 'Flash ZIP' and flashing one of the kernels I have patched.
You can only share kernels if you are on the same Android version for example 5.0.x!
Source Codes:
Tree
Any screenshot? I didn't understand the ui bugs. What are they ? Great work fritzcola I will install my device when ui bugs are solved
CrazyWinner said:
Any screenshot? I didn't understand the ui bugs. What are they ? Great work fritzcola I will install my device when ui bugs are solved
Click to expand...
Click to collapse
Look here! https://www.dropbox.com/s/whor0zf6xx7z4jh/VID_20150523_234854.mp4?dl=0
fritzcola said:
Look here! https://www.dropbox.com/s/whor0zf6xx7z4jh/VID_20150523_234854.mp4?dl=0
Click to expand...
Click to collapse
Ow it's no problem for me Installing now , great work !
thanks
its work good
HI @fritzcola i have this bugs
after flash kernel
system ui has stopped on Euphoria rom
sim internet not work on ResurrectionRemix+BlissPop rom
some rom need to disable sim (plane mod )or it got bootloop from home screen PAC-ROM LP rom
work before but now i have this.
many times when add lolipop rom in multiboot i get error
blkdiscrad faild: operation not supported on transport endpoint
e:error executing updater binary in zip '/tmp/mr_update.zip
faild to install zip
thanks
mater2 said:
HI @fritzcola i have this bugs
after flash kernel
system ui has stopped on Euphoria rom
sim internet not work on ResurrectionRemix+BlissPop rom
some rom need to disable sim (plane mod )or it got bootloop from home screen PAC-ROM LP rom
work before but now i have this.
many times when add lolipop rom in multiboot i get error
blkdiscrad faild: operation not supported on transport endpoint
e:error executing updater binary in zip '/tmp/mr_update.zip
faild to install zip
thanks
Click to expand...
Click to collapse
That error with executing bla bla bla is rom related!
I already have TWRP 2.8.6.0 installed. To use your MultiROM Mod do I just need to flash MultiROM zip? Or do I need to flash recovery img (I found in your link)?
Will the uninstall zip send me back directly to the Stock TWRP 2.8.6.0?
__________________________________________
It works. But I'm getting the same problem as @mater2.
"error executing updater binary in zip '/tmp/mr_update.zip";
I tried latest BlissPop 3.4 and Euphoria 1.1.
If it is ROM related how can we solve it?
I saw some users reporting the same problem with the Nexus 5. They said the problem was on the "updater-script" of the ROM.
Thanks for your work and attention.
Enviado de meu Optimus 4X HD usando Tapatalk
gugu6897 said:
I already have TWRP 2.8.6.0 installed. To use your MultiROM Mod do I just need to flash MultiROM zip? Or do I need to flash recovery img (I found in your link)?
Will the uninstall zip send me back directly to the Stock TWRP 2.8.6.0?
__________________________________________
It works. But I'm getting the same problem as @mater2.
"error executing updater binary in zip '/tmp/mr_update.zip";
I tried latest BlissPop 3.4 and Euphoria 1.1.
If it is ROM related how can we solve it?
I saw some users reporting the same problem with the Nexus 5. They said the problem was on the "updater-script" of the ROM.
Thanks for your work and attention.
Enviado de meu Optimus 4X HD usando Tapatalk
Click to expand...
Click to collapse
1. Create backup from primary rom
2. Wipe everything and install rom you want as secondary as primary
3. Make backup from Primary you want to have as secondary
4. Use option to add rom to MR with Backup
5. Restore backup from old Primary
Are iodak and werewolf supporting multirom ?
@fritzcola
@gugu6897
strange thing its work for me all roms i can multiboot after some days and try some roms except euphoria because its not work with patched kernal after that
the error Shows up i try to format every thing internal +cache+davlik
doesn't fix that .
its allow to add 4.4.4 or 4.1.2 rom but 5.0x didn't
thanks for your good work
CrazyWinner said:
Are iodak and werewolf supporting multirom ?
Click to expand...
Click to collapse
I tried Werewolf kernel. The answer is no [emoji17].
Enviado de meu Optimus 4X HD usando Tapatalk
@gugu6897 @CrazyWinner
the kernel in this post (patched kernel) only can used for multiboot.
when use patched kernel
maybe you will have bug with sim internet with all roms except blissbob.
every thing else work good
@CrazyWinner, looks like iodak (and mourta too) has kexec-hardboot, but my secondary ROM (MIUI v5) don't boot. I double tap it, but the device just power off.
Does someone know any ROM that works with MultiROM?
Enviado de meu Optimus 4X HD usando Tapatalk
Look at Known Bugs in post #1
Sent from my A0001 using XDA Free mobile app
fritzcola said:
Look at Known Bugs in post #1
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I forgot about that [emoji28].
Enviado de meu Optimus 4X HD usando Tapatalk
progress
is it 'save' and will you update this anytime soon??
an update to MultiROM v33 - MultiROM TWRP 3.0.0-1 would be amazing
Extractor 2.4 from @Alexey71
derders said:
an update to MultiROM v33 - MultiROM TWRP 3.0.0-1 would be amazing
Click to expand...
Click to collapse
+1
I just discover the win tool Extractor 2.4 from @Alexey71 , as I didn't succeed to get finish compiling mmb 5.1.1.37 (or 29), I played with @csk1jw 2xAosp LP &MM system.new.sdat:
http://forum.xda-developers.com/showpost.php?p=57742855&postcount=42
extraction + re-zip(boot.img+file_contexts +/system/) in @laufersteppenwolf Nameless 5.1.zip + twrp’ add 2nd multirom + reboot and IT JUST WORKS!
I can now multiboot, WITH Nameless 5.1 AS PRIMARY: mmb 5.1 as 2nd+
cm11+OEMlg JB (+ BlisspopLP+ crdoidLP).
Many thanks to native kexeced Nameless’ kernel for LP!
Unfortunately’ the re-zipped aosp MM did not boot (boot.img conflict? or primary slot required with kexec.. or I miss more).
I believe there won’t be any future update on mmbLP, so it will be good if, @csk1jw or @MoltenMotherBoard or @streambinder could make an old_fashion-zipped official ultimate edition to be used with gorgeous @fritzcola ’ multirom 2.8.6 .
Also if they explain me how to bake it, patched with microG, i try wakelockblocker's patch for a better battery control in ‘pure’ FLOSS.
I still hope that, in this combination, some could give a try to my infamous nightly-cm11+3; while waiting for a snappy MM snapshot...
http://forum.xda-developers.com/and...kelock-blocker-official-2016-nightly-t3393825
Basics multirom tips;
-If you think something is wrong, like battery drain or excessive reboot: in twrp menu go to advanced menu then fix permissions and re-flash multirom32 on primary rom before rebooting;
-Always use ext sdcard for twrp’s copy-backup and avoid using twrp’s File Manager to restore, otherwise they could be buried and waste your mem until a complete re-format; if needed: boot in primary rom (or install a rom ZIP!) and copy them to sdcard/twrp/backup/IdDevice… with your favorite apk.
-For better efficiency use native kexeced Nameless 5.1 for primary rom.
Actually I don’t know if mmb5.1 is 100% compatible with @laufersteppenwolf ‘s Nameless 5.1_kernel.
Be aware that the smell of night roasted marshmallows is scientifically attracting werewolves.
Related
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps. Sorry for inconvience.
this is beta release. for t705 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/show....php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock firmware as primary. you can flash cm as additional.
Installation:
1. https://yadi.sk/d/t5peOTA-c84cv - this is modded recovery. flash via odin
2. https://yadi.sk/d/wEbLeriJc84dP - patched stock kernel
https://yadi.sk/d/EXpUO4tTc84db - multirom main program
flash through modded recovery patched kernel and multirom.
uninstallation:
https://yadi.sk/d/wm-dD6bgc8EZ9 - flash this uninstaller through recovery, then flash original twrp
multirom apk from play store doesnt support this release.
reserved
more reserved
new version has been uploaded
changelog:
- wrong resolution and position on twrp, but usable -FIXED
- in List Roms installed roms dont shown -FIXED
- in multirom boot menu touchscreen downt work. use buttons (vol-,vol+,power) -FIXED
Great to see this for the Tab S, will it get ported to SM-T800?
Hi!
When I try to flash UNOFFICIAL CM like additional I get an error: Error executing updater binary in zip '/tmp/mr_update.zip'.
What am I doing wrong?
I´ve managed to install the latest cm11 build on my sm-705, but wifi doesnt work.
Does someone now how to fix it?
[/COLOR]
svardman said:
I´ve managed to install the latest cm11 build on my sm-705, but wifi doesnt work.
Does someone now how to fix it?
Click to expand...
Click to collapse
do the cellular functions work? calls and mms/sms, data?
thought the cm11 was for t700 wifi only. Odd that wifi does not work (assuming cell data and calls work..that would be strange)
No nothing of those thing works, wifi works IF I install cm 11 as the primary rom, but not if I installs cm 11 as the secondary rom.
svardman said:
No nothing of those thing works, wifi works IF I install cm 11 as the primary rom, but not if I installs cm 11 as the secondary rom.
Click to expand...
Click to collapse
yes that rom is not for the 705.
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps. Sorry for inconvience.
Is it OK to use this Kernal on the t700 with stock Rom and cm12? I would like to give it a try just not sure.
Hello It is possible to try a multirom for T705 , set primary rom a Sam based rom (with SkyHigh kernel) and secondary CM rom (wifi only T700).
Thank you
Might give this another try.
Leonidas87 said:
Samsung Galaxy Note 4 Dual Boot/multi Rom support: https://youtu.be/CpegzNc4ZH0
Check this out. Trying to get support brought to our tablet.
Click to expand...
Click to collapse
Good luck would really like to see thay on our tab S
Ok everyone we have a new development
---------- Post added at 02:21 AM ---------- Previous post was at 02:20 AM ----------
I got a developer to bring dual/tri/quad boot if you want to our Galaxy tab s 8.4 t700
Fallow the link:
http://forum.xda-developers.com/showthread.php?t=3137677
(MOD) Dual/Tri Boot Galaxy Tab S 8.4 T700
Dual boot patcher
I found this one but I think it's the same thing.
http://forum.xda-developers.com/showthread.php?t=2447534
It works fine on my t700
working with the dev to bring multiboot patcher to TM-800 so we can use touchwiz and cm/aosp roms along side it
already used on my note 4 and works very well:good:
Actual:
I use CyanogenMod and Mokee teams sources and add some changes to device config.
Latest CM12 builds
СМ12.1 build 24.07.2015
normal- https://yadi.sk/d/l0sQrKeXi4rpT
experimental - https://yadi.sk/d/Sus83ATLi4rjv (aptx bt, mako gps)
news: - kernel, config updates . SoundControl removed, revert to deodex.
revert cm12.1 BT - https://yadi.sk/d/DHjDF-fAi4sQE
СМ 12.1 build 21/07/2015
normal - https://yadi.sk/d/EwsQB88Qhz7RD
experimental - https://yadi.sk/d/X07SjR3Fhz7Rm (GPS from nexus4, APTX BT)
+fixed updater-script - added ifelse(is_mounted("/system"), unmount("/system"));
СМ12.1 build 13.07.2015 - https://yadi.sk/d/CtPkfkpchq2Yb
СМ12.1 build 13.07.2015 w aptx support(experimental) - https://yadi.sk/d/LRV6F7N2hq2bS
fixed: wifi, BT, boot light, recovery, offline charging
Cm 12.1 03.07.2015 build - https://yadi.sk/d/GG3gFTtYhe3dQ
Changes in kernel, libs, binaries, configs
Tested - worked/
CM12.1 11.06.2015 build - https://yadi.sk/d/VyIKm27xhCdhE
CM12.1 20.05.2015 build - https://yadi.sk/d/WnR7d73mgkzcX
CM12.1 28.04.2015 build - https://yadi.sk/d/bn_IsRx1gJaRs
kernel w soundcontrol v3, many kernel and ril updates from см team
CM12.1 20.04.2015 build - https://yadi.sk/d/xiKPp0EBg7Kyo
kernel w soundcontrol v3, updates from см team
gps libs from мако(nexus 4) (possible gps work better) for recovery - https://yadi.sk/d/JU39SUbPg7Kmu
PAC 5 20.04.2015 build from neosuslik - https://drive.google.com/uc?id=0B6kPZoGYA4tfaFhOdjIxenNYbnM&export=download
Mokee 5.1 12.04.2015 build from neosuslik - https://docs.google.com/uc?id=0B6kPZoGYA4tfSGdlNldodnhuVTQ&export=download
CM12.1 build(06.04.2015) tested - https://yadi.sk/d/bzBHxTDmfoyck
move apps to sd fix added, dual recovery
kernel w SoundControl v3 for cm12.1 - https://yadi.sk/d/xPWTpM4ufpgnA - you need faux sound control or other app to tweak sound levels.
CM12 build (01.04.2015), ODEXed, fix for move apps to sdcard - https://yadi.sk/d/93AA69qtffk7Q
CM12 build (12.03.2015), ODEXed - https://yadi.sk/d/dTadZHj_fCZKN
CM12 build (04/03/2015), ODEXed - https://yadi.sk/d/K20AhXQ4f2ha9
CM12 build (28/02/2015) - https://yadi.sk/d/GGDHoe76ewFe4
CM12 build (20/02/2015) - https://yadi.sk/d/mmi7ic1Eeo5Eh
news:
new cm12 updates, bugfixes and bugs
Mokee5 build (25/02/2015) - https://yadi.sk/d/yI-cBxQheskpk
How to install:
a)
1. flash boot.img from archive
2. boot to recovery and flash firmware archive
b) reboot to recovery and flash firmware archive
Old(not actual now):
Big thanks to thomas1991_12 and pabx. This Rom based on their work.
English screenshots - http://forum.xda-developers.com/showpost.php?p=56982062&postcount=77
More Russian screenshots - http://4pda.ru/forum/index.php?showtopic=475149&st=9040&view=findpost&p=35853307
Whats worked: see original theme - http://forum.xda-developers.com/xperia-z/orig-development/exp-lollipop-xperia-z-t2929369
Latest CM12 port(qsnc 09.02.2015 build based) - https://yadi.sk/d/QcxE0x0WedRUd
Updated boot.img w philz recovery and vibro for 09.02.2015 - https://yadi.sk/d/anPzmPL0eeiCg
CM12 for ZR, cm-12-20150112-INFECTED-yuga based:
CM12 for ZR: cm-12-20150112-INFECTED-yuga.zip port - https://yadi.sk/d/L_eIwqujdz6sb
30.12.2014 Update, pabx 5.0.8 build based:
boot - https://yadi.sk/d/BMTyrqVpdnfDQ
system - https://yadi.sk/d/uK10pxZSdnfDa
fix - https://yadi.sk/d/4CBtWW7wdnfDJ
20.12.2014 Update
system.img from 20.12.2014 - https://yadi.sk/d/LObcDGPOdXW4B
boot.img - https://yadi.sk/d/ynTfhBdHdXW3v
fix(Xperia ZR specified files (zr camera libs, sensors.conf etc, you need install it via twrp recovery before boot system)) - https://yadi.sk/d/GU_LI9S2dYwya
04.12.2014 Update:
system.img from 4.12.2014 - https://yadi.sk/d/yeqUq35rdAgGG
boot.img - https://yadi.sk/d/jXkoWjC4dAgFZ
fix(Xperia ZR specified files (zr camera libs, sensors.conf etc, you need install it via twrp recovery before boot system)) - https://yadi.sk/d/8fWVGGj5dAgHM
GAPPS - https://yadi.sk/d/wxoFZUWidAgJr
Worked SuperSu - http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
***************************************************
Installing:
flash via fastboot or flashtool (in fastboot mode) boot and system images
Fastboot:
fastboot flash boot boot.img
fastboot flash system system.img
flash fix(recommended before first boot), supersu, gapps ...etc via recovery
if no internal sdcard found try this(in adb or terminal console):
su
restorecon -FR /data/media/0
***************************************************
Google Apps installation
After booting your phone for the first time, download the gapps package and push it to /sdcard using adb (or MTP):
adb push gapps_50_yuga_004-00cb.tgz /sdcard/
adb reboot
Your phone will now reboot and automatically install gapps during the boot process. (note that your phone will reboot twice - this is normal).
recommend to keep the gapps package in /sdcard/ after the installation finished: Upgrading to a new release will erase your existing gapps installation - but if the package is still present in /sdcard/, it will be automatically installed during the first boot.
*************************************************
Thank you for your effort Looking forward to testing this ROM upon upload. And i know it sounds silly, but an english version will be uploaded right???
I've been checking XDA like 10 times a day for the past two weeks hoping for this, and now it's finally here!!! You sir, deserve a medal.
I have a question, and I'm not sure if it's supposed to go here or the Q&A thread, since it's not specifically related to this ROM, per se. I just want to know how you built this; where did you get the device tree/binaries (not really sure what I'm talking about here, I've only read the building tutorials, don't really understand them fully)? AFAIK, Sony hasn't released them for the ZR, so how'd you do it? Is there some way to port them from other devices or something? Even a reference point to start searching would be great.
Thank you for your work!
P.S. Also, does this question belong in the Q&A thread or not?
Even i was wondering, but i thought perhaps it's only right to give the dev some time to upload the full details
kash296 said:
Even i was wondering, but i thought perhaps it's only right to give the dev some time to upload the full details
Click to expand...
Click to collapse
Of course, no pressure at all on the dev; I just wanted to say kudos, and thought I might as well ask. [emoji12]
xenius9 said:
Coming soon... Now kernel worked, ROM started, need little fixes.
Big thanks to thomas1991_12 and pabx. This Rom based on their work.
Bad news:
I have no time to develop, rom not work on all ZR-s - need additional kernel developing?(on many ZR models this rom work(on 2 phones work normal now), on other not (on my zr not work properly - mixed image on screen))
Now i have:
Kernel w twrp recovery - https://yadi.sk/d/WJw4gqmqcnLWd
SystemImage (from sony z, need add camera libs in vendor folder and some in etc/firmware and fix sensors.conf - from .283 stock firmware) - https://yadi.sk/d/S0Bh4H8gcmqRv
Xperia ZR specified files - https://yadi.sk/d/VZ8whMhccoCnt - zr camera libs, sensors.conf etc, you can install it via twrp recovery
Installing:
flash via fastboot or flashtool (in fastboot mode) boot and system images
test
Root - flash latest supersu via twrp recovery http://download.chainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Click to expand...
Click to collapse
Um. So that means right now, it's a list of separate files??? Anyway awesome work.
P.S Sorry abt quoting the whole post, i hate that. But my comment wouldn't make any sense then
Awsome
Everything working fine. Just like stable daily driver rom. Can't say about battery right now.
The only thing missing is root because SuperSU 2.23 dosen't seem to work. I think some kernel modifications will be needed for proper execution of SU binary
BTW Thanks alot .
sshivampp said:
Everything working fine. Just like stable daily driver rom. Can't say about battery right now.
The only thing missing is root because SuperSU 2.23 dosen't seem to work. I think some kernel modifications will be needed for proper execution of SU binary
BTW Thanks alot .
Click to expand...
Click to collapse
RIL works ????? ( Are you able to make calls and receive calls and send messages etc ?)
If you are using this as daily driver then try testing bluetooth, wifi, RIL, mobile internet (2g+3g), camera etc......
I would definitely do all this on weekend....
@Xenius :- HATS OFF MAN.......... Even if it just boots, I would say that it's sheer genius..........
nikhilkaushik said:
RIL works ????? ( Are you able to make calls and receive calls and send messages etc ?)
If you are using this as daily driver then try testing bluetooth, wifi, RIL, mobile internet (2g+3g), camera etc......
I would definitely do all this on weekend....
@Xenius :- HATS OFF MAN.......... Even if it just boots, I would say that it's sheer genius..........
Click to expand...
Click to collapse
I have exaaams You guys are tempting me And what do we do abt Gapps?? Jus download one of the lollipop gapps???
nikhilkaushik said:
RIL works ????? ( Are you able to make calls and receive calls and send messages etc ?)
If you are using this as daily driver then try testing bluetooth, wifi, RIL, mobile internet (2g+3g), camera etc......
I would definitely do all this on weekend....
@Xenius :- HATS OFF MAN.......... Even if it just boots, I would say that it's sheer genius..........
Click to expand...
Click to collapse
Bluetooth is fine except I cannot accept or share file with apk extension
WiFi also seems to be fine till now and yes I can make calls, messages, and can connect to data network.
Camera quality is accepteble (photo preview is kind of buggy )
Till now what I cannot test its GPS as I don't use it. but can provide logcat if anyone wants
Edit: At latest lollipop release for xperia Z (18 November), RIL is broken, atleast in ZR with this kernel, don't know about Z
maybe kernel update will fix this
---------- Post added at 10:49 PM ---------- Previous post was at 10:40 PM ----------
kash296 said:
I have exaaams You guys are tempting me And what do we do abt Gapps?? Jus download one of the lollipop gapps???
Click to expand...
Click to collapse
I suggest exam first
BTW you can download gapps from here
or direct link of one I downloaded here (I don't remember the source page but it was from XDA)
Thanks for the gapps link. Holidays inbetween so it aint a prob for the exams. Downloading the image right now, will try out the bluetooth and see if i too get the same issue
Xenius you are genius. Booted and running smoothly without any FCs.
Sent from my Lollipop for ZR using XDA Free mobile app
.
Man
big tnxfor your awsome work:cyclops:
And can you upload your kernel source? May be developers like @Alx31TLse can build more lollipop roms:fingers-crossed:
Yes i can, now i build new kernel w new ramdisk(w working root).
18.11.2014 firmware working... new kernel too... root working
Files...soon.
All updates added. See 1st post.
xenius9 said:
All updates added. See 1st post.
Click to expand...
Click to collapse
I am having trouble downloading from playstore after flashing gapps.. As there isn't a file manager preinstalled, I'm trying to download one, so that i can get back my old apps which are backed up in the SD card. Anyone else has the same issue abt the play store?
P.S I found out the problem. My Gmail wasn't synced so my account wasn't fully functional. Never mind
kash296 said:
I am having trouble downloading from playstore after flashing gapps.. As there isn't a file manager preinstalled, I'm trying to download one, so that i can get back my old apps which are backed up in the SD card. Anyone else has the same issue abt the play store?
Click to expand...
Click to collapse
I Use adb for apps installation and total commander+adb plugin for any dev deals
you can made small installation zip for recovery w needed apps
xenius9 said:
I Use adb for apps installation and total commander+adb plugin for any dev deals
you can made small installation zip for recovery w needed apps
Click to expand...
Click to collapse
Not so familiar with the adb codes, i've never felt the need to use them. Is the kernel fully permissive? I'd like to know if i can run Viper4android on it.
kash296 said:
Not so familiar with the adb codes, i've never felt the need to use them. Is the kernel fully permissive? I'd like to know if i can run Viper4android on it.
Click to expand...
Click to collapse
Install it and test)))
xenius9 said:
Install it and test)))
Click to expand...
Click to collapse
I'm definitely going to. But why i asked is, cause they were mentioning about permissive kernels. So i thought i'd ask you about that.
And i forgot to ask. The exclamatory symbol on the signal icon ? Why is it coming?? Is it indicating any issue???
Unofficial MultiROM for Galaxy Tab 10.1
MultiROM gives your device the ability to install and boot multiple Android ROMs, or even other Linux based operating systems alongside each other. The primary component of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot.
Features
Multiboot as many Android ROMs as you want
Restore custom recovery backups as secondary ROMs
Dual-boot alternative operating systems (Ubuntu Touch, Firefox OS, Arch Linux) alongside Android, without formatting your device
Install and boot from USB drives connected by OTG cables (on supported devices)
WARNING
This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. While MultiROM no longer messes with the data partition or boot sector, it is possible that something goes wrong and you will have to flash factory images again.
Make backups. Always.
Click to expand...
Click to collapse
https://github.com/Tasssadar/multirom/wiki
Introduction
MultiROM uses a kernel feature called kexec which enables the host ROM to live boot another kernel over the currently running kernel. This allows us to boot into secondary ROMs. The host ROM must be a ROM running a kernel with the kexec-hardboot feature. .
Installation
There are three parts required to install MultiROM.
MultiROM bootloader/injector
- Download the appropriate Multirom installer for you device
Modified TWRP
- Download the appropriate Multirom TWRP for your device
Patched kernel
- You must be using a host ROM a with a kernel that has the kexec-hardboot patch.
Install the Multirom TWRP
(twrp2860_multirom-yyyymmdd-p4xxxx.zip)
Reboot into Multirom recovery
Install the host ROM
Option 1
Install AOSP 5.1.1 or AOSP 6.0
Option 2
Install an Android 4.1 to 4.4 ROM
Download the kexec hardboot kernel for Android 4.1 to 4.4 ROMs
(p4[wifi|tmo]-kernel-*-for-android_4.1-4.4.zip)
Install the kexec hardboot kernel
Install the MultiROM bootloader/injector
(multirom-yyyymmdd-vxx-UNOFFICIAL-p4xxxx.zip)
Adding secondary ROMs
Boot into recovery
Go to Advanced > MultiROM > Add ROM
Select the ROM ZIP file to install
Reboot and select the ROM to boot
Flashing ZIPs to secondary ROMs
Boot into recovery
Go to Advanced > MultiROM > List ROMs
Select a ROM
Go to Flash ZIP
Select a ZIP to flash
Host ROMs with native kexec hardboot support
aosp-5.1.1
aosp-6.0
Questions & Answers and other notes
* What secondary ROMs are supported?
Supported: Android 4.1 (Jellybean) and up
NOT Supported: Android 4.0.4 (Ice Cream Sandwich / ICS) and Android 3 (Honeycomb) * The MultiROM Manager app will not work with this device since it is unofficial port.
* You cannot install Linux/Ubuntu or any other non-Android OSes because none have been ported to this device.
The ROMs that will work are the ones that we already have available for this device.
* Encryption has not been tested and is unlikely to work.
Known Issues:
* Volume keys aren't working in the bootloader (Trampoline).
Change Log
Code:
January 8, 2017
Update TWRP kernel
February 20, 2016
Multrom v33
* Updates for Android 6.0 compatibility
* Boot secondary ROMs faster
Source Code
https://github.com/Decatf
https://github.com/Tasssadar/
kexec-hardboot patch for Galaxy Tab 10.1
Credits
All credits go to the MultiROM authors and the authors of the kexec-hardboot patches.
XDA:DevDB Information
Unofficial MultiROM v33 for Galaxy Tab 10.1, Tool/Utility for the Samsung Galaxy Tab 10.1
Contributors
decatf
Source Code: https://github.com/Decatf
Version Information
Status: Stable
Created 2015-06-21
Last Updated 2017-01-08
Downloads
MultiROM
multirom-20160220-v33-UNOFFICIAL-p4wifi.zip
multirom-20160220-v33-UNOFFICIAL-p4.zip
multirom-20160220-v33-UNOFFICIAL-p4tmo.zip
Modified TWRP
twrp3000_multirom-20160206-p4wifi.zip
twrp3000_multirom-20160207-p4.zip
twrp3000_multirom-20160207-p4tmo.zip
twrp3000_multirom-20160206-p4wifi.tar.md5
twrp3000_multirom-20160207-p4.tar.md5
twrp3000_multirom-20160207-p4tmo.tar.md5
twrp2870_multirom-20150814-p4wifi.zip
twrp2870_multirom-20150814-p4.zip
twrp2870_multirom-20150814-p4tmo.zip
twrp2870_multirom-20150814-p4wifi.tar.md5
twrp2870_multirom-20150814-p4.tar.md5
twrp2870_multirom-20150814-p4tmo.tar.md5
kernel with kexec-hardboot patch
for Android 4.1 to Android 4.4 ROMs
p4wifi-kernel-20160220-for-android_4.1-4.4.zip
p4-kernel-20160220-for-android_4.1-4.4.zip
p4tmo-kernel-20160220-for-android_4.1-4.4.zip
Kernel features:
CPU overclock (1.2Ghz - 1.6Ghz)
CPU voltage control
CPU temperature readings
GPU overclock (400Mhz)
BFQ / FIOPs scheduler
L2 cache optimization
Voodoo Sound
USB Charging
Updated WIFI driver
ZRAM backports
Kernel 3.4 block/writeback backports
kexec-hardboot support
Smoother backlight control
Touch screen pressure level
Note: This kernel can be used with any Android 4.1 to Android 4.4 ROM for this device. i.e. Host ROM / Secondary ROM / Non-MultiROM.
hwcomposer 1.0
p75xx-hwcomposer_1_0.zip
This is a little bonus for all you faithful users. This is a standalone installer of hwcomposer 1.0. This is meant to be used with Android 4.1 - 4.4 ROMs. It will work on any Android 4.1 - 4.4 ROM for this device. It should make the 2D interface smoother.
Do NOT use it on Android 5.x or 6.x. These ROMs are already using a version of this hwcomposer.
Do NOT use it on Android 4.0.4 (ICS) or Android 3 (Honeycomb). hwcomposer 1.0 is not compatible with these versions of Android.
All hail decatf lol.
Question, the secondary ROM doesn't have to have the kesec-hardboot feature right?
eushaun99 said:
All hail decatf lol.
Question, the secondary ROM doesn't have to have the kesec-hardboot feature right?
Click to expand...
Click to collapse
Right. There is nothing extra needed in the secondary ROM.
@decatf why i cant flash multirom, it keep saying error excuting updapte binary. Any idea??
Sent from my SM-N910L using XDA Free mobile app
Same problem - Can't flash multirom-20150620-v32-UNOFFICIAL-p4.zip. , I tried on F2FS and EXT4.
honhan0904 said:
@decatf why i cant flash multirom, it keep saying error excuting updapte binary. Any idea??
Sent from my SM-N910L using XDA Free mobile app
Click to expand...
Click to collapse
vkmaxx said:
Same problem - Can't flash multirom-20150620-v32-UNOFFICIAL-p4.zip. , I tried on F2FS and EXT4.
Click to expand...
Click to collapse
I reuploaded it. It should be fixed now.
I have flash your 5.1 rom
But when i choose android 4.3 the secondary rom it say the internal rom nêd kễc kernel. I thought you have add it to your rom?
Sent from my p4 using XDA Premium HD app
honhan0904 said:
I have flash your 5.1 rom
But when i choose android 4.3 the secondary rom it say the internal rom nêd kễc kernel. I thought you have add it to your rom?
Sent from my p4 using XDA Premium HD app
Click to expand...
Click to collapse
kexec-hardboot wasn't enabled properly on the p4 and p4tmo 20150620 ROM. I've uploaded the standalone kernel installer in the second post.
Install it on your primary ROM and it should be able to boot into secondary ROMs.
Finally i can use both android 5.1 and 4.3 . Thanks alot decatf, you have brough a new life to this tab since android 5.0
Sent from my SM-N910L using XDA Free mobile app
This is awesome! Works great on my p4tmo. I'm using it with two versions of your 5.1 AOSP rom, one without gapps (my daily driver) and one with gapps (secondary; mainly for the social media apps).
A word of warning: If you flash the v2 SELinux enforcing zip on the secondary rom and then boot to it, the OS won't be able to see/access internal storage and a lot of things will crash/force close. If it's running under Permissive mode, things work fine. I'd prefer to be running under Enforcing mode as well on the secondary rom, but I won't complain. Just being able to dual-boot in the first place is fantastic.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Is this forum to be seen as an extension to your aosp thread, where the images keep being updated to support MultiRom and do the discussion here? Or are there any special in-between patches, libraries and so forth only to be found here? I am not entirely sure how to see this thread in relation to your aosp thread.
Pleaseenlighten me, as I am an avid fan and have been using your rom from day 5 (or so).
Sent from my p4wifi using XDA Free mobile app
Just_Another_N00b said:
Is this forum to be seen as an extension to your aosp thread, where the images keep being updated to support MultiRom and do the discussion here? Or are there any special in-between patches, libraries and so forth only to be found here? I am not entirely sure how to see this thread in relation to your aosp thread.
Pleaseenlighten me, as I am an avid fan and have been using your rom from day 5 (or so).
Sent from my p4wifi using XDA Free mobile app
Click to expand...
Click to collapse
This thread for discussing about multirom version. And the other thread is talk about aosp version
Sent from my p4 using XDA Premium HD app
honhan0904 said:
This thread for discussing about multirom version. And the other thread is talk about aosp version
Sent from my p4 using XDA Premium HD app
Click to expand...
Click to collapse
But you have to agree there is quite some overlap, as the latest TWRP and Rom, both supporting MultiRom can be downloaded from the aosp thread. So this thread is really more of an add-on discussing issues and solutions on the MultiRom part of the p4xxxx set-up of what @decatf is doing.
Separate question: is MultiRom also going to be supported or implementable in M?
Sent from my p4wifi using XDA Free mobile app
Just_Another_N00b said:
But you have to agree there is quite some overlap, as the latest TWRP and Rom, both supporting MultiRom can be downloaded from the aosp thread. So this thread is really more of an add-on discussing issues and solutions on the MultiRom part of the p4xxxx set-up of what @decatf is doing.
Separate question: is MultiRom also going to be supported or implementable in M?
Sent from my p4wifi using XDA Free mobile app
Click to expand...
Click to collapse
The recovery in this thread is the custom MultiROM TWRP. It is a recovery that has customizations to support MultiROM. The recovery in the AOSP thread is just regular TWRP. I have also posted the kexec-hardboot kernel in this thread. The third thing required is the MultiROM installer itself. There is nothing special in the primary ROM that is needed for MultiROM.
Want to know if I could run your 5.1.1 rom on here with partition warning from the rom
lilferraro said:
Want to know if I could run your 5.1.1 rom on here with partition warning from the rom
Click to expand...
Click to collapse
Both versions of TWRP use the extra partition. You must install the Multirom TWRP in this thread in order to use Multirom. The normal TWRP does not have Multirom support.
Edit: So, yes the AOSP 5.1.1 ROM will work.
...
Does this allow you to run the original Stock 4.0.4 on a P7510 along side your 5.1.1 ROM? And, if so, does anyone have a flashable copy of the stock?
Thanks
Samsung Galaxy Tab 2
AOSP - Project
This Rom is based on AOSP to give the user a pure AOSP feeling.
The builds only includes device specific changes to compile and get a booting AOSP!
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Downloads:
ROM Downloads for all supported devices can be found here
(Those who have a repartitioned system partition use "not-block-based" builds! Other builds won't be flashable on those devices!)
[#DONATETOME]
FAQ
Q: Will there be any updates?
A: Yes, there will, but only if i can fix a bug or AOSP releases an Update - else there's no update needed.
Q: There's a nice feature in XXX-Rom and i like to have this included - ADD IT!
A: Sorry, i'lll keep this Rom Stock-AOSP as possible. Maybe XXX-Rom is a better choice for you, if you really need this feature.
Q: How to enable root?
A: This Rom doesn't have root included. Why? Because root isn't part of AOSP. You can find the way to SuperSU Thread from @Chainfire and download SuperSU as flashable-ZIP if you need root.
Q: Is it possible to overclock the kernel?
A: Yes and no. First of all you need root and a Kernel-App like KernelAdiutor. After that you can slight OC the CPU & GPU - this Rom includes latest SlimLP Kernel.
Q: I found a bug.
A: Nice finding my friend Please provide needed logs - ADB will be your best friend, if you are replying in a development thread
There's a lot of tutorials out on YouTube or XDA on how to setup and use ADB - it's really simple!
At least you should tell step by step how to reproduce the issue.
I started creating a gerneral FAQ on my github - it includes instructions how to flash a Rom, how to get proper logs, etc. etc. etc., you can find it here
Changelog
Code:
2015-11-08 It's stock AOSP as released by Google (Android 5.1.1 R29 LVY48I), only additions
- screenshot: quick delete action
- advanced reboot menu
- Launcher3 instead Launcher2
- BootMessage: Show each app name being optimized during boot
- Show application's package name in the "App info" screen.
- Open app when clicking on icon in App Info screen
(... forgot about the releases between ...)
2015-08-07 based on Android 5.1.1_r9
XDA:DevDB Information
[P31xx][5.1.1] Samsung Galaxy Tab 2 AOSP-Project, ROM for the Samsung Galaxy Tab 2
Contributors
Android-Andi
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-08-07
Last Updated 2017-04-30
Wow! Andi!
Nice to see that AOSP Lollipop came to us again! Great work dev, @Android-Andi ?
Sent from my GT-P3100 using Tapatalk
Amazing, pure LP AOSP for my tab 2.
I really appreciate it...
Is f2fs in Cache and Data supported in this ROM?
Sent from my GT-P3100 using Tapatalk
Bhaskara Rao said:
Is f2fs in Cache and Data supported in this ROM?
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
No, sry. Think it needs quite more changes than i would like to add... But i will take a closer look next time
Wow, this is awesome. Now I need to see if I can port Layers on top. Thanks Andi!!!
Sent from my Nexus 6 using Tapatalk
Thank you, Andi for the latest AOSP. No issues on clean installation. ROM is fluid. YouTube is not working. Logs attached.
Bhaskara Rao said:
Thank you, Andi for the latest AOSP. No issues on clean installation. ROM is fluid. YouTube is not working. Logs attached.
Click to expand...
Click to collapse
Thanks buddy I'll look into it next week, have some more time then
Clean install of latest AOSP (aosp_p3110-20150807.zip) with Dhollmen 3.0.101 kernel.
Youtube is working, but 720P videos do not work.
ilyichspb said:
Clean install of latest AOSP (aosp_p3110-20150807.zip) with Dhollmen 3.0.101 kernel.
Youtube is working, but 720P videos do not work.
Click to expand...
Click to collapse
Hey bruh @ilyichspb i also want to flash my kernel
I have tried but i softbricked my tab.
So,it will be great if you tell me the steps to flash a kernel.:laugh:
Aosp is smooth and lagfree.great work Andi.:fingers-crossed::good:
AFAIK Dhollmen Kernel doesn't have a fix for emmc bug. Only Android-Andi's ROMs and Recoveries have it. Take an informed decision before flashing custom kernels.
Sent from my GT-P3100 using Tapatalk
[email protected] said:
So,it will be great if you tell me the steps to flash a kernel.:laugh:
Click to expand...
Click to collapse
full wipe
install (via CWM)
AOSP
kernel
gapps
reboot
---------- Post added at 07:41 AM ---------- Previous post was at 07:39 AM ----------
Bhaskara Rao said:
AFAIK Dhollmen Kernel doesn't have a fix for emmc bug. Only Android-Andi's ROMs and Recoveries have it. Take an informed decision before flashing custom kernels.
Click to expand...
Click to collapse
Looks like you are right. I will keep an eye on that. So far everything is working fine.
Seems like google went to nightly builds, r12 source released
Thanks!, will try soon
What is the recommended recovery to install this rom. I'm still running old ketut's stock rom. Thanks
Android-Andi's latest TWRP.
https://www.androidfilehost.com/?w=files&flid=25704
Sent from my GT-P3100 using Tapatalk
Bhaskara Rao said:
Android-Andi's latest TWRP.
https://www.androidfilehost.com/?w=files&flid=25704
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
Whenevr i go to recovery i.e,twrp wipe>advance wipe>change system partition
Twrp says invalid partition select
I have tried this in both android andi's twrp and official twrp
I'm on p3100.
What to do.need help:victory:
I want to flash a rom withf2fs support thats why
[email protected] said:
Whenevr i go to recovery i.e,twrp wipe>advance wipe>change system partition
Twrp says invalid partition select
I have tried this in both android andi's twrp and official twrp
I'm on p3100.
What to do.need help:victory:
I want to flash a rom withf2fs support thats why
Click to expand...
Click to collapse
AOSP doesn't support f2fs.
About f2fs: take my twrp with "f2fs" in it's name. If you have more question about recovery then use the recovery thread pls.
Android-Andi said:
AOSP doesn't support f2fs.
About f2fs: take my twrp with "f2fs" in it's name. If you have more question about recovery then use the recovery thread pls.
Click to expand...
Click to collapse
Sorry! I got the sol of my problem
i didnt select cache and data before tapping on change partition
One question
Does Your latest recovery i,e. 2.8.7.1 supports f2fs.
i want to post this in recovery thread but xda said that u have less than 10 posts
RECOVERY
TWRP & CM-Recovery
Z00A/Z008 ( LP Bootloader)
Just as the title says these are unofficial recovery builds for Asus Zenfone 2 Z00A and Z008 models
These have been tested and confirmed functional. These are built from current CM devices trees, CM kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 2.8.7.3 (LP based)
TWRP 2.8.7.7 (M based)
CM-Recovery 9-28-15 (LP based)
CM-Recovery 12-22-15 (M based)
{ Cm-Recovery doesn't use "version" tags so using build date as a version # }
SOURCES
Recovery built in a CM-12.1/13.0 environment respectively using device trees/kernel
from our CM device trees/kernel CM-zenfone2 github
Z00A LP Tree HERE
Z008 LP Tree HERE
Z00A M Tree HERE
Z008 M Tree HERE
Kernel Source
CM-Recovery source from CM-recovery
TWRP source tyipically from Omnirom
HOWEVER 2.8.7.6 beta uses modified TWRP source from omnirom (and patched from thier gerrit) from
HERE
Code:
Changelog:
1-22-16:
TWRP 2.8.7.7
- fixed OTG & external SDCARD mount
- from TWRP: language support, code cleanup and minor fixes(see twrp github for full list)
- this is pre-release testing main ly for soon to be released TWRP 3.0
12-22-15:
* updated builds
* should fix backups in TWRP
* should fix issues flashing newer ROMS after 12-17-15
12-7-15
* 2.8.7.5 TWRP builds
* fixed opengapps flashing
12-6-15
* split into new thread
* Marshmallow based recoveries now live
* TWRP is WIP prior to next major official tag, new theme included for testing
Z00A/Z008 ( MM Bootloader)
Just as the title says these are unofficial recovery builds for Asus Zenfone 2 Z00A and Z008 models
These have been tested and confirmed functional. These are built from current CM devices trees, CM kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 3.0.2-M1 (MM based)
SOURCES
Recovery built in a Omnirom-6.0 environment respectively using device trees/kernel below
Z00A/Z008 MM Tree HERE
Kernel Source HERE
TWRP source tyipically from Omnirom
Code:
Changelog:
Initial source built MM bootloader friendly based recovery release
Z00D
Just as the title says these are unnoficial recovery builds for the Asus Zenfone 2 Z00D (ze500cl) model
These have been tested and confirmed functional. These are built from experimental devices trees, modified Stock kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 3.0.2-0
SOURCES
Recovery built in a omnirom environment respectively using device trees/kernel
from our my github
Device Tree
Kernel Source
Code:
Changelog:
5-3-16: Initial TWRP build
XDA:DevDB Information
Zenfone2 Recovery, Tool/Utility for the Asus ZenFone 2
Contributors
jrior001, crpalmer
Source Code: https://github.com/CM-zenfone2
Version Information
Status: Beta
Beta Release Date: 2015-12-06
Created 2015-12-07
Last Updated 2016-08-03
Niceeeeeeeeeeeeeeeee
Well this was unexpected, thank you so much for this!
Edit: Well I tried the MM version, and I must say I love the new look! It's kinda laggy, but that's very expected and I got a recovery log.
Aceofzeroz said:
It's kinda laggy, but that's very expected and I got a recovery log.
Click to expand...
Click to collapse
TWRP still uses some really old code for pixelflinger. We have been using a JB era patch from Intel to add x86 optimized acceleration, which Dees_Troy(TWRP dev) and the zenfone5/6 devs ported to KK & LP. I updated it for M, but this is about as good as it gets until TWRP overhauls that section of their code. Without this patch is basically unusable.
And yes the new theme is sexy It's months in the making from TWRP contributer @z31s1g and it's quite lovely.
jrior001 said:
TWRP still uses some really old code for pixelflinger. We have been using a JB era patch from Intel to add x86 optimized acceleration, which Dees_Troy(TWRP dev) and the zenfone5/6 devs ported to KK & LP. I updated it for M, but this is about as good as it gets until TWRP overhauls that section of their code. Without this patch is basically unusable.
And yes the new theme is sexy It's months in the making from TWRP contributer @z31s1g and it's quite lovely.
Click to expand...
Click to collapse
Ah, I understand the situation now and glad that the patch worked out for the time being. Definitely better than not having the latest TWRP to play with, so my highest gratitude for the amazing work bringing up Marshmallow in time for the holidays! :thumbup:
Sent from the Ace's MB865 using Tapatalk
This is a bit wonky with device encryption. It'll boot the recovery without a theme loaded and ask for my pattern (as expected). I'll put that in and it'll decrypt and mount storage, then the "put in your pattern" prompt comes up again (this time, with my twrp theme loaded). I can cancel that prompt just fine and it'll sit on the main screen and I can proceed from there, so it's not a showstopper at least.
This didn't happen on 2.8.7.3.
edit: on flashing opengapps 6.0 micro, I'm warned that the recovery is missing the xz binary and can't flash the zip (and told me to update to the latest recovery for my device, lol). I'll upload the generated log shortly.
edit edit:
Code:
# Begin Open GApps Install Log
-----------------------------------------------------------------------------
ROM Android Version | 6.0
-----------------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: The installer detected that your recovery does not support
XZ decompression. Please update your recovery or switch to another one like TWRP.
# Begin User's gapps-config
# End User's gapps-config
Fortunately, flashing my L-gapps seems to have worked fine (...seeeeeems to. I'll see if it works. The setup app did at least update itself, so there's that.)
Is there an easy way to update my TWRP? Any apps that can do this for me?
roach9 said:
Is there an easy way to update my TWRP? Any apps that can do this for me?
Click to expand...
Click to collapse
I know Flashify can do that in many devices, I am not sure about ours, I think best way would be to flash it using fastboot.
Marshmallow recovery can be used to flash lollipop Rom...??..and vice versa...??
Any difference for 2.8.7.4 vs .3 other than the look? Googled it and found nothing.
Sayan44 said:
I know Flashify can do that in many devices, I am not sure about ours, I think best way would be to flash it using fastboot.
Click to expand...
Click to collapse
Why not via TWRP itself? TWRP has a feature to flash an .img directly to boot or recovery.
Sent from my ASUS_Z00AD
I am on 2.8.7.3. I am thinking to flash cm13. Is it necessary to update twrp? Or I can flash cm13 using my old one?
Sent from my ASUS_Z00A using Tapatalk
rex_perfect said:
Marshmallow recovery can be used to flash lollipop Rom...??..and vice versa...??
Click to expand...
Click to collapse
Pretty much, LP version is stable and works for flashing M ROMs.
Sent from my ASUS_Z00A using Tapatalk
espeon said:
This is a bit wonky with device encryption. It'll boot the recovery without a theme loaded and ask for my pattern (as expected). I'll put that in and it'll decrypt and mount storage, then the "put in your pattern" prompt comes up again (this time, with my twrp theme loaded). I can cancel that prompt just fine and it'll sit on the main screen and I can proceed from there, so it's not a showstopper at least.
This didn't happen on 2.8.7.3.
edit: on flashing opengapps 6.0 micro, I'm warned that the recovery is missing the xz binary and can't flash the zip (and told me to update to the latest recovery for my device, lol). I'll upload the generated log shortly.
edit edit:
Code:
# Begin Open GApps Install Log
-----------------------------------------------------------------------------
ROM Android Version | 6.0
-----------------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: The installer detected that your recovery does not support
XZ decompression. Please update your recovery or switch to another one like TWRP.
# Begin User's gapps-config
# End User's gapps-config
Fortunately, flashing my L-gapps seems to have worked fine (...seeeeeems to. I'll see if it works. The setup app did at least update itself, so there's that.)
Click to expand...
Click to collapse
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
So what's the difference of this TWRP and TheSSJ TWRP?
jrior001 said:
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
The 2nd one happened after I decrypted; I forgot to mention that. I don't think it actually happened when I was encrypted using the L-based recovery (I upgraded my recovery, then decrypted, then tried flashing the rom + gapps)
Thread moved to proper forum
jrior001 said:
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Having the same issue actually, not encrypted, worked on .3 no pin or lock on screen either. Happened trying to install the latest Gapps package.
Heavybullets said:
Having the same issue actually, not encrypted, worked on .3 no pin or lock on screen either. Happened trying to install the latest Gapps package.
Click to expand...
Click to collapse
ended up fastboot installing the recovory, didnt work, factory reset, then try it, didn't work, fixing permissions, all that, nothing has worked for me, the latest .4 twrp still comes up with that "The installer detected that your recovery does not support
XZ decompression." Error.
Heavybullets said:
ended up fastboot installing the recovory, didnt work, factory reset, then try it, didn't work, fixing permissions, all that, nothing has worked for me, the latest .4 twrp still comes up with that "The installer detected that your recovery does not support
XZ decompression." Error.
Click to expand...
Click to collapse
well yeah when you have a missing binary reflashing it probably isn't going to do anything, assuming it didn't get corrupted