Database Info

E: Unable to mount /cache

I am trying to install the cm9 rom on my new att htc one x. I used the tutorials on oneXroot.net to unlock the boot loader and install twrp. When ever I try to install the rom, I get an error saying that
e:unable to mount /cache
I went to the mount option and tried to manually mount the cache but it wont. I saw some other videos on youtube, that were succesful in getting cm9 running using clockworkmod. I flashed that and clockworkmod won't even run. Please help. I hate htc sense, if the hardware wasn't so appealing I wouldn't have even bought this phone.

I don't think CM9 ROMs have been created for the HTC One X. My recommendation would be to go over to the One X Development forum and try out one of the ROMs listed there. I am running Clean ROM 3.1 Standard Edition with no issues, thus far.

We have an unofficial CM 9 port.
It sounds to me like the OP installed the CWM for the Tegra 3 HOX.
The one for our phone is here

Thanks for the install tool tip.
Hey,
So using the above link provided I was able to install the clockworkmod. But that is it. I am back to square one on installing the rom. Now I get this error instead.
E:Error in /sdcard/download/.....Roms name.....
I tried it with two unofficial cm9, exodised and endeavor, both of them give the same error. Please help.

1297 yeturesp
There's a good chance your sdcard might be hosed. You might be better off checking this thread (http://forum.xda-developers.com/showthread.php?t=1740448&highlight=bricked) for next steps.

theshanthan said:
Hey,
So using the above link provided I was able to install the clockworkmod. But that is it. I am back to square one on installing the rom. Now I get this error instead.
E:Error in /sdcard/download/.....Roms name.....
I tried it with two unofficial cm9, exodised and endeavor, both of them give the same error. Please help.
Click to expand...
Click to collapse
*smh*
quit installing International ONe X Roms.
Our CM 9 is here http://forum.xda-developers.com/showthread.php?t=1688448
Our dev Section is here http://forum.xda-developers.com/forumdisplay.php?f=1541

theshanthan said:
I tried it with two unofficial cm9, exodised and endeavor
Click to expand...
Click to collapse
To reiterate the above, you are trying to install roms for a different phone. The international HOX has the same name but different internals.
There is only one cm9 for the AT&T One X, and it is still an alpha with various things not working.

Thanks a lot guys.
My confusion was the problem. I actually figured out that I was using the wrong roms and googled for the right one and managed to install it. I was just logging in to post this and found the answer already. Thanks a lot.
This is one of the best forums ever and you are getting a thanks.

[Q] Question about Samsung Galaxy S II Skyrocket SGH-I727

