Database Users

[Q] Plasma Active ROM installation error

Hi Everybody!
I have a Nexus 7, I managed to install Ubuntu Touch on the device through Multirom (v9). I would like to install Plasma Active too, but unfortunatelly I got an error, it says that "Your Multirom version too low for this zip file or unable to find multirom binary". I also attached a picture from the error message.
If somebody knows what should I do, please answer!
Thanks!

NokiaN9 said:
Hi Everybody!
I have a Nexus 7, I managed to install Ubuntu Touch on the device through Multirom (v9). I would like to install Plasma Active too, but unfortunatelly I got an error, it says that "Your Multirom version too low for this zip file or unable to find multirom binary". I also attached a picture from the error message.
If somebody knows what should I do, please answer!
Thanks!
Click to expand...
Click to collapse
I get exactly the same error. I've updated to the last Multirom, recovery and the same.... I'm installing the old Plasma...

rperezan said:
I get exactly the same error. I've updated to the last Multirom, recovery and the same.... I'm installing the old Plasma...
Click to expand...
Click to collapse
Thanks! Which version did you manage to install?

Hey guys,
I am experiencing the exact same problems trying to install the Plasma Active ROM using the ZIP file. I am having the same problem with the older version from here: http://forum.xda-developers.com/showpost.php?p=36573053&postcount=2
I've also followed these very clear steps here: http://forum.xda-developers.com/showpost.php?p=38686669&postcount=153 but still no luck.
I'm on MultiRom v9 and TWRP v2.4.4.0, bootloader 4.18.
I am also not sure of what the cause is of the zipped Plasma Active ROM not installing from TWRP?
Hope anyone can help!
Cheers!
NeverMind

Lol, in case of PA, Tizen, WebOS you dont have to go to the Multirom menu and add ROM, you only have to install zip from TWRP menu! This is the solution!

