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!

[Q] ElementalX 1.6 works on Nexus 7?

Hey guys, a bit of a newbie at all of this so please bare with me.
I'm looking at using the NExus 7 (2013) as the headunit on my car and to do this I would need OTG as well as Power at the same time through a USB hub.
Seems like the ElementalX1.6 allows this, but would it work on the new nexus 7?
Would I just have to root the device and install elemental on it for it to work?
your help is much appreciated.

Darkshrimp said:
Hey guys, a bit of a newbie at all of this so please bare with me.
I'm looking at using the NExus 7 (2013) as the headunit on my car and to do this I would need OTG as well as Power at the same time through a USB hub.
Seems like the ElementalX1.6 allows this, but would it work on the new nexus 7?
Would I just have to root the device and install elemental on it for it to work?
your help is much appreciated.
Click to expand...
Click to collapse
yes, you need to root. check the Official Development Section, there is a thread on it. I believe 1.7 just included the feature you are asking for.

Since I'm not yet allowed to post weithin dev threads, could somebody post for me stating that keyboard wouldn't pop up in both aosp and Dolphin Browser after flashing elementalx 1.8 beta (see attached log for kernel details I opted for). Thanks in advance and sorry for posting in the 'wrong' thread..
Edit: I'm using Slimbean 4.3.1 rom (oct 13 weekly)

Ænimal said:
Since I'm not yet allowed to post weithin dev threads, could somebody post for me stating that keyboard wouldn't pop up in both aosp and Dolphin Browser after flashing elementalx 1.8 beta (see attached log for kernel details I opted for).
Click to expand...
Click to collapse
It's extremely unlikely that the kernel is responsible.
I'm running ElementalX 1.8 and Slim Bean GIT version (a bit newer than the Oct 13 weekly) and the keyboard works fine.