Hey there guys,
I'm a noob so I had to post here. Although I've already read the intro guides to installing ROM's. Right now running the CM 11 nightly on my skyrocket. I'm looking for a better rom that has kitkat and I came across the Hellkat/BlueLightning roms. I wanted to install blue lightning but I have a couple questions before I mess anything up (I've read that being fully informed and taking precautions is a must)
So I wanted to know, if I'm installing this rom: http://forum.xda-developers.com/showthread.php?t=2624875
Can I use the current recovery that I'm using? It's CWM v.6.0.3.7
I read that it's recommended to use a SELinux compatible recovery.
Someone in the thread said to use twrp 2.6.1 but I don't want to change from CWM to twrp.
So can I go ahead and install blue lightning? Do i absolutely HAVE to change to twrp? Or does the newest CWM for my phone work with installing the blue lightning build? (a link would be appreciated!)
Also, a question that I've always had, I don't have to install the first version of the rom right? I can just go ahead and install the zip of the latest build? That's what I've been doing, and when multiple updates come along, I install the latest build and not the builds in between. Can someone clarify this for me? I'm not doing something wrong right?
Thanks in advance for answering my lengthy question and helping me out.
Cheers :good:

svvparakala said:
Hey there guys,
I'm a noob so I had to post here. Although I've already read the intro guides to installing ROM's. Right now running the CM 11 nightly on my skyrocket. I'm looking for a better rom that has kitkat and I came across the Hellkat/BlueLightning roms. I wanted to install blue lightning but I have a couple questions before I mess anything up (I've read that being fully informed and taking precautions is a must)
So I wanted to know, if I'm installing this rom: http://forum.xda-developers.com/showthread.php?t=2624875
Can I use the current recovery that I'm using? It's CWM v.6.0.3.7
I read that it's recommended to use a SELinux compatible recovery.
Someone in the thread said to use twrp 2.6.1 but I don't want to change from CWM to twrp.
So can I go ahead and install blue lightning? Do i absolutely HAVE to change to twrp? Or does the newest CWM for my phone work with installing the blue lightning build? (a link would be appreciated!)
Also, a question that I've always had, I don't have to install the first version of the rom right? I can just go ahead and install the zip of the latest build? That's what I've been doing, and when multiple updates come along, I install the latest build and not the builds in between. Can someone clarify this for me? I'm not doing something wrong right?
Thanks in advance for answering my lengthy question and helping me out.
Cheers :good:
Click to expand...
Click to collapse
Poured your heart out I see. Ill try and clear things up. First of though, you can use either CWM or TWRP recovery's. I actually prefer CWM to. If you are installing Kit Kat though you do need CWM v6.0.3.7 or above! Also you need a Jellybean radio. As for the ROM I am running HellDevs Unofficial CM.11 Built using the Linaro toolchain, Works great! Also No you do not have to install the first versions, Just Wipe data, cache and dalvic. Use any version you want! Hope I helped if you have any more questions id be happy to help.

Thanks!
SighIsAnonymous said:
Poured your heart out I see. Ill try and clear things up. First of though, you can use either CWM or TWRP recovery's. I actually prefer CWM to. If you are installing Kit Kat though you do need CWM v6.0.3.7 or above! Also you need a Jellybean radio. As for the ROM I am running HellDevs Unofficial CM.11 Built using the Linaro toolchain, Works great! Also No you do not have to install the first versions, Just Wipe data, cache and dalvic. Use any version you want! Hope I helped if you have any more questions id be happy to help.
Click to expand...
Click to collapse
Ah, so it's not much different from when I was installing the CM 11. Thanks for the quick reply! :victory:
(P.S. how do you close a thread/mark it as answered?)

svvparakala said:
Ah, so it's not much different from when I was installing the CM 11. Thanks for the quick reply! :victory:
(P.S. how do you close a thread/mark it as answered?)
Click to expand...
Click to collapse
Anytime bub! I actually don't know how to close it. But leaving it up could help other people also.. Who have the same question.

Md5 Checksum?
SighIsAnonymous said:
Anytime bub! I actually don't know how to close it. But leaving it up could help other people also.. Who have the same question.
Click to expand...
Click to collapse
Actually I do have another question I was hoping you might be able to help me out with. I've heard that MD5 checksum is an important step. I downloaded the blulightning build. But when I copied the md5 checksum they had on the goo page, it didn't match the one on the zip file, or the md5 file that i downloaded (if i click on the md5 number on goo) Is something wrong? Or am i messing something up here?
Can't post this as a reply to the blue lightning thread yet, still under 10 posts :silly:

svvparakala said:
Actually I do have another question I was hoping you might be able to help me out with. I've heard that MD5 checksum is an important step. I downloaded the blulightning build. But when I copied the md5 checksum they had on the goo page, it didn't match the one on the zip file, or the md5 file that i downloaded (if i click on the md5 number on goo) Is something wrong? Or am i messing something up here?
Can't post this as a reply to the blue lightning thread yet, still under 10 posts :silly:
Click to expand...
Click to collapse
I usually don't check it. You did it all wrong though. There's a few ways to check the MD5, either through busybox on the phone or a app on the computer. Don't worry I thought the same thing you did when I started.:laugh: But here's a great thread with more information! http://forum.xda-developers.com/showthread.php?p=17065076 Personally though if you are sure you download the file correctly you should be good. Also most the time if something is wrong CWM Will tell you and not even let you flash it. Check that thread though it could maybe clear some things up for you.:angel:

[Q&A] [RECOVERY] TWRP touch recovery v2.8.4.0

Q&A for [RECOVERY] TWRP touch recovery v2.8.4.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWRP touch recovery v2.8.4.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

dd98 said:
You used OFFICIAL TWRP WITH hboot 2.16!! I would strongly advise you to switch to a TWRP thats built for 2.16 (like the one in the op), if not you could potentially HARD BRICK your phone
Click to expand...
Click to collapse
This is wrong. Official TWRP hast support for 2.16 since 2.8.3.0.
Edit: The original thread has unfortunately got a post count restriction which prevents me from posting there.

Hauk92 said:
This is wrong. Official TWRP hast support for 2.16 since 2.8.3.0.
Edit: The original thread has unfortunately got a post count restriction which prevents me from posting there.
Click to expand...
Click to collapse
it works as normal on 2.16, yes, but doing things like formatting /system will hard brick your phone which is too big a risk to take

Why do you think that? The risk should not be bigger than in 2.8.1.1.

This post in the main thread further elaborates that the newer TWRP versions work on both hboots. @dd98
Although there is a script which selects the right fstab.

Hauk92 said:
This post in the main thread further elaborates that the newer TWRP versions work on both hboots. @dd98
Although there is a script which selects the right fstab.
Click to expand...
Click to collapse
@Hauk92 Thanks for the PM
Yeah, I'm blind, the script is there. I was looking for the updated script by mdmower which just symlinks the right fstab from the init.recovery.qcom.rc, but the official TWRP uses his older solution with calling a shell script.
Have you tried and verified that it works?

I tried 2.8.4 which works flawless for me, including formatting system and flashing roms etc.
There might be some errors in the log which are related to mtp and the twrp version (they show up on other devices, too), but they can safely be ignored.

CM encrypted /data support
Hi,
It's great to see the unified hboot support making it into the official release. Although I'm running on 2.15 at present, I'm thinking of switching to 2.16.
However, one thing still seems to be lacking from the official release that is working on mdmower's build -- support for encrypted CM devices with the new partition layout.
I'm running CM12 (upgraded from CM11, on which the original encryption of /data was done). Using mdmower's 2.8.1.1 (and previous versions), I am able to successfully decrypt /data within TWRP in order to perform backups etc.
However, if I try the official 2.8.5.0 build, I get an error that /data can't be mounted and no crypto footer can be found. My understanding though is that CM no longer uses a crypto footer but uses the "extra" partition instead. Is there a patch to support this which could be pushed upstream, or is this something which is supposed work, and there's something odd about my system?
Thanks,
Z

Fixed in 2.8.5.5
In answer to my own post, for anyone else who stumbles upon it, this was fixed by mdmower in his unofficial 2.8.5.5 build (his 2.8.5.4 had the same issue).
With any luck, this will also be fixed in the next official release.
Z

[ROM] [ALPHA] [WIP} AOSP 7.0 Lollipop for Nexus Q -1/15/17

READ IN ENTIRETY BEFOR INSTALLING
I have procured a new Nexus Q. Work has resumed on Android 7.0, from a hardware and specs standpoint, there is no reason to think that this device is not capable of running Nougat if the Galaxy Nexus can. Stay tuned for a build in the coming weeks, I will also be uploading this project to github shortly
AOSP 7.0 Nougat for Nexus Q
Code:
Quote:
DISCLAMER
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Working:
TBD
Not Working:
TBD
Recovery
https://drive.google.com/file/d/0B7WYr1U8sRRAM1d3czhER0RoTGM/view?usp=sharing
./fastboot flash recovery
MAKE A BACKUP BEFORE INSTALLING AND SEND ME A LOGCAT WHEN YOU ENCOUNTER ISSUES SO I CAN TRY TO RESOLVE THEM
DL Link (Google Drive):
***LINK REMOVED*** -
Anyone interested in an early build send me a PM

Nice! Thanks very much for this! I'll try it when I'm back home in a few days. I was planning to try and work on this myself but perhaps I can transfer some efforts over to Android TV. Do you have the source for this on GitHub as that could also be really helpful - that way a few of us can contribute to help fix things etc.

New build coming soon with proper sources and fixes posted to GitHub. Also, if anyone would be interested, I believe that it may be possible to use an OTG webcam for Skype/etc.

Great stuff, thanks for doing this. Should be able to get android TV then since it's just a separate launcher.

Hmm, not having any luck flashing this. I get an "Installation aborted" error. What recovery are you using?

New build. Testing needed.

jyeley5 said:
New build. Testing needed.
Click to expand...
Click to collapse
What are the changes?

jyeley5 said:
New build. Testing needed.
Click to expand...
Click to collapse
This one seems to flash now (although it completes suspiciously quickly) but attempting to boot results in just a black screen over HDMI. I can't take a logcat because of the device permissions but is does show up with ADB so it presumably it is at least booting the kernel and a some core system but seemingly nothing past that - not even a boot animation.

wollac11 said:
This one seems to flash now (although it completes suspiciously quickly) but attempting to boot results in just a black screen over HDMI. I can't take a logcat because of the device permissions but is does show up with ADB so it presumably it is at least booting the kernel and a some core system but seemingly nothing past that - not even a boot animation.
Click to expand...
Click to collapse
Updated the CM base and merged some changes that I've been porting over. Did you install over another build or wipe fresh?

jyeley5 said:
Updated the CM base and merged some changes that I've been porting over. Did you install over another build or wipe fresh?
Click to expand...
Click to collapse
It was a fresh install, cleaned system, data and cache.

wollac11 said:
This one seems to flash now (although it completes suspiciously quickly) but attempting to boot results in just a black screen over HDMI. I can't take a logcat because of the device permissions but is does show up with ADB so it presumably it is at least booting the kernel and a some core system but seemingly nothing past that - not even a boot animation.
Click to expand...
Click to collapse
Try installing over a working CM11 build. Can you get me a logcat if that still doesn't resolve the issue?

jyeley5 said:
Try installing over a working CM11 build. Can you get me a logcat if that still doesn't resolve the issue?
Click to expand...
Click to collapse
I just tried flashing over Cm11 and nothing so far. Seems also to not boot. The speed at which it flashes in recovery says to me something isn't right with the updater script. There is no way it is copying the 255MB contents onto the Nexus Q in that time. Cm11 (which is smaller) takes far longer.
I tried to get a logcat but as before I am not able to get one of the boot attempt as the device appears as offline (because I can't authorise the PC RSA keys with adb as that would need Android to finish booting at least once). I can get you a recovery log or a logcat while flashing the Zip from recovery if you like but that's about it.
Have you actually had this booting on a Nexus Q then at all yet? And if so, how exactly did you install it, with which recovery and if over another ROM which one was it?

Possibly stupid question...
I'm new to this forum, at least posting here. So, since the Nexus Q app is no longer supported, how does one enable USB debugging on the Q? Any redirects and help would be greatly appreciated! I just got a brand new Q today for $10 at a local Goodwill (accompanied by fellow Q's). I was very sad to see these are no longer factory-functional.
If this is the wrong place to post, I apologize in advance, and would gladly accept on where-to-post details.
Thanks!

Natodroid1 said:
I'm new to this forum, at least posting here. So, since the Nexus Q app is no longer supported, how does one enable USB debugging on the Q? Any redirects and help would be greatly appreciated! I just got a brand new Q today for $10 at a local Goodwill (accompanied by fellow Q's). I was very sad to see these are no longer factory-functional.
If this is the wrong place to post, I apologize in advance, and would gladly accept on where-to-post details.
Thanks!
Click to expand...
Click to collapse
You've replied to a post about a specific custom ROM in the development section (which is completely the wrong place) and failed follow the XDA rule of searching before asking a question, because if you had you'd find the answer has already posted multiple times. Not trying to be harsh or rude - just letting you know!
If you have general questions or need help you should really go to the the "Nexus Q Help, Q&A and troubleshooting" section.
However, the situation is that you can't enable debugging on the stock ROM, but you can boot the Nexus Q into fastboot mode by holding your hand over the Q while you turn it on - this will make the led turn and stay red if successful (nothing will be shown onscreen). From there you can unlock your Q and boot a custom recovery image by issuing the correct fastboot commands from your PC. The custom recovery allows you to flash a custom ROM. The stock ROM is no use without the app which cannot be registered anymore since the servers are down.

Huge update, let me know how it's working

jyeley5 said:
Huge update, let me know how it's working
Click to expand...
Click to collapse
How to install this? Please give us some instruction.

Recovery added to original post, flash in fastboot. An amplifier build will be posted as soon as I finish it.

I keep getting "Installation aborted" when trying to flash. Not sure what I'm doing wrong. Used the recovery you just posted.

jyeley5 said:
Huge update, let me know how it's working
Click to expand...
Click to collapse
Tried to flash this latest version but it seems that there is an error in the updater-script. I get a status 6 error in recovery: "Installation Aborted".
Edit: So I edited the updater-script to remedy the status 6 error and then it progressed through most of the way before giving a status 7. I managed to fix the status 7 with a further edit to the updater-script but it still won't boot anything at all. I cannot take a logcat because it isn't booting anything at all and so there is no adb server.
I presume that you have this running on your Q but if you do then you clearly did not use the ZIP that was provided as that doesn't work. Do you have the system images which you just flashed from the bootloader with fastboot? If so perhaps you could share those so I could have a go flashing those instead and see if it will boot then.

wollac, you are correct in stating that I posted the wrong build (uploaded the wrong zip from my dev folder. However, the build I MEANT to post is booting on my Q, though BT and the Amp are not working yet. I'm a tad scatterbrained with finals, but I am compiling a new build that should hopefully resolve the bluetooth issues at least, and I will upload as soon as it's done.

TF300T Questions

I have a TF300T with the latest firmware installed - JOP40D.US_epad-10.6.1.27.5-20130902. I suffer from the extreme slowdown that I have researched endlessly. I found answers that have said to root and install a custom ROM. I have already unlocked the device using Asus V8 Unlock tool. I get the "Device is unlocked" at boot.
My questions are:
What is the best custom recovery for this tablet?
What rom should I use / do people like the most?
I have found the KatKiss ROM Nougat 7.1. I have also found this ROM located here http://www.teamandroid.com/2015/05/12/install-android-511-cm121-asus-transformer-pad-tf300t-nightly-lollipop-rom/ which from my understanding will give OTA updates.
The process seems complex. I am not a layman, but some of the steps I have found for the process are confusing; like fastboot and adp (or something). I am still looking through forum posts to help me understand the processes involved. The biggest problem I have is finding a custom recovery and custom ROM.
Thank you in advance for any assistance you may be able to give. (I'm still searching on my own as well lol.)

Ok, I got twrp installed, so that question is answered. Now I guess the only thing else about my questions is what ROM should I use? I wish to increase the performance of the device without loosing any functionality. I see the KatKiss ROM I posted doesn't allow recording of video.

BLznFuN said:
Ok, I got twrp installed, so that question is answered. Now I guess the only thing else about my questions is what ROM should I use? I wish to increase the performance of the device without loosing any functionality. I see the KatKiss ROM I posted doesn't allow recording of video.
Click to expand...
Click to collapse
In order to avoid any issues you must be sure to have the genuine Kang TWRP 2.8.7.2 installed from here. There is also md5 available. (https://www.androidfilehost.com/?fid=24052804347781183)
Regarding your second question you are right KatKiss - Nougatella #014 is still in development. Bluetoth and video recording are missing right now. But it's only a question of time.
In my opinion KatKiss - KatshMallow #029 is the mostly perfected rom. (http://forum.xda-developers.com/transformer-tf300t/development/rom-t3237867).
So I would recommend to you to take this one firstly. Please pay attention carefully on the install instruction in post #1. The first install should be a clean one!
Good luck!