Hi!
Thanks for the info!
So in TWRP, not from the multirom menu, but from the main menu.
And then it will still be added to the current boot options in the multirom menu at boot? (and you won't lose the other boot options??)
Cheers!
NeverMind

_never_mind_ said:
Hi!
Thanks for the info!
So in TWRP, not from the multirom menu, but from the main menu.
And then it will still be added to the current boot options in the multirom menu at boot? (and you won't lose the other boot options??)
Cheers!
NeverMind
Click to expand...
Click to collapse
Hi! Yes, off course, it works and it will be added in the ROM-list! I managed to install it this way on my N7. Also Tizen and WebOS works this way!

NokiaN9 said:
Lol, in case of PA, Tizen, WebOS you dont have to go to the Multirom menu and add ROM, you only have to install zip from TWRP menu! This is the solution!
Click to expand...
Click to collapse
Right Thank you!

Thanks! Indeed it worked

[RELEASE] Multi Recovery Flasher

im just letting the S3 users know that i have now got an s3 and will begin developing for s3 now!
starting with my first creation for the s3, i have made a flashable .zip file that flashes the selected recovery, so no need for re-downloading and re-flashing, simply flash the .zip, then aroma will open asking whitch recovery to flash then it will flash then reboot into the new recovery!
coming soon!

ricky310711 said:
im just letting the S3 users know that i have now got an s3 and will begin developing for s3 now!
starting with my first creation for the s3, i have made a flashable .zip file that flashes the selected recovery, so no need for re-downloading and re-flashing, simply flash the .zip, then aroma will open asking whitch recovery to flash then it will flash then reboot into the new recovery!
coming soon!
Click to expand...
Click to collapse
Looking forward, it will be useful, any information about the development state?

mirroalex said:
Looking forward will be useful, any information about the development state?
Click to expand...
Click to collapse
i actually just amde the packages and tested each of them, all ive gotta do is configure aroma and we will be up and running by tommorow arvo!

will it automatically download the newest version of the selected recovery?

chrismast said:
will it automatically download the newest version of the selected recovery?
Click to expand...
Click to collapse
Its a flashable .zip package, I will just gather the latest recoveries and update every month

ricky310711 said:
Its a flashable .zip package, I will just gather the latest recoveries and update every month
Click to expand...
Click to collapse
ok, good luck with it!
personally I do not see the point yet as I just can download the single recovery (there is anyway not that much choice) and flash it but I am sure there are users that will appreciate an Aroma installer.

chrismast said:
ok, good luck with it!
personally I do not see the point yet as I just can download the single recovery (there is anyway not that much choice) and flash it but I am sure there are users that will appreciate an Aroma installer.
Click to expand...
Click to collapse
The point of this being that some recoveries cant flash certain .zip files... eg twrp 2.5.0.0 cannot flash .zip files with aroma, this is also a pachage to help developers!

ricky310711 said:
The point of this being that some recoveries cant flash certain .zip files... eg twrp 2.5.0.0 cannot flash .zip files with aroma, this is also a pachage to help developers!
Click to expand...
Click to collapse
ah ok, didn't know that, anyway as I said for certain people surly helpful! Good luck!

An app that could connect to a central repository and download the latest versions would be great. Then using the same method stweaks by siyah uses to "hijack" recovery or temp boot would make more sense to me.
That way you open app, choose recovery to boot and flash your zips. Then boot back to android...
Rather than boot recovery, flash zip,,choose recovery, flash zip...
Or just use philz recovery and be able to flash all zips anyway
Sent from my GT-I9300 using Tapatalk 2

rootSU said:
An app that could connect to a central repository and download the latest versions would be great. Then using the same method stweaks by siyah uses to "hijack" recovery or temp boot would make more sense to me.
That way you open app, choose recovery to boot and flash your zips. Then boot back to android...
Rather than boot recovery, flash zip,,choose recovery, flash zip...
Or just use philz recovery and be able to flash all zips anyway
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Seems legit, although I do not have time to make a . Apk of it..
Also keep in mibd what if you didnt have data connection, or yet couldnt even boot...

[OTA][TWRP]cm-12.0-YNG1TAS0YL update TWRP flashable [ZIP]

I made a Twrp flashable zip for the CM12S OTA update
My initial warning was a
WARNINGS
This update is intended to be used to update from CM11S-XNPH05Q to CM-12.0-YNG1TAS0YL,
Users have reported it working via other dirty flashes, so do so at your own risk.
HOWEVER I AM NOT RESPONSIBLE FOR BRICKS OR YOUR OWN STUPIDITY
THIS IS YOUR ONLY WARNING
DOWLOAD HERE
Installation process (this will keep root, and keep twrp installed. if not just flashing the zip will reflash CM recovery each boot)
1) Download the OTA zip above and the latest SuperSU.zip (here)
2) put both files on your internal storage
3) Reboot into TWRP
4) flash the modified OTA and wipe the caches
5) Flash SuperSU.zip
6) reboot
Credits
@James1o1o with out him i wouldn't have the OTA zip
-iCatalystic (Reddit user who posted the megalink that James1o1o reposted)
@Harfainx for the method for making this twrp flashable
@Chainfire for SuperSU

Reserved for OP

Huzzah! Awesome, homie. Thanks for the link

Will this wipe the device?

IDK what the big deal is. I downloaded and flashed this one; http://forum.xda-developers.com/showpost.php?p=60095886&postcount=13
I was on OxygenOS
wipe and flash with TWRP
running perfect

spicediablo said:
Will this wipe the device?
Click to expand...
Click to collapse
nope, didn't when I flashed it

I heard people saying it would flash over CM11 nightlies and I didn't believe it. Just for grins, I backed up my CM12 nightlies, wiped cache/dalvik-art and gave it a whirl. So far no problems, but later in the day I'm going to do a clean install.

gcng said:
IDK what the big deal is. I downloaded and flashed this one; http://forum.xda-developers.com/showpost.php?p=60095886&postcount=13
I was on OxygenOS
wipe and flash with TWRP
running perfect
Click to expand...
Click to collapse
this has the assert lines removed from the updater script, you needed to remove them before on cm11.
Apparently not now, the warnings are because since this has a radio.img and other stuff you can brick your device.

