Develop Bugs

Problems with Rom Toolbox; Failed to mount system Read/Write

Today, i updated to the latest version of Cyanogenmod 10.2 nightlies; i was previously running CM 10.1 RC2 on Gnex. I was using the adblocker feature on Rom toolbox and it use to work beautifully without any errors. After the update, i tried using the adblocker feature again but this time it gave me message " Failed to mount system Read/Write ."
Can anyone please help me solve this problem ? I'm still new to the nexus/xda community and i'm not really sure what to do.
Thanks in advance

Amnr123 said:
Today, i updated to the latest version of Cyanogenmod 10.2 nightlies; i was previously running CM 10.1 RC2 on Gnex. I was using the adblocker feature on Rom toolbox and it use to work beautifully without any errors. After the update, i tried using the adblocker feature again but this time it gave me message " Failed to mount system Read/Write ."
Can anyone please help me solve this problem ? I'm still new to the nexus/xda community and i'm not really sure what to do.
Thanks in advance
Click to expand...
Click to collapse
Hello,
I have the same problem too, but with another rom (JB 4.3.1 for another phone).
I am trying to track down a fix for this. If I find one that works, I will post back with a possible solution.

bombermanCC said:
Hello,
I have the same problem too, but with another rom (JB 4.3.1 for another phone).
I am trying to track down a fix for this. If I find one that works, I will post back with a possible solution.
Click to expand...
Click to collapse
Amnr123 said:
Today, i updated to the latest version of Cyanogenmod 10.2 nightlies; i was previously running CM 10.1 RC2 on Gnex. I was using the adblocker feature on Rom toolbox and it use to work beautifully without any errors. After the update, i tried using the adblocker feature again but this time it gave me message " Failed to mount system Read/Write ."
Can anyone please help me solve this problem ? I'm still new to the nexus/xda community and i'm not really sure what to do.
Thanks in advance
Click to expand...
Click to collapse
Had same problem until I installed Busybox - free on Play!

Problem after installing GApps [CM12]

Hello,
hey. I have been using Cynogenmod since three years for my Galaxy W.I updated to version 12.0 with Recovery : CWM 6.0.5.1..... . But when I flash GApps (Downloaded from link provided in this thread), Phone becomes so slow that its almost impossible to use. Trebuchet keeps on crashing. Things wont open for like a minute or so..... Any idea??

Dude its the problem of the ROM it lags too much you can revert back to kitkat or get used to it like me ?
Sent from my GT-I8150 using XDA Free mobile app

GTP 8.4 purchased rooted, what should I do next ?

Hello,
A few months ago I purchased a previously owned Samsung Galaxy Tab Pro 8.4. The tab has been rooted, as SuperSU is " installed " and functioning. To be sure I don't brick the device, I am reaching out for suggested next steps.
Long story short, the battery life of this tab has become horrible. To rub salt in the wound, I generally have to reboot it 3-5 times just to get it to start charging. I have read on a different thread that this isn't uncommon, and that the ROM might have a bug in it causing this.
I believe the next step is to flash a different ROM. However, I don't know which way to go as I cant tell what recovery this device is running, or even what mod could be running. (I have a feeling the stock recovery is still intact.)
I would imagine that my next step is dependent on confirming the recovery that is running. If so, is it possible to figure out ? (picture of recovery boot attached) ...Just found out new members are not allowed to include pictures in posts )
Device detail, all obtained from Settings>Device>About:
-Model: SM-T320 (wifi only version)
-Android version: 4.4.2
-Kernel version: 3.4.0-3264497
[email protected] #1 - Tue Nov 11, 2014
-Build Number: KOT49H.T320UEU1ANK1
-When clicking the Status menu, it is noted that the device status is " Custom "
When attaching the picture, i just realized that the Build number reflected within the settings app differs from the build listed in the recovery boot screen........
Thank you all in advance! I am VERY new to android and a huge rookie.

Flash TWRP via Odin and flash CM12.1 in that. Ditch TouchWiz for a better experience.
And for the battery problem you mentioned, you might want to take a look at the battery reseating thread which is somewhere around our device subforum.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]

AndyYan said:
Flash TWRP via Odin and flash CM12.1 in that. Ditch TouchWiz for a better experience.
And for the battery problem you mentioned, you might want to take a look at the battery reseating thread which is somewhere around our device subforum.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
Thank you !
I am finding that the CM12.1 ROM is Lollipop. Do I need to update my tab to lollipop first, or is the OS with the ROM ?
again, i am very new to Android. i apologize if this is a silly question...

APT082 said:
Thank you !
I am finding that the CM12.1 ROM is Lollipop. Do I need to update my tab to lollipop first, or is the OS with the ROM ?
again, i am very new to Android. i apologize if this is a silly question...
Click to expand...
Click to collapse
Nope, just start flashing from whatever version you're already on. The TabPRO 8.4 doesn't have official Lollipop yet, by the way.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]

AndyYan said:
Nope, just start flashing from whatever version you're already on. The TabPRO 8.4 doesn't have official Lollipop yet, by the way.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
I apologize for the delay. My ISP has been down for a few days now.
I flashed TWRP via Odin and downloaded the latest release of CM 12.1 ( mondrianwifi ).
When flashing the zip through TWRP;
Cant install this package on top of incompatible data. Please try another package or run a factory reset​E: Error executing update binary in zip 'file location and name'​
I wiping cache/dalvik, but this didnt help.
Any additional advice ?
again, thank you.
-- I just performed a factory data reset, and experience the same error when trying to flash the CM12.1 ZIP via TWRP.