tni.andro said:
It's extremely unlikely that the kernel is responsible.
I'm running ElementalX 1.8 and Slim Bean GIT version (a bit newer than the Oct 13 weekly) and the keyboard works fine.
Click to expand...
Click to collapse
Well, went back to 1.6 for now and everything's golden. Didn't change anything option-wise, except for the battery life extension feature, obviously. Just thought it would be nice to let dev know, because I really appreciate his work..
Update: Reinstalled ElementalX 1.8 beta with power button to bypass dt2w enabled this time and keyboard is working in all browsers (including 'minimus' as secondary rom - didn't run multirom the first time I tried.) So everything's fine now, thanks.

No problems here with keyboard using AOSP browser, 1.8 ElementalX beta, Carbon ROM 1015 build. I do use swiftkey tablet keyboard though.

[Q] Very low screen bright after reboot

Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot

reypescador said:
Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot
Click to expand...
Click to collapse
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411

muiriddin said:
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411
Click to expand...
Click to collapse
Thank you very much
I try to read the info and decide what to do.
Thanks again

Ok it´s done
First I´ve installer V500-4.2.2-Base from recovery, I have reinstalled CM 11 and everything OK.
I have tried a step beyond and I have installed [KERNEL][v500][4.4.4][AOSP] RedKernel [16/09] (everybody seems to be very happy with it) but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help

reypescador said:
but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help
Click to expand...
Click to collapse
Seems to be problems with Super SU but I can´t solve them at the moment

You must install the UKM scripts from recovery. Read the op from the red kernel thread...

edisso10018 said:
You must install the UKM scripts from recovery. Read the op from the red kernel thread...
Click to expand...
Click to collapse
What he said!
This confused me at first too. In the very early days of redkernel he included his own forked version of the UKM scripts those have been removed because the UKM script maintainer agreed to merge his changes and therefore he doesn't have to maintain his own copy (better for all involved so he can focus on kernel development). Search the thread you will find a link to where you can download the official UKM scripts and your problem will go away.
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...

muiriddin said:
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...
Click to expand...
Click to collapse
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium

ncguy68 said:
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.

muiriddin said:
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.
Click to expand...
Click to collapse
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium

ncguy68 said:
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.

muiriddin said:
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.
Click to expand...
Click to collapse
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium

ncguy68 said:
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I am unaware of a problem with the 4.4.2 base files provided. I have just never used them, I already had the LG Support Tool downloaded and it was easiest to use the path I knew and was comfortable with.
The key thing (and why I run the 4.4.2 base instead of the 4.2.2. base) that is different is the brightness at its lowest setting. The 4.2.2 base on many of the V500's suffers from alternating light and dark spots on one side of the tablet when viewing the tablet in low light with the brightness at its lowest setting and viewing gmail (any app with a white background basically). I use my tablet mostly in dark conditions like this (man I make it sound like I live in a basement somewhere *laughs*). The 4.4.2 base firmware changes the tablet so it functions well at the lowest brightness.
The first picture in this thread shows the screen problem I refer to (although not on a white screen):
http://forum.xda-developers.com/showthread.php?t=2553055

IllusionRom Lollipop LRX21M

Hello guys! From IllusionRom team we wanna offer one of the first compiled versions of Lollipop in XDA.
WE ARE USING THE BINARIES FROM THE SECOND LOLLIPOP PREVIEW, SINCE LOLLIPOP OFFICIAL BINARIES ARE NOT RELEASED YET.
This thread will get updated really soon, but right now we are focusing fix some errors and update the ROM..
Flashing steps:
TWRP IS RECOMMENDED
Download the ROM on the section above.
Download the gapps on the section above.
Go on TWRP, and wipe data,system, cache and dalvik cache.
Flash the ROM.
Then press back key, go on Reboot section and select Recovery
It will reboot into TWRP again, so now flash gapps(and superSU if you want root).
Enjoy!
Code:
[CENTER]ROM DOWNLOAD:
[SIZE="3"][URL="https://www.androidfilehost.com/?fid=95784891001607000"]IllusionRom AOSP Release 1[/URL][/SIZE]
[SIZE="2"][URL="https://www.copy.com/s/AQMTxHJP7jXiSqZU"]AOSP Release 1[/URL][/SIZE]
MIRRORS:
****IllusionRom AOSP Release 1****
[URL="http://uploadboy.com/fnbmnm1p0k5t.html"]UploadBoy[/URL] thanks to @solimavera
****AOSP Release 1****
[URL="https://drive.google.com/file/d/0ByrfJAT1lgDFcjJyeTVVMUp6MG8/view"]Google Drive[/URL] thanks to [user=4668017]@NABENDU1[/user]
[URL="http://www.bpear.me/lollipop/aosp_hammerhead-ota-eng.hieu.zip"]bpear[/URL] thanks to [user=3007198]@bpear96[/user][/CENTER]
Code:
[CENTER]GAPPS DOWNLOAD:
[SIZE="3"][URL="https://www.androidfilehost.com/?fid=95784891001607224"]AndroidLollipopGapps-Minimal[/URL][/SIZE][/CENTER]
Known issues:
* TWRP will tell you after flashing that there is no SO installed, but there is. It is just Google zip format is different from KitKat.
* If root is not working, read this post.
XDA:DevDB Information
IllusionRom, ROM for the Google Nexus 5
Contributors
herna, aznrice2k4, show-p1984, drioidmaster92
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Beta
Created 2014-11-05
Last Updated 2014-11-07

Nice , can't wait!

Damn!!!
I just got home from work and started building, oh well.
Kudos for being first!

Downloading now.. Nice

Suhaas said:
Downloading now.. Will it work with multi ROM?
Click to expand...
Click to collapse
I can´t answer you sincerely. I did not try with MultiROM, but I would put my hand in the fire that it will not
We´ll try to make it MultiROM compatible if it is on our hands. Don´t worry.

could you mirror it on Androidfilehost or dev-host please? my nerwork is governments and copy.com is bloked.
thank you.

Mirror
Google Drive Mirrror
Click Me
@herna if you could link this to your OP

Mirror: http://www.bpear.me/lollipop/aosp_hammerhead-ota-eng.hieu.zip

ooo whut?

thank you for mirrors
downloading now

nice! looking forward to progress!

Hello guys. Another post from me. @aznrice2k4 , @MidnightNinja and me are working for release a Gapps with all new apps from Nexus 9 system dump.
As a lot of people seems that are not able to live without root, thanked to one of most cool guys I know @sykopompos , we are gonna release a modified version of the kernel which has selinux set to permissive, so that allow us to can use root working at 100%. It needs to be flashed via fastboot.
fastboot flash boot bricked-boot.img
Download link: Here here!

Great work man.. Much appreciated.... Have been refreshing the dev page and chkng the xda page since monday
Just one qstn.. Will this still have the miscellaneous battery drain ?
Sent from my Nexus 5 using XDA Free mobile app

There isn't a particular reason that we have to use TWRP right? Other recoveries should work? You guys rock! :good:
Also we can just flash the new kernel, then flash SuperSU to get root, right?

1. Root works after flashing supersu. No need to flash another kernel since it's my exp bricked version.
2. You can use multirom but it has to be internal and not secondary. Why? IDK. I tried.
3. Flash another kernel and I have no guarantee for anything.
4. I haven't even had the chance to text back my gf since all I've been doing is rebooting rebooting and testing gapps. Battery life? Good, I supposed. I have no clue.

Anybody wanna tell me how to get back into recovery. I guess I jumped the gun.
Tried to volume- plus power and got the red triangle android guy.
Manage to download es file explorer off internet and saw my files intact on SD.
Didn't see the no root issue so didn't flash SuperSU. .
BTW no internet or computer with me

Looking foward for the gapps and we're good to go....
Sent from my Nexus 5 using Tapatalk

Have you tried it with multirom?
thanks

razrlover said:
Anybody wanna tell me how to get back into recovery. I guess I jumped the gun.
Tried to volume- plus power and got the red triangle android guy.
Manage to download es file explorer off internet and saw my files intact on SD.
Didn't see the no root issue so didn't flash SuperSU. .
BTW no internet or computer with me
Click to expand...
Click to collapse
Seems that flashing this zip will take out or replace the recovery. All you need to do is download TWRP(my favorite), and flash it via fastboot. With that you will have back your recovery access. I have internet and computer working perfect to me, idk what happened to you. I would recommend you to flash the L 2nd preview radio indeed.

aznrice2k4 said:
1. Root works after flashing supersu. No need to flash another kernel since it's my exp bricked version.
2. You can use multirom but it has to be internal and not secondary. Why? IDK. I tried.
3. Flash another kernel and I have no guarantee for anything.
4. I haven't even had the chance to text back my gf since all I've been doing is rebooting rebooting and testing gapps. Battery life? Good, I supposed. I have no clue.
Click to expand...
Click to collapse
Wait so we do not need to flash the permissive kernel?
Also, this doesn't have the Play Store, correct?

what is: recovery with WITH SELINUX SUPPORT?

heya, well my topic pretty much says it all, I am currently running mahdi rom 2.4 (yes its been a while) and after some looking about decided that I want 2 go for his latest version 2.9, but I noticed something that I haven't seen before and that is "SELINUX SUPPORT" what is this how do I find out if I have it or not
Thnx for the help

b3ava said:
heya, well my topic pretty much says it all, I am currently running mahdi rom 2.4 (yes its been a while) and after some looking about decided that I want 2 go for his latest version 2.9, but I noticed something that I haven't seen before and that is "SELINUX SUPPORT" what is this how do I find out if I have it or not
Thnx for the help
Click to expand...
Click to collapse
"recovery with WITH SELINUX SUPPORT?"
It's a security feature. It's enabled within the kernel the recovery is built with, and the recovery itself.
I don't know which recovery you are using because you don't say. For example, I think TWRP added SElinux somewhere around 2.6.x. If you are on a later version you have it. Again for TWRP just boot to TWRP and check the log it will tell you the SE linux status.

forgot to say thanx was on 6.3.2.1 which after a quick google search after your info confirms I have it thanx a million buddy