[Q] CM10 trouble installing - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I have the s3 for at&t. I flashed cm10 mod on my phone and when I went to reboot it, it went to the screen CyanogenMod and it just kept going around in circles like it was loading . problem is it never stopped. Phone is rooted and I have clockwordmod as well. this is the CM10 I used... Direct Download: cm-10-20120915-NIGHTLY-d2att.zip. Is the clockwordmod I need??..... Install ClockworkMod Recovery for "d2att". if so how do I get it?? i tried getting on my phone but it didnt work. am I missing something??
Any help would be much appreciated.
Thanks ,
Dan

danbear7777 said:
I have the s3 for at&t. I flashed cm10 mod on my phone and when I went to reboot it, it went to the screen CyanogenMod and it just kept going around in circles like it was loading . problem is it never stopped. Phone is rooted and I have clockwordmod as well. this is the CM10 I used... Direct Download: cm-10-20120915-NIGHTLY-d2att.zip. Is the clockwordmod I need??..... Install ClockworkMod Recovery for "d2att". if so how do I get it?? i tried getting on my phone but it didnt work. am I missing something??
Any help would be much appreciated.
Thanks ,
Dan
Click to expand...
Click to collapse
Take a look here
I would make sure you do a wipe data and wipe cache first. Then install the ROM

You can download Clockwork Recovery (Rom Manager) from the Play Store.
Once installed click "Flash ClockworkMod Recovery" and when it asks Choose your phone (d2att).
Then as kangi26 said, make sure to reboot into recovery and do a wipe before installing the rom.

Forgot to wipe the cache!!! redid everything. works like a charm!! thanks to all for the advice!!!
Dan

Related

[Q] Cache Issue When Wiping Using CWM & SuperWipe