APT082 said:
I apologize for the delay. My ISP has been down for a few days now.
I flashed TWRP via Odin and downloaded the latest release of CM 12.1 ( mondrianwifi ).
When flashing the zip through TWRP;
Cant install this package on top of incompatible data. Please try another package or run a factory reset​E: Error executing update binary in zip 'file location and name'​
I wiping cache/dalvik, but this didnt help.
Any additional advice ?
again, thank you.
-- I just performed a factory data reset, and experience the same error when trying to flash the CM12.1 ZIP via TWRP.
Click to expand...
Click to collapse
Sorry I missed your post. It should just be a matter of wiping both /data and /system - at least it worked for me that way.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]

TWRP verifying version dates

Hello, this is my first post. I'm new to flashing phones. I have a Sony Xperia S and I'm trying to update it beyond Android 4. I instaled TWRP 2.8.7 Nozomi, and flashed Cyanogen 9 which happened to have a date of Nov/2015. When I tried to install Cyanogen 12, last version dated July/2015, I received the message "Can't flash version xxxx over a newer one". I don't know how to erase the first installation or how to override the date verification. Help is welcomed
Humberto Mejia

HMejia_U said:
Hello, this is my first post. I'm new to flashing phones. I have a Sony Xperia S and I'm trying to update it beyond Android 4. I instaled TWRP 2.8.7 Nozomi, and flashed Cyanogen 9 which happened to have a date of Nov/2015. When I tried to install Cyanogen 12, last version dated July/2015, I received the message "Can't flash version xxxx over a newer one". I don't know how to erase the first installation or how to override the date verification. Help is welcomed
Humberto Mejia
Click to expand...
Click to collapse
this is a mistake of the rom developer... he should not check that asset .... so please report to him
Sent from my Xperia T using XDA Free mobile app

assert failed: oppo.verify_trustzone("TZ.BF.4.0.1-81399") == "1"

Hi and sorry for the potential newb post
Been using CM / Lineage for years and never come across an individual firmware upgrade requirement until now.
I am on Lineage nightly Feb 8th and cant go any further due to:
comparing tz version TZ.BF4.0.1-83199 to tz.bf.4.0.1-76917
assert failed: oppo.verify_trustzone("TZ.BF.4.0.1-81399") == "1"
updater process ended with ERROR: 7 error installing zip file
I have the working 1+3 TWRP installed so Is it possible to upgrade the firmware only?
Or do I have to wipe and install the latest OOS then go back to Lineage?
I downloaded OOS 41 and there is a firmware folder in there with a few bin / mbn files so kinda hoping I can somehow flash just the firmware and keep my build.
Appreciate any help....
Cheers
Gaz

Here is the latest firmware (4.0.3). Download firmware + modem and flash in TWRP before LineageOS.

Spot on - thanks Fam im sorted

Familotel said:
Here is the latest firmware (4.0.3). Download firmware + modem and flash in TWRP before LineageOS.
Click to expand...
Click to collapse
great work!thanks

Familotel said:
Here is the latest firmware (4.0.3). Download firmware + modem and flash in TWRP before LineageOS.
Click to expand...
Click to collapse
Hey there, sorry to bug you guys. Unfortunately I'm noob so I can't comment on the main LOS thread, but I have an issue that hopefully someone can help with. Originally on CM14 nightlies, without any dramas, obviously with the change from CM on LOS I've flashed the experimental build, then the LOS nightly to get started, all went fine until the change to unified requiring the firmware update. I've installed 2nd March nightly (by editing the file to ignore the trustzone version) in case it was that, but no seems not.
I've flashed the latest FW as mentioned, and the Baseband version is M8996FAAAANAQM-1.85373.1.86546.1 so it appears I'm running definitely running the latest FW (and there were no errors on install) I then reboot to system, download the latest nightly and go to install - still getting the TZ.BF.4.0.1-83199 to TZ.BF.4.0.1-85373 error.... Have I missed a step somewhere? or is this blindingly obvious and I'm a muppet?
Any helps appreciated! cheers

Same issue with the same parameters!
Z-master said:
Hey there, sorry to bug you guys. Unfortunately I'm noob so I can't comment on the main LOS thread, but I have an issue that hopefully someone can help with. Originally on CM14 nightlies, without any dramas, obviously with the change from CM on LOS I've flashed the experimental build, then the LOS nightly to get started, all went fine until the change to unified requiring the firmware update. I've installed 2nd March nightly (by editing the file to ignore the trustzone version) in case it was that, but no seems not.
I've flashed the latest FW as mentioned, and the Baseband version is M8996FAAAANAQM-1.85373.1.86546.1 so it appears I'm running definitely running the latest FW (and there were no errors on install) I then reboot to system, download the latest nightly and go to install - still getting the TZ.BF.4.0.1-83199 to TZ.BF.4.0.1-85373 error.... Have I missed a step somewhere? or is this blindingly obvious and I'm a muppet?
Any helps appreciated! cheers
Click to expand...
Click to collapse
Hi, I have the exact same issue. I've flashed the firmware to 4.0.3 and successfully installed the nightly from 08/02/2017. Now when I try to flash the nightly from 09/03/2017 I get this issue again! This time nothing helps so far.
Please, if you find a solution - let me know!

devianity said:
Hi, I have the exact same issue. I've flashed the firmware to 4.0.3 and successfully installed the nightly from 08/02/2017. Now when I try to flash the nightly from 09/03/2017 I get this issue again! This time nothing helps so far.
Please, if you find a solution - let me know!
Click to expand...
Click to collapse
Install the firmware from the Open Beta here:
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628

Yeah i had the same issue - open beta 12 is required for the 9th Mar build