Does this also flash modem etc.?

furrycurry said:
Does this also flash modem etc.?
Click to expand...
Click to collapse
yes, this is the OTA update that was pulled, just has a few lines removed from the updater-script

really?
working with multirom as secondary.

thoughtlesskyle said:
Credits
@James1o1o with out him i wouldn't have the OTA zip
Click to expand...
Click to collapse
FYI, James just copied the link from here:
http://www.reddit.com/r/oneplus/comments/32iby5/so_it_begins/
I'm glad he reposted it, but this guy deserves the credit for uploading it to Mega. :good:

CafeKampuchia said:
FYI, James just copied the link from here:
http://www.reddit.com/r/oneplus/comments/32iby5/so_it_begins/
I'm glad he reposted it, but this guy deserves the credit for uploading it to Mega. :good:
Click to expand...
Click to collapse
putting that in the OP now
Edit it's there, didn't know where it came from didn't mean to miss credit.

Hey, whats the difference its having from the one that is other post? There peoples are simply flashing from CM12 nightlies.

So after flashing it with Philz Recovery with the result "t", my Android just doesn't boot up anymore. The boot animation animates for an infinite time. What now?
Edit: Well, I held the power button until it was off, restarted and now it's working. It's magic. [place parrot here]

shaheen7m said:
Hey, whats the difference its having from the one that is other post? There peoples are simply flashing from CM12 nightlies.
Click to expand...
Click to collapse
You can try it at your own risk, there is a small updater script change that allows twrp to flash it. It does flash a radio which can be dangerous. If it's working for them then this should in Theory work, try it at your own risk and let us know if it works

thoughtlesskyle said:
You can try it at your own risk, there is a small updater script change that allows twrp to flash it. It does flash a radio which can be dangerous. If it's working for them then this should in Theory work, try it at your own risk and let us know if it works
Click to expand...
Click to collapse
One guy in the other thread already bricked his device trying to flash from Oxygen People flashing from CM11s & CM11/12 nightlies seem to be doing ok except for the occasional FC, probably from not clearing cache/dalvik.

CafeKampuchia said:
One guy in the other thread already bricked his device trying to flash from Oxygen
Click to expand...
Click to collapse
I bricked mine last week going from cm12 back to 11S, luckily I was able to get it up and running by flashing colorOS via their flashtool and then reflashing cm11S again.
These are reasons why I am stressing this so much. I had it happen, it sucks but I got my device back

thoughtlesskyle said:
I bricked mine last week going from cm12 back to 11S, luckily I was able to get it up and running by flashing colorOS via their flashtool and then reflashing cm11S again.
These are reasons why I am stressing this so much. I had it happen, it sucks but I got my device back
Click to expand...
Click to collapse
Totally agree. I like your huge disclaimer on the OP :good:

CafeKampuchia said:
Totally agree. I like your huge disclaimer on the OP :good:
Click to expand...
Click to collapse
Been doing this too long to be vague about that kind of stuff, if it was just system and boot img I'd tell you to flash it however you want because there isn't a ton of things that those can mess up

ROOT Nexus 6 - Android M Dev Preview

