Related
ive been using nand backup since eris was rooted. I recently started having this error come up when trying to nand b/u and nand restore. i flashed the fresh rom 2.1 and then i ran into issues. got an error on
my screen:
"Error...Run "nandroid-mobile.sh" via adb!"
everything worked fine up until now.
And i dont think its the rom that did this.
lately, all the latest roms ive been using have been having shutdown issues, requiring battery pulls following shutdown. Im not sure if all the batterypulling broke my amon ra, but im stuck with having to reflash the rom when having issues with it. very time consuming, battery draining, and very annoying. anyone else having this issue or any suggestions??
Mime has done that too. I've noticed it when my battery was below 15%. Try connecting to a charger or let your battery charge a little bit.
After I did that I had no more problems.
iflip said:
ive been using nand backup since eris was rooted. I recently started having this error come up when trying to nand b/u and nand restore. i flashed the fresh rom 2.1 and then i ran into issues. got an error on
my screen:
"Error...Run "nandroid-mobile.sh" via adb!"
everything worked fine up until now.
And i dont think its the rom that did this.
lately, all the latest roms ive been using have been having shutdown issues, requiring battery pulls following shutdown. Im not sure if all the batterypulling broke my amon ra, but im stuck with having to reflash the rom when having issues with it. very time consuming, battery draining, and very annoying. anyone else having this issue or any suggestions??
Click to expand...
Click to collapse
yea its most likely because your battery is low, charge it a bit then restore
iflip said:
ive been using nand backup since eris was rooted. I recently started having this error come up when trying to nand b/u and nand restore. i flashed the fresh rom 2.1 and then i ran into issues. got an error on
my screen:
"Error...Run "nandroid-mobile.sh" via adb!"
everything worked fine up until now.
And i dont think its the rom that did this.
lately, all the latest roms ive been using have been having shutdown issues, requiring battery pulls following shutdown. Im not sure if all the batterypulling broke my amon ra, but im stuck with having to reflash the rom when having issues with it. very time consuming, battery draining, and very annoying. anyone else having this issue or any suggestions??
Click to expand...
Click to collapse
ya it usually does that with a low battery .....
only happened to me once ..... but a very wise man told me this was almost always the cause
ive been charged all day. still no luck.. :-(
iflip said:
ive been using nand backup since eris was rooted. I recently started having this error come up when trying to nand b/u and nand restore. i flashed the fresh rom 2.1 and then i ran into issues. got an error on
my screen:
"Error...Run "nandroid-mobile.sh" via adb!"
Click to expand...
Click to collapse
I think I had the "Error : run 'nandroid-mobile.sh restore' via adb!" problem before when trying to restore a rom in recovery, but i think it was because of renaming the folder inside the "nandroid" folder on the sd card.
i didnt rename anything
quick question what recovery are you using?
I had problems similar to this on CLOCKWORKMOD recovery, to the point where i couldn't flash or restore any nand. I even tried flashing root rom and that also failed. when It tried to write boot and the system in failed and then i had to replace my phone because it wouldn't even boot after trying to flash root rom.
using amon ra.
i think im gonna try to reinstall recovery img via adb. any requests to stop me go right ahead.
i tried reinstalling recoery img via adb and still nothing!!!! AARRGH!!!
Sounds lime my issue js rather unique. Doesnt seem like anyone else had this problem yet. Well i guess for now im .sh out of luck.
-------------------------------------
Sent via the XDA Tapatalk App
iflip said:
Sounds lime my issue js rather unique. Doesnt seem like anyone else had this problem yet. Well i guess for now im .sh out of luck.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I had this problem when the memory on my sd card was almost full. I deleted a bunch of zip files and a bunch of the nand backups and it worked fine. I've also experienced the low power and the invalid rename issue too. hope this helps.
That sounds like a solution. Thx. i will trh to free up space on sd. Ive been pretty full for a while tho, but never encountered this msg.
-------------------------------------
Sent via the XDA Tapatalk App
nand restore error run nandoid mobile via adb
I just got this error and simply needed to have power plugged in to complete the restore. Hope this helps.
Well, there's two ways to go about solving this type of problem.
One would be to use the built in functionality of the Recovery menu system to copy the recovery log file (/cache/recovery/log) to your SD card and then - oh, I don't know, maybe look at it to see what error messages are in there? Really super-duper users could even just do a "adb shell cat /cache/recovery/log | more" with the recovery console still running, but that presumes a high level of skill (operating a space bar on the keyboard).
The other way would be to ask a bunch of strangers on the internet to speculate about what the problem might be.
I prefer the 2nd way; it's far less efficient, but much more entertaining. Hours of fun, really.
J/K. Have a look at Amon_RA's announcement post for the Eris, where he says:
Always check recovery.log before posting your issues!
bftb0
i am having the same exact problem with my nexus one. the error: run 'nandroid-mobile.sh restore' via adb. i am a new root user and this is my first time attempting to do any nand restores, and i get that error. is it possible i used the newer recorvery which is not compatible with cyanogen 5.0.7 ROM? i just followed all the links on the rooting guide and said to use all latest files.
my battery is 100% and my sd card has 2gb of free space. i'm really at a loss what to do. thanks.
Verify that there is a folder named nandroid in the root directory of your SDcard. If not, create one. I was having the exact same problem until I did that.
there is definitely a nandroid folder on my sdcard root drive, and inside that folder are 3 backup folders with associated files. i'm going nuts.
you can rename the back up files with names starting with "BDS-". You can't rename the folder directly under "nandroid" in your directory. if you do, you will get the "run mobile.sh" error. you will also get this error if your battery is low or you have no storage left. the folder directly under the "nandroid" folder it is your serial number. if you're having issues, just go to the "other" menu and select "send recovery.log to SD card." then go in and search the recovery.log file on your sdcard for "serialno=" right after that there will be a 12 character string of capital letters and numbers directly followed by lower case letters that are useless for this purpose. Create a folder with the same name as that string (capital letters and numbers only, no lower case) and place your previously renamed backups into that folder and voila! you'll be able to restore them.
My issue never got fixed, but I did try a different memory card, copied over my backups, and now they restore fine. And I did rename them to "stockROM" and they restore just fine. So the name does not matter.
I tried formatting the original memory card then copied all the contents back onto it, and still will not work with nand restores. It took me 5 hours to dump my card and reload it, so some files on that card must be screwing something up. Sucks cause now I'm stuck with this small card and with my music on it now It's full, so I have no room to do anything. Wish I could get my main card working with backups.
Was wondering which recovery everyone likes and why. Been using Ra since my G1 and I love it. (searched around for one of these and didnt see it. Mods delete if there was already one of these polls)
Amon all the way
Sent from my EVO using the Earths core to power my death ray
So...since this brought up...I see that some ROMs don't work with some recoveries? Is that correct? I swear it seems some ROMs only work with clockwork...but then I read all over that clockwork is buggy...or doesn't seem to work for everyone...or something.
I was thinking Amon Ra was the way to go.
I'll follow the answers to this one as well.
sablesurfer said:
So...since this brought up...I see that some ROMs don't work with some recoveries? Is that correct? I swear it seems some ROMs only work with clockwork...but then I read all over that clockwork is buggy...or doesn't seem to work for everyone...or something.
I was thinking Amon Ra was the way to go.
I'll follow the answers to this one as well.
Click to expand...
Click to collapse
Thats true. As far as I know, there have been issues with Clockwork not wiping correctly(I know someone like that)and causing bootloops after flashing. I dont know of any roms that dont work with Ra, but I believe Rom Manager will only work with Clockwork.
Clockwork since it is compatible with ROM Manager.
Clockwork since it has a back option in the menus. It's also updated frequently.
I've been running clock on the evo. I tried putting amon in but I guess I'm too stupid cause when I tried following the directions, I borked the phone good and it took me awhile to get everything back into working order. I could flash it now with rom manager but I'm kinda afraid after the last fiasco.
Sent from my PC36100 using XDA App
I've found that using both have worked for me the best. If I'm running Fresh Rom I will use Amon Ra's but I'll use clockwork for cm6. Its so easy to jump back and forth between recoveries using rom manager its never really an issue. Either way both developers are awesome and their recoveries both have good things to offer
anyway to switch back to Amon? not feelin the Clockwork im too use to it...
seriousblack25 said:
anyway to switch back to Amon? not feelin the Clockwork im too use to it...
Click to expand...
Click to collapse
Use ROM Manager to "flash alternate recovery."
another poll
dglowe343 said:
Was wondering which recovery everyone likes and why.
Click to expand...
Click to collapse
i was wondering the same thing exactly!! So a few days ago i asked the question on the Cyanogen forums... I got a lot of good responses and summarized the comments on the first post... check it out here: http://forum.cyanogenmod.com/topic/2562-best-recovery-for-evo-to-use-with-cm6/
I haven't had one single problem with clockwork recovery.
I like the recovery originally included with toastcfl's root found here. it's very similar to Armon's (don't know if things have to be signed or not), but you use the power button to go back instead of the double-press volume (which I find annoying to do).
I just don't like clockwork as much as the other two, that's just the way it is.
Using Amon Ra because I think it's the only recovery fully compatible with DamageControl.
Not sure of the actual "differences" between it and Clockwork - can anyone clarify?
oblivion0 said:
Using Amon Ra because I think it's the only recovery fully compatible with DamageControl.
Not sure of the actual "differences" between it and Clockwork - can anyone clarify?
Click to expand...
Click to collapse
I'm using clockwork with Damage Control I've had zero problems so far.
I hate Amon recovery... always have to move my ROM downloads to the root of the SD card... forget it 90% of the time and have to reboot to fix it... and that doesn't work so well if I borked my ROM.
I use Clockwork and have zero issues unless I'm trying to autoflash theme updates and such so I have to do those manually. Otherwise no complaints. And no signing issues with Clockwork either.
Amon_RA's recovery FTW!
Well, since rooting 24 hours ago, I've been using Clockwork via recovery boot (not through ROM Manager) and it's worked flawlessly so far. Backed up my rooted stock setup, flashed Fresh, DC, CM6, and then back to Fresh, wiped between every flash, and I've had no problems. Even flashed some Fresh Tweaks in the recovery boot. I actually flashed Amon Ra to see how I liked it . . . and I didn't. Mostly just navigating was a pain with the volume up+down thing, everything else seems like a wash. My only question is whether the Dalvik cache is really being wiped by Clockwork, since it takes half a second to complete when I select the option. I'm going to test it in a few minutes here.
Going to give Baked Snack a run for a while, we'll see how that holds up.
I have wondered that for awhile, silver. It may sound stupid but at least a confirmation in the log messages below would be nice.
Sent from my PC36100 using XDA App
herbthehammer said:
I have wondered that for awhile, silver. It may sound stupid but at least a confirmation in the log messages below would be nice.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Okay, I decided to test. Fired up ADB and booted into recovery from Android. Mounted /data and looked inside /data/dalvik-cache. There was a long list of .dex files. Then I unmounted /data and used the Clockwork menu to wipe the Dalvik-cache (this option is located under the "advanced" menu, NOT just the "wipe cache" option). Re-mounted /data and looked inside . . . and the dalvik-cache directory was gone. It took *slightly* longer than normal when I actually hit the button to wipe it (more like .7 seconds instead of .5), but it does appear that my Clockwork v2.5.0.1 is wiping dalvik just fine. And, of course, when I rebooted back into Android (rooted .6 stock at the moment) it took a long time to boot at the 4G screen, as the cache was being rebuilt. Once I was back in, I checked the /data directory again and dalvik-cache was back and full of .dex files again.
So there. No more speculating, just science.
And if you're ever worried about it, you can just use ADB to wipe the dalvik-cache yourself:
Code:
adb shell
mount /data
rm -rf /data/dalvik-cache/*
Then you can use the Clockwork menu to wipe everything else and flash your ROM. These three commands actually just delete everything inside the dalvik-cache directory, whereas Clockwork appears to remove the directory entirely. Doesn't really matter either way, the system will replace the directory if it gets deleted.
Mmm . . . terminal code.
Hi guys,
I've tried using unrevoked 3.3 on my wildfire, with android 2.1, didn't work - so I tried 3.2 and I got the ClockworkMod Recovery v2.5.0.1 on there, I can boot into that now,
But still not knowing how to root it,
Can someone give me some advice from here, I get the "Internal error" message and can't go any further, but I assume you can manually do it, since I've got the clockworkmod recovery on there,
Toby =)
Soulquarian33 said:
Hi guys,
I've tried using unrevoked 3.3 on my wildfire, with android 2.1, didn't work - so I tried 3.2 and I got the ClockworkMod Recovery v2.5.0.1 on there, I can boot into that now,
But still not knowing how to root it,
Can someone give me some advice from here, I get the "Internal error" message and can't go any further, but I assume you can manually do it, since I've got the clockworkmod recovery on there,
Toby =)
Click to expand...
Click to collapse
if you have clockworkmod recovery then that means you rooted it, just put a custom rom onto your sd card, boot into recovery and install zip from sd card. do a nandroid backup of your rom first.
When I try using Titanium Backup, I get a failed message...
Sent from my HTC Wildfire using XDA App
Okay, I installed busy box and it says it rooted, does the clockworkmod matter what version you have?
Sent from my HTC Wildfire using XDA App
Soulquarian33 said:
Okay, I installed busy box and it says it rooted, does the clockworkmod matter what version you have?
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Nope, you should be fine.
Thank you, I'll let you know how it goes, is Wildpuzzle rom trustworthy? It's been around for awhile right? =)
Yeah wildpuzzle is good, I used to use it.
I had abit of a freak out, I wiped my phone then couldn't load any custom rom =( But now its loading, hoping it works...
I don't know if the rom is loading or not, the screen with the android symbol coming out of the box showed up now and white backgroud with the "HTC quietly brilliant" animation seems to be sitting there forever,
I installed the SUnAaBh v1.1** rom from sc card,
Does this seem right?
First boot takes 10 to 15 min.
You should have done a nandroid backup of your stock rom first, oh well.
If it doesn't boot, do a full wipe, wipe data/factory reset and wipe cache in recovery and flash again.
After like 2 or 3 minutes, the screen goes black then the HTC logo screen comes back on and loads again, makes me think its in a loop and no installed right =\
Do a full wipe and try flash again. If it doesn't work, try a different rom.
Yeah, I did a back up with nandroid then moved the files to my computer incase, they was in a folder called orangeworkmod folder?,
Wipe cache?
Soulquarian33 said:
Yeah, I did a back up with nandroid then moved the files to my computer incase, they was in a folder called orangeworkmod folder?,
Wipe cache?
Click to expand...
Click to collapse
Yes, you should wipe data and cache before installing a new rom. They are all there in recovery.
Okay, yeah - its all good, was just taking time, does wildpuzzle rom have overclocking feature, or is that a application?
Edit: whoops, I meant to post this in Q&A - feel free to move it there if more appropriate.
So the surge in cant mount cache E errors peaked a last week it seems. The problems and solutions were all over the map. Where it came from, what caused it, how people recovered, what they were doing when it all started. Even in the dev forums, it's still a partial unknown. (Good ideas as to how to fix/avoid, but no nailed-down cause other than circumstantial evidence)
So the bottom line from what my still-beginner's eye tells me is that clockwork recovery is borked, it's linked with using rom manager, and previously having used the gfree rooting method, an much of this happens after flashing a new rom (and possibly not wiping every cache?).
In the main gfree thread
http://forum.xda-developers.com/showthread.php?t=858996
it does say that recovery might get borked (and you need to pull the battery to reboot) but you can fix it by reinstalling recovery through clockwork. Well, I never had a problem needing to pull the battery. Well, wait a minute. I did.
What I did:
visionary11 to temp
abd gfree files over
terminal: etc gfree -f, worked fine.
rebooted and say s=off at hboot screen
knew i wasnt rooted yet until i did visionary again, so i did.
black screen for too long, didnt come back as rooted, hung on black screen
Rebooted by taking battery out, did vis11 again and then it returned to the vis screen, and i was su ok in terminal.
now- that time i had to pull that battery, and having previously used gfree - do i have a borked cwm and i dont even know it?
i can boot into hboot then pick recovery, i even made nandroid. but the proof is when you do a restore or flash a new rom, im almost afraid to do a nandroid restore.... Ive just flashed a single time-- RG1.6 (working great)
now, are we supposed to ALWAYS, as a prevantative measure, reflash recovery 3.0.2.4 even if we havent had a problem?
Have those who received this error at one point or another-- have they ALL reflashed 3024 after using gfree to root?
my point is, that warning in the gfree root thread (second red text line) means more to me now that I know more of the moving parts. Is avoiding this soft/hard brick as easy as making it mandatory to reinstall/reflash a fresh CWM3024 after rooting or after every flash of a rom?
I know about pd15immg and part7 working for many people to restore from the error. i also know about the earlier ext3 CWM 2.x recovery version being needed to reflash pd15img with less problems than 3024. but those solutions, while a good bet, are still not shown to be slam dunk.
im just trying to come up with some steps that will almost guarantee avoidance of the cache error loop to begin with...
well for starters, i think that anyone who doesn't do a nandroid backup and then a full wipe before flashing a rom is asking for trouble. I run clockwork 3.0.2.4 and have had ZERO issues. here is what i do:
wipe...
/dalvik-cache
/cache
/data
/system
then...
factory data reset...no issues and i flash too often lol.
According to trueblue_drew he says to do this as far as wiping your stuff...
This is how you should wipe:
Main Recovery Menu:
1. Wipe data / factory reset
2. wipe cache partition
Advanced Recovery Menu:
3. Wipe Dalvik Cache
Mounts and Storage Recovery Menu:
4. Format System
Sent from my HTC Glacier using XDA App
It only happens to gfree users i think. If they reflash recovery after using gfree the issue is basically avoided.
1. i'm not super focused on the wiping part, so i dont want to make this thread into a wiping thread, although it is important. im trying to wrap my head around the entire gamut of causes and get some main ansers that are solid
2. "reflash recovery after using gfree the issue is basically avoided.". I'd like to get some data on this, and I'm hoping that people who DID reflash CWM after gfree ( reflashed it a second time after wiping everything and flashing a rom-- if they STILL got the error. I'm betting that only a small minority flashed CWM recovery TWICE. I'm hoping to find out if any of them STILL got the error ( i'm hoping not). I"m also wondering how many didnt reflash CWM (because there was nothing acting up to cause them to do so) but they still may have a latent problem there, waiting to creep up after some incomplete data wipe, or some SD card anomaly, and then surface...
I had the error once & had to replace the phone.. I made the mistake by usin recovery 3.0.0.5(this was before 3.0.0.6 & 3.0 2.4 came out)to go bck to a froyo rom but only because cm7 rc2 wasnt allowin me to do anythin with the phone(all forcecloses) so booted recovery wipe everythin & flashed froyo rom & there goes my phone.Fried.lol my mistake for not READING before flashin.. Anyway ive been readin lately that people have been tryin to restore apps & data with titanium,big no-no,with restorin data frm other roms...
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
Kernel-ckisgen-smartass-v1.1
I pulled that same mistake also when CM7 alpha previews first came out, I had the 3.0.0.5 recovery, installed the preview to test out,and then I restored a nandroid backup of my Iced Glacier rom and instead of being stuck at the mytouch screen or not booting up, I just got bootloops until I flashed the froyo capable version of Clockwork through adb. Mind you, that's when I had used the first method of gaining S-OFF. I haven't been using gfree method until I got this, my third replacement and first method wouldn't stick so I ended up using gfree.
I'm soo leaning over the gfree method being the culprit and ****ing up the paritions.
I have the same thread over in the general section and user "_ice_" said that gfree also alters you dev partition block which can also cause problems.
I'm also very scared to flash roms, I've tried flashing the new virtous rom the other day, my heart just dropped after it got stuck at the mytouch screen for 5 minutes, i wiped everything, and it still wouldn't boot, I did a nandroid it wouldn't pass the mytouch, obviously I could still enter the recovery so I knew I was good and had no errors about not being able to mount. I just flashed CM7 all over again after wiping system, data, cache, dalvik etc and then advanced restored data and it booted back up.
Here is what i would say.
To avoid these issues, do these things:
1. If you used gfree, reflash cwm recovery at least once. Preferably twice to make it stick.
2. If you used the visionary method with root.sh, don't worry about it as much. Reflashing cwm recovery isn't required, but it can't hurt.
Because of this I would recommend the root.sh method unless you want carrier unlock.
Sent from my HTC Glacier using XDA App
What if the root.sh method doesn't stick? Many have said if it doesn't work twice, then do a factory reset.
I'll be unrooting and trying the root.sh method again, and I'll update this thread as well as mine with how I did it and a step by step tutorial. Even though we have one, I feel like its vague and doesn't give much advice.
And also, this has been happening with G2 users as well, G2 users are looking into it and seems as there is a batch of chips that are bad and get corrupted after a while. That's just a possibility as what about the users who aren't rooted and or rooted with root.sh.
And also, those users were rooted via gfree. I'm going to read the logs from the irc channel and post a summary on my thread later on with my findings.
Sent from my HTC Glacier using XDA App
kimbernator said:
Here is what i would say.
To avoid these issues, do these things:
1. If you used gfree, reflash cwm recovery at least once. Preferably twice to make it stick.
Click to expand...
Click to collapse
What do u mean by reflashin cwr? Sorry for the dumb question..
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
Kernel-ckisgen-smartass-v1.1
Rom manager, and the top will say current recovery, click on it, confirm mytouch 4g, and then it'll flash. But the thing is, we still haven't been able to rule out and say that the recovery is causing this problem.
Sent from my HTC Glacier using XDA App
xdviper said:
Rom manager, and the top will say current recovery, click on it, confirm mytouch 4g, and then it'll flash. But the thing is, we still haven't been able to rule out and say that the recovery is causing this problem.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I thought that was what that meant lol.. I been on 3.0.2.4 since day 1 it came out & havent ran into those nasty forcecloses then the dreaded error YET.. Before I flash a rom now I always reflash recovery,then power off phone & go into recovery manually,then I wipe by 1st wiping data then cache then dalvik then format system(i do this 2 or 3 times dependin what rom im gonna flash)then I flash the rom..Another thing I never do is restore apps,i rather just dwnload them again..I dnt do nandroid restores cause I dnt trust it but always do bckups(would only nandroid restore if ABSOLUTELY have too) With my other mytouch that I screwed up,i wasnt careful enough now I make sure I have an empty phone before I flash
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
Kernel-ckisgen-smartass-v1.1
Funny, right after I posted this, bam!, like 3-4 threads appeared in various places talking about variants of this. This is what I was trying to improve upon, but oh well, we'll jump around from thread to thread I guess...
Ok, so to start off, I have resolved this, I am just trying to find out why it happened to prevent future occurrences. I was running Calkulin's EViO 3 v1.0, HBOOT 0.76, 2.15 Radio, Stock Kernel.
So here is what happened that led up to the problem. I had just downloaded the Latest amazon App of the day (x-Scope browser pro), and used the Reboot app that comes prepackaged with Calkulin's rom to reboot the phone. Upon restarting the phone got hung at the HTC EVO 4G screen (I let it sit here for about 15 minutes). My thought was ok, something is wrong with this app. So I booted into recovery to attempt to fix the problem.
Upon booting into recovery (Ra Recovery 2.3), I was greeted with
E:\ Can't mount CACHE:recovery/command
E:\ Can't mount CACHE:recovery/log
E:\ Can't mount CACHE:recovery/log
It took several minutes for these 3 errors to process on the recovery screen, every time I navigated to a new menu they would appear again. The first thing I did was wipe my Cache, and Dalvik. This removed the errors from the recovery, however the phone still wouldn't boot. So I ran VR_Superwipe and restored my CM7 nandroid. All is good now, however I would really like to know what caused this to happen in the first place.
I tried to google it, however it appears to be a very uncommon error to get, and of the posts I found with the same error people claimed it was unrecoverable and they had to run the RUU to fix it(This was not the case).
Somehow, someway, I believe either by the install of the app, and/or you had a corrupted rom install and that you just had bad timing! I've had the same situation happen to me.
Sent from Looney Tunes Central!
tazman1963 said:
Somehow, someway, I believe either by the install of the app, and/or you had a corrupted rom install and that you just had bad timing! I've had the same situation happen to me.
Sent from Looney Tunes Central!
Click to expand...
Click to collapse
Appreciate the reaponse. Yeah that seems to be what it looks like. I've been back on cm7 since that post with zero issues.
Sent from my PC36100 using Tapatalk