Related
Hello all just bought a new Samsung Galaxy SII from craigslist already rooted with 4.0.3 Jedi Mind Trick. After reading for what seems 4-5 hours i have been trying to put together how to properly without bricking switching it to 10.0.0 Stable as i use to use Cyanogenmod 2-3 years ago on my devices. Seem alot of things have changed and there is a cluster**** of stuff out there now. If you could direct me to a how to or show me how to do it i would greatly appreciate it!
Thanks all!
Assuming you have nothing personal to back up that you can't just download from google play or your google account again: download cyanogen 10 and it's gapps. reboot into recovery mode. factory reset, wipe data, wipe system, wipe cache, wipe dalvik. pick the install zip from sd card or so option, browse to cyanogen, then install gapps the same way. wipe dalvik again and reboot.
I was thinking of doing this myself JMT to CM10. I didn't think there was anything special to do same as flashing from any other ROM to CM10. If there is a special requirement I would think they'd post in in with the ROM post information.
Alawishis said:
I was thinking of doing this myself JMT to CM10. I didn't think there was anything special to do same as flashing from any other ROM to CM10. If there is a special requirement I would think they'd post in in with the ROM post information.
Click to expand...
Click to collapse
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
melvinator said:
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
Click to expand...
Click to collapse
honestly - i backed up everything to my external and then formatted the internal when i went from TW to AOSP for the last time. well worth it. nice folder clean up and then you can just manually take all the stuff you want back.
and you should just be able to odin on cwm or twrp - then flash the rom of your choice.
new ion? said:
honestly - i backed up everything to my external and then formatted the internal when i went from TW to AOSP for the last time. well worth it. nice folder clean up and then you can just manually take all the stuff you want back.
and you should just be able to odin on cwm or twrp - then flash the rom of your choice.
Click to expand...
Click to collapse
trying to look up how to do that now .... Searching the forum now... Might you be able to tell me real quick how? I already Downloaded the 5.2 file they suggest to use but can't find a working toturial that is just for flashing the cwm.
melvinator said:
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
Click to expand...
Click to collapse
If you get stuck at the boot logo, it's called a soft brick. You don't have to use ODIN or go back to ICS. Just make sure the ROM zip you downloaded isn't corrupt (check the size/m5d if possible), wipe everything, and reboot into recovery to try installing again.
arcsine said:
If you get stuck at the boot logo, it's called a soft brick. You don't have to use ODIN or go back to ICS. Just make sure the ROM zip you downloaded isn't corrupt (check the size/m5d if possible), wipe everything, and reboot into recovery to try installing again.
Click to expand...
Click to collapse
I already used Odin to go back to 2.3.5
Btw I appreciate the help
My woman's is waiting that I fail to say I told you so -_-
melvinator said:
I already used Odin to go back to 2.3.5
Btw I appreciate the help
My woman's is waiting that I fail to say I told you so -_-
Click to expand...
Click to collapse
You won't fail. Follow the guidelines step by step. Print it out, make notes. Anything. Read. The step by step guide works... that'll get you with cwm. Then, you can flash the zip you will put on your phone... either a SU zip or just a rooted ROM. Follow flashing instructions.
Just realized - you'll be way better off if, once you have cwm on, just format the internal ONCE YOU HAVE A ROM ON AN EXTERNAL SD CARD. then flash CM10. THEN you'll have a fresh AOSP install.
Sent from my SAMSUNG-SGH-T989 using xda premium
new ion? said:
You won't fail. Follow the guidelines step by step. Print it out, make notes. Anything. Read. The step by step guide works... that'll get you with cwm. Then, you can flash the zip you will put on your phone... either a SU zip or just a rooted ROM. Follow flashing instructions.
Just realized - you'll be way better off if, once you have cwm on, just format the internal ONCE YOU HAVE A ROM ON AN EXTERNAL SD CARD. then flash CM10. THEN you'll have a fresh AOSP install.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
melvinator said:
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
Click to expand...
Click to collapse
Go back, format system, and then reinstall.
Sent from my SAMSUNG-SGH-T989 using xda premium
Update your recovery to twrp or cwm 6+ and don't use dark side scripts
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Please excuse my harshness but this is not as hard as many make it seem. I would say if it takes you more than a couple attempts maybe it is just not for you. I only say this because I would hate to see you mess up your phone. Now if you think a bootloop is a brick then we need to do things at a slower pace with you.
If you already have your phone rooted then
1.download goomanager from the playstore and then
2.open it up and allow it to grant permission from CM
3.hit menu button while goo manager is open
4.click on install OpenRecoveryScript
5.let it do its thing
6.reboot into your new TWRP recovery
7.Wipe/Data Factory Reset
8.Flash Rom
9.Flash Gapps
10.Reboot
You can throw in a backup of files somewhere in there if you like.... Your choice
melvinator said:
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
Click to expand...
Click to collapse
I had a bootloop when using CWM v6.0.1.5. So a friend of mine told me he had success with CWM v6.0.1.5 Touch. So I switched to the touch recovery and... SUCCESS.
Here's the link to CWM touch and non-touch:
http://forum.xda-developers.com/showthread.php?t=1893464
A boot loop could mean a bad download or bad flash but it is most definitely NOT a bricked device. All you needed to do was get a fresh download and move it to your SD card by mounting it in recovery. Then, wipe EVERYTHING but the SD. EVERYTHING. Then flash the ROM, Gapps and whatever radio. I go from CM to AOKP to other random TW roms all the time and never have issues.
The 2 best recoveries are twrp or my favorite because I'm used to it is cwm 6.0.1.5. http://forum.xda-developers.com/showthread.php?t=1844637
Also if your phone boot loops don't freak out' just either reboot to see if that works out first and if not reboot into recovery. Also with these new recoveries do not use dark side scripts.
Factory reset
Format system
Format cache
Format data
Flash ROM
Flash gapps
Reboot and enjoy
Sent from my SAMSUNG-SGH-T989 using xda premium
This did it!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Sorry for the necro on the thread, but I didn't want it to be stated I didn't look around some either.
I am going from JMT to CM and want to make sure it's as seamless as possible. I use CWM and usually usually use darkside complete wipes, but I read in a previous post not to use darkside. Is there a reason for this? I can't see why this wouldn't work as it's just a wipe.
Also I use Titanium Backup. Is it possible to backup my apps and data and restore them since its not TW any longer? I want to be able to restore as much of my data as possible and make sure I don't lose it.
P.S. - If thread necroing is not appreciated, I apologize.
Hey everybody.
I used to flash all sorts of roms on my old galaxy vibrant but I bought a new t989 a few months ago and I want to go to a custom from the stock tmob bloatware infested ICS. I already rooted via odin and installed clockwork recovery, which comes up just fine with the usual volume and power combo so i'm good there.
My question is should I flash my first rom (probably jedi mind trick 5 or x1,or if anyone knows a daily driver ready jelly bean??)
via clockwork mod like on my vibrant? or do I use twrp which I also have via goo manager? I prefer cwm because I am familiar with how to wipe cache, reset and flash with it but I can't figure out why some mods recommend one or the other.
Also,
I keep seeing some roms that come with a radio zip and was wondering if all roms require this or is it just certain roms?
Thanks in advance for any help. I just don't want to wreck my phone the first time. Remember, I've flashed a million times on my vibrant but never on my t989 so any pointers or heads up would be appreciated.
Get darkside wipe scripts (both wipe cache and super wipe)
Go ahead with the Jedi X1 ROM its very stable and fast as hell
But if you want Jelly Bean I recommend Galaxy SBean v8 or Liquidsmooth rc8 they're the most stable JB ROMs from what I experienced
Remember to always wipe dalvic cache and fix permissions (darkside cache wipe) after flashing a new ROM
After you flash your ROM and Gapps then boot that's when you can flash kernels, mods, and apk's so it would have a lesser chance of a soft brick
Happy Flashing!
Sent from my SGH-T989 using xda app-developers app
arthurgreeeen said:
Get darkside wipe scripts (both wipe cache and super wipe)
Go ahead with the Jedi X1 ROM its very stable and fast as hell
But if you want Jelly Bean I recommend Galaxy SBean v8 or Liquidsmooth rc8 they're the most stable JB ROMs from what I experienced
Remember to always wipe dalvic cache and fix permissions (darkside cache wipe) after flashing a new ROM
After you flash your ROM and Gapps then boot that's when you can flash kernels, mods, and apk's so it would have a lesser chance of a soft brick
Happy Flashing!
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Cool. Thanks for the reply. I went and grabbed super wipe and cache wipe. So essentially, I just put those two on my sd and flash like I do a rom zip from recovery and then flash the rom itself and do a darkside cache wipe after new rom is installed before restarting and booting for the first time? Do I still need to do factory reset/wipe or is that part of the scripts? I have the goo app so I can use twrp instead since it's recommended for almost all roms I will be installing. Any major reason why, besides that it has touch function and backup renaming? Is it safe to install from the goo app on stock rom?
I think I will probably try one of the jellybean roms you suggested. I just didn't want random reboots, and I heard that's an issue with jelly bean roms but I think that might have been specific to aokp ones or something. Occasional FCs aren't too big of a deal though.
One other thing though... how do I fix permissions? I kept reading about that but never did it. Do you mean in recovery or under superuser?
how to properly flash a rom
http://forum.xda-developers.com/showthread.php?t=1926754
just follow that and you should be fine.
you can fix permission in recovery. its under advanced in cwm and twrp.
merrygocow said:
how to properly flash a rom
http://forum.xda-developers.com/showthread.php?t=1926754
just follow that and you should be fine.
you can fix permission in recovery. its under advanced in cwm and twrp.
Click to expand...
Click to collapse
Ok thanks. He seems to recommend not using the darkside scripts. I have a slightly older CWM 5.0.2.6 that I did via odin BTW so do I fall into the 'don't' use darkside category or does he mean anything after 5.0.2.7? I don't mind wiping cache and dalvik manually and doing all the formats if that's the case.
Do I fix permissions after I have booted the rom and waited 10 mins and restarted back into cwm or before I boot it for the first time?
benjmiester said:
Ok thanks. He seems to recommend not using the darkside scripts. I have a slightly older CWM 5.0.2.6 that I did via odin BTW so do I fall into the 'don't' use darkside category or does he mean anything after 5.0.2.7? I don't mind wiping cache and dalvik manually and doing all the formats if that's the case.
Do I fix permissions after I have booted the rom and waited 10 mins and restarted back into cwm or before I boot it for the first time?
Click to expand...
Click to collapse
I usually do it after flashing. And you don't need to do it every single time. Also, there's no need to follow everything down to the letter when you flash, wipe cache/dalvik/factory reset/wipe system/fix permissions/sit for 10 mins/reboot/reboot again/etc. Flashing is like cooking. As long as you don't deviate too much from the recipe, you'll get edible food (or a working ROM). If it doesn't work out, just toss the food out and try again (softbricked phone, reflash). If you try something stupid, you'll set your kitchen on fire when you don't have insurance (comparable to hard bricking your phone).
I usually wait till I've restored all my apps before fixing permissions, and then sometimes I don't if everything is working fine. As for recovery, I know you're familiar with CWM, but I'd recommend spending some time using TWRP. It's really great. You don't need the scripts with TWRP, but since TWRP lets you cue up zips, you can set it to do super wipe, ROM, gapps, and cache wipe all in one go. Kinda cool. And if you're itching to try jelly bean, AOKP JB milestone 1 is stable and smooth. There are even a couple custom kernels for it and CM10 (which has also reached a stable version, though I haven't tried it).
Sent from my beastly Galaxy S 2.
Dark side super wipe and cache wipe work perfectly on 5.0.2.6! That's how I got PACman ROM on my phone. I didn't bother with fix permissions. Well, I would say don't worry unless the instructions specify to do so.
Either way, I like CWM because I used it on my Samsung Galaxy Ace. Its just the wipes are broken for this phone so the scripts have to be used and work perfect. Happy flashing!
Sent from my SAMSUNG-SGH-T989 using xda premium
benjmiester said:
Ok thanks. He seems to recommend not using the darkside scripts. I have a slightly older CWM 5.0.2.6 that I did via odin BTW so do I fall into the 'don't' use darkside category or does he mean anything after 5.0.2.7? I don't mind wiping cache and dalvik manually and doing all the formats if that's the case.
Do I fix permissions after I have booted the rom and waited 10 mins and restarted back into cwm or before I boot it for the first time?
Click to expand...
Click to collapse
no it's fine to use the scripts w/ cwm 5. just don't use the scripts on cwm 6. that's what he meant.
i usually fix permission after the first reboot & waiting 10-15 mins.
i second the twrp recommendation...however if you're flashing something old, then cwm is the way to go. i haven't had any problems flashing anything in cwm. the latest twrp however failed me after i tried to flash a gb theme for jugg lol.
merrygocow said:
no it's fine to use the scripts w/ cwm 5. just don't use the scripts on cwm 6. that's what he meant.
i usually fix permission after the first reboot & waiting 10-15 mins.
i second the twrp recommendation...however if you're flashing something old, then cwm is the way to go. i haven't had any problems flashing anything in cwm. the latest twrp however failed me after i tried to flash a gb theme for jugg lol.
Click to expand...
Click to collapse
Ok, just wanted to make sure on that one.
Thanks for all the input everybody. Hopefully I will get a chance to do my flash over the holiday. I plan on going with the Sbean V8. Really all of the roms out look excellent but this one looks good for a JB daily driver. I went ahead and downloaded Jedi X1 too though in case the sbean doesn't work out for whatever reason. I have to tether my phone at home for internet so I thought it might be good to have a backup just in case PDAnet doesn't want to work.
Is twrp ok to install from Goo manager on my stock rom or should I flash a new rom and then use it from then on? I just want to make sure it won't conflict with the stocker or the CWM that I have on it already.
benjmiester said:
Ok, just wanted to make sure on that one.
Thanks for all the input everybody. Hopefully I will get a chance to do my flash over the holiday. I plan on going with the Sbean V8. Really all of the roms out look excellent but this one looks good for a JB daily driver. I went ahead and downloaded Jedi X1 too though in case the sbean doesn't work out for whatever reason. I have to tether my phone at home for internet so I thought it might be good to have a backup just in case PDAnet doesn't want to work.
Is twrp ok to install from Goo manager on my stock rom or should I flash a new rom and then use it from then on? I just want to make sure it won't conflict with the stocker or the CWM that I have on it already.
Click to expand...
Click to collapse
--Update--
I got Sbean v8 installed and working just wonderfully! I used CWM for my install with the darkside superwipe and cache wipe scripts. Everything went fine and i'm very happy with the new rom. Thanks everyone. I hope this thread will help any other first flashers in the future.
I searched and looked at other threads with people having the same problems, but none helped, and none of those threads had an OP with the Galaxy S3.
So here's the thing, I got rooted yesterday, and it was all good. Then today, I flashed the LiquidSmooth ROM and GApps with ROM Toolbox, and it went fine. Then I decided I wanted to try a different one, so I flashed to my backup, and that went fine. So I downloaded and put both the PACman ROM with GApps 4.1 from like 12/12, and RootBox with the newest 4.2 GApps onto my internal SD. However, I'm using ROM Toolbox, and when I added RootBox and the 4.2 GApps to the queue, in the right order, and told it to install them, and to wipe the devik cache (I think that's what it's called) and to delete all the data and stuff like you are supposed to, it booted into recovery, wiped the data, and then just stopped. So I had to restore to my backup, which the newest one vanished, so I had to use the day old one.
Next I booted into recovery, to manually add the files myself, however, they weren't there. The only thing that showed up was the old 4.1 12/12 GApps, and nothing else. I then tried to install PACman and the 4.1 GApps from ROM Toolbox, but it did the same thing, and I had to restore to my back up.
Can anyone maybe shed some light to why the ROM's aren't coming up?
When you looked for the ROMs in TWRP, which directory did you look in? Did you download the ROMs via ROM Toolbox?
Sent from my SGH-T999 using xda app-developers app
GhostIsBaked said:
When you looked for the ROMs in TWRP, which directory did you look in? Did you download the ROMs via ROM Toolbox?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I looked in the sdcard directory I'm pretty sure. And I just downloaded RootBox from ROM Toolbox, and tried to install it, but it did the same thing and didn't work.
My phone only had like, 35% battery when I did this, could that be a problem?
NorNichols said:
I looked in the sdcard directory I'm pretty sure. And I just downloaded RootBox from ROM Toolbox, and tried to install it, but it did the same thing and didn't work.
Click to expand...
Click to collapse
If you're going to manually flash it through recovery, Root box should be in directory /sdcard/romtoolbox/download/ or something similar since ROM toolbox creates its own folder
Also when you say it just stops, what do you see on your screen?
Sent from my SGH-T999 using xda app-developers app
Well, if I start it through ROM Toolbox, it reboots into recovery, and then says like, wiping data or something similar, and then it goes back to the TWRP home screen, and then if I boot back into the system it's just stock, and then I have to restore to my backup.
And if I flash it manually, wont' it not matter where it is, or isn't it supposed to be in the root of the sdcard? Like, I can see if I was doing it through ROM Toolbox, but when I do it manually, it shouldn't matter, right?
Okay, so I just tried again, and it the last thing it says is (this isn't word for word, closest I can remember) Something cash make4ext.something or something close to that. Then it just goes to the home screen of TWRP.
Okay, so this is what just happened, I went to install LiquidSmooth again, and it said, Unable to locate zip file '/sdcard/romtoolbox/downloads/blahblahblah(doesn't show full directory)
E: Error installing zip file
Checking for MD5 file
E:No MD5 file found
Error flashing zip
NorNichols said:
Well, if I start it through ROM Toolbox, it reboots into recovery, and then says like, wiping data or something similar, and then it goes back to the TWRP home screen, and then if I boot back into the system it's just stock, and then I have to restore to my backup.
And if I flash it manually, wont' it not matter where it is, or isn't it supposed to be in the root of the sdcard? Like, I can see if I was doing it through ROM Toolbox, but when I do it manually, it shouldn't matter, right?
Okay, so I just tried again, and it the last thing it says is (this isn't word for word, closest I can remember) Something cash make4ext.something or something close to that. Then it just goes to the home screen of TWRP.
Okay, so this is what just happened, I went to install LiquidSmooth again, and it said, Unable to locate zip file '/sdcard/romtoolbox/downloads/blahblahblah(doesn't show full directory)
E: Error installing zip file
Checking for MD5 file
E:No MD5 file found
Error flashing zip
Click to expand...
Click to collapse
What version of TWRP are you on?
Try flashing it through TWRP without using toolbox
Download liquid smooth
Download
Steps:
1.Boot into recovery
2.create backup if needed
3.wipe dalvik cache
4.wipe cache
5.wipe factory reset
6.wipe system
7.install- Select the ROM .zip and install
8.Install the 4.2 gapps (12-12)
9. Reboot system
Sent from my SGH-T999 using xda app-developers app
Well actually, I wanted to try the PACman ROM next, so could I just download that and do all the same things, but with that, and instead of the 4.2 GApps, use the 12/12 4.1 GApps?
Also, I'm using 2.3.3.1, and I see that there is a newer one. Can I just flash that one over this one using ROM Toolbox?
NorNichols said:
Well actually, I wanted to try the PACman ROM next, so could I just download that and do all the same things, but with that, and instead of the 4.2 GApps, use the 12/12 4.1 GApps?
Also, I'm using 2.3.3.1, and I see that there is a newer one. Can I just flash that one over this one using ROM Toolbox?
Click to expand...
Click to collapse
Yea but make sure it's specifically for this device (d2tmo/sgh-t999)
The 12-12-12 gapps are 4.2 which are the correct ones to use for PAC Man as well.
DO THIS FIRST
Easiest way to update it is to download GooManager from the playstore. Once, installed, press menu button and install the open recovery script. Latest is 2.4.1.
Sent from my SGH-T999 using xda app-developers app
rnedkle and
It's still not there, I dragged and dropped it into my phone on my computer, but I don't see it. GApps is there, but not the ROM.
I'll try GooManager now, just weird that ROM Toolbox was working earlier and so was TWRP, but now TWRP can't find the ROM and ROM Toolbox can't install things. I went from thinking, wow this isn't hard at all, to, why won't this work! I'll download GooManager in just a bit, my phone is restoring to a backup.
NorNichols said:
It's still not there, I dragged and dropped it into my phone on my computer, but I don't see it. GApps is there, but not the ROM.
I'll try GooManager now, just weird that ROM Toolbox was working earlier and so was TWRP, but now TWRP can't find the ROM and ROM Toolbox can't install things. I went from thinking, wow this isn't hard at all, to, why won't this work! I'll download GooManager in just a bit, my phone is restoring to a backup.
Click to expand...
Click to collapse
OK. I'm gonna catch some sleep for a bit. I'll check back in the morning. Hope everything goes alright man :thumbup:
Sent from my SGH-T999 using xda app-developers app
GhostIsBaked said:
OK. I'm gonna catch some sleep for a bit. I'll check back in the morning. Hope everything goes alright man :thumbup:
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Okay, I appreciate the help. Sleep well.
For anyone who see's this next, just tried GooManager, also didn't work, so I'm pretty much going to give up for the rest of tonight and see what any of you have to say tomorrow. This is a bummer, but oh well, it's just weird that it was working fine and now it won't. I'm going to bed.
You putting these on intsd or extsd? You can't see them through TWRP, the phones file browser, or the computer? Unmount/remount the extsd in Storage settings.
Don't flash through an app. Flash things manually through recovery. If you always use an app to flash for you, you don't learn how to fix problems when you run into them.
You can Odin TWRP from my signature (hopefully you have Mobile ODIN), or here's a zip: http://db.tt/0SzQ0aK7
I bet all of your ROMs are still on your phone. The latest JB creates partitions in your memory. These partitions are for multiple users. Your problem is amplified by having an old recovery. You can locate all of your stuff by going to your memory and going through the folders that start with emulated/0. The latest recovery will fix this issue and you'll be able to use ROM toolbox to flash.
GBP85 said:
I bet all of your ROMs are still on your phone. The latest JB creates partitions in your memory. These partitions are for multiple users. Your problem is amplified by having an old recovery. You can locate all of your stuff by going to your memory and going through the folders that start with emulated/0. The latest recovery will fix this issue and you'll be able to use ROM toolbox to flash.
Click to expand...
Click to collapse
How do I get into the memory to find emulated/0?
Edit: I flashed CWR, and it worked just fine...but then I decided I didn't like the PACman ROM, so now I'm back to restoring back to normal...I guess next I'll try Carbon or Rootbox.
Edit2: Aww dangit, guys I'm a failure. It's stuck on the Samsung logo after you pass the tmobile one, so now I am back into recovery and reset everything and formatted and stuff, and now I'm trying to restore from the backup again...I think if I fix it, my flashing ROM days are done for awhile.
Edit 3: Ended up using Odin to get a rooted stock build on there, then downloaded ROM Toolbox, flashed TWRP, put the backup back on my phone since I have a copy of it on my computer, restored, and now we are all good.
Hello! I have managed to root my phone, but I got the set up wizard message and the gapps error. After a google search it told me I had the wrong version of gapps. However, when I go to the official gapps page, the download for cm 10.1 only works with 4.2.2 and not 4.1.2. The one for cm 10.0 is for 4.1.2, but on the hercules downloads page, the 10.1 stable release is already out (that's the one I used!). Does this mean I have to run 10.1 without gapps, or downgrade to 10.0 if I want gapps?
Trust me, I have searched for this. Any help would be appreciated.
if you are on 10.1 grab the first one on the page http://goo.im/gapps also double check make sure you have no market installed if you do then you dont need any gapps install everything from the market
Alright
Ok, I'm gonna try that. +1 thanks for you. Man, I'm such a noob. :crying: :crying:
Bro all good we (I) was all there gotta start some where :thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Roulette
krazierokz said:
Bro all good we (I) was all there gotta start some where :thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
It's circling now...it's been at it for about 5 minutes now...the wait is unbearable!
Circling
It appears to have no end to the blue circling boot screen. I tried clearing cache and factory reset using CWM, no cigar still. Any fixes for this?
The CM version is the 10.1 stable release for hercules.
The gapps version is the 20130301 version.
which link did you flash for the CM what thread point in the right direction where you flashed from ? if you booted up the first flash and gapps were incorrect it shouldnt matter when you update the gapps it wipes the old files just make sure to wipe dalvik/cache and reboot
My Idiocy
I am retarded. I decided to go and unroot the phone and flash a stock rom and try again. I then flashed twrp via odin (which I prefer now) with no problems. But for some reason, no matter how many times I clear everything and try different kernels, the device will just not root. I have tried the superuser zips from the official site, I have tried the superuser from CWM's site, nothing works. Gah. Now what? Am I stuck stock forever?
Babbalabba said:
? Am I stuck stock forever?
Click to expand...
Click to collapse
Just use TWRP to flash whatever (Hercules) ROM you want. Make sure you wipe dalvik, cache, system and data.
Alright, I will try a wipe again, and then flash a custom ROM. If it doesn't root me I will report back with the situation. Thank you for all your help!
Um, just another question before I proceed with wipe and rom...if the ROM is based off of JB 4.2.2, such as Cyanogen mod, will my phone just run 4.2.2 as part of the rom, or will it be incompatible?
EDIT: Never mind...
I love you all forever. It works, and I have gapps running and root access. Thank you so much...I really don't know what to say.
tl;dr: What happens if I upgrade to CWM 6 after having used Darkside Superwipe on CWM 5?
And now the long explanation of what happened:
I have a Telus T989D, and I had installed the stock Telus JB ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2343748
I previously had CWM, but as per the instructions in the thread I installed TWRP, ran the Infamous Superwipe zip file, and then proceeded to flash the ROM.
Then today I decided to install CM 10.1. The first thing I did was flash CWM 6.x (I forget the exact version, but it was the latest one) from ODIN. Then I downloaded the latest stable build (CM 10.1.2). I then ran the Infamous Superwipe zip file again, and flashed CM 10.1. The result was that the phone would get stuck on the Cyanogenmod circle logo. I did some Googling and found out some people who had bootloops after installing Cyanogenmod, and it was suggested that this was due to a bad wipe, and that using Darkside Superwipe would fix the problem. So I proceeded to give Darkside Superwipe a try... Of course at the time I hadn't realized that 1) What I had was not actually a boot loop (it wasn't rebooting, it was just stuck at the logo), and 2) that Darkside Superwipe should not be used with CWM 6. After flashing the Darkside file, my CWM 6 would load up but would fail to flash ANY zip file that I selected (it would just get stuck on the first line, "Installing xxx.zip"). It would also fail to wipe the /cache partition (would freeze at "wiping /cache partition").
After soft-bricking my phone by trying to flash a different recovery from Heimdall, I ended up following a guide on this forum to flash the stock Gingerbread ROM from Odin. I then flashed CWM 5.0.2.7, did the Darkside Superwipe, installed CM 10.1, and now thankfully the phone works.
My question is... Does anybody know what happened here? And any ideas what will happen if I try to upgrade my CyanogenMod later on? Will I have any issues running CWM 5.x with CM 10.1 or 10.2? I'm a bit afraid of updating to CWM 6 since I have no idea what the result will be.
I later learned that Infamous Wipe is only to be used with TW-based 4.1.2 ROMs, since it adds a preload partition. Did I end up somehow messing up my partitions by using the Infamous & Darkside Superwipe files?
Sorry for the long post... I just figured I should give as much information as possible! I'd really appreciate it if anybody has an explanation for what happened (messed up partitions?) and how to fix it!
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Faruk88 said:
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Click to expand...
Click to collapse
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Faruk88 said:
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Click to expand...
Click to collapse
U can use goo manager if u want, but I will say this, sometimes too can cause soft bricks, in which case u would need Odin to recover , so in my professional opinion I would suggest using Odin from scratch
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app