Hey everyone!
Since the release of the Android M Preview I have been trying to figure out a way to root my device. In almost every case I found myself in a boot loop or validation error after modifying the system partition. After a day or so I finally found the following combination to root Android M on the Nexus 6. I wanted to put this in an easy to find format for anyone wanting root.
Update: Here are a few things I want to point out based on trending replies thus far:
Please not that this boot image sets SE Linux to Permissive rather than enforcing. If you care about this sort of thing, don't flash it.
Before you say "this doesn't work on my favorite CrapROM, CM, OmniROM, etc. please remember it wasn't designed to. This was designed and tested exclusively with the M Dev Preview.
I am not responsible for any damage to your devices, etc. If you get a boot loop you can get back to booting by simply flashing the stock "M" system image via fastboot.
Dev Preview 1:
Download the Elite Kernel from here: http://projectelite.net/buck/shamu/M/Elite_Shamu_M-05_31_2015.zip
Download and the SuperSU flashable zip package. In this case you'll want the 2.49 package. - http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Put both flashable zips on your /sdcard/.
Download fix_rw_boot.img from here: http://downloads.codefi.re/networkingpro/fix_rw_boot.img
Reboot to bootloader mode.
Flash fix_rw_boot.img to the boot partition using fastboot. (fastboot flash boot fix_rw_boot.img)
Reboot phone normally and allow the phone to attempt to boot (you will see the boot animation but it will never boot completely).
Wait for two minutes then reboot into TWRP recovery. You can use physical buttons or adb reboot recovery.
Once rebooted into TWRP flash the Elite Kernel then the SuperSU package.
Reboot - Note that the validation check is gone at this point.
Profit
Update: See second post for a flashable Busybox .zip for the Android M Preview.
*** If you have already installed a different Kernel you can still keep it. To unlock system R/W simply download and flash the included fix_rw_boot.img, reboot, wait 2 minutes, reboot to TWRP and flash original boot image again via recovery.
Dev Preview 2:
It has been brought to my attention that the second Dev Preview does not work like the first. I personally have not had time to test or use it, but @abogrhen sent me the following directions, and requested I update the OP. All links are included and all credit to abogrhen. Here goes:
1. Download no encrypt img
2. Install the M Preview 2 normally, but replace the boot img with no encrypt img (you can use NRT )
3. After the phone boots normally do a factory reset (if the storage space is lower than normal) if not skip this step.
4. After booting normally enable USB debugging then flash the latest TWRP.
4. Boot into TWRP and flash the latest Elemental X (others may work ), SuperSU , and Busybox (in that exact order).
5. You now have a rooted M2 with no encryption.
http://projectelite.net/buck/shamu/insecure_noencrypt_boot.img
https://www.androidfilehost.com/?fid=24052804347786093
https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
http://downloads.codefi.re/networkingpro/BusyBox-Android_M.zip
Credits:
@abogrhen - Tutorial for Dev Preview 2
Kernel - Elite Kernels - buckmarble
SuperSU - Chainfire
Root Verification - Root Checker Pro - Joey Krim - https://play.google.com/store/apps/details?id=com.joeykrim.rootcheckp&hl=en
Enjoy everyone!
NetworkingPro
Try to learn something about everything and everything about something.
NetworkingPro | TEAM CODEFIRE

Busy Box and Ad Away
Update: Install Ad Away v 3.0 and Busy Box on Android M.
Busy Box - http://downloads.codefi.re/networkingpro/BusyBox-Android_M.zip - This is a flashable zip I made to install Busybox on Android M. Flash in TWRP. This zip also creates all Simlinks.
Ad Away v 3.0 - Verified to work on Android M - http://downloads.codefi.re/networkingpro/AdAway_v3.0.apk
Note: This version of Busy Box is NOT the same as most Busy Box installers on the play store. Never versions of Android, including Android M, require that Busybox be compiled using (PIE) Position Independent Executable support. This version has been compiled specifically for that on the ARM architecture.
Enjoy, and let me know if you have any issues!

NetworkingPro said:
Update: Install Ad Away v 3.0 and Busy Box on Android M.
Busy Box - http://downloads.codefi.re/networkingpro/BusyBox-Android_M.zip - This is a flashable zip I made to install Busybox on Android M. Flash in TWRP. This zip also creates all Simlinks.
Ad Away v 3.0 - Verified to work on Android M - http://downloads.codefi.re/networkingpro/AdAway_v3.0.apk
Note: This version of Busy Box is NOT the same as most Busy Box installers on the play store. Never versions of Android, including Android M, require that Busybox be compiled using (PIE) Position Independent Executable support. This version has been compiled specifically for that on the ARM architecture.
Enjoy, and let me know if you have any issues!
Click to expand...
Click to collapse
thanks for posting this,
btw, your bb and aa links are 403.

