Related
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
Hi everyone!
I installed a few days ago OmniROM on my freshly unlocked Nexus 4, with Franco's kernel and I really like it! I love that there are updates everyday!
But I never succeeded to perform it with built-in OTA updater. So I always flashed it as usual, and it works. But downloading the entire file everyday is boring.
So, when I start the installation via the built-in OTA updater, it reboots the phone into recovery (I use ClockworkMod Recovery v6.0.4.3), and then it says that it failed the installation. There are no problem after that, I just reboot normally. It actually says:
"Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher. /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue".
I attached to the thread the log quoted in the error message.
So am I doing something wrong? I don't have the premium option of ROM Manager, and I saw there is an OTA option in the app. Does it mess with the built-in OTA updater?
Thanks in advance!
OTA updater won't work on CWM as it doesn't have "openrecoveryscript"
TWRP has this and works with no issues
Okay, thanks.
For installing it, as I now have CWM, is it possible to install TWRP from their Android app and erase CWM?
Tiwenty said:
Okay, thanks.
For installing it, as I now have CWM, is it possible to install TWRP from their Android app and erase CWM?
Click to expand...
Click to collapse
Install GooManager and flash TWRP from it.
I think we're going to have to add some sort of message to the updater indicating that it won't work with any official CWM release (anything compiled with I_AM_KOUSH set) - These CWM releases block anything but ROM Manager from using the extendedcommands interface.
Philz Touch CWM works fine with OTA
mithun46 said:
OTA updater won't work on CWM as it doesn't have "openrecoveryscript"
TWRP has this and works with no issues
Click to expand...
Click to collapse
I'm using the Philz Touch CWM and OTA is working fine, in fact everything seems to be working just fine.
http://forum.xda-developers.com/showthread.php?t=2552673
This is on a T-Mobile Galaxy Note 2.:good:
Okay, thanks everyone. I flashed TWRP and I am now waiting for an OTA to test this!
PhilZ has openrecoveryscript support
Okay, so the OTA worked. Thanks you guys!
A question, is it normal that SuperSU is removed each time I upgrade?
Entropy512 said:
I think we're going to have to add some sort of message to the updater indicating that it won't work with any official CWM release (anything compiled with I_AM_KOUSH set) - These CWM releases block anything but ROM Manager from using the extendedcommands interface.
Click to expand...
Click to collapse
It's on my todo list ...
Tiwenty said:
Okay, so the OTA worked. Thanks you guys!
A question, is it normal that SuperSU is removed each time I upgrade?
Click to expand...
Click to collapse
If you don't install the backup script from the SuperSU settings menu - yes for the time being.
Okay, I installed the backup script for SuperSU. It now stays when I upgrade.
But each time I upgrade, when I return from recovery, it optimizes all of my apps. It takes around 15 minutes. Maybe it is because I use ARC, if I go back to Dalvik will it stop?
Tiwenty said:
Okay, I installed the backup script for SuperSU. It now stays when I upgrade.
But each time I upgrade, when I return from recovery, it optimizes all of my apps. It takes around 15 minutes. Maybe it is because I use ARC, if I go back to Dalvik will it stop?
Click to expand...
Click to collapse
This is standard - usually happens any time the frameworks get touched. Shouldn't be taking 15 minutes though...
Oh wait, you're using ART, that's probably it. ART is notorious for VERY long bootup optimization times.
Hi all, I have 3 S5 models with the same problem (M, F and FD) and I have been running cm nightlies in these devices, but I am unable to update the rom by clicking update now after the download, the device will just boot to the recovery and I have to manually pick the right file, sometimes it just work (at random) but most of the time I have to pick the file, my guess is that I have the wrong recovery, I tried Philz and I am now running TWRP, which do you recommend?
TWRP should be able to automatically install ROM updates. Also Questions don't go in the General section
serdasteclas said:
Hi all, I have 3 S5 models with the same problem (M, F and FD) and I have been running cm nightlies in these devices, but I am unable to update the rom by clicking update now after the download, the device will just boot to the recovery and I have to manually pick the right file, sometimes it just work (at random) but most of the time I have to pick the file, my guess is that I have the wrong recovery, I tried Philz and I am now running TWRP, which do you recommend?
Click to expand...
Click to collapse
you could try deelting the old updates, if it only has one file to pick from and it picks it everytime theres ur problem
aliyangohar4 said:
TWRP should be able to automatically install ROM updates. Also Questions don't go in the General section
Click to expand...
Click to collapse
TWRP should be able to automatically install ROM updates. Also Questions don't go in the General section
Click to expand...
Click to collapse
Sorry, I'll move this as soon as I find out how, maybe my problem is the version.
-PiLoT- said:
you could try deelting the old updates, if it only has one file to pick from and it picks it everytime theres ur problem
Click to expand...
Click to collapse
Even if I delete all the other files it doesn't reboot and installs automatically as it should
Is it working now?
aliyangohar4 said:
Is it working now?
Click to expand...
Click to collapse
I installed TWRP manager and updated TWRP to 2.8.6.0 but the problem persist, when I am installing the file I can see an error:
E:Zip file is corrupt!
E:Error installing zip file '@/cache/recovery/block.map'
serdasteclas said:
I installed TWRP manager and updated TWRP to 2.8.6.0 but the problem persist, when I am installing the file I can see an error:
E:Zip file is corrupt!
E:Error installing zip file '@/cache/recovery/block.map'
Click to expand...
Click to collapse
That's not a TWRP issue
Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.
Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk
kenmacker said:
Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
You need to turn on USB Debugging, and then run the app.
USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk
work great
thanks
Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.
kenmacker said:
USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Look if you have your SHILD's bootloader unlocked, that may be causing the problem.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
I wanted a full restore/clean version of the ROM without waiting for the factory image to be updated.
I flashed the 101 Factory Image from here. I notice that 103 is there now so just skip this step and flash that now.
I noticed that after flashing the latest SuperSU the device would never boot.
So I had to use KingRoot but for me the apk method never worked so I went with the desktop version.
To get Root I went to KingRoot's XDA page and downloaded the Desktop version.
When running the program it is all in Chinese but is thankfully idiot proof with its one big button on it. Just make sure that USB Debugging is turned on and wait for it to finish, it will reboot during the process.
KingRoot installs its own version of a Super User advisor so it will prompt when something needs root access and for most people that would be enough but I prefer SuperSU, Thankfully KingRoot has a set of instructions, follow these to the letter and it will guide you through removing KingRoot and installing SuperSU. During that process you will get a lot of errors saying that files are no longer there, just ignore them, that means the initial uninstall got the files.
Once I was able to ensure that SuperSU and Root where staying after a reboot I re-installed TWRP (for some reason I couldn't get CWM to stick after a reboot but oh well I like TWRP more >_>) and made a backup of my stock rooted device.
I then went to this page and grabbed the Unofficial Xposed 5.1 .zip and went to this page and grabbed the Xposed Installer.
Rebooted and waited for the App Cache to re-build as the Xposed framework nukes it then installed my mods as normal.
Took a little bit longer than normal to update but oh well, Everything is working smoothly and I'm happy with it.
Rooted my Shield two times wth CWM without problems.
astuermer said:
Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.
Click to expand...
Click to collapse
Which cmw did you use and where did you get it? I tried using flashify with twrp and it says boot failed when booting into recover.
astuermer said:
Rooted my Shield two times wth CWM without problems.
Click to expand...
Click to collapse
Give me a few mins. I will upload my Recovery package...
Here we go. I've flashed and rooted my SHIELD successfully after OTA upgrade - and today again after flashing the clean 103 factory Image.
SHIELD-Portable-Recoveries.zip
Update: I've attached a ZIP file with 4 different recoveries. Simply execute the Batch file I've included (if you're on Windows) and select 1-4.
stock KitKat recovery (from update 101)
stock Lollipop recovery (from update 103)
ClockworkMod recovery (CWM) 6.0.4.4 (somewhere from XDA, but couldn't find the link)
TWRP recovery 2.8.5.0 (from here)
From @Steel01 The TWRP located here may give people problems and we should be using the one in the MultiROM TWRP located here.
Source here.
EDIT: I will test tonight and see what happens when you image with the factory image and just install MultiROM's TWRP and then try SuperSU's latest BETA.
I was trying to use the other TWRP before and could never boot which is why I did the KingRoot method.
If you wanted to change Kinguser to SuperSU all you have to do is download any "Control Rotation App" and set it as Portrait Mode (if it didn't work make sure that the Nvidia Shield Portable is in a sitting position and flip it , It should work , If not try installing other apps), Install "Super-Sume" , Then touch the big blue button , After that wait until the process is done , You should see SuperSU, In the other hand Kinguser has already vanished (I'm not sure if SuperSU will open automatically or not), Install the binary, Reboot, Done.
Have a nice day
Well, ive rooted my phone when it was on September update 2018, when the updates arrives i just flash magisk uninstaller from TWRP (temporary need pc to boot to it) and when i check it with root checker it says my device ain't rooted and i get back installing the update from ota ... the update is downloading , and in step 1 it shows couldn't install , and they it downloads again ... please anyone help me out to install OTA updates !
sahil_firoz said:
Well, ive rooted my phone when it was on September update 2018, when the updates arrives i just flash magisk uninstaller from TWRP (temporary need pc to boot to it) and when i check it with root checker it says my device ain't rooted and i get back installing the update from ota ... the update is downloading , and in step 1 it shows couldn't install , and they it downloads again ... please anyone help me out to install OTA updates !
Click to expand...
Click to collapse
That's because you have twrp installed, otas on every device won't install if you have a custom recovery. The only way I know to remove twrp is to reflash the rom with mi flash tool, or flash a twrp flashable stock rom without flashing the twrp installer.
WhatzIt2Ya said:
That's because you have twrp installed, otas on every device won't install if you have a custom recovery. The only way I know to remove twrp is to reflash the rom with mi flash tool, or flash a twrp flashable stock rom without flashing the twrp installer.
Click to expand...
Click to collapse
TWRP is not installed permanently well, i just boot TWRP with the command ! ... and also with the file .. connected to PC ,,, well, how i know is that when i hold down volume down and power button it shows *no commands* this is why there is no custom recovery installed ! when i searched xda deeply i found that if the TWRP is temporarily installed then, unrooot it and when you install it the ota update will install !
sahil_firoz said:
TWRP is not installed permanently well, i just boot TWRP with the command ! ... and also with the file .. connected to PC ,,, well, how i know is that when i hold down volume down and power button it shows *no commands* this is why there is no custom recovery installed ! when i searched xda deeply i found that if the TWRP is temporarily installed then, unrooot it and when you install it the ota update will install !
Click to expand...
Click to collapse
I thought volume down + power enters fastboot mode. Volume up + power enters recovery. Anyways, if you dont have TWRP installed, then you have to reset your phone.
WhatzIt2Ya said:
I thought volume down + power enters fastboot mode. Volume up + power enters recovery. Anyways, if you dont have TWRP installed, then you have to reset your phone.
Click to expand...
Click to collapse
Oh man, so I have to reset everytime ?? ... By the way for getting into twrp I use mi A1 tool to boot
sahil_firoz said:
Oh man, so I have to reset everytime ?? ... By the way for getting into twrp I use mi A1 tool to boot
Click to expand...
Click to collapse
Well, as long as you didn't flash twrp installer zip, and the ota still fails, then your only solution is to reset your phone.
sahil_firoz said:
Well, ive rooted my phone when it was on September update 2018, when the updates arrives i just flash magisk uninstaller from TWRP (temporary need pc to boot to it) and when i check it with root checker it says my device ain't rooted and i get back installing the update from ota ... the update is downloading , and in step 1 it shows couldn't install , and they it downloads again ... please anyone help me out to install OTA updates !
Click to expand...
Click to collapse
You probably made a mistake and made changes to the system partition. A common mistake is to start twrp and mount the partition as read/write. Even if you did not make any changes, the partition info will be changed and any OTA will fail from that point on.
barrack1 said:
You probably made a mistake and made changes to the system partition. A common mistake is to start twrp and mount the partition as read/write. Even if you did not make any changes, the partition info will be changed and any OTA will fail from that point on.
Click to expand...
Click to collapse
thanks my man ! , Bye Bye stock rom .............. custom ROM FTW !! XD