I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?
Same issue with Clockworkmod Recovery
Sorry to say I can't answer your question, but actually just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.
I hate to say it but... use TWRP. It looks and works better. Trust me.
Sent from my SGH-T989 using xda app-developers app
whatiznt said:
I hate to say it but... use TWRP. It looks and works better. Trust me.
Click to expand...
Click to collapse
I trust you but on the Team Win Recovery Project's changelog you can see that it has not been updated in almost a year! CWM is updated much more frequently and also I enjoy having the touch version! Very convenient.
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
jalight27 said:
Just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.
Click to expand...
Click to collapse
Thank you my friend. What you describe is exactly what happened to me. Tell me, what version of CWM Recovery do you have? Were you coming from stock? Which CM9 was it? Nightly, stable?
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Please pardon my ignorance as I am relatively new at all this. How do you downgrade CWM? I am unable to boot the phone into the ROM. Can it be done through Recovery? ODIN?
I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.
Same version as you've got. Was actually coming from Jedi Mind Trick v8 and was going with the nighty. I loaded a backup of my stock ICS, which of course froze during the restore once it got to the cache, but I let it sit for like 15 min or so and then reset it and surprisingly it loaded up fine despite the fact that I had to reset it during the restore. I'm trying to follow up with the advice these two guys gave me on my post (really the same thing they've told you). With my extremely limited knowledge in this field I'm still working it all out and trying to make sure I ask the stupid questions so as not to mess anything up, well at least not too bad, lol.
mintharis said:
I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.
Click to expand...
Click to collapse
Go into rom manager and scroll down to previous versions
VoiD_Dweller said:
Go into rom manager and scroll down to previous versions
Click to expand...
Click to collapse
I don't have ROM manager installed. Does it provide a tar that can be flashed via Odin?
Newer Recovery
Clockworkmod 6 doesn't need the Darkside tools anymore. I had a similar problem but it was causing my phone to lock up. Just try using the regular cache wipe and dalvik cache wipe and see if that works for you.
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.
Pugnap00 said:
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.
Click to expand...
Click to collapse
Can you please provide a link for the 5.0.2.7 tar you flashed?
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
CWM v6.0.1.4 has pretty much made my phone useless. When in Recovery I can't even scroll down or up. I even tried restarting my phone to downgrade but I have no response from my MENU, HOME, BACK or SEARCH button.
WORD OF ADVICE. PLEASE STAY AWAY FROM CWM v6.0.1.4.
EdwardLThompson said:
I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?
Click to expand...
Click to collapse
Simple Solution is that the Cache in your device is large, it has to be cleaned, For this use Darkside cache wipe. It Solves the problem.
suffuciently hungeom
mintharis said:
Can you please provide a link for the 5.0.2.7 tar you flashed?
Click to expand...
Click to collapse
Here you go,
Look at step 6, it will have links to the tar based on your carrier. Its actually 5.0.2.6, works just the same though.
http://theunlockr.com/2011/12/01/how-to-root-the-samsung-galaxy-s-ii-all-versions/
I hope this helps you!
That happened to me as well when I was going to update to CM10. The faq for CM10 says you need to update to a Touch version of CWM which ROM Manager really wanted to install the Touch version. CWM shows it's version 6 and the menus were different but when I was finally able to get a ROM to boot in Safe Mode it reported CWM as being version 5.x. I could not mount or dismount the Cache in CWM. ODIN brought it back to stock but I messed around with the partition checkbox and hard bricked it. Otherwise it looked as tho things would have been ok after using ODIN to start over.
Darkside's wipe wouldn't work (either version) in this case.
screw cwm im going to twrp
ok same thing happened to me..but there are files i need in the phone and i dont think i want to use cwm after this...so can i use odin to flash it to twrp and recover my files through the twrp usb mount?
(lol nvm, i flashed a older version of cwm through odin and then recovered my files then got twrp)
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Like I said in my earlier post had your exact problem and did exactly what was recommend here, and it worked beautifully. Solved all my problems, no residual effects to speak of. Now I can flash my roms in peace.

[Q] Need Help Small Problem

So, been a couple weeks been trying to flash CM10 ROMs, Paranoid, AOKP and CYANO, Everytime i flash I wipe everything as instructed and when it reboots it just hangs on the cyanogem boot image with the wheel spinning and does nothing. Not even a boot loop?! I let it sit for up to a half hour before and still nothing. But I can go and restore my old rom (not CM!) and works great..and if I flash a a new TW rom it flashes correctly.
Any ideas. I am on CWM when I flash. I also tried to flash TWRP and that would not take as well and had to go back to CWM.
Things I would check:
Verify MD5 tags of the roms your flashing when you download
Try wiping cache/dalvik/system and doing a factory reset after you have a successful flash
Question I have for you...
Have you tried unrooting and rooting again?
TWRP and CWM should both work, but have you ran the darkside scripts if using CWM? > http://forum.xda-developers.com/showthread.php?t=1477955
Lastly - I have heard people needing to reflash several times before it "takes" which it sounds like maybe you've tried & I realize these may be very basic things for you but you never know hopefully someone can help the more info you provide.
ldd_recoil said:
Things I would check:
Verify MD5 tags of the roms your flashing when you download
Try wiping cache/dalvik/system and doing a factory reset after you have a successful flash
Question I have for you...
Have you ever successfully loaded a custom rom on this particular phone?.... because you may have improperly rooted
TWRP and CWM should both work, but have you ran the darkside scripts if using CWM? > http://forum.xda-developers.com/showthread.php?t=1477955
Click to expand...
Click to collapse
I am on a custom rom now and everything is fine..but when I try to flash anything other than a Touchwhiz rom it seems to fail. I had paranoid running for a little while but I could not access my external sd so went back to my Jedi Mind Trick rom and everything was fine...so I decided to try a different paranoid thinking the issue was with this specific rom and it would not boot..went back to JMT and then tried aosp cm10 rom thinking and it wouldn't boot.
i have tried everything you have suggested except for the Factory Reset after the flash. Never really check the MD5 though. Might give it a try later on when I get bored with this rom again.
Thanks,
T
Sorry, reread your post now that I have the right context... Try unrooting and rerooting if you continue to have new rom flash issues.
toreone said:
So, been a couple weeks been trying to flash CM10 ROMs, Paranoid, AOKP and CYANO, Everytime i flash I wipe everything as instructed and when it reboots it just hangs on the cyanogem boot image with the wheel spinning and does nothing. Not even a boot loop?! I let it sit for up to a half hour before and still nothing. But I can go and restore my old rom (not CM!) and works great..and if I flash a a new TW rom it flashes correctly.
Any ideas. I am on CWM when I flash. I also tried to flash TWRP and that would not take as well and had to go back to CWM.
Click to expand...
Click to collapse
Solution is Simple.... When it hang in the cyanogenmod boot image with the wheel spinning just switch off -> Go to recovery -> install the DarkSide Cache Wipe.Zip then see the magic.... :good:
srikanth.t989 said:
Solution is Simple.... When it hang in the cyanogenmod boot image with the wheel spinning just switch off -> Go to recovery -> install the DarkSide Cache Wipe.Zip then see the magic.... :good:
Click to expand...
Click to collapse
Thanks, i will give this a try next time i flash...and i'll report back. This happened with a few different roms...this should fix those too!? also, I am pretty sure I ran the Darkside before I did first boot...should I have waited?
EDIT::: THIS WORKED...IT WAS HUNG UP ON BOOT IMAGE..FOLLOWED INSTRUCTIONS ON TOP AND BINGO!!!! I SAW THE MAGIC
toreone said:
Thanks, i will give this a try next time i flash...and i'll report back. This happened with a few different roms...this should fix those too!? also, I am pretty sure I ran the Darkside before I did first boot...should I have waited?
Click to expand...
Click to collapse
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
cluckkillerb said:
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
Click to expand...
Click to collapse
I actually tried this yesterday and it went through the motions and when I restarted into recovery it was just like a blue background with the Team Win on it but never made it past that...so I had to flash back to CWM through Odin to get it to be able to flash again..
cluckkillerb said:
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
Click to expand...
Click to collapse
After doing this try downloading quickboot to boot into twrp recovery, if that doesn't help you might need to flash back to stock/re-root and start from square one =/

[Q] Help, won't boot any custom roms.

After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app

[Q] Help! Stuck in bootloop

Hi guys! Happy New Year!!
I have a problem, I run MiNCO v6 ROM and till yesterday it worked properly, but i found the volume a little bitt low, so i installed Vomer's patch audiov5, available in his modding thread and designed for MiNCO ROMs, which didn't gave me any problem with past MiNCO ROM versions live v5 or v4.
So I went to recovery, installed mod from .zip and rebooted; after 5 minutes the device was still blocked on a screen saying: "Android Upgrade, Application starting..." or something like that; so i decided to remove battery, and put it back again. From this moment the phone is stuck in boot loop, if i turn it on it block on MINCO logo.
I can access recovery using fastboot mode so i tried to restore from a Nandroid i had on the device but recovery said there were no files, i don't know why.
SO what can i do?? I have original ROM zip saved on the memory of the device, maybe i could wipe cache and flash fresh ROM?? Do i need to wipe also data and dalvik?? Other solutions??
Thanks.
Wipe data. Flash a known good rom. I don't see why you needed to make a thread when you could get to recovery.
063_XOBX said:
Wipe data. Flash a known good rom. I don't see why you needed to make a thread when you could get to recovery.
Click to expand...
Click to collapse
Sry if I just wanted to be shure of what I'm doing.

Cyanogenmod 10.1.2 but setup stopped...

Ok I've been reading and reading these threads and have found a lot of great info. Right now my phone is useless so I guess I'm asking for a little more specific info for my current situtation. I used mskip's toolkit to root my phone then followed wwjoshdew's video on how to use goomanager to flash CyanogenMod 10.1.2. Everything seemed to be going fine when I got the spinning blue circle screen then came the "Unfortunately, setup wizard has stopped" and "Unfortunately, the process com.google.process.gapps has stopped". Over and over and over. I can get to download mode and recovery mode but not sure what my next coarse of action should be. This is on an AT&T galaxy s3 originally running 4.1.1. Thanks in advance to any and all help....
I wouldn't use goo manager to flash anything!! U should have flashed straight from recovery, be it cwm or twrp. Did u perform a nandroid backup before u flashed cyan? If so, I would wipe, factory data reset, and install your backup.
Have you tried reflashing Google Apps?
Reboot to recovery, clear cache/dalvik, reflash GApps, clear cache/dalvik again to be sure all is tidy.
Also be sure you have the correct version of GApps; that has messed me up at least once.
Other than that you can always retry the whole process i.e. CM and Apps
Thanks for the replies. I'll try and figure that stuff out. Only reason I've gotten this far was because I was following the toolkit prompts and did the steps in the video as he did them. This is the first time I've tried anything except updating to JB so...
Well, I can't say I've made any progress. I googled correct gapps for cm 10.1.2 and downloaded it but it's like a big collection of stuff that odin won't put in the PDA file spot. I'm not even sure if its the right one. I'm so lost right now. I see all these cwm and twrp recovery files in the toolkit files but not sure if they would help me or not. I know this is fixable since I can still get into recovery and download mode. At this point I would even just go back to stock at least that way I could get rooted again through the toolkit. I'm guess I'm such a noob that I need step by step. I feel like my right arm is missing not having a phone...
Ok I have 2 different versions of gapps that claim to be the right one. I would love to try flashing them to try them out but odin doesn't see them. What am I doing wrong?
Which recovery do u have installed on your phone?
For one dont use odin to flash any custom roms, first download the latest cyanogen mod and gapps, if you need the latest gapps you can get them here. Next you are going to want to boot to recovery and do a factory reset/full wipe then wipe cache/dalvik cache, next go to the top and select load zip from sd card, install cyanogen mod and gapps and reboot the phone.
Ok something different happened this time when I went into recovery. TWRP v2.3.3.1 showed up. I wiped the cache/Dalvik and did the factory reset from there. I have cm-10.1.2-d2att and gapps-jb-20130301-signed ready to copy somewhere. I opened the internal card and saw 8 or so icons that said local disk. so I created a new folder and put the cm and gapps files in there. Does that sound right?
Well that seems to have worked. Rebooted and went through all the google stuff. I'll test everything and see how it works
Glad u got it working!! I usually download Roms straight from my phone, over WiFi of course, and place on the root of the SD card, not in a folder, and flash from there...

Categories

Resources