bweN diorD said:
thanks for posting this,
btw, your bb and aa links are 403.
Click to expand...
Click to collapse
Thanks for the info! Mind giving it a try now? Had to CHMOD magic.

NetworkingPro said:
Thanks for the info! Mind giving it a try now? Had to CHMOD magic.
Click to expand...
Click to collapse
yep, good now
thanks

This doesn't seem to work with MultiROM.

But this kernel change the selinux to permissive or disabled, right?
I don't like this, I will wait root for enforcing selinux.

Does anyone know how to fix device failed verification message at the start of boot process ?

At first, I reflashed android M again after getting that nasty error. Though, your phone will still boot. However, I got rid of it when I went back to 5.1.1.
Sent from my Nexus 6 using XDA Free mobile app

arregull said:
At first, I reflashed android M again after getting that nasty error. Though, your phone will still boot. However, I got rid of it when I went back to 5.1.1.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Tried reflashing M, but its still there.
So you are not on M in the end? I want to keep M for now.

jodvova said:
Does anyone know how to fix device failed verification message at the start of boot process ?
Click to expand...
Click to collapse
Install stock recovery, do a full wipe with it, and don't install TWRP for the moment or the message appears again.

Well, I got root and I am so grateful for that. Ad away will not apply hosts however and that was the biggest reason for rooting! Any ideas?
Update, AdBlockPlus is working. BBS and Gsam Root Companion are no go, seems like the priv-app folder is still locked despite root. Tried Root Explorer and get an error. Greenify is working! Thanks so much @NetworkingPro

brando56894 said:
This doesn't seem to work with MultiROM.
Click to expand...
Click to collapse
What doesn't? There are three things here. Theres a boot image compiled for Android M, an ad blocker and a custom Busybox installer, also compiled for Android M.

jodvova said:
Does anyone know how to fix device failed verification message at the start of boot process ?
Click to expand...
Click to collapse
Did you flash this kernel? Flashing the included boot image should get rid of the failed verification message.

jason1332 said:
Well, I got root and I am so grateful for that. Ad away will not apply hosts however and that was the biggest reason for rooting! Any ideas?
Update, AdBlockPlus is working. BBS and Gsam Root Companion are no go, seems like the priv-app folder is still locked despite root. Tried Root Explorer and get an error. Greenify is working! Thanks so much @NetworkingPro
Click to expand...
Click to collapse
You're welcome. It may very well be hit and miss for some apps. Thanks for the feedback. Glad to hear its all working for you so far.

Any chance you could explain what you did to the ram disc to get this working.Trying to make it work nexus 5
http://forum.xda-developers.com/showthread.php?t=3123469
Rooting android dev preview
Sent from my Nexus 5 using XDA Free mobile app

a g bell said:
Any chance you could explain what you did to the ram disc to get this working.Trying to make it work nexus 5
http://forum.xda-developers.com/showthread.php?t=3123469
Rooting android dev preview
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It was done in source, not the ramdisk.

adrynalyne said:
It was done in source, not the ramdisk.
Click to expand...
Click to collapse
OK so what was done in source to make it work?there is an L kernel that boots on nexus 5 but flashing su gives no boot past ani.
Sent from my Nexus 5 using XDA Free mobile app

a g bell said:
OK so what was done in source to make it work?there is an L kernel that boots on nexus 5 but flashing su gives no boot past ani.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
https://github.com/DespairFactor/N6-Preview

Does this enforce encryption?

TWRP Recovery For Oneplus X

From the official Chinese support forum.
Credit goes to counter-stike
/Support flash and update of official rom.
/Support MTP
/Support disabling offical recovery
/Supported Models: E100X (All regional model, Onyx or Ceramic)
Must unlock bootloader and install proper ADB driver before flash.
Now enjoy root and custom rom!
Download Link (English Version)

Resolved!

Here is the english version repacked by me
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
md5sum - 164519c4a50ea5e9c1244cd7aedf2c74

