Ok so, I was flashing CM7-GX4...everything was going fine until I flashed GAPPS, now I'm stuck at two screens alternating between the CM7 boot animation and the screen that says "Welcome to PC36100", upon this screen loading it quickly restarts the CM7 boot animation, so on and so forth. I am able to get into CWM recovery. Please help.
Thank you in advance.
thats a boot loop, looks like you want to wipe everything and try again
elegantai said:
thats a boot loop, looks like you want to wipe everything and try again
Click to expand...
Click to collapse
What if the PC36IMG file is renamed? I changed the name previously per the instructions of some thread I saw somewhere. Could this be the problem?
well you lost me at the hboot image. The only time i have ever had to use a file like that is when i was rooting my phone.
I also do not use cwm, so i am kinda limited in the help i can provide. Did you wipe your system/data/cache before you flashed cm7?
I wiped everything. I've put the SD card in another phone and renamed it back to PC36IMG...lets see what happens LOL
Renamed file back to PC36IMG...still stuck in boot loop
What exactly are you using the pc36img for?
elegantai said:
What exactly are you using the pc36img for?
Click to expand...
Click to collapse
I'm not using it for anything. It's just there from back when I rooted the phone. I had renamed it a while ago. Everything was going fine, install CM7 GX4 ROM, rebooted, attempted to install GAPPS and thats when I got stuck going back and forth between the two screens. I have put the SD card in another phone and renamed it to the original PC36IMG (figuring since I was stuck at a screen saying Welcome to PC36100 it couldnt find the file or something), and I'm still having the same problems. I've wiped and wiped and wiped using CWM and reinstalled CM7-GX4 several times and am still getting the same bootloop.
I'm running a restore from CWM...hopefully that will take me back to a point where I can do something.
yeah, you dont need the pc36img after you root so that is not the problem. My only guess is that cwm is not wiping everything properly or you are missing a step in the install process. I guess you can try a few things:
See if your cwm recovery is up to date (i know earlier versions had issues clearing out properly, but that has since been fixed)
Start back from the beginning of the install process with that rom. Make sure to wipe data, system, and cache, and go back through step by step (sometimes it is easy to overlook a step). Also i noticed in the rom you are using it says to make sure to flash the wi-max kernel, so make sure you do that.
Lastly, I have never used that rom, but if you do not need 4g you can try flashing the actual cyanogenmod nightlies. They are very stable (its what i am running now), and you can grab the latest nightly from:http://mirror.teamdouche.net and grab the gapps from: http://goo-inside.me (universal package)
Sorry to lay a crap load of info on you, but i just don't know what would cause it. A bootloop (which is what you are experiencing with the going back and forth between screens) basically means something did not install right and is making your phone restart over and over.
elegantai said:
yeah, you dont need the pc36img after you root so that is not the problem. My only guess is that cwm is not wiping everything properly or you are missing a step in the install process. I guess you can try a few things:
See if your cwm recovery is up to date (i know earlier versions had issues clearing out properly, but that has since been fixed)
Start back from the beginning of the install process with that rom. Make sure to wipe data, system, and cache, and go back through step by step (sometimes it is easy to overlook a step). Also i noticed in the rom you are using it says to make sure to flash the wi-max kernel, so make sure you do that.
Lastly, I have never used that rom, but if you do not need 4g you can try flashing the actual cyanogenmod nightlies. They are very stable (its what i am running now), and you can grab the latest nightly from: mirror.teamdouche.net and grab the gapps from: goo-inside.me (universal package)
Sorry to lay a crap load of info on you, but i just don't know what would cause it. A bootloop (which is what you are experiencing with the going back and forth between screens) basically means something did not install right and is making your phone restart over and over.
Click to expand...
Click to collapse
I ran the recovery and got back to an old point. I guess I'll try again! Weird that it happened after flashing GAPPS as everything was fine up until that point. I'll grab the gapps from your source. Thanks!
nooomoto said:
I ran the recovery and got back to an old point. I guess I'll try again! Weird that it happened after flashing GAPPS as everything was fine up until that point. I'll grab the gapps from your source. Thanks!
Click to expand...
Click to collapse
Well, i would only use the gapps from the link i provided if you are going to flash the official cm7 nightlies. I wouldnt mix and match! i surely don't want to cause further problems for you! lol. I was reading over that rom and I am not sure why you would need to reboot between installing the rom and the gapps. But again, not familiar with that version!
Sorry i couldnt help more hope you get it!
elegantai said:
Well, i would only use the gapps from the link i provided if you are going to flash the official cm7 nightlies. I wouldnt mix and match! i surely don't want to cause further problems for you! lol. I was reading over that rom and I am not sure why you would need to reboot between installing the rom and the gapps. But again, not familiar with that version!
Sorry i couldnt help more hope you get it!
Click to expand...
Click to collapse
I used the gapps from your source and everything went fine. Thanks again for the help!
no problemo, glad you got it working!
Related
First let me say...its been awhile since I have posted here, I love the auto search based on the title of a post lol. That is awesome. Needless to say I didn't find anything related to my issue...
Here we go,
I have had my phone rooted forever and a day. I have only ever used fresh roms since It's been rooted. ( about a week after launch ) The issue popped up about a few months or so ago with one of his updates. No matter how i tried to download or install it would always bootloop. I have done the full data, dalvic, cache wipes and got the same results. I figured *f* it and just went back to my nandroid of the old version and forgot about it.
There have been several releases that I have tried from fresh that did the same thing. I figured tonight I would try the synergy rom for something new and to see if my phone would take it. I was using clockwork mod for my recovery. I did a nandroid of my phone and away I went.
I flashed amon_ra since that is synergy's recovery of choice and went through the whole process.
3 hours later...here I am with a phone still stuck in a bootloop when i try the rom and now I learned for some reason that amon_ra nandroid restore is not compatiable with the ones from clockwork that i have on my phone. *quick edit* I have also tried downloading several other roms, and am having the same issues.....even tried redownloading the same roms several times thinking it was a corrupt download or something.
There was one restore available that took me back to what seems to be an unrooted phone. I still have access to the recovery and am able to flash roms, but all the sprint crap is back and I don;t have superuser on the phone anymore.
So there is my story. I am an old hand at flashing and know how to wipe and all that before installing and i seem stuck to use this OG sprint crap for the rest of my contract, unless one of you wonderful phone guru's can point me in the right direction.
~owl
There's a thread here with the SU 3.0
install that, go to menu in the app, make sure that permission is toggled on
HipKat said:
There's a thread here with the SU 3.0
install that, go to menu in the app, make sure that permission is toggled on
Click to expand...
Click to collapse
Well at least i can get SU back on the device...
any more advice as to why the phone is refusing to flash any rom??
Maybe try a superwipe script or wipe everything like boot and all except SD card
Sent From My Pocket
{ParanoiA} said:
Maybe try a superwipe script or wipe everything like boot and all except SD card
Sent From My Pocket
Click to expand...
Click to collapse
+1
I usually wipe everything 3 times in Amon then a superwipe zip after that.
Gotta be clean
YEah, do a wipe of everything except SDCard: and Battery stats, if you're not fully charged. Wipe Cache and Dalvik-Cache a few times each. I don't use superwipes myself, but anyhow, after that, flash a stock ROM. Make a nandroid of it, if your phone boots up fine.
Then go back, wipe everything again and flash the ROM you want to use.
I really want to thank all of you that have taken the time to post some ideas here for me, but as of right now I have had no love from my phone with any of them.
It will flash a radio just fine, flash wimax fine as well, but no love for the ROMS.
Anymore ideas out there??
Hey guys,
glad to say that ive been able to debrick my phone like 5 times in a row successfully which is a weight off my shoulders.
however, once im debricked, rooted, cwm installed, and all .img's pushed i try to flash a custom rom. i've tried every one and i get bootloops every time... they seem to install just fine. very normal timing and everything, no errors. any ideas?
Don't format /data. Are you doing that? Link the steps you're taking when you are in cwm to flash over the rom. Maybe something is amiss.
nope not formatting data. ive been doing wipe cache, wipe dalvik, and format /system.
Man I was in the same boat as you but was finally able to get it sorted this morning. What I highly, highly recommend is starting as fresh and as clean as you possibly can. That is before you do CWM or anything like that restore your phone with the Korean kdz, push all the images (system being last) then make sure you have a bootable, working phone. Also I would recommend using different/new/fresh .img files...I downloaded ones from the unbricking thread and only used a copy of my baseband.img. I had a feeling one of my files wasn't quite right so starting with all new ones may have helped.
Don't try anything from a backup or do a restore or anything-start fresh and make sure everything works as it should. From there do CWM and then do your ROMS. I know you're almost there and its a headache to keep starting from the bottom but do it all one step at a time, in order and you will find success.
Good luck!
good call. i havent been pushing all the .img's. just the three he mentioned above. let me try this for the 80th time. ill let you know how it goes. just curious, do you use the v10f or v10i kdz?
Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.
If i was you i would install the new CWM, once it installs the new CWM it'll work.
gte460z said:
Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.
Click to expand...
Click to collapse
yep i know that part. thanks
Revolution said:
If i was you i would install the new CWM, once it installs the new CWM it'll work.
Click to expand...
Click to collapse
new cwm?? as in the newest version available?does it work on the nitro?
[CWM][24/01] ClockworkMod 5 Recovery For LG Nitro HD
http://forum.xda-developers.com/forumdisplay.php?f=1448
Follow instruction's then try flashing a ROM it should fix your problem.
ive been using cwm... doesnt get rid of the bootloops
mic.mayorga said:
ive been using cwm... doesnt get rid of the bootloops
Click to expand...
Click to collapse
I'm not sure you understand bro, there is a NEW UPDATE
Update your CWM and it'll fix this issue.
I had the same problem for awhile. Had to use the Unbricker:http://forum.xda-developers.com/showthread.php?t=1412367
Followed ALL instructions, including "Restoring Nitro HD partition images" before flashing CWM. After that, no more bootloops and installed Revolutions rom w/out issue. Reboots just fine after.
I used the V10i-the direct download from LG...I think all the other recommendations are spot on but first and foremost get everything squared away with a fresh install of the kdz, all the images (in the proper order), the new version of CWM and then your rom of choice...Hope you're making some progress!
I'm on the new CWM and still have a loop if I reboot. Then I need to restore from CWM to get going again.
The soft brick boot loop I got was caused solely by format /system. I did not format /data.
I went through the whole deal last night and this morning and was able to get a fresh start on everything and am now running the HD ROM and haven't had a boot loop since I got everything back up and running...
I really think starting with the freshest install and making sure everything is functional step by step is where you'll be able to get through all that mess...just stay away from and restores or using any .img files that may have any software glitches as you'll get back to square one every time.
Hope you get it sorted out!
nah bro, i had the new update. no worries tho i pushed all the images in the debrick and fixed it. thanks for all the help guys B)
Tight work-glad you were able to get it straight! Now once you get it where you want make a new backup with Nandroid and CWM and you'll be golden in case anything else happens.
Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks
huydq5000 said:
Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks
Click to expand...
Click to collapse
Go look at the thread "[Solved] Unbricking solution...". Follow it to the T, however, i'd recommend using v10i.kdz rather than v10f.kdz. Definitely try the f version first but if it doesn't work try i. That's what I did. Basically what you're going to want to do is:
1. Restore the phone to a korean image using the v10i (or f) file and the LG software provided and referenced in the unblocking thread.
2. Once booted, root the phone. (specific instructions for v10i are in a thread somewhere linked by [email protected] v10f use either SuperOneClick root or DoomLord v4. Make sure you have adb installed for doomlord.
3. Once rooted use adb to push over stock .img files in this order: boot, recovery, firmware, baseband, system.
4. after the files are pushed boot into phone and root again (optional).
5. Install CWM5 through adb or terminal emulator.
Good luck, let me know if you have any questions and I can go into more detail.
Green lens Defy, UK Unbranded. I've tried everything.
Tried these SBF:
JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_Service1FF
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P019_A010_HWp3_Service1FF.sbf
With these:
update-cm-7.1.0-11-Defy-signed
update-cm-7.1.0-jordan-signed
CM72-20120304-NIGHTLY-Defy
Done eveything in this link: http://forum.xda-developers.com/showpost.php?p=24119414&postcount=12
Whats going wrong? Been at it hours now, and this is not the 1st Defy I've done!
I did make a backup shortly after flashing the 1st SBF, and can still get back on to the standard ROM. But I want CM7.
All help appreciated.
Re flash this sbf
joey_t said:
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P019_A010_HWp3_Service1FF.sbf
With these:
update-cm-7.1.0-11-Defy-signed
update-cm-7.1.0-jordan-signed
CM72-20120304-NIGHTLY-Defy
Click to expand...
Click to collapse
Then follow your link with volume down battery in, wipe data / factory reset,
Then root it with super one click
Then reboot
Then install 2nd init via instructions
Then flash cm7.1 stable
But once you get back into the standard moto software take a while and read the beginners guides
teamwork makes the dream work
Thanks, I appreciate the help.
However, its basically what I already did, but did it again anyway, and same result.
Getting stuck on the blue cyanogen screen. It must be CM7 file, although these are all the same files I'm using from my first sucessful installation.
I remember being stuck at the same point, but not sure how I resolved it.
Do you know if it would be OK to make a backup of the CM7 from my working phone, and install it on this other Defy?
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Edit: OK, tried my last suggestion. Not good. Have a working CM7, but no signal, when I check the IMEI on the phone using *#06#, it shows as all zero's, which may explain the problem.
joey_t said:
Green lens Defy, UK Unbranded. I've tried everything.
Tried these SBF:
JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_Service1FF
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P019_A010_HWp3_Service1FF.sbf
With these:
update-cm-7.1.0-11-Defy-signed
update-cm-7.1.0-jordan-signed
CM72-20120304-NIGHTLY-Defy
Done eveything in this link: http://forum.xda-developers.com/showpost.php?p=24119414&postcount=12
Whats going wrong? Been at it hours now, and this is not the 1st Defy I've done!
I did make a backup shortly after flashing the 1st SBF, and can still get back on to the standard ROM. But I want CM7.
All help appreciated.
Click to expand...
Click to collapse
joey_t said:
Thanks, I appreciate the help.
However, its basically what I already did, but did it again anyway, and same result.
Getting stuck on the blue cyanogen screen. It must be CM7 file, although these are all the same files I'm using from my first sucessful installation.
I remember being stuck at the same point, but not sure how I resolved it.
Do you know if it would be OK to make a backup of the CM7 from my working phone, and install it on this other Defy?
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Edit: OK, tried my last suggestion. Not good. Have a working CM7, but no signal, when I check the IMEI on the phone using *#06#, it shows as all zero's, which may explain the problem.
Click to expand...
Click to collapse
Try baseband switcher app which is in CM itself and try switching to your region
Strictly follow these steps:
INSTRUCTIONS:
1. Flash froyo (SBF using RSD lite)
2. Copy *.zip to sdcard
3. Reboot your device in BootMenu/ClockWork
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the *zip
6. reboot
Refer to the following article for more information:
http://forum.xda-developers.com/showthread.php?t=1033654
Hope this helps!
joey_t said:
Thanks, I appreciate the help.
However, its basically what I already did, but did it again anyway, and same result.
Getting stuck on the blue cyanogen screen. It must be CM7 file, although these are all the same files I'm using from my first sucessful installation.
I remember being stuck at the same point, but not sure how I resolved it.
Do you know if it would be OK to make a backup of the CM7 from my working phone, and install it on this other Defy?
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Edit: OK, tried my last suggestion. Not good. Have a working CM7, but no signal, when I check the IMEI on the phone using *#06#, it shows as all zero's, which may explain the problem.
Click to expand...
Click to collapse
Hold on the above post for a minute,
Enter boot menu,
Go stable recovery,
Wipe data,
Wipe cache,
Wipe dalvik(under advanced)
The rom should boot easy,
Then use baseband switcher (some cm have it installed) choose the frequency to work with your phone ie if the phone was for 850/2100 use a 850/2100 baseband
teamwork makes the dream work
adamo3957 said:
teamwork makes the dream work
Click to expand...
Click to collapse
Well said!!
Thanks for the replies guys. However, I just flashed the standard SBF again after the blank IMEI issue. So back to square one again.
Are you both suggesting I should use the backup ROM from my other phone, then use the baseband switcher to get the signal back?
If so that would be much easier, as I know my backup ROM works fine.
joey_t said:
Thanks for the replies guys. However, I just flashed the standard SBF again after the blank IMEI issue. So back to square one again.
Are you both suggesting I should use the backup ROM from my other phone, then use the baseband switcher to get the signal back?
If so that would be much easier, as I know my backup ROM works fine.
Click to expand...
Click to collapse
That would work fine as long as you are using froyo kernel for both, so my suggestion is this
Root
Install 2nd init
Go to recovery on you working cm defy and back up everything (cache data system boot recovery and only leave pds, )
Copy the images to your blank factory defy,
Restore all Tue images you just made - remember no pds,
Should boot 1st go
Then if your doing it for someone else re enter recovery and wipe data,
All this is done via the 2nd init recovery
teamwork makes the dream work
Thanks, once again I appreiciate your help, just a couple of things in your last set of instructions:
1. Whats pds? Can't see an option to leave that.
2. Tue images?
Edit:
Ok should have at least looked into PDs before I asked.
But Tue images? Still not sure on that.
1st backup off working phone, excluding pds hasn't changed. For some reason, it saying it cannot find system.img, andriod_secure.img and cache.img. But I only copied over the clockworkmod backup folder. I think I saw the android_secure folder elsewhere, so will go back on that.
OK contents of backup folder from working cm7 defy are:
.android_secure.vfat.tar
boot.img
cache.ext3.tar
data.ext3.tar
devtree.img
nadroid.md5
recovery.img
system.ext3.tar
There is no system.img, android_secure.img and cache.img on this folder, hence why the restore cannot find those files.
I'm checking versions of clockworkmod recovery are the same on both phones, thats the only thing I can think is making it different. Checked, same versions.
I seem to be having more sucess, trying my install of cm7, where it gets to the blue logo screen, then running the restore. However, still no signal. I don't seem to have the baseband switcher option in my version. Any direct links to the latest cm7 build, as the one on the link from Rajneeshgadge17, is down.
SUCCESS!
Thanks for your patience adamo3957 and Rajneeshgadge17.
I eventually went for a complete fresh install of everything, downloading the same version of cm7 I already had even, just to check that. Now up and running :thumb:
Now, I just need to sort the other Defy I killed when atempting the macguyver fix!
Download CM7.1.0 from below mentioned link:
http://download.cyanogenmod.com/?type=stable&device=umts_jordan
Follow the same steps as mentioned in the above article ans share the results.
INSTRUCTIONS:
1. Flash froyo
2. Copy *.zip to sdcard
3. Reboot your device in BootMenu/ClockWork
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the *zip
6. reboot
Click to expand...
Click to collapse
joey_t said:
SUCCESS!
Thanks for your patience adamo3957 and Rajneeshgadge17.
I eventually went for a complete fresh install of everything, downloading the same version of cm7 I already had even, just to check that. Now up and running :thumb:
Now, I just need to sort the other Defy I killed when atempting the macguyver fix!
Click to expand...
Click to collapse
Just noticed your post now
I have had Cyanogenmod 7 for some time now, but ever since yesterday it is stuck on the Cyanogenmod boot screen and does nothing. I can get into Clockworkmod Recovery, but I am scared to do anything past that for fear of messing something up. Do you all know something I could try to get my phone back working (It is an HTC Inspire on AT&T)
Thanks
Ellimistopher said:
I have had Cyanogenmod 7 for some time now, but ever since yesterday it is stuck on the Cyanogenmod boot screen and does nothing. I can get into Clockworkmod Recovery, but I am scared to do anything past that for fear of messing something up. Do you all know something I could try to get my phone back working (It is an HTC Inspire on AT&T)
Thanks
Click to expand...
Click to collapse
Do you remember anything that happened/changed between when it was working and when it wasn't? S-ON or S-OFF?
Since you can get into CWM, I would just flash a new ROM. In fact, I would first dirty flash the same ROM over the one you've got first to see if that fixes it. If that doesn't work, clean flash a different ROM.
bananagranola said:
Do you remember anything that happened/changed between when it was working and when it wasn't? S-ON or S-OFF?
Since you can get into CWM, I would just flash a new ROM. In fact, I would first dirty flash the same ROM over the one you've got first to see if that fixes it. If that doesn't work, clean flash a different ROM.
Click to expand...
Click to collapse
What's the easiest way of going about this, I haven't ever done anything past the initial root and flash
Just put the ROM to be flashed on the SD card, it's a zip - and then choose to "install from zip" and navigate to it in Recovery. You could find a superwipe .zip file - which cleans all caches etc - on this forum, and that will give you the assurance that your phone is squeaky clean for when you flash the ROM zip file.
Just make sure your phone is - preferably - fully charged. The only thing that can go wrong is the battery running out while flashing .
If for whatever reason it still doesn't get past the bootloop, re-flash or try flashing a different ROM.
There are plenty of really good ROMs for the HD in the ROM sub-forum, for a rock-solid alternative, look at the Android Revolution ROMs.
Ellimistopher said:
What's the easiest way of going about this, I haven't ever done anything past the initial root and flash
Click to expand...
Click to collapse
Download the ROM (make sure it's the exact same version as the one you first flashed) onto your computer. Get the ROM onto your phone, either by using an sdcard adapter or by booting into CWM and mounting the sdcard on the computer. In CWM, wipe cache and dalvik, then install the ROM zip. Reboot. (If you're S-ON, say so; there are a couple extra steps.)
If that doesn't work, do it again with a different ROM. Also, instead of wiping only cache and dalvik, also wipe system and data. You will lose all your installed apps and saved data.
Sorry, but I can't give exact step-by-step CWM instructions because I don't use CWM.
So all I did was reflash the exact same file that I already had on my SD card, and that worked. Cleared the data/caches and I'm back online. Thanks for the help.
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...