Related
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!
Ok Fellow EVO owners, for those of you still around, I know you are busy applying the S-Off and Root to your phones, but have any of you tried the next steps of loading another ROM? I am currently trying to load on CM7, however after it finishes flashing the ROM, it boots into the flash animation and just stays there. Tried clearing cache to no avail. Looking for possible solution...
Need more information.
Most likely you aren't wiping SYSTEM, however.
Flash Dalvik?
What information do you need?
I have to admit I am new to the Android scene. Phone was updated to the OTA when I purchased so I have been lurking till now.
Here is what details I have:
S-Off via the Revolutionary method just released
Replaced Clockworks with Amon-RA
Successfully performed backup and restore of device to test
Downloaded CM7 latest Stable version and placed on SD-Card
Booted into recovery and wiped Cache and Dalvik-cache
Flashed .zip from SD-Card
Got the message that it was successful
Within Amon-Ra selected reboot device
Device booted into the flash screen for CM7 and it just keeps cycling that screen over and over, it never actually proceeds into the OS
If you need more let me know.
Thanks
You need to wipe everything.
Sent from my PC36100 using XDA Premium App
freejack347 said:
What information do you need?
I have to admit I am new to the Android scene. Phone was updated to the OTA when I purchased so I have been lurking till now.
Here is what details I have:
S-Off via the Revolutionary method just released
Replaced Clockworks with Amon-RA
Successfully performed backup and restore of device to test
Downloaded CM7 latest Stable version and placed on SD-Card
Booted into recovery and wiped Cache and Dalvik-cache
Flashed .zip from SD-Card
Got the message that it was successful
Within Amon-Ra selected reboot device
Device booted into the flash screen for CM7 and it just keeps cycling that screen over and over, it never actually proceeds into the OS
If you need more let me know.
Thanks
Click to expand...
Click to collapse
First let me say, Welcome to the flashing scene. You will be an addict and we're here to help you out
I would recommend flashing this first:
http://dc370.4shared.com/download/KV-YsWJ7/VR_SUPERWIPE.zip?tsid=20110815-030517-d546271d
This will wipe your phone's memory.
Then flash the CM7.zip. Let me know how this goes for you dude.
Wipe Data, System, Cache, Dalvik, android.secure, SDext, boot, and everything I might've forgotten (except SD card). Flash VR Superwipe (http://www.virusrom.com/Tools/VR_SUPERWIPE.zip). Flash Cyanogenmod, flash GAPPS (Google Apps: you want this if you want Market and such - packaged separately due to legal issues). Reboot, enjoy
tropicalbrit said:
Wipe Data, System, Cache, Dalvik, android.secure, SDext, boot, and everything I might've forgotten (except SD card). Flash VR Superwipe (http://www.virusrom.com/Tools/VR_SUPERWIPE.zip). Flash Cyanogenmod, flash GAPPS (Google Apps: you want this if you want Market and such - packaged separately due to legal issues). Reboot, enjoy
Click to expand...
Click to collapse
+1...Here's the GAPPS so you won't have to google it:
http://cmw.22aaf3.com/gapps/gapps-gb-20110613-signed.zip
spyd312 said:
+1...Here's the GAPPS so you won't have to google it
Click to expand...
Click to collapse
I looked around for like an HOUR trying to figure out the gapps issue, couldn't find the package. (day 3 of S-off/root)
I do have a question tho, is the SPRINT Visual Voicemail available in the market or do you need a special package to get it to work? I have seen a little about it on the forums but have yet to find much info..
I know there is a gapps zip in the evo deck thread that has sprint vvm included. That rom is very similar to cm so you could try flashing that gapps instead.
Anyone know if cm7 and that gapps package has been tried... going to bed now but could try tmrw.
Sent from my cm7 PC36100 using XDA App
infallibleapex said:
I looked around for like an HOUR trying to figure out the gapps issue, couldn't find the package. (day 3 of S-off/root)
I do have a question tho, is the SPRINT Visual Voicemail available in the market or do you need a special package to get it to work? I have seen a little about it on the forums but have yet to find much info..
Click to expand...
Click to collapse
If u search on here there is a fix for the sprint vvm. If when on a sense rom use titanium backup to back up sprint vvm including data. Then once u flash cm7 and its up and running use titanium backup to restore sprint vvm + data. There is a flashable zip also somewhere around here. Id link u to the thread but I'm on my phone right now
To op if all the wiping doesn't seem to work it could be ur SD card. Sometimes it goes bad. Transfer everything off and then format SD card after that transfer things back and try again
Papa Smurf151 said:
If u search on here there is a fix for the sprint vvm. If when on a sense rom use titanium backup to back up sprint vvm including data. Then once u flash cm7 and its up and running use titanium backup to restore sprint vvm + data. There is a flashable zip also somewhere around here. Id link u to the thread but I'm on my phone right now
Click to expand...
Click to collapse
I appreciate it. I tossed the one from the DECK EVO thread on the card, did a backup and will try flashing it tomorrow... i gotta got to work in a few hours and this website is like crack, I can't stop trolling...
confirmed, the gapps+vm from the deck evo thread worked like a charm..
i cannot load any 2.3 rom on my evo none, only froyo an ideas
Did you fully wipe before you flash
sent from my HTC evolution running a freshly baked gingerbread with the 4gs in it
foresure84 said:
i cannot load any 2.3 rom on my evo none, only froyo an ideas
Click to expand...
Click to collapse
Its either your recovery, not wiping correctly, or bad downloads.
neither, i can load any froyo rom, just not 2.3
what do you think
teh roxxorz said:
Its either your recovery, not wiping correctly, or bad downloads.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1277431
foresure84 said:
http://forum.xda-developers.com/showthread.php?t=1277431
Click to expand...
Click to collapse
No, because its for the 3D. Another user tried flashing it and it just doesn't flash; luckily it didn't brick his phone.
teh roxxorz said:
No, because its for the 3D. Another user tried flashing it and it just doesn't flash; luckily it didn't brick his phone.
Click to expand...
Click to collapse
thnks i'm stumped
foresure84 said:
thnks i'm stumped
Click to expand...
Click to collapse
What he's saying is that the ROM you linked to is for the EVO 3D, not the regular EVO. Make sure that you are attempting to flash an EVO ROM and if you still have problems then please post a description of exactly what happens when you try to flash a gb ROM.
Sent from my PC36100 using XDA App
every time, i try to load a 2.3 rom, it just bootloops at the slash screen, i've done many, phones, prior to this, so i'm familiar with most of the does and don'ts (this is my tester phone), my daily evo i had no problems updating to GB
i cant load any GB roms on this evo....( it's my testing evo) strange they all do the same thing just keep rebooting on the splash screen this evo is hardware 003, the last rom on this is
android 2.21
baseband 2.15.00.09.1
kernel is 2.6.32.24- kings-havs ocUv
build bumber
caulkins evio 2 rom v1.5
software number
3.30.651.2
pri 1.77-003
prl version
60662
foresure84 said:
i cant load any GB roms on this evo....( it's my testing evo) strange they all do the same thing just keep rebooting on the splash screen this evo is hardware 003, the last rom on this is....2
Click to expand...
Click to collapse
What recovery are you using? I would suggest you install AmonRa 2.3, if you are already using it reinstall it from a fresh download. Next wipe everything except your SD, wipe system, wipe boot, sdext, ect...
dafunk60 said:
What recovery are you using? I would suggest you install AmonRa 2.3, if you are already using it reinstall it from a fresh download. Next wipe everything except your SD, wipe system, wipe boot, sdext, ect...
Click to expand...
Click to collapse
every time, i try to load a 2.3 rom, it just bootloops at the slash screen, i've done many, phones, prior to this, so i'm familiar with most of the does and don'ts (this is my tester phone), my daily evo i had no problems updating to GB
foresure84 said:
every time, i try to load a 2.3 rom, it just bootloops at the slash screen, i've done many, phones, prior to this, so i'm familiar with most of the does and don'ts (this is my tester phone), my daily evo i had no problems updating to GB
Click to expand...
Click to collapse
I wasn't trying to insult your intelligence and I understand the issue you are trying to resolve. If I recall correctly it is caused by the boot partition not being wiped. This does not cause an issue when switching from 2.2 rom to 2.2 rom because kernels are specific to the version of android (and sometimes other system elements such as sense / asop). And again, if I recall correctly, the "wipe all" command on many older recoveries did not wipe the boot partition, or wipe it completely so when you go to boot your 2.3 system with a 2.2 kernel it doesn't work and you get a boot loop. Hence my question & suggestion. Best of luck finding a fix.
please update your radio to one of the ones that came with gingerbread and try again..remember the safer way to update radios is through bootloader and not recovery...and remember the phone will reboot during the update, do not touch the phone until it reboots a second time or you may brick it..
Okay here is what I did to get GB, on my (evo tester phone)
1) booted the evo into recovery
2) factory reset 2x
3) ran VR_SUPERWIPE 2x
4) then I ran, SNS SUPER WIPE 2x, still could not run 2.3 GB at all!!, trying all kind of things for a little over a week.
5) Went through my files, found an old RUU. (RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.71_003_release_147044_signed) THIS IS THE ON YOU HAVE TO PLUG THE EVO INTO THE COMPUTER TO RUN.
6) Booted the evo into bootloader, then ran the RUU.
7) REBOOTED PHONE,… okay looks like stock,
8) Rebooted to bootloader s-off, is now s-on…. Dayum
9) I said F**K IT… repeated steps 1-3, then ran (deo_4.54.651.1)
10) This is the same rom I tried to install all week, now it install, verified, the version, guess what. 2.3.3.. wtf
11) I then installed, GW (signed_Team-Nocturnal_Stock_RLS.02).. (it also restored my custom splash screen)
12) IT INSTALLED NO PROBLEM… WTF…
13) STILL WITH SUPER USER PRIVIELGES
14) How is this possible with s-on
Like ca1ne said. I am 99% sure your issue is outdated radios. Update those then flash a gingerbread Rom, preferably one based on the ota 4.54.
tapatalk signature here. lovely.
tommytomatoe said:
Like ca1ne said. I am 99% sure your issue is outdated radios. Update those then flash a gingerbread Rom, preferably one based on the ota 4.54.
tapatalk signature here. lovely.
Click to expand...
Click to collapse
tried that previously, also did you read the post above?
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.
Hey guys,
First post here,
i was searching around for my problem, and i haven't found an accurate answer so thought to share my problem and hopefully find an answer.
i am from Canada, Edmonton, and i am with Rogers.
First problem,
i run CM 10.1 and Most the NIGHTLY updates they were butter smooth and works great, until Update number CM-10.120130317 till the current update. All the updates i download, my phone freezes LOT! example of how it freezes , i try to unlock my phone, it freezes . I try to write something it freezes . and sometimes when its on sleep it freezes i can't turn the screen on again! so i always downgrade to CM-10.120130316 to have that stable ROM.
I did the wipe date /factory reset from the ROM manager, and wipe cache and dalvik. and yet the problem is not solve.
So my question is, dose anyone facing the same problem? or it's just me?
Second Problem
am having this beyond annoying notification, where it says my message has not been sent! but my message get's sent and all acts normal. But i always get notification and its never gone. I have screen shoot the problem. Is there a way i can fix this? i've have attached in the thread.
if you guys have any questions or want me to provide some information please do ask.
Looking forward to hear the feedback.
Cheers,
for starts, you're running nightlies and you need to remember that. i'm not an advocate of these, but thats just my opinion. you generally cant run a non-perfected piece of software and repeatedly dirty flash layers of updates on top. you will generally begin to experience bugs that can only be fixed with a full wipe and clean install.
that being said, i would either 1) commit to these cm10.1 nightlies and perhaps even just stick with 1 of them thats working well for you or 2), find a stable 4.1 or 4.2 rom and install after a full wipe. backup first.
There's a warning that these builds are unstable and use them at your own risk. I use cm10.1 20130317 build and it is extremely stable. A few quirks but nothing major. I plan on sticking with it since the 3.4 kernel on the newer nightlies isn't optimized yet, which result is lower battery life.
Sent from my SAMSUNG-SGH-I747
xBeerdroiDx said:
for starts, you're running nightlies and you need to remember that. i'm not an advocate of these, but thats just my opinion. you generally cant run a non-perfected piece of software and repeatedly dirty flash layers of updates on top. you will generally begin to experience bugs that can only be fixed with a full wipe and clean install.
that being said, i would either 1) commit to these cm10.1 nightlies and perhaps even just stick with 1 of them thats working well for you or 2), find a stable 4.1 or 4.2 rom and install after a full wipe. backup first.
Click to expand...
Click to collapse
Domoo said:
There's a warning that these builds are unstable and use them at your own risk. I use cm10.1 20130317 build and it is extremely stable. A few quirks but nothing major. I plan on sticking with it since the 3.4 kernel on the newer nightlies isn't optimized yet, which result is lower battery life.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Thank you guys for the time to post in my thread. Alright, i will stick with update that runs well in my cellphone..
However for my second problem, do you know how i can fix that problem? i am talking about the message not sent notification.
Thanks in advance!
xBeerdroiDx said:
that being said, i would either 1) commit to these cm10.1 nightlies and perhaps even just stick with 1 of them thats working well for you or 2), find a stable 4.1 or 4.2 rom and install after a full wipe. backup first.
Click to expand...
Click to collapse
MH_91 said:
However for my second problem, do you know how i can fix that problem? i am talking about the message not sent notification.
Click to expand...
Click to collapse
assuming you have a stable backup to rely on, i would wipe data/factory rest, wipe cache, wipe dalvik cache and reflash either your current update or (preferably) the one you were running with no problems before. perhaps flash the one listed by a user above that seems to be running well
xBeerdroiDx said:
assuming you have a stable backup to rely on, i would wipe data/factory rest, wipe cache, wipe dalvik cache and reflash either your current update or (preferably) the one you were running with no problems before. perhaps flash the one listed by a user above that seems to be running well
Click to expand...
Click to collapse
Yes, i am have backed up all my stuff. oddly, i did all that you have mentioned last weekend, and still i got those glitches and the text matter it was gone at the start, but i got it back again.
Noob question, what dose "Flash" exactly means? maybe i know what flash step is, but i didnt know it was called by that term lol..
MH_91 said:
Yes, i am have backed up all my stuff. oddly, i did all that you have mentioned last weekend, and still i got those glitches and the text matter it was gone at the start, but i got it back again.
Noob question, what dose "Flash" exactly means? maybe i know what flash step is, but i didnt know it was called by that term lol..
Click to expand...
Click to collapse
and you tried flashing a different (previous) version of cm10.1 when you did that? there's always a full wipe. that includes formatting /system in recovery.
flash = install.
xBeerdroiDx said:
and you tried flashing a different (previous) version of cm10.1 when you did that? there's always a full wipe. that includes formatting /system in recovery.
flash = install.
Click to expand...
Click to collapse
Interesting.. i have got an idea i will try to do it hopefully by tonight or tomorrow. and i will share the results.
i was thinking to manually download the latest update nightlies instead of my phone update it for me, and then do the wipe thing and then i install it manually, maybe that will fix my problem.
am using G cloud for my backup and it dose his job pretty well. I wanted to use the Titanium backup but it kinda was too complicated for me.
Why they just don't call it "install" instead of Flash then lol?
MH_91 said:
Interesting.. i have got an idea i will try to do it hopefully by tonight or tomorrow. and i will share the results.
i was thinking to manually download the latest update nightlies instead of my phone update it for me, and then do the wipe thing and then i install it manually, maybe that will fix my problem.
am using G cloud for my backup and it dose his job pretty well. I wanted to use the Titanium backup but it kinda was too complicated for me.
Why they just don't call it "install" instead of Flash then lol?
Click to expand...
Click to collapse
avoid using the OTA update feature on your phone. i didnt know you were doing things that way. you'll notice many more bugs and problems that route.
you are on the right path when you say download the actual update (latest release) yourself. make sure you have the gapps to go with it. boot into cwm, wipe data/both cache, flash rom, flash gapps
xBeerdroiDx said:
avoid using the OTA update feature on your phone. i didnt know you were doing things that way. you'll notice many more bugs and problems that route.
you are on the right path when you say download the actual update (latest release) yourself. make sure you have the gapps to go with it. boot into cwm, wipe data/both cache, flash rom, flash gapps
Click to expand...
Click to collapse
Will do mate! Thank you so much for your kind help! i really appreciated it. i will for sure share the results with you very soon.
Have a good one.