What is system image?
When I open the backup menu I get an option I've never seen before in other phones called "system image".
Could someone please explain to me what it contains? And is there a need to back this up?

How to flash ?

hey guys, just got my OnePlus X White version. it comes with H2OS and i wanna flash it to OxygenOS. I can't seem to get it working tho. any help please?

Sherwinnn said:
hey guys, just got my OnePlus X White version. it comes with H2OS and i wanna flash it to OxygenOS. I can't seem to get it working tho. any help please?
Click to expand...
Click to collapse
Simon posted a link with instructions here: http://forum.xda-developers.com/showpost.php?p=63718460&postcount=3

Savya said:
Beware! This Recovery is also in Chinese so its impossible to use for most of us. Maybe mention that too?
Click to expand...
Click to collapse
sorry for the inconvenience, updated the link to English version.

can someone dump system.img and boot.img?

Sherwinnn said:
hey guys, just got my OnePlus X White version. it comes with H2OS and i wanna flash it to OxygenOS. I can't seem to get it working tho. any help please?
Click to expand...
Click to collapse
1. Taking threads off-topic is against forum rules. This thread is about TWRP recovery.
2. Double posting is against forum rules.
http://forum.xda-developers.com/oneplus-x/help/h2os-to-oxygenos-t3243838

Can someone confirm this as working?
Should i rather wait for official twrp?
I have had old phones quite a while now and being a bit causious because i usually don´t spend 300€ to a phone.

Fatsodonkey said:
Can someone confirm this as working?
Should i rather wait for official twrp?
I have had old phones quite a while now and being a bit causious because i usually don´t spend 300€ to a phone.
Click to expand...
Click to collapse
Take a look in the rooting thread.

Mirror links:
Original TWRP by @qwsdert4 -- MIRROR
English repacked by @ukanth -- MIRROR

ckret said:
can someone dump system.img and boot.img?
Click to expand...
Click to collapse
Found OTA (looks like full) from some tutorial which has boot.img and full system dump
http://pan.baidu.com/s/1hq98Uoc

hey, so i just flashed this TWRP recovery and i managed to boot into TWRP recovery. But, whenever i click the 'Reboot' option or 'Power Off' option, the TWRP just stays right there and it won't even reboot or power off. I have to hold down the power button to turn off the phone and power it back. Any ideas why this is happening and anything that i've done wrong in the process?

Sherwinnn said:
hey, so i just flashed this TWRP recovery and i managed to boot into TWRP recovery. But, whenever i click the 'Reboot' option or 'Power Off' option, the TWRP just stays right there and it won't even reboot or power off. I have to hold down the power button to turn off the phone and power it back. Any ideas why this is happening and anything that i've done wrong in the process?
Click to expand...
Click to collapse
Its a Bug, i guess same is happening with everyone. We just have to wait for official TWRP. and also
Bug Till NoW
Extra Option Named System partition Under Backup, Which has no Function and Doesn't Work.
Cant reboot/power off from recovery as it just freezes the recovery.
OTG doesn't work in Recovery.
TWRP gets replaced with Stock recovery after each Boot.

N_lover27 said:
Its a Bug, i guess same is happening with everyone. We just have to wait for official TWRP. and also
Bug Till NoW
Extra Option Named System partition Under Backup, Which has no Function and Doesn't Work.
Cant reboot/power off from recovery as it just freezes the recovery.
OTG doesn't work in Recovery.
TWRP gets replaced with Stock recovery after each Boot.
Click to expand...
Click to collapse
can you dump boot.img for me?
just make a backup with twrp if its working
this way we can build a working twrp version

ckret said:
can you dump boot.img for me?
just make a backup with twrp if its working
this way we can build a working twrp version
Click to expand...
Click to collapse
here u go

N_lover27 said:
here u go
Click to expand...
Click to collapse
thanks.
its weird though.. when i unpack the boot.img it misses some files...

ckret said:
thanks.
its weird though.. when i unpack the boot.img it misses some files...
Click to expand...
Click to collapse
